From d684d2d4b7e9bc8a1fcad58dfa5f8006ee5bb1ca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:30:54 -0500
Subject: [PATCH 0001/1325] New translations developer-faqs.mdx (Russian)

---
 .../pages/ru/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/ru/developing/developer-faqs.mdx b/website/pages/ru/developing/developer-faqs.mdx
index 178862db0a24..7ae20c6b3db9 100644
--- a/website/pages/ru/developing/developer-faqs.mdx
+++ b/website/pages/ru/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Часто задаваемы вопросы для разработчиков
 ---
 
-## 1. Что такое субграф?
+На этой странице собраны некоторые из наиболее частых вопросов для разработчиков, использующих The Graph.
 
-Субграф - это пользовательский API, построенный на данных блокчейна. Субграфы запрашиваются с помощью языка запросов GraphQL и развертываются на ноде Graph с помощью Graph CLI. После развертывания и публикации в децентрализованной сети The Graph индексаторы обрабатывают субграфы и делают их доступными для запросов со стороны потребителей субграфов.
+## Вопросы, связанные с субграфом
 
-## 2. Могу ли я удалить свой субграф?
+### 1. Что такое субграф?
 
-После создания субграфов их удаление невозможно.
+Субграф - это пользовательский API, построенный на данных блокчейна. Субграфы запрашиваются с использованием языка запросов GraphQL и развертываются на Graph Node с помощью Graph CLI. После развертывания и публикации в децентрализованной сети The Graph индексаторы обрабатывают субграфы и делают их доступными для запросов потребителей субграфов.
 
-## 3. Могу ли я изменить имя своего субграфа?
+### 2. Каков первый шаг в создании субграфа?
 
-Нет. После создания субграфа изменить его имя нельзя. Обязательно хорошо подумайте, прежде чем создавать свой субграф, чтобы его можно было легко найти и идентифицировать другими децентрализованными приложениями.
+Для успешного создания субграфа Вам потребуется установить The Graph CLI. Перед началом работы, ознакомьтесь с разделом [Быстрый старт](/quick-start/). Подробную информацию см. в разделе [Создание субграфа](/developing/creating-a-subgraph/).
 
-## 4. Могу ли я изменить учетную запись GitHub, связанную с моим субграфом?
+### 3. Могу ли я создать субграф, если в моих смарт-контрактах нет событий?
 
-Нет. После создания субграфа связанная с ним учетная запись GitHub не может быть изменена. Обязательно как следует обдумайте этот вопрос перед созданием субграфа.
+Настоятельно рекомендуется структурировать смарт-контракты так, чтобы они содержали события, связанные с данными, которые вы хотите запросить. Обработчики событий в субграфе срабатывают на события контракта и являются самым быстрым способом получения нужных данных.
 
-## 5. Могу ли я создать субграф, если в моих смарт-контрактах нет событий?
+Если контракты, с которыми Вы работаете, не содержат событий, Ваш субграф может использовать обработчики вызовов и блоков для запуска индексации. Хотя это не рекомендуется, так как производительность будет существенно ниже.
 
-Настоятельно рекомендуется структурировать свои смарт-контракты так, чтобы события были связаны с данными, которые Вы хотите запросить. Обработчики событий в субрафе запускаются событиями контракта и являются самым быстрым способом получения полезных данных.
+### 4. Могу ли я изменить учетную запись GitHub, связанную с моим субграфом?
 
-Если контракты, с которыми Вы работаете, не содержат событий, Ваш субграф может использовать обработчики вызовов и блоков для запуска индексации. Хотя это не рекомендуется, так как производительность будет значительно ниже.
+Нет. После создания субграфа связанная с ним учетная запись GitHub не может быть изменена. Пожалуйста, учтите это перед созданием субграфа.
 
-## 6. Можно ли развернуть один субграф с одним и тем же именем для нескольких сетей?
+### 5. Как обновить субграф в майннете?
 
-Вам понадобятся отдельные имена для нескольких сетей. Хотя у Вас не может быть разных субграфов под одним и тем же именем, есть удобные способы иметь единую кодовую базу для нескольких сетей. Подробнее об этом читайте в нашей документации: [Повторное развертывание субграфа](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+Вы можете развернуть новую версию своего субграфа в Subgraph Studio с помощью интерфейса командной строки (CLI). Это действие сохраняет конфиденциальность вашего субграфа, но, если результат Вас удовлетворит, Вы сможете опубликовать его в Graph Explorer. При этом будет создана новая версия Вашего субграфа, на которую Кураторы смогут начать подавать сигналы.
 
-## 7. Чем шаблоны отличаются от источников данных?
+### 6. Можно ли дублировать субграф на другую учетную запись или конечную точку без повторного развертывания?
 
-Шаблоны позволяют создавать источники данных на лету, пока Ваш субграф индексируется. Может случиться так, что Ваш контракт будет создавать новые контракты по мере того, как люди будут с ним взаимодействовать, и, поскольку Вы заранее знаете стуктуру этих контрактов (ABI, события и т. д.), Вы сможете определить, как Вы хотите индексировать их в шаблоне и, когда они сгенерируются, Ваш субграф создаст динамический источник данных, предоставив адрес контракта.
+Вы должны повторно развернуть субграф, но если идентификатор субграфа (хэш IPFS) не изменится, его не нужно будет синхронизировать с самого начала.
+
+### 7. Как вызвать контрактную функцию или получить доступ к публичной переменной состояния из моих мэппингов субграфа?
+
+Просмотрите положение `Доступ к смарт-контракту` в разделе [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Могу ли я импортировать `ethers.js` или другие библиотеки JS в мои мэппинги субграфов?
+
+В настоящее время нет, так как мэппинги написаны на языке AssemblyScript.
+
+Одним из возможных альтернативных решений является хранение необработанных данных в объектах и выполнение логики, для которой требуются библиотеки JS на клиенте.
+
+### 9. При прослушивании нескольких контрактов, возможно ли выбрать порядок прослушивания событий контрактов?
+
+Внутри субграфа события всегда обрабатываются в том порядке, в котором они появляются в блоках, независимо от того, относится ли это к нескольким контрактам или нет.
+
+### 10. Чем шаблоны отличаются от источников данных?
+
+Шаблоны позволяют Вам быстро создавать источники данных, пока Ваш субграф индексируется. Ваш контракт может создавать новые контракты по мере того, как люди будут с ним взаимодействовать. Поскольку форма этих контрактов (ABI, события и т. д.) известна заранее, Вы сможете определить, как Вы хотите индексировать их в шаблоне. Когда они будут сгенерированы, Ваш субграф создаст динамический источник данных, предоставив адрес контракта.
 
 Ознакомьтесь с параграфом "Создание экземпляра шаблона источника данных" в разделе: [Шаблоны источников данных](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. Как убедиться, что я использую последнюю версию graph-node для своих локальных развертываний?
+### 11. Можно ли настроить субграф с помощью `graph init` из `graph-cli` с двумя контрактами? Или мне следует вручную добавить другой источник данных в `subgraph.yaml` после запуска `graph init`?
 
-Вы можете запустить следующую команду:
+Да. В самой команде `graph init` Вы можете добавлять несколько источников данных, вводя контракты один за другим.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+Вы также можете использовать команду `graph add` для добавления нового источника данных.
 
-**ПРИМЕЧАНИЕ:** docker / docker-compose всегда будет использовать ту версию graph-node, которая была получена при первом запуске, поэтому важно сделать это, чтобы убедиться, что Вы используете последнюю версию graph-node.
+### 12. В каком порядке вызываются обработчики событий, блоков и вызовов для источника данных?
 
-## 9. Как вызвать контрактную функцию или получить доступ к публичной переменной состояния из моих мэппингов субграфа?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Можно ли настроить субграф с помощью `graph init` из `graph-cli` с двумя контрактами? Или мне следует вручную добавить другой источник данных в `subgraph.yaml` после запуска `graph init`?
+### 13. Как убедиться, что я использую последнюю версию graph-node для своих локальных развертываний?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+Вы можете запустить следующую команду:
 
-## 11. Я хочу внести свой вклад или добавить issue на GitHub. Где я могу найти репозитории с открытым исходным кодом?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Примечание: docker / docker-compose всегда будет использовать ту версию graph-node, которая была получена при первом запуске, поэтому убедитесь, что используете последнюю версию graph-node.
 
-## 12. Каков рекомендуемый способ создания "автоматически сгенерированных" идентификаторов для объекта при обработке событий?
+### 14. Каков рекомендуемый способ создания "автоматически сгенерированных" идентификаторов для объекта при обработке событий?
 
 Если во время события создается только один объект и нет ничего лучшего, то индекс хэша транзакции и журнала будет уникальным. Вы можете замаскировать их, преобразовав в байты, а затем, пропустив через `crypto.keccak256`, но это не сделает их более уникальными.
 
-## 13. Можно ли при прослушивании нескольких контрактов выбрать порядок, в котором контракты прослушивают события?
+### 15. Могу ли я удалить свой субграф?
 
-Внутри субграфа события всегда обрабатываются в том порядке, в котором они появляются в блоках, независимо от того, относится ли это к нескольким контрактам или нет.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
+
+## Вопросы, связанный с сетью
+
+### 16. Какие сети поддерживает The Graph?
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+Вы можете найти список поддерживаемых сетей [здесь](/developing/supported-networks).
+
+### 17. Можно ли различать сети (майннет, Sepolia, локальную) внутри обработчиков событий?
 
 Да. Вы можете это сделать, импортировав `graph-ts`, как показано в примере ниже:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
-
-Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
+### 18. Поддерживаете ли Вы обработчики блоков и вызовов на Sepolia?
 
-## 16. Могу ли я импортировать ethers.js или другие библиотеки JS в мои мэппинги субграфов?
+Да. Sepolia поддерживает обработчики блоков, обработчики вызовов и обработчики событий. Следует отметить, что обработчики событий намного более эффективны, чем два других обработчика, и они поддерживаются в каждой сети, совместимой с EVM.
 
-В настоящее время нет, так как сопоставления написаны на AssemblyScript. Одним из возможных альтернативных решений является хранение необработанных данных в объектах и выполнение логики, для которой требуются библиотеки JS на клиенте.
+## Вопросы, связанные с Индексированием & Запросами
 
-## 17. Можно ли указать, с какого блока следует начинать индексацию?
+### 19. Можно ли указать, с какого блока следует начинать индексирование?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Да. `dataSources.source.startBlock` в файле `subgraph.yaml` указывает номер блока, с которого источник данных начинает индексирование. В большинстве случаев мы предлагаем использовать блок, в котором создавался контракт: [Стартовые блоки](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Есть ли какие-нибудь советы по увеличению производительности индексации? Мой субграф очень долго синхронизируется
+### 20. Есть ли какие-либо советы по увеличению производительности индексирования? Синхронизация моего субграфа занимает очень много времени
 
 Да, Вам следует обратить внимание на дополнительную функцию стартового блока, чтобы начать индексирование с блока, в котором был развернут контракт: [Стартовые блоки](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Есть ли способ непосредственно выполнить запрос к субграфу, чтобы определить последний номер блока, который он проиндексировал?
+### 21. Есть ли способ напрямую запросить субграф, чтобы определить номер последнего проиндексированного блока?
 
 Да! Попробуйте выполнить следующую команду, заменив "organization/subgraphName" на название организации, под которой она опубликована, и имя Вашего субграфа:
 
@@ -102,44 +121,27 @@ Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the n
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. Какие сети поддерживает The Graph?
-
-Вы можете найти список поддерживаемых сетей [здесь](/developing/supported-networks).
-
-## 21. Можно ли дублировать субграф на другую учетную запись или эндпоинт без повторного развертывания?
-
-Вы должны повторно развернуть субграф, но если идентификатор субграфа (хэш IPFS) не изменится, его не нужно будет синхронизировать с самого начала.
-
-## 22. Можно ли использовать Apollo Federation поверх graph-node?
+### 22. Есть ли ограничение на количество объектов, которые The Graph может вернуть за один запрос?
 
-Federation пока не поддерживается, хотя мы хотим сделать это в будущем. На данный момент Вы можете использовать объединение схем либо на клиенте, либо через прокси-сервис.
-
-## 23. Есть ли ограничение на количество объектов, которые The Graph может вернуть за один запрос?
-
-По умолчанию ответы на запросы ограничены 100 единицами на коллекцию. Если Вы хотите получать больше, Вы можете довести количество до 1000 единиц на коллекцию, а после этого можно переводить их в пагинацию:
+По умолчанию ответы на запросы ограничены 100 единицами на коллекцию. Если Вы хотите получить больше, Вы можете довести количество до 1000 единиц на коллекцию, а для получения ещё большего количества можно использовать пагинацию:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. Если мой интерфейс децентрализованного приложения использует The Graph для запросов, нужно ли мне напрямую записывать ключ запроса во внешний интерфейс? Не станут ли очень высокими комиссии за запросы пользователей вследствие их злонамеренных действий?
-
-В настоящее время рекомендуемым подходом для децентрализованного приложения является добавление ключа во внешний интерфейс и предоставление его конечным пользователям. Тем не менее, Вы можете ограничить этот ключ именем хоста, например _yourdapp.io_ и субграфом. Шлюз в настоящее время управляется Edge & Node. Частью ответственности шлюза является отслеживание неправомерного поведения и блокировка трафика от вредоносных клиентов.
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Перейдите в Hosted Service, чтобы найти субграфы, которые Вы или другие развернули в нём. Вы можете найти его [здесь](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-The Graph никогда не будет взимать плату за Hosted Service. The Graph — это децентрализованный протокол, и взимание платы за централизованную услугу не соответствует ценностям The Graph. Hosted Service всегда был временным шагом, помогающим получить доступ к децентрализованной сети. У разработчиков будет достаточно времени, чтобы перейти на децентрализованную сеть, когда им будет удобно.
+В настоящее время рекомендуемым подходом для децентрализованного приложения является добавление ключа во внешний интерфейс и предоставление его конечным пользователям. При этом Вы можете ограничить этот ключ именем хоста, например _yourdapp.io_ и субграфом. Шлюз в настоящее время находится в управлении Edge & Node. Частью ответственности шлюза является отслеживание злоупотреблений и блокировка трафика от вредоносных клиентов.
 
-## 27. How do I update a subgraph on mainnet?
+## Прочее
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Можно ли использовать Apollo Federation поверх graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation пока не поддерживается. В настоящее время Вы можете использовать объединение схем либо на клиенте, либо через прокси-сервис.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. Я хочу внести свой вклад или добавить задачу на GitHub. Где я могу найти репозитории с открытым исходным кодом?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 5b12cb0edfeae8f2d0c0de387d121cd44d0250bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:30:56 -0500
Subject: [PATCH 0002/1325] New translations supported-networks.mdx (Turkish)

---
 .../pages/tr/developing/supported-networks.mdx   | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/tr/developing/supported-networks.mdx b/website/pages/tr/developing/supported-networks.mdx
index b2e82c63136e..964822fcca6d 100644
--- a/website/pages/tr/developing/supported-networks.mdx
+++ b/website/pages/tr/developing/supported-networks.mdx
@@ -9,16 +9,16 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 
 <SupportedNetworksTable networks={props.networks} />
 
-\* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).  
-\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
+\* Temel ağ desteği, [yükseltme Endeksleyicisi](https://thegraph.com/blog/upgrade-indexer/) tarafından sağlanmaktadır.  
+\*\* Graph Düğümü ile Entegrasyon: `evm`, `near`, `cosmos`, `osmosis` ve `ar`, Graph Düğümü'nde yerel işleyici (handler) ve tür (type) desteğine sahiptir. Firehose ve Substreams uyumlu zincirler, genelleştirilmiş [Substreams destekli subgraph](/cookbook/substreams-powered-subgraphs) entegrasyonundan yararlanabilir (`evm` ve `near` ağları buna dahil). &#8288;<sup>†</sup> [Substreams destekli subgraph’lerin](/cookbook/substreams-powered-subgraphs) dağıtımını destekler.
 
-- Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
-- If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
+- Subgraph Studio, örneğin JSON-RPC, Firehose ve Substreams uç noktaları gibi temel teknolojilerin istikrarlılığına ve güvenilirliğine bel bağlar.
+- Gnosis Chain’i endeksleyen subgraph'ler artık `gnosis` ağ tanımlayıcısı ile dağıtılabilir.
+- Bir subgraph CLI aracılığıyla yayımlandıysa ve bir Endeksleyici tarafından algılandıysa, teknik olarak, desteklenmeden de sorgulanabilir. Yeni ağların entegrasyonunu daha da kolaylaştırmak için çalışmalar devam etmektedir.
 - Merkeziyetsiz ağda hangi özelliklerin desteklendiğinin tam listesi için [bu sayfaya](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) göz atın.
 
-## Running Graph Node locally
+## Graph Düğümünü yerel olarak çalıştırma
 
-If your preferred network isn't supported on The Graph's decentralized network, you can run your own [Graph Node](https://github.com/graphprotocol/graph-node) to index any EVM-compatible network. Make sure that the [version](https://github.com/graphprotocol/graph-node/releases) you are using supports the network and you have the needed configuration.
+Tercih ettiğiniz ağ The Graph’in merkeziyetsiz ağı tarafından desteklenmiyorsa, herhangi bir EVM uyumlu ağı endekslemek için kendi [Graph Düğümü'nüzü](https://github.com/graphprotocol/graph-node) çalıştırabilirsiniz. Kullandığınız [sürümün](https://github.com/graphprotocol/graph-node/releases) ağı desteklediğinden ve gerekli yapılandırmaları yaptığınızdan emin olun.
 
-Graph Node can also index other protocols, via a Firehose integration. Firehose integrations have been created for NEAR, Arweave and Cosmos-based networks. Additionally, Graph Node can support Substreams-powered subgraphs for any network with Substreams support.
+Graph Düğümü, Firehose entegrasyonu aracılığıyla diğer protokolleri de endeksleyebilir. NEAR, Arweave ve Cosmos tabanlı ağlar için Firehose entegrasyonları oluşturulmuştur. Ayrıca, Graph Düğümü, Substreams desteğine sahip herhangi bir ağ için Substreams destekli subgraph'leri de destekleyebilir.

From c4dbc70e2ef8cee4911e35301d85d51f0ef1a45e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:30:57 -0500
Subject: [PATCH 0003/1325] New translations subgraph-studio-faqs.mdx (Turkish)

---
 .../tr/deploying/subgraph-studio-faqs.mdx      | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/tr/deploying/subgraph-studio-faqs.mdx b/website/pages/tr/deploying/subgraph-studio-faqs.mdx
index d276978f68ce..8213fdbbac4a 100644
--- a/website/pages/tr/deploying/subgraph-studio-faqs.mdx
+++ b/website/pages/tr/deploying/subgraph-studio-faqs.mdx
@@ -1,31 +1,31 @@
 ---
-title: Subgraph Studio FAQs
+title: Subgrap Studio Hakkında SSS
 ---
 
 ## 1. Subgraph Stüdyo Nedir?
 
-[Subgraph Studio](https://thegraph.com/studio/) is a dapp for creating, managing, and publishing subgraphs and API keys.
+[Subgraph Studio](https://thegraph.com/studio/), subgraph'ler ve API anahtarları oluşturmak, yönetmek ve yayımlamaya yarayan bir dapp'tir.
 
 ## 2. API Anahtarını Nasıl Oluşturabilirim?
 
-To create an API, navigate to Subgraph Studio and connect your wallet. You will be able to click the API keys tab at the top. There, you will be able to create an API key.
+Bir API oluşturmak için Subgraph Studio'ya gidin ve cüzdanınızı bağlayın. Üst kısımda API anahtarları sekmesine tıklayabilirsiniz. Orada bir API anahtarı oluşturabileceksiniz.
 
 ## 3. Birden Çok API Anahtarı Oluşturabilir miyim?
 
-Yes! You can create multiple API Keys to use in different projects. Check out the link [here](https://thegraph.com/studio/apikeys/).
+Evet! Farklı projelerde kullanmak için birden fazla API anahtarı oluşturabilirsiniz. Daha fazla bilgi için [buraya](https://thegraph.com/studio/apikeys/) göz atın.
 
 ## 4. API Anahtarı için Domain'i Nasıl Kısıtlarım?
 
-After creating an API Key, in the Security section, you can define the domains that can query a specific API Key.
+Bir API Anahtarı oluşturduktan sonra, Güvenlik bölümünde belirli bir API Anahtarını sorgulayabilecek alanları tanımlayabilirsiniz.
 
 ## 5. Subgraph'ımı Başka Birine Devredebilir miyim?
 
-Yes, subgraphs that have been published to Arbitrum One can be transferred to a new wallet or a Multisig. You can do so by clicking the three dots next to the 'Publish' button on the subgraph's details page and selecting 'Transfer ownership'.
+Evet, Arbitrum One'da yayımlanmış subgraph'ler yeni bir cüzdana veya bir Multisig'e aktarılabilir. Bunu, subgraph'in ayrıntılar sayfasında 'Yayımla' düğmesinin yanındaki üç noktaya tıklayıp 'Sahipliği devret' seçeneğini seçerek yapabilirsiniz.
 
-Note that you will no longer be able to see or edit the subgraph in Studio once it has been transferred.
+Subgraph'i devrettikten sonra onu Studio'da artık göremeyeceğinizi veya düzenleyemeyeceğinizi unutmayın.
 
 ## 6. Kullanmak İstediğim Subgraph'ın Geliştiricisi Değilsem, bu Subgraphlar için Sorgu URL'lerini Nasıl Bulabilirim?
 
-You can find the query URL of each subgraph in the Subgraph Details section of Graph Explorer. When you click on the “Query” button, you will be directed to a pane wherein you can view the query URL of the subgraph you’re interested in. You can then replace the `<api_key>` placeholder with the API key you wish to leverage in Subgraph Studio.
+Her bir subgraph'in sorgu URL'sini Graph Gezgini'ndeki Subgraph Ayrıntıları bölümünde bulabilirsiniz. “Sorgula” düğmesine tıkladığınızda, ilgilendiğiniz subgraph'in sorgu URL'sini görüntüleyebileceğiniz bir panele yönlendirilirsiniz. Ardından, `<api_key>` yer tutucusunu Subgraph Studio’da kullanmak istediğiniz API anahtarı ile değiştirebilirsiniz.
 
-Remember that you can create an API key and query any subgraph published to the network, even if you build a subgraph yourself. These queries via the new API key, are paid queries as any other on the network.
+Unutmayın, bir API anahtarı oluşturarak ağda yayımlanmış herhangi bir subgraph'i sorgulayabilirsiniz; bu durum, kendi subgraph'inizi oluşturmuş olsanız bile geçerlidir. Bu yeni API anahtarı üzerinden yapılan sorgular, ağdaki diğer sorgular gibi ücretlidir.

From fb63a585d4d175fa33715873ed9eb55dcfc79d4e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:30:58 -0500
Subject: [PATCH 0004/1325] New translations developer-faqs.mdx (Turkish)

---
 .../pages/tr/developing/developer-faqs.mdx    | 152 +++++++++---------
 1 file changed, 77 insertions(+), 75 deletions(-)

diff --git a/website/pages/tr/developing/developer-faqs.mdx b/website/pages/tr/developing/developer-faqs.mdx
index b3d712bb4de8..c21248d34942 100644
--- a/website/pages/tr/developing/developer-faqs.mdx
+++ b/website/pages/tr/developing/developer-faqs.mdx
@@ -2,144 +2,146 @@
 title: Geliştirici SSS
 ---
 
-## 1. Subgraph nedir?
+Bu sayfa, The Graph üzerinde geliştirme yapan geliştiricilerin sunduğu en yaygın soruların bazılarını özetlemektedir.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph ile İlgili Sorular
 
-## 2. Subgraph'ımı silebilir miyim?
+### 1. Subgraph nedir?
 
-It is not possible to delete subgraphs once they are created.
+Bir subgraph, blokzinciri verilerine dayalı olarak oluşturulmuş özel yapım bir API’dir. Subgraph'ler, GraphQL sorgu dili kullanılarak sorgulanır ve The Graph CLI kullanılarak bir Graph Düğümü'nde yayına alınır. Dağıtılıp The Graph’in merkeziyetsiz ağına yayımlandığında, Endeksleyiciler subgraph'leri işler ve sorgu yapmaları için kullanıcıların erişimine sunar.
 
-## 3. Subgraph ismimi değiştirebilir miyim?
+### 2. Subgraph oluşturmanın ilk adımı nedir?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+Başarılı bir şekilde subgraph oluşturmak için The Graph CLI’yi kurmanız gerekir. Başlamak için [Hızlı Başlangıç](/quick-start/) bölümüne göz atın. Ayrıntılı bilgi için [Subgraph Oluşturma](/developing/creating-a-subgraph/) bölümünü inceleyin.
 
-## 4. Subgraph'ımla ilişkili GitHub hesabını değiştirebilir miyim?
+### 3. Akıllı sözleşmelerim olay içermiyorsa yine de subgraph oluşturabilir miyim?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+Akıllı sözleşmelerinizi, sorgulamak istediğiniz verilerle ilişkili olaylara sahip olacak şekilde yapılandırmanız şiddetle önerilir. Subgraph içindeki olay işleyicileri sözleşme olayları tarafından tetiklenir ve kullanışlı verilere erişmenin en hızlı yolu bu işleyicileri kullanmaktır.
 
-## 5. Akıllı sözleşmelerimin olayları yoksa yine de bir subgraph oluşturabilir miyim?
+Eğer çalıştığınız sözleşmeler olay içermiyorsa, subgraph’inizin endekslenmesini çağrı ve blok işleyicileri kullanarak tetikleyebilirsiniz. Ancak bu tavsiye edilmeyen bir yöntemdir ve performansı önemli ölçüde yavaşlatacaktır.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Subgraph'ımla ilişkili GitHub hesabını değiştirebilir miyim?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+Hayır. Bir subgraph oluşturulduktan sonra, ilişkili GitHub hesabı değiştirilemez. Bu nedenle, subgraph oluşturmadan önce bunu dikkatlice düşünmelisiniz.
 
-## 6. Birden fazla ağ için aynı isme sahip bir subgraph'ı dağıtmak mümkün mü?
+### 5. Mainnet'teki bir subgraph nasıl güncellenir?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+CLI'yi kullanarak Subgraph Studio’ya yeni bir subgraph sürümü dağıtabilirsiniz. Bu işlem subgraph’inizi gizli olarak tutar, ancak memnun kaldığınızda Graph Gezgini’nde yayımlayabilirsiniz. Bu, Küratörlerin sinyal vermeye başlayabileceği yeni bir subgraph sürümü oluşturur.
 
-## 7. Şablonların veri kaynaklarından farkı nedir?
+### 6. Bir subgraph’i yeniden dağıtmadan başka bir hesaba veya uç noktaya kopyalayabilir miyim?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+Subgraph’i yeniden dağıtmanız gerekir ancak subgraph ID'si (IPFS hash’i) değişmezse, senkronizasyona baştan başlamanıza gerek kalmaz.
 
-Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
+### 7. Subgraph eşlemelerinden sözleşme fonksiyonunu nasıl çağırabilir veya bir genel durum değişkenine nasıl erişebilirim?
 
-## 8. Yerel dağıtımlarım için graph-node'un en son sürümünü kullandığımdan nasıl emin olabilirim?
+[AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state) bölümündeki `Akıllı sözleşmeye erişim` kısmına göz atın.
 
-You can run the following command:
+### 8. Subgraph eşleyicilerinde `ethers.js` veya diğer JS kütüphanelerini kullanabilir miyim?
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+Eşleyiciler AssemblyScript ile yazıldığından dolayı şu anda mümkün değil.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+Bunun alternatif bir çözümü, verileri varlıklarda ham halde depolayıp, JS kütüphanelerine ihtiyaç duyan işlemleri istemci üzerinde gerçekleştirmektir.
 
-## 9. Subgraph eşleştirmelerimden bir sözleşme fonksiyonunu nasıl çağırabilirim veya genel bir durum değişkenine nasıl erişebilirim?
+### 9. Birden fazla sözleşmeyi dinlerken, olayları dinlenecek sözleşmelerin sırasını seçmek mümkün müdür?
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+Bir subgraph içindeki olaylar, birden fazla sözleşme üzerinde olup olmamaya bakmaksızın her zaman bloklarda göründükleri sırayla işlenir.
 
-## 10. İki sözleşme ile `graph-cli`den `graph init` kullanarak bir subgraph oluşturmak mümkün mü? Yoksa `graph init`'i çalıştırdıktan sonra `subgraph.yaml` dosyasına manuel olarak başka bir veri kaynağı mı eklemeliyim?
+### 10. Şablonlar veri kaynaklarından ne açıdan farklıdır?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+Şablonlar, subgraph’iniz endeksleme yaparken veri kaynaklarını hızlıca oluşturmanızı sağlar. Sözleşmeniz, kullanıcılar etkileşime girdikçe yeni sözleşmeler yaratabilir. Bu sözleşmelerin yapısını (ABI, olaylar vb.) önceden bildiğinizden, onları nasıl endekslemek istediğinizi bir şablonda tanımlayabilirsiniz. Yeni sözleşmeler oluşturulduğunda, subgraph’iniz sözleşme adresini tespit ederek dinamik bir veri kaynağı oluşturacaktır.
 
-## 11. Katkıda bulunmak veya bir GitHub sorunu eklemek istiyorum. Açık kaynak depolarını nerede bulabilirim?
+"Bir Veri Kaynağı Şablonunu Başlatma" bölümüne göz atın: [Veri Kaynağı Şablonları](/developing/creating-a-subgraph#data-source-templates).
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+### 11. `graph init` komutunu `graph-cli` ile kullanarak iki sözleşme içeren bir subgraph kurmak mümkün müdür? Yoksa `graph init` komutunu çalıştırdıktan sonra `subgraph.yaml` dosyasına elle bir başka dataSource eklemem mi gerekir?
 
-## 12. Olayları işlerken bir varlık için "otomatik oluşturulan" kimlikler oluşturmanın önerilen yolu nedir?
+Evet, mümkündür. `graph init` komutunu kullanırken, sözleşmeleri art arda girerek birden fazla dataSource ekleyebilirsiniz.
 
-If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
+Ayrıca, yeni bir dataSource eklemek için `graph add` komutunu da kullanabilirsiniz.
 
-## 13. Birden fazla sözleşmenin etkinliklerini gözlemlerken, olayların etkinliklerini gözlemlemek için sözleşme sırasını seçmek mümkün mü?
+### 12. Bir veri kaynağı için olay, blok ve çağrı işleyicileri hangi sırayla tetiklenir?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Olay ve çağrı işleyicileri, öncelikle blok içindeki işlem indisine göre sıralanır. Aynı işlem içindeki olay ve çağrı işleyicileri, şu sıralama kuralına düzenlenir: önce olay işleyicileri, ardından çağrı işleyicileri gelir; her tür kendi içinde manifestoda tanımlandığı sıraya uyar. Blok işleyicileri, olay ve çağrı işleyicilerinden sonra çalıştırılır ve manifestoda tanımlandıkları sıraya göre gerçekleştirilir. Ayrıca, bu sıralama kuralları değişime tabi olabilir.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+Yeni dinamik veri kaynakları oluşturulduğunda, dinamik veri kaynakları için tanımlanan işleyiciler yalnızca mevcut tüm veri kaynağı işleyicileri işlendiğinde işlemeye başlar ve her tetiklendiğinde aynı sırada tekrar eder.
 
-Yes. You can do this by importing `graph-ts` as per the example below:
+### 13. Yerel çalışma ortamımda graph-node'un en son sürümünü kullandığımdan nasıl emin olabilirim?
 
-```javascript
-import { dataSource } from '@graphprotocol/graph-ts'
+Aşağıdaki komutu çalıştırabilirsiniz:
 
-dataSource.network()
-dataSource.address()
+```sh
+docker pull graphprotocol/graph-node:latest
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+> Not: docker / docker-compose, ilk çalıştırdığınızda çekilen graph-node sürümünü kullanmaya devam edecektir. Bu yüzden en son graph-node sürümünü kullandığınızdan emin olun.
 
-Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
+### 14. Olayları işlerken bir varlık için "otomatik oluşturulan" id'leri yaratmanın önerilen yolu nedir?
 
-## 16. Subgraph eşleştirmelerime ethers.js veya diğer JS kütüphanelerini aktarabilir miyim?
+Eğer olay sırasında yalnızca bir varlık oluşturuluyorsa ve daha iyi bir seçenek yoksa, işlem hash'i + log indisi benzersiz bir id olur. Bunları Bytes'a dönüştürüp `crypto.keccak256` üzerinden geçirerek gizleyebilirsiniz ancak bu işlemi daha benzersiz hale getirmez.
 
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+### 15. Subgraph'imi silebilir miyim?
 
-## 17. İndekslemeye hangi bloktan başlanacağını belirtmek mümkün mü?
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+## Ağ ile İlgili Sorular
 
-## 18. İndeksleme performansını artırmak için bazı ipuçları var mı? Subgraph'ımın senkronize edilmesi çok uzun zaman alıyor
+### 16. The Graph hangi ağları desteklemektedir?
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Desteklenen ağların listesini [burada](/developing/supported-networks) bulabilirsiniz.
 
-## 19. Subgraph üzerinde doğrudan sorgulama yaparak indekslediği en son blok numarasını belirlemenin bir yol var mı?
+### 17. Olay işleyicileri içerisinde ağlar (mainnet, Sepolia, yerel) arasında ayrım yapmak mümkün müdür?
 
-Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
+Evet, mümkündür. Aşağıdaki örnekteki gibi `graph-ts` kullanarak yapabilirsiniz:
 
-```sh
-curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
+```javascript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+dataSource.network()
+dataSource.address()
 ```
 
-## 20. Graph hangi ağları destekliyor?
+### 18. Sepolia ağında blok ve çağrı işleyicilerini destekliyor musunuz?
 
-You can find the list of the supported networks [here](/developing/supported-networks).
+Evet. Sepolia, blok işleyicileri, çağrı işleyicileri ve olay işleyicilerini destekler. Olay işleyicilerinin diğer iki işleyiciye göre çok daha yüksek performansa sahip olduğu ve tüm EVM uyumlu ağlarda desteklendiği unutulmamalıdır.
 
-## 21. Bir subgraph'ı yeniden dağıtmadan başka bir hesaba veya uç noktaya çoğaltmak mümkün mü?
+## Endeksleme ve Sorgulama ile İlgili Sorular
 
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+### 19. Endekslemeye hangi bloktan başlanacağını belirtmek mümkün müdür?
 
-## 22. Apollo Federation'ı graph-node üzerinde kullanmak mümkün mü?
+Evet. `subgraph.yaml` dosyasındaki `dataSources.source.startBlock`, veri kaynağının endekslemeye başladığı blok numarasını belirtir. Çoğu durumda, sözleşmenin oluşturulduğu bloğun kullanılmasını öneriyoruz. Daha fazla bilgi için: [Başlangıç blokları](/developing/creating-a-subgraph#start-blocks)
 
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
+### 20. Endeksleme performansını artırmak için ipuçları var mı? Subgraph'imin senkronize edilmesi çok uzun zaman alıyor
 
-## 23. Graph'ın sorgu başına kaç nesne döndürebileceğine dair bir sınır var mı?
+Sözleşmenin dağıtıldığı bloktan itibaren endeksleme yapmak için opsiyonel başlangıç bloğu özelliğine göz atabilirsiniz: [Başlangıç blokları](/developing/creating-a-subgraph#start-blocks)
 
-By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
+### 21. Subgraph üzerinde doğrudan sorgulama yaparak endekslenmiş en son blok numarasını öğrenmenin bir yolu var mı?
 
-```graphql
-someCollection(first: 1000, skip: <number>) { ... }
-```
+Var! Aşağıdaki komutu, "organization/subgraphName" kısmına subgraph'inizi yayımladığınız organizasyon adını ve subgraph'inizin adını koyarak deneyin:
 
-## Dapp önyüzüm Graph'ı sorgulamak için kullanıyorsa, sorgu anahtarını önyüze doğrudan yazmam gerekiyor mu? Kullanıcılar için sorgu ücreti ödesek, kötü niyetli kullanıcılar sorgu ücretlerimizin çok yüksek olmasına neden olabilir mi?
+```sh
+curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
+```
 
-Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
+### 22. The Graph'in sorgu başına kaç nesne döndürebileceğine dair bir sınır var mı?
 
-## 25. Where do I go to find my current subgraph on the hosted service?
+Varsayılan olarak, sorgu yanıtları koleksiyon başına 100 ögeyle sınırlıdır. Daha fazlasını almak istiyorsanız koleksiyon başına 1000 ögeye kadar çıkabilirsiniz. Daha da fazlası için şu şekilde sayfalama yapabilirsiniz:
 
-Sizin veya başkalarının barındırılan hizmete dağıttığı subgraphları bulmak için barındırılan hizmete gidin. [Burada](https://thegraph.com/hosted-service) bulabilirsiniz.
+```graphql
+someCollection(first: 1000, skip: <sayı>) { ... }
+```
 
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-Graph, barındırılan hizmet için asla ücret talep etmeyecektir. Graph merkeziyetsiz bir protokoldür ve merkezi bir hizmet için ücret almak Graph'in değerleriyle uyuşmamaktadır. Barındırılan hizmet, merkeziyetsiz ağa ulaşmaya yardımcı olmak için her zaman geçici bir adım olmuştur. Geliştiriciler, merkeziyetsiz ağa rahatça yükseltebilmek için yeterli süreye sahip olacaklardır.
+Şu anda, bir merkeziyetsiz uygulama için önerilen yaklaşım, anahtarı önyüze eklemek ve son kullanıcılara göstermektir. Bununla birlikte, bu anahtarı _yourdapp.io_ gibi bir sunucu adına ve bir subgraph'e sınırlayabilirsiniz. Ağ geçidi şu anda Edge & Node tarafından çalıştırılıyor. Bir ağ geçidinin sorumluluğunun bir kısmı, kötü amaçlı davranışları izlemek ve kötü niyetli istemcilerden gelen trafiği engellemektir.
 
-## 27. How do I update a subgraph on mainnet?
+## Diğer
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Apollo Federation'ı graph-node üzerinde kullanmak mümkün mü?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation henüz desteklenmiyor. Şu anda, şema birleştirme yöntemini ya istemci tarafında ya da bir proxy hizmeti aracılığıyla kullanabilirsiniz.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. Katkıda bulunmak veya bir GitHub issue'su eklemek istiyorum. Açık kaynak kod depolarını nerede bulabilirim?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 34fddc7f30787e035b20312ca5baa61ec90d17b8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:30:59 -0500
Subject: [PATCH 0005/1325] New translations developer-faqs.mdx (Hindi)

---
 .../pages/hi/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/hi/developing/developer-faqs.mdx b/website/pages/hi/developing/developer-faqs.mdx
index ce378ef44162..ec23a849d8cb 100644
--- a/website/pages/hi/developing/developer-faqs.mdx
+++ b/website/pages/hi/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: डेवलपर अक्सर पूछे जाने वाले प्रश्न
 ---
 
-## 1. सबग्राफ क्या है?
+यह पृष्ठ 'The Graph' पर निर्माण कर रहे डेवलपर्स के लिए कुछ सामान्य प्रश्नों का सारांश प्रस्तुत करता है।
 
-एक सबग्राफ ब्लॉकचैन डेटा पर निर्मित एक कस्टम एपीआई है। सबग्राफ को ग्राफ़क्यूएल क्वेरी भाषा का उपयोग करके पूछताछ की जाती है और ग्राफ़ सीएलआई का उपयोग करके ग्राफ़ नोड पर तैनात किया जाता है। एक बार द ग्राफ के विकेंद्रीकृत नेटवर्क पर तैनात और प्रकाशित होने के बाद, इंडेक्सर्स सबग्राफ को प्रोसेस करते हैं और उन्हें सबग्राफ उपभोक्ताओं द्वारा पूछे जाने के लिए उपलब्ध कराते हैं।
+## सबग्रह संबंधित
 
-## 2. क्या मैं अपना सबग्राफ मिटा सकता हूँ?
+### 1. सबग्राफ क्या है?
 
-सबग्राफ बनाने के बाद उन्हें हटाना संभव नहीं है।
+एक subgraph एक कस्टम API है जो ब्लॉकचेन डेटा पर आधारित है। subgraphs को GraphQL क्वेरी भाषा का उपयोग करके क्वेरी किया जाता है और इन्हें The Graph CLI का उपयोग करके Graph Node पर तैनात किया जाता है। एक बार तैनात और The Graph के विकेन्द्रीकृत नेटवर्क पर प्रकाशित होने के बाद, Indexers subgraphs को प्रोसेस करते हैं और उन्हें subgraph उपभोक्ताओं के लिए क्वेरी करने के लिए उपलब्ध कराते हैं।
 
-## 3. क्या मैं अपना सबग्राफ नाम बदल सकता हूँ?
+### 2. एक Subgraph बनाने का पहला कदम क्या है?
 
-नहीं। एक बार सबग्राफ बन जाने के बाद, नाम बदला नहीं जा सकता। अपना सबग्राफ बनाने से पहले इस पर सावधानी से विचार करना सुनिश्चित करें ताकि यह आसानी से खोजा जा सके और अन्य डैप द्वारा पहचाना जा सके।
+एक सबग्रह को सफलतापूर्वक बनाने के लिए, आपको The Graph CLI स्थापित करने की आवश्यकता होगी। आरंभ करने के लिए [Quick Start](/quick-start/) की समीक्षा करें। विस्तृत जानकारी के लिए, देखें [Creating a Subgraph](/developing/creating-a-subgraph/)।
 
-## 4. क्या मैं अपने सबग्राफ से जुड़े GitHub खाते को बदल सकता हूँ?
+### 3. क्या मैं अभी भी एक subgraph बना सकता हूँ यदि मेरी स्मार्ट कॉन्ट्रैक्ट्स में कोई इवेंट्स नहीं हैं?
 
-नहीं। एक बार सबग्राफ बन जाने के बाद, संबंधित GitHub खाते को बदला नहीं जा सकता। अपना सबग्राफ बनाने से पहले इस पर ध्यान से विचार करना सुनिश्चित करें।
+यह अत्यधिक अनुशंसित है कि आप अपने स्मार्ट अनुबंधों को इस तरह से संरचित करें कि उन डेटा के साथ घटनाएँ हों जिनमें आपकी रुचि है। अनुबंध की घटनाओं द्वारा संचालित 'event handlers' को Subgraph में ट्रिगर किया जाता है और यह उपयोगी डेटा प्राप्त करने का सबसे तेज़ तरीका है।
 
-## 5. अगर मेरे स्मार्ट कॉन्ट्रैक्ट में इवेंट नहीं हैं तो क्या मैं अब भी सबग्राफ बना सकता हूं?
+अगर आप जिन अनुबंधों के साथ काम कर रहे हैं, उनमें घटनाएँ नहीं हैं, तो आपका subgraph कॉल और ब्लॉक हैंडलर्स का उपयोग कर सकता है ताकि इंडेक्सिंग को ट्रिगर किया जा सके। हालाँकि, यह अनुशंसित नहीं है, क्योंकि प्रदर्शन काफी धीमा होगा।
 
-यह अत्यधिक अनुशंसा की जाती है कि आप अपने स्मार्ट अनुबंधों को उस डेटा से संबंधित घटनाओं के लिए तैयार करें, जिसे आप क्वेरी करने में रुचि रखते हैं। सबग्राफ में ईवेंट हैंडलर अनुबंध की घटनाओं से ट्रिगर होते हैं और उपयोगी डेटा को पुनः प्राप्त करने का सबसे तेज़ तरीका हैं।
+### 4. क्या मैं अपने सबग्राफ से जुड़े GitHub खाते को बदल सकता हूँ?
 
-यदि आप जिन अनुबंधों के साथ काम कर रहे हैं, उनमें घटनाएँ नहीं हैं, तो आपका सबग्राफ इंडेक्सिंग को ट्रिगर करने के लिए कॉल और ब्लॉक हैंडलर का उपयोग कर सकता है। हालांकि यह अनुशंसित नहीं है, क्योंकि प्रदर्शन काफी धीमा होगा।
+एक बार जब एक subgraph बनाया जाता है, तो संबंधित GitHub खाता नहीं बदला जा सकता है। कृपया अपने subgraph को बनाने से पहले इसे ध्यान से विचार करें।
 
-## 6. क्या कई नेटवर्क के लिए एक ही नाम के साथ एक सबग्राफ को तैनात करना संभव है?
+### 5. मैं मुख्य नेटवर्क पर एक subgraph को कैसे अपडेट करूँ?
 
-आपको कई नेटवर्क के लिए अलग-अलग नामों की आवश्यकता होगी। जबकि आपके पास एक ही नाम के तहत अलग-अलग सबग्राफ नहीं हो सकते हैं, कई नेटवर्क के लिए एक ही कोडबेस रखने के सुविधाजनक तरीके हैं। हमारे दस्तावेज़ में इस पर अधिक जानकारी प्राप्त करें: [Redeploying-a-subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+आप अपने subgraph का नया संस्करण Subgraph Studio में CLI का उपयोग करके डिप्लॉय कर सकते हैं। यह क्रिया आपके subgraph को निजी रखती है, लेकिन जब आप इससे खुश हों, तो आप Graph Explorer में इसे प्रकाशित कर सकते हैं। इससे आपके subgraph का एक नया संस्करण बनेगा जिस पर Curators सिग्नल करना शुरू कर सकते हैं।
 
-## 7. टेम्प्लेट डेटा स्रोतों से कैसे भिन्न हैं?
+### 6. एक Subgraph को दूसरे खाते या एंडपॉइंट पर बिना पुनः तैनात किए डुप्लिकेट करना संभव है?
 
-टेम्प्लेट आपको तुरंत डेटा स्रोत बनाने की अनुमति देते हैं, जबकि आपका सबग्राफ इंडेक्स कर रहा होता है। यह मामला हो सकता है कि आपका अनुबंध नए अनुबंधों को जन्म देगा क्योंकि लोग इसके साथ बातचीत करते हैं, और चूंकि आप उन अनुबंधों (एबीआई, घटनाओं, आदि) के आकार को जानते हैं, इसलिए आप परिभाषित कर सकते हैं कि आप उन्हें एक टेम्पलेट में कैसे अनुक्रमित करना चाहते हैं और जब वे आपका सबग्राफ अनुबंध के पते की आपूर्ति करके एक गतिशील डेटा स्रोत बनाएगा।
+आपको सबग्राफ को फिर से तैनात करना होगा, लेकिन अगर सबग्राफ आईडी (आईपीएफएस हैश) नहीं बदलता है, तो इसे शुरुआत से सिंक नहीं करना पड़ेगा।
+
+### 7. आप अपने subgraph mappings से एक contract function को कैसे कॉल करें या एक सार्वजनिक state variable तक कैसे पहुँचें?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. क्या मैं अपने subgraph mappings में `ethers.js` या अन्य JS पुस्तकालय आयात कर सकता हूँ?
+
+AssemblyScript में वर्तमान में मैपिंग्स नहीं लिखी जा रही हैं।
+
+एक संभावित वैकल्पिक समाधान यह है कि कच्चे डेटा को एंटिटीज़ में स्टोर किया जाए और जो लॉजिक JS पुस्तकालय की आवश्यकता होती है, उसे क्लाइंट पर किया जाए।
+
+### 9. कई कॉन्ट्रैक्ट सुनते समय, क्या घटनाओं को सुनने के लिए कॉन्ट्रैक्ट के क्रम का चयन करना संभव है?
+
+एक सबग्राफ के भीतर, घटनाओं को हमेशा उसी क्रम में संसाधित किया जाता है जिस क्रम में वे ब्लॉक में दिखाई देते हैं, भले ही वह कई अनुबंधों में हो या नहीं।
+
+### 10. टेम्प्लेट्स और डेटा स्रोतों में क्या अंतर है?
+
+Templates आपको डेटा स्रोतों को तेजी से बनाने की अनुमति देते हैं, जबकि आपका subgraph इंडेक्सिंग कर रहा है। आपका कॉन्ट्रैक्ट नए कॉन्ट्रैक्ट उत्पन्न कर सकता है जब लोग इसके साथ इंटरैक्ट करते हैं। चूंकि आप उन कॉन्ट्रैक्टों का आकार (ABI, इवेंट, आदि) पहले से जानते हैं, आप यह निर्धारित कर सकते हैं कि आप उन्हें एक टेम्पलेट में कैसे इंडेक्स करना चाहते हैं। जब वे उत्पन्न होते हैं, तो आपका subgraph कॉन्ट्रैक्ट पते को प्रदान करके एक डायनामिक डेटा स्रोत बनाएगा।
 
 "डेटा स्रोत टेम्प्लेट को तत्काल बनाना" अनुभाग देखें: [डेटा स्रोत टेम्प्लेट](/developing/creating-a-subgraph#data-source-templates)।
 
-## 8. मैं कैसे सुनिश्चित करूं कि मैं अपने स्थानीय परिनियोजन के लिए ग्राफ-नोड के नवीनतम संस्करण का उपयोग कर रहा हूं?
+### 11. क्या `graph init` का उपयोग करके `graph-cli` से एक subgraph सेट करना संभव है जिसमें दो कॉन्ट्रैक्ट हैं? या मुझे `graph init` चलाने के बाद `subgraph.yaml` में एक और dataSource मैन्युअल रूप से जोड़ना चाहिए?
 
-आप निम्न आदेश चला सकते हैं:
+हाँ। `graph init` कमांड पर आप एक के बाद एक कॉन्ट्रैक्ट दर्ज करके कई dataSources जोड़ सकते हैं।
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+आप इसका भी उपयोग कर सकते हैं `graph add` कमांड एक नया dataSource जोड़ने के लिए।
 
-**ध्यान दें:** docker / docker-compose हमेशा किसी भी ग्राफ-नोड संस्करण का उपयोग करेगा जिसे आपने पहली बार चलाया था, इसलिए यह सुनिश्चित करने के लिए ऐसा करना महत्वपूर्ण है कि आप नवीनतम संस्करण के साथ अद्यतित हैं ग्राफ-नोड का।
+### 12. एक डेटा स्रोत के लिए इवेंट, ब्लॉक और कॉल हैंडलर्स को किस क्रम में ट्रिगर किया जाता है?
 
-## 9. मैं अपने सबग्राफ मैपिंग से किसी अनुबंध फ़ंक्शन को कैसे कॉल करूं या किसी सार्वजनिक स्थिति चर तक कैसे पहुंचूं?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. क्या दो अनुबंधों के साथ `graph-cli` से `graph init` का उपयोग करके एक सबग्राफ सेट करना संभव है? या `graph init` चलाने के बाद मुझे `subgraph.yaml` में मैन्युअल रूप से एक और डेटा स्रोत जोड़ना चाहिए?
+### 13. यह सुनिश्चित करने के लिए कि मैं अपने स्थानीय डिप्लॉयमेंट के लिए graph-node का नवीनतम संस्करण उपयोग कर रहा हूँ?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+आप निम्न आदेश चला सकते हैं:
 
-## 11. मैं गिटहब मुद्दे में योगदान देना चाहता हूं या जोड़ना चाहता हूं। मुझे ओपन सोर्स रिपॉजिटरी कहां मिल सकती है?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> ध्यान दें: docker / docker-compose हमेशा उसी graph-node संस्करण का उपयोग करेगा जिसे आपने पहली बार इसे चलाने पर खींचा था, इसलिए सुनिश्चित करें कि आप graph-node के नवीनतम संस्करण के साथ अपडेट हैं।
 
-## 12. घटनाओं को संभालते समय एक इकाई के लिए "ऑटोजेनरेटेड" आईडी बनाने का अनुशंसित तरीका क्या है?
+### 14. इवेंट्स को हैंडल करते समय एक एंटिटी के लिए "स्वतः उत्पन्न" आईडी बनाने का अनुशंसित तरीका क्या है?
 
 यदि घटना के दौरान केवल एक इकाई बनाई जाती है और यदि कुछ भी बेहतर उपलब्ध नहीं है, तो लेन-देन हैश + लॉग इंडेक्स अद्वितीय होगा। आप इन्हें बाइट्स में परिवर्तित करके और फिर इसे `crypto.keccak256` के माध्यम से पाइप करके अस्पष्ट कर सकते हैं, लेकिन यह इसे और अधिक विशिष्ट नहीं बनाएगा।
 
-## 13. एकाधिक अनुबंधों को सुनते समय, क्या घटनाओं को सुनने के लिए अनुबंध आदेश का चयन करना संभव है?
+### 15. क्या मैं अपना subgraph हटा सकता हूँ?
 
-एक सबग्राफ के भीतर, घटनाओं को हमेशा उसी क्रम में संसाधित किया जाता है जिस क्रम में वे ब्लॉक में दिखाई देते हैं, भले ही वह कई अनुबंधों में हो या नहीं।
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## नेटवर्क से संबंधित।
+
+### 16. The Graph द्वारा समर्थित नेटवर्क कौन से हैं?
+
+आप समर्थित नेटवर्क की सूची [यहां](/Developing/supported-networks) प्राप्त कर सकते हैं।
+
+### 17. क्या इवेंट हैंडलर्स के भीतर नेटवर्क (mainnet, Sepolia, local) के बीच अंतर करना संभव है?
 
 हाँ। नीचे दिए गए उदाहरण के अनुसार आप `ग्राफ़-टीएस` आयात करके ऐसा कर सकते हैं:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. क्या आप Sepolia पर block और call handlers का समर्थन करते हैं?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. क्या मैं अपने सबग्राफ मैपिंग में ethers.js या अन्य JS लाइब्रेरी आयात कर सकता हूँ?
-
-वर्तमान में नहीं, क्योंकि मैपिंग असेंबलीस्क्रिप्ट में लिखे गए हैं। इसका एक संभावित वैकल्पिक समाधान संस्थाओं में कच्चे डेटा को स्टोर करना और तर्क करना है जिसके लिए क्लाइंट पर जेएस पुस्तकालयों की आवश्यकता होती है।
+## Indexing & Querying से संबंधित
 
-## 17. क्या यह निर्दिष्ट करना संभव है कि किस ब्लॉक पर अनुक्रमण शुरू करना है?
+### 19. क्या यह संभव है कि किस ब्लॉक से इंडेक्सिंग शुरू की जाए?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+`dataSources.source.startBlock` `subgraph.yaml` फ़ाइल में उस ब्लॉक का नंबर निर्दिष्ट करता है जिससे dataSource डेटा इंडेक्स करना शुरू करता है। अधिकांश मामलों में, हम अनुशंसा करते हैं कि उस ब्लॉक का उपयोग करें जहाँ अनुबंध बनाया गया था: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. क्या इंडेक्सिंग के प्रदर्शन को बढ़ाने के लिए कुछ टिप्स हैं? मेरा सबग्राफ सिंक होने में काफी समय ले रहा है
+### 20. यहां कुछ सुझाव दिए गए हैं ताकि इंडेक्सिंग का प्रदर्शन बढ़ सके। मेरा subgraph बहुत लंबे समय तक सिंक होने में समय ले रहा है।
 
-हां, आपको उस ब्लॉक से अनुक्रमण शुरू करने के लिए वैकल्पिक स्टार्ट ब्लॉक सुविधा पर एक नज़र डालनी चाहिए जिसे अनुबंध तैनात किया गया था: [स्टार्ट ब्लॉक](/developing/creating-a-subgraph#start-blocks)
+आपको वैकल्पिक 'स्टार्ट ब्लॉक' विशेषता पर एक नज़र डालनी चाहिए ताकि आप उस ब्लॉक से अनुक्रमण शुरू कर सकें जहां अनुबंध को तैनात किया गया था: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. क्या इंडेक्स किए गए नवीनतम ब्लॉक नंबर को निर्धारित करने के लिए सीधे सबग्राफ से पूछताछ करने का कोई तरीका है?
+### 21. क्या कोई तरीका है कि 'subgraph' को सीधे क्वेरी करके यह पता लगाया जा सके कि उसने कौन सा लेटेस्ट ब्लॉक नंबर इंडेक्स किया है?
 
 हाँ! निम्न आदेश का प्रयास करें, "संगठन/सबग्राफनाम" को उस संगठन के साथ प्रतिस्थापित करें जिसके अंतर्गत वह प्रकाशित है और आपके सबग्राफ का नाम:
 
@@ -102,44 +121,27 @@ Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the n
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. ग्राफ़ द्वारा कौन से नेटवर्क समर्थित हैं?
-
-आप समर्थित नेटवर्क की सूची [यहां](/Developing/supported-networks) प्राप्त कर सकते हैं।
-
-## 21. क्या किसी सबग्राफ को किसी अन्य खाते या समापन बिंदु पर पुन: नियोजित किए बिना डुप्लिकेट करना संभव है?
-
-आपको सबग्राफ को फिर से तैनात करना होगा, लेकिन अगर सबग्राफ आईडी (आईपीएफएस हैश) नहीं बदलता है, तो इसे शुरुआत से सिंक नहीं करना पड़ेगा।
-
-## 22. क्या ग्राफ-नोड के शीर्ष पर अपोलो फेडरेशन का उपयोग करना संभव है?
+### 22. क्या The Graph एक क्वेरी में कितने ऑब्जेक्ट्स वापस कर सकता है, इस पर कोई सीमा है?
 
-फेडरेशन अभी समर्थित नहीं है, हालांकि हम भविष्य में इसका समर्थन करना चाहते हैं। इस समय, आप जो कुछ कर सकते हैं वह क्लाइंट पर या प्रॉक्सी सेवा के माध्यम से स्कीमा सिलाई का उपयोग कर रहा है।
-
-## 23. क्या इसकी कोई सीमा है कि ग्राफ़ प्रति क्वेरी कितने ऑब्जेक्ट लौटा सकता है?
-
-डिफ़ॉल्ट रूप से, क्वेरी प्रतिसाद प्रति संग्रह 100 आइटम तक सीमित हैं। यदि आप अधिक प्राप्त करना चाहते हैं, तो आप प्रति संग्रह 1000 आइटम तक जा सकते हैं और उससे अधिक, आप पृष्ठांकित कर सकते हैं:
+डिफ़ॉल्ट रूप से, क्वेरी उत्तर हर संग्रह के लिए 100 आइटम तक सीमित होते हैं। यदि आप अधिक प्राप्त करना चाहते हैं, तो आप 1000 आइटम तक जा सकते हैं और उसके बाद, आप पेजिनेट कर सकते हैं:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. यदि मेरा डैप फ़्रंटएंड क्वेरी करने के लिए ग्राफ़ का उपयोग करता है, तो क्या मुझे अपनी क्वेरी कुंजी को सीधे फ़्रंटेंड में लिखने की आवश्यकता है? क्या होगा यदि हम उपयोगकर्ताओं के लिए क्वेरी शुल्क का भुगतान करते हैं - क्या दुर्भावनापूर्ण उपयोगकर्ता हमारी क्वेरी फीस बहुत अधिक होने का कारण बनेंगे?
-
-वर्तमान में, डैप के लिए अनुशंसित तरीका फ्रंटएंड में कुंजी जोड़ना और अंतिम उपयोगकर्ताओं के लिए इसे उजागर करना है। उस ने कहा, आप उस कुंजी को होस्टनाम तक सीमित कर सकते हैं, जैसे _yourdapp.io_ और सबग्राफ। गेटवे वर्तमान में Edge &amp द्वारा चलाया जा रहा है; नोड। गेटवे की जिम्मेदारी का हिस्सा अपमानजनक व्यवहार की निगरानी करना और दुर्भावनापूर्ण ग्राहकों से आने वाले ट्रैफ़िक को ब्लॉक करना है।
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
+वर्तमान में, एक dapp के लिए अनुशंसित तरीका यह है कि कुंजी को फ्रंटेंड में जोड़ा जाए और इसे एंड यूज़र्स के लिए एक्सपोज़ किया जाए। हालांकि, आप उस कुंजी को एक होस्टनेम जैसे _yourdapp.io_ और सबग्राफ़ तक सीमित कर सकते हैं। गेटवे को फिलहाल Edge & Node द्वारा चलाया जा रहा है। गेटवे की जिम्मेदारी का एक हिस्सा यह भी है कि वह दुरुपयोग करने वाले व्यवहार की निगरानी करे और दुर्भावनापूर्ण क्लाइंट्स से ट्रैफ़िक को ब्लॉक करे।
 
-## 27. How do I update a subgraph on mainnet?
+## विविध
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### क्या Apollo Federation  का उपयोग graph-node के ऊपर किया जा सकता है?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation अभी समर्थित नहीं है। फिलहाल, आप schema stitching का उपयोग कर सकते हैं, या तो क्लाइंट पर या एक प्रॉक्सी सेवा के माध्यम से।
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. मैं योगदान देना चाहता हूँ या कोई GitHub मुद्दा जोड़ना चाहता हूँ। मुझे ओपन सोर्स रिपॉज़िटरीज़ कहाँ मिल सकती हैं?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 04e85887a8d8d2cfaa4889749cebaca84d6a9b79 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:00 -0500
Subject: [PATCH 0006/1325] New translations indexing.mdx (Hindi)

---
 website/pages/hi/network/indexing.mdx | 48 +++++++++++++--------------
 1 file changed, 24 insertions(+), 24 deletions(-)

diff --git a/website/pages/hi/network/indexing.mdx b/website/pages/hi/network/indexing.mdx
index 2acc45128080..62544f991701 100644
--- a/website/pages/hi/network/indexing.mdx
+++ b/website/pages/hi/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 कई समुदाय-निर्मित डैशबोर्ड में लंबित पुरस्कार मान शामिल हैं और इन चरणों का पालन करके उन्हें आसानी से मैन्युअल रूप से चेक किया जा सकता है:
 
-1. सभी सक्रिय आवंटनों के लिए आईडी प्राप्त करने के लिए [मेननेट सबग्राफ](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) को क्वेरी करें:
+1. [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) से सभी सक्रिय आवंटनों के लिए IDs प्राप्त करने के लिए क्वेरी करें:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Once an allocation has been closed the rebates are available to be claimed by th
 - **माध्यम** - प्रोडक्शन इंडेक्सर प्रति सेकंड 100 सबग्राफ और 200-500 अनुरोधों का समर्थन करता है।
 - **बड़ा** - वर्तमान में उपयोग किए जाने वाले सभी सबग्राफ को अनुक्रमित करने और संबंधित ट्रैफ़िक के अनुरोधों को पूरा करने के लिए तैयार है।
 
-| Setup | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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               |
 
 ### एक इंडेक्सर को कौन सी बुनियादी सुरक्षा सावधानियां बरतनी चाहिए?
 
@@ -149,20 +149,20 @@ Once an allocation has been closed the rebates are available to be claimed by th
 
 #### Graph Node
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए) | / | --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<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए)           | /                                                    | --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<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Port | Purpose                                                  | Routes                                                                  | CLI Argument   | Environment Variable   |
+| ---- | -------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                       | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ graph indexer status
 
 - `ग्राफ़ अनुक्रमणिका नियम हो सकता है [विकल्प] <deployment-id>` — परिनियोजन के लिए `निर्णय आधार` को `नियमों` पर सेट करें, ताकि अनुक्रमणिका एजेंट अनुक्रमण नियमों का उपयोग करेगा यह तय करने के लिए कि इस परिनियोजन को अनुक्रमित करना है या नहीं।
 
-- `ग्राफ़ अनुक्रमणिका क्रियाओं को [विकल्प] <कार्रवाई-आईडी>` मिलता है - `सभी` का उपयोग करके एक या अधिक क्रियाएं प्राप्त करें या प्राप्त करने के लिए `कार्रवाई-आईडी` खाली छोड़ दें सभी क्रियाएं। एक अतिरिक्त तर्क `--status` का उपयोग किसी निश्चित स्थिति के सभी कार्यों को प्रिंट करने के लिए किया जा सकता है।
+- `ग्राफ़ Indexerक्रियाओं को [विकल्प] <कार्रवाई-आईडी>` मिलता है - `सभी` का उपयोग करके एक या अधिक क्रियाएं प्राप्त करें या प्राप्त करने के लिए `action-id` खाली छोड़ दें सभी क्रियाएं। एक अतिरिक्त तर्क `--status` का उपयोग किसी निश्चित स्थिति के सभी कार्यों को प्रिंट करने के लिए किया जा सकता है।
 
 - `ग्राफ इंडेक्सर एक्शन कतार आवंटन <deployment-id> <allocation-amount>` - कतार आवंटन कार्रवाई
 
@@ -559,7 +559,7 @@ graph indexer status
 
 - `ग्राफ़ अनुक्रमणिका क्रियाएँ स्वीकृत निष्पादित करती हैं` - कार्यकर्ता को स्वीकृत क्रियाओं को तुरंत निष्पादित करने के लिए बाध्य करें
 
-सभी आदेश जो आउटपुट में नियम प्रदर्शित करते हैं, समर्थित आउटपुट स्वरूपों (`तालिका`, `yaml`, और `json`) के बीच `का उपयोग करके चुन सकते हैं - आउटपुट` तर्क।
+सभी आदेश जो आउटपुट में नियम प्रदर्शित करते हैं, समर्थित आउटपुट स्वरूपों (`तालिका`, `yaml`, और `json`) के बीच ` का उपयोग करके चुन सकते हैं - आउटपुट ` तर्क।
 
 #### Indexing rules
 
@@ -623,7 +623,7 @@ graph indexer rules delete QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
 - सभी कतारबद्ध क्रियाओं को देखने के लिए इंडेक्सर `indexer-cli` का उपयोग कर सकता है
 - इंडेक्सर (या अन्य सॉफ़्टवेयर) `इंडेक्सर-क्ली` का उपयोग करके कतार में क्रियाओं को स्वीकृत या रद्द कर सकता है। स्वीकृति और रद्द करने के आदेश इनपुट के रूप में क्रिया आईडी की एक सरणी लेते हैं।
 - निष्पादन कार्यकर्ता नियमित रूप से स्वीकृत कार्यों के लिए कतार का चुनाव करता है। यह कतार से `अनुमोदित` कार्यों को पकड़ लेगा, उन्हें निष्पादित करने का प्रयास करेगा, और निष्पादन की स्थिति के आधार पर डीबी में मूल्यों को `सफलता` या `विफल< पर अपडेट करेगा। /0>.</li>
-  <li>If an action is successful the worker will ensure that there is an indexing rule present that tells the agent how to manage the allocation moving forward, useful when taking manual actions while the agent is in <code>auto` or `oversight` mode.
+<li>If an action is successful the worker will ensure that there is an indexing rule present that tells the agent how to manage the allocation moving forward, useful when taking manual actions while the agent is in <code>auto` or `oversight` mode.
 - अनुक्रमणक क्रिया निष्पादन के इतिहास को देखने के लिए क्रिया कतार की निगरानी कर सकता है और यदि आवश्यक हो तो निष्पादन विफल होने पर क्रिया आइटम को पुन: अनुमोदित और अद्यतन कर सकता है। क्रिया कतार पंक्तिबद्ध और की गई सभी कार्रवाइयों का इतिहास प्रदान करती है।
 
 डेटा मॉडल:
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### आवंटन का जीवन
 
-एक इंडेक्सर द्वारा बनाए जाने के बाद एक स्वस्थ आवंटन चार राज्यों से होकर जाता है।
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 164e53154ded9d52a475b365bbc0616bbc85cd31 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:01 -0500
Subject: [PATCH 0007/1325] New translations curating.mdx (French)

---
 website/pages/fr/network/curating.mdx | 96 ++++++++-------------------
 1 file changed, 29 insertions(+), 67 deletions(-)

diff --git a/website/pages/fr/network/curating.mdx b/website/pages/fr/network/curating.mdx
index f7b06fd56ac2..da503e1d6dea 100644
--- a/website/pages/fr/network/curating.mdx
+++ b/website/pages/fr/network/curating.mdx
@@ -2,75 +2,73 @@
 title: Curation
 ---
 
-Curators are critical to The Graph's decentralized economy. They use their knowledge of the web3 ecosystem to assess and signal on the subgraphs that should be indexed by The Graph Network. Through Graph Explorer, Curators view network data to make signaling decisions. In turn, The Graph Network rewards Curators who signal on good quality subgraphs with a share of the query fees those subgraphs generate. The amount of GRT signaled is one of the key considerations for indexers when determining which subgraphs to index.
+Les Curateurs jouent un rôle essentiel dans l'économie décentralisée de The Graph. Ils utilisent leur connaissance de l'écosystème web3 pour évaluer et signaler les subgraphs qui devraient être indexés par The Graph Network. à travers Graph Explorer, les Curateurs consultent les données du réseau pour prendre des décisions de signalisation. En retour, The Graph Network récompense les Curateurs qui signalent des subgraphs de bonne qualité en leur reversant une partie des frais de recherche générés par ces subgraphs. La quantité de GRT signalée est l'une des principales considérations des Indexeurs lorsqu'ils déterminent les subgraphs à indexer.
 
-## What Does Signaling Mean for The Graph Network?
+## Que signifie "le signalement" pour The Graph Network?
 
-Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
+Avant que les consommateurs ne puissent interroger un subgraphs, celui-ci doit être indexé. C'est ici que la curation entre en jeu. Afin que les Indexeurs puissent gagner des frais de requête substantiels sur des subgraphs de qualité, ils doivent savoir quels subgraphs indexer. Lorsque les Curateurs signalent un subgraphs , ils indiquent aux Indexeurs qu'un subgraphs est demandé et de qualité suffisante pour être indexé.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Les signaux des Curateurs sont représentés par des jetons ERC20 appelés Graph Curation Shares (GCS). Ceux qui veulent gagner plus de frais de requête doivent signaler leurs GRT aux subgraphs qui, selon eux, généreront un flux important de frais pour le réseau. Les Curateurs ne peuvent pas être réduits pour mauvais comportement, mais il y a une taxe de dépôt sur les Curateurs pour dissuader les mauvaises décisions pouvant nuire à l'intégrité du réseau. Les Curateurs gagneront également moins de frais de requête s'ils sélectionnent un subgraph de mauvaise qualité car il y aura moins de requêtes à traiter ou moins d'Indexeurs pour les traiter.
 
-Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
+Le [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) garantit l'indexation de tous les subgraphs. Signaler du GRT sur un subgraph particulier attirera plus d'indexeurs. Cette incitation d'indexeurs supplémentaires à travers la curation vise à améliorer la qualité du service pour les requêtes en réduisant la latence et en améliorant la disponibilité du réseau.
 
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
+Lors du signalement, les Curateurs peuvent décider de signaler une version spécifique du subgraph ou de signaler en utilisant l'auto-migration. S'ils signalent en utilisant l'auto-migration, les parts d'un Curateur seront toujours mises à jour vers la dernière version publiée par le développeur. S'ils décident de signaler une version spécifique, les parts resteront toujours sur cette version spécifique.
 
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
+Si vous avez besoin d'assistance avec la curation pour améliorer la qualité du service, veuillez envoyer une demande à l'équipe Edge & Node à l'adresse support@thegraph.zendesk.com et spécifier les subgraphs pour lesquels vous avez besoin d'assistance.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
+Les Indexeurs peuvent trouver des subgraphs à indexer en fonction des signaux de curation qu'ils voient dans Graph Explorer (capture d'écran ci-dessous).
 
 ![Les subgraphs d'exploration](/img/explorer-subgraphs.png)
 
 ## Comment signaler
 
-Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer)
+Dans l'onglet Curateur de Graph Explorer, les Curateurs pourront signaler et dé-signaler certains subgraphs en fonction des statistiques du réseau. Pour un aperçu étape par étape de la procédure à suivre dans Graph Explorer, [cliquez ici.](/network/explorer)
 
 Un curateur peut choisir de signaler une version spécifique d'un sugraph ou de faire migrer automatiquement son signal vers la version de production la plus récente de ce subgraph. Ces deux stratégies sont valables et comportent leurs propres avantages et inconvénients.
 
-La signalisation sur une version spécifique est particulièrement utile lorsqu'un subgraph est utilisé par plusieurs dApps. Un dApp peut avoir besoin de mettre à jour régulièrement le subgraph avec de nouvelles fonctionnalités. Une autre dApp pourrait préférer utiliser une version plus ancienne et bien testée du subgraph. Lors de la curation initiale, une taxe standard de 1% est encourue.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 La migration automatique de votre signal vers la version de production la plus récente peut s'avérer utile pour vous assurer que vous continuez à accumuler des frais de requête. Chaque fois que vous effectuez une curation, une taxe de curation de 1 % est appliquée. Vous paierez également une taxe de curation de 0,5 % à chaque migration. Les développeurs de subgraphs sont découragés de publier fréquemment de nouvelles versions - ils doivent payer une taxe de curation de 0,5 % sur toutes les parts de curation migrées automatiquement.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Remarque** : La première adresse qui signale un subgraph particulier est considérée comme le premier Curateur et devra faire un travail plus intensif en gaz que les Curateurs suivants, car le premier Curateur initialise les jetons de curation à se partager et transfère également les jetons dans le proxy de The Graph.
 
-## Withdrawing your GRT
+## Retrait de vos GRT
 
-Curators have the option to withdraw their signaled GRT at any time.
+Les Curateurs ont la possibilité de retirer leur GRT signalé à tout moment.
 
-Unlike the process of delegating, if you decide to withdraw your signaled GRT you will not have to wait for a cooldown period and will receive the entire amount (minus the 1% curation tax).
+Contrairement au processus de délégation, si vous décidez de retirer vos GRT signalés, vous n'aurez pas un délai d'attente et vous recevrez le montant total (moins la taxe de curation de 1%).
 
-Once a curator withdraws their signal, indexers may choose to keep indexing the subgraph, even if there's currently no active GRT signaled.
+Une fois qu'un Curateur retire ses signaux, les Indexeurs peuvent choisir de continuer à indexer le subgraph, même s'il n'y a actuellement aucun GRT signalé actif.
 
-However, it is recommended that curators leave their signaled GRT in place not only to receive a portion of the query fees, but also to ensure reliability and uptime of the subgraph.
+Cependant, il est recommandé que les Curateurs laissent leur GRT signalé en place non seulement pour recevoir une partie des frais de requête, mais aussi pour assurer la fiabilité et la disponibilité du subgraph.
 
 ## Risques
 
 1. Le marché des requêtes est intrinsèquement jeune chez The Graph et il y a un risque que votre %APY soit inférieur à vos attentes en raison de la dynamique naissante du marché.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Frais de curation - lorsqu'un Curateur signale des GRT sur un subgraph, il doit s'acquitter d'une taxe de curation de 1%. Cette taxe est brûlée.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Un subgraph peut échouer à cause d'un bug. Un subgraph qui échoue n'accumule pas de frais de requête. Par conséquent, vous devrez attendre que le développeur corrige le bogue et déploie une nouvelle version.
    - Si vous êtes abonné à la version la plus récente d'un subgraph, vos parts migreront automatiquement vers cette nouvelle version. Cela entraînera une taxe de curation de 0,5 %.
-   - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
+   - Si vous avez signalé sur une version spécifique d'un subgraph et qu'elle échoue, vous devrez brûler manuellement vos parts de curation. Vous pouvez alors signaler sur la nouvelle version du subgraph, encourant ainsi une taxe de curation de 1%.
 
 ## FAQs sur la Curation
 
 ### 1. Quel pourcentage des frais de requête les Curateurs perçoivent-ils?
 
-By signalling on a subgraph, you will earn a share of all the query fees that the subgraph generates. 10% of all query fees go to the Curators pro-rata to their curation shares. This 10% is subject to governance.
+En signalant sur un subgraph, vous gagnerez une part de tous les frais de requête générés par le subgraph. 10% de tous les frais de requête vont aux Curateurs au prorata de leurs parts de curation. Ces 10% sont soumis à la gouvernance.
 
 ### 2. Comment décider quels sont les subgraphs de haute qualité sur lesquels on peut émettre un signal ?
 
-Trouver des subgraphs de haute qualité est une tâche complexe, mais elle peut être abordée de plusieurs manières différentes. En tant que Curateur, vous voulez rechercher des subgraphs fiables qui génèrent un volume de requêtes. Un subgraph fiable peut être précieux s'il est complet, précis et répond aux besoins en données d'une dApp. Un subgraph mal architecturé pourrait nécessiter d'être révisé ou republié, et peut également échouer. Il est crucial pour les Curateurs d'examiner l'architecture ou le code d'un subgraph afin d'évaluer si un subgraph est précieux. En conséquence :
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Les curateurs peuvent utiliser leur compréhension d'un réseau pour essayer de prédire comment un subgraph individuel peut générer un volume de requêtes plus ou moins élevé à l'avenir
-- Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
+- Les Curateurs peuvent utiliser leur compréhension d'un réseau pour essayer de prédire comment un subgraph individuel peut générer un volume de requêtes plus élevé ou plus faible à l'avenir
+- Les Curateurs doivent également comprendre les métriques disponibles via Graph Explorer. Des métriques telles que le volume de requêtes passées et l'identité du développeur du subgraph peuvent aider à déterminer si un subgraph mérite ou non d'être signalé.
 
 ### 3. Quel est le coût de la mise à jour d'un subgraph ?
 
-Migrating your curation shares to a new subgraph version incurs a curation tax of 1%. Curators can choose to subscribe to the newest version of a subgraph. When curator shares get auto-migrated to a new version, Curators will also pay half curation tax, ie. 0.5%, because upgrading subgraphs is an on-chain action that costs gas.
+La migration de vos parts de curation vers une nouvelle version de subgraph entraîne une taxe de curation de 1%. Les Curateurs peuvent choisir de s'abonner à la version la plus récente d'un subgraph. Lorsque les parts de Curateur sont auto-migrées vers une nouvelle version, les Curateurs paieront également une demi-taxe de curation, soit 0,5%, car la mise à jour des subgraphs est une action on-chain qui coûte des frais de gaz.
 
 ### 4. À quelle fréquence puis-je mettre à jour mon subgraph ?
 
@@ -78,49 +76,13 @@ Il est conseillé de ne pas mettre à jour vos subgraphs trop fréquemment. Voir
 
 ### 5. Puis-je vendre mes parts de curateurs ?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
-
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
-
-### 6. Am I eligible for a curation grant?
-
-Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
-
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Courbe de liaison 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Prix des actions](/img/price-per-share.png)
-
-Par conséquent, le prix augmente de façon linéaire, ce qui signifie qu'il est de plus en plus cher d'acheter une action au fil du temps. Voici un exemple de ce que nous entendons par là, voir la courbe de liaison ci-dessous :
-
-![Courbe de liaison](/img/bonding-curve.png)
-
-Considérons que nous avons deux curateurs qui monnayent des actions pour un subgraph :
+Les parts de curation ne peuvent pas être "achetées" ou "vendues" comme d'autres jetons ERC20 que vous pourriez connaître. Elles ne peuvent être que mintée (créees) ou brûlées (détruites).
 
-- Le curateur A est le premier à signaler sur le subgraph. En ajoutant 120 000 GRT dans la courbe, il est capable de frapper 2000 parts.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Comme les deux curateurs détiennent la moitié du total des parts de curation, ils recevraient un montant égal de redevances de curateur.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Le curateur restant recevrait alors toutes les redevances de curateur pour ce subgraph. S'il brûlait ses pièces pour retirer la GRT, il recevrait 120 000 GRT.
-- **TLDR** : La valeur en GRT des parts de curation est déterminée par la courbe de liaison et peut-être volatile. Il est possible de subir de grosses pertes. Signer tôt signifie que vous investissez moins de GRT pour chaque action. Par extension, cela signifie que vous gagnez plus de redevances de curation par GRT que les curateurs ultérieurs pour le même subgraph.
+En tant que Curateur sur Arbitrum, vous êtes assuré de récupérer les GRT que vous avez initialement déposé (moins la taxe).
 
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
+### 6. Suis-je éligible à une subvention de curation?
 
-Dans le cas de The Graph, la [mise en œuvre par Bancor d'une formule de courbe de liaison](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) est exploitée.
+Les subventions de curation sont déterminées individuellement au cas par cas. Si vous avez besoin d'assistance avec la curation, veuillez envoyer une demande à l'adresse support@thegraph.zendesk.com.
 
 Vous ne savez toujours pas où vous en êtes ? Regardez notre guide vidéo sur la curation ci-dessous :
 

From 6161b7f90a5ff6264057663647b247c97b9fec47 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:03 -0500
Subject: [PATCH 0008/1325] New translations publishing-a-subgraph.mdx (French)

---
 .../fr/publishing/publishing-a-subgraph.mdx   | 90 +++++++++----------
 1 file changed, 45 insertions(+), 45 deletions(-)

diff --git a/website/pages/fr/publishing/publishing-a-subgraph.mdx b/website/pages/fr/publishing/publishing-a-subgraph.mdx
index 7b93e7ad52d4..c66f02c0b12f 100644
--- a/website/pages/fr/publishing/publishing-a-subgraph.mdx
+++ b/website/pages/fr/publishing/publishing-a-subgraph.mdx
@@ -2,93 +2,93 @@
 title: Publication d'un subgraph sur le réseau décentralisé
 ---
 
-Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network.
+Une fois que vous avez [déployé votre subgraph sur Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) et qu'il est prêt à passer en production, vous pouvez le publier sur le réseau décentralisé.
 
-When you publish a subgraph to the decentralized network, you make it available for:
+Lorsque vous publiez un subgraph sur le réseau décentralisé, vous le rendez disponible pour :
 
-- [Curators](/network/curating) to begin curating it.
-- [Indexers](/network/indexing) to begin indexing it.
+- [Les Curateurs](/network/curating), qui peuvent commencer à le curer.
+- [Les Indexeurs](/network/indexing), qui peuvent commencer à l’indexer.
 
 <VideoEmbed youtube="satdwdbvzAQ" />
 
-Check out the list of [supported networks](/developing/supported-networks).
+Consultez la liste des [réseaux pris en charge](/developing/supported-networks).
 
-## Publishing from Subgraph Studio
+## Publication à partir de Subgraph Studio
 
-1. Go to the [Subgraph Studio](https://thegraph.com/studio/) dashboard
-2. Click on the **Publish** button
-3. Your subgraph will now be visible in [Graph Explorer](https://thegraph.com/explorer/).
+1. Allez sur le tableau de bord de [Subgraph Studio](https://thegraph.com/studio/)
+2. Cliquez sur le bouton **Publish**
+3. Votre subgraph sera maintenant visible dans [Graph Explorer](https://thegraph.com/explorer/).
 
-All published versions of an existing subgraph can:
+Toutes les versions publiées d'un subgraph existant peuvent :
 
-- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq).
+- Être publiées sur Arbitrum One. [En savoir plus sur The Graph Network sur Arbitrum](/arbitrum/arbitrum-faq).
 
-- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published.
+- Indexer des données sur l'un des [réseaux pris en charge](/developing/supported-networks), quel que soit le réseau sur lequel le subgraph a été publié.
 
 ### Mise à jour des métadonnées d'un subgraph publié
 
-- After publishing your subgraph to the decentralized network, you can update the metadata anytime in Subgraph Studio.
-- Once you’ve saved your changes and published the updates, they will appear in Graph Explorer.
-- It's important to note that this process will not create a new version since your deployment has not changed.
+- Après avoir publié votre subgraph sur le réseau décentralisé, vous pouvez mettre à jour les métadonnées à tout moment dans Subgraph Studio.
+- Une fois que vous avez enregistré vos modifications et publié les mises à jour, elles apparaîtront dans Graph Explorer.
+- Il est important de noter que ce processus ne créera pas une nouvelle version puisque votre déploiement n'a pas changé.
 
-## Publishing from the CLI
+## Publication à partir de la CLI
 
-As of version 0.73.0, you can also publish your subgraph with the [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
+À partir de la version 0.73.0, vous pouvez également publier votre subgraph avec la [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
 
-1. Open the `graph-cli`.
-2. Use the following commands: `graph codegen && graph build` then `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.
+1. Ouvrez la `graph-cli`.
+2. Utilisez les commandes suivantes : `graph codegen && graph build` puis `graph publish`.
+3. Une fenêtre s'ouvrira, vous permettant de connecter votre portefeuille, d'ajouter des métadonnées et de déployer votre subgraph finalisé sur le réseau de votre choix.
 
 ![cli-ui](/img/cli-ui.png)
 
-### Customizing your deployment
+### Personnalisation de votre déploiement
 
-You can upload your subgraph build to a specific IPFS node and further customize your deployment with the following flags:
+Vous pouvez uploader votre build de subgraph sur un nœud IPFS spécifique et personnaliser davantage votre déploiement avec les options suivantes :
 
 ```
 USAGE
-  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url
-    <value>]
+  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url 
+     <value>]
 
 FLAGS
-  -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
-  --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
-  --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
-                               <options: arbitrum-one|arbitrum-sepolia>
-  --subgraph-id=<value>        Subgraph ID to publish to.
-  --webapp-url=<value>         [default: https://cli.thegraph.com/publish] URL of the web UI you want to use to deploy.
+  -h, --help Afficher l'aide du CLI.
+  -i, --ipfs=<value>      [default: https://api.thegraph.com/ipfs/api/v0] Téléchargez les résultats du build sur un nœud IPFS.
+  --ipfs-hash=<value>       Hash IPFS du manifeste du subgraph à déployer. 
+  --protocol-network=<option> [default: arbitrum-one] Le réseau à utiliser pour le déploiement du subgraph.
+                                <options: arbitrum-one|arbitrum-sepolia> 
+  --subgraph-id=<value>         ID du subgraph à publier.
+  --webapp-url=<value>        [default: https://cli.thegraph.com/publish] URL de l'interface web que vous souhaitez utiliser pour déployer.
 
 ```
 
-## Adding signal to your subgraph
+## Ajout de signal à votre subgraph
 
-Developers can add GRT signal to their subgraphs to incentivize Indexers to query the subgraph.
+Les développeurs peuvent ajouter des signaux GRT à leurs subgraphs pour inciter les Indexeurs à interroger le subgraph.
 
-- If a subgraph is eligible for indexing rewards, Indexers who provide a "proof of indexing" will receive a GRT reward, based on the amount of GRT signalled.
+- Si un subgraph est éligible aux récompenses d'indexation, les Indexeurs qui fournissent une "preuve d'indexation" recevront une récompense en GRT, basée sur la quantité de GRT signalée.
 
-- You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
+- Vous pouvez vérifier l'éligibilité aux récompenses d'indexation en fonction de l'utilisation des fonctionnalités du subgraph [ici](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 
-- Specific supported networks can be checked [here](/developing/supported-networks).
+- Les réseaux spécifiques pris en charge peuvent être vérifiés [ici](/developing/supported-networks).
 
-> Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers.
+> Ajouter un signal à un subgraph non éligible aux récompenses n'attirera pas d'Indexeurs supplémentaires.
 
-> If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph.
+> Si votre subgraph est éligible aux récompenses, il est recommandé de curer votre propre subgraph avec au moins 3 000 GRT afin d'attirer des indexeurs supplémentaires pour indexer votre subgraph.
 
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
+L'[Indexer Sunrise Upgrade](/sunrise/#what-is-the-upgrade-indexer) garantit l'indexation de tous les subgraphs. Cependant, le signalement de GRT sur un subgraph particulier attirera plus d'indexeurs. Cette incitation supplémentaire des Indexeurs par la curation vise à améliorer la qualité du service pour les requêtes en réduisant la latence et en améliorant la disponibilité du réseau.
 
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
+Lors du signalement, les Curateurs peuvent décider de signaler une version spécifique du subgraph ou de signaler en utilisant l'auto-migration. S'ils signalent en utilisant l'auto-migration, les parts d'un Curateur seront toujours mises à jour vers la dernière version publiée par le développeur. S'ils décident de signaler une version spécifique, les parts resteront toujours sur cette version spécifique.
 
-Indexers can find subgraphs to index based on curation signals they see in Graph Explorer.
+Les Indexeurs peuvent trouver des subgraphs à indexer en fonction des signaux de curation qu'ils voient dans Graph Explorer.
 
 ![Les subgraphs d'exploration](/img/explorer-subgraphs.png)
 
-Subgraph Studio enables you to add signal to your subgraph by adding GRT to your subgraph's curation pool in the same transaction it is published.
+Subgraph Studio vous permet d'ajouter des signaux à votre subgraph en ajoutant des GRT au pool de curation de votre subgraph dans la même transaction où il est publié.
 
 ![Pool de curation](/img/curate-own-subgraph-tx.png)
 
-Alternatively, you can add GRT signal to a published subgraph from Graph Explorer.
+Alternativement, vous pouvez ajouter des signaux GRT à un subgraph publié à partir de Graph Explorer.
 
-![Signal from Explorer](/img/signal-from-explorer.png)
+![Signal depuis Explorer](/img/signal-from-explorer.png)
 
-Learn more about [Curating](/network/curating/) on The Graph Network.
+En savoir plus sur la [curation](/network/curating/) sur The Graph Network.

From f72465eb6cde0adc9dc6db547945dad953226240 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:03 -0500
Subject: [PATCH 0009/1325] New translations delegating.mdx (French)

---
 website/pages/fr/network/delegating.mdx | 103 ++++++++++++++++--------
 1 file changed, 70 insertions(+), 33 deletions(-)

diff --git a/website/pages/fr/network/delegating.mdx b/website/pages/fr/network/delegating.mdx
index ba31be5aa31f..de7d6558d89c 100644
--- a/website/pages/fr/network/delegating.mdx
+++ b/website/pages/fr/network/delegating.mdx
@@ -2,15 +2,25 @@
 title: Délégation
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Les Délégateurs sont des participants au réseau qui délèguent (c'est-à-dire "stakent") des GRT à un ou plusieurs Indexeurs.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- Ils aident à sécuriser le réseau sans exécuter eux-mêmes un Graph Node.
+
+- Ils gagnent une partie des frais de requête et des récompenses d'un Indexeur en lui déléguant des GRT.
+
+## Comment ça marche?
+
+Le nombre de requêtes qu'un Indexeur peut traiter dépend de son propre stake, **le stake déléguée**, et le prix que l'Indexeur facture pour chaque requête. Par conséquent, plus la participation allouée à un indexeur est élevée, plus un indexeur peut traiter de requêtes potentielles.
 
 ## Guide du délégué
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Apprenez comment être un délégateur efficace dans The Graph Network.
+
+Les Délégateurs partagent les gains du protocole aux côtés de tous les indexeurs en fonction de leur participation déléguée. Par conséquent, ils doivent faire preuve de discernement pour choisir les indexeurs en fonction de plusieurs facteurs.
+
+> Veuillez noter que ce guide ne couvre pas des étapes telles que la configuration proprement dite de MetaMask. La communauté Ethereum fournit une ressource complète concernant les portefeuilles via le lien suivant ([source](https://ethereum.org/en/wallets/)).
 
-There are three sections in this guide:
+Ce guide comporte trois sections:
 
 - Les risques de la délégation de jetons dans The Graph Network
 - Comment calculer les rendements escomptés en tant que délégué
@@ -24,81 +34,108 @@ Les principaux risques liés à la fonction de délégué dans le protocole sont
 
 Les délégués ne peuvent pas être licenciés en cas de mauvais comportement, mais ils sont soumis à une taxe visant à décourager les mauvaises décisions susceptibles de nuire à l'intégrité du réseau.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+En tant que Délégateur, il est important de comprendre ce qui suit :
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- Vous serez facturé 0,5% chaque fois que vous déléguez. Cela signifie que si vous déléguez 1,000 GRT, vous brûlerez automatiquement 5 GRT.
+
+- Pour être en sécurité, vous devriez calculer votre retour potentiel lorsque vous déléguez à un Indexeur. Par exemple, vous pourriez calculer combien de jours il faudra avant d'avoir récupéré la taxe de 0,5% sur votre délégation.
 
 ### La période de découplage de la délégation
 
-Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
+Chaque fois qu'un Délégateur veut se désengager, ses jetons sont soumis à une période de d'attente de 28 jours. Cela signifie qu'ils ne peuvent pas transférer leurs jetons ou gagner des récompenses pendant 28 jours.
+
+### Pourquoi ceci est t-il important?
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+Si vous choisissez un Indexeur qui n'est pas fiable ou qui ne fait pas du bon travail, vous voudrez vous désengager. Cela signifie que vous perdrez beaucoup d'opportunités de gagner des récompenses, ce qui peut être aussi mauvais que de brûler des GRT. Par conséquent, il est recommandé de choisir judicieusement un Indexeur.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  !Délégation débondage](/img/Delegation-Unbonding.png) _Notez la commission de 0,5% dans l'interface utilisateur de la
-  délégation, ainsi que la période de débondage de 28 jours. de 28 jours
+  !Délégation débondage](/img/Delegation-Unbonding.png) _Notez la commission de 0,5% dans l'interface utilisateur de la délégation, ainsi que la période de débondage de 28 jours.
+  de 28 jours
 </div>
 
 ### Choisir un indexeur digne de confiance avec une rémunération équitable pour les délégués
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+Pour comprendre comment choisir un Indexeur fiable, vous devez comprendre les paramètres de Délégation.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Paramètres de Délégation
+
+- **Part de Récompense d'Indexation** - La portion des récompenses que l'Indexeur gardera pour lui-même.
+  - Si la part de récompense d'un indexeur est fixée à 100%, en tant que délégateur, vous recevrez 0 récompense d'indexation.
+  - Si elle est fixée à 80%, en tant que Délégateur, vous recevrez 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Le meilleur indexeur donne aux délégués 90 % des récompenses. Le
-  celui du milieu donne 20 % aux délégués. Celui du bas donne aux délégués environ 83 %.*
+   celui du milieu donne 20 % aux délégués. Celui du bas donne aux délégués environ 83 %.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Part de Frais de Requête** - C'est comme la part de récompense d'indexation, mais elle s'applique aux gains sur les frais de requête que l'Indexeur collecte.
+
+Comme vous pouvez le voir, pour choisir le bon Indexeur, vous devez prendre en compte plusieurs éléments.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- Il est fortement recommandé d'explorer [le Discord de The Graph ](https://discord.gg/graphprotocol) pour déterminer quels Indexeurs ont les meilleures réputations sociales et techniques et aussi lesquels récompensent les Délégateurs de manière cohérente.
+- Beaucoup d'Indexeurs sont très actifs sur Discord et seront heureux de répondre à vos questions.
+- Beaucoup d'entre eux indexent depuis des mois et font de leur mieux pour aider les Délégateurs à obtenir un bon retour, car cela améliore la santé et le succès du réseau.
 
-### Calcul du rendement attendu des délégués
+## Calcul du rendement attendu par les Délégateurs
 
-A Delegator must consider a lot of factors when determining the return. These include:
+Un Délégateur doit considérer les facteurs suivants pour déterminer un rendement :
 
-- Un délégué technique peut également examiner la capacité de l'indexeur à utiliser les jetons délégués dont il dispose. Si un indexeur n'alloue pas tous les jetons disponibles, il ne réalise pas le profit maximum qu'il pourrait réaliser pour lui-même ou pour ses délégués.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Considérer la capacité d'un Indexeur à utiliser les jetons délégués dont il dispose.
+  - Si un Indexeur n'alloue pas tous les jetons disponibles, ils ne gagnent pas le maximum de profit qu'ils pourraient obtenir pour lui même ou ses Déléguateurs.
+- Soyez attentif aux premiers jours de la délégation.
+  - Un Indexeur peut choisir de fermer une allocation et de collecter des récompenses à tout moment entre 1 et 28 jours. Il est possible qu'un indexeur ait encore beaucoup de récompenses à collecter, de sorte que le total de ses récompenses est faible.
 
 ### Considérant la réduction des frais d'interrogation et la réduction des frais d'indexation
 
-Comme décrit dans les sections précédentes, vous devez choisir un indexeur qui est transparent et honnête dans la fixation de sa réduction des frais de requête et d'indexation. Un délégué doit également examiner le temps de refroidissement des paramètres pour voir de combien de temps il dispose. Après cela, il est assez simple de calculer le montant des récompenses que les délégués reçoivent. La formule est la suivante :
+Vous devriez choisir un Indexeur qui est transparent et honnête dans la fixation de ses frais de requête et de ses réductions de frais d'indexation. Vous devez également examiner le Paramètre délai de récupérations pour voir de combien de temps vous disposez. Une fois cela fait, il est facile de calculer le montant des récompenses que vous obtenez.
+
+La formule est :
 
 ![Délégation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Compte tenu du pool de délégation de l'indexeur
 
-Une autre chose qu'un délégant doit prendre en compte est la proportion du pool de délégation qu'il possède. Toutes les récompenses de délégation sont partagées équitablement, avec un simple rééquilibrage du pool déterminé par le montant que le délégant a déposé dans le pool. Cela donne au délégant une part du pool :
+Les Déléguateurs doivent considérer la proportion du Pool de Délégation qu'ils possèdent.
 
-![Formule de partage](/img/Share-Forumla.png)
+Toutes les récompenses de délégation sont partagées de manière égale, avec un rééquilibrage du pool basé sur le montant que le Déléguateur a déposé dans le pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+Cela donne au Déléguateur une part du pool :
+
+![Formule de partage](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> La formule ci-dessus montre qu'il est possible pour un Indexeur offrant seulement 20% aux Déléguateurs de fournir une meilleure récompense qu'un Indexeur donnant 90%. Il suffit de faire les calculs pour déterminer la meilleure récompense.
 
 ### Compte tenu de la capacité de délégation
 
-Une autre chose à considérer est la capacité de délégation. Actuellement, le ratio de délégation est fixé à 16. Cela signifie que si un indexeur a mis en jeu 1 000 000 GRT, sa capacité de délégation est de 16 000 000 GRT de jetons délégués qu'il peut utiliser dans le protocole. Tout jeton délégué dépassant ce montant diluera toutes les récompenses du délégué.
+Enfin, considérez la capacité de délégation. Actuellement, le Ratio de Délégation est fixé à 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Pourquoi est-ce important?
 
-Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
+Cela signifie que si un Indexeur a staké 1 000 000 GRT, sa Capacité de Délégation est de 16 000 000 GRT de tokens délégués qu'ils peuvent utiliser dans le protocole. Tous les tokens délégués au-delà de ce montant dilueront toutes les récompenses des Déléguateurs.
+
+Imaginez un Indexeur avec 100 000 000 GRT délégués à lui, mais sa capacité est seulement de 16 000 000 GRT. Cela signifie effectivement que 84 000 000 de GRT ne sont pas utilisés pour gagner des tokens. Ainsi, les Déléguateurs et les Indexeurs gagnent moins de récompenses qu'ils pourraient.
+
+Par conséquent, un Déléguateur doit toujours considérer la Capacité de Délégation d'un Indexeur et en tenir compte dans leur prise de décision.
 
 ## FAQ et bugs pour les délégants
 
 ### Bug MetaMask « Transaction en attente »
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. Lorsque j'essaie de déléguer ma transaction dans MetaMask, elle apparaît comme « En attente » ( "Pending") ou « En file d'attente » ( "Queued") plus longtemps que prévu. Que devrais-je faire?
+
+Parfois, les tentatives de déléguer aux Indexeurs via MetaMask peuvent échouer et entraîner des périodes prolongées de tentatives de transaction "Pending" ou "Queued".
+
+#### Exemple
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Imaginons que vous tentiez de déléguer avec des frais de gaz insuffisants par rapport aux prix actuels.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- Cette action peut entraîner l'affichage de la tentative de transaction comme "En attente" dans votre portefeuille MetaMask pendant plus de 15 minutes. Dans ce cas, vous pouvez essayer des transactions ultérieures, mais elles ne seront traitées que lorsque la transaction initiale sera minée, car les transactions pour une adresse doivent être traitées dans l'ordre.
+- Dans de tels cas, ces transactions peuvent être annulées dans MetaMask, mais les tentatives de transactions accumuleront des frais de gas sans aucune garantie que les tentatives ultérieures seront réussies.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+Une solution simple à ce problème consiste à redémarrer le navigateur (par exemple, en utilisant "abort:restart" dans la barre d'adresse), ce qui annulera toutes les tentatives précédentes sans que le gaz ne soit soustrait du portefeuille. Plusieurs utilisateurs ayant rencontré ce problème ont signalé des transactions réussies après avoir redémarré leur navigateur et tenté de déléguer.
 
-## Guide vidéo pour l'interface utilisateur du réseau
+## Guide Vidéo
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+Ce guide vidéo passe en revue cette page tout en interagissant avec l'interface utilisateur.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From bbeb5a05fd234ee37faca6e9b62ef47cced0ccc3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:05 -0500
Subject: [PATCH 0010/1325] New translations indexing.mdx (French)

---
 website/pages/fr/network/indexing.mdx | 108 +++++++++++++-------------
 1 file changed, 54 insertions(+), 54 deletions(-)

diff --git a/website/pages/fr/network/indexing.mdx b/website/pages/fr/network/indexing.mdx
index 6fd8178366cd..55955d4a56b9 100644
--- a/website/pages/fr/network/indexing.mdx
+++ b/website/pages/fr/network/indexing.mdx
@@ -26,7 +26,7 @@ La mise minimale pour un indexeur est actuellement fixée à 100 000 GRT.
 
 Les récompenses de l'indexation proviennent de l'inflation du protocole qui est fixée à 3 % par an. Ils sont répartis entre les subraphs en fonction de la proportion de tous les signaux de curation sur chacun, puis distribués proportionnellement aux indexeurs en fonction de leur participation allouée sur ce subgraph. **Une allocation doit être clôturée avec une preuve d'indexation (POI) valide et répondant aux normes fixées par la charte d'arbitrage afin d'être éligible aux récompenses.**
 
-Numerous tools have been created by the community for calculating rewards; you'll find a collection of them organized in the [Community Guides collection](https://www.notion.so/Community-Guides-abbb10f4dba040d5ba81648ca093e70c). You can also find an up to date list of tools in the #Delegators and #Indexers channels on the [Discord server](https://discord.gg/graphprotocol). Here we link a [recommended allocation optimiser](https://github.com/graphprotocol/allocation-optimizer) integrated with the indexer software stack.
+De nombreux outils ont été créés par la communauté pour calculer les récompenses ; vous trouverez une collection de ces outils organisés dans la [collection de guides communautaires](https://www.notion.so/Community-Guides-abbb10f4dba040d5ba81648ca093e70c). Vous pouvez également trouver une liste à jour des outils dans les canaux #Delegators et #Indexers sur le [serveur Discord](https://discord.gg/graphprotocol). Nous recommandons [un optimiseur d'allocation](https://github.com/graphprotocol/allocation-optimizer) intégré à la pile logicielle de l'Indexeur.
 
 ### Qu'est-ce qu'une preuve d'indexation (POI) ?
 
@@ -38,11 +38,11 @@ Les allocations accumulent continuellement des récompenses pendant qu'elles son
 
 ### Les récompenses d’indexation en attente peuvent-elles être surveillées ?
 
-The RewardsManager contract has a read-only [getRewards](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/rewards/RewardsManager.sol#L316) function that can be used to check the pending rewards for a specific allocation.
+Le contrat RewardsManager a une fonction [getRewards](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/rewards/RewardsManager.sol#L316) en lecture seule qui peut être utilisée pour vérifier les récompenses en attente pour une allocation spécifique.
 
 De nombreux tableaux de bord créés par la communauté incluent des valeurs de récompenses en attente et ils peuvent être facilement vérifiés manuellement en suivant ces étapes :
 
-1. Interrogez le [subgraph du mainnet](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) pour obtenir les ID de toutes les allocations actives :
+1. Interrogez le [réseau principal de subgraphs](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) pour obtenir les identifiants de toutes les allocations actives :
 
 ```graphql
 query indexerAllocations {
@@ -63,7 +63,7 @@ Utilisez Etherscan pour appeler `getRewards()` :
 - Naviguer vers [Interface d'étherscan pour le contrat de récompenses](https://etherscan.io/address/0x9Ac758AB77733b4150A901ebd659cbF8cB93ED66#readProxyContract)
 
 * Appeller `getRewards()`:
-  - Expand the **9. getRewards** dropdown.
+  - Déroulez le menu **9. getRewards**.
   - Saisissez le **allocationID** dans l'entrée.
   - Cliquez sur le bouton **Requête**.
 
@@ -113,11 +113,11 @@ Les indexeurs peuvent se différencier en appliquant des techniques avancées po
 - **Large** : Prêt à indexer tous les subgraphs actuellement utilisés et à répondre aux demandes pour le trafic associé.
 
 | Installation | Postgres<br />(CPUs) | Postgres<br />(mémoire en Gbs) | Postgres<br />(disque en TB) | VMs<br />(CPUs) | VMs<br />(mémoire en Gbs) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Petit | 4 | 8 | 1 | 4 | 16 |
-| Standard | 8 | 30 | 11 | 12 | 48 |
-| Moyen | 16 | 64 | 2 | 32 | 64 |
-| Large | 72 | 468 | 3.5 | 48 |  |
+| ------------ |:--------------------------:|:------------------------------------:|:----------------------------------:|:---------------------:|:-------------------------------:|
+| Petit        |             4              |                  8                   |                 1                  |           4           |               16                |
+| Standard     |             8              |                  30                  |                 11                 |          12           |               48                |
+| Moyen        |             16             |                  64                  |                 2                  |          32           |               64                |
+| Large        |             72             |                 468                  |                3.5                 |          48           |                                 |
 
 ### Quelles sont les précautions de sécurité de base qu’un indexeur doit prendre ?
 
@@ -149,20 +149,20 @@ Remarque : Pour prendre en charge la mise à l'échelle agile, il est recommand
 
 #### Nœud de The Graph
 
-| Port | Objectif | Routes | Argument CLI | Variable d'environnement |
-| --- | --- | --- | --- | --- |
-| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(pour gérer les déploiements) | / | --admin-port | - |
-| 8030 | API de statut d'indexation des subgraphs | /graphq | --index-node-port | - |
-| 8040 | Métriques Prometheus | /metrics | --metrics-port | - |
+| Port | Objectif                                                         | Routes                                               | Argument CLI      | Variable d'environnement |
+| ---- | ---------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------------ |
+| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                        |
+| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                        |
+| 8020 | JSON-RPC<br />(pour gérer les déploiements)                | /                                                    | --admin-port      | -                        |
+| 8030 | API de statut d'indexation des subgraphs                         | /graphq                                              | --index-node-port | -                        |
+| 8040 | Métriques Prometheus                                             | /metrics                                             | --metrics-port    | -                        |
 
 #### Service d'indexation
 
-| Port | Objectif | Routes | Argument CLI | Variable d'environnement |
-| --- | --- | --- | --- | --- |
-| 7600 | Serveur HTTP GraphQL<br />(pour les requêtes payantes de subgraphs) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Métriques Prometheus | /metrics | --metrics-port | - |
+| Port | Objectif                                                                  | Routes                                                                  | Argument CLI   | Variable d'environnement |
+| ---- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ------------------------ |
+| 7600 | Serveur HTTP GraphQL<br />(pour les requêtes payantes de subgraphs) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT`   |
+| 7300 | Métriques Prometheus                                                      | /metrics                                                                | --metrics-port | -                        |
 
 #### Agent indexeur
 
@@ -182,9 +182,9 @@ Remarque : Pour prendre en charge la mise à l'échelle agile, il est recommand
 
 #### Créer un projet Google Cloud
 
-- Clone or navigate to the [Indexer repository](https://github.com/graphprotocol/indexer).
+- Cloner ou naviguez vers le [répertoire de l'Indexeur](https://github.com/graphprotocol/indexer).
 
-- Navigate to the `./terraform` directory, this is where all commands should be executed.
+- Accédez au répertoire `./terraform`, c'est là que toutes les commandes doivent être exécutées.
 
 ```sh
 cd terraform
@@ -297,7 +297,7 @@ Déployez toutes les ressources avec `kubectl apply -k $dir`.
 
 ### Nœud de The Graph
 
-[Graph Node](https://github.com/graphprotocol/graph-node) is an open source Rust implementation that event sources the Ethereum blockchain to deterministically update a data store that can be queried via the GraphQL endpoint. Developers use subgraphs to define their schema, and a set of mappings for transforming the data sourced from the blockchain and the Graph Node handles syncing the entire chain, monitoring for new blocks, and serving it via a GraphQL endpoint.
+[Graph Node](https://github.com/graphprotocol/graph-node) est une implémentation open source en Rust qui source les événements de la blockchain Ethereum pour mettre à jour de manière déterministe un magasin de données pouvant être interrogé via l'endpoint GraphQL. Les développeurs utilisent des subgraphs pour définir leur schéma et un ensemble de mappages pour transformer les données provenant de la blockchain et le Graph Node gère la synchronisation de toute la chaîne, surveille les nouveaux blocs et les sert via un endpoint GraphQL.
 
 #### Commencer à partir des sources
 
@@ -465,26 +465,26 @@ Consultez la section [Configurer l'infrastructure du serveur à l'aide de Terraf
 
 ```sh
 graph-indexer-agent start \
-  --ethereum <MAINNET_ETH_ENDPOINT> \
+  --ethereum <ENDPOINT_RESEAU_PRINCIPAL_ETHEREUM> \
   --ethereum-network mainnet \
   --mnemonic <MNEMONIC> \
-  --indexer-address <INDEXER_ADDRESS> \
+  --indexer-address <ADRESSE_DE_LINDEXEUR> \
   --graph-node-query-endpoint http://localhost:8000/ \
   --graph-node-status-endpoint http://localhost:8030/graphql \
   --graph-node-admin-endpoint http://localhost:8020/ \
   --public-indexer-url http://localhost:7600/ \
-  --indexer-geo-coordinates <YOUR_COORDINATES> \
+  --indexer-geo-coordinates <VOS COORDONNEES> \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
   --postgres-host localhost \
   --postgres-port 5432 \
-  --postgres-username <DB_USERNAME> \
-  --postgres-password <DB_PASSWORD> \
+  --postgres-username <NOM_D_UTILISATEUR_DE_LA_BD> \
+  --postgres-password <MOT_DE_PASSE_DE_LA_BD> \
   --postgres-database indexer \
   --allocation-management auto \
   | pino-pretty
@@ -496,23 +496,23 @@ graph-indexer-agent start \
 SERVER_HOST=localhost \
 SERVER_PORT=5432 \
 SERVER_DB_NAME=is_staging \
-SERVER_DB_USER=<DB_USERNAME> \
-SERVER_DB_PASSWORD=<DB_PASSWORD> \
+SERVER_DB_USER=<NOM_D_UTILISATEUR_DE_LA_BD> \
+SERVER_DB_PASSWORD=<MOT_DE_PASSE_DE_LA_BD> \
 graph-indexer-service start \
-  --ethereum <MAINNET_ETH_ENDPOINT> \
+  --ethereum <ENDPOINT_RESEAU_PRINCIPAL_ETHEREUM> \
   --ethereum-network mainnet \
   --mnemonic <MNEMONIC> \
-  --indexer-address <INDEXER_ADDRESS> \
+  --indexer-address <ADRESSE_DE_LINDEXEUR> \
   --port 7600 \
   --metrics-port 7300 \
   --graph-node-query-endpoint http://localhost:8000/ \
   --graph-node-status-endpoint http://localhost:8030/graphql \
   --postgres-host localhost \
   --postgres-port 5432 \
-  --postgres-username <DB_USERNAME> \
-  --postgres-password <DB_PASSWORD> \
+  --postgres-username <NOM_D_UTILISATEUR_DE_LA_BD> \
+  --postgres-password <MOT_DE_PASSE_DE_LA_BD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ La **Indexer CLI** se connecte à l'agent Indexer, généralement via la redirec
 
 - `règles de l'indexeur graphique peut-être [options] <deployment-id>` — Définissez le `decisionBasis` pour un déploiement sur `rules`, afin que l'agent indexeur utilisez des règles d'indexation pour décider d'indexer ou non ce déploiement.
 
-- `graph indexer actions get [options] <action-id>` - Récupère une ou plusieurs actions en utilisant `all` ou laissez `action-id` vide pour obtenir toutes les actions. Un argument supplémentaire `--status` peut être utilisé pour imprimer toutes les actions d'un certain statut.
+- `graph indexer actions get [options] <action-id>` - Récupérez une ou plusieurs actions en utilisant `all` ou laissez `action-id` vide pour obtenir toutes les actions. Un argument supplémentaire `--status` peut être utilisé pour afficher toutes les actions d'un certain statut.
 
 - `file d'attente d'action de l'indexeur de graphs alloue <deployment-id> <allocation-amount>` - Action d'allocation de file d'attente
 
@@ -751,9 +751,9 @@ indexer cost set model my_model.agora
 
 ### Enjeu dans le protocole
 
-The first steps to participating in the network as an Indexer are to approve the protocol, stake funds, and (optionally) set up an operator address for day-to-day protocol interactions.
+Les premières étapes pour participer au réseau en tant qu'Indexeur sont d'approuver le protocole, de staker des fonds et (facultativement) de configurer une adresse opérateur pour les interactions quotidiennes avec le protocole.
 
-> Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools).
+> Note : Pour les besoins de ces instructions, Remix sera utilisé pour l'interaction avec le contrat, mais n'hésitez pas à utiliser l'outil de votre choix ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), et [MyCrypto](https://www.mycrypto.com/account) sont quelques autres outils connus).
 
 Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l'indexeur](/network/indexing#indexer-components) peuvent être démarrés et commencer leurs interactions avec le réseau.
 
@@ -763,7 +763,7 @@ Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l
 
 2. Dans `File Explorer`, créez un fichier nommé **GraphToken.abi** avec l'[ABI du jeton](https://raw.githubusercontent.com/graphprotocol/contracts/mainnet-deploy-build/build/abis/GraphToken.json).
 
-3. With `GraphToken.abi` selected and open in the editor, switch to the `Deploy and run transactions` section in the Remix interface.
+3. Avec `GraphToken.abi` sélectionné et ouvert dans l'éditeur, passez à la section `Déployer et exécuter des transactions` dans l’interface de Remix.
 
 4. Sous Environnement, sélectionnez `Injected Web3` et sous `Compte` sélectionnez votre adresse d'indexeur.
 
@@ -777,7 +777,7 @@ Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l
 
 2. Dans l'`Explorateur de fichiers`, créez un fichier nommé **Staking.abi** avec l'ABI de staking.
 
-3. With `Staking.abi` selected and open in the editor, switch to the `Deploy and run transactions` section in the Remix interface.
+3. Avec `Staking.abi` sélectionné et ouvert dans l'éditeur, passez à la section `Déployer et exécuter des transactions` dans l’interface de Remix.
 
 4. Sous Environnement, sélectionnez `Injected Web3` et sous `Compte` sélectionnez votre adresse d'indexeur.
 
@@ -793,28 +793,28 @@ Une fois qu'un indexeur a staké des GRT dans le protocole, les [composants de l
 setDelegationParameters(950000, 600000, 500)
 ```
 
-### Setting delegation parameters
+### Définition des paramètres de délégation
 
-The `setDelegationParameters()` function in the [staking contract](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol) is essential for Indexers, allowing them to set parameters that define their interactions with Delegators, influencing their reward sharing and delegation capacity.
+La fonction `setDelegationParameters()` dans le [contrat de staking](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol) est essentielle pour les Indexeurs, leur permettant de définir des paramètres qui définissent leurs interactions avec les Délégateurs, influençant leur partage des récompenses et leur capacité de délégation.
 
-### How to set delegation parameters
+### Comment définir les paramètres de délégation
 
-To set the delegation parameters using Graph Explorer interface, follow these steps:
+Pour définir les paramètres de délégation à l'aide de l'interface Graph Explorer, suivez ces étapes :
 
-1. Navigate to [Graph Explorer](https://thegraph.com/explorer/).
-2. Connect your wallet. Choose multisig (such as Gnosis Safe) and then select mainnet. Note: You will need to repeat this process for Arbitrum One.
-3. Connect the wallet you have as a signer.
-4. Navigate to the 'Settings' section and select 'Delegation Parameters'. These parameters should be configured to achieve an effective cut within the desired range. Upon entering values in the provided input fields, the interface will automatically calculate the effective cut. Adjust these values as necessary to attain the desired effective cut percentage.
-5. Submit the transaction to the network.
+1. Naviguez vers [Graph Explorer](https://thegraph.com/explorer/).
+2. Connectez votre portefeuille. Choisissez multisig (comme Gnosis Safe) puis sélectionnez mainnet. Note : Vous devrez répéter ce processus pour Arbitrum One.
+3. Connectez le portefeuille que vous avez en tant que signataire.
+4. Accédez à la section "Settings" puis sélectionnez "Delegation Parameters". Ces paramètres doivent être configurés afin d’obtenir un taux effectif dans la fourchette souhaitée. Une fois les valeurs saisies dans les champs prévus, l’interface calcule automatiquement ce taux effectif. Ajustez les valeurs selon vos besoins pour atteindre le pourcentage effectif désiré.
+5. Soumettez la transaction au réseau.
 
-> Note: This transaction will need to be confirmed by the multisig wallet signers.
+> Note : Cette transaction devra être confirmée par les signataires du portefeuille multisig.
 
 ### La durée de vie d'une allocation
 
-Après avoir été créée par un indexeur, une allocation saine passe par quatre états.
+After being created by an Indexer a healthy allocation goes through two states.
 
-- **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
+- **Active** - Une fois qu'une allocation est créée on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) elle est considérée comme **active**. Une partie du staking de l'Indexeur et/ou du staking délégué est allouée à un déploiement de subgraph, ce qui leur permet de réclamer des récompenses d'indexation et de servir des requêtes pour ce déploiement de subgraph. L'agent Indexeur gère la création des allocations en fonction des règles de l'Indexeur.
 
-- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)).
+- **Closed** - Un Indexeur est libre de fermer une allocation une fois qu'une époque est passée ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) ou son agent Indexeur fermera automatiquement l'allocation après le **maxAllocationEpochs** (actuellement 28 jours). Lorsqu'une allocation est fermée avec une preuve d'indexation (POI) valide, leurs récompenses d'indexation sont distribuées à l'Indexeur et à ses Délégateurs ([en savoir plus](/network/indexing/#how-are-indexing-rewards-distributed)).
 
 Il est recommandé aux indexeurs d'utiliser la fonctionnalité de synchronisation hors chaîne pour synchroniser les déploiements de subgraphs avec Chainhead avant de créer l'allocation en chaîne. Cette fonctionnalité est particulièrement utile pour les sous-graphes dont la synchronisation peut prendre plus de 28 époques ou qui risquent d'échouer de manière indéterministe.

From ce4a8d4c50fefe0fb6a3c469f6554730e1dccdf4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:06 -0500
Subject: [PATCH 0011/1325] New translations indexing.mdx (Turkish)

---
 website/pages/tr/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/tr/network/indexing.mdx b/website/pages/tr/network/indexing.mdx
index 1c6318d64907..a9c25ebeee43 100644
--- a/website/pages/tr/network/indexing.mdx
+++ b/website/pages/tr/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Many of the community-made dashboards include pending rewards values and they can be easily checked manually by following these steps:
 
-1. Query the [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) to get the IDs for all active allocations:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Indexers may differentiate themselves by applying advanced techniques for making
 - **Orta** - 100 subgraph ve saniyede 200-500 isteği destekleyen Üretim İndeksleyici.
 - **Yüksek** - Şu anda kullanılan tüm subgraphları indekslemek ve ilgili trafik için istekleri sunmak için hazırlanmıştır.
 
-| Kurulum | Postgres<br />(CPU'lar) | Postgres<br />(GB cinsinden bellek) | Postgres<br />(TB cinsinden disk) | VM'ler<br />(CPU'lar) | VM'ler<br />(GB cinsinden bellek) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Düşük | 4 | 8 | 1 | 4 | 16 |
-| Standart | 8 | 30 | 1 | 12 | 48 |
-| Orta | 16 | 64 | 2 | 32 | 64 |
-| Yüksek | 72 | 468 | 3.5 | 48 | 184 |
+| Kurulum  | Postgres<br />(CPU'lar) | Postgres<br />(GB cinsinden bellek) | Postgres<br />(TB cinsinden disk) | VM'ler<br />(CPU'lar) | VM'ler<br />(GB cinsinden bellek) |
+| -------- |:-----------------------------:|:-----------------------------------------:|:---------------------------------------:|:---------------------------:|:---------------------------------------:|
+| Düşük    |               4               |                     8                     |                    1                    |              4              |                   16                    |
+| Standart |               8               |                    30                     |                    1                    |             12              |                   48                    |
+| Orta     |              16               |                    64                     |                    2                    |             32              |                   64                    |
+| Yüksek   |              72               |                    468                    |                   3.5                   |             48              |                   184                   |
 
 ### Bir İndeksleyicinin alması gereken bazı temel güvenlik önlemleri nelerdir?
 
@@ -149,20 +149,20 @@ Not: Çevik ölçeklendirmeyi desteklemek için, sorgulama ve indeksleme endişe
 
 #### Graph Node
 
-| Port | Amaç | Rotalar | CLI Argümanı | Ortam Değişkeni |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />( subgraph abonelikleri için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(dağıtımları yönetmek için) | / | --admin-port | - |
-| 8030 | Subgraph indeksleme durum API'si | /graphql | --index-node-port | - |
-| 8040 | Prometheus metrikleri | /metrics | --metrics-port | - |
+| Port | Amaç                                                        | Rotalar                                              | CLI Argümanı      | Ortam Değişkeni |
+| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
+| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
+| 8001 | GraphQL WS<br />( subgraph abonelikleri için)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
+| 8020 | JSON-RPC<br />(dağıtımları yönetmek için)             | /                                                    | --admin-port      | -               |
+| 8030 | Subgraph indeksleme durum API'si                            | /graphql                                             | --index-node-port | -               |
+| 8040 | Prometheus metrikleri                                       | /metrics                                             | --metrics-port    | -               |
 
 #### İndeksleyici Hizmeti
 
-| Port | Amaç | Rotalar | CLI Argümanı | Ortam Değişkeni |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP sunucusu<br />(ücretli subgraph sorguları için) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrikleri | /metrics | --metrics-port | - |
+| Port | Amaç                                                               | Rotalar                                                                 | CLI Argümanı   | Ortam Değişkeni        |
+| ---- | ------------------------------------------------------------------ | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP sunucusu<br />(ücretli subgraph sorguları için) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrikleri                                              | /metrics                                                                | --metrics-port | -                      |
 
 #### İndeksleyici Aracı
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ graph indexer status
 
 - `graph indexer rules maybe [options] <deployment-id>` — Bir dağıtım için `decisionBasis` öğesini `rules` olarak ayarlayın, böylece İndeksleyici aracısı bu dağıtımı indeksleyip indekslemeyeceğine karar vermek için indeksleme kurallarını kullanacaktır.
 
-- `graph indexer actions get [options] <action-id>` - `all` kullanarak bir veya daha fazla eylemi getirin veya tüm eylemleri almak için `action-id`'yi boş bırakın. Belirli bir durumdaki tüm eylemleri yazdırmak için `--status` ek argümanı kullanılabilir.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Kuyruk tahsis eylemi
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### Bir tahsisin ömrü
 
-Bir İndeksleyici tarafından oluşturulmasının ardından sağlıklı bir tahsis dört aşamadan geçer.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From a0d45ec39202b4ed0a2ebda6311b0da91c0b3ea2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:07 -0500
Subject: [PATCH 0012/1325] New translations unit-testing-framework.mdx
 (Russian)

---
 .../ru/developing/unit-testing-framework.mdx  | 160 ++++++++++--------
 1 file changed, 87 insertions(+), 73 deletions(-)

diff --git a/website/pages/ru/developing/unit-testing-framework.mdx b/website/pages/ru/developing/unit-testing-framework.mdx
index 82e48c024709..698e25117b45 100644
--- a/website/pages/ru/developing/unit-testing-framework.mdx
+++ b/website/pages/ru/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Фреймворк модульного тестирования
 ---
 
-Matchstick - это фреймворк модульного тестирования, разработанный компанией [LimeChain](https://limechain.tech/), который позволяет разработчикам субграфов тестировать логику мэппинга в изолированной среде и уверенно развертывать свои субграфы!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Начало работы
 
-### Установка зависимостей
+### Install Dependencies
 
-Чтобы использовать вспомогательные методы тестирования и запускать тесты, Вам необходимо будет установить следующие зависимости:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` зависит от PostgreSQL, поэтому, если у Вас его еще нет, Вам нужно будет его установить. Мы настоятельно рекомендуем использовать приведенные ниже команды, так как добавление их любым другим способом может привести к непредвиденным ошибкам!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
 
-#### MacOS
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-Команда установки Postgres:
+#### Using MacOS
+
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ brew install postgresql
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Команда установки Postgres (зависит от вашего дистрибутива):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 Вы можете использовать Matchstick в WSL как с помощью подхода Docker, так и с помощью бинарного подхода. Поскольку WSL может быть немного сложной задачей, вот несколько советов на случай, если Вы столкнетесь с такими проблемами, как
 
@@ -76,7 +85,7 @@ sudo apt-get install libpq-dev
 }
 ```
 
-### Применение
+### Using Matchstick
 
 Чтобы использовать **Matchstick** в своём проекте subgraph, просто откройте терминал, перейдите в корневую папку своего проекта и запустите `graph test [options] <datasource>` - он загрузит последний двоичный файл **Matchstick** и запустит указанный тест или все тесты в тестовой папке (или все существующие тесты, если флаг источника данных не указан).
 
@@ -116,7 +125,7 @@ graph test path/to/file.test.ts
 
 Из `graph-cli 0.25.2` команда `graph test` поддерживает запуск `matchstick` в контейнере docker с флагом `-d`. Реализация docker использует [bind mount](https://docs.docker.com/storage/bind-mounts /), чтобы не приходилось перестраивать образ docker каждый раз, когда выполняется команда `graph test -d`. В качестве альтернативы Вы можете следовать инструкциям из репозитория [matchstick](https://github.com/LimeChain/matchstick#docker-) для запуска docker вручную.
 
-❗ `graph test -d` forces `docker run` to run with flag `-t`. This must be removed to run inside non-interactive environments (like GitHub CI).
+❗ Команда `graph test -d` принудительно запускает `docker run` с флагом `-t`. Этот флаг необходимо удалить для запуска в неинтерактивных средах (таких, например, как GitHub CI).
 
 ❗ Если Вы ранее запускали `graph test`, Вы можете столкнуться со следующей ошибкой во время сборки docker:
 
@@ -144,9 +153,9 @@ manifestPath: path/to/subgraph.yaml
 
 Также Вы можете посмотреть серию видеороликов [>"Как использовать Matchstick для написания модульных тестов для Ваших субграфов"](https://www.youtube.com/playlist?list=PLTqyKgxaGF3SNakGQwczpSGVjS_xvOv3h)
 
-## Tests structure
+## Структура тестов
 
-_**IMPORTANT: The test structure described below depens on `matchstick-as` version >=0.5.0**_
+_**ВАЖНО: Описанная ниже тестовая структура зависит от версии `matchstick-as` >=0.5.0**_
 
 ### describe()
 
@@ -373,7 +382,7 @@ describe("handleNewGravatars, () => {
 
 ```typescript
 import { describe, test, beforeEach } from 'matchstick-as/assembly/index'
-import { handleUpdatedGravatar, handleNewGravatar } from '../../src/gravity'
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
 
 describe('handleUpdatedGravatars', () => {
   beforeEach(() => {
@@ -524,7 +533,7 @@ assertNotNull<T>(value: T)
 entityCount(entityType: string, expectedCount: i32)
 ```
 
-As of version 0.6.0, asserts support custom error messages as well
+Начиная с версии 0.6.0, утверждения также поддерживают настраиваемые сообщения об ошибках
 
 ```typescript
 assert.fieldEquals('Gravatar', '0x123', 'id', '0x123', 'Id should be 0x123')
@@ -877,7 +886,7 @@ assert.equals(ethereum.Value.fromString("hello"); ethereum.Value.fromString("hel
 assert.notInStore('Gravatar', '23')
 ```
 
-### Printing the whole store, or single entities from it (for debug purposes)
+### Вывод всего хранилища или отдельных его объектов (в целях отладки)
 
 С помощью этой вспомогательной функции можно вывести всё хранилище на консоль:
 
@@ -887,7 +896,7 @@ import { logStore } from 'matchstick-as/assembly/store'
 logStore()
 ```
 
-As of version 0.6.0, `logStore` no longer prints derived fields, instead users can use the new `logEntity` function. Of course `logEntity` can be used to print any entity, not just ones that have derived fields. `logEntity` takes the entity type, entity id and a `showRelated` flag to indicate if users want to print the related derived entities.
+Начиная с версии 0.6.0, `logStore` больше не выводит производные поля. Вместо этого пользователи могут использовать новую функцию `logEntity`. Конечно, `logEntity` можно использовать для вывода любого объекта, а не только тех, у которых есть производные поля. `logEntity` принимает тип объекта, идентификатор объекта и флаг `showRelated`, указывающий, хочет ли пользователь вывести связанные производные объекты.
 
 ```
 import { logEntity } from 'matchstick-as/assembly/store'
@@ -949,16 +958,16 @@ test('Blow everything up', () => {
 
 ### Тестирование производных полей
 
-Testing derived fields is a feature which allows users to set a field on a certain entity and have another entity be updated automatically if it derives one of its fields from the first entity.
+Тестирование производных полей — это функция, которая позволяет пользователям устанавливать поле для определенного объекта и автоматически обновлять другой объект, если он извлекает одно из своих полей из первого объекта.
 
-Before version `0.6.0` it was possible to get the derived entities by accessing them as entity fields/properties, like so:
+До версии `0.6.0` можно было получить производные объекты, обратившись к ним как к полям/свойствам объектов, например:
 
 ```typescript
 let entity = ExampleEntity.load('id')
 let derivedEntity = entity.derived_entity
 ```
 
-As of version `0.6.0`, this is done by using the `loadRelated` function of graph-node, the derived entities can be accessed the same way as in the handlers.
+Начиная с версии `0.6.0` это делается с помощью функции `loadRelated` graph-node, к производным объектам можно получить доступ так же, как и в обработчиках.
 
 ```typescript
 test('Derived fields example test', () => {
@@ -1000,9 +1009,9 @@ test('Derived fields example test', () => {
 })
 ```
 
-### Testing `loadInBlock`
+### Тестирование `loadInBlock`
 
-As of version `0.6.0`, users can test `loadInBlock` by using the `mockInBlockStore`, it allows mocking entities in the block cache.
+Начиная с версии `0.6.0`, пользователи могут тестировать `loadInBlock` с помощью `mockInBlockStore`, он позволяет имитировать объекты в кеше блоков.
 
 ```typescript
 import { afterAll, beforeAll, describe, mockInBlockStore, test } from 'matchstick-as'
@@ -1086,46 +1095,46 @@ test('Data source simple mocking example', () => {
 
 Обратите внимание, что функция DataSource Mock.resetValues() вызывается в конце. Это происходит потому, что значения запоминаются при их изменении, и их необходимо сбросить, если Вы хотите вернуться к значениям по умолчанию.
 
-### Testing dynamic data source creation
+### Тестирование создания источника динамических данных
 
-As of version `0.6.0`, it is possible to test if a new data source has been created from a template. This feature supports both ethereum/contract and file/ipfs templates. There are four functions for this:
+Начиная с версии `0.6.0`, можно проверить, был ли создан новый источник данных из шаблона. Эта функция поддерживает шаблоны ethereum/contract и file/ipfs. Для этого предусмотрены четыре функции:
 
-- `assert.dataSourceCount(templateName, expectedCount)` can be used to assert the expected count of data sources from the specified template
-- `assert.dataSourceExists(templateName, address/ipfsHash)` asserts that a data source with the specified identifier (could be a contract address or IPFS file hash) from a specified template was created
-- `logDataSources(templateName)` prints all data sources from the specified template to the console for debugging purposes
-- `readFile(path)` reads a JSON file that represents an IPFS file and returns the content as Bytes
+- `assert.dataSourceCount(templateName,expectedCount)` можно использовать для подтверждения ожидаемого количества источников данных из указанного шаблона
+- `assert.dataSourceExists(templateName, адрес/ipfsHash)` подтверждает, что источник данных с указанным идентификатором (может быть адресом контракта или хешем файла IPFS) из указанного шаблона был создан
+- `logDataSources(templateName)` выводит все источники данных из указанного шаблона на консоль в целях отладки
+- `readFile(path)` считывает файл JSON, представляющий файл IPFS, и возвращает содержимое в виде байтов
 
-#### Testing `ethereum/contract` templates
+#### Тестирование шаблонов `ethereum/contract`
 
 ```typescript
 test('ethereum/contract dataSource creation example', () => {
-  // Assert there are no dataSources created from GraphTokenLockWallet template
-  assert.dataSourceCount('GraphTokenLockWallet', 0)
+// Подтверждаем, что не создано ни одного источника данных из шаблона GraphTokenLockWallet
+assert.dataSourceCount('GraphTokenLockWallet', 0)
 
-  // Create a new GraphTokenLockWallet datasource with address 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
-  GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
+// Создаем новый источник данных GraphTokenLockWallet с адресом 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
+GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
 
-  // Assert the dataSource has been created
-  assert.dataSourceCount('GraphTokenLockWallet', 1)
+// Подтверждаем, что источник данных создан
+assert.dataSourceCount('GraphTokenLockWallet', 1)
 
-  // Add a second dataSource with context
-  let context = new DataSourceContext()
-  context.set('contextVal', Value.fromI32(325))
+// Добавляем второй источник данных с контекстом
+let context = new DataSourceContext()
+context.set('contextVal', Value.fromI32(325))
 
-  GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
+GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
 
-  // Assert there are now 2 dataSources
-  assert.dataSourceCount('GraphTokenLockWallet', 2)
+// Подтверждаем, что теперь есть 2 источника данных
+assert.dataSourceCount('GraphTokenLockWallet', 2)
 
-  // Assert that a dataSource with address "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B" was created
-  // Keep in mind that `Address` type is transformed to lower case when decoded, so you have to pass the address as all lower case when asserting if it exists
-  assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
+// Подтверждаем, что был создан источник данных с адресом "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B"
+// Имейте в виду, что тип `Address` преобразуется в строчные буквы при декодировании, поэтому адрес нужно передавать полностью в нижнем регистре, когда Вы проверяете его наличие.
+assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
 
-  logDataSources('GraphTokenLockWallet')
+logDataSources('GraphTokenLockWallet')
 })
 ```
 
-##### Example `logDataSource` output
+##### Пример вывода `logDataSource`
 
 ```bash
 🛠  {
@@ -1149,11 +1158,11 @@ test('ethereum/contract dataSource creation example', () => {
 }
 ```
 
-#### Testing `file/ipfs` templates
+#### Тестирование шаблонов `file/ipfs`
 
-Similarly to contract dynamic data sources, users can test test file datas sources and their handlers
+Аналогично контрактным источникам динамических данных пользователи могут тестировать источники данных тестовых файлов и их обработчики
 
-##### Example `subgraph.yaml`
+##### Пример `subgraph.yaml`
 
 ```yaml
 ...
@@ -1174,7 +1183,7 @@ templates:
           file: ./abis/GraphTokenLockWallet.json
 ```
 
-##### Example `schema.graphql`
+##### Пример `schema.graphql`
 
 ```graphql
 """
@@ -1194,7 +1203,7 @@ type TokenLockMetadata @entity {
 }
 ```
 
-##### Example `metadata.json`
+##### Пример `metadata.json`
 
 ```json
 {
@@ -1205,15 +1214,15 @@ type TokenLockMetadata @entity {
 }
 ```
 
-##### Example handler
+##### Пример обработчика
 
 ```typescript
 export function handleMetadata(content: Bytes): void {
-  // dataSource.stringParams() returns the File DataSource CID
-  // stringParam() will be mocked in the handler test
-  // for more info https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
-  let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
-  const value = json.fromBytes(content).toObject()
+ // dataSource.stringParams() возвращает CID источника данных файла
+// stringParam() будет имитироваться в тесте обработчика
+// для получения дополнительной информации https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
+let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
+const value = json.fromBytes(content).toObject()
 
   if (value) {
     const startTime = value.get('startTime')
@@ -1233,7 +1242,7 @@ export function handleMetadata(content: Bytes): void {
 }
 ```
 
-##### Example test
+##### Пример теста
 
 ```typescript
 import { assert, test, dataSourceMock, readFile } from 'matchstick-as'
@@ -1244,31 +1253,32 @@ import { TokenLockMetadata } from '../../generated/schema'
 import { GraphTokenLockMetadata } from '../../generated/templates'
 
 test('file/ipfs dataSource creation example', () => {
-  // Generate the dataSource CID from the ipfsHash + ipfs path file
-  // For example QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
+  // Сгенерируйте the dataSource CID from the ipfsHash + ipfs path file
+  // Например, QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
   const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
   const CID = `${ipfshash}/example.json`
 
-  // Create a new dataSource using the generated CID
+  // Создайте новый источник данных, используя сгенерированный CID
   GraphTokenLockMetadata.create(CID)
 
-  // Assert the dataSource has been created
+  // Подтвердите, что источник данных создан
   assert.dataSourceCount('GraphTokenLockMetadata', 1)
   assert.dataSourceExists('GraphTokenLockMetadata', CID)
   logDataSources('GraphTokenLockMetadata')
 
-  // Now we have to mock the dataSource metadata and specifically dataSource.stringParam()
-  // dataSource.stringParams actually uses the value of dataSource.address(), so we will mock the address using dataSourceMock from  matchstick-as
-  // First we will reset the values and then use dataSourceMock.setAddress() to set the CID
+  // Теперь нам нужно смоделировать метаданные dataSource, в частности,
+ dataSource.stringParam()
+  // dataSource.stringParams на самом деле использует значение dataSource.address(), поэтому мы будем имитировать адрес, используя dataSourceMock из matchstick-as
+  // Сначала мы сбросим значения, а затем используем dataSourceMock.setAddress() для установки CID
   dataSourceMock.resetValues()
   dataSourceMock.setAddress(CID)
 
-  // Now we need to generate the Bytes to pass to the dataSource handler
-  // For this case we introduced a new function readFile, that reads a local json and returns the content as Bytes
+  // Теперь нам нужно сгенерировать байты для передачи обработчику dataSource
+  // Для этого случая мы ввели новую функцию readFile, которая считывает локальный json и возвращает содержимое в виде байтов
   const content = readFile(`path/to/metadata.json`)
   handleMetadata(content)
 
-  // Now we will test if a TokenLockMetadata was created
+  // Теперь проверим, был ли создан TokenLockMetadata
   const metadata = TokenLockMetadata.load(CID)
 
   assert.bigIntEquals(metadata!.endTime, BigInt.fromI32(1))
@@ -1371,19 +1381,23 @@ Global test coverage: 22.2% (2/9 handlers).
 Это означает, что Вы использовали в своем коде `console.log`, который не поддерживается AssemblyScript. Пожалуйста, рассмотрите возможность использования [API логирования](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Несовпадение в аргументах вызвано несоответствием в `graph-ts` и `matchstick-as`. Лучший способ устранить проблемы, подобные этой, - обновить всё до последней выпущенной версии.
 
+## Дополнительные источники
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Обратная связь
 
 Если у Вас есть какие-либо вопросы, отзывы, пожелания по функциям или Вы просто хотите связаться с нами, лучшим местом будет Graph Discord, где у нас есть выделенный канал для Matchstick под названием 🔥| unit-testing.

From 0f517215953028dd154e3f6b893e6f0761fc2229 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:09 -0500
Subject: [PATCH 0013/1325] New translations curating.mdx (Turkish)

---
 website/pages/tr/network/curating.mdx | 56 +++++----------------------
 1 file changed, 9 insertions(+), 47 deletions(-)

diff --git a/website/pages/tr/network/curating.mdx b/website/pages/tr/network/curating.mdx
index 4dd69fee41a8..17c05c0de615 100644
--- a/website/pages/tr/network/curating.mdx
+++ b/website/pages/tr/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risks
 
 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version.
    - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,7 +61,7 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. How do I decide which subgraphs are high quality to signal on?
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
 - Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
@@ -78,50 +76,14 @@ Subgraph'ınızı çok sık güncellememeniz önerilir. Daha fazla ayrıntı iç
 
 ### 5. Can I sell my curation shares?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Price per shares](/img/price-per-share.png)
-
-As a result, price increases linearly, meaning that it will get more expensive to purchase a share over time. Here’s an example of what we mean, see the bonding curve below:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Consider we have two curators that mint shares for a subgraph:
-
-- Curator A is the first to signal on the subgraph. By adding 120,000 GRT into the curve, they are able to mint 2000 shares.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Since both curators hold half the total of curation shares, they would receive an equal amount of curator royalties.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- The remaining curator would now receive all the curator royalties for that subgraph. If they were to burn their shares to withdraw GRT, they would receive 120,000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In the case of The Graph, [Bancor’s implementation of a bonding curve formula](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) is leveraged.
-
 Still confused? Check out our Curation video guide below:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 0b005a81919d1b98ba0d0d2e79408de0868b3e1b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:10 -0500
Subject: [PATCH 0014/1325] New translations delegating.mdx (Russian)

---
 website/pages/ru/network/delegating.mdx | 95 +++++++++++++++++--------
 1 file changed, 66 insertions(+), 29 deletions(-)

diff --git a/website/pages/ru/network/delegating.mdx b/website/pages/ru/network/delegating.mdx
index a05f9a7b20de..423bafc439ab 100644
--- a/website/pages/ru/network/delegating.mdx
+++ b/website/pages/ru/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Делегирование
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Инструкция Делегатора
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,86 @@ There are three sections in this guide:
 
 Делегаторы не могут быть наказаны за некорректное поведение, но они уплачивают комиссию на делегацию, который должен стимулировать обдуманный выбор Индексатора для делегации.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Период unbonding (разблокировки) делегирования
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Обратите внимание на комиссию в размере 0,5% в
-  пользовательском интерфейсе Delegation, а также на 28-дневный срок период разблокировки._
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Обратите внимание на комиссию в размере 0,5% в пользовательском интерфейсе Delegation, а также на 28-дневный срок
+  период разблокировки._
 </div>
 
 ### Выбор надежного Индексатора со справедливым распределением вознаграждений для Делегаторов
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Топ-индексатор отдает делегаторам 90% вознаграждений. Средний
   отдает - 20%. Нижний индексатор дает ~83%
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Расчет ожидаемой доходности делегатов
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Технически подкованный Делегатор также может оценить способность Индексатора использовать доступные ему делегированные токены. Если Индексатор не распределяет все доступные токены, он не зарабатывает максимальную прибыль, которую мог бы получить для себя или своих Делегаторов.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Учёт среза комиссии за запросы и срез вознаграждения за индексацию
 
-Как описано в предыдущих разделах, следует выбирать Индексатора, который является прозрачным и честным в установлении своего Среза комиссии за запросы и Среза вознаграждения за индексацию. Делегатору также стоит обратить внимание на время охлаждения параметров, чтобы понять, какой временной запас у него есть. После этого достаточно просто рассчитать количество вознаграждений, которое получают Делегаторы. Формула следующая:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Осмотр пула делегирования индексатора
 
-Еще одним аспектом, который Делегатор должен учитывать, является доля в общем пуле делегирования, которая принадлежит ему. Все вознаграждения от делегирования распределяются равномерно, с простым перебалансированием пула, определяемым количеством токенов, которое Делегатор внес в пул. Это дает Делегатору определенную долю в пуле:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Учёт возможности делегирования
 
-Еще одним фактором, который следует учитывать, является вместимость делегирования. В настоящее время соотношение делегирования установлено на уровне 16. Это означает, что если у Индексатора есть 1,000,000 застейканых GRT, его вместимость делегирования составляет 16,000,000 GRT делегированных токенов, которые он может использовать в протоколе. Любые делегированные токены сверх этого объема будут разбавлять вознаграждения всех Делегаторов.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### Ошибка Метамаска "Pending Transaction"
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Пример
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Видео руководство по сетевому интерфейсу
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 8885a0108a6389cda852de0cb86e2a8ab0246a1a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:11 -0500
Subject: [PATCH 0015/1325] New translations explorer.mdx (French)

---
 website/pages/fr/network/explorer.mdx | 103 +++++++++++++++++---------
 1 file changed, 68 insertions(+), 35 deletions(-)

diff --git a/website/pages/fr/network/explorer.mdx b/website/pages/fr/network/explorer.mdx
index 8542686d9f27..fa9c6046f691 100644
--- a/website/pages/fr/network/explorer.mdx
+++ b/website/pages/fr/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Découvrez Graph Explorer et accédez au monde des subgraphs et des données réseau.
+
+Graph Explorer se compose de plusieurs parties où vous pouvez interagir avec d'autres développeurs de subgraphs, développeurs de dapps, Curateurs, Indexeurs et Délégateurs.
+
+## Guide Vidéo
+
+Pour une vue d'ensemble de Graph Explorer, consultez la vidéo ci-dessous :
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+Après avoir terminé le déploiement et la publication de votre subgraph dans Subgraph Studio, cliquez sur l'onglet "subgraphs" en haut de la barre de navigation pour accéder aux éléments suivants :
+
+- Vos propres subgraphs terminés
+- Les subgraphs publiés par d'autres
+- Le subgraph exact que vous voulez (basé sur la date de création, le montant du signal ou le nom).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-Lorsque vous cliquerez sur un subgraph, vous pourrez tester des requêtes dans l'aire de jeu et exploiter les détails du réseau pour prendre des décisions éclairées. Vous pourrez également signaler le GRT sur votre propre subgraph ou sur les subgraphs d'autres personnes afin de sensibiliser les indexeurs à son importance et à sa qualité. Ceci est essentiel car le fait de signaler un subgraph incite à l'indexer, ce qui signifie qu'il fera surface sur le réseau pour éventuellement répondre à des requêtes.
+Lorsque vous cliquez sur un subgraph, vous pourrez faire ce qui suit :
+
+- 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.
+- Signaler des GRT sur votre propre subgraph ou sur les subgraphs des autres pour informer les Indexeurs de son importance et de sa qualité.
+- Ceci est crucial car le signalement sur un subgraph l'incite à être indexé, ce qui signifie qu'il finira par apparaître sur le réseau pour servir des requêtes.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-Sur la page dédiée à chaque subgraph, plusieurs détails font surface. Il s'agit notamment de:
+Sur la page dédiée de chaque subgraph, vous pouvez faire ce qui suit :
 
 - Signal/Un-signal sur les subgraphs
 - Afficher plus de détails tels que des graphs, l'ID de déploiement actuel et d'autres métadonnées
@@ -31,26 +45,32 @@ Sur la page dédiée à chaque subgraph, plusieurs détails font surface. Il s'a
 
 ## Participants
 
-Dans cet onglet, vous aurez une vue d'ensemble de toutes les personnes qui participent aux activités du réseau, telles que les indexeurs, les délégateurs et les curateurs. Ci-dessous, nous examinerons en profondeur ce que chaque onglet signifie pour vous.
+Cette section offre une vue d'ensemble de tous les "participants", ce qui inclut tous ceux qui participent au réseau, tels que les Indexeurs, les Délégateurs et les Curateurs.
 
 ### 1. Indexeurs
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Commençons par les indexeurs. Les indexeurs sont l'épine dorsale du protocole, étant ceux qui misent sur les subgraphs, les indexent et envoient des requêtes à toute personne consommant des subgraphs. Dans le tableau Indexeurs, vous pourrez voir les paramètres de délégation d'un indexeur, sa participation, le montant qu'ils ont misé sur chaque subgraph et le montant des revenus qu'ils ont tirés des frais de requête et des récompenses d'indexation. Analyses approfondies ci-dessous :
+Les Indexeurs sont la colonne vertébrale du protocole. Ils stakent sur les subgraphs, les indexent et servent les requêtes à quiconque consomme les subgraphs.
+
+Dans le tableau des Indexeurs, vous pouvez voir les paramètres de délégation des Indexeurs, leur staking, combien ils ont staké sur chaque subgraph et combien de revenus ils ont généré à partir des frais de requête et des récompenses d'indexation.
 
-- Query Fee Cut - le pourcentage des remises sur les frais de requête que l'indexeur conserve lorsqu'il les partage avec les délégués
-- Réduction de récompense effective - la réduction de récompense d'indexation appliquée au pool de délégation. S’il est négatif, cela signifie que l’indexeur distribue une partie de ses récompenses. S'il est positif, cela signifie que l'indexeur conserve une partie de ses récompenses
-- Cooldown Remaining : temps restant jusqu'à ce que l'indexeur puisse modifier les paramètres de délégation ci-dessus. Des périodes de refroidissement sont définies par les indexeurs lorsqu'ils mettent à jour leurs paramètres de délégation
-- Propriété : il s'agit de la participation déposée par l'indexeur, qui peut être réduite en cas de comportement malveillant ou incorrect
-- Délégué - Participation des délégués qui peut être allouée par l'indexeur, mais ne peut pas être réduite
-- Alloué - Participation que les indexeurs allouent activement aux subgraphs qu'ils indexent
-- Capacité de délégation disponible - le montant de la participation déléguée que les indexeurs peuvent encore recevoir avant qu'ils ne soient surdélégués
+**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.
+- Allocated - Le staking 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.
-- Frais de requête - il s'agit du total des frais que les utilisateurs finaux ont payés pour les requêtes d'un indexeur pendant toute la durée de l'indexation
+- 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.
 
-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 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. Les paramètres d'indexation sont définis en cliquant sur le côté droit du tableau, ou en accédant au profil d'un indexeur et en cliquant sur le bouton « Délégué ».
+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.
+
+- Les paramètres d'indexation peuvent être définis en cliquant sur le côté droit du tableau ou en accédant au profil d'un Indexeur et en cliquant sur le bouton "Delegate ".
 
 Pour en savoir plus sur la façon de devenir un indexeur, vous pouvez consulter la [documentation officielle](/network/indexing) ou les [guides de l'indexeur de la Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ Pour en savoir plus sur la façon de devenir un indexeur, vous pouvez consulter
 
 ### 2. Curateurs
 
-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 intéressant, il peut le curer en signalant sa courbe de liaison. Ce faisant, les curateurs indiquent aux indexeurs quels sont les subgraphs de haute qualité qui devraient être indexés.
+Les Curateurs analysent les subgraphs pour identifier ceux de la plus haute qualité. Une fois qu'un Curateur a trouvé un subgraph potentiellement de haute qualité, il peut le curer en le signalant sur sa courbe de liaison. Ce faisant, les Curateurs informent les Indexeurs des subgraphs de haute qualité qui doivent être indexés.
+
+- Les Curateurs peuvent être des membres de la communauté, des consommateurs de données ou même des développeurs de subgraphs qui signalent leurs propres subgraphs en déposant des jetons GRT dans une courbe de liaison.
+  - En déposant des GRT, les Curateurs mintent des actions de curation d'un subgraph. En conséquence, ils peuvent gagner une partie des frais de requête générés par le subgraph sur lequel ils ont signalé.
+  - La courbe de liaison incite les Curateurs à curer les sources de données de la plus haute qualité.
 
-Les conservateurs peuvent être des membres de la communauté, des consommateurs de données ou même des développeurs de subgraphs qui signalent sur leurs propres subgraphs en déposant des jetons GRT dans une courbe de liaison. En déposant GRT, les curateurs créent des actions de curation d'un subgraph. En conséquence, les curateurs sont éligibles pour gagner une partie des frais de requête générés par le subgraph sur lequel ils ont signalé. La courbe de liaison incite les curateurs à conserver des sources de données de la plus haute qualité. Le Tableau Curateurs de cette section vous permettra de voir :
+Dans le tableau des Curateurs ci-dessous, vous pouvez voir :
 
 - La date à laquelle le curateur a commencé à organiser
 - Le nombre de GRT déposés
@@ -68,34 +92,36 @@ Les conservateurs peuvent être des membres de la communauté, des consommateurs
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-Si vous souhaitez en savoir plus sur le rôle de curateur, vous pouvez le faire en visitant les liens suivants de [The Graph Academy](https://thegraph.academy/curators/) ou de la [documentation officielle.](/network/curating)
+Si vous souhaitez en savoir plus sur le rôle de Curateur, vous pouvez le faire en consultant la [documentation officielle.](/network/curating) ou [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Délégués
 
-Les délégués 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 « jalonnant ») des jetons GRT à un ou plusieurs indexeurs. Sans délégués, les indexeurs sont moins susceptibles de gagner des récompenses et des frais importants. Par conséquent, les indexeurs cherchent à attirer les délégants en leur offrant une partie des récompenses d'indexation et des frais de requête qu'ils gagnent.
+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.
 
-Les délégués, quant à eux, sélectionnent les indexeurs sur la base d'un certain nombre de variables différentes, telles que les performances passées, les taux de récompense de l'indexation et les réductions des frais d'interrogation. La réputation au sein de la communauté peut également jouer un rôle à cet égard ! Il est recommandé d'entrer en contact avec les indexeurs sélectionnés via le [Discord du Graph](https://discord.gg/graphprotocol) ou le [Forum du Graph](https://forum.thegraph.com/) !
+- Sans Délégateurs, les Indexeurs sont moins susceptibles de gagner des récompenses et des frais importants. Par conséquent, les Indexeurs attirent les Délégateurs en leur offrant une partie de leurs récompenses d'indexation et de leurs frais de requête.
+- 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é de se connecter avec les Indexeurs sélectionnés via [Discord](https://discord.gg/graphprotocol) ou [le Forum](https://forum.thegraph.com/) de The Graph!
 
 ![Explorer Image 7](/img/Delegation-Overview.png)
 
-Le tableau des délégués vous permet de voir les délégués actifs dans la communauté, ainsi que des indicateurs tels que :
+Dans le tableau des Délégateurs, vous pouvez voir les Délégateurs actifs dans la communauté et les métriques importantes :
 
 - Le nombre d’indexeurs auxquels un délégant délègue
 - Délégation originale d’un délégant
 - Les récompenses qu'ils ont accumulées mais qu'ils n'ont pas retirées du protocole
 - Les récompenses obtenues qu'ils ont retirées du protocole
 - Quantité totale de GRT qu'ils ont actuellement dans le protocole
-- La date de leur dernière délégation à
+- La date de leur dernière délégation
 
-Si vous voulez en savoir plus sur la façon de devenir un délégué, ne cherchez plus ! Il vous suffit de consulter la [documentation officielle](/network/delegating) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+Si vous souhaitez en savoir plus sur comment devenir Délégateur, consultez la [documentation officielle](/network/delegating) ou [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Réseau
 
-Dans la section Réseau, vous verrez des indicateurs globaux ainsi que la possibilité de passer à une base par écho et d'analyser les paramètres du réseau de manière plus détaillée. Ces détails vous donneront une idée des performances du réseau au fil du temps.
+Dans cette section, vous pouvez consulter les indicateurs clés de performance (KPI) globaux du réseau et passer en mode par époque (epoch) pour analyser plus en détail les métriques du réseau. Ces informations vous donneront une vision de l’évolution des performances du réseau du réseau au fil du temps.
 
 ### Aperçu
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+La section d'aperçu présente à la fois toutes les métriques actuelles du réseau et certaines métriques cumulatives au fil du temps :
 
 - L’enjeu total actuel du réseau
 - La répartition des enjeux entre les indexeurs et leurs délégués
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Paramètres du protocole tels que la récompense de la curation, le taux d'inflation, etc
 - Récompenses et frais de l'époque actuelle
 
-Quelques détails clés qui méritent d'être mentionnés :
+Quelques détails clés à noter :
 
-- Les **Frais de requête représentent les frais générés par les consommateurs**, et 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 la clôture de leurs allocations vers les subgraphs. et 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é à l'émission du réseau au cours de l'époque.** Bien que l'émission du protocole soit fixe, les récompenses ne sont frappées qu'une fois que les indexeurs ont clôturé 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 allocations qui étaient ouvertes depuis plusieurs jours).
+- **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é fermé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ées de l'émission du réseau pendant cette époque.** Bien que l'émission du protocole soit fixe, les récompenses ne sont mintées que lorsque les Indexeurs ferment leurs allocations vis-à-vis des subgraphs qu'ils ont indexés. Ainsi, le nombre de récompenses par époque varie (c'est-à-dire que pendant certaines époques, les Indexeurs peuvent avoir collectivement fermé des allocations qui ont été ouvertes pendant plusieurs jours).
 
 ![Explorer Image 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ Dans la section Époques, vous pouvez analyser, époque par époque, des métriq
   - L'époque active est celle où les indexeurs sont en train d'allouer des enjeux et de collecter des frais de requête
   - Les époques de règlement sont celles au cours desquelles les canaux d'État sont réglées. Cela signifie que les indexeurs sont soumis à des réductions si les consommateurs ouvrent des litiges à leur encontre.
   - 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 pour lesquelles il ne reste plus aucune remise sur les frais de requête à réclamer par les indexeurs, et sont donc finalisées.
+  - Les époques finalisées sont les époques qui n'ont plus de remboursements de frais de requête à réclamer par les Indexeurs.
 
 ![Explorer Image 9](/img/Epoch-Stats.png)
 
 ## Votre profil d'utilisateur
 
-Maintenant que nous avons parlé des statistiques du réseau, passons à votre profil personnel. Votre profil personnel vous permet de voir votre activité sur le réseau, quelle que soit la manière dont vous participez au réseau. Votre portefeuille crypto fera office de profil utilisateur, et avec le tableau de bord utilisateur, vous pourrez voir :
+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 :
 
 ### Aperçu du profil
 
-C'est ici que vous pouvez voir toutes les actions en cours que vous avez entreprises. Vous y trouverez également les informations relatives à votre profil, votre description et votre site web (si vous en avez ajouté un).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Onglet Subgraphs
 
-Si vous cliquez sur l'onglet Subgraphs, vous verrez vos subgraphs publiés. Cela n'inclut pas les subgraphs déployés avec l'interface de programmation à des fins de test - les subgraphs ne s'affichent que lorsqu'ils sont publiés sur le réseau décentralisé.
+Dans l'onglet Subgraphs, vous verrez vos subgraphs publiés.
+
+> Ceci n'inclura pas les subgraphs déployés avec la CLI à des fins de test. Les subgraphs n'apparaîtront que lorsqu'ils sont publiés sur le réseau décentralisé.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Onglet Indexation
 
-Si vous cliquez sur l'onglet Indexation, vous trouverez un tableau avec toutes les allocations actives et historiques vers les subgraphs, ainsi que des graphs que vous pouvez analyser et voir vos performances passées en tant qu'indexeur.
+Dans l'onglet Indexation, vous trouverez un tableau avec toutes les allocations actives et historiques via-à-vis des subgraphs. Vous trouverez également des graphiques où vous pourrez voir et analyser vos performances passées en tant qu'Indexeur.
 
 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 :
 
@@ -158,7 +189,9 @@ Cette section comprendra également des détails sur vos récompenses nettes d'i
 
 ### Onglet Délégation
 
-Les délégués sont importants pour le Graph Network. Un délégant doit utiliser ses connaissances pour choisir un indexeur qui fournira un bon retour sur récompenses. Vous trouverez ici les détails de vos délégations actives et historiques, ainsi que les mesures des indexeurs vers lesquels vous avez délégué.
+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.
+
+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é.
 
 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.
 
@@ -198,6 +231,6 @@ Dans votre profil utilisateur, vous pourrez gérer les détails de votre profil
 
 ![Explorer Image 15](/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.
+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.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>![Détails du portefeuille](/img/Wallet-Details.png)</div>

From a1f3e180e54b457167274ea2c00b433b2a4ba5a5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:12 -0500
Subject: [PATCH 0016/1325] New translations developing.mdx (Hindi)

---
 website/pages/hi/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/hi/network/developing.mdx b/website/pages/hi/network/developing.mdx
index bb2091a777df..edd73ccbe18e 100644
--- a/website/pages/hi/network/developing.mdx
+++ b/website/pages/hi/network/developing.mdx
@@ -2,52 +2,29 @@
 title: विकसित होना
 ---
 
-डेवलपर्स द ग्राफ इकोसिस्टम के डिमांड साइड हैं। डेवलपर्स सबग्राफ बनाते हैं और उन्हें ग्राफ़ नेटवर्क पर प्रकाशित करते हैं। फिर, वे अपने अनुप्रयोगों को शक्ति प्रदान करने के लिए ग्राफकलाइन के साथ लाइव सबग्राफ को क्वेरी करते हैं।
+कोडिंग तुरंत शुरू करने के लिए, [डेवलपर क्विक स्टार्ट पर जाएं](/quick-start/)।
 
-## सबग्राफ जीवनचक्र
+## अवलोकन
 
-नेटवर्क में परिनियोजित सबग्राफ का एक परिभाषित जीवनचक्र होता है।
+एक डेवलपर के रूप में, आपको अपने dapp को बनाने और शक्ति प्रदान करने के लिए डेटा की आवश्यकता होती है। ब्लॉकचेन डेटा को क्वेरी करना और इंडेक्स करना चुनौतीपूर्ण होता है, लेकिन The Graph इस समस्या का समाधान प्रदान करता है।
 
-### स्थानीय रूप से बनाएँ
+The Graph पर, आप:
 
-जैसा कि सभी सबग्राफ विकास के साथ होता है, यह स्थानीय विकास और परीक्षण से शुरू होता है। डेवलपर उसी स्थानीय सेटअप का उपयोग कर सकते हैं, चाहे वे ग्राफ़ नेटवर्क, होस्ट की गई सेवा या स्थानीय ग्राफ़ नोड के लिए बना रहे हों, अपने निर्माण के लिए `ग्राफ़-क्ली` और `ग्राफ़-टीएस` का लाभ उठा रहे हों सबग्राफ। डेवलपर्स को अपने सबग्राफ की मजबूती में सुधार करने के लिए इकाई परीक्षण के लिए [मैचस्टिक](https://github.com/LimeChain/matchstick) जैसे उपकरणों का उपयोग करने के लिए प्रोत्साहित किया जाता है।
+1.  "बनाएँ, डिप्लॉय करें, और The Graph में subgraphs प्रकाशित करें Graph CLI और" [Subgraph Studio](https://thegraph.com/studio/).
+2.  मौजूदा subgraphs को क्वेरी करने के लिए GraphQL का उपयोग करें।
 
-> फीचर और नेटवर्क सपोर्ट के मामले में द ग्राफ नेटवर्क पर कुछ बाधाएं हैं। केवल [समर्थित नेटवर्क](/developing/supported-networks) पर सबग्राफ इंडेक्सिंग पुरस्कार अर्जित करेंगे, और IPFS से डेटा प्राप्त करने वाले सबग्राफ भी योग्य नहीं हैं।
+### GraphQL क्या है?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) APIs  के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है।
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### डेवलपर क्रियाएँ
 
-### नेटवर्क पर प्रकाशित करें
+- अन्य डेवलपर्स द्वारा बनाए गए subgraphs को [The Graph Network](https://thegraph.com/explorer) में query करें और उन्हें अपनी dapps में एकीकृत करें।
+- विशिष्ट डेटा आवश्यकताओं को पूरा करने के लिए कस्टम सबग्राफ़ बनाएं, जिससे अन्य डेवलपर्स के लिए स्केलेबिलिटी और लचीलापन में सुधार हो सके।
+- अपने subgraphs को The Graph Network में तैनात करें, प्रकाशित करें और संकेत दें।
 
-जब डेवलपर अपने सबग्राफ से खुश होता है, तो वे इसे द ग्राफ़ नेटवर्क पर प्रकाशित कर सकते हैं। यह एक ऑन-चेन एक्शन है, जो सबग्राफ को पंजीकृत करता है ताकि यह इंडेक्सर्स द्वारा खोजा जा सके। प्रकाशित सबग्राफ में संबंधित एनएफटी होता है, जो तब आसानी से हस्तांतरणीय होता है। प्रकाशित सबग्राफ में मेटाडेटा जुड़ा हुआ है, जो अन्य नेटवर्क प्रतिभागियों को उपयोगी संदर्भ और जानकारी प्रदान करता है।
+### सबग्राफ़ क्या हैं?
 
-### इंडेक्सिंग को प्रोत्साहित करने के लिए सिग्नल
+एक Subgraph एक कस्टम API है जो ब्लॉकचेन डेटा पर आधारित होता है। यह ब्लॉकचेन से डेटा निकालता है, उसे प्रोसेस करता है, और उसे इस तरह से संग्रहित करता है कि उसे GraphQL के माध्यम से आसानी से क्वेरी किया जा सके।
 
-प्रकाशित उपग्राफों को संकेत जोड़े बिना अनुक्रमणकों द्वारा उठाए जाने की संभावना नहीं है। सिग्नल किसी दिए गए सबग्राफ से जुड़ा GRT लॉक है, जो इंडेक्सर्स को इंगित करता है कि एक दिया गया सबग्राफ क्वेरी वॉल्यूम प्राप्त करेगा, और इसे प्रोसेस करने के लिए उपलब्ध इंडेक्सिंग रिवार्ड्स में भी योगदान देता है। इंडेक्सिंग को प्रोत्साहित करने के लिए सबग्राफ डेवलपर्स आमतौर पर अपने सबग्राफ में सिग्नल जोड़ते हैं। तीसरे पक्ष के क्यूरेटर किसी दिए गए सबग्राफ पर भी संकेत दे सकते हैं, अगर उन्हें लगता है कि सबग्राफ से क्वेरी वॉल्यूम बढ़ने की संभावना है।
-
-### पूछताछ & एप्लीकेशन का विकास
-
-एक बार एक सबग्राफ इंडेक्सर्स द्वारा संसाधित किया गया है और पूछताछ के लिए उपलब्ध है, डेवलपर्स अपने अनुप्रयोगों में सबग्राफ का उपयोग करना शुरू कर सकते हैं। विकासकर्ता एक गेटवे के माध्यम से सबग्राफ को क्वेरी करते हैं, जो उनके प्रश्नों को एक इंडेक्सर को अग्रेषित करता है जिसने सबग्राफ को संसाधित किया है, जीआरटी में क्वेरी शुल्क का भुगतान करता है।
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### सबग्राफ का बहिष्कार करना
-
-किसी बिंदु पर एक डेवलपर यह तय कर सकता है कि उन्हें अब प्रकाशित सबग्राफ की आवश्यकता नहीं है। उस बिंदु पर वे सबग्राफ को बहिष्कृत कर सकते हैं, जो किसी भी संकेतित जीआरटी को क्यूरेटर को लौटाता है।
-
-### विविध डेवलपर भूमिकाएँ
-
-कुछ डेवलपर नेटवर्क पर पूर्ण सबग्राफ जीवनचक्र के साथ संलग्न होंगे, अपने स्वयं के सबग्राफ पर प्रकाशन, पूछताछ और पुनरावृति करेंगे। कुछ सबग्राफ विकास पर ध्यान केंद्रित कर सकते हैं, खुले एपीआई का निर्माण कर सकते हैं, जिस पर अन्य निर्माण कर सकते हैं। कुछ एप्लिकेशन केंद्रित हो सकते हैं, दूसरों द्वारा तैनात किए गए सबग्राफ को क्वेरी कर सकते हैं।
-
-### डेवलपर्स और नेटवर्क अर्थशास्त्र
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From ca2bba354c910fb26778cd71d86d0aae2d3da797 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:13 -0500
Subject: [PATCH 0017/1325] New translations developing.mdx (French)

---
 website/pages/fr/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/fr/network/developing.mdx b/website/pages/fr/network/developing.mdx
index 9379c97ea334..dd4512515ba2 100644
--- a/website/pages/fr/network/developing.mdx
+++ b/website/pages/fr/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Le Développement
 ---
 
-Les développeurs constituent le côté demande de l’écosystème The Graph. Les développeurs créent des subgraphs et les publient sur The Graph Network. Ensuite, ils interrogent les subgraphs en direct avec GraphQL afin d'alimenter leurs applications.
+Pour commencer à coder immédiatement, rendez-vous sur [Démarrage rapide pour développeurs](/quick-start/).
 
-## Flux du cycle de vie des subgraphs
+## Aperçu
 
-Les subgraphs déployés sur le réseau ont un cycle de vie défini.
+En tant que développeur, vous avez besoin de données pour construire et alimenter votre d'Api. Interroger et indexer des données blockchain constitue un défi, mais The Graph fournit une solution à ce problème.
 
-### Développer localement
+Sur The Graph, vous pouvez :
 
-Comme pour tout développement de subgraphs, cela commence par le développement et les tests locaux. Les développeurs peuvent utiliser la même configuration locale, qu'ils construisent pour The Graph Network, le service hébergé ou un nœud Graph local, en tirant parti de `graph-cli` et `graph-ts` pour créer leur subgraph. Les développeurs sont encouragés à utiliser des outils tels que [Matchstick](https://github.com/LimeChain/matchstick) pour les tests unitaires afin d'améliorer la robustesse de leurs subgraphs.
+1.  Créer, déployer et publier des subgraphs sur The Graph en utilisant Graph CLI et [Subgraph Studio](https://thegraph.com/studio/).
+2.  Utiliser GraphQL pour interroger des subgraphs existants.
 
-> Le réseau de graphes est soumis à certaines contraintes, en termes de fonctionnalités et de réseaux pris en charge. Seuls les subgraphs des [réseaux pris en charge](/developing/supported-networks) obtiendront des récompenses en matière d'indexation, et les subgraphs qui récupèrent des données à partir d'IPFS ne sont pas non plus éligibles.
+### Qu'est-ce que GraphQL ?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) est le langage de requête pour les API et un un moteur d'exécution pour exécuter ces requêtes avec vos données existantes. The Graph utilise GraphQL pour interroger les subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Actions des Développeurs
 
-### Publier sur le réseau
+- Interroger des subgraphs créés par d'autres développeurs dans [The Graph Network](https://thegraph.com/explorer) et les intégrer dans vos propres dapps.
+- Créer des subgraphs personnalisés pour répondre à des besoins de données spécifiques, permettant une meilleure évolutivité et flexibilité pour les autres développeurs.
+- Déployer, publier et signaler vos subgraphs au sein de The Graph Network.
 
-Lorsque le développeur est satisfait de son subgraph, il peut le publier sur le réseau The Graph. Il s'agit d'une action 'on-chain', qui enregistre le subgraph afin qu'il puisse être découvert par les indexeurs. Les subgraphs publiés ont un NFT correspondant, qui est alors facilement transférable. Le subgraph publié est associé à des métadonnées qui fournissent aux autres participants du réseau un contexte et des informations utiles.
+### Que sont les subgraphs ?
 
-### Signal pour encourager l'indexation
+Un subgraph est une API personnalisée construite sur des données blockchain. Il extrait des données d'une blockchain, les traite et les stocke afin qu'elles puissent être facilement interrogées via GraphQL.
 
-Les subgraphs publiés ont peu de chances d'être repérés par les indexeurs sans l'ajout d'un signal. Le signal est constitué de GRT verrouillés associés à un subgraph donné, ce qui indique aux indexeurs qu'un subgraph donné recevra du volume de requêtes et contribue également aux récompenses d'indexation disponibles pour le traiter. Les développeurs de subgraphs ajoutent généralement un signal à leur subgraph afin d'encourager l'indexation. Les curateurs tiers peuvent également ajouter un signal à un subgraph donné s'ils estiment que ce dernier est susceptible de générer un volume de requêtes.
-
-### Interrogation & Développement d'applications
-
-Une fois qu'un subgraph a été traité par les indexeurs et est disponible pour l'interrogation, les développeurs peuvent commencer à utiliser le subgraph dans leurs applications. Les développeurs interrogent les subgraphs via une passerelle, qui transmet leurs requêtes à un indexeur qui a traité le subgraph, en payant les frais de requête en GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Mise à jour des subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Une fois que le développeur de subgraph est prêt à mettre à jour, il peut lancer une transaction pour pointer son subgraph vers la nouvelle version. La mise à jour du subgraph migre tout signal vers la nouvelle version (en supposant que l'utilisateur qui a appliqué le signal a sélectionné "migrer automatiquement"), ce qui entraîne également une taxe de migration. Cette migration de signal devrait inciter les indexeurs à commencer à indexer la nouvelle version du subgraph, elle devrait donc bientôt être disponible pour les interrogations.
-
-### Dépréciation des subgraphs
-
-À un moment donné, un développeur peut décider qu'il n'a plus besoin d'un subgraph publié. À ce stade, ils peuvent déprécier le subgraph, qui renvoie tout GRT signalé aux curateurs.
-
-### Diversité des rôles des développeurs
-
-Certains développeurs s'engageront dans le cycle de vie complet des subgraphs sur le réseau, en publiant, en interrogeant et en itérant sur leurs propres subgraphs. D'autres se concentreront sur le développement de subgraphs, en créant des API ouvertes sur lesquelles d'autres pourront s'appuyer. D'autres peuvent se concentrer sur les applications, en interrogeant les subgraphs déployés par d'autres.
-
-### Economie du réseau et des développeurs
-
-Les développeurs sont des acteurs économiques clés dans le réseau, bloquant des GRT pour encourager l'indexation et, surtout, interroger des subgraphs, ce qui constitue l'échange de valeur principal du réseau. Les développeurs de subgraphs brûlent également des GRT à chaque mise à jour d'un subgraph.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 28afca5a9e86eb230649ed1b0b590f965be7a2fe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:14 -0500
Subject: [PATCH 0018/1325] New translations quick-start.mdx (Hindi)

---
 website/pages/hi/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/hi/quick-start.mdx b/website/pages/hi/quick-start.mdx
index ad090e4226e8..aa55257484bd 100644
--- a/website/pages/hi/quick-start.mdx
+++ b/website/pages/hi/quick-start.mdx
@@ -2,24 +2,26 @@
 title: जल्दी शुरू
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-यह मार्गदर्शिका यह मानते हुए लिखी गई है कि आपके पास:
+## आवश्यक शर्तें
 
 - एक क्रिप्टो वॉलेट
-- आपकी पसंद के नेटवर्क पर एक स्मार्ट अनुबंध पता
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. सबग्राफ स्टूडियो पर एक सबग्राफ बनाएं
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+[Subgraph Studio](https://thegraph.com/studio/) पर जाएँ और अपने वॉलेट को कनेक्ट करें।
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio आपको सबग्राफ़ बनाने, प्रबंधित करने, तैनात करने और प्रकाशित करने की सुविधा देता है, साथ ही API कुंजी बनाने और प्रबंधित करने की भी अनुमति देता है।
 
-## 2. ग्राफ़ सीएलआई स्थापित करें
+"एक सबग्राफ बनाएं" पर क्लिक करें। सबग्राफ का नाम टाइटल केस में रखनाrecommended है: "सबग्राफ नाम चेन नाम"।
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. ग्राफ़ सीएलआई स्थापित करें
 
 अपनी स्थानीय मशीन पर, निम्न आदेशों में से कोई एक चलाएँ:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. अपना Subgraph इनिशियलाइज़ करें
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+निम्नलिखित आदेश एक मौजूदा अनुबंध से आपके Subgraph को प्रारंभ करता है:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-जब आप अपना सबग्राफ इनिशियलाइज़ करते हैं, तो सीएलआई टूल आपसे निम्नलिखित जानकारी मांगेगा:
+जब आप अपने subgraph को प्रारंभ करते हैं, CLI आपसे निम्नलिखित जानकारी मांगेगा:
 
-- प्रोटोकॉल: वह प्रोटोकॉल चुनें जिससे आपका सबग्राफ डेटा को अनुक्रमित करेगा
-- सबग्राफ स्लग: अपने सबग्राफ के लिए एक नाम बनाएं। आपका सबग्राफ स्लग आपके सबग्राफ के लिए एक पहचानकर्ता है।
-- सबग्राफ बनाने के लिए निर्देशिका: अपनी स्थानीय निर्देशिका चुनें
-- एथेरियम नेटवर्क (वैकल्पिक): आपको यह निर्दिष्ट करने की आवश्यकता हो सकती है कि आपका सबग्राफ किस ईवीएम-संगत नेटवर्क से डेटा को अनुक्रमित करेगा
-- अनुबंध का पता: उस स्मार्ट अनुबंध के पते का पता लगाएं, जिससे आप डेटा की क्वेरी करना चाहते हैं
-- ABI: यदि ABI ऑटोपॉप्युलेटेड नहीं है, तो आपको इसे JSON फ़ाइल के रूप में मैन्युअल रूप से इनपुट करना होगा
-- स्टार्ट ब्लॉक: यह सुझाव दिया जाता है कि आप समय बचाने के लिए स्टार्ट ब्लॉक इनपुट करें जबकि आपका सबग्राफ ब्लॉकचैन डेटा को अनुक्रमित करता है। आप उस ब्लॉक को ढूंढकर स्टार्ट ब्लॉक का पता लगा सकते हैं जहां आपका अनुबंध तैनात किया गया था।
-- अनुबंध का नाम: अपने अनुबंध का नाम इनपुट करें
-- इकाइयों के रूप में अनुक्रमणिका अनुबंध ईवेंट: यह सुझाव दिया जाता है कि आप इसे सही पर सेट करें क्योंकि यह प्रत्येक उत्सर्जित ईवेंट के लिए स्वचालित रूप से आपके सबग्राफ में मैपिंग जोड़ देगा
-- दूसरा अनुबंध जोड़ें (वैकल्पिक): आप एक और अनुबंध जोड़ सकते हैं
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 अपने सबग्राफ को इनिशियलाइज़ करते समय क्या अपेक्षा की जाए, इसके उदाहरण के लिए निम्न स्क्रीनशॉट देखें:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![Subgraph command](/img/CLI-Example.png)
+
+### 4. Edit your subgraph
+
+पिछले चरण में `init` कमांड एक स्कैफोल्ड Subgraph बनाता है जिसे आप अपने Subgraph को बनाने के लिए प्रारंभिक बिंदु के रूप में उपयोग कर सकते हैं।
+
+जब आप Subgraph में बदलाव करते हैं, तो आप मुख्य रूप से तीन फाइलों के साथ काम करेंगे:
 
-## 4. Write your subgraph
+- Manifest (subgraph.yaml) - मेनिफेस्ट परिभाषित करता है कि आपका Subgraph किस डेटा सोर्स को अनुक्रमित करेगा
+- Schema (schema.graphql) - ग्राफक्यूएल स्कीमा परिभाषित करता है कि आप Subgraph से कौन सा डेटा प्राप्त करना चाहते हैं
+- असेंबलीस्क्रिप्ट मैपिंग (mapping.ts) - यह वह कोड है जो स्कीमा में परिभाषित इकाई के लिए आपके डेटा सोर्स से डेटा का अनुवाद करता है।
 
-पिछले आदेश एक मचान सबग्राफ बनाते हैं जिसका उपयोग आप अपने सबग्राफ के निर्माण के लिए शुरुआती बिंदु के रूप में कर सकते हैं। सबग्राफ में बदलाव करते समय, आप मुख्य रूप से तीन फाइलों के साथ काम करेंगे:
+अपने उपग्राफ को लिखने के लिए विस्तृत विवरण के लिए, [सबग्राफ बनाना](/developing/creating-a-subgraph/) देखें।
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. अपने Subgraph का परीक्षण करें
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+याद रखें, तैनाती और प्रकाशन एक समान नहीं हैं।
 
-## 5. Deploy to Subgraph Studio
+जब आप एक सबग्राफ तैनात करते हैं, तो आप इसे [सबग्राफ स्टूडियो](https://thegraph.com/studio/) पर भेजते हैं, जहां आप इसे परीक्षण, चरणबद्ध और समीक्षा कर सकते हैं।
+
+जब आप एक Subgraph प्रकाशित करते हैं, तो आप इसे विकेंद्रीकृत नेटवर्क पर ऑन-चेन प्रकाशित कर रहे हैं।
 
 एक बार आपका सबग्राफ लिखे जाने के बाद, निम्नलिखित कमांड चलाएँ:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+अपने सबग्राफ को प्रमाणित और तैनात करें। तैनाती key सबग्राफ स्टूडियो में सबग्राफ पेज पर पाई जा सकती है।
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- अपने सबग्राफ को प्रमाणित और तैनात करें। तैनाती key सबग्राफ स्टूडियो में सबग्राफ पेज पर पाई जा सकती है।
+### 6. अपने 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:
+
+- एक नमूना क्वेरी चलाएँ।
+- अपने Subgraph का विश्लेषण करने के लिए डैशबोर्ड में जानकारी देखें।
+- लॉग आपको बताएंगे कि क्या आपके Subgraph में कोई त्रुटि है। एक ऑपरेशनल Subgraph के लॉग इस तरह दिखेंगे:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. अपने Subgraph को ग्राफ़ के The Graph Network पर प्रकाशित करें
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Subgraph Studio से प्रकाशित
+
+अपने subgraph को प्रकाशित करने के लिए, डैशबोर्ड में Publish बटन पर क्लिक करें।
+
+![Publish a subgraph on Subgraph Studio](/img/publish-sub-transfer.png)
+
+उस नेटवर्क का चयन करें जिस पर आप अपना Subgraph प्रकाशित करना चाहते हैं।
+
+#### Publishing from the CLI
+
+Version 0.73.0 के अनुसार, आप अपने subgraph को graph-cli के साथ भी publish कर सकते हैं।
+
+`graph-cli` खोलें।
+
+निम्नलिखित कमांड का उपयोग करें:
+
+````
 ```sh
-$ graph auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. अपने सबग्राफ का परीक्षण करें
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-लॉग आपको बताएंगे कि क्या आपके सबग्राफ में कोई त्रुटि है। एक ऑपरेशनल सबग्राफ के लॉग इस तरह दिखेंगे:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+Then,
+
+```sh
+graph publish
 ```
+````
+
+3. एक विंडो खुलेगी, जो आपको अपनी वॉलेट कनेक्ट करने, मेटाडेटा जोड़ने, और अपने अंतिम Subgraph को आपकी पसंद के नेटवर्क पर डिप्लॉय करने की अनुमति देगी।
+
+![cli-ui](/img/cli-ui.png)
+
+अपने डिप्लॉयमेंट को कस्टमाइज़ करने के लिए, देखें [Publishing a Subgraph](/publishing/publishing-a-subgraph/)।
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - यह कार्रवाई सेवा की गुणवत्ता में सुधार करती है, विलंबता को कम करती है, और आपके Subgraph के लिए नेटवर्क की पुनरावृत्ति और उपलब्धता को बढ़ाती है।
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. यदि इंडेक्सिंग पुरस्कारों के लिए योग्य हैं, तो Indexers संकेतित राशि के आधार पर GRT पुरस्कार प्राप्त करते हैं।
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - कम से कम 3,000 GRT का चयन करना अनुशंसित है ताकि 3 Indexer को आकर्षित किया जा सके। Subgraph फ़ीचर उपयोग और समर्थित नेटवर्क के आधार पर पुरस्कार पात्रता की जांच करें।
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+क्यूरेशन के बारे में अधिक जानने के लिए, पढ़ें [Curating](/network/curating/)।
 
-गैस की लागत बचाने के लिए, जब आप ग्राफ़ के विकेंद्रीकृत नेटवर्क पर अपना सबग्राफ प्रकाशित करते हैं, तो आप अपने सबग्राफ को उसी लेन-देन में क्यूरेट कर सकते हैं, जिसे आपने इस बटन का चयन करके प्रकाशित किया था:
+गैस लागत को बचाने के लिए, आप इसे प्रकाशित करते समय अपने Subgraph को उसी लेनदेन में क्यूरेट कर सकते हैं, इस विकल्प का चयन करके:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-अब, आप अपने सबग्राफ को अपने सबग्राफ के क्वेरी URL पर ग्राफ़क्यूएल क्वेरी भेजकर क्वेरी कर सकते हैं, जिसे आप क्वेरी बटन पर क्लिक करके पा सकते हैं।
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+अपने subgraph से data query करने के बारे में अधिक जानकारी के लिए, अधिक पढ़ें [Querying The Graph](/querying/querying-the-graph/)।

From fd99e6de8bcc74762408a6d32521090c179f41f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:15 -0500
Subject: [PATCH 0019/1325] New translations quick-start.mdx (German)

---
 website/pages/de/quick-start.mdx | 225 +++++++++++++++++--------------
 1 file changed, 121 insertions(+), 104 deletions(-)

diff --git a/website/pages/de/quick-start.mdx b/website/pages/de/quick-start.mdx
index 1a3c915185de..10201769e249 100644
--- a/website/pages/de/quick-start.mdx
+++ b/website/pages/de/quick-start.mdx
@@ -2,166 +2,183 @@
 title: Schnellstart
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Stellen Sie sicher, dass Ihr Subgraph Daten aus einem [unterstützten Netzwerk] (/developing/supported-networks) indiziert.
-
-Bei der Erstellung dieses Leitfadens wird davon ausgegangen, dass Sie über die entsprechenden Kenntnisse verfügen:
+## Prerequisites
 
 - Eine Krypto-Wallet
-- Eine Smart-Contract-Adresse im Netzwerk Ihrer Wahl nach
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Erstellen Sie einen Untergraphen in Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Gehen Sie zu [Subgraph Studio] (https://thegraph.com/studio/) und verbinden Sie Ihre Wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Mit Subgraph Studio können Sie Subgraphen erstellen, verwalten, bereitstellen und veröffentlichen sowie API-Schlüssel erstellen und verwalten.
 
-## 2. Installieren der Graph-CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Installieren der Graph-CLI
 
 Führen Sie einen der folgenden Befehle auf Ihrem lokalen Computer aus:
 
-Using [npm](https://www.npmjs.com/):
+Verwendung von [npm](https://www.npmjs.com/):
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
 ```
 
-Using [yarn](https://yarnpkg.com/):
+Verwendung von [yarn] (https://yarnpkg.com/):
 
 ```sh
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> Die Befehle für Ihren spezifischen Subgraphen finden Sie auf der Subgraphen-Seite in [Subgraph Studio](https://thegraph.com/studio/).
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
+
+Mit dem folgenden Befehl wird Ihr Subgraph aus einem bestehenden Vertrag initialisiert:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Wenn Sie Ihren Untergraphen initialisieren, fragt das CLI-Tool Sie nach den folgenden Informationen:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Protokoll: Wählen Sie das Protokoll aus, von dem Ihr Untergraph ( Subgraph ) Daten indizieren soll.
-- Subgraph slug: Erstellen Sie einen Namen für Ihren Subgraphen. Ihr Subgraph-Slug ist ein Identifikationsmerkmal für Ihren Subgraphen.
-- Verzeichnis zur Erstellung des Subgraphen: Wählen Sie Ihr lokales Verzeichnis
-- Ethereum-Netzwerk (optional): Sie müssen ggf. angeben, von welchem EVM-kompatiblen Netzwerk Ihr Subgraph Daten indizieren soll.
-- Vertragsadresse: Suchen Sie die Smart-Contract-Adresse, von der Sie Daten abfragen möchten
-- ABI: Wenn die ABI nicht automatisch ausgefüllt wird, müssen Sie sie manuell in Form einer JSON-Datei eingeben.
-- Startblock: Es wird empfohlen, den Startblock einzugeben, um Zeit zu sparen, während Ihr Subgraph die Blockchain-Daten indiziert. Sie können den Startblock finden, indem Sie den Block suchen, in dem Ihr Vertrag bereitgestellt wurde.
-- Vertragsname: Geben Sie den Namen Ihres Vertrags ein
-- Index contract events as entities (Vertragsereignisse als Entitäten): Es wird empfohlen, dies auf true (wahr) zu setzen, da es automatisch Zuordnungen zu Ihrem Subgraph für jedes emittierte Ereignis hinzufügt
-- Einen weiteren Vertrag hinzufügen (optional): Sie können einen weiteren Vertrag hinzufügen
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 Der folgende Screenshot zeigt ein Beispiel dafür, was Sie bei der Initialisierung Ihres Untergraphen ( Subgraph ) erwarten können:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![Subgraph command](/img/CLI-Example.png)
+
+### 4. Edit your subgraph
 
-## 4. Write 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.
 
-Die vorangegangenen Befehle erstellen einen gerüstartigen Subgraphen, den Sie als Ausgangspunkt für den Aufbau Ihres Subgraphen verwenden können. Wenn Sie Änderungen an dem Subgraphen vornehmen, werden Sie hauptsächlich mit
+When making changes to the subgraph, you will mainly work with three files:
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+- Manifest (`subgraph.yaml`) - definiert, welche Datenquellen Ihr Subgraph indizieren wird.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (mapping.ts) - Dies ist der Code, der die Daten aus Ihren Datenquellen in die im Schema definierten Entitäten übersetzt.
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 5. Deploy to Subgraph Studio
+### 5. Deploy your subgraph
+
+Denken Sie daran, dass die Bereitstellung nicht dasselbe ist wie die Veröffentlichung.
+
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Sobald Ihr Subgraph geschrieben ist, führen Sie die folgenden Befehle aus:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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
 
-- Authentifizieren Sie Ihren Subgraphen und stellen Sie ihn bereit. Den Bereitstellungsschlüssel finden Sie auf der Seite "Subgraph" in Subgraph Studio.
+If you’d like to test your subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following:
 
+- Führen Sie eine Testabfrage durch.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Veröffentlichung mit Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![Publish a subgraph on Subgraph Studio](/img/publish-sub-transfer.png)
+
+Select the network to which you would like to publish your subgraph.
+
+#### Veröffentlichen über die CLI
+
+As of version 0.73.0, you can also publish your subgraph with the Graph CLI.
+
+Öffnen Sie den `graph-cli`.
+
+Verwenden Sie die folgenden Befehle:
+
+````
 ```sh
-$ graph auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Testen Sie Ihren Untergraphen ( Subgraphen )
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-In den Protokollen können Sie sehen, ob es Fehler in Ihrem Subgraphen gibt. Die Protokolle eines funktionierenden Subgraphen sehen wie folgt aus:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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)
+
+Wie Sie Ihre Bereitstellung anpassen können, erfahren Sie unter [Veröffentlichen eines Subgraphen](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. Indexer erhalten GRT Rewards auf der Grundlage des signalisierten Betrags, wenn sie für Indexing Rewards in Frage kommen.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - Es wird empfohlen, mindestens 3.000 GRT zu kuratieren, um 3 Indexer anzuziehen. Prüfen Sie die Berechtigung zum Reward anhand der Nutzung der Subgraph-Funktionen und der unterstützten Netzwerke.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+Um mehr über Kuratierung zu erfahren, lesen Sie [Kuratieren](/network/curating/).
 
-Um Gaskosten zu sparen, können Sie Ihren Subgraphen in der gleichen Transaktion kuratieren, in der Sie ihn veröffentlicht haben, indem Sie diese Schaltfläche auswählen, wenn Sie Ihren Subgraphen im dezentralen Netzwerk von The Graph veröffentlichen:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph veröffentlichen](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Jetzt können Sie Ihren Subgraphen abfragen, indem Sie GraphQL-Abfragen an die Abfrage-URL Ihres Subgraphen senden, die Sie durch Klicken auf die Abfrage-Schaltfläche finden können.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+Weitere Informationen zur Abfrage von Daten aus Ihrem Subgraphen finden Sie unter [Querying The Graph](/querying/querying-the-graph/).

From 54dbb542fbc247bc106b5d9f9c4c4b594fa443ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:16 -0500
Subject: [PATCH 0020/1325] New translations quick-start.mdx (Russian)

---
 website/pages/ru/quick-start.mdx | 225 +++++++++++++++++--------------
 1 file changed, 121 insertions(+), 104 deletions(-)

diff --git a/website/pages/ru/quick-start.mdx b/website/pages/ru/quick-start.mdx
index ff0df0fc6713..1d043dcffac2 100644
--- a/website/pages/ru/quick-start.mdx
+++ b/website/pages/ru/quick-start.mdx
@@ -2,166 +2,183 @@
 title: Быстрый старт
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Убедитесь, что ваш субграф будет индексировать данные из [поддерживаемой сети](/developing/supported-networks).
-
-Это руководство написано, исходя из того, что у Вас есть:
+## Предварительные требования
 
 - Криптовалютный кошелек
-- Адрес смарт-контракта в выбранной Вами сети
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Создание субграфа в Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Перейдите в [Subgraph Studio](https://thegraph.com/studio/) и подключите свой кошелек.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio позволяет создавать, управлять, развертывать и публиковать субграфы, а также создавать и управлять API-ключами.
 
-## 2. Установка Graph CLI
+Нажмите "Создать субграф". Рекомендуется называть субграф с использованием Заглавного регистра: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Установка Graph CLI
 
 Выполните одну из следующих команд на своём локальном компьютере:
 
-Using [npm](https://www.npmjs.com/):
+Использование [npm](https://www.npmjs.com/):
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
 ```
 
-Using [yarn](https://yarnpkg.com/):
+Использование [yarn](https://yarnpkg.com/):
 
 ```sh
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Инициализация Вашего cубграфа
+
+> Вы можете найти команды для своего конкретного субграфа на странице субграфа в [Subgraph Studio](https://thegraph.com/studio/).
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
+
+Следующая команда инициализирует ваш субграф из существующего контракта:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-При инициализации субграфа инструмент CLI запросит у Вас следующую информацию:
+При инициализации субграфа CLI запросит у Вас следующую информацию:
 
-- Протокол: выберите протокол, по которому Ваш субграф будет индексировать данные
-- Слаг субграфа: создайте имя для своего субграфа. Ваш слаг субграфа — это идентификатор для Вашего субграфа.
-- Директория для создания субграфа: выберите локальную директорию
-- Сеть Ethereum (необязательно): Вам может потребоваться указать, из какой сети, совместимой с EVM, ваш субграф будет индексировать данные
-- Адрес контракта: найдите адрес смарт-контракта, с которого хотите запросить данные
-- ABI: если ABI не заполняется автоматически, Вам нужно будет ввести его вручную как файл JSON
-- Стартовый блок: рекомендуется ввести стартовый блок, чтобы сэкономить время, пока Ваш субграф индексирует данные блокчейна. Вы можете найти стартовый блок, найдя блок, в котором был развернут Ваш контракт.
-- Имя контракта: введите имя Вашего контракта
-- Индексировать события контракта как объекты: рекомендуется установить для этого параметра значение true, поскольку он автоматически добавит сопоставления в Ваш субграф для каждого запускаемого события
-- Добавить еще один контракт (опционально): Вы можете добавить еще один контракт
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 На следующем скриншоте показан пример того, чего следует ожидать при инициализации субграфа:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![Subgraph command](/img/CLI-Example.png)
+
+### 4. Edit your subgraph
 
-## 4. Write your subgraph
+Команда `init` на предыдущем шаге создает шаблон субграфа, который Вы можете использовать в качестве отправной точки для его разработки.
 
-Предыдущая команда создала "скелет" субграфа, который Вы можете использовать в качестве отправной точки для построения своего субграфа. При внесении изменений в субграф Вы будете в основном работать с тремя файлами:
+При внесении изменений в субграф Вы будете работать в основном с тремя файлами:
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+- Манифест (`subgraph.yaml`) — определяет, какие источники данных Ваш субграф будет индексировать.
+- Схема (`schema.graphql`) - Схема GraphQL определяет, какие данные Вы хотите извлечь из субграфа.
+- AssemblyScript Mappings (mapping.ts) - это код, который преобразует данные из Ваших источников данных в объекты, определенные в схеме.
 
-Для получения дополнительной информации о том, как создать свой субграф, см. [Creating a Subgraph](/developing/creating-a-subgraph).
+Для получения более детальной информации о том, как создать свой субграф, ознакомьтесь с разделом [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 5. Deploy to Subgraph Studio
+### 5. Развертывание Вашего субграфа
+
+Помните, развертывание — это не то же самое, что публикация.
+
+Когда Вы развертываете субграф, Вы загружаете его в [Subgraph Studio](https://thegraph.com/studio/), где можете его протестировать, подготовить и просмотреть.
+
+Когда Вы публикуете субграф, Вы публикуете его в децентрализованной сети на чейне.
 
 После того как Ваш субграф будет написан, выполните следующие команды:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Аутентифицируйте и разверните свой субграф. Ключ развертывания можно найти на странице Subgraph в Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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. Просмотр Вашего субграфа
 
-- Аутентифицируйте и разверните свой субграф. Ключ развертывания можно найти на странице Subgraph в Subgraph Studio.
+If you’d like to test your subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following:
 
+- Запустить пример запроса.
+- Проанализировать Ваш субграф на панели управления для проверки информации.
+- Проверить логи на панели управления, чтобы убедиться, нет ли ошибок в Вашем субграфе. Логи рабочего субграфа будут выглядеть следующим образом:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### Публикация Вашего субграфа в сети The Graph
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Публикация с помощью Subgraph Studio
+
+Чтобы опубликовать свой субграф, нажмите кнопку «Опубликовать» на панели управления.
+
+![Publish a subgraph on Subgraph Studio](/img/publish-sub-transfer.png)
+
+Выберите сеть, в которую хотите опубликовать свой субграф.
+
+#### Публикация с помощью CLI
+
+Начиная с версии 0.73.0, Вы также можете публиковать свой субграф с помощью Graph CLI.
+
+Откройте `graph-cli`.
+
+Используйте следующие команды:
+
+````
 ```sh
-$ graph auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Тестирование Вашего субграфа
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-Логи сообщат вам, есть ли какие-либо ошибки с вашим субграфом. Логи рабочего субграфа будут выглядеть следующим образом:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+Then,
+
+```sh
+graph publish
 ```
+````
+
+3. Откроется окно, где Вы сможете подключить свой кошелек, добавить метаданные и развернуть финализированный субграф в выбранной Вами сети.
+
+![cli-ui](/img/cli-ui.png)
+
+Для настройки развертывания ознакомьтесь с разделом [Публикация субграфа](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Добавление сигнала к Вашему субграфу
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - Это действие улучшает качество обслуживания, снижает задержку и увеличивает надежность и доступность сети для Вашего субграфа.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. Если индексаторы имеют право на получение вознаграждений за индексацию, они получат вознаграждения в GRT, в соответствии с количеством поданного сигнала.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - Рекомендуется добавить как минимум 3,000 GRT, чтобы привлечь 3 индексаторов. Проверьте право на вознаграждение на основе использования функций субграфа и поддерживаемых сетей.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+Чтобы узнать больше о кураторстве, прочитайте раздел [Curating](/network/curating/).
 
-Чтобы сэкономить на расходах за газ, Вы можете курировать свой субграф в той же транзакции, в которой Вы его опубликовали, нажав эту кнопку при публикации своего субграфа в децентрализованной сети The Graph:
+Чтобы сэкономить на расходах на газ, Вы можете курировать свой субграф в той же транзакции, в которой Вы его публикуете, выбрав эту опцию:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Запрос Вашего субграфа
 
-Теперь Вы можете запросить свой субграф, отправив запросы GraphQL на URL-адрес запроса Вашего субграфа, который можно найти, нажав кнопку запроса.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+Для получения дополнительной информации о запросах данных из Вашего субграфа прочитайте раздел [Querying The Graph](/querying/querying-the-graph/).

From c862f2793f5ba71933c2b8bd8eea361de325055d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:17 -0500
Subject: [PATCH 0021/1325] New translations quick-start.mdx (Turkish)

---
 website/pages/tr/quick-start.mdx | 225 +++++++++++++++++--------------
 1 file changed, 121 insertions(+), 104 deletions(-)

diff --git a/website/pages/tr/quick-start.mdx b/website/pages/tr/quick-start.mdx
index 6b5178a057f3..4c4b532e41c0 100644
--- a/website/pages/tr/quick-start.mdx
+++ b/website/pages/tr/quick-start.mdx
@@ -2,166 +2,183 @@
 title: Hızlı Başlangıç
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Subgraph'ınızın [desteklenen bir ağdan](/developing/supported-networks) gelen verileri indeksleyeceğinden emin olun.
-
-Bu rehber, aşağıdakilere sahip olduğunuzu varsayar:
+## Ön Koşullar
 
 - Bir kripto cüzdanı
-- Seçtiğiniz ağ üzerinde bir akıllı sözleşme adresi
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Subgraph Stüdyo'da bir subgraph oluşturun
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+[Subgraph Studio](https://thegraph.com/studio/)'ya gidin ve cüzdanınızı bağlayın.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio, subgraph oluşturmanıza, yönetmenize, yayına almanıza ve yayımlamanıza, ayrıca API anahtarlarını oluşturmanıza ve yönetmenize olanak tanır.
 
-## 2. Graph CLI'yi yükleyin
+"Subgraph Oluştur" düğmesine tıklayın. Subgraph'in adını başlık formunda vermeniz önerilir: "Subgraph Adı Ağ Adı".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Graph CLI'yi yükleyin
 
 Yerel makinenizde aşağıdaki komutlardan birini çalıştırın:
 
-Using [npm](https://www.npmjs.com/):
+[npm](https://www.npmjs.com/) kullanarak:
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
 ```
 
-Using [yarn](https://yarnpkg.com/):
+[yarn](https://yarnpkg.com/) kullanarak:
 
 ```sh
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Subgraph'inizi başlatın
+
+> Size ait spesifik subgraph'le ilgili komutları [Subgraph Studio](https://thegraph.com/studio/)'daki subgraph sayfasında bulabilirsiniz.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
+
+Aşağıdaki komut, subgraph'inizi mevcut bir akıllı sözleşmeden başlatır:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Subgraph'ınızı başlattığınızda, CLI aracı sizden aşağıdaki bilgileri isteyecektir:
+Subgraph'inizi başlattığınızda, CLI sizden aşağıdaki bilgileri isteyecektir:
 
-- Protokol: Subgraph'ınızın veri indeksleyeceği protokolü seçin
-- Subgraph slug: Subgraph'ınız için bir ad oluşturun. Subgraph slug'ınız subgraph'ınız için bir tanımlayıcıdır.
-- Subgraph'ınızın oluşturulacağı dizin: yerel dizininizi seçin
-- Ethereum ağı (opsiyonel): Subgraph'ınızın hangi EVM uyumlu ağdan veri indeksleyeceğini belirtmeniz gerekebilir
-- Sözleşme adresi: Veri sorgulamak istediğiniz akıllı sözleşme adresini bulun
-- ABI: ABI otomatik olarak doldurulmuyorsa, JSON dosyası haline manuel olarak girmeniz gerekecektir
-- Başlangıç Bloğu: Subgraph'ınız blok zinciri verilerini indekslerken zaman kazanmak için başlangıç bloğunu girmeniz önerilir. Başlangıç bloğunu, sözleşmenizin dağıtıldığı bloğu bularak bulabilirsiniz.
-- Sözleşme Adı: Sözleşmenizin adını girin
-- Sözleşme olaylarını varlıklar olarak indeksleyin: Yayılan her olay için subgraph'ınıza otomatik olarak eşlemeler ekleyeceğinden bunu true olarak ayarlamanız önerilir
-- Başka bir sözleşme ekle (opsiyonel): Başka bir sözleşme ekleyebilirsiniz
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 Subgraph'ınızı başlatırken neyle karşılaşacağınıza dair bir örnek için aşağıdaki ekran görüntüsüne bakın:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![Subgraph command](/img/CLI-Example.png)
+
+### 4. Edit your subgraph
 
-## 4. Write your subgraph
+Önceki adımda `init` komutu, subgraph'inizi oluşturmak için kullanabileceğiniz bir iskelet subgraph yaratır.
 
-Önceki komutlar, subgraph'ınızı oluşturmak için bir başlangıç noktası olarak kullanabileceğiniz bir subgraph iskeletini oluşturur. Subgraph'ta değişiklik yaparken, temel olarak üç dosya ile çalışacaksınız:
+Subgraph'inizde değişiklik yaparken, ağırlıklı olarak üç dosya ile çalışacaksınız:
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+- Manifesto (`subgraph.yaml`): Subgraph'inizin hangi veri kaynaklarını endeksleyeceğini tanımlar.
+- Şema (`schema.graphql`): Subgraph'ten hangi veriyi almak istediğinizi tanımlar.
+- AssemblyScript Eşlemeleri (`mapping.ts`): Veri kaynaklarınızdan gelen veriyi şemada tanımlanan varlıklara dönüştürür.
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Subgraph yazımı hakkında ayrıntılı bilgi için [Subgraph Oluşturma](/developing/creating-a-subgraph/) sayfasına göz atın.
 
-## 5. Deploy to Subgraph Studio
+### 5. Subgraph'inizi yayına alın
+
+Unutmayın; yayına almak, yayımlamakla aynı şey değildir.
+
+Bir subgraph'i yayına aldığınızda, onu [Subgraph Studio](https://thegraph.com/studio/)'ya gönderirsiniz; burada subgraph'i test edebilir, yayına almaya hazırlayabilir ve inceleyebilirsiniz.
+
+Bir subgraph'i yayımladığınızda, onu merkeziyetsiz ağda, zincir üzerinde yayımlamış olursunuz.
 
 Subgraph'ınız yazıldıktan sonra aşağıdaki komutları çalıştırın:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Subgraph'inizi kimlik doğrulayıp yayına alın. Yayına alma anahtarını, Subgraph Studio'daki subgraph sayfasında bulabilirsiniz.
+
+![Yayına alma anahtarı](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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. Subgraph'inizi gözden geçirin
 
-- Subgraph'ınızı doğrulayın ve dağıtın. Dağıtım anahtarı Subgraph Stüdyo'daki Subgraph sayfasında bulunabilir.
+If you’d like to test your subgraph before publishing it, you can use [Subgraph Studio](https://thegraph.com/studio/) to do the following:
 
+- Örnek bir sorgu çalıştırabilirsiniz.
+- Subgraph'iniz hakkında bilgi kontrol etmek için kontrol panelini analiz edebilirsiniz.
+- Subgraph'inizde hata olup olmadığını görmek için kontrol panelindeki kayıtları kontrol edin. Çalışan bir subgraph'in kayıtları şu şekilde görünecektir:
+
+  ![Subgraph kayıtları](/img/subgraph-logs-image.png)
+
+### 7. Subgraph'inizi The Graph Ağında yayımlayın
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Subgraph Studio ile yayımlama
+
+Subgraph'inizi yayımlamak için, kontrol panelindeki Yayımla düğmesine tıklayın.
+
+![Publish a subgraph on Subgraph Studio](/img/publish-sub-transfer.png)
+
+Subgraph'inizi yayımlamak istediğiniz ağı seçin.
+
+#### CLI ile yayımlama
+
+Sürüm 0.73.0 itibarıyla, subgraph'inizi Graph CLI ile de yayımlayabilirsiniz.
+
+`graph-cli`yi açın.
+
+Şu komutları kullanın:
+
+````
 ```sh
-$ graph auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Subgraph'ınızı Test Edin
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-Kayıtlar, subgraph'ınızla ilgili herhangi bir hata olup olmadığını size söyleyecektir. Çalışan bir subgraph'ın kayıtları aşağıdaki gibi görünecektir:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+Then,
+
+```sh
+graph publish
 ```
+````
+
+3. Bir pencere açılacak, cüzdanınızı bağlayabilecek, meta verileri ekleyebilecek ve sonuçlandırılmış subgraph'inizi seçtiğiniz ağda yayımlayabileceksiniz.
+
+![cli-ui](/img/cli-ui.png)
+
+Yayımlamanızı özelleştirmek için, [Subgraph Yayımlama](/publishing/publishing-a-subgraph/) sayfasına göz atın.
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Subgraph'inize sinyal ekleme
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - Bu işlem, hizmet kalitesini artırır, gecikmeyi azaltır ve subgraph'inizin ağdaki yedekliliğini ve müsaitliğini artırır.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. Endeksleme ödüllerine hak kazanan Endeksleyiciler sinyal miktarına bağlı olarak GRT ödülü alırlar.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - En az 3 Endeksleyici çekmek için en az 3.000 GRT küratörlük yapmanız önerilir. Subgraph özelliği kullanımı ve desteklenen ağlara bağlı olarak ödül hak kazanımlarının nasıl dağıtıldığını kontrol edin.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+Küratörlük hakkında daha fazla bilgi için [Küratörlük](/network/curating/) sayfasını okuyun.
 
-Gas maliyetlerinden tasarruf etmek için, subgraph'ınızı Graph'ın merkeziyetsiz ağında yayınlarken bu düğmeyi seçerek subgraph'ınızı yayınladığınız işlemle aynı işlemde kürate edebilirsiniz:
+Gas maliyetlerinden tasarruf etmek için, subgraph'inizi küratörlük işlemini, yayımlama işlemiyle aynı anda yapabilirsiniz. Bunun için şu seçeneği seçin:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Subgraph'inizi sorgulama
 
-Şimdi, subgraph'ınızın Sorgu URL'sine GraphQL sorguları göndererek onu sorgulayabilirsiniz; bu URL'yi sorgu düğmesine tıklayarak bulabilirsiniz.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+Subgraph'inizden veri sorgulama hakkında daha fazla bilgi için [The Graph'e Sorgu Gönderme](/querying/querying-the-graph/) sayfasına bakın.

From bb669858de5e91d252f007aa1848249b142a0f92 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:18 -0500
Subject: [PATCH 0022/1325] New translations quick-start.mdx (Romanian)

---
 website/pages/ro/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/ro/quick-start.mdx b/website/pages/ro/quick-start.mdx
index cba2247457b8..429d4d51116f 100644
--- a/website/pages/ro/quick-start.mdx
+++ b/website/pages/ro/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Quick Start
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-This guide is written assuming that you have:
+## Prerequisites
 
 - A crypto wallet
-- A smart contract address on the network of your choice
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-When you initialize your subgraph, the CLI tool will ask you for the following information:
+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
-- Subgraph slug: create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: choose your local directory
-- 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 autopopulated, you will need to input it manually as a JSON file
-- Start Block: it is suggested that you input the start block to save time while your subgraph indexes blockchain data. You can locate the start block by finding the block where your contract was deployed.
-- 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
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-The previous commands create a scaffold subgraph that you can use as a starting point for building your subgraph. When making changes to the subgraph, you will mainly work with three files:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Once your subgraph is written, run the following commands:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Test your subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-The logs will tell you if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking on the query button.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 364a5e032eb6d69bafe714f83f5708e1e3feebdd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:19 -0500
Subject: [PATCH 0023/1325] New translations quick-start.mdx (French)

---
 website/pages/fr/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/fr/quick-start.mdx b/website/pages/fr/quick-start.mdx
index 25d4ae1f22c2..5759a2cb0dbb 100644
--- a/website/pages/fr/quick-start.mdx
+++ b/website/pages/fr/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Démarrage Rapide
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Assurez-vous que votre subgraph indexera les données d'un [réseau pris en charge] (/developing/supported-networks).
-
-Ce guide est rédigé en supposant que vous possédez :
+## Conditions préalables
 
 - Un portefeuille crypto
-- Une adresse de smart contract sur le réseau de votre choix
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Créez un subgraph sur Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Installez la CLI Graph
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Installez la CLI Graph
 
 Sur votre machine locale, exécutez l'une des commandes suivantes :
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 npm install -g @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Lorsque vous initialisez votre subgraph, l'outil CLI vous demande les informations suivantes :
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Protocole : choisissez le protocole à partir duquel votre subgraph indexera les données
-- Slug de subgraph : créez un nom pour votre subgraph. Votre slug de subgraph est un identifiant pour votre subgraph.
-- Répertoire dans lequel créer le subgraph : choisissez votre répertoire local
-- Réseau Ethereum (facultatif) : vous devrez peut-être spécifier à partir de quel réseau compatible EVM votre subgraph indexera les données
-- Adresse du contrat : localisez l'adresse du contrat intelligent à partir de laquelle vous souhaitez interroger les données
-- ABI : si l'ABI n'est pas renseigné automatiquement, vous devrez le saisir manuellement sous forme de fichier JSON
-- Bloc de démarrage : il est suggéré de saisir le bloc de démarrage pour gagner du temps pendant que votre subgraph indexe les données de la blockchain. Vous pouvez localiser le bloc de démarrage en recherchant le bloc dans lequel votre contrat a été déployé.
-- Nom du contrat : saisissez le nom de votre contrat
-- Indexer les événements de contrat en tant qu'entités : il est suggéré de définir cette valeur sur true car cela ajoutera automatiquement des mappages à votre subgraph pour chaque événement émis
-- Ajouter un autre contrat (facultatif) : vous pouvez ajouter un autre contrat
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 La capture d'écran suivante donne un exemple de ce qui vous attend lors de l'initialisation de votre subgraph :
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-Les commandes précédentes créent un subgraph d'échafaudage que vous pouvez utiliser comme point de départ pour construire votre propre subgraph. Lorsque vous apporterez des modifications au subgraph, vous travaillerez principalement avec trois fichiers :
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Déployer votre subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+N'oubliez pas que déployer n'est pas la même chose que publier.
 
-## 5. Deploy to Subgraph Studio
+Lorsque vous déployez un subgraph, vous le poussez vers [Subgraph Studio](https://thegraph.com/studio/), où vous pouvez le tester, le mettre en scène/préproduction et l'examiner.
+
+Lorsque vous publiez un subgraph, vous le publiez sur la blockchain vers le réseau décentralisé.
 
 Une fois votre subgraph écrit, exécutez les commandes suivantes :
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authentifiez-vous et déployez votre subgraph. La clé de déploiement se trouve sur la page du subgraph dans Subgraph Studio.
+
+![Clé de déploiement](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Authentifiez et déployez votre subgraph. La clé de déploiement se trouve sur la page du subgraph dans Subgraph Studio.
+### 6. Examiner votre 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:
+
+- Exécuter un exemple de requête.
+- Analyser votre subgraph dans le tableau de bord pour vérifier les informations.
+- Vérifier les logs sur le tableau de bord pour voir si des erreurs surviennent avec votre subgraph. Les logs d'un subgraph opérationnel ressembleront à ceci :
+
+  ![Logs du subgraph](/img/subgraph-logs-image.png)
+
+### 7. Publier votre subgraph sur The Graph Network⁠
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publier avec Subgraph Studio⁠
+
+Pour publier votre subgraph, cliquez sur le bouton "Publish" dans le tableau de bord.
+
+![Publish a subgraph on Subgraph Studio](/img/publish-sub-transfer.png)
+
+Sélectionnez le réseau sur lequel vous souhaitez publier votre subgraph.
+
+#### Publication avec l'Interface en Ligne de Commande (CLI)
+
+À partir de la version 0.73.0, vous pouvez également publier votre subgraph avec Graph CLI.
+
+Ouvrez le `graph-cli`.
+
+Utilisez les commandes suivantes :
+
+````
 ```sh
-$ graph auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Testez votre subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-Les registres ou logs vous indiqueront s'il y a des erreurs avec votre subgraph. Les logs d'un subgraph opérationnel ressembleront à ceci :
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+Then,
+
+```sh
+graph publish
 ```
+````
+
+3. Une fenêtre s'ouvrira, vous permettant de connecter votre portefeuille, d'ajouter des métadonnées et de déployer votre subgraph final sur un réseau de votre choix.
+
+![cli-ui](/img/cli-ui.png)
+
+Pour personnaliser votre déploiement, consultez [Publication d'un Subgraph](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Ajouter un signal à votre subgraph⁠
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - Cette action améliore la qualité du service, réduit la latence et renforce la redondance et la disponibilité du réseau pour votre subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. Si éligibles aux récompenses d'indexation, les Indexeurs reçoivent des récompenses en GRT proportionnelles au montant signalé.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - Il est recommandé de curer au moins 3 000 GRT pour attirer 3 Indexeurs. Vérifiez l'éligibilité aux récompenses en fonction de l'utilisation des fonctionnalités du subgraph et des réseaux supportés.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+Pour en savoir plus sur la curation, lisez [Curation](/network/curating/).
 
-Pour économiser sur les coûts de gaz, vous pouvez organiser votre subgraph dans la même transaction que celle où vous l'avez publié en sélectionnant ce bouton lorsque vous publiez votre subgraph sur le réseau décentralisé de The Graph :
+Pour économiser sur les frais de gas, vous pouvez curer votre subgraph dans la même transaction que celle où vous le publiez en sélectionnant cette option :
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Interroger votre subgraph
 
-Désormais, vous pouvez interroger votre subgraph en envoyant des requêtes GraphQL à l'URL de requête de votre subgraph, que vous pouvez trouver en cliquant sur le bouton de requête.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+Pour plus d'informations sur l'interrogation des données de votre subgraph, lisez [Interroger The Graph](/querying/querying-the-graph/).

From faa9bb49ac0d53eb47f119367c6b683da89fd8d4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:20 -0500
Subject: [PATCH 0024/1325] New translations quick-start.mdx (Spanish)

---
 website/pages/es/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/es/quick-start.mdx b/website/pages/es/quick-start.mdx
index b0765ca7fd36..f7c62e51c1f0 100644
--- a/website/pages/es/quick-start.mdx
+++ b/website/pages/es/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Comienzo Rapido
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-Esta guía está escrita asumiendo que tú tienes:
+## Prerrequisitos
 
 - Una wallet crypto
-- Una dirección de un smart contract en la red de tu preferencia
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Crea un subgrafo en el Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Instala the graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Instala the graph CLI
 
 En tu dispositivo, ejecuta alguno de los siguientes comandos:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Cuando inicies tu subgrafo, la herramienta CLI te preguntará por la siguiente información:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Protocol: elige el protocolo desde el cual tu subgrafo indexará datos
-- Subgraph slug: crea un nombre para tu subgrafo. El slug de tu subgrafo es un identificador para el mismo.
-- Directorio para crear el subgrafo: elige el directorio local de tu elección
-- Red Ethereum (opcional): Es posible que debas especificar desde qué red compatible con EVM tu subgrafo indexará datos
-- Dirección del contrato: Localiza la dirección del contrato inteligente del que deseas consultar los datos
-- ABI: Si el ABI no se completa automáticamente, deberás ingresar los datos manualmente en formato JSON
-- Start Block: se sugiere que ingreses el bloque de inicio para ahorrar tiempo mientras tu subgrafo indexa los datos de la blockchain. Puedes ubicar el bloque de inicio encontrando el bloque en el que se deployó tu contrato.
-- Nombre del contrato: introduce el nombre de tu contrato
-- Indexar eventos del contrato como entidades: se sugiere que lo establezcas en "verdadero" ya que automáticamente agregará mapeos a tu subgrafo para cada evento emitido
-- Añade otro contrato(opcional): puedes añadir otro contrato
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 Ve la siguiente captura para un ejemplo de que debes de esperar cuando inicializes tu subgrafo:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-Los comandos anteriores crean un subgrafo de andamio que puedes utilizar como punto de partida para construir tu subgrafo. Al realizar cambios en el subgrafo, trabajarás principalmente con tres archivos:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Una vez escrito tu subgrafo, ejecuta los siguientes comandos:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Autentica y deploya tu subgrafo. La clave para deployar se puede encontrar en la página de Subgraph en Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Prueba tu subgrafo
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-Los registros te indicarán si hay algún error con tu subgrafo. Los registros de un subgrafo operativo se verán así:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-Para ahorrar en costos de gas, puedes curar tu subgrafo en la misma transacción en la que lo publicas seleccionando este botón al publicar tu subgrafo en la red descentralizada de The Graph:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Ahora puedes hacer consultas a tu subgrafo enviando consultas GraphQL a la URL de consulta de tu subgrafo, que puedes encontrar haciendo clic en el botón de consulta.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From b544908b89d5816a33a00c5fbef7532dc9bdb7cc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:21 -0500
Subject: [PATCH 0025/1325] New translations quick-start.mdx (Arabic)

---
 website/pages/ar/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/ar/quick-start.mdx b/website/pages/ar/quick-start.mdx
index f510c6ba381d..8a52663bfc8c 100644
--- a/website/pages/ar/quick-start.mdx
+++ b/website/pages/ar/quick-start.mdx
@@ -2,24 +2,26 @@
 title: بداية سريعة
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-تأكد من أن الغراف الفرعي الخاص بك سيقوم بفهرسة البيانات من [الشبكة المدعومة](/developing/supported-networks).
-
-تم كتابة هذا الدليل على افتراض أن لديك:
+## المتطلبات الأساسية
 
 - محفظة عملات رقمية
-- عنوان عقد ذكي على الشبكة التي تختارها
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-انتقل إلى [سبغراف استوديو] (https://thegraph.com/studio) وقم بربط محفظتك.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> يمكنك العثور على الأوامر المتعلقة بالغراف الفرعي الخاص بك على صفحة الغراف الفرعي في (سبغراف استوديو) (https://thegraph.com/studio).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> يمكنك العثور على الأوامر المتعلقة بالغراف الفرعي الخاص بك على صفحة الغراف الفرعي في (سبغراف استوديو) (https://thegraph.com/studio).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-عند تهيئة غرافك الفرعي، ستطلب منك أداة "واجهة سطر الأوامر" (CLI) المعلومات التالية:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- البروتوكول: اختر البروتوكول الذي سيفهرس من فهرسة البيانات
-- المعرّف الخاص بالغراف الفرعي: قم بإنشاء اسم لغرافك الغرعي. يُعتبر "سبغراف سلوج" معرّف فريد يستخدم لتمييز غرافك الفرعي.
-- الدليل الذي سيتم إنشاء الغراف الفرعي فيه: اختر الدليل المحلي الذي ترغب في إنشاء الغراف الفرعي فيه
-- شبكة الايثيروم(اختيارية): قد تحتاج إلى تحديد الشبكة المتوافقة مع آلة إيثيريوم الإفتراضية التي سيقوم غرافك الفرعي بفهرسة البيانات منها
-- Contract address: Locate the smart contract address you’d like to query data from
-- واجهة التطبيق الثنائية: إذا لم يتم ملء واجهة التطبيق الثنائية تلقائياً، فستحتاج إلى إدخاله يدوياً كملف JSON
-- كتلة البداية: يُقترح إدخال كتلة البداية لتوفير الوقت أثناء قيام غرافك الفرعي بفهرسة بيانات سلاسل الكتل. يمكنك تحديد كتلة البداية من خلال العثور على الكتلة التي تم نشر عقدك فيها.
-- Contract Name: input the name of your contract
-- فهرسة أحداث العقد ككيانات: يُقترح ضبط هذا الخيار على "صحيح" (True) حيث سيتم إضافة تعيينات تلقائية إلى غرافك الفرعي لكل حدث يتم إصداره
-- إضافة عقد آخر (اختياري): يمكنك إضافة عقد آخر
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 يرجى مراجعة الصورة المرفقة كمثال عن ما يمكن توقعه عند تهيئة غرافك الفرعي:
 
-أمر الغراف الفرعي(/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-الأوامر السابقة تنشئ هيكل غرافك الفرعي والذي يمكنك استخدامه كنقطة بداية لبناء غرافك الفرعي. عند إجراء تغييرات على الغراف الفرعي، ستعمل بشكل رئيسي مع ثلاثة ملفات:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-للمزيد من المعلومات حول كيفية كتابة غرافك الفرعي، يُرجى الاطلاع على إنشاء غراف فرعي(/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 عند كتابة غرافك الفرعي، قم بتنفيذ الأوامر التالية:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. اختبر غرافك الفرعي
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-ستخبرك السجلات إذا كانت هناك أي أخطاء في غرافك الفرعي. ستبدو سجلات الغراف الفرعي الفعّال على النحو التالي:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-إذا فشل غرافك الفرعي، فيمكنك الاستعلام عن صحة الغراف الفرعي باستخدام ملعب غرافي GraphiQL Playground. لاحظ أنه يمكنك الاستفادة من الاستعلام أدناه وإدخال معرف النشر الخاص بك لغرافك الفرعي. في هذه الحالة، `Qm...` هو معرف النشر (يمكن العثور عليه في صفحة الغراف الفرعي ضمن **التفاصيل**). سيخبرك الاستعلام أدناه عند فشل الغراف الفرعي حتى تتمكن من إصلاحه بناءً عليه:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-حدد الشبكة التي ترغب في نشر غرافك الفرعي عليها. يُوصى بنشر الغرافات الفرعية على شبكة أربترم ون للاستفادة من [سرعة معاملات أسرع وتكاليف غاز أقل](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-لتوفير تكاليف الغاز، يمكنك تنسيق غرافك الفرعي في نفس العملية التي نشرته عن طريق اختيار هذا الزر عند نشر غرافك الفرعي على شبكة الغراف اللامركزية:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-الآن يمكنك الاستعلام عن غرافك الفرعي عن طريق إرسال استعلامات لغة GraphQL إلى عنوان استعلامات غرافك الفرعي URL والذي يمكنك أن تجده عن طريق النقر على زر الاستعلام.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 7e71ff68872e8206ff67b3ffce41c579e55bb84e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:22 -0500
Subject: [PATCH 0026/1325] New translations quick-start.mdx (Czech)

---
 website/pages/cs/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/cs/quick-start.mdx b/website/pages/cs/quick-start.mdx
index 458443a8e3dd..a9a090bca4d6 100644
--- a/website/pages/cs/quick-start.mdx
+++ b/website/pages/cs/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Rychlé Začít
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ujistěte se, že váš podgraf bude indexovat data z [podporované sítě](/developing/supported-networks).
-
-Tato příručka je napsána za předpokladu, že máte:
+## Požadavky
 
 - Kryptopeněženka
-- Adresa chytrého kontraktu v síti podle vašeho výběru
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Vytvoření podgrafu v Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Přejděte do [Subgraph Studio](https://thegraph.com/studio/) a připojte peněženku.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Nainstalujte Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Nainstalujte Graph CLI
 
 V místním počítači spusťte jeden z následujících příkazů:
 
@@ -35,133 +37,148 @@ Použitím [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> Příkazy pro konkrétní podgraf najdete na stránce podgrafu v [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> Příkazy pro konkrétní podgraf najdete na stránce podgrafu v [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Při inicializaci podgrafu vás nástroj CLI požádá o následující informace:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Protokol: vyberte protokol, ze kterého bude váš podgraf indexovat data.
-- Slug podgrafu: vytvořte název podgrafu. Váš podgraf slug je identifikátor vašeho podgrafu.
-- Adresář pro vytvoření podgrafu: vyberte místní adresář.
-- Ethereum síť (nepovinné): možná budete muset zadat, ze které sítě kompatibilní s EVM bude váš subgraf indexovat data.
-- Adresa zakázky: Vyhledejte adresu chytré smlouvy, ze které se chcete dotazovat na data.
-- ABI: Pokud se ABI nevyplňuje automaticky, je třeba jej zadat ručně jako soubor JSON.
-- Počáteční blok: Doporučuje se zadat počáteční blok, abyste ušetřili čas, zatímco váš subgraf indexuje data blockchainu. Počáteční blok můžete vyhledat tak, že najdete blok, ve kterém byl váš kontrakt nasazen.
-- Název smlouvy: zadejte název své smlouvy.
-- Indexovat události smlouvy jako entity: doporučujeme nastavit tuto hodnotu na true, protože se automaticky přidá mapování do vašeho subgrafu pro každou emitovanou událost
-- Přidat další smlouvu(nepovinné): můžete přidat další smlouvu
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 Na následujícím snímku najdete příklad toho, co můžete očekávat při inicializaci podgrafu:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-Předchozí příkazy vytvořily podgraf lešení, který můžete použít jako výchozí bod pro sestavení podgrafu. Při provádění změn v podgrafu budete pracovat především se třemi soubory:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - Manifest definuje, jaké datové zdroje budou vaše podgrafy indexovat.
-- Schéma (`schema.graphql`) - Schéma GraphQL definuje, jaká data chcete z podgrafu získat.
-- AssemblyScript Mapování (`mapping.ts`) - Jedná se o kód, který převádí data z vašich datových zdrojů na entity definované ve schématu.
+### 5. Deploy your subgraph
 
-Další informace o zápisu podgrafu naleznete v části [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Jakmile je podgraf napsán, spusťte následující příkazy:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Ověřte a nasaďte svůj podgraf. Klíč k nasazení najdete na stránce Subgraph ve Studiu Subgraph.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-Budete vyzváni k zadání štítku verze. Důrazně se doporučuje použít [semver](https://semver.org/) pro označení verzí jako `0.0.1`. Přesto můžete jako verzi zvolit libovolný řetězec, například:`v1`, `version1`, `asdf`.
-
-## 6. Otestujte svůj podgraf
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-V protokolech se dozvíte, zda se v podgrafu vyskytly nějaké chyby. Protokoly funkčního podgrafu budou vypadat takto:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-Pokud podgraf selhává, můžete se na stav podgrafu zeptat pomocí nástroje GraphiQL Playground. Všimněte si, že můžete využít níže uvedený dotaz a zadat ID nasazení vašeho podgrafu. V tomto případě je `Qm...` ID nasazení (které najdete na stránce podgrafu v části **Podrobnosti**). Níže uvedený dotaz vás informuje o selhání podgrafu, takže můžete podle toho provádět ladění:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Přidání signálu do podgrafu
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Vyberte síť, do které chcete podgraf publikovat. Doporučujeme publikovat podgrafy do sítě Arbitrum One, abyste mohli využít výhod [vyšší rychlost transakcí a nižší náklady na plyn](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-Pro vyšší kvalitu služeb a silnější redundanci můžete svůj podgraf upravit tak, aby přilákal více indexátorů. V době psaní tohoto článku je doporučeno, abyste svůj podgraf kurátorovali s alespoň 3,000 GRT, abyste zajistili, že 3-5 dalších Indexerů začne obsluhovat dotazy na vašem podgrafu.
+To learn more about curation, read [Curating](/network/curating/).
 
-Abyste ušetřili náklady na benzín, můžete svůj subgraf kurátorovat ve stejné transakci, v níž jste ho publikovali, a to výběrem tohoto tlačítka při publikování subgrafu do decentralizované sítě The Graph:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Nyní se můžete dotazovat na svůj podgraf odesláním dotazů GraphQL na adresu URL dotazu podgrafu, kterou najdete kliknutím na tlačítko dotazu.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-Další informace o dotazování na data z podgrafu najdete [zde](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 050b821a5c5885429d75e62b28b40b897576a49d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:23 -0500
Subject: [PATCH 0027/1325] New translations quick-start.mdx (Italian)

---
 website/pages/it/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/it/quick-start.mdx b/website/pages/it/quick-start.mdx
index cba2247457b8..429d4d51116f 100644
--- a/website/pages/it/quick-start.mdx
+++ b/website/pages/it/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Quick Start
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-This guide is written assuming that you have:
+## Prerequisites
 
 - A crypto wallet
-- A smart contract address on the network of your choice
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-When you initialize your subgraph, the CLI tool will ask you for the following information:
+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
-- Subgraph slug: create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: choose your local directory
-- 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 autopopulated, you will need to input it manually as a JSON file
-- Start Block: it is suggested that you input the start block to save time while your subgraph indexes blockchain data. You can locate the start block by finding the block where your contract was deployed.
-- 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
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-The previous commands create a scaffold subgraph that you can use as a starting point for building your subgraph. When making changes to the subgraph, you will mainly work with three files:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Once your subgraph is written, run the following commands:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Test your subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-The logs will tell you if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking on the query button.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 73287e935d93a807241def15eba8abd6543c554d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:24 -0500
Subject: [PATCH 0028/1325] New translations quick-start.mdx (Japanese)

---
 website/pages/ja/quick-start.mdx | 220 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 101 deletions(-)

diff --git a/website/pages/ja/quick-start.mdx b/website/pages/ja/quick-start.mdx
index 987d081a1d94..618252856359 100644
--- a/website/pages/ja/quick-start.mdx
+++ b/website/pages/ja/quick-start.mdx
@@ -2,24 +2,26 @@
 title: クイックスタート
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-サブグラフが [supported network](/developing/supported-networks) からのデータにインデックスを付けることを確認してください。
-
-このガイドは、次のことを前提として書かれています。
+## 前提条件
 
 - クリプトウォレット
-- 選択したネットワーク上のスマート コントラクト アドレス
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Subgraph Studio でサブグラフを作成する
+### 1. Create a subgraph in Subgraph Studio
 
-[Subgraph Studio](https://thegraph.com/studio/)にアクセスし、ウォレットを接続する。
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Graph CLI をインストールする
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Graph CLI をインストールする
 
 ローカル マシンで、次のいずれかのコマンドを実行します。
 
@@ -35,132 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> 特定のサブグラフのコマンドは、[Subgraph Studio](https://thegraph.com/studio/) のサブグラフ ページで見つけることができます。
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> 特定のサブグラフのコマンドは、[Subgraph Studio](https://thegraph.com/studio/) のサブグラフ ページで見つけることができます。
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-サブグラフを初期化すると、CLI ツールは次の情報を要求します。
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- プロトコル: サブグラフがデータのインデックスを作成するプロトコルを選択します
-- サブグラフ スラッグ: サブグラフの名前を作成します。サブグラフ スラッグは、サブグラフの識別子です。
-- サブグラフを作成するディレクトリ: ローカル ディレクトリを選択します
-- Ethereum ネットワーク (オプション): サブグラフがデータのインデックスを作成する EVM 互換ネットワークを指定する必要がある場合があります。
-- コントラクト アドレス: データを照会するスマート コントラクト アドレスを見つけます。
-- ABI: ABI が自動入力されない場合は、JSON ファイルとして手動で入力する必要があります
-- 開始ブロック: サブグラフがブロックチェーン データをインデックス化する間、時間を節約するために開始ブロックを入力することをお勧めします。コントラクトが展開されたブロックを見つけることで、開始ブロックを見つけることができます。
-- 契約名: 契約の名前を入力します
-- コントラクト イベントをエンティティとしてインデックス付けする: これを true に設定することをお勧めします。発行されたすべてのイベントのサブグラフにマッピングが自動的に追加されるためです。
-- 別の契約を追加 (オプション): 別の契約を追加できます
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 サブグラフを初期化する際に予想されることの例については、次のスクリーンショットを参照してください。
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-前述のコマンドでは、サブグラフを作成するための出発点として使用できる scaffold サブグラフを作成します。 サブグラフに変更を加える際には、主に 3 つのファイルを使用します:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 サブグラフが作成されたら、次のコマンドを実行します。
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- サブグラフの認証とデプロイを行います。 デプロイキーは、Subgraph Studio の Subgraph ページにあります。
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-バージョンラベルの入力を求められます。 「0.0.1」のようなバージョン管理には [semver](https://semver.org/) を使用することを強くお勧めします。 つまり、「v1」、「version1」、「asdf」などの任意の文字列をバージョンとして自由に選択できます。
-
-## 6. サブグラフをテストする
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-ログは、サブグラフにエラーがあるかどうかを示します。運用サブグラフのログは次のようになります。
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-サブグラフに障害が発生した場合は、GraphiQL Playground を使用してサブグラフの健全性をクエリできます。 以下のクエリを利用して、サブグラフのデプロイメント ID を入力できることに注意してください。 この場合、`Qm...` はデプロイメント ID です (これは、サブグラフ ページの **詳細** にあります)。 以下のクエリはサブグラフがいつ失敗したかを通知するため、それに応じてデバッグできます。
-
-```graphql
-{
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-サブグラフを公開したいネットワークを選択します。 [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq) を利用するために、サブグラフを Arbitrum One に公開することをお勧めします。
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-ガスのコストを節約するために、サブグラフを The Graph の分散型ネットワークに公開するときにこのボタンを選択すると、公開したのと同じトランザクションでサブグラフをキュレートできます。
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-これで、GraphQL クエリをサブグラフのクエリ URL に送信することで、サブグラフにクエリを実行できます。これは、クエリ ボタンをクリックして見つけることができます。
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-サブグラフからデータをクエリする方法については、[こちら](/querying/querying-the-graph/)を参照してください。
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From e111009961dfdc4ef650abb4fd1d62cc4616afac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:25 -0500
Subject: [PATCH 0029/1325] New translations quick-start.mdx (Korean)

---
 website/pages/ko/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/ko/quick-start.mdx b/website/pages/ko/quick-start.mdx
index cba2247457b8..429d4d51116f 100644
--- a/website/pages/ko/quick-start.mdx
+++ b/website/pages/ko/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Quick Start
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-This guide is written assuming that you have:
+## Prerequisites
 
 - A crypto wallet
-- A smart contract address on the network of your choice
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-When you initialize your subgraph, the CLI tool will ask you for the following information:
+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
-- Subgraph slug: create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: choose your local directory
-- 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 autopopulated, you will need to input it manually as a JSON file
-- Start Block: it is suggested that you input the start block to save time while your subgraph indexes blockchain data. You can locate the start block by finding the block where your contract was deployed.
-- 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
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-The previous commands create a scaffold subgraph that you can use as a starting point for building your subgraph. When making changes to the subgraph, you will mainly work with three files:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Once your subgraph is written, run the following commands:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Test your subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-The logs will tell you if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking on the query button.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 3315f4368f22d37194a32624d338abe8ae90b2dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:26 -0500
Subject: [PATCH 0030/1325] New translations quick-start.mdx (Dutch)

---
 website/pages/nl/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/nl/quick-start.mdx b/website/pages/nl/quick-start.mdx
index 0d0c1c067ba6..671df69b7c30 100644
--- a/website/pages/nl/quick-start.mdx
+++ b/website/pages/nl/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Snelle Start
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-This guide is written assuming that you have:
+## Prerequisites
 
 - A crypto wallet
-- A smart contract address on the network of your choice
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-When you initialize your subgraph, the CLI tool will ask you for the following information:
+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
-- Subgraph slug: create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: choose your local directory
-- 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 autopopulated, you will need to input it manually as a JSON file
-- Start Block: it is suggested that you input the start block to save time while your subgraph indexes blockchain data. You can locate the start block by finding the block where your contract was deployed.
-- 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
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-The previous commands create a scaffold subgraph that you can use as a starting point for building your subgraph. When making changes to the subgraph, you will mainly work with three files:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Once your subgraph is written, run the following commands:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Test your subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-The logs will tell you if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking on the query button.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 7ba0c9f52e7d78855737ea4c31d486f37a4970d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:27 -0500
Subject: [PATCH 0031/1325] New translations quick-start.mdx (Polish)

---
 website/pages/pl/quick-start.mdx | 223 +++++++++++++++++--------------
 1 file changed, 120 insertions(+), 103 deletions(-)

diff --git a/website/pages/pl/quick-start.mdx b/website/pages/pl/quick-start.mdx
index 522fd48fbb07..9a4ebfc960d3 100644
--- a/website/pages/pl/quick-start.mdx
+++ b/website/pages/pl/quick-start.mdx
@@ -1,25 +1,27 @@
 ---
-title: ' Na start'
+title: " Na start"
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-This guide is written assuming that you have:
+## Prerequisites
 
 - A crypto wallet
-- A smart contract address on the network of your choice
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-When you initialize your subgraph, the CLI tool will ask you for the following information:
+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
-- Subgraph slug: create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: choose your local directory
-- 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 autopopulated, you will need to input it manually as a JSON file
-- Start Block: it is suggested that you input the start block to save time while your subgraph indexes blockchain data. You can locate the start block by finding the block where your contract was deployed.
-- 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
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-The previous commands create a scaffold subgraph that you can use as a starting point for building your subgraph. When making changes to the subgraph, you will mainly work with three files:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Once your subgraph is written, run the following commands:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Authenticate and deploy your subgraph. The deploy key can be found on the Subgraph page in Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Test your subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-The logs will tell you if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking on the query button.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 7cd400b1912ef137b3a11a87d0f0e6f4dd6fdc4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:28 -0500
Subject: [PATCH 0032/1325] New translations quick-start.mdx (Portuguese)

---
 website/pages/pt/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/pt/quick-start.mdx b/website/pages/pt/quick-start.mdx
index 54befd3e6949..b84ba0083d5f 100644
--- a/website/pages/pt/quick-start.mdx
+++ b/website/pages/pt/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Começo Rápido
 ---
 
-Este guia explicará rapidamente como inicializar, criar, e lançar o seu subgraph ao Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Garanta que o seu subgraph indexará dados de uma [rede apoiada](/developing/supported-networks).
-
-Este guia presume que tem:
+## Pré-requisitos
 
 - Uma carteira de criptomoedas
-- Um endereço de contrato inteligente na rede da sua escolha
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Como criar um subgraph no Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Entre no [Subgraph Studio](https://thegraph.com/studio/) e conecte a sua carteira de criptomoedas.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Quando a sua carteira estiver conectada, clique em "Criar um Subgraph". Vale nomear o subgraph em Title Case: "Nome Do Subgraph Nome Da Chain."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Como instalar a Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-A Graph CLI é escrita em TypeScript e precisa ter instalado o `node`, e `npm` ou `yarn` para ser isada. Verifique se tem a versão mais recente da CLI instalada.
+### 2. Como instalar o Graph CLI
 
 Execute um dos seguintes comandos na sua máquina local:
 
@@ -35,133 +37,148 @@ Uso de [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Como inicializar o seu subgraph de um contrato existente
+### 3. Initialize your subgraph
+
+> Veja comandos para o seu subgraph específico na página do subgraph no [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Inicialize o seu subgraph a partir de um contrato existente ao executar o comando initialize:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> Veja comandos para o seu subgraph específico na página do subgraph no [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Ao inicializar o seu subgraph, a ferramenta CLI pedirá pelas seguintes informações:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Protocolo: Escolha o protocolo do qual o subgraph indexará dados
-- Slug do subgraph: crie um nome para o seu subgraph. O slug serve como uma identidade para o seu subgraph.
-- Diretório onde o subgraph será criado: escolha o seu diretório local
-- 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 consultar dados
-- ABI: 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 lançado.
-- Nome do Contrato: insira o nome do seu contrato
-- Indexar eventos de contrato como entidades: é sugerido configurar isto como true, já que ele automaticamente adicionará mapeamentos ao seu subgraph para cada evento emitido
-- Adicionar outro contrato (opcional): adicionar outro contrato
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 Veja a imagem a seguir para um exemplo do que esperar quando for inicializar o seu subgraph:
 
-![Comando do subgraph](/img/subgraph-init-example.png)
+![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:
 
-## 4. Como escrever o seu subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-O comando interior cria um subgraph de altura que pode ser usado como ponto de partida para construir o seu subgraph. Enquanto faz mudanças ao subgraph, trabalhará principalmente com três arquivos:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - O manifest define quais fontes de dados serão indexadas pelos seus subgraphs.
-- Schema (`schema.graphql`) - O schema GraphQL define quais dados deseja retirar do subgraph.
-- Mapeamentos em AssemblyScript (`mapping.ts`) — Este é o código que traduz dados das suas fontes de dados às entidades definidas no schema.
+### 5. Deploy your subgraph
 
-Para mais informações sobre como escrever o seu subgraph, veja [Como Criar um Subgraph](/desenvolvimento/como-criar-um-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Lançamento no Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Quando o seu subgraph estiver escrito, execute os seguintes comandos:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Autentique e lance o seu subgraph. A chave de lançamento (deploy key) pode ser encontrada na página "Subgraph" do Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Logs do subgraph](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![Publish a subgraph on Subgraph Studio](/img/publish-sub-transfer.png)
+
+Select the network to which you would like to publish your subgraph.
+
+#### Publicação da 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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-Há de inserir um rótulo de versão. É altamente recomendado usar o [semver](https://semver.org/) para números de versão, como `0.0.1`. Dito isto, dá para escolher qualquer string como versão, por exemplo: `v1`, `version1`, `asdf`.
-
-## 6. Como testar o seu subgraph
-
-No ambiente de testes do Subgraph Studio, é possível testar o seu subgraph ao fazer uma query de exemplo.
-
-Os logs dirão-lhe se há quaisquer erros com o seu subgraph. Os logs de um subgraph operacional parecerão com isto:
-
-![Logs do subgraph](/img/subgraph-logs-image.png)
-
-Se o seu subgraph continuar a falhar, faça um query sobre a saúde do subgraph com o GraphiQL Playground. Perceba que dá para usar o query abaixo e inserir sua ID de lançamento para seu subgraph. Neste caso, `Qm...` é a ID de lançamento (na página Subgraph sob **Detalhes**). O texto abaixo te dirá quando um subgraph falha para que você possa fazer o debug de acordo:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+Then,
+
+```sh
+graph publish
 ```
+````
+
+3. Uma janela será aberta para o programador conectar a sua carteira, adicionar metadados e lançar o seu subgraph finalizado a uma rede de sua escolha.
+
+![cli-ui](/img/cli-ui.png)
+
+To customize your deployment, see [Publishing a Subgraph](/publishing/publishing-a-subgraph/).
 
-## 7. Como Editar o Seu Subgraph na Rede Descentralizada do The Graph
+#### Como adicionar sinal ao seu subgraph
 
-Quando o seu subgraph for lançado ao Subgraph Studio, estiver testado, e estiver pronto para produção, poderá então editá-lo na rede descentralizada.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-No Subgraph Studio, será possível clicar no botão de editar no canto superior direito da página do seu subgraph.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Selecione a rede onde quer editar o seu subgraph. Vale editar subgraphs no Arbitrum One, para aproveitar as [transações mais rápidas e custos menores de gas](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-O (Indexador de atualização)[/sunrise/#about-the-upgrade-indexer] começará a servir queries no seu subgraph independente da curadoria dele, e fornecerá 100 mil queries grátis por mês.
+   - 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.
 
-Para uma qualidade maior de serviço e redundâncias mais fortes, é possível curar o seu subgraph para atrair mais Indexadores. Na hora da criação deste artigo, é recomendado curar o seu próprio subgraph com, no mínimo, 3.000 GRT para garantir que 3 a 5 Indexadores a mais comecem a servir queries no seu subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-Para poupar custos de gas, cure o seu subgraph na mesma transação em que ele foi publicado, ao selecionar este botão quando publicar o seu subgraph na rede descentralizada do The Graph:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Editar subgraph](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Queries no seu subgraph
+### 8. Queries no seu subgraph
 
-Agora, podes consultar o seu subgraph com o envio de queries GraphQL para o URL de Query do seu subgraph, que pode ser visto ao clicar no botão Query.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-Se não tiver a sua chave API, é possível fazer queries via o URL de query de desenvolvimento com limite de ritmo, que pode ser usado para desenvolvimento e encenações.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-Para mais informações sobre queries de dados do seu subgraph, leia mais [aqui](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From c381be96fe470ff2da75a9061e241d57136d339b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:29 -0500
Subject: [PATCH 0033/1325] New translations common-issues.mdx (Russian)

---
 website/pages/ru/developing/graph-ts/common-issues.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ru/developing/graph-ts/common-issues.mdx b/website/pages/ru/developing/graph-ts/common-issues.mdx
index 127d5d70548f..a07a63600785 100644
--- a/website/pages/ru/developing/graph-ts/common-issues.mdx
+++ b/website/pages/ru/developing/graph-ts/common-issues.mdx
@@ -2,7 +2,7 @@
 title: Распространенные проблемы с AssemblyScript
 ---
 
-There are certain [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) issues that are common to run into during subgraph development. They range in debug difficulty, however, being aware of them may help. The following is a non-exhaustive list of these issues:
+Существуют определенные проблемы c [AssemblyScript] (https://github.com/AssemblyScript/assemblyscript), с которыми часто приходится сталкиваться при разработке субграфа. Они различаются по сложности отладки, однако знание о них может помочь. Ниже приведен неполный перечень этих проблем:
 
-- `Private` class variables are not enforced in [AssembyScript](https://www.assemblyscript.org/status.html#language-features). There is no way to protect class variables from being directly changed from the class object.
-- Scope is not inherited into [closure functions](https://www.assemblyscript.org/status.html#on-closures), i.e. variables declared outside of closure functions cannot be used. Explanation in [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s).
+- `Переменные класса `Private\` не применяются в [AssembyScript](https://www.assemblyscript.org/status.html#language-features). Невозможно защитить переменные класса от непосредственного изменения из объекта класса.
+- Область видимости не наследуется [функциями замыкания](https://www.assemblyscript.org/status.html#on-closures), т.е. переменные, объявленные вне функций замыкания, не могут быть использованы. Пояснения см. в [Рекомендациях для разработчиков #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s).

From 5153533bb4dcca9891f27f8fb70e48d17c5adcd1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:31 -0500
Subject: [PATCH 0034/1325] New translations api.mdx (Russian)

---
 website/pages/ru/developing/graph-ts/api.mdx | 475 ++++++++++---------
 1 file changed, 243 insertions(+), 232 deletions(-)

diff --git a/website/pages/ru/developing/graph-ts/api.mdx b/website/pages/ru/developing/graph-ts/api.mdx
index b661a7f7b048..b5a90b9930fb 100644
--- a/website/pages/ru/developing/graph-ts/api.mdx
+++ b/website/pages/ru/developing/graph-ts/api.mdx
@@ -2,47 +2,49 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Примечание: Если Вы создали субграф до версии `graph-cli`/`graph-ts` 0.22.0`, значит, Вы используете более старую версию AssemblyScript. Рекомендуется ознакомиться с [`Руководством по миграции\`](/release-notes/assemblyscript-migration-guide).
 
-На этой странице описаны встроенные API, которые можно использовать при написании мэппингов субграфов. По умолчанию доступны два вида API:
+Узнайте, какие встроенные API можно использовать при написании мэппингов субграфов. По умолчанию доступны два типа API:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- [Библиотека The Graph TypeScript](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Код, сгенерированный из файлов субграфов с помощью `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+Вы также можете добавлять другие библиотеки в качестве зависимостей, если они совместимы с [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Поскольку мэппинги языков написаны на AssemblyScript, полезно ознакомиться с функциями языка и стандартной библиотеки на [вики-странице AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Референс API
 
-The `@graphprotocol/graph-ts` library provides the following APIs:
+Библиотека `@graphprotocol/graph-ts` предоставляет следующие API:
 
-- An `ethereum` API for working with Ethereum smart contracts, events, blocks, transactions, and Ethereum values.
-- A `store` API to load and save entities from and to the Graph Node store.
-- A `log` API to log messages to the Graph Node output and Graph Explorer.
-- An `ipfs` API to load files from IPFS.
-- A `json` API to parse JSON data.
-- A `crypto` API to use cryptographic functions.
+- API `ethereum` для работы со смарт-контактами Ethereum, событиями, блоками, транзакциями и значениями Ethereum.
+- API `store` для загрузки и сохранения объектов из хранилища the Graph Node и в него.
+- API `log` для регистрации сообщений в выходных данных the Graph Node и Graph Explorer.
+- API `ipfs` для загрузки файлов из IPFS.
+- API `json` для выполнения разбора данных в формате JSON.
+- API `crypto` для использования криптографических функций.
 - Низкоуровневые примитивы для перевода между системами различных типов, таких как Ethereum, JSON, GraphQL и AssemblyScript.
 
 ### Версии
 
-The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
+`apiVersion` в манифесте субграфа указывает версию мэппинга API, которая запускается посредством Graph Node для данного субграфа.
 
-| Версия | Примечания к релизу |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Версия | Примечания к релизу                                                                                                                                                                                                                          |
+| :----: | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9 | Добавлены новые функции хоста [`eth_get_balance`](#balance-of-an-address) и [`hasCode`](#check-if-an-address-a-contract-or-eoa)                                                                                                              |
+|  0.0.8 | Добавлена проверка наличия полей в схеме при сохранении объекта.                                                                                                                                                                             |
+|  0.0.7 | К типам Ethereum добавлены классы `TransactionReceipt` и `Log`<br />К объекту Ethereum Event добавлено поле `receipt`                                                                                                                        |
+|  0.0.6 | В объект Ethereum Transaction добавлено поле `nonce`<br />В объект Ethereum Block добавлено поле `baseFeePerGas`                                                                                                                             |
+|  0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` |
+|  0.0.4 | В объект Ethereum SmartContractCall добавлено поле `functionSignature`                                                                                                                                                                       |
+|  0.0.3 | В объект Ethereum Call добавлено поле `from`<br />`etherem.call.address` переименован в ethereum.call.to\`                                                                                                                                   |
+|  0.0.2 | В объект Ethereum Transaction добавлено поле `input`                                                                                                                                                                                         |
 
 ### Встроенные типы
 
-Documentation on the base types built into AssemblyScript can be found in the [AssemblyScript wiki](https://www.assemblyscript.org/types.html).
+Документацию по базовым типам, встроенным в AssemblyScript, можно найти в [AssemblyScript wiki](https://www.assemblyscript.org/types.html).
 
-The following additional types are provided by `@graphprotocol/graph-ts`.
+Дополнительные типы, предоставляемые `@graphprotocol/graph-ts`.
 
 #### ByteArray
 
@@ -50,26 +52,26 @@ The following additional types are provided by `@graphprotocol/graph-ts`.
 import { ByteArray } from '@graphprotocol/graph-ts'
 ```
 
-`ByteArray` represents an array of `u8`.
+`ByteArray` представляет собой массив `u8`.
 
-_Construction_
+_Конструкция_
 
-- `fromI32(x: i32): ByteArray` - Decomposes `x` into bytes.
-- `fromHexString(hex: string): ByteArray` - Input length must be even. Prefixing with `0x` is optional.
+- `fromI32(x: i32): ByteArray` — Разбивает `x` на байты.
+- `fromHexString(hex: string): ByteArray` - Длина ввода должна быть четной. Префикс `0x` необязателен.
 
-_Type conversions_
+_Преобразования типов_
 
-- `toHexString(): string` - Converts to a hex string prefixed with `0x`.
-- `toString(): string` - Interprets the bytes as a UTF-8 string.
-- `toBase58(): string` - Encodes the bytes into a base58 string.
-- `toU32(): u32` - Interprets the bytes as a little-endian `u32`. Throws in case of overflow.
-- `toI32(): i32` - Interprets the byte array as a little-endian `i32`. Throws in case of overflow.
+- `toHexString(): string` - Преобразуется в шестнадцатеричную строку с префиксом `0x`.
+- `toString(): string` - Интерпретирует байты как строку UTF-8.
+- `to Base 58(): string` - Кодирует байты в строку base58.
+- `to U32(): u32` - Интерпретирует байты как little-endian `u32`. Выбрасывает в случае переполнения.
+- `to I32(): i32` - Интерпретирует массив байтов как little-endian `i32`. Выбрасывает в случае переполнения.
 
-_Operators_
+_Операторы_
 
-- `equals(y: ByteArray): bool` – can be written as `x == y`.
-- `concat(other: ByteArray) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by `other`
-- `concatI32(other: i32) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by the byte representation of `other`
+- `equals(y: ByteArray): bool` – может быть записано как `x == y`.
+- `concat(other: ByteArray) : ByteArray` - возвращает новый `ByteArray`, состоящий из `this`, за которым непосредственно следует `other`
+- `concatI32(other: i32) : ByteArray` - возвращает новый `ByteArray`, состоящий из `this`, за которым непосредственно следует байтовое представление `other`
 
 #### BigDecimal
 
@@ -77,32 +79,32 @@ _Operators_
 import { BigDecimal } from '@graphprotocol/graph-ts'
 ```
 
-`BigDecimal` is used to represent arbitrary precision decimals.
+`BigDecimal` используется для представления десятичных знаков произвольной точности.
 
-> Note: [Internally](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal` is stored in [IEEE-754 decimal128 floating-point format](https://en.wikipedia.org/wiki/Decimal128_floating-point_format), which supports 34 decimal digits of significand. This makes `BigDecimal` unsuitable for representing fixed-point types that can span wider than 34 digits, such as a Solidity [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) or equivalent.
+> Примечание: [Внутренне](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal` хранится в [формате с плавающей точкой IEEE-754 decimal128](https://en.wikipedia.org/wiki/Decimal128_floating-point_format), который поддерживает 34 десятичных знака после запятой. Это делает `BigDecimal` непригодным для представления типов с фиксированной точкой, которые могут охватывать более 34 знаков, таких как Solidity [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) или его эквивалентов.
 
-_Construction_
+_Конструкция_
 
-- `constructor(bigInt: BigInt)` – creates a `BigDecimal` from an `BigInt`.
-- `static fromString(s: string): BigDecimal` – parses from a decimal string.
+- `constructor(bigInt: BigInt)` — создает `BigDecimal` из `BigInt`.
+- `static fromString(s: string): BigDecimal` – выполняет синтаксический разбор из десятичной строки.
 
-_Type conversions_
+_Преобразования типов_
 
-- `toString(): string` – prints to a decimal string.
+- `toString(): string` – выводит в виде десятичной строки.
 
-_Math_
+_Математика_
 
-- `plus(y: BigDecimal): BigDecimal` – can be written as `x + y`.
-- `minus(y: BigDecimal): BigDecimal` – can be written as `x - y`.
-- `times(y: BigDecimal): BigDecimal` – can be written as `x * y`.
-- `div(y: BigDecimal): BigDecimal` – can be written as `x / y`.
-- `equals(y: BigDecimal): bool` – can be written as `x == y`.
-- `notEqual(y: BigDecimal): bool` – can be written as `x != y`.
-- `lt(y: BigDecimal): bool` – can be written as `x < y`.
-- `le(y: BigDecimal): bool` – can be written as `x <= y`.
-- `gt(y: BigDecimal): bool` – can be written as `x > y`.
-- `ge(y: BigDecimal): bool` – can be written as `x >= y`.
-- `neg(): BigDecimal` - can be written as `-x`.
+- `plus(y: BigDecimal): BigDecimal` – может быть записано как `x + y`.
+- `minus(y: BigDecimal): BigDecimal` – может быть записано как `x - y`.
+- `times(y: BigDecimal): BigDecimal` – может быть записано как `x * y`.
+- `div(y: BigDecimal): BigDecimal` – может быть записано как `x / y`.
+- `equals(y: BigDecimal): bool` – может быть записано как `x == y`.
+- `notEqual(y: BigDecimal): bool` – может быть записано как `x != y`.
+- `lt(y: BigDecimal): bool` – может быть записано как `x < y`.
+- `le(y: BigDecimal): bool` – может быть записано как `x <= y`.
+- `gt(y: BigDecimal): bool` – может быть записано как `x > y`.
+- `ge(y: BigDecimal): bool` – может быть записано как `x >= y`.
+- `neg(): BigDecimal` - может быть записано как `-x`.
 
 #### BigInt
 
@@ -110,53 +112,53 @@ _Math_
 import { BigInt } from '@graphprotocol/graph-ts'
 ```
 
-`BigInt` is used to represent big integers. This includes Ethereum values of type `uint32` to `uint256` and `int64` to `int256`. Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.
+`BigInt` используется для представления больших целых чисел. Сюда входят значения Ethereum типа от `uint32` до `uint256` и от `int64` до `int256`. Все, что находится ниже `uint32`, например `int32`, `uint24` или `int8`, представлено как `i32`.
 
-The `BigInt` class has the following API:
+Класс `BigInt` имеет следующий API:
 
-_Construction_
+_Конструкция_
 
-- `BigInt.fromI32(x: i32): BigInt` – creates a `BigInt` from an `i32`.
+- `BigInt.fromI32(x: i32): BigInt` – создает `BigInt` из `i32`.
 
-- `BigInt.fromString(s: string): BigInt`– Parses a `BigInt` from a string.
+- `BigInt.fromString(s:string): BigInt`– Выполняет разбор `BigInt` из строки.
 
-- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` – Interprets `bytes` as an unsigned, little-endian integer. If your input is big-endian, call `.reverse()` first.
+- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` — Интерпретирует `bytes` беззнаковое целое число в формате little-endian (младшие байты идут первыми). Если Ваши входные данные в формате big-endian (старшие байты идут первыми), сначала вызовите `.reverse()`.
 
-- `BigInt.fromSignedBytes(x: Bytes): BigInt` – Interprets `bytes` as a signed, little-endian integer. If your input is big-endian, call `.reverse()` first.
+- `BigInt.fromSignedBytes(x: Bytes): BigInt` — Интерпретирует `bytes` как знаковое целое число в формате little-endian (младшие байты идут первыми). Если Ваши входные данные в формате big-endian (старшие байты идут первыми), сначала вызовите `.reverse()`.
 
-  _Type conversions_
+  _Преобразования типов_
 
-- `x.toHex(): string` – turns `BigInt` into a string of hexadecimal characters.
+- `x.toHex(): string` – преобразует `BigInt` в строку шестнадцатеричных символов.
 
-- `x.toString(): string` – turns `BigInt` into a decimal number string.
+- `x.toString(): string` – преобразует `BigInt` в строку десятичных чисел.
 
-- `x.toI32(): i32` – returns the `BigInt` as an `i32`; fails if the value does not fit into `i32`. It's a good idea to first check `x.isI32()`.
+- `x.toI32(): i32` – возвращает `BigInt` в виде `i32`; завершается с ошибкой, если значение не соответствует `i32`. Рекомендуется сначала проверить `x.is I32()`.
 
-- `x.toBigDecimal(): BigDecimal` - converts into a decimal with no fractional part.
+- `x.to BigDecimal(): BigDecimal` - преобразует в десятичное число без дробной части.
 
-_Math_
+_Математика_
 
-- `x.plus(y: BigInt): BigInt` – can be written as `x + y`.
-- `x.minus(y: BigInt): BigInt` – can be written as `x - y`.
-- `x.times(y: BigInt): BigInt` – can be written as `x * y`.
-- `x.div(y: BigInt): BigInt` – can be written as `x / y`.
-- `x.mod(y: BigInt): BigInt` – can be written as `x % y`.
-- `x.equals(y: BigInt): bool` – can be written as `x == y`.
-- `x.notEqual(y: BigInt): bool` – can be written as `x != y`.
-- `x.lt(y: BigInt): bool` – can be written as `x < y`.
-- `x.le(y: BigInt): bool` – can be written as `x <= y`.
-- `x.gt(y: BigInt): bool` – can be written as `x > y`.
-- `x.ge(y: BigInt): bool` – can be written as `x >= y`.
-- `x.neg(): BigInt` – can be written as `-x`.
-- `x.divDecimal(y: BigDecimal): BigDecimal` – divides by a decimal, giving a decimal result.
-- `x.isZero(): bool` – Convenience for checking if the number is zero.
-- `x.isI32(): bool` – Check if the number fits in an `i32`.
-- `x.abs(): BigInt` – Absolute value.
-- `x.pow(exp: u8): BigInt` – Exponentiation.
-- `bitOr(x: BigInt, y: BigInt): BigInt` – can be written as `x | y`.
-- `bitAnd(x: BigInt, y: BigInt): BigInt` – can be written as `x & y`.
-- `leftShift(x: BigInt, bits: u8): BigInt` – can be written as `x << y`.
-- `rightShift(x: BigInt, bits: u8): BigInt` – can be written as `x >> y`.
+- `x.plus(y: BigInt): BigInt` – может быть записано как `x + y`.
+- `x.minus(y: BigInt): BigInt` – может быть записано как `x - y`.
+- `x.times(y: BigInt): BigInt` – может быть записано как `x * y`.
+- `x.div(y: BigInt): BigInt` – может быть записано как `x / y`.
+- `x.mod(y: BigInt): BigInt` – может быть записано как `x % y`.
+- `x.equals(y: BigInt): bool` – может быть записано как `x == y`.
+- `x.notEqual(y: BigInt): bool` – может быть записано как `x != y`.
+- `x.lt(y: BigInt): bool` – может быть записано как `x < y`.
+- `x.le(y: BigInt): bool` – может быть записано как `x <= y`.
+- `x.gt(y: BigInt): bool` – может быть записано как `x > y`.
+- `x.ge(y: BigInt): bool` – может быть записано как `x >= y`.
+- `x.neg(): BigInt` – может быть записано как `-x`.
+- `x.divDecimal(y: BigDecimal): BigDecimal` – делит на десятичное число, что дает десятичный результат.
+- `x.isZero(): bool` – Удобство для проверки, равно ли число нулю.
+- `x.isI32(): bool` – Проверяет, соответствует ли число `i32`.
+- `x.abs(): BigInt` – Абсолютное значение.
+- `x.pow(exp: u8): BigInt` – Возведение в степень.
+- `bitOr(x: BigInt, y: BigInt): BigInt` – может быть записан как `x | y`.
+- `bitAnd(x: BigInt, y: BigInt): BigInt` – может быть записан как `x & y`.
+- `leftShift(x: BigInt, bits: u8): BigInt` – может быть записан как `x << y`.
+- `rightShift(x: BigInt, bits: u8): BigInt` – может быть записан как `x >> y`.
 
 #### TypedMap
 
@@ -164,15 +166,15 @@ _Math_
 import { TypedMap } from '@graphprotocol/graph-ts'
 ```
 
-`TypedMap` can be used to store key-value pairs. See [this example](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
+`TypedMap` можно использовать для хранения пар ключ-значение. Смотрите [этот пример](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
 
-The `TypedMap` class has the following API:
+Класс `TypedMap` имеет следующий API:
 
-- `new TypedMap<K, V>()` – creates an empty map with keys of type `K` and values of type `V`
-- `map.set(key: K, value: V): void` – sets the value of `key` to `value`
-- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – returns the key-value pair for a `key` or `null` if the `key` does not exist in the map
-- `map.get(key: K): V | null` – returns the value for a `key` or `null` if the `key` does not exist in the map
-- `map.isSet(key: K): bool` – returns `true` if the `key` exists in the map and `false` if it does not
+- `new TypedMap<K, V>()` создает пустую карту с ключами типа `K` и значениями типа `V`
+- `map.set(key: K, value: V): void` – устанавливает значение `key` в `value`
+- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – возвращает пару ключ-значение для `key` или `null`, если `key` не существует на карте
+- `map.get(key: K): V | null` – возвращает значение для `key` или `null`, если `key` не существует на карте
+- `map.isSet(key: K): bool` – возвращает `true`, если `key` существует на карте, и `false`, если его нет
 
 #### Bytes
 
@@ -180,25 +182,25 @@ The `TypedMap` class has the following API:
 import { Bytes } from '@graphprotocol/graph-ts'
 ```
 
-`Bytes` is used to represent arbitrary-length arrays of bytes. This includes Ethereum values of type `bytes`, `bytes32`, etc.
+`Bytes` используется для представления массивов байтов произвольной длины. Сюда входят значения Ethereum типа `bytes`, `bytes32` и т. д.
 
-The `Bytes` class extends AssemblyScript's [Uint8Array](https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) and this supports all the `Uint8Array` functionality, plus the following new methods:
+Класс `Bytes` расширяет [Uint8Array] из AssemblyScript (https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) и поддерживает все функциональные возможности `Uint8Array`, а также следующие новые методы:
 
-_Construction_
+_Конструкция_
 
-- `fromHexString(hex: string) : Bytes` - Convert the string `hex` which must consist of an even number of hexadecimal digits to a `ByteArray`. The string `hex` can optionally start with `0x`
-- `fromI32(i: i32) : Bytes` - Convert `i` to an array of bytes
+- `fromHexString(hex: string) : Bytes` - Преобразует строку `hex`, которая должна состоять из четного числа шестнадцатеричных цифр, в `ByteArray`. Строка `hex` может опционально начинаться с `0x`
+- `fromI32(i: i32) : Bytes` - Преобразовывает `i` в массив байтов
 
-_Type conversions_
+_Преобразования типов_
 
-- `b.toHex()` – returns a hexadecimal string representing the bytes in the array
-- `b.toString()` – converts the bytes in the array to a string of unicode characters
-- `b.toBase58()` – turns an Ethereum Bytes value to base58 encoding (used for IPFS hashes)
+- `b.toHex()` – возвращает шестнадцатеричную строку, представляющую байты в массиве
+- `b.toString()` – преобразует байты в массиве в строку символов Unicode
+- `b.toBase58()` – преобразует значение Ethereum `Bytes` в кодировку `base58` (используется для хэшей IPFS)
 
-_Operators_
+_Операторы_
 
-- `b.concat(other: Bytes) : Bytes` - - return new `Bytes` consisting of `this` directly followed by `other`
-- `b.concatI32(other: i32) : ByteArray` - return new `Bytes` consisting of `this` directly follow by the byte representation of `other`
+- `b.concat(other: Bytes) : Bytes` - - возвращает новые `Bytes`, состоящие из `this`, за которым непосредственно следует `other`
+- `b.concatI32(other: i32) : ByteArray` - возвращает новые `Bytes`, состоящие из `this`, за которым непосредственно следует байтовое представление `other`
 
 #### Address
 
@@ -206,12 +208,12 @@ _Operators_
 import { Address } from '@graphprotocol/graph-ts'
 ```
 
-`Address` extends `Bytes` to represent Ethereum `address` values.
+`Address` расширяет `Bytes` для представления значений Ethereum `address`.
 
-It adds the following method on top of the `Bytes` API:
+Поверх `Bytes` API добавляется следующий метод:
 
-- `Address.fromString(s: string): Address` – creates an `Address` from a hexadecimal string
-- `Address.fromBytes(b: Bytes): Address` – create an `Address` from `b` which must be exactly 20 bytes long. Passing in a value with fewer or more bytes will result in an error
+- `Address.fromString(s: string): Address` – создает `Address` из шестнадцатеричной строки
+- `Address.fromBytes(b: Bytes): Address` — создайте `Address` из `b` длиной ровно 20 байт. Передача значения с меньшим или большим количеством байт приведет к ошибке
 
 ### Store API
 
@@ -219,9 +221,9 @@ It adds the following method on top of the `Bytes` API:
 import { store } from '@graphprotocol/graph-ts'
 ```
 
-The `store` API allows to load, save and remove entities from and to the Graph Node store.
+API `store` позволяет загружать, сохранять и удалять объекты из хранилища the Graph Node и в него.
 
-Entities written to the store map one-to-one to the `@entity` types defined in the subgraph's GraphQL schema. To make working with these entities convenient, the `graph codegen` command provided by the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) generates entity classes, which are subclasses of the built-in `Entity` type, with property getters and setters for the fields in the schema as well as methods to load and save these entities.
+Объекты, записанные в хранилище карты, сопоставляются один к одному с типами `@entity`, определенными в схеме субграфов GraphQL. Чтобы сделать работу с этими объектами удобной, команда `graph codegen`, предоставляемая [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) генерирует классы объектов, которые являются подклассами встроенного типа `Entity`, с геттерами и сеттерами свойств для полей в схеме, а также методами загрузки и сохранения этих объектов.
 
 #### Создание объектов
 
@@ -231,7 +233,7 @@ Entities written to the store map one-to-one to the `@entity` types defined in t
 // Импорт класса событий Transfer, сгенерированного из ERC20 ABI
 import { Transfer as TransferEvent } from '../generated/ERC20/ERC20'
 
-// Импорт типа объекта Transfer, сгенерированного из схемы GraphQL
+// Импорт типа объекта Transfer, сгенерированного из схемы GraphQL 
 import { Transfer } from '../generated/schema'
 событие
 // Обработчик события передачи
@@ -250,9 +252,11 @@ transfer.save()
 }
 ```
 
-When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
+Когда при обработке чейна возникает событие `Transfer`, оно передается обработчику события `handleTransfer`, используя сгенерированный тип `Transfer` (здесь используется псевдоним `TransferEvent`, чтобы избежать конфликта наименования с типом объекта). Этот тип позволяет получить доступ к таким данным, как материнская транзакция события и ее параметры.
+
+Каждый объект должен иметь уникальный идентификатор, чтобы избежать конфликтов с другими объектами. Параметры событий довольно часто включают уникальный идентификатор, который можно использовать.
 
-Каждый объект должен иметь уникальный идентификатор, чтобы избежать коллизий с другими объектами. Довольно часто параметры события включают уникальный идентификатор, который может быть использован. Примечание: Использование хэша транзакции в качестве идентификатора предполагает, что никакие другие события в той же транзакции не создают объекты с этим хэшем в качестве идентификатора.
+> Примечание: Использование хэша транзакции в качестве идентификатора предполагает, что никакие другие события в той же транзакции не создают объекты с этим хэшем в качестве идентификатора.
 
 #### Загрузка объектов из хранилища
 
@@ -265,18 +269,22 @@ if (transfer == null) {
   transfer = new Transfer(id)
 }
 
+
 // Используйте объект Transfer, как и раньше
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+Поскольку объект может еще не существовать в хранилище, метод `load` возвращает значение типа `Transfer | null`. Таким образом, перед использованием значения может потребоваться проверка на наличие `null`.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Примечание: Загрузка объектов необходима только в том случае, если изменения, внесенные в мэппинг, зависят от предыдущих данных объекта. В следующем разделе описаны два способа обновления существующих объектов.
 
 #### Поиск объектов, созданных внутри блока
 
-As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
+Начиная с `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 и `@graphprotocol/graph-cli` v0.49.0 метод `loadInBlock` доступен для всех типов объектов.
 
-Хранилище API облегчает поиск объектов, которые были созданы или обновлены в текущем блоке. Типичная ситуация для этого заключается в том, что один обработчик создает транзакцию из некоторого события в чейне, а более поздний обработчик хочет получить доступ к этой транзакции, если она существует. В случае, когда транзакция не была осуществлена, субграфу придется обратиться к базе данных только для того, чтобы узнать, что объект не существует; если же автор субграфа знает, что объект, должен был быть создан в том же блоке, использование loadInBlock позволит избежать этого обхода базы данных. Для некоторых субграфов эти пропущенные запросы могут значительно увеличить время индексации.
+API хранилища облегчает извлечение объектов, которые были созданы или обновлены в текущем блоке. Типичная ситуация: один обработчик создает транзакцию из какого-то события в он-чейне, а следующий обработчик хочет получить доступ к этой транзакции, если она существует.
+
+- В случае, если транзакция не существует, субграф должен будет обратиться к базе данных просто для того, чтобы узнать, что объект не существует. Если автор субграфа уже знает, что объект должен быть создан в том же блоке, использование `loadInBlock` позволяет избежать этого обращения к базе данных.
+- Для некоторых субграфов эти пропущенные поиски могут существенно увеличить время индексации.
 
 ```typescript
 let id = event.transaction.hash // или некоторым образом создается идентификатор
@@ -285,14 +293,15 @@ if (transfer == null) {
   transfer = new Transfer(id)
 }
 
+
 // Используйте объект Transfer, как и раньше
 ```
 
-> Note: If there is no entity created in the given block, `loadInBlock` will return `null` even if there is an entity with the given ID in the store.
+> Примечание: Если в данном блоке не создан объект, `loadInBlock` вернет `null`, даже если в хранилище есть объект с данным идентификатором.
 
 #### Поиск производных объектов
 
-As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 and `@graphprotocol/graph-cli` v0.51.0 the `loadRelated` method is available.
+Начиная с `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 и `@graphprotocol/graph-cli` v0.51.0 метод `loadRelated` доступен.
 
 Это позволяет загружать поля производных объектов из обработчика событий. Например, учитывая следующую схему:
 
@@ -309,7 +318,7 @@ type Holder @entity {
 }
 ```
 
-The following code will load the `Token` entity that the `Holder` entity was derived from:
+Следующий код загрузит объект `Token`, из которого был получен объект `Holder`:
 
 ```typescript
 let holder = Holder.load('test-id')
@@ -321,8 +330,8 @@ let tokens = holder.tokens.load()
 
 Существует два способа обновить существующий объект:
 
-1. Load the entity with e.g. `Transfer.load(id)`, set properties on the entity, then `.save()` it back to the store.
-2. Simply create the entity with e.g. `new Transfer(id)`, set properties on the entity, then `.save()` it to the store. If the entity already exists, the changes are merged into it.
+1. Загрузите объект, например, с помощью `Transfer.load(id)`, установите свойства объекта, затем с помощью `.save()` верните его обратно в хранилище.
+2. Просто создайте объект, например, с помощью `new Transfer(id)`, установите свойства объекта, затем с помощью `.save()` сохраните его в хранилище. Если объект уже существует, изменения будут объединены с ним.
 
 Изменение свойств в большинстве случаев не вызывает затруднений благодаря сгенерированным установщикам свойств:
 
@@ -340,9 +349,9 @@ transfer.from.unset()
 transfer.from = null
 ```
 
-This only works with optional properties, i.e. properties that are declared without a `!` in GraphQL. Two examples would be `owner: Bytes` or `amount: BigInt`.
+Это работает только с необязательными свойствами, то есть свойствами, объявленными без `!` в GraphQL. Два примера: `owner: Bytes` или `amount: BigInt`.
 
-Updating array properties is a little more involved, as the getting an array from an entity creates a copy of that array. This means array properties have to be set again explicitly after changing the array. The following assumes `entity` has a `numbers: [BigInt!]!` field.
+Обновление свойств массива немного сложнее, поскольку получение массива из объекта создает копию этого массива. Это означает, что после изменения массива необходимо снова точно задать его свойства. В следующем примере предполагается, что `entity` имеет поле `numbers: [BigInt!]!`.
 
 ```typescript
 // Это не сработает
@@ -358,7 +367,7 @@ entity.save()
 
 #### Удаление объектов из хранилища
 
-There is currently no way to remove an entity via the generated types. Instead, removing an entity requires passing the name of the entity type and the entity ID to `store.remove`:
+В настоящее время нет способа удалить объект с помощью сгенерированных типов. Вместо этого для удаления объекта требуется передать имя типа объекта и идентификатор объекта в `store.remove`:
 
 ```typescript
 import { store } from '@graphprotocol/graph-ts'
@@ -373,9 +382,9 @@ Ethereum API предоставляет доступ к смарт-контра
 
 #### Поддержка типов Ethereum
 
-As with entities, `graph codegen` generates classes for all smart contracts and events used in a subgraph. For this, the contract ABIs need to be part of the data source in the subgraph manifest. Typically, the ABI files are stored in an `abis/` folder.
+Как и в случае с объектами, `graph codegen` генерирует классы для всех смарт-контрактов и событий, используемых в субграфе. Для этого ABI контракта должны быть частью источника данных в манифесте субграфа. Как правило, файлы ABI хранятся в папке `abis/`.
 
-With the generated classes, conversions between Ethereum types and the [built-in types](#built-in-types) take place behind the scenes so that subgraph authors do not have to worry about them.
+С помощью сгенерированных классов преобразования между типами Ethereum и [встроенными типами] (#built-in-types) происходят за кулисами, так что авторам субграфов не нужно беспокоиться о них.
 
 Следующий пример иллюстрирует это. С учётом схемы субграфа, такой как
 
@@ -388,7 +397,7 @@ type Transfer @entity {
 }
 ```
 
-and a `Transfer(address,address,uint256)` event signature on Ethereum, the `from`, `to` and `amount` values of type `address`, `address` and `uint256` are converted to `Address` and `BigInt`, allowing them to be passed on to the `Bytes!` and `BigInt!` properties of the `Transfer` entity:
+и сигнатура события `Transfer(address,address,uint256)` на Ethereum, значения `from`, `to` и `amount` типа `address`, `address` и `uint256` преобразуются в `Address` и `BigInt`, что позволяет передавать их в свойства `Bytes!` и `BigInt!` объекта `Transfer`:
 
 ```typescript
 let id = event.transaction.hash
@@ -401,7 +410,7 @@ transfer.save()
 
 #### События и данные о блоках/транзакциях
 
-Ethereum events passed to event handlers, such as the `Transfer` event in the previous examples, not only provide access to the event parameters but also to their parent transaction and the block they are part of. The following data can be obtained from `event` instances (these classes are a part of the `ethereum` module in `graph-ts`):
+События Ethereum, передаваемые обработчикам событий, такие как событие `Transfer` в предыдущих примерах, предоставляют доступ не только к параметрам события, но и к их материнской транзакции и блоку, частью которого они являются. Следующие данные могут быть получены из экземпляров `event` (эти классы являются частью модуля `ethereum` в `graph-ts`):
 
 ```typescript
 class Event {
@@ -476,7 +485,7 @@ class Log {
 
 #### Доступ к состоянию смарт-контракта
 
-The code generated by `graph codegen` also includes classes for the smart contracts used in the subgraph. These can be used to access public state variables and call functions of the contract at the current block.
+Код, сгенерированный с помощью `graph codegen`, также включает классы для смарт-контрактов, используемых в субграфе. Они могут быть использованы для доступа к общедоступным переменным состояния и вызова функций контракта в текущем блоке.
 
 Распространенным шаблоном является доступ к контракту, из которого исходит событие. Это достигается с помощью следующего кода:
 
@@ -495,15 +504,17 @@ export function handleTransfer(event: TransferEvent) {
 }
 ```
 
-`Transfer` is aliased to `TransferEvent` here to avoid a naming conflict with the entity type
+`Transfer` связывается с `TransferEvent`, чтобы избежать конфликта наименований с типом объекта
 
-As long as the `ERC20Contract` on Ethereum has a public read-only function called `symbol`, it can be called with `.symbol()`. For public state variables a method with the same name is created automatically.
+Пока `ERC20Contract` в Ethereum имеет общедоступную функцию только для чтения, называемую `symbol`, ее можно вызвать с помощью `.symbol()`. Для общедоступных переменных состояния автоматически создается метод с таким же именем.
 
 Любой другой контракт, который является частью субграфа, может быть импортирован из сгенерированного кода и привязан к действительному адресу.
 
 #### Обработка возвращенных вызовов
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+Если методы Вашего контракта, доступные только для чтения, могут вернуться к предыдущему состоянию, то Вам следует решить эту проблему, вызвав сгенерированный метод контракта с префиксом `try_`.
+
+- Например, контракт Gravity предоставляет метод `gravatarToOwner`. Этот код сможет выполнить возврат в этом методе:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,11 +526,11 @@ if (callResult.reverted) {
 }
 ```
 
-Обратите внимание, что Graph Node, подключенная к клиенту Geth или Infura, может обнаруживать не все откаты. Если Вы полагаетесь на это, мы рекомендуем использовать Graph Node, подключенную к клиенту Parity.
+> Примечание: Graph Node, подключенный к клиенту Geth или Infura, может обнаружить не все откаты. Если Вы полагаетесь на это, мы рекомендуем использовать Graph Node, подключенный к клиенту Parity.
 
 #### Кодирование/декодирование ABI
 
-Data can be encoded and decoded according to Ethereum's ABI encoding format using the `encode` and `decode` functions in the `ethereum` module.
+Данные могут быть закодированы и декодированы в соответствии с форматом кодирования ABI Ethereum с использованием функций `encode` и `decode` в модуле `ethereum`.
 
 ```typescript
 import { Address, BigInt, ethereum } from '@graphprotocol/graph-ts'
@@ -538,33 +549,33 @@ let decoded = ethereum.decode('(address,uint256)', encoded)
 
 Для получения дополнительной информации:
 
-- [ABI Spec](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
-- Encoding/decoding [Rust library/CLI](https://github.com/rust-ethereum/ethabi)
-- More [complex example](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
+- [Спецификация ABI](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
+- Кодирование/декодирование [библиотека Rust/CLI](https://github.com/rust-ethereum/ethabi)
+- Более [сложный пример] (https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
 
-#### Balance of an Address
+#### Баланс адреса
 
-The native token balance of an address can be retrieved using the `ethereum` module. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`. The `getBalance()` retrieves the balance of the specified address as of the end of the block in which the event is triggered.
+Баланс нативного токена адреса можно получить с помощью модуля `ethereum`. Эта функция доступна начиная с `apiVersion: 0.0.9`, которая определена `subgraph.yaml`. `getBalance()` извлекает баланс указанного адреса на конец блока, в котором инициировано событие.
 
 ```typescript
 import { ethereum } from '@graphprotocol/graph-ts'
 
 let address = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
-let balance = ethereum.getBalance(address) // returns balance in BigInt
+let balance = ethereum.getBalance(address) // возвращает баланс в BigInt
 ```
 
-#### Check if an Address is a Contract or EOA
+#### Проверьте, является ли адрес контрактом или EOA
 
-To check whether an address is a smart contract address or an externally owned address (EOA), use the `hasCode()` function from the `ethereum` module which will return `boolean`. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`.
+Чтобы проверить, является ли адрес адресом смарт-контракта или внешним адресом (EOA), используйте функцию `hasCode()` из модуля `ethereum`, которая вернет `boolean`. Эта функция доступна начиная с `apiVersion: 0.0.9`, которая определена `subgraph.yaml`.
 
 ```typescript
 import { ethereum } from '@graphprotocol/graph-ts'
 
 let contractAddr = Address.fromString('0x2E645469f354BB4F5c8a05B3b30A929361cf77eC')
-let isContract = ethereum.hasCode(contractAddr).inner // returns true
+let isContract = ethereum.hasCode(contractAddr).inner // возвращает ложное значение
 
 let eoa = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
-let isContract = ethereum.hasCode(eoa).inner // returns false
+let isContract = ethereum.hasCode(eoa).inner // возвращает ложное значение
 ```
 
 ### Регистрация API
@@ -573,17 +584,17 @@ let isContract = ethereum.hasCode(eoa).inner // returns false
 import { log } from '@graphprotocol/graph-ts'
 ```
 
-The `log` API allows subgraphs to log information to the Graph Node standard output as well as Graph Explorer. Messages can be logged using different log levels. A basic format string syntax is provided to compose log messages from argument.
+API `log` позволяет субграфам записывать информацию в стандартный вывод Graph Node, а также в Graph Explorer. Сообщения могут быть зарегистрированы с использованием различных уровней ведения лога. Для составления сообщений лога из аргумента предусмотрен синтаксис строки базового формата.
 
-The `log` API includes the following functions:
+API `log` включает в себя следующие функции:
 
-- `log.debug(fmt: string, args: Array<string>): void` - logs a debug message.
-- `log.info(fmt: string, args: Array<string>): void` - logs an informational message.
-- `log.warning(fmt: string, args: Array<string>): void` - logs a warning.
-- `log.error(fmt: string, args: Array<string>): void` - logs an error message.
-- `log.critical(fmt: string, args: Array<string>): void` – logs a critical message _and_ terminates the subgraph.
+- `log.debug(fmt: string, args: Array<string>): void` - регистрирует сообщение об отладке.
+- `log.info (fmt: string, args: Array<string>): void` - регистрирует информационное сообщение.
+- `log.warning(fmt: string, args: Array<string>): void` - регистрирует предупреждение.
+- `log.error(fmt: string, args: Array<string>): void` - регистрирует сообщение об ошибке.
+- `log.critical(fmt: string, args: Array<string>): void` – регистрирует критическое сообщение и завершает работу субграфа.
 
-The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
+API `log` принимает строку формата и массив строковых значений. Затем он заменяет заполнители строковыми значениями из массива. Первый `{}` заполнитель заменяется первым значением в массиве, второй `{}` заполнитель заменяется вторым значением и так далее.
 
 ```typescript
 log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.toString(), 'already a string'])
@@ -593,7 +604,7 @@ log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.
 
 ##### Регистрация одного значения
 
-In the example below, the string value "A" is passed into an array to become`['A']` before being logged:
+В приведенном ниже примере строковое значение "A" передается в массив, чтобы стать `['A']` перед тем как будет записано в лог:
 
 ```typescript
 let myValue = 'A'
@@ -619,7 +630,7 @@ export function handleSomeEvent(event: SomeEvent): void {
 
 #### Регистрация нескольких записей из существующего массива
 
-Each entry in the arguments array requires its own placeholder `{}` in the log message string. The below example contains three placeholders `{}` in the log message. Because of this, all three values in `myArray` are logged.
+Для каждой записи в массиве arguments требуется свой собственный заполнитель `{}` в строке сообщения лога. В приведенном ниже примере в сообщении лога содержатся три заполнителя `{}`. По этой причине в `myArray` регистрируются все три значения.
 
 ```typescript
 let myArray = ['A', 'B', 'C']
@@ -663,7 +674,7 @@ export function handleSomeEvent(event: SomeEvent): void {
 import { ipfs } from '@graphprotocol/graph-ts'
 ```
 
-Smart contracts occasionally anchor IPFS files on chain. This allows mappings to obtain the IPFS hashes from the contract and read the corresponding files from IPFS. The file data will be returned as `Bytes`, which usually requires further processing, e.g. with the `json` API documented later on this page.
+Смарт-контракты иногда привязывают файлы IPFS к чейну. Это позволяет мэппингам получать хэши IPFS из контракта и считывать соответствующие файлы из IPFS. Данные файла будут возвращены в виде `Bytes`, что обычно требует дальнейшей обработки, например, с помощью `json` API, описанного далее на этой странице.
 
 При наличии хеша или пути IPFS чтение файла из IPFS выполняется следующим образом:
 
@@ -678,16 +689,16 @@ let path = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile'
 let data = ipfs.cat(path)
 ```
 
-**Note:** `ipfs.cat` is not deterministic at the moment. If the file cannot be retrieved over the IPFS network before the request times out, it will return `null`. Due to this, it's always worth checking the result for `null`.
+**Примечание:** `pfs.cat` на данный момент не является детерминированным. Если файл не может быть получен по сети IPFS до истечения времени ожидания запроса, он вернет `null`. В связи с этим всегда стоит проверять результат на наличие `null`.
 
-It is also possible to process larger files in a streaming fashion with `ipfs.map`. The function expects the hash or path for an IPFS file, the name of a callback, and flags to modify its behavior:
+С помощью `ipfs.map` можно также обрабатывать файлы большего размера в потоковом режиме. Функция ожидает, что хэш или путь к файлу IPFS, имя обратного вызова и флаги изменят его поведение:
 
 ```typescript
 import { JSONValue, Value } from '@graphprotocol/graph-ts'
 
 export function processItem(value: JSONValue, userData: Value): void {
-  // Смотрите документацию по JsonValue для получения подробной информации о работе
-  // со значениями JSON
+// Смотрите документацию по JsonValue для получения подробной информации о работе
+// со значениями JSON
   let obj = value.toObject()
   let id = obj.get('id')
   let title = obj.get('title')
@@ -696,7 +707,7 @@ export function processItem(value: JSONValue, userData: Value): void {
     return
   }
 
-  // Обратные вызовы также могут создавать объекты
+// Обратные вызовы также могут создавать объекты
   let newItem = new Item(id)
   newItem.title = title.toString()
   newitem.parent = userData.toString() // Установите для родителя значение "parentId"
@@ -710,9 +721,9 @@ ipfs.map('Qm...', 'processItem', Value.fromString('parentId'), ['json'])
 ipfs.mapJSON('Qm...', 'processItem', Value.fromString('parentId'))
 ```
 
-The only flag currently supported is `json`, which must be passed to `ipfs.map`. With the `json` flag, the IPFS file must consist of a series of JSON values, one value per line. The call to `ipfs.map` will read each line in the file, deserialize it into a `JSONValue` and call the callback for each of them. The callback can then use entity operations to store data from the `JSONValue`. Entity changes are stored only when the handler that called `ipfs.map` finishes successfully; in the meantime, they are kept in memory, and the size of the file that `ipfs.map` can process is therefore limited.
+Единственным поддерживаемым в настоящее время флагом является `json`, который должен быть передан в `ipfs.map`. С флагом `json` файл IPFS должен состоять из серии значений JSON, по одному значению в строке. Вызов `ipfs.map` прочитает каждую строку в файле, десериализует ее в `JSONValue` и совершит обратный вызов для каждой из них. Затем обратный вызов может использовать операции с объектами для хранения данных из `JSONValue`. Изменения объекта сохраняются только после успешного завершения обработчика, вызвавшего `ipfs.map`; в то же время они хранятся в памяти, и поэтому размер файла, который может обработать `ipfs.map`, ограничен.
 
-On success, `ipfs.map` returns `void`. If any invocation of the callback causes an error, the handler that invoked `ipfs.map` is aborted, and the subgraph is marked as failed.
+При успешном завершении `ipfs.map` возвращает `void`. Если какое-либо совершение обратного вызова приводит к ошибке, обработчик, вызвавший `ipfs.map`, прерывается, а субграф помечается как давший сбой.
 
 ### Crypto API
 
@@ -720,7 +731,7 @@ On success, `ipfs.map` returns `void`. If any invocation of the callback causes
 import { crypto } from '@graphprotocol/graph-ts'
 ```
 
-The `crypto` API makes a cryptographic functions available for use in mappings. Right now, there is only one:
+API `crypto` делает криптографические функции доступными для использования в мэппингах. На данный момент есть только один:
 
 - `crypto.keccak256(input: ByteArray): ByteArray`
 
@@ -730,14 +741,14 @@ The `crypto` API makes a cryptographic functions available for use in mappings.
 import { json, JSONValueKind } from '@graphprotocol/graph-ts'
 ```
 
-JSON data can be parsed using the `json` API:
+Данные JSON могут быть разобраны с помощью `json` API:
 
-- `json.fromBytes(data: Bytes): JSONValue` – parses JSON data from a `Bytes` array interpreted as a valid UTF-8 sequence
-- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – safe version of `json.fromBytes`, it returns an error variant if the parsing failed
-- `json.fromString(data: string): JSONValue` – parses JSON data from a valid UTF-8 `String`
-- `json.try_fromString(data: string): Result<JSONValue, boolean>` – safe version of `json.fromString`, it returns an error variant if the parsing failed
+- `json.fromBytes(data: Bytes): JSONValue` – выполняет разбор данных JSON из массива `Bytes`, интерпретируемого как допустимая последовательность UTF-8
+- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – безопасная версия `json.fromBytes`, возвращает вариант ошибки, если выполнение разбора не удалось
+- `json.fromString(data: string): JSONValue` – выполняет разбор данных JSON из допустимой UTF-8 `String`
+- `json.try_fromString(data: string): Result<JSONValue, boolean>` – безопасная версия `json.fromString`, возвращает вариант ошибки, если выполнение разбора не удалось
 
-The `JSONValue` class provides a way to pull values out of an arbitrary JSON document. Since JSON values can be booleans, numbers, arrays and more, `JSONValue` comes with a `kind` property to check the type of a value:
+Класс `JSONValue` предоставляет способ извлечения значений из произвольного документа JSON. Поскольку значениями JSON могут быть логические значения, числа, массивы и многое другое, `JSONValue` поставляется со свойством `kind` для проверки типа значения:
 
 ```typescript
 let value = json.fromBytes(...)
@@ -746,63 +757,63 @@ if (value.kind == JSONValueKind.BOOL) {
 }
 ```
 
-In addition, there is a method to check if the value is `null`:
+Кроме того, существует способ проверить, является ли значение `null`:
 
 - `value.isNull(): boolean`
 
-When the type of a value is certain, it can be converted to a [built-in type](#built-in-types) using one of the following methods:
+Когда тип значения определен, его можно преобразовать во [встроенный тип](#built-in-types), используя один из следующих методов:
 
 - `value.toBool(): boolean`
 - `value.toI64(): i64`
 - `value.toF64(): f64`
 - `value.toBigInt(): BigInt`
 - `value.toString(): string`
-- `value.toArray(): Array<JSONValue>` - (and then convert `JSONValue` with one of the 5 methods above)
+- `value.toArray(): Array<JSONValue>` - (а затем преобразовать `JSONValue` одним из 5 методов, описанных выше)
 
 ### Справка по преобразованию типов
 
-| Source(s)            | Destination          | Conversion function           |
-| -------------------- | -------------------- | ----------------------------- |
-| Address              | Bytes                | none                          |
-| Address              | String               | s.toHexString()               |
-| BigDecimal           | String               | s.toString()                  |
-| BigInt               | BigDecimal           | s.toBigDecimal()              |
-| BigInt               | String (hexadecimal) | s.toHexString() или s.toHex() |
-| BigInt               | String (unicode)     | s.toString()                  |
-| BigInt               | i32                  | s.toI32()                     |
-| Boolean              | Boolean              | none                          |
-| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)     |
-| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)   |
-| Bytes                | String (hexadecimal) | s.toHexString() или s.toHex() |
-| Bytes                | String (unicode)     | s.toString()                  |
-| Bytes                | String (base58)      | s.toBase58()                  |
-| Bytes                | i32                  | s.toI32()                     |
-| Bytes                | u32                  | s.toU32()                     |
-| Bytes                | JSON                 | json.fromBytes(s)             |
-| int8                 | i32                  | none                          |
-| int32                | i32                  | none                          |
-| int32                | BigInt               | BigInt.fromI32(s)             |
-| uint24               | i32                  | none                          |
-| int64 - int256       | BigInt               | none                          |
-| uint32 - uint256     | BigInt               | none                          |
-| JSON                 | boolean              | s.toBool()                    |
-| JSON                 | i64                  | s.toI64()                     |
-| JSON                 | u64                  | s.toU64()                     |
-| JSON                 | f64                  | s.toF64()                     |
-| JSON                 | BigInt               | s.toBigInt()                  |
-| JSON                 | string               | s.toString()                  |
-| JSON                 | Array                | s.toArray()                   |
-| JSON                 | Object               | s.toObject()                  |
-| String               | Address              | Address.fromString(s)         |
-| Bytes                | Address              | Address.fromBytes(s)          |
-| String               | BigInt               | BigInt.fromString(s)          |
-| String               | BigDecimal           | BigDecimal.fromString(s)      |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)    |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)         |
+| Источник(и)            | Место назначения          | Функция преобразования              |
+| ---------------------- | ------------------------- | ----------------------------------- |
+| Address                | Bytes                     | отсутствует                         |
+| Address                | String                    | s.toHexString()                     |
+| BigDecimal             | String                    | s.toString()                        |
+| BigInt                 | BigDecimal                | s.toBigDecimal()                    |
+| BigInt                 | String (hexadecimal)      | s.toHexString() или s.toHex()       |
+| BigInt                 | String (unicode)          | s.toString()                        |
+| BigInt                 | i32                       | s.toI32()                           |
+| Boolean                | Boolean                   | отсутствует                         |
+| Bytes (signed)         | BigInt                    | BigInt.fromSignedBytes(s)           |
+| Bytes (unsigned)       | BigInt                    | BigInt.fromUnsignedBytes(s)         |
+| Bytes                  | String (hexadecimal)      | s.toHexString() или s.toHex()       |
+| Bytes                  | String (unicode)          | s.toString()                        |
+| Bytes                  | String (base58)           | s.toBase58()                        |
+| Bytes                  | i32                       | s.toI32()                           |
+| Bytes                  | u32                       | s.toU32()                           |
+| Bytes                  | JSON                      | json.fromBytes(s)                   |
+| int8                   | i32                       | отсутствует                         |
+| int32                  | i32                       | отсутствует                         |
+| int32                  | BigInt                    | BigInt.fromI32(s)                   |
+| uint24                 | i32                       | отсутствует                         |
+| int64 - int256         | BigInt                    | отсутствует                         |
+| uint32 - uint256       | BigInt                    | отсутствует                         |
+| JSON                   | boolean                   | s.toBool()                          |
+| JSON                   | i64                       | s.toU64()                           |
+| JSON                   | u64                       | s.toU64()                           |
+| JSON                   | f64                       | s.toF64()                           |
+| JSON                   | BigInt                    | s.toBigInt()                        |
+| JSON                   | string                    | s.toString()                        |
+| JSON                   | Array                     | s.toArray()                         |
+| JSON                   | Object                    | s.toObject()                        |
+| String                 | Address                   | Address.fromString(s)               |
+| Bytes                  | Address                   | Address.fromBytes(s)                |
+| String                 | BigInt                    | BigInt.fromString(s)                |
+| String                 | BigDecimal                | BigDecimal.fromString(s)            |
+| String (hexadecimal)   | Bytes                     | ByteArray.fromHexString(s)          |
+| String (UTF-8)         | Bytes                     | ByteArray.fromUTF8(s)               |
 
 ### Метаданные источника данных
 
-You can inspect the contract address, network and context of the data source that invoked the handler through the `dataSource` namespace:
+Вы можете проверить адрес контракта, сеть и контекст источника данных, который вызвал обработчик, через пространство имен `DataSource`:
 
 - `dataSource.address(): Address`
 - `dataSource.network(): string`
@@ -810,7 +821,7 @@ You can inspect the contract address, network and context of the data source tha
 
 ### Объект и DataSourceContext
 
-The base `Entity` class and the child `DataSourceContext` class have helpers to dynamically set and get fields:
+Базовый класс `Entity` и дочерний класс `DataSourceContext` имеют помощников для динамической установки и получения полей:
 
 - `setString(key: string, value: string): void`
 - `setI32(key: string, value: i32): void`
@@ -825,11 +836,11 @@ The base `Entity` class and the child `DataSourceContext` class have helpers to
 - `getBoolean(key: string): boolean`
 - `getBigDecimal(key: string): BigDecimal`
 
-### DataSourceContext in Manifest
+### DataSourceContext в манифесте
 
-The `context` section within `dataSources` allows you to define key-value pairs that are accessible within your subgraph mappings. The available types are `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`.
+Раздел `context` в `dataSources` позволяет Вам определять пары ключ-значение, которые доступны в Ваших мэппингах субграфа. Доступные типы: `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List` и `BigInt`.
 
-Here is a YAML example illustrating the usage of various types in the `context` section:
+Ниже приведен пример YAML, иллюстрирующий использование различных типов в разделе `context`:
 
 ```yaml
 dataSources:
@@ -869,13 +880,13 @@ dataSources:
         data: '1000000000000000000000000'
 ```
 
-- `Bool`: Specifies a Boolean value (`true` or `false`).
-- `String`: Specifies a String value.
-- `Int`: Specifies a 32-bit integer.
-- `Int8`: Specifies an 8-bit integer.
-- `BigDecimal`: Specifies a decimal number. Must be quoted.
-- `Bytes`: Specifies a hexadecimal string.
-- `List`: Specifies a list of items. Each item needs to specify its type and data.
-- `BigInt`: Specifies a large integer value. Must be quoted due to its large size.
+- `Bool`: Определяет логическое значение (`true` или `false`).
+- `String`: Определяет строковое значение.
+- `Int`: Определяет 32-разрядное целое число.
+- `Int8`: Определяет 8-разрядное целое число.
+- `BigDecimal`: Определяет десятичное число. Необходимо заключить в кавычки.
+- `Bytes`: Определяет шестнадцатеричную строку.
+- `List`: Определяет список элементов. Для каждого элемента необходимо указать его тип и данные.
+- `BigInt`: Определяет большое целочисленное значение. Необходимо заключить в кавычки из-за большого размера.
 
-This context is then accessible in your subgraph mapping files, enabling more dynamic and configurable subgraphs.
+Затем этот контекст становится доступным в Ваших мэппинговых файлах субграфов, что позволяет сделать субграфы более динамичными и настраиваемыми.

From 0d3c5f944be108b1abd95d71d7491a74b9f37bbb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:32 -0500
Subject: [PATCH 0035/1325] New translations quick-start.mdx (Swedish)

---
 website/pages/sv/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/sv/quick-start.mdx b/website/pages/sv/quick-start.mdx
index 2a6e084ed0fd..d59221b1659c 100644
--- a/website/pages/sv/quick-start.mdx
+++ b/website/pages/sv/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Snabbstart
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Se till att din subgraf kommer att indexera data från ett [nätverk som stöds] (/developing/supported-networks).
-
-Den här guiden är skriven förutsatt att du har:
+## Förutsättningar
 
 - En kryptoplånbok
-- En smart kontraktsadress på det nätverk du väljer
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Skapa en subgraf på Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Installera Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Installera Graph CLI
 
 Kör ett av följande kommandon på din lokala dator:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-När du initierar din subgraf kommer CLI verktyget att be dig om följande information:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Protokoll: välj det protokoll som din subgraf ska indexera data från
-- Subgragh slug: skapa ett namn för din subgraf. Din subgraf snigel är en identifierare för din subgraf.
-- Katalog att skapa subgrafen i: välj din lokala katalog
-- Ethereum nätverk (valfritt): du kan behöva ange vilket EVM kompatibelt nätverk din subgraf kommer att indexera data från
-- Kontraktsadress: Leta upp den smarta kontraktsadress som du vill fråga data från
-- ABI: Om ABI inte fylls i automatiskt måste du mata in det manuellt som en JSON fil
-- Startblock: det föreslås att du matar in startblocket för att spara tid medan din subgraf indexerar blockkedjedata. Du kan hitta startblocket genom att hitta blocket där ditt kontrakt distribuerades.
-- Kontraktsnamn: ange namnet på ditt kontrakt
-- Indexera kontraktshändelser som entiteter: det föreslås att du ställer in detta till sant eftersom det automatiskt lägger till mappningar till din subgraf för varje emitterad händelse
-- Lägg till ett annat kontrakt (valfritt): du kan lägga till ett annat kontrakt
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 Se följande skärmdump för ett exempel för vad du kan förvänta dig när du initierar din subgraf:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-De tidigare kommandona skapar en ställnings undergraf som du kan använda som utgångspunkt för att bygga din undergraf. När du gör ändringar i subgrafen kommer du huvudsakligen att arbeta med tre filer:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 När din subgraf är skriven, kör följande kommandon:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Autentisera och distribuera din subgraf. Implementeringsnyckeln finns på Subgraph sidan i Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Testa din subgraf
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-Loggarna kommer att berätta om det finns några fel med din subgraf. Loggarna för en operativ subgraf kommer att se ut så här:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-För att spara på gaskostnaderna kan du kurera din subgraf i samma transaktion som du publicerade den genom att välja den här knappen när du publicerar din subgraf till The Graphs decentraliserade nätverk:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Nu kan du fråga din subgraf genom att skicka GraphQL frågor till din subgrafs fråge URL, som du kan hitta genom att klicka på frågeknappen.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 3fa04867aa02079a9eb3464714bdf8d14748265a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:33 -0500
Subject: [PATCH 0036/1325] New translations quick-start.mdx (Ukrainian)

---
 website/pages/uk/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/uk/quick-start.mdx b/website/pages/uk/quick-start.mdx
index e1c67fc854ce..28d6bbbe5601 100644
--- a/website/pages/uk/quick-start.mdx
+++ b/website/pages/uk/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Швидкий старт
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-Цей покроковий посібник написаний з урахуванням того, що у вас уже є:
+## Prerequisites
 
 - Криптогаманець
-- Адреса смартконтракту в мережі, яку ви обрали
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Створення підграфа в Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Встановлення Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Встановлення Graph CLI
 
 На вашому локальному комп'ютері запустіть одну з наведених нижче команд:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-Коли ви ініціалізуєте ваш підграф, CLI інструмент запитає вас про таку інформацію:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- Протокол: виберіть протокол, з якого ваш підграф буде індексувати дані
-- Підграф мітка: створіть ім'я для вашого підграфа. Ваша підграф мітка є ідентифікатором для вашого підграфа.
-- Директорія для створення підграфа в ній: оберіть вашу локальну директорію
-- Мережа Ethereum (необов'язково): можливо, вам потрібно буде вказати, з якої EVM-сумісної мережі ваш підграф буде індексувати дані
-- Адреса контракту: Вкажіть адресу смарт-контракту, з якого ви хочете запитувати дані
-- ABI: Якщо ABI не заповнюється автоматично, вам потрібно буде ввести його вручну у вигляді JSON-файлу
-- Стартовий блок: рекомендується вказати стартовий блок, щоб заощадити час, поки ваш підграф індексує дані з блокчейну. Ви можете знайти стартовий блок, знайшовши блок, де був розгорнутий ваш контракт.
-- Назва контракту: введіть назву вашого контракту
-- Індексація подій контракту у якості елементів: рекомендується встановити значення true, оскільки це автоматично додасть відповідність вашого підграфа для кожної виданої події
-- Додання ще одного контракту (необов'язково): ви можете додати ще один контракт
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 На наступному скриншоті ви можете побачити, чого варто очікувати при ініціалізації вашого підграфа:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-Попередні команди створюють так званий "скелет" підграфа, який ви можете використовувати як відправну точку для побудови вашого підграфа. При внесенні змін до підграфа ви будете працювати переважно з трьома файлами:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Як тільки ваш підграф буде написаний, виконайте наступні команди:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Автентифікуйте та розгорніть ваш підграф. Ключ для розгортання можна знайти на сторінці підграфа у Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Тестування вашого підграфа
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-Журнали покажуть вам, чи є якісь помилки у вашому підграфі. Журнал робочого підграфа матиме такий вигляд:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-Щоб заощадити на витратах на газ, ви можете надіслати сигнал на власний підграф у тій самій транзакції, в якій ви його опублікували, вибравши цю функцію під час публікації підграфа в децентралізованій мережі The Graph:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Тепер ви можете запитувати ваш підграф, надсилаючи GraphQL-запити на URL-адресу запиту вашого підграфа, яку ви можете знайти, натиснувши на кнопку запиту.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 6e3052a1154295ba634f49d93feb30874d96ce7b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:34 -0500
Subject: [PATCH 0037/1325] New translations quick-start.mdx (Chinese
 Simplified)

---
 website/pages/zh/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/zh/quick-start.mdx b/website/pages/zh/quick-start.mdx
index dfd8e5f92aa2..b68efb3aa361 100644
--- a/website/pages/zh/quick-start.mdx
+++ b/website/pages/zh/quick-start.mdx
@@ -2,24 +2,26 @@
 title: 快速开始
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-确保您的子图将从一个[受支持的网络](/developing/supported-networks) 中索引数据。
-
-本指南是在假设您具备以下条件的情况下编写的：
+## 先决条件
 
 - 一个加密钱包
-- 您选择的网络上的智能合约地址
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. 在子图工作室中创建子图
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. 安装 Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. 安装 Graph CLI
 
 在本地计算机上，运行以下命令之一：
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> 您可以在[Subgraph Studio](https://thegraph.com/studio/)的子图页面找到针对您特定子图的命令。
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> 您可以在[Subgraph Studio](https://thegraph.com/studio/)的子图页面找到针对您特定子图的命令。
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-初始化子图时，CLI工具会要求您提供以下信息：
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- 协议：选择子图索引数据的协议
-- 子图段塞：为您的子图创建一个名称。您的子图段塞是子图的标识符。
-- 创建子图的目录：选择您的本地目录
-- 以太坊网络（可选）：您可能需要指定子图将从哪个EVM兼容网络索引数据
-- 合约地址：找到要查询数据的智能合约地址
-- ABI：如果ABI不是自动填充的，则需要将其手动输入为JSON文件
-- 起始区块：建议您在子图索引区块链数据时输入起始区块以节省时间。您可以通过查找部署合约区块来定位起始区块。
-- 合约名称：输入您的合约名称
-- 将合约事件作为实体进行索引：建议您将其设置为true，因为它将自动为每个发出的事件向子图添加映射
-- 添加其他合约（可选）：您可以添加其他合约
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 请参阅下面的屏幕截图，以获取初始化子图时所需的示例：
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-前面的命令创建了一个原始子图，可以将其用作构建子图的起点。当对子图进行更改时，将主要使用三个文件:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 一旦您的子图被编写好，请运行以下命令：
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-您将被要求输入一个版本标签。强烈建议使用（语义化版本）[semver](https://semver.org/) 进行版本控制，如`0.0.1`。尽管如此，您可以自由选择任何字符串作为版本，比如：`v1`，`version1`，`asdf`。
-
-## 6. 测试子图
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-日志会告诉你你的子图是否有任何错误。操作子图的日志如下所示：
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-如果子图失败了，可以通过使用 GraphiQL Playground查询子图的健康状况。注意，你可以利用下面的查询，输入你的子图的部署 ID。在这种情况下，Qm... 是部署 ID（可以在子图页面的详细信息下找到）。下面的查询会提示，当一个子图失败时，则可进行相应调试。
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-选择您希望发布子图的网络。建议将子图发布到 Arbitrum One，以利用[更快的交易速度和更低的Gas费用](/arbitrum/arbitrum-faq)。
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-为了节省gas成本，您可以在将子图发布到Graph的去中心化网络时选择此按钮，在发布子图的同一交易中策展子图：
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-现在，您可以通过将GraphQL查询发送到子图的查询URL来查询子图，您可以单击查询按钮找到该查询URL。
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 2bc7e09250524a783df628b39bf5eb4de8e41f84 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:35 -0500
Subject: [PATCH 0038/1325] New translations quick-start.mdx (Urdu (Pakistan))

---
 website/pages/ur/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/ur/quick-start.mdx b/website/pages/ur/quick-start.mdx
index 5126122005e2..bc1a9909a23d 100644
--- a/website/pages/ur/quick-start.mdx
+++ b/website/pages/ur/quick-start.mdx
@@ -2,24 +2,26 @@
 title: فورا شروع کریں
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-اس بات کو یقینی بنائیں کہ آپ کا سب گراف کسی [تعاون یافتہ نیٹ ورک] (/developing/supported-networks) سے ڈیٹا کو ترتیب دے رہا ہے۔.
-
-یہ گائیڈ یہ فرض کرتے ہوئے لکھی گئ ہے کہ آپ کے پاس ہے:
+## شرطیں
 
 - ایک کرپٹو والیٹ
-- ایک سمارٹ کنٹریکٹ ایڈریس جو آپ کی مرضی کے نیٹ ورک پر ہے
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. سب گراف سٹوڈیو پر سب گراف بنائیں
+### 1. Create a subgraph in Subgraph Studio
 
-[سب گراف سٹوڈیو](https://thegraph.com/studio/) پر جائیں اور اپنے والیٹ کو منسلک کریں۔
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. گراف CLI انسٹال کریں
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. گراف CLI انسٹال کریں
 
 اپنی مقامی مشین پر، درج زیل کمانڈز میں سے ایک کو رن کریں:
 
@@ -35,133 +37,148 @@ npm install -g @graphprotocol/graph-cli@latest
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> آپ اپنے مخصوص سب گراف کے لیے سب گراف کے پیج پر [سب گراف سٹوڈیو](https://thegraph.com/studio/) میں کمانڈز تلاش کر سکتے ہیں.
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio<SUBGRAPH_SLUG>
+graph init
 ```
 
-> آپ اپنے مخصوص سب گراف کے لیے سب گراف کے پیج پر [سب گراف سٹوڈیو](https://thegraph.com/studio/) میں کمانڈز تلاش کر سکتے ہیں.
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-جب آپ اپنے سب گراف کو شروع کرتے ہیں, CLI ٹول درج ذیل معلومات کے لۓ آپ سے پوچھے گا:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- پروٹوکول: پروٹوکول منتخب جس سے آپ کا سب گراف ڈیٹا انڈیکس کرے گا
-- سب گراف سلگ: اپنے سب گراف کے لیےؑ نام رکھیں. آپ کا سب گراف سلگ آپ کع سب گراف کا شناخت کنندہ ہے.
-- سب گراف بنانے کے لیۓ ڈائریکٹری: اپنی مقامی ڈائریکٹری منتخب کریں
-- ایتھیریم نیٹ ورک(اختیاری): آپ کو یہ بتانے کی ضرورت ہو سکتی ہے کہ آپ کا سب گراف کس EVM سے مطابقت رکھنے والے نیٹ ورک سے ڈیٹا کو انڈیکس کرے گا
-- کنٹریکٹ ایڈریس: وہ سمارٹ کنٹریکٹ ایڈریس تلاش کریں جس سے آپ ڈیٹا کیوری کرنا چاہتے ہیں
-- ABI: اگر ABI خود بخود نہیں ہے، آپ کو اسے JSON فائل کے طور پر دستی طور پر ان پٹ کرنے کی ضرورت ہوگی
-- سٹارٹ بلاک: یہ تجویز کیا جاتا ہے کے آپ وقت بچانے کے لیۓ سٹارٹ بلاک میں ان پٹ کریں جبکہ آپ کا سب گراف بلاکچین ڈیٹا کو انڈیکس کرتا ہے۔ آپ اس بلاک کو تلاش کر کے سٹارٹ بلاک کا پتہ لگا سکتے ہیں جہاں آپ کا کنٹریکٹ تعینات کیا گیا تھا.
-- کنٹریکٹ کا نام: اپنے کنٹریکٹ کا نام درج کریں
-- کنٹریکٹ کے واقعات کو انڈیکس کریں بطور ادارے: یہ تجویز کیا جاتا ہے کہ آپ اسے درست پر سیٹ کریں کیونکہ یہ خود بخود ہر خارج ہونے والے واقع کے لیے آپ کے سب گراف میں میپنگس کا اضافہ کر دے گا۔
-- ایک اور کنٹریکٹ شامل کریں(اختیاری): آپ ایک اور کنٹریکٹ شامل کر سکتے ہیں۔
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 اپنے سب گراف کو شروع کرتے وقت کیا توقع کی جائے اس کی مثال کے لیے درج ذیل اسکرین شاٹ دیکھیں:
 
-![سب گراف کمانڈ](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-پچھلی کمانڈز ایک سکیفولڈ سب گراف بناتی ہیں جسے آپ اپنے سب گراف کی تعمیر کے لیے نقطہ آغاز کے طور پر استعمال کر سکتے ہیں۔ سب گراف میں تبدیلی کرتے وقت، آپ بنیادی طور پر تین فائلوں کے ساتھ کام کریں گے:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 ایک بار آپ کا سب گراف لکھا جائے، درج ذیل کمانڈز رن کریں:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![سب گراف لاگز](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-آپ سے ورژن کا لیبل طلب کیا جائے گا۔ `0.0.1` کی طرح ورژن بنانے کے لیے [سیمور](https://semver.org/) استعمال کرنے کی پر زور سفارش کی جاتی ہے۔ کو بتاتی ہے، آپ کسی بھی سٹرنگ کو ورژن کے طور پر منتخب کرنے کے لیے آزاد ہیں جیسے: `v1`، `version1`، `asdf`۔
-
-## 6. اپنے سب گراف کو ٹیسٹ کریں
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-لوگز آپ کو بتائیں گے اکر آپ کے سب گراف میں مسائل ہیں۔ آپریشنل سب گراف کے لوگز اس طرح کے دکھیں گے:
-
-![سب گراف لاگز](/img/subgraph-logs-image.png)
-
-اگر آپ کا سب گراف ناکام ہو رہا ہے، تو آپ GraphiQL پلے گراؤنڈ کا استعمال کر کے سب گراف کی صحت کے بارے میں کیوری کر سکتے ہیں۔ نوٹ کریں کہ آپ نیچے دیے گئے کیوری سے فائدہ اٹھا سکتے ہیں اور اپنے سب گراف کے لیے اپنی تعیناتی شناخت درج کر سکتے ہیں۔ اس صورت میں، `Qm...` تعیناتی شناخت ہے (جو **تفصیلات** کے تحت سب گراف کے پیج پر واقع ہو سکتی ہے)۔ ذیل کا کیوری آپ کو بتائے گا کہ سب گراف کب ناکام ہوجاتا ہے، لہذا آپ اس کے مطابق ڈی بگ کرسکتے ہیں:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-وہ نیٹ ورک منتخب کریں جس پر آپ اپنا سب گراف شائع کرنا چاہتے ہیں۔ Arbitrum One کے سب گراف شائع کرنے کی سفارش کی جاتی ہے تاکہ [تیز تر ٹرانزیکشن کی رفتار اور گیس کے کم اخراجات] (/arbitrum/arbitrum-faq) سے فائدہ اٹھایا جا سکے۔
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-گیس کی قیمتیں بچانے کے لیے، جب آپ اپنا سب گراف گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر شائع کرتے ہیں تو آپ اس بٹن کو منتخب کرکے اپنے سب گراف کو اسی ٹرانزیکشن میں درست کر سکتے ہیں جسے آپ نے شائع کیا تھا:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![سب گراف شائع کریں](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-اب، آپ اپنے سب گراف کی کیوریز کو اپنے سب گراف کے کیوری URL پر بھیج کر اپنے سب گراف سے کیوری کر سکتے ہیں، جسے آپ کیوری کے بٹن پر کلک کر کے تلاش کر سکتے ہیں.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-اپنے سب گراف سے ڈیٹا کیوری کرنے کے بارے میں مزید معلومات کے لیے، مزید پڑھیں [یہاں](/querying/querying-the-graph/)۔
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 796db007a169f59bb5942074bdc708b1568eeb29 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:36 -0500
Subject: [PATCH 0039/1325] New translations quick-start.mdx (Vietnamese)

---
 website/pages/vi/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/vi/quick-start.mdx b/website/pages/vi/quick-start.mdx
index d091de61071e..366aa6ebe8a4 100644
--- a/website/pages/vi/quick-start.mdx
+++ b/website/pages/vi/quick-start.mdx
@@ -2,24 +2,26 @@
 title: Bắt đầu nhanh
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-This guide is written assuming that you have:
+## Điều kiện tiên quyết
 
 - A crypto wallet
-- A smart contract address on the network of your choice
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. Create a subgraph on Subgraph Studio
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. Install the Graph CLI
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. Install the Graph CLI
 
 On your local machine, run one of the following commands:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-When you initialize your subgraph, the CLI tool will ask you for the following information:
+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
-- Subgraph slug: create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
-- Directory to create the subgraph in: choose your local directory
-- 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 autopopulated, you will need to input it manually as a JSON file
-- Start Block: it is suggested that you input the start block to save time while your subgraph indexes blockchain data. You can locate the start block by finding the block where your contract was deployed.
-- 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
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-The previous commands create a scaffold subgraph that you can use as a starting point for building your subgraph. When making changes to the subgraph, you will mainly work with three files:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 Once your subgraph is written, run the following commands:
 
+````
 ```sh
-$ graph codegen
-$ graph build
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+The CLI will ask for a version label. It's strongly recommended to use [semantic versioning](https://semver.org/), e.g. `0.0.1`.
 
-- Xác thực và triển khai subgraph của bạn. Bạn có thể tìm thấy khóa triển khai trên trang Subgraph trong Subgraph Studio.
+### 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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. Test your subgraph
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-The logs will tell you if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-To save on gas costs, you can curate your subgraph in the same transaction that you published it by selecting this button when you publish your subgraph to The Graph’s decentralized network:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-Now, you can query your subgraph by sending GraphQL queries to your subgraph’s Query URL, which you can find by clicking on the query button.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From 7aea5cac2052f8cc1645c15ca8c8d6f11debc266 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:37 -0500
Subject: [PATCH 0040/1325] New translations quick-start.mdx (Marathi)

---
 website/pages/mr/quick-start.mdx | 221 +++++++++++++++++--------------
 1 file changed, 119 insertions(+), 102 deletions(-)

diff --git a/website/pages/mr/quick-start.mdx b/website/pages/mr/quick-start.mdx
index 960c8e212b69..af229e33e695 100644
--- a/website/pages/mr/quick-start.mdx
+++ b/website/pages/mr/quick-start.mdx
@@ -2,24 +2,26 @@
 title: क्विक स्टार्ट
 ---
 
-This guide will quickly take you through how to initialize, create, and deploy your subgraph to Subgraph Studio.
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
 
-Ensure that your subgraph will be indexing data from a [supported network](/developing/supported-networks).
-
-हे मार्गदर्शक तुमच्याकडे आहे असे गृहीत धरून लिहिले आहे:
+## पूर्वतयारी
 
 - एक क्रिप्टो वॉलेट
-- तुमच्या पसंतीच्या नेटवर्कवर एक स्मार्ट करार पत्ता
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- A package manager of your choice (`npm`, `yarn` or `pnpm`)
+
+## How to Build a Subgraph
 
-## 1. सबग्राफ स्टुडिओवर सबग्राफ तयार करा
+### 1. Create a subgraph in Subgraph Studio
 
-Go to the [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
 
-Once your wallet is connected, you can begin by clicking “Create a Subgraph." It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name."
+Subgraph Studio lets you create, manage, deploy, and publish subgraphs, as well as create and manage API keys.
 
-## 2. आलेख CLI स्थापित करा
+Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
-The Graph CLI is written in TypeScript and you will need to have `node` and either `npm` or `yarn` installed to use it. Check that you have the most recent CLI version installed.
+### 2. आलेख CLI स्थापित करा
 
 तुमच्या स्थानिक मशीनवर, खालीलपैकी एक कमांड चालवा:
 
@@ -35,133 +37,148 @@ Using [yarn](https://yarnpkg.com/):
 yarn global add @graphprotocol/graph-cli
 ```
 
-## 3. Initialize your subgraph from existing contract
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
 
-Initialize your subgraph from an existing contract by running the initialize command:
+The following command initializes your subgraph from an existing contract:
 
 ```sh
-graph init --studio <SUBGRAPH_SLUG>
+graph init
 ```
 
-> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+If your contract was verified on Etherscan, then the ABI will automatically be created in the CLI.
 
-तुम्ही तुमचा सबग्राफ सुरू करता तेव्हा, CLI टूल तुम्हाला खालील माहितीसाठी विचारेल:
+When you initialize your subgraph, the CLI will ask you for the following information:
 
-- प्रोटोकॉल: तुमचा सबग्राफ 4 वरून डेटा अनुक्रमित करेल असा प्रोटोकॉल निवडा
-- सबग्राफ स्लग: तुमच्या सबग्राफसाठी नाव तयार करा. तुमचा सबग्राफ स्लग तुमच्या सबग्राफसाठी एक ओळखकर्ता आहे.
-- उपग्राफ तयार करण्यासाठी निर्देशिका: तुमची स्थानिक निर्देशिका निवडा
-- इथरियम नेटवर्क (पर्यायी): तुमचा सबग्राफ कोणत्या EVM-सुसंगत नेटवर्कवरून डेटा अनुक्रमित करेल ते तुम्हाला निर्दिष्ट करावे लागेल
-- कॉन्ट्रॅक्ट अॅड्रेस: ​​तुम्ही ज्यावरून डेटा क्वेरी करू इच्छिता तो स्मार्ट कॉन्ट्रॅक्ट अॅड्रेस शोधा
-- ABI: ABI ऑटोपॉप्युलेट नसल्यास, तुम्हाला JSON फाइल म्हणून व्यक्तिचलितपणे इनपुट करावे लागेल
-- स्टार्ट ब्लॉक: तुमचा सबग्राफ ब्लॉकचेन डेटा इंडेक्स करत असताना वेळ वाचवण्यासाठी तुम्ही स्टार्ट ब्लॉक इनपुट करा असे सुचवले जाते. तुमचा करार जिथे तैनात करण्यात आला होता तो ब्लॉक शोधून तुम्ही स्टार्ट ब्लॉक शोधू शकता.
-- कराराचे नाव: तुमच्या कराराचे नाव प्रविष्ट करा
-- इंडेक्स कॉन्ट्रॅक्ट इव्हेंट्स घटक म्हणून: असे सुचवले जाते की तुम्ही हे सत्य वर सेट करा कारण ते प्रत्येक उत्सर्जित इव्हेंटसाठी तुमच्या सबग्राफमध्ये स्वयंचलितपणे मॅपिंग जोडेल
-- दुसरा करार जोडा(पर्यायी): तुम्ही दुसरा करार जोडू शकता
+- **Protocol**: Choose the protocol your subgraph will be indexing data from.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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.
 
 तुमचा सबग्राफ सुरू करताना काय अपेक्षा करावी याच्या उदाहरणासाठी खालील स्क्रीनशॉट पहा:
 
-![Subgraph command](/img/subgraph-init-example.png)
+![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:
 
-## 4. Write your subgraph
+- Manifest (`subgraph.yaml`) - defines what data sources your subgraph will index.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
 
-मागील कमांड एक स्कॅफोल्ड सबग्राफ तयार करतात ज्याचा वापर तुम्ही तुमचा सबग्राफ तयार करण्यासाठी प्रारंभिक बिंदू म्हणून करू शकता. सबग्राफमध्ये बदल करताना, तुम्ही प्रामुख्याने तीन फाइल्ससह कार्य कराल:
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-- Manifest (`subgraph.yaml`) - The manifest defines what datasources your subgraphs will index.
-- Schema (`schema.graphql`) - The GraphQL schema defines what data you wish to retrieve from the subgraph.
-- AssemblyScript Mappings (`mapping.ts`) - This is the code that translates data from your datasources to the entities defined in the schema.
+### 5. Deploy your subgraph
 
-For more information on how to write your subgraph, see [Creating a Subgraph](/developing/creating-a-subgraph).
+Remember, deploying is not the same as publishing.
 
-## 5. Deploy to Subgraph Studio
+When you deploy a subgraph, you push it to [Subgraph Studio](https://thegraph.com/studio/), where you can test, stage and review it.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
 
 तुमचा सबग्राफ लिहिल्यानंतर, खालील आदेश चालवा:
 
+````
 ```sh
-$ आलेख कोडजेन
-$ आलेख बिल्ड
+graph codegen && graph build
 ```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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 auth --studio <DEPLOY_KEY>
-$ graph deploy --studio <SUBGRAPH_SLUG>
+graph codegen && graph build
 ```
 
-You will be asked for a version label. It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as:`v1`, `version1`, `asdf`.
-
-## 6. तुमच्या सबग्राफची चाचणी घ्या
-
-In Subgraph Studio's playground environment, you can test your subgraph by making a sample query.
-
-तुमच्या सबग्राफमध्ये काही त्रुटी असल्यास नोंदी तुम्हाला सांगतील. ऑपरेशनल सबग्राफचे लॉग यासारखे दिसतील:
-
-![Subgraph logs](/img/subgraph-logs-image.png)
-
-If your subgraph is failing, you can query the subgraph health by using the GraphiQL Playground. Note that you can leverage the query below and input your deployment ID for your subgraph. In this case, `Qm...` is the deployment ID (which can be located on the Subgraph page under **Details**). The query below will tell you when a subgraph fails, so you can debug accordingly:
-
-```graphql
-{
-  indexingStatuses(subgraphs: ["Qm..."]) {
-    node
-    synced
-    health
-    fatalError {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    nonFatalErrors {
-      message
-      block {
-        number
-        hash
-      }
-      handler
-    }
-    chains {
-      network
-      chainHeadBlock {
-        number
-      }
-      earliestBlock {
-        number
-      }
-      latestBlock {
-        number
-      }
-      lastHealthyBlock {
-        number
-      }
-    }
-    entityCount
-  }
-}
+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](/publishing/publishing-a-subgraph/).
 
-## 7. Publish your subgraph to The Graph’s Decentralized Network
+#### Adding signal to your subgraph
 
-Once your subgraph has been deployed to Subgraph Studio, you have tested it out, and you are ready to put it into production, you can then publish it to the decentralized network.
+1. To attract Indexers to query your subgraph, you should add GRT curation signal to it.
 
-In Subgraph Studio, you will be able to click the publish button on the top right of your subgraph's page.
+   - This action improves quality of service, reduces latency, and enhances network redundancy and availability for your subgraph.
 
-Select the network you would like to publish your subgraph to. It is recommended to publish subgraphs to Arbitrum One to take advantage of the [faster transaction speeds and lower gas costs](/arbitrum/arbitrum-faq).
+2. If eligible for indexing rewards, Indexers receive GRT rewards based on the signaled amount.
 
-The (upgrade Indexer)[/sunrise/#about-the-upgrade-indexer] will begin serving queries on your subgraph regardless of subgraph curation, and it will provide you with 100,000 free queries per month.
+   - 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.
 
-For a higher quality of service and stronger redundancy, you can curate your subgraph to attract more Indexers. At the time of writing, it is recommended that you curate your own subgraph with at least 3,000 GRT to ensure 3-5 additional Indexers begin serving queries on your subgraph.
+To learn more about curation, read [Curating](/network/curating/).
 
-गॅसच्या खर्चावर बचत करण्यासाठी, जेव्हा तुम्ही तुमचा सबग्राफ The Graph च्या विकेंद्रित नेटवर्कवर प्रकाशित करता तेव्हा हे बटण निवडून तुम्ही प्रकाशित केलेल्या व्यवहारात तुम्ही तुमचा सबग्राफ क्युरेट करू शकता:
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
 
-![Subgraph publish](/img/publish-and-signal-tx.png)
+![Subgraph publish](/img/studio-publish-modal.png)
 
-## 8. Query your subgraph
+### 8. Query your subgraph
 
-आता, तुम्ही तुमच्या सबग्राफच्या क्वेरी URL वर GraphQL क्वेरी पाठवून तुमच्या सबग्राफची क्वेरी करू शकता, जी तुम्ही क्वेरी बटणावर क्लिक करून शोधू शकता.
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
 
-If you don't have your API key, you can query via the free, rate-limited development query URL, which can be used for development and staging.
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
 
-For more information about querying data from your subgraph, read more [here](/querying/querying-the-graph/).
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From b35b37b13362b5f320f82bf783e69d7d707d7bd8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:38 -0500
Subject: [PATCH 0041/1325] New translations quick-start.mdx (Swahili)

---
 website/pages/sw/quick-start.mdx | 184 +++++++++++++++++++++++++++++++
 1 file changed, 184 insertions(+)
 create mode 100644 website/pages/sw/quick-start.mdx

diff --git a/website/pages/sw/quick-start.mdx b/website/pages/sw/quick-start.mdx
new file mode 100644
index 000000000000..429d4d51116f
--- /dev/null
+++ b/website/pages/sw/quick-start.mdx
@@ -0,0 +1,184 @@
+---
+title: Quick Start
+---
+
+Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
+
+## Prerequisites
+
+- A crypto wallet
+- A smart contract address on a [supported network](/developing/supported-networks/)
+- [Node.js](https://nodejs.org/) installed
+- 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".
+
+### 2. Install the Graph CLI
+
+On your local machine, run one of the following commands:
+
+Using [npm](https://www.npmjs.com/):
+
+```sh
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+Using [yarn](https://yarnpkg.com/):
+
+```sh
+yarn global add @graphprotocol/graph-cli
+```
+
+### 3. Initialize your subgraph
+
+> You can find commands for your specific subgraph on the subgraph page in [Subgraph Studio](https://thegraph.com/studio/).
+
+The `graph init` command will automatically create a scaffold of a subgraph based on your contract's events.
+
+The following command initializes your subgraph from an existing contract:
+
+```sh
+graph init
+```
+
+If your contract was verified on Etherscan, 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.
+- **Subgraph slug**: Create a name for your subgraph. Your subgraph slug is an identifier for your subgraph.
+- **Directory**: Choose a directory to create your subgraph in.
+- **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.
+- **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:
+
+![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.
+- Schema (`schema.graphql`) - defines what data you wish to retrieve from the subgraph.
+- AssemblyScript Mappings (`mapping.ts`) - translates data from your data sources to the entities defined in the schema.
+
+For a detailed breakdown on how to write your subgraph, check out [Creating a Subgraph](/developing/creating-a-subgraph/).
+
+### 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.
+
+When you publish a subgraph, you are publishing it onchain to the decentralized network.
+
+Once your subgraph is written, run the following commands:
+
+````
+```sh
+graph codegen && graph build
+```
+````
+
+Authenticate and deploy your subgraph. The deploy key can be found on the subgraph's page in Subgraph Studio.
+
+![Deploy key](/img/subgraph-studio-deploy-key.jpg)
+
+````
+```sh
+
+graph auth <DEPLOY_KEY>
+
+graph deploy <SUBGRAPH_SLUG>
+```
+````
+
+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:
+
+- Run a sample query.
+- Analyze your subgraph in the dashboard to check information.
+- Check the logs on the dashboard to see if there are any errors with your subgraph. The logs of an operational subgraph will look like this:
+
+  ![Subgraph logs](/img/subgraph-logs-image.png)
+
+### 7. Publish your subgraph to The Graph Network
+
+Publishing a subgraph to the decentralized network is an onchain action that makes your subgraph available for [Curators](/network/curating/) to curate it and [Indexers](/network/indexing/) to index it.
+
+#### Publishing with Subgraph Studio
+
+To publish your subgraph, click the Publish button in the dashboard.
+
+![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](/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](/network/curating/).
+
+To save on gas costs, you can curate your subgraph in the same transaction you publish it by selecting this option:
+
+![Subgraph publish](/img/studio-publish-modal.png)
+
+### 8. Query your subgraph
+
+You now have access to 100,000 free queries per month with your subgraph on The Graph Network!
+
+You can query your subgraph by sending GraphQL queries to its Query URL, which you can find by clicking the Query button.
+
+For more information about querying data from your subgraph, read [Querying The Graph](/querying/querying-the-graph/).

From d0426e592e7386700eb756399f98a30cdfbd3309 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:40 -0500
Subject: [PATCH 0042/1325] New translations api.mdx (Hindi)

---
 website/pages/hi/developing/graph-ts/api.mdx | 59 +++++++++++---------
 1 file changed, 32 insertions(+), 27 deletions(-)

diff --git a/website/pages/hi/developing/graph-ts/api.mdx b/website/pages/hi/developing/graph-ts/api.mdx
index 7c27b5762589..b43331af7860 100644
--- a/website/pages/hi/developing/graph-ts/api.mdx
+++ b/website/pages/hi/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: असेंबलीस्क्रिप्ट एपीआई
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> ध्यान दें: यदि आपने `graph-cli`/`graph-ts` version `0.22.0` से पहले एक subgragh बनाया है, तो आप AssemblyScript के पुराना संस्करण का उपयोग कर रहे हैं, हम अनुशंसा करते हैं कि [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-यह पृष्ठ दस्तावेज करता है कि सबग्राफ मैपिंग लिखते समय किन अंतर्निहित एपीआई का उपयोग किया जा सकता है। बॉक्स से बाहर दो प्रकार के एपीआई उपलब्ध हैं:
+यह पृष्ठ दस्तावेज करता है कि Subgraph मैपिंग लिखते समय किन अंतर्निहित एपीआई का उपयोग किया जा सकता है। बॉक्स से बाहर दो प्रकार के एपीआई उपलब्ध हैं:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The Graph TypeScript लाइब्रेरी (https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (graph-ts)
+- `graph codegen` द्वारा subgraph files से उत्पन्न code
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+आप अन्य पुस्तकालयों को भी निर्भरताओं के रूप में जोड़ सकते हैं, बशर्ते कि वे [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) के साथ संगत हों।
+
+चूंकि भाषा मैपिंग्स AssemblyScript में लिखी गई हैं, इसलिए [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) से भाषा और मानक पुस्तकालय की सुविधाओं की समीक्षा करना उपयोगी है।
 
 ## एपीआई संदर्भ
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| संस्करण | रिलीज नोट्स |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| संस्करण | रिलीज नोट्स                                                                                                                                                                                                                                   |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### अंतर्निहित प्रकार
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-अन्य संस्थाओं के साथ टकराव से बचने के लिए प्रत्येक इकाई के पास एक विशिष्ट आईडी होनी चाहिए। ईवेंट पैरामीटर के लिए एक अद्वितीय पहचानकर्ता शामिल करना काफी सामान्य है जिसका उपयोग किया जा सकता है। नोट: आईडी के रूप में लेन-देन हैश का उपयोग करना मानता है कि एक ही लेन-देन में कोई अन्य घटना इस हैश के साथ आईडी के रूप में संस्था नहीं बनाती है।
+प्रत्येक इकाई के पास एक अद्वितीय ID होनी चाहिए ताकि अन्य इकाइयों के साथ टकराव से बचा जा सके। यह काफी सामान्य है कि इवेंट पैरामीटर में एक अद्वितीय पहचानकर्ता शामिल होता है जिसका उपयोग किया जा सकता है।
+
+> नोट: लेन-देन हैश को आईडी के रूप में उपयोग करने का मतलब यह है कि उसी लेन-देन में कोई अन्य घटनाएँ इस हैश को आईडी के रूप में Entities नहीं बनाती हैं।
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+चूंकि एंटिटी स्टोर में अभी मौजूद नहीं हो सकती है, इसलिए `load` विधि `Transfer | null` प्रकार का मान लौटाती है। मान का उपयोग करने से पहले `null` मामले की जांच करना आवश्यक हो सकता है।
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> ध्यान दें: एंटिटी लोड करना तभी आवश्यक है जब मैपिंग में किए गए परिवर्तन किसी एंटिटी के पिछले डेटा पर निर्भर हों। मौजूदा एंटिटी को अपडेट करने के दो तरीकों के लिए अगला सेक्शन देखें।
 
 #### एक ब्लॉक के साथ बनाई गई संस्थाओं को देखना
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-स्टोर एपीआई उन संस्थाओं की पुनर्प्राप्ति की सुविधा देता है जो वर्तमान ब्लॉक में बनाई या अपडेट की गई थीं। इसके लिए एक विशिष्ट स्थिति यह है कि एक हैंडलर कुछ ऑन-चेन ईवेंट से लेन-देन बनाता है, और बाद में हैंडलर मौजूद होने पर इस लेनदेन तक पहुंचना चाहता है। ऐसे मामले में जहां लेन-देन मौजूद नहीं है, सबग्राफ को केवल यह पता लगाने के लिए डेटाबेस में जाना होगा कि इकाई मौजूद नहीं है; अगर सबग्राफ लेखक पहले से ही जानता है कि इकाई को उसी ब्लॉक में बनाया जाना चाहिए, तो loadInBlock का उपयोग करके इस डेटाबेस राउंडट्रिप से बचा जाता है। कुछ सबग्राफ के लिए, ये छूटे हुए लुकअप इंडेक्सिंग समय में महत्वपूर्ण योगदान दे सकते हैं।
+स्टोर एपीआई वर्तमान ब्लॉक में बनाए गए या अपडेट किए गए Entities को पुनः प्राप्त करने की सुविधा प्रदान करता है। इस स्थिति में एक हैंडलर किसी ऑन-चेन घटना से एक लेन-देन बनाता है, और एक बाद वाला हैंडलर चाहता है कि यदि यह लेन-देन मौजूद है, तो वह इसे एक्सेस कर सके।
+
+- यदि लेन-देन मौजूद नहीं है, तो subgraph को केवल यह पता लगाने के लिए डेटाबेस में जाना होगा कि Entity मौजूद नहीं है। यदि subgraph लेखक पहले से जानता है कि Entity उसी ब्लॉक में बनाई जानी चाहिए थी, तो `loadInBlock` का उपयोग इस डेटाबेस राउंडट्रिप से बचाता है।
+- कुछ subgraphs के लिए, ये छूटे हुए लुकअप्स indexing समय में महत्वपूर्ण योगदान दे सकते हैं।
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ As long as the `ERC20Contract` on Ethereum has a public read-only function calle
 
 #### रिवर्टेड कॉल्स को हैंडल करना
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+यदि आपके अनुबंध के केवल-पढ़ने वाले तरीके वापस हो सकते हैं, तो आपको इसे `try_` से पूर्व निर्धारित अनुबंध विधि को कॉल करके संभालना चाहिए।
+
+- उदाहरण के लिए, Gravity कॉन्ट्रैक्ट `gravatarToOwner` मेथड को उजागर करता है। यह कोड उस मेथड में एक रिवर्ट को संभालने में सक्षम होगा:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-ध्यान दें कि Geth या Infura क्लाइंट से जुड़ा एक ग्राफ़ नोड सभी रिवर्ट का पता नहीं लगा सकता है, अगर आप इस पर भरोसा करते हैं तो हम पैरिटी क्लाइंट से जुड़े ग्राफ़ नोड का उपयोग करने की सलाह देते हैं।
+> नोट: एक Graph नोड जो Geth या Infura क्लाइंट से जुड़ा है, सभी रिवर्ट का पता नहीं लगा सकता है। यदि आप इस पर निर्भर करते हैं, तो हम Parity क्लाइंट से जुड़े Graph नोड का उपयोग करने की सिफारिश करते हैं।
 
 #### एन्कोडिंग/डिकोडिंग एबीआई
 
@@ -540,7 +549,7 @@ let decoded = ethereum.decode('(address,uint256)', encoded)
 
 - [ABI Spec](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
 - Encoding/decoding [Rust library/CLI](https://github.com/rust-ethereum/ethabi)
-- More [complex example](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
+- ज्यादा जटिल उदाहरण (https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
 
 #### Balance of an Address
 
@@ -586,11 +595,7 @@ The `log` API includes the following functions:
 The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
 
 ```typescript
-log.info('संदेश प्रदर्शित किया जाना है: {}, {}, {}', [
-  value.toString(),
-  OtherValue.toString(),
-  'पहले से ही एक स्ट्रिंग',
-])
+log.info ('संदेश प्रदर्शित किया जाना है: {}, {}, {}', [value.toString (), OtherValue.toString (), 'पहले से ही एक स्ट्रिंग'])
 ```
 
 #### एक या अधिक मान लॉग करना

From 52d08742c99cb16833989ba244a0b7f889e5f998 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:41 -0500
Subject: [PATCH 0043/1325] New translations
 substreams-powered-subgraphs-faq.mdx (Russian)

---
 .../ru/developing/substreams-powered-subgraphs-faq.mdx    | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ru/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ru/developing/substreams-powered-subgraphs-faq.mdx
index f71be80fe729..4d6d97dd686f 100644
--- a/website/pages/ru/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/ru/developing/substreams-powered-subgraphs-faq.mdx
@@ -4,7 +4,7 @@ title: Часто задаваемые вопросы о субграфах, р
 
 ## Что такое субпотоки?
 
-Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere.
+Substreams (Субпотоки), разработанные [StreamingFast](https://www.streamingfast.io/), представляют собой исключительно мощный механизм обработки, способный потреблять обширные потоки блокчейн-данных. Субпотоки позволяют оптимизировать и формировать данные блокчейна для быстрого и бесперебойного использования приложениями конечных пользователей. В частности, Субпотоки - это независимый от блокчейна, распараллеленный и ориентированный на потоковую передачу движок, служащий в качестве уровня преобразования данных блокчейна. Работая на базе [Firehose](https://firehose.streamingfast.io), он позволяет разработчикам писать модули на языке Rust, использовать модули сообщества,обеспечивать крайне высокую производительность индексирования и [отправлять](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) свои данные в любое место.
 
 Go to the [Substreams Documentation](/substreams) to learn more about Substreams.
 
@@ -22,7 +22,7 @@ Go to the [Substreams Documentation](/substreams) to learn more about Substreams
 
 ## Каковы преимущества использования субграфов, работающих на основе Субпотоков?
 
-Substreams-powered subgraphs combine all the benefits of Substreams with the queryability of subgraphs. They bring greater composability and high-performance indexing to The Graph. They also enable new data use cases; for example, once you've built your Substreams-powered Subgraph, you can reuse your [Substreams modules](https://substreams.streamingfast.io/documentation/develop/manifest-modules) to output to different [sinks](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) such as PostgreSQL, MongoDB, and Kafka.
+Субграфы, работающие на основе Субпотоков, сочетают в себе все преимущества Субпотоков с возможностью запроса субграфов.Они обеспечивают более высокую совместимость и высокопроизводительное индексирование в The Graph. Они также позволяют создавать новые варианты использования данных; например, после того, как Вы создали свой субграф на базе Субпотоков, Вы можете повторно использовать свои [модули Субпотоков](https://substreams.streamingfast.io/documentation/develop/manifest-modules) для вывода в разные [приёмники](https://substreams.streamingfast.io/reference-and-specs/manifests#sink), такие как PostgreSQL, MongoDB и Kafka.
 
 ## В чем преимущества Субпотоков?
 
@@ -66,13 +66,13 @@ The [Substreams documentation](/substreams) will teach you how to build Substrea
 
 В документации [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) показано, как упаковать их для развертывания в The Graph.
 
-The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code.
+[Новейший инструмент Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) позволит Вам загрузить проект Substreams без использования какого-либо кода.
 
 ## Какова роль модулей Rust в Субпотоках?
 
 Модули Rust - это эквивалент мапперов AssemblyScript в субграфах. Они компилируются в WASM аналогичным образом, но модель программирования допускает параллельное выполнение. Они определяют, какие преобразования и агрегации необходимо применить к необработанным данным блокчейна.
 
-See [modules documentation](https://substreams.streamingfast.io/documentation/develop/manifest-modules) for details.
+Подробную информацию см. в [документации по модулям](https://substreams.streamingfast.io/documentation/develop/manifest-modules).
 
 ## Что делает Субпотоки компонуемыми?
 

From 626ecc6951e4ac1d7cfbe8042d75d893ac080007 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:42 -0500
Subject: [PATCH 0044/1325] New translations tap.mdx (Hindi)

---
 website/pages/hi/tap.mdx | 128 +++++++++++++++++++--------------------
 1 file changed, 64 insertions(+), 64 deletions(-)

diff --git a/website/pages/hi/tap.mdx b/website/pages/hi/tap.mdx
index 0a41faab9c11..8ae86546431a 100644
--- a/website/pages/hi/tap.mdx
+++ b/website/pages/hi/tap.mdx
@@ -1,102 +1,102 @@
 ---
-title: TAP Migration Guide
+title: TAP माइग्रेशन गाइड
 ---
 
-Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
+The Graph के नए भुगतान प्रणाली, Timeline Aggregation Protocol, TAP के बारे में जानें। यह प्रणाली तेज, कुशल माइक्रोट्रांजेक्शन प्रदान करती है जिसमें विश्वास को न्यूनतम किया गया है।
 
-## Overview
+## अवलोकन
 
-[TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
+[TAP](https://docs.rs/tap_core/latest/tap_core/index.html) मौजूदा Scalar भुगतान प्रणाली का एक ड्रॉप-इन प्रतिस्थापन है। यह निम्नलिखित प्रमुख सुविधाएँ प्रदान करता है:
 
-- Efficiently handles micropayments.
-- Adds a layer of consolidations to on-chain transactions and costs.
-- Allows Indexers control of receipts and payments, guaranteeing payment for queries.
-- It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
+- सूक्ष्म भुगतानों को कुशलता से संभालता है।
+- ऑन-चेन लेनदेन और लागतों में समेकनों की एक परत जोड़ता है।
+- प्राप्तियों और भुगतान पर Indexers को नियंत्रण की अनुमति देता है, प्रश्नों के लिए भुगतान की गारंटी देता है।
+- यह विकेन्द्रीकृत, विश्वास रहित गेटवे को सक्षम बनाता है और कई भेजने वालों के लिए indexer-service के प्रदर्शन में सुधार करता है।
 
-## Specifics
+## विशिष्टताएँ
 
-TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
+TAP एक प्रेषक को एक प्राप्तकर्ता को कई भुगतान करने की अनुमति देता है, TAP Receipts, जो इन भुगतानों को एकल भुगतान में एकत्र करता है, जिसे Receipt Aggregate Voucher भी कहा जाता है, जिसे RAV के नाम से भी जाना जाता है। यह एकत्रित भुगतान फिर ब्लॉकचेन पर सत्यापित किया जा सकता है, लेनदेन की संख्या को कम करता है और भुगतान प्रक्रिया को सरल बनाता है।
 
-For each query, the gateway will send you a `signed receipt` that is stored on your database. Then, these queries will be aggregated by a `tap-agent` through a request. Afterwards, you’ll receive a RAV. You can update a RAV by sending it with newer receipts and this will generate a new RAV with an increased value.
+प्रत्येक क्वेरी के लिए, गेटवे आपको एक साइन किए गए रिसिप्ट भेजेगा जिसे आपके डेटाबेस में संग्रहीत किया जाएगा। फिर, इन क्वेरियों को एक अनुरोध के माध्यम से एक टेप-एजेंट द्वारा समेकित किया जाएगा। इसके बाद, आपको एक RAV प्राप्त होगा। आप नए रिसिप्ट्स के साथ इसे भेजकर RAV को अपडेट कर सकते हैं और इससे एक नया RAV उत्पन्न होगा जिसमें बढ़ी हुई राशि होगी।
 
-### RAV Details
+### RAV विवरण
 
-- It’s money that is waiting to be sent to the blockchain.
+- यह वह पैसा है जो ब्लॉकचेन पर भेजे जाने का इंतजार कर रहा है।
 
-- It will continue to send requests to aggregate and ensure that the total value of non-aggregated receipts does not exceed the `amount willing to lose`.
+- यह जारी रखेगा अनुरोध भेजना ताकि यह सुनिश्चित किया जा सके कि गैर-एकत्रित रसीदों का कुल मूल्य 'amount willing to lose' से अधिक न हो।
 
-- Each RAV can be redeemed once in the contracts, which is why they are sent after the allocation is closed.
+- प्रत्येक RAV को अनुबंधों में एक बार भुनाया जा सकता है, यही कारण है कि इन्हें आवंटन बंद होने के बाद भेजा जाता है।
 
-### Redeeming RAV
+### RAV का उपयोग करना
 
-As long as you run `tap-agent` and `indexer-agent`, everything will be executed automatically. The following provides a detailed breakdown of the process:
+जब तक आप tap-agent और indexer-agent को चलाते हैं, सब कुछ स्वचालित रूप से निष्पादित होगा। निम्नलिखित प्रक्रिया का विस्तृत विवरण प्रदान करता है:
 
-1. An Indexer closes allocation.
+1. एक Indexer आवंटन बंद करता है।
 
-2. `<recently-closed-allocation-buffer> period, tap-agent` takes all pending receipts for that specific allocation and requests an aggregation into a RAV, marking it as `last`.
+2. <recently-closed-allocation-buffer> अवधि, tap-agent सभी लंबित प्राप्तियों को उस विशेष आवंटन के लिए लेता है और एक RAV में समेकन के लिए अनुरोध करता है, इसे 'last' के रूप में चिह्नित करता है।
 
-3. `indexer-agent` takes all the last RAVS and sends redeem requests to the blockchain, which will update the value of `redeem_at`.
+3. indexer-agent सभी पिछले RAVS लेता है और ब्लॉकचेन को रिडीम अनुरोध भेजता है, जो redeem_at के मान को अपडेट करेगा।
 
-4. During the `<finality-time>` period, `indexer-agent` monitors if the blockchain has any reorganizations that revert the transaction.
+4. <finality-time> अवधि के दौरान, indexer-agent यह देखता है कि क्या ब्लॉकचेन में कोई पुनर्गठन है जो लेनदेन को पूर्ववत करता है।
 
-   - If it was reverted, the RAV is resent to the blockchain. If it was not reverted, it gets marked as `final`.
+   - यदि इसे रिवर्ट किया गया, तो RAV को फिर से ब्लॉकचेन पर भेजा जाता है। यदि इसे रिवर्ट नहीं किया गया, तो इसे final के रूप में चिह्नित किया जाता है।
 
-## Blockchain Addresses
+## ब्लॉकचेन पते(Addresses)
 
-### Contracts
+### contract
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
-### Gateway
+### गेटवे 
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
-| ---------- | --------------------------------------------- | --------------------------------------------- |
-| Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
-| Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
-| Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
+| घटक               | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
+| ----------------- | --------------------------------------------- | --------------------------------------------- |
+| प्रेषक            | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
+| हस्ताक्षरकर्ता    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
+| संकेन्द्रीयकर्ता  | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
 ### Requirements
 
-In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
+एक Indexer चलाने की सामान्य आवश्यकताओं के अलावा, आपको TAP अपडेट को क्वेरी करने के लिए एक tap-escrow-subgraph एंडपॉइंट की आवश्यकता होगी। आप TAP को क्वेरी करने के लिए The Graph Network का उपयोग कर सकते हैं या अपने graph-node पर स्वयं होस्ट कर सकते हैं।
 
 - [Graph TAP Aribtrum Sepolia subgraph (for The Graph testnet)](https://thegraph.com/explorer/subgraphs/7ubx365MiqBH5iUz6XWXWT8PTof5BVAyEzdb8m17RvbD)
 - [Graph TAP Arbitrum One subgraph (for The Graph mainnet)](https://thegraph.com/explorer/subgraphs/4sukbNVTzGELnhdnpyPqsf1QqtzNHEYKKmJkgaT8z6M1)
 
-> Note: `indexer-agent` does not currently handle the indexing of this subgraph like it does for the network subgraph deployement. As a result, you have to index it manually.
+> टिप्पणी:indexer-agent वर्तमान में इस subgraph की indexing को वैसे हैंडल नहीं करता जैसे वह network subgraph deployment के लिए करता है। इसके परिणामस्वरूप, आपको इसे मैन्युअली इंडेक्स करना होगा।
 
-## Migration Guide
+## माइग्रेशन गाइड
 
-### Software versions
+### सॉफ़्टवेयर संस्करण
 
 The required software version can be found [here](https://github.com/graphprotocol/indexer/blob/main/docs/networks/arbitrum-one.md#latest-releases).
 
-### Steps
+### कदम
 
-1. **Indexer Agent**
+1. **Indexer एजेंट**
 
-   - Follow the [same process](https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components).
-   - Give the new argument `--tap-subgraph-endpoint` to activate the new TAP codepaths and enable redeeming of TAP RAVs.
+   - उसी प्रक्रिया का पालन करें'(https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components).
+   - नया तर्क --tap-subgraph-endpoint दें ताकि नए TAP कोडपाथ्स को सक्रिय किया जा सके और TAP RAVs को रिडीम करने की अनुमति मिल सके।
 
-2. **Indexer Service**
+2. **Indexer सेवा**
 
-   - Fully replace your current configuration with the [new Indexer Service rs](https://github.com/graphprotocol/indexer-rs). It's recommend that you use the [container image](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs).
-   - Like the older version, you can scale Indexer Service horizontally easily. It is still stateless.
+   - अपने वर्तमान कॉन्फ़िगरेशन को पूरी तरह से new Indexer Service rs (https://github.com/graphprotocol/indexer-rs). से बदलें। यह सुझाव दिया गया है कि आप container image (https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs). का उपयोग करें।
+   - पुरानी संस्करण की तरह, आप Indexer Service को आसानी से क्षैतिज रूप से स्केल कर सकते हैं। यह अभी भी stateless है।
 
-3. **TAP Agent**
+3. **TAP एजेंट**
 
-   - Run _one_ single instance of [TAP Agent](https://github.com/graphprotocol/indexer-rs) at all times. It's recommend that you use the [container image](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs).
+   - हमेशा एक ही उदाहरण चलाएँ TAP Agent (https://github.com/graphprotocol/indexer-rs)। यह सिफारिश की जाती है कि आप container image (https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs). का उपयोग करें।
 
-4. **Configure Indexer Service and TAP Agent**
+4. इंडेक्सर सेवा और TAP एजेंट कॉन्फ़िगर करें
 
-   Configuration is a TOML file shared between `indexer-service` and `tap-agent`, supplied with the argument `--config /path/to/config.toml`.
+   कॉन्फ़िगरेशन एक TOML फ़ाइल है जो indexer-service और tap-agent के बीच साझा की जाती है, जो --config /path/to/config.toml तर्क के साथ प्रदान की जाती है।
 
-   Check out the full [configuration](https://github.com/graphprotocol/indexer-rs/blob/main/config/maximal-config-example.toml) and the [default values](https://github.com/graphprotocol/indexer-rs/blob/main/config/default_values.toml)
+   पूरा configuration (https://github.com/graphprotocol/indexer-rs/blob/main/config/maximal-config-example.toml)और default values (https://github.com/graphprotocol/indexer-rs/blob/main/config/default_values.toml) देखें।
 
-For minimal configuration, use the following template:
+"कम से कम कॉन्फ़िगरेशन के लिए, निम्नलिखित टेम्पलेट का उपयोग करें:"
 
 ```bash
 # You will have to change *all* the values below to match your setup.
@@ -168,26 +168,26 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+टिप्पणियाँ:
 
-- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
-- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
+- tap.sender_aggregator_endpoints के लिए मान gateway section (/tap/#gateway). में पाए जा सकते हैं।
+- blockchain.receipts_verifier_address के लिए मानों का उपयोग उचित तरीके से Blockchain addresses section (/tap/#contracts)  के अनुसार किया जाना चाहिए, जिसमें उचित चेन आईडी का उपयोग किया गया है।
 
-**Log Level**
+**लॉग स्तर**
 
-- You can set the log level by using the `RUST_LOG` environment variable.
-- It’s recommended that you set it to `RUST_LOG=indexer_tap_agent=debug,info`.
+- आप लॉग स्तर को RUST_LOG एनवायरनमेंट वेरिएबल का उपयोग करके सेट कर सकते हैं।
+- यह अनुशंसा की जाती है कि आप इसे RUST_LOG=indexer_tap_agent=debug,info पर सेट करें।
 
-## Monitoring
+## निगरानी
 
-### Metrics
+### मेट्रिक्स
 
-All components expose the port 7300 to be queried by prometheus.
+सभी घटक पोर्ट 7300 को प्रदर्शित करते हैं जिसे prometheus द्वारा क्वेरी किया जा सकता है।
 
-### Grafana Dashboard
+### Grafana डैशबोर्ड
 
-You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) and import.
+आप Grafana Dashboard (https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json)  डाउनलोड कर सकते हैं और इम्पोर्ट कर सकते हैं।
 
-### Launchpad
+### लॉन्चपैड
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+वर्तमान में, indexer-rs और tap-agent का एक WIP संस्करण है जो यहाँ पाया जा सकता है यहां (https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 6e610f84414f62dcab086de1210c5fcaf0096683 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:43 -0500
Subject: [PATCH 0045/1325] New translations multiple-networks.mdx (Turkish)

---
 .../pages/tr/deploying/multiple-networks.mdx  | 96 +++++++++----------
 1 file changed, 48 insertions(+), 48 deletions(-)

diff --git a/website/pages/tr/deploying/multiple-networks.mdx b/website/pages/tr/deploying/multiple-networks.mdx
index dc2b8e533430..0394197d25f9 100644
--- a/website/pages/tr/deploying/multiple-networks.mdx
+++ b/website/pages/tr/deploying/multiple-networks.mdx
@@ -1,37 +1,37 @@
 ---
-title: Deploying a Subgraph to Multiple Networks
+title: Bir Subgraph'i Birden Fazla Ağda Dağıtma
 ---
 
-This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
+Bu sayfa, bir subgraph'i birden fazla ağda nasıl dağıtacağınızı açıklar. Bir subgraph'i dağıtmak için öncelikle [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)'yi yüklemeniz gerekir. Henüz bir subgraph oluşturmadıysanız, [Subgraph Oluşturma](/developing/creating-a-subgraph) bölümüne bakın.
 
-## Deploying the subgraph to multiple networks
+## Subgraph'i Birden Fazla Ağda Dağıtma
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+Bazı durumlarda, tüm kodu tekrarlamak zorunda olmadan aynı subgraph'i birden fazla ağda yayına almak isteyebilirsiniz. Bunu yapmaktaki temel zorluk, sözleşme kodu tamamen aynı olsa dahi, farklı ağlardaki sözleşme adreslerinin farklı olmasıdır.
 
-### Using `graph-cli`
+### `graph-cli` Kullanarak
 
-Both `graph build` (since `v0.29.0`) and `graph deploy` (since `v0.32.0`) accept two new options:
+Hem `graph build` (`v0.29.0`'dan itibaren) hem de `graph deploy` (`v0.32.0`'dan itibaren) komutları iki yeni seçeneği kabul eder:
 
 ```sh
-Options:
+Seçenekler:
 
       ...
-      --network <name>          Network configuration to use from the networks config file
-      --network-file <path>     Networks config file path (default: "./networks.json")
+      --network <name>          Ağ yapılandırmasını networks config dosyasını kullanarak yapmak için
+      --network-file <path>     Ağ yapılandırma dosya yolu (varsayılan: "./networks.json")
 ```
 
-You can use the `--network` option to specify a network configuration from a `json` standard file (defaults to `networks.json`) to easily update your subgraph during development.
+`--network` seçeneğini, geliştirme sırasında subgraph'inizi kolayca güncellemek amacıyla, bir `json` standart dosyası kullanarak bir ağ yapılandırması belirlemek için kullanabilirsiniz. (Varsayılan olarak `networks.json` dosyasını kullanır.)
 
-> Note: The `init` command will now auto-generate a `networks.json` based on the provided information. You will then be able to update existing or add additional networks.
+> Not: Artık, `init` komutu, sağlanan bilgilere dayanarak otomatik olarak bir `networks.json` dosyası oluşturmaktadır. Daha sonra mevcut ağları güncelleyebilir veya yeni ağlar ekleyebilirsiniz.
 
-If you don't have a `networks.json` file, you'll need to manually create one with the following structure:
+Eğer bir `networks.json` dosyanız yoksa, aşağıdaki yapı ile manuel olarak oluşturmanız gerekecek:
 
 ```json
 {
-    "network1": { // the network name
-        "dataSource1": { // the dataSource name
-            "address": "0xabc...", // the contract address (optional)
-            "startBlock": 123456 // the startBlock (optional)
+    "network1": { // ağ adı
+        "dataSource1": { //veri kaynağı adı
+            "address": "0xabc...", // sözleşme adresi (isteğe bağlı)
+            "startBlock": 123456 // başlangıç bloku (isteğe bağlı)
         },
         "dataSource2": {
             "address": "0x123...",
@@ -52,9 +52,9 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 }
 ```
 
-> Note: You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
+> Not: Yapılandırma dosyasında `templates` (şablonlar, eğer varsa) kısmını doldurmanıza gerek yoktur, yalnızca `dataSources` (veri kaynaklarını) belirtmelisiniz. Eğer `subgraph.yaml` dosyasında `templates` kısmı tanımlanmışsa, bunların ağı `--network` seçeneği ile belirtilen ağa otomatik olarak güncellenecektir.
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `sepolia` networks, and this is your `subgraph.yaml`:
+Şimdi, subgraph'inizi `mainnet` ve `sepolia` ağlarında dağıtmak istediğinizi varsayalım ve `subgraph.yaml` dosyanız aşağıdaki gibi olsun\`:
 
 ```yaml
 # ...
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Ağ yapılandırma dosyanız şu şekilde olmalıdır:
 
 ```json
 {
@@ -86,17 +86,17 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Şimdi aşağıdaki komutlardan birini çalıştırabilirsiniz:
 
 ```sh
-# Using default networks.json file
+# Varsayılan networks.json dosyasını kullanarak
 yarn build --network sepolia
 
-# Using custom named file
+# Özel adlandırılmış bir dosya kullanarak
 yarn build --network sepolia --network-file path/to/config
 ```
 
-The `build` command will update your `subgraph.yaml` with the `sepolia` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+`build` komutu, `subgraph.yaml` dosyanızı `sepolia` yapılandırmasıyla güncelleyip ardından subgraph'i yeniden derleyecektir. `subgraph.yaml` dosyanız artık şöyle görünmelidir:
 
 ```yaml
 # ...
@@ -111,23 +111,23 @@ dataSources:
       kind: ethereum/events
 ```
 
-Now you are ready to `yarn deploy`.
+Artık `yarn deploy` komutunu çalıştırmaya hazırsınız.
 
-> Note: As mentioned earlier, since `graph-cli 0.32.0` you can directly run `yarn deploy` with the `--network` option:
+> Not: Daha önce de belirtildiği gibi, `graph-cli 0.32.0` sürümünden itibaren `yarn deploy` komutunu doğrudan `--network` seçeneğiyle çalıştırabilirsiniz:
 
 ```sh
-# Using default networks.json file
+# Varsayılan networks.json dosyasını kullanarak
 yarn deploy --network sepolia
 
-# Using custom named file
+# Özel adlandırılmış bir dosya kullanarak
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### <code>subgraph.yaml</code> şablonunu kullanarak:
 
-One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
+Daha eski `graph-cli` sürümlerini kullanarak kontrat adresleri gibi unsurları parametrize etmenin bir yolu, bunların bir kısmını [Mustache](https://mustache.github.io/) veya [Handlebar](https://handlebarsjs.com/) gibi bir şablonlama sistemiyle oluşturmaktır.
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Sepolia using different contract addresses. You could then define two config files providing the addresses for each network:
+Bu yaklaşımı açıklamak için, bir subgraph'in mainnet ve Sepolia ağlarına farklı sözleşme adresleri ile dağıtılması gerektiğini varsayalım. Her ağ için adresleri sağlayan iki yapılandırma dosyası tanımlayabilirsiniz:
 
 ```json
 {
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+ve
 
 ```json
 {
@@ -145,7 +145,7 @@ and
 }
 ```
 
-Along with that, you would substitute the network name and addresses in the manifest with variable placeholders `{{network}}` and `{{address}}` and rename the manifest to e.g. `subgraph.template.yaml`:
+Bununla birlikte, ağ adını ve adresleri manifesto içinde `{{network}}` ve `{{address}}` gibi değişken yer tutucularla değiştirir ve manifestoyu örneğin `subgraph.template.yaml` olarak yeniden adlandırırsınız:
 
 ```yaml
 # ...
@@ -162,7 +162,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-In order to generate a manifest to either network, you could add two additional commands to `package.json` along with a dependency on `mustache`:
+Her iki ağ için de bir manifesto oluşturmak amacıyla, `package.json` dosyasına `mustache` gereksinimiyle birlikte iki ek komut ekleyebilirsiniz:
 
 ```json
 {
@@ -179,7 +179,7 @@ In order to generate a manifest to either network, you could add two additional
 }
 ```
 
-To deploy this subgraph for mainnet or Sepolia you would now simply run one of the two following commands:
+Bu subgraph'i mainnet veya Sepolia üzerinde yayına almak için artık aşağıdaki iki komuttan birini çalıştırabilirsiniz:
 
 ```sh
 # Mainnet:
@@ -189,29 +189,29 @@ yarn prepare:mainnet && yarn deploy
 yarn prepare:sepolia && yarn deploy
 ```
 
-A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
+Bunun çalışan bir örneğini [burada](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759) bulabilirsiniz.
 
-**Note:** This approach can also be applied to more complex situations, where it is necessary to substitute more than contract addresses and network names or where generating mappings or ABIs from templates as well.
+**Not**: Bu yaklaşım, sözleşme adresleri ve ağ adlarının ötesinde daha fazla değişiklik yapmanın, veya şablonlardan mapping ya da ABI'ler oluşturmanın gerekli olduğu, daha karmaşık durumlara da uygulanabilir.
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+Bu işlem, subgraph'inizin geride kalıp kalmadığını kontrol etmek için `chainHeadBlock` değerini subgraph'inizdeki `latestBlock` ile karşılaştırmanızı sağlar. `synced`, subgraph'in zincire daha önce hiç yetişip yetişmediğini belirtir. `health` ise şu anda hata olmadığında `healthy` ve bir hata nedeniyle subgraph'in ilerlemesi durduğunda `failed` değerlerini alabilir. Bu durumda, hataya dair ayrıntılar için `fatalError` alanını kontrol edebilirsiniz.
 
-## Subgraph Studio subgraph archive policy
+## Subgraph Studio Subgraph Arşivleme Politikası
 
-A subgraph version in Studio is archived if and only if it meets the following criteria:
+Studio’daki bir subgraph sürümü yalnızca aşağıdaki kriterleri karşılaması durumunda arşivlenir:
 
-- The version is not published to the network (or pending publish)
-- The version was created 45 or more days ago
-- The subgraph hasn't been queried in 30 days
+- Sürüm ağa yayımlanmamıştır (veya yayım askıda kalmıştır)
+- Sürüm, 45 gün veya daha uzun bir süre önce oluşturulmuştur
+- Subgraph son 30 gündür sorgulanmamıştır
 
-In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
+Ek olarak, yeni bir sürüm yayına alındığında, eğer subgraph yayımlanmadıysa, subgraph’in N-2 sürümü arşivlenir.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Bu politika kapsamında etkilenen her subgraph, ilgili sürümü geri getirme seçeneğine sahiptir.
 
-## Checking subgraph health
+## Subgraph durumunu kontrol etme
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Bir subgraph'in başarıyla senkronize olması, sonsuza kadar sorunsuz çalışmaya devam edeceğine dair iyi bir işarettir. Ancak, ağdaki yeni tetikleyiciler subgraph'inizin test edilmemiş bir hata durumuna düşmesine neden olabilir, veya performans sorunları ya da düğüm operatörlerindeki sorunlar nedeniyle subgraph geride kalmaya başlayabilir.
 
-Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+Graph Düğümü, subgraph'inizin durumunu kontrol etmek için sorgu yapabileceğiniz bir GraphQL uç noktası sunar. Sağlayıcı hizmetinde bu uç nokta `https://api.thegraph.com/index-node/graphql` adresinde bulunmaktadır. Yerel bir düğümde ise varsayılan olarak `8030/graphql` portunda erişilebilir. Bu uç noktanın tam şemasına [buradan](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql) ulaşabilirsiniz. İşte bir subgraph'in güncel sürümünün durumunu kontrol eden örnek bir sorgu:
 
 ```graphql
 {
@@ -238,4 +238,4 @@ Graph Node exposes a GraphQL endpoint which you can query to check the status of
 }
 ```
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+Bu işlem, subgraph'inizin geride kalıp kalmadığını kontrol etmek için `chainHeadBlock` değerini subgraph'inizdeki `latestBlock` ile karşılaştırmanızı sağlar. `synced`, subgraph'in zincire daha önce hiç yetişip yetişmediğini belirtir. `health` ise şu anda hata olmadığında `healthy` ve bir hata nedeniyle subgraph'in ilerlemesi durduğunda `failed` değerlerini alabilir. Bu durumda, hataya dair ayrıntılar için `fatalError` alanını kontrol edebilirsiniz.

From 8a7ee6411a9a425679ed1e4b172d97624179cdbf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:44 -0500
Subject: [PATCH 0046/1325] New translations transfer-a-subgraph.mdx (Turkish)

---
 .../pages/tr/managing/transfer-a-subgraph.mdx | 59 ++++++-------------
 1 file changed, 18 insertions(+), 41 deletions(-)

diff --git a/website/pages/tr/managing/transfer-a-subgraph.mdx b/website/pages/tr/managing/transfer-a-subgraph.mdx
index c4060284d5d9..78f649b0e669 100644
--- a/website/pages/tr/managing/transfer-a-subgraph.mdx
+++ b/website/pages/tr/managing/transfer-a-subgraph.mdx
@@ -1,65 +1,42 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Bir Subgraph’i Transfer Etme
 ---
 
-## Transferring ownership of a subgraph
+Merkeziyetsiz ağda yayımlanan subgraph’ler, NFT olarak oluşturulup subgraph’i yayımlayan adrese gönderilir. Bu NFT, The Graph Ağı’ndaki hesaplar arasında transferi kolaylaştıran standart bir ERC721 sözleşmesini temel alır.
 
-Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+## Hatırlatmalar
 
-**Please note the following:**
+- NFT’ye sahip olan kişi, subgraph’in kontrolünü elinde tutar.
+- NFT’nin sahibi NFT’yi satmaya veya transfer etmeye karar verirse, artık bu subgraph’i ağ üzerinde düzenleyemez veya güncelleyemez.
+- Subgraph kontrolünü kolayca bir multi-sig cüzdana taşıyabilirsiniz.
+- Bir topluluk üyesi, bir DAO adına subgraph oluşturabilir.
 
-- Whoever owns the NFT controls the subgraph.
-- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
-- You can easily move control of a subgraph to a multi-sig.
-- A community member can create a subgraph on behalf of a DAO.
+## Subgraph’inizi NFT Olarak Görüntüleyin
 
-### View your subgraph as an NFT
-
-To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+Subgraph’inizi bir NFT olarak görüntülemek için, **OpenSea** gibi bir NFT pazar yerini ziyaret edebilirsiniz:
 
 ```
 https://opensea.io/your-wallet-address
 ```
 
-Or a wallet explorer like **Rainbow.me**:
+Ya da **Rainbow.me** gibi bir cüzdan gezgini kullanabilirsiniz:
 
 ```
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
-
-To transfer ownership of a subgraph, do the following:
-
-1.  Use the UI built into Subgraph Studio:
-
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
-
-2.  Choose the address that you would like to transfer the subgraph to:
-
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
-
-Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
-
-![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
+## Adım Adım
 
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+Bir subgraph’in sahipliğini transfer etmek için şu adımları izleyin:
 
-### Step-by-Step
+1. Subgraph Studio’ya entegre edilmiş kullanıcı arayüzünü kullanın:
 
-To deprecate your subgraph, do the following:
+   ![Subgraph Sahipliği Transferi](/img/subgraph-ownership-transfer-1.png)
 
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
+2. Subgraph’i transfer etmek istediğiniz adresi seçin:
 
-**Please note the following:**
+   ![Subgraph Sahipliği Transferi](/img/subgraph-ownership-transfer-2.png)
 
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
+Alternatif olarak, OpenSea gibi NFT pazar yerlerinin entegre kullanıcı arayüzünü de kullanabilirsiniz:
 
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
+![NFT Pazar Yerinden Subgraph Sahipliği Transferi](/img/subgraph-ownership-transfer-nft-marketplace.png)

From 044160c781e9a8accac492f123a9aa2fcad16f7c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:45 -0500
Subject: [PATCH 0047/1325] New translations deploy-using-subgraph-studio.mdx
 (Turkish)

---
 .../deploy-using-subgraph-studio.mdx          | 136 +++++++++---------
 1 file changed, 67 insertions(+), 69 deletions(-)

diff --git a/website/pages/tr/deploying/deploy-using-subgraph-studio.mdx b/website/pages/tr/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..eaca0a81f65f 100644
--- a/website/pages/tr/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/tr/deploying/deploy-using-subgraph-studio.mdx
@@ -1,139 +1,137 @@
 ---
-title: Deploy Using Subgraph Studio
+title: Subgraph Studio Kullanarak Dağıtma
 ---
 
-Learn how to deploy your subgraph to Subgraph Studio.
+Subgraph'inizi Subgraph Studio'da dağıtma adımlarını öğrenin.
 
-> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
+> Not: Bir subgraph'i yayına aldığınızda, onu Subgraph Studio’ya iletmiş olursunuz ve orada test edebilirsiniz. Dağıtmanın yayımlamakla aynı şey olmadığını hatırlamak önemlidir. Bir subgraph'i yayımladığınızda, onu zincir üzerinde yayımlamış olursunuz.
 
-## Subgraph Studio Overview
+## Subgraph Studio'ya Genel Bakış
 
-In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
+[Subgraph Studio](https://thegraph.com/studio/)'da aşağıdakileri yapabilirsiniz:
 
-- View a list of subgraphs you've created
-- Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
-- Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
-- Test your subgraph in the playground environment
-- Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
-- Manage your billing
+- Oluşturmuş olduğunuz sugraph'lerin listesini görüntülemek
+- Belirli bir subgraph'i yönetmek, subgraph'in detaylarını görmek ve durumunu görüntülemek
+- Belirli subgraph'ler için API anahtarlarınızı oluşturmak ve yönetmek
+- API anahtarlarınızı belirli alanlara sınırlamak ve yalnızca belirli Endeksleyicilerin bu anahtarlarla sorgulama yapmasına izin vermek
+- Subgraph'inizi oluşturmak
+- Subgraph'inizi The Graph CLI'yi kullanarak dağıtmak
+- Subgraph'inizi playground ortamında test etmek
+- Geliştirme sorgu URL'sini kullanarak subgraph’inizi hazırlama ortamına entegre etmek
+- Subgraph'inizi The Graph Ağında yayımlamak
+- Faturalarınızı yönetmek
 
-## Install The Graph CLI
+## The Graph CLI'yi Yükleme
 
-Before deploying, you must install The Graph CLI.
+Dağıtmadan önce The Graph CLI'yi yüklemeniz gerekmektedir.
 
-You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+The Graph CLI'yi kullanmak için bilgisayarınızda [Node.js](https://nodejs.org/) ve tercih ettiğiniz bir paket yöneticisi (`npm`, `yarn` veya `pnpm`) kurulu olmalıdır. CLI'ın [en son](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) sürümünü kontrol edin.
 
-**Install with yarn:**
+### yarn ile kurulum
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### npm ile kurulum
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
+## Başlayalım
 
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+1. [Subgraph Studio](https://thegraph.com/studio/)'yu açın.
+2. Giriş yapmak için cüzdanınızı bağlayın.
+   - Cüzdan bağlamak için MetaMask, Conbase Wallet, WalletConnect ya da Safe kullanabilirsiniz.
+3. Giriş yaptıktan sonra, benzersiz yayına alma anahtarınız subgraph ayrıntıları sayfasında görünecektir.
+   - Dağıtma anahtarınız subgraph'lerinizi yayımlamanızı veya API anahtarlarınızı ve faturanızı yönetmenizi sağlar. Dağıtma anahtarınız benzersizdir; ancak anahtarınızın ele geçirildiğini düşünüyorsanız bu anahtarı yeniden yaratabilirsiniz.
 
-1. Open [Subgraph Studio](https://thegraph.com/studio/).
-2. Connect your wallet to sign in.
-   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
-3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
-   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
+> Önemli not: Subgraph'leri sorgulamak için bir API anahtarına sahip olmanız gerekmektedir
 
-> Important: You need an API key to query subgraphs
-
-### How to Create a Subgraph in Subgraph Studio
+### Subgraph Stüdyo'da Subgraph Nasıl Oluşturulur
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> Daha fazla yazılı detay için [Hızlı Başlangıç](/quick-start/) bölümünü inceleyin.
 
-### Subgraph Compatibility with The Graph Network
+### The Graph Ağı ile Subgraph Uyumluluğu
 
-In order to be supported by Indexers on The Graph Network, subgraphs must:
+Subgraph'lerin Graph Ağı Endeksleyicileri tarafından desteklenebilmesi için şu gereklilikleri karşılaması gerekir:
 
-- Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- [Desteklenen bir ağı](/developing/supported-networks) endeksliyor olmalı
+- Aşağıdaki özelliklerden hiçbirini kullanmamalı:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - Kritik olmayan hatalar
+  - Graftlama
 
-## Initialize Your Subgraph
+## Subgraph'inizi İlklendirme
 
-Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
+Subgraph’iniz Subgraph Studio’da oluşturulduktan sonra, aşağıdaki komutla CLI üzerinden subgraph kodunu ilklendirebilirsiniz:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
-You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+`<SUBGRAPH_SLUG>` değerini Subgraph Studio’daki subgraph ayrıntı sayfanızda bulabilirsiniz; aşağıdaki resme bakın:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
-After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+`graph init` komutunu çalıştırdıktan sonra sorgulamak istediğiniz kontrat adresini, ağı ve ABI’yi girmeniz istenecektir. Bu komut, yerel makinenizde subgraph’inizle çalışmaya başlamanız için bazı temel kodları içeren yeni bir klasör oluşturacaktır. Sonrasında subgraph'inizi işlevselliğini test ederek nihayetlendirebilirsiniz.
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Subgraph’inizi Subgraph Studio’da yayına alabilmek için önce CLI üzerinden hesabınıza giriş yapmanız gerekmektedir. Bunun için, subgraph ayrıntıları sayfanızda bulabileceğiniz yayına alma anahtarınıza ihtiyacınız olacak.
 
-Then, use the following command to authenticate from the CLI:
+CLI üzerinden kimlik doğrulaması yapmak için aşağıdaki komutu kullanın:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
-## Deploying a Subgraph
+## Bir Subgraph’i Dağıtma
 
-Once you are ready, you can deploy your subgraph to Subgraph Studio.
+Hazır olduğunuzda subgraph’inizi Subgraph Studio’da dağıtabilirsiniz.
 
-> Deploying a subgraph with the CLI pushes it to the Studio, where you can test it and and update the metadata. This action won't publish your subgraph to the decentralized network.
+> CLI ile bir subgraph dağıtmak, onu Studio’ya iletir; burada subgraph'i test edip meta verilerini güncelleyebilirsiniz. Bu işlem, subgraph’inizi merkeziyetsiz ağda yayımlamaz.
 
-Use the following CLI command to deploy your subgraph:
+Subgraph’inizi dağıtmak için aşağıdaki CLI komutunu kullanın:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
-After running this command, the CLI will ask for a version label.
+Bu komutu çalıştırdıktan sonra CLI sizden bir sürüm etiketi isteyecektir.
 
-- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
-- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
+- Sürüm etiketlemede [semver](https://semver.org/) (örn. 0.0.1) kullanmanız tavsiye edilir. Ancak `v1`, `version1` veya `asfdf` gibi başka bir dize de seçebilirsiniz.
+- Oluşturduğunuz etiketler Graph Gezgini'nde görünür olacak. Küratörler bu etiketlere göre belirli bir sürüme sinyal verip vermemeyi kararlaştırabilirler; bu nedenle seçimlerinizi dikkatle yapın.
 
-## Testing Your Subgraph
+## Subgraph’inizi Test Etme
 
-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.
+Yayına aldıktan sonra, subgraph’inizi (Subgraph Studio’da veya sorgu URL’si ile kendi uygulamanızda) test edebilir, yeni bir sürüm yayına alabilir, meta verileri güncelleyebilir ve hazır olduğunuzda [Graph Gezgini](https://thegraph.com/explorer)'nde yayımlayabilirsiniz.
 
-Use Subgraph Studio to check the logs on the dashboard and look for any errors with your subgraph.
+Subgraph Studio’da günlükleri kontrol ederek subgraph’inizle ilgili hataları görebilirsiniz.
 
-## Publish Your Subgraph
+## Subgraph’inizi Yayımlama
 
-In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/).
+Subgraph’inizi başarıyla yayımlamak için [subgraph yayımlama](/publishing/publishing-a-subgraph/) adımlarını gözden geçirin.
 
-## Versioning Your Subgraph with the CLI
+## CLI ile Subgraph’inizi Sürümleme
 
-If you want to update your subgraph, you can do the following:
+Subgraph’inizi güncellemek isterseniz, aşağıdaki adımları izleyebilirsiniz:
 
-- You can deploy a new version to Studio using the CLI (it will only be private at this point).
-- Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
-- This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
+- CLI kullanarak Studio’da yeni bir sürüm dağıtabilirsiniz (bu sürüm yalnızca özel olarak kalacaktır).
+- Memnun kaldığınızda, yeni dağıtımınızı [Graph Gezgini](https://thegraph.com/explorer)'nde yayımlayabilirsiniz.
+- Bu işlem, küratörlerin sinyal vermeye başlayabileceği ve Endeksleyicilerin endeksleyebileceği, subgraph'inizin yeni bir sürümünü oluşturur.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+Ayrıca, subgraph'inizin meta verilerini yeni bir sürüm yayımlamak zorunda kalmadan güncelleyebilirsiniz. Studio’daki (profil resmi, isim, açıklama gibi) subgraph ayrıntılarını [Graph Gezgini](https://thegraph.com/explorer)'ndeki **Ayrıntıları Güncelle** seçeneğini işaretleyerek güncelleyebilirsiniz. Bu seçenek işaretlendiğinde, yeni bir sürüm yayımlamaya gerek kalmadan, Explorer'da subgraph ayrıntılarını güncelleyen bir blokzincir işlemi oluşturulur.
 
-> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
+> Bir subgraph’in yeni bir sürümünü ağda yayımlamanın maliyetleri olduğunu unutmayın. İşlem ücretlerine ek olarak, otomatik olarak taşınan sinyalin kürasyon vergisinin bir kısmını da finanse etmeniz gerekmektedir. Küratörler subgraph'inize sinyal vermemişse subgraph'inizin yeni bir sürümünü yayımlayamazsınız. Daha fazla bilgi için [buraya](/network/curating/) göz atın.
 
-## Automatic Archiving of Subgraph Versions
+## Subgraph Sürümlerinin Otomatik Arşivlenmesi
 
-Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
+Subgraph Studio’da yeni bir subgraph sürümü yayına aldığınızda, önceki sürüm arşivlenecektir. Arşivlenen sürümler endekslenmez/senkronize edilmez ve bu nedenle sorgulanamaz. Subgraph’inizin arşivlenen bir sürümünü Subgraph Studio'da arşivden çıkarabilirsiniz.
 
-> Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.
+> Not: Studio’da yayına alınan ancak yayımlanmamış subgraph'lerin önceki sürümlerinin otomatik olarak arşivlenecektir.
 
-![Subgraph Studio - Unarchive](/img/Unarchive.png)
+![Subgraph Studio - Arşivden Çıkarma](/img/Unarchive.png)

From b8c273708231d8fa5b5bd18af14c149eab6662f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:46 -0500
Subject: [PATCH 0048/1325] New translations transfer-to-the-graph.mdx (Hindi)

---
 .../hi/cookbook/transfer-to-the-graph.mdx      | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/hi/cookbook/transfer-to-the-graph.mdx b/website/pages/hi/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..caa5f49f29fa 100644
--- a/website/pages/hi/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/hi/cookbook/transfer-to-the-graph.mdx
@@ -12,16 +12,16 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
 ### Create a Subgraph in Subgraph Studio
 
-- Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
-- Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
+- [Subgraph Studio](https://thegraph.com/studio/) पर जाएँ और अपने वॉलेट को कनेक्ट करें।
+- "एक सबग्राफ बनाएं" पर क्लिक करें। सबग्राफ का नाम टाइटल केस में रखनाrecommended है: "सबग्राफ नाम चेन नाम"।
 
 > Note: After publishing, the subgraph name will be editable but requires on-chain action each time, so name it properly.
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### उदाहरण
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### अतिरिक्त संसाधन
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 74bc863be6eed8b0ae3a83f8b0d226082991ebdc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:47 -0500
Subject: [PATCH 0049/1325] New translations triggers-example.mdx (Hindi)

---
 website/pages/hi/sps/triggers-example.mdx | 69 ++++++++++++-----------
 1 file changed, 36 insertions(+), 33 deletions(-)

diff --git a/website/pages/hi/sps/triggers-example.mdx b/website/pages/hi/sps/triggers-example.mdx
index d8d61566295e..2f9eab3900f0 100644
--- a/website/pages/hi/sps/triggers-example.mdx
+++ b/website/pages/hi/sps/triggers-example.mdx
@@ -1,24 +1,27 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "ट्यूटोरियल: Solana पर एक Substreams-शक्ति वाले Subgraph सेट करें"
 ---
 
-## Prerequisites
+## आवश्यक शर्तें
 
-Before starting, make sure to:
+'शुरू करने से पहले, सुनिश्चित करें कि:'
 
-- Complete the [Getting Started Guide](https://github.com/streamingfast/substreams-starter) to set up your development environment using a Dev Container.
-- Be familiar with The Graph and basic blockchain concepts such as transactions and Protobufs.
+- अपने विकास पर्यावरण को सेट अप करने के लिए Getting Started Guide(https://github.com/streamingfast/substreams-starter) को पूरा करें, एक Dev Container का उपयोग करके।
+- The Graph और मूल ब्लॉकचेन अवधारणाओं जैसे कि लेनदेन और Protobufs से परिचित रहें।
 
-## Step 1: Initialize Your Project
+## चरण 1: अपने प्रोजेक्ट को प्रारंभ करें
 
-1. Open your Dev Container and run the following command to initialize your project:
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
+1. अपने Dev Container को खोलें और अपने प्रोजेक्ट को शुरू करने के लिए निम्नलिखित कमांड चलाएं:
 
    ```bash
-   substreams init
+   substreams प्रारंभ करें
    ```
 
-2. Select the "minimal" project option.
-3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
+2. "Minimal" प्रोजेक्ट विकल्प चुनें।
+
+3. substreams.yaml फ़ाइल की सामग्री को निम्नलिखित कॉन्फ़िगरेशन से बदलें, जो SPL टोकन प्रोग्राम आईडी पर Orca अकाउंट के लेनदेन को फ़िल्टर करता है:
 
 ```yaml
 specVersion: v0.1.0
@@ -44,15 +47,15 @@ params: # Modify the param fields to meet your needs
   map_spl_transfers: token_contract:orcaEKTdK7LKz57vaAYr9QeNsVEPfiu6QeMU1kektZE
 ```
 
-## Step 2: Generate the Subgraph Manifest
+## चरण 2: Subgraph Manifest उत्पन्न करें
 
-Once the project is initialized, generate a subgraph manifest by running the following command in the Dev Container:
+एक बार जब प्रोजेक्ट इनिशियलाइज़ हो जाए, Dev Container में निम्नलिखित कमांड चलाकर subgraph मैनिफेस्ट जेनरेट करें: 
 
 ```bash
-substreams codegen subgraph
+'सबस्ट्रीम्स कोडजेन' subgraph
 ```
 
-You will generate a`subgraph.yaml` manifest which imports the Substreams package as a data source:
+आप subgraph.yaml मैनिफेस्ट बनाएंगे जो डेटा स्रोत के रूप में Substreams पैकेज को इम्पोर्ट करता है:
 
 ```yaml
 ---
@@ -71,9 +74,9 @@ dataSources:
       handler: handleTriggers
 ```
 
-## Step 3: Define Entities in `schema.graphql`
+## चरण 3: schema.graphql में संस्थाएँ परिभाषित करें
 
-Define the fields you want to save in your subgraph entities by updating the `schema.graphql` file. Here is an example:
+अपने सबग्राफ एंटिटीज़ में सहेजने के लिए फ़ील्ड्स को परिभाषित करें, schema.graphql फ़ाइल को अपडेट करके। यहाँ एक उदाहरण है:
 
 ```graphql
 type MyTransfer @entity {
@@ -85,21 +88,11 @@ type MyTransfer @entity {
 }
 ```
 
-This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
-
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+यह स्कीमा एक MyTransfer एंटिटी को परिभाषित करता है जिसमें फ़ील्ड्स जैसे कि id, amount, source, designation, और signers शामिल हैं।
 
-## Step 5: Handle Substreams Data in `mappings.ts`
+## चरण 4: mappings.ts में Substreams डेटा को संभालें
 
-With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
+प्रोटोकॉल वस्तुओं के जनित होने के साथ, आप अब 'mappings.ts' फ़ाइल में डिकोडेड सबस्ट्रीम डेटा को संभाल सकते हैं, जो कि './src' निर्देशिका में पाई जाती है। नीचे दिया गया उदाहरण दिखाता है कि कैसे 'Orca' खाता आईडी से जुड़े गैर-व्युत्पन्न ट्रांसफर को सबग्राफ संस्थाओं में निकाला जा सकता है:
 
 ```ts
 import { Protobuf } from 'as-proto/assembly'
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,8 +123,18 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
-## Conclusion
+## चरण 5: Protobuf फ़ाइलें उत्पन्न करें
+
+AssemblyScript में Protobuf ऑब्जेक्ट बनाने के लिए, निम्नलिखित कमांड चलाएँ:
+
+```bash
+npm चलाएँ protogen
+```
+
+यह कमांड Protobuf परिभाषाओं को AssemblyScript में परिवर्तित करता है, जिससे आप उन्हें हैंडलर में उपयोग कर सकते हैं।
+
+## निष्कर्ष
 
-You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.
+आपने सफलतापूर्वक एक ट्रिगर-आधारित Substreams-शक्ति वाला subgraph स्थापित कर लिया है जो एक Solana SPL टोकन के लिए है। अब आप अपने विशिष्ट उपयोग के मामले के अनुसार अपने स्कीमा, मैपिंग और मॉड्यूल को और अनुकूलित कर सकते हैं।
 
-For more advanced customization and optimizations, check out the official [Substreams documentation](https://substreams.streamingfast.io/tutorials/solana).
+अधिक उन्नत अनुकूलन और ऑप्टिमाइजेशन के लिए, आधिकारिक Substreams documentation(https://substreams.streamingfast.io/tutorials/solana) देखें।

From 517babb5549b7dcd32c4bf5e70d713b804686d16 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:48 -0500
Subject: [PATCH 0050/1325] New translations transfer-a-subgraph.mdx (Hindi)

---
 .../pages/hi/managing/transfer-a-subgraph.mdx | 57 ++++++-------------
 1 file changed, 17 insertions(+), 40 deletions(-)

diff --git a/website/pages/hi/managing/transfer-a-subgraph.mdx b/website/pages/hi/managing/transfer-a-subgraph.mdx
index c4060284d5d9..f424782f7940 100644
--- a/website/pages/hi/managing/transfer-a-subgraph.mdx
+++ b/website/pages/hi/managing/transfer-a-subgraph.mdx
@@ -1,65 +1,42 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: सबग्राफ ट्रांसफर करें
 ---
 
-## Transferring ownership of a subgraph
+विभिन्न नेटवर्क पर प्रकाशित subgraphs के लिए उस पते पर एक NFT जारी किया गया है जिसने subgraph प्रकाशित किया। NFT एक मानक ERC721 पर आधारित है, जो The Graph नेटवर्क पर खातों के बीच स्थानांतरण की सुविधा देता है।
 
-Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+## अनुस्मारक 
 
-**Please note the following:**
+- जो भी 'NFT' का मालिक है, वह subgraph को नियंत्रित करता है।
+- यदि मालिक 'NFT' को बेचने या स्थानांतरित करने का निर्णय लेता है, तो वे नेटवर्क पर उस subgraph को संपादित या अपडेट नहीं कर पाएंगे।
+- आप आसानी से एक subgraph का नियंत्रण एक multi-sig में स्थानांतरित कर सकते हैं।
+- एक समुदाय का सदस्य DAO की ओर से एक subgraph बना सकता है।
 
-- Whoever owns the NFT controls the subgraph.
-- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
-- You can easily move control of a subgraph to a multi-sig.
-- A community member can create a subgraph on behalf of a DAO.
+## अपने 'subgraph' को एक NFT के रूप में देखें
 
-### View your subgraph as an NFT
-
-To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+अपने 'subgraph' को एक NFT के रूप में देखने के लिए, आप एक NFT मार्केटप्लेस जैसे OpenSea पर जा सकते हैं:
 
 ```
 https://opensea.io/your-wallet-address
 ```
 
-Or a wallet explorer like **Rainbow.me**:
+या एक वॉलेट एक्सप्लोरर जैसे **Rainbow.me**:
 
 ```
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## चरण-दर-चरण
 
-To transfer ownership of a subgraph, do the following:
+एक Subgraph का स्वामित्व स्थानांतरित करने के लिए, निम्नलिखित करें:
 
-1.  Use the UI built into Subgraph Studio:
+1. 'Subgraph Studio' में निर्मित UI का उपयोग करें:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. उस पते का चयन करें जिसे आप 'subgraph' को स्थानांतरित करना चाहेंगे:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
-Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
+आप वैकल्पिक रूप से NFT बाजारों जैसे OpenSea के अंतर्निहित UI का भी उपयोग कर सकते हैं:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From fbab41a0e6328476e6dbaac91d7fa21fb555e521 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:50 -0500
Subject: [PATCH 0051/1325] New translations overview.mdx (French)

---
 website/pages/fr/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/fr/network/overview.mdx b/website/pages/fr/network/overview.mdx
index 09210f52ce37..44bb43d7f444 100644
--- a/website/pages/fr/network/overview.mdx
+++ b/website/pages/fr/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Présentation du réseau
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network est un protocole d'indexation décentralisé pour organiser les données de la blockchain.
 
-## Aperçu
+## Comment ça marche ?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Les applications utilisent [GraphQL](/querying/graphql-api/) pour interroger des API ouvertes appelées subgraphs et récupérer les données indexées sur le réseau. Avec The Graph, les développeurs peuvent créer des applications sans serveur qui fonctionnent entièrement sur une infrastructure publique.
+
+## Spécificités⁠
+
+The Graph Network est composé d'Indexeurs, de Curateurs et de Délégateurs qui fournissent des services au réseau et servent des données aux applications web3.
 
 ![Économie des jetons](/img/Network-roles@2x.png)
 
-Pour garantir la sécurité économique du Graph Network et l'intégrité des données interrogées, les participants misent et utilisent des jetons Graph ([GRT](/tokenomics)). GRT est un jeton utilitaire de travail qui est un ERC-20 utilisé pour allouer des ressources dans le réseau.
+### Économie
+
+Pour garantir la sécurité économique de The Graph Network et l'intégrité des données interrogées, les participants stakent et utilisent des Graph Tokens ([GRT](/tokenomics)). Le GRT est un jeton utilitaire de travail qui est un ERC-20, utilisé pour allouer des ressources dans le réseau.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Les Indexeurs, Curateurs et Déléguateurs actifs peuvent fournir des services et tirer des revenus du réseau. Le revenu qu'ils perçoivent est proportionnel à la quantité de travail qu'ils effectuent et à leur GRT stakés.

From 7de32836f1bda16babd42646616673ab7c350214 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:51 -0500
Subject: [PATCH 0052/1325] New translations delegating.mdx (Turkish)

---
 website/pages/tr/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/tr/network/delegating.mdx b/website/pages/tr/network/delegating.mdx
index 81824234e072..a7be05b9f698 100644
--- a/website/pages/tr/network/delegating.mdx
+++ b/website/pages/tr/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegator Guide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Listed below are the main risks of being a Delegator in the protocol.
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### The delegation unbonding period
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) _Note the 0.5% fee in the Delegation UI, as well as the 28 day
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *The top Indexer is giving Delegators 90% of the rewards. The
   middle one is giving Delegators 20%. The bottom one is giving Delegators ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculating Delegators expected return
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- A technical Delegator can also look at the Indexer's ability to use the Delegated tokens available to them. If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considering the query fee cut and indexing fee cut
 
-As described in the above sections, you should choose an Indexer that is transparent and honest about setting their Query Fee Cut and Indexing Fee Cuts. A Delegator should also look at the Parameters Cooldown time to see how much of a time buffer they have. After that is done, it is fairly simple to calculate the amount of rewards the Delegators are getting. The formula is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Considering the Indexer's delegation pool
 
-Another thing a Delegator has to consider is what proportion of the Delegation Pool they own. All delegation rewards are shared evenly, with a simple rebalancing of the pool determined by the amount the Delegator has deposited into the pool. This gives the Delegator a share of the pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considering the delegation capacity
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Örnek
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 163357bc40f1546fdb822aa129a93e62ecb5b633 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:52 -0500
Subject: [PATCH 0053/1325] New translations explorer.mdx (Turkish)

---
 website/pages/tr/network/explorer.mdx | 103 +++++++++++++++++---------
 1 file changed, 68 insertions(+), 35 deletions(-)

diff --git a/website/pages/tr/network/explorer.mdx b/website/pages/tr/network/explorer.mdx
index 852af644a69a..cb6d3012f0a6 100644
--- a/website/pages/tr/network/explorer.mdx
+++ b/website/pages/tr/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Gezgini
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraph'ler
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Gezgin Gürüntüsü 1](/img/Subgraphs-Explorer-Landing.png)
 
-Bir subgraph tıkladığınızda, test alanında sorguları test edebilecek ve bilinçli kararlar vermek için ağ ayrıntılarından yararlanabileceksiniz. Ayrıca, kendi subgraph'ınız veya başkalarının subgraphlar'ında GRT sinyali vererek indeksleyicilerin bunun önemi ve kalitesinden haberdar olmasını sağlayabileceksiniz. Bu oldukça önemlidir, çünkü bir subgraph'ta sinyal vermek, pnun indekslenmesini teşvik eder, bu da onların nihayetinde sorguları sunmak için ağda görünmeleri anlamına gelir.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Gezgin Gürüntüsü 2](/img/Subgraph-Details.png)
 
-Her bir subgraph'ın özel sayfasında, çeşitli ayrıntılar ortaya çıkmaktadır. Bunlar şunları içerir:
+On each subgraph’s dedicated page, you can do the following:
 
 - Subgraphlar üzerinde sinyal/sinyalsizlik
 - Grafikler, mevcut dağıtım kimliği ve diğer üst veri gibi daha fazla ayrıntı görüntüleme
@@ -31,26 +45,32 @@ Her bir subgraph'ın özel sayfasında, çeşitli ayrıntılar ortaya çıkmakta
 
 ## Katılımcılar
 
-Bu kısımda İndeksleyiciler, Delegatörler ve Küratörler gibi ağ faaliyetlerine katılan tüm kişilerin kuş bakışı bir görüş elde edeceksiniz. Aşağıda, her bir kısmın sizin için ne anlama geldiğini derinlemesine inceleyeceğiz.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. İndeksleyiciler
 
 ![Gezgin Gürüntüsü 4](/img/Indexer-Pane.png)
 
-İndeksleyiciler ile başlayalım. İndeksleyiciler protokolün bel kemiğidir, subgraphlar'a stake eden, indeksleyen ve subgraphlar'ı kullanan herkese sorgu sunan kişilerdir. İndeksleyiciler tablosunda, bir İndeksleyicinin temsilci parametrelerini, hisselerini, her bir subgraph'a ne kadar stake ettiklerini, sorgu ücretlerini ve indeksleme ödüllerinden ne kadar gelir elde ettiklerini görebileceksiniz. Derinlemesine incelemeler aşağıda:
+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.
 
-- Sorgu Ücreti Kesintisi - İndeksleyici'nin Delegatörlerle bölüşürken tuttuğu sorgu ücreti indirimlerinin %'si
-- Efektif Ödül Kesintisi - delegasyon havuzuna uygulanan indeksleme ödülü kesintisi. Eğer negatifse, indeksleyicinin ödüllerinin bir kısmını verdiği anlamına gelir. Pozitifse, İndeksleyicinin ödüllerinin bir kısmını elinde tuttuğu anlamına gelir
-- Kalan Bekleme Süresi - İndeksleyici'nin yukarıdaki delegatör parametrelerini değiştirebilmesi için kalan süre. Bekleme süreleri, İndeksleyiciler tarafından delegatör parametrelerini güncellediklerinde ayarlanır
-- Depozito - Bu, İndeksleyici'nin kötü niyetli veya yanlış davranışı sonucunda kesilebilecek yatırılmış payıdır
-- Delege edilmiş - İndeksleyici tarafından tahsis edilebilen ancak kesilemeyen Delegatörler'in payları
-- Tahsis edilmiş - İndeksleyiciler'in indeksledikleri subgraphlar'a aktif olarak ayırdıkları paydır
-- Mevcut Delegasyon Kapasitesi - İndekslendiricilerin aşırı delege edilmiş duruma gelmeden önce alabilecekleri delege edilebilecek pay miktarı
+**Ayrıntılar**
+
+- 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.
 - 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.
-- Sorgu Ücretleri - bu, son kullanıcıların bir İndeksleyiciden gelen sorgular için tüm zaman içinde ödediği toplam ücretlerdir
+- 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.
 
-İndeksleyiciler hem sorgu ücretleri hem de indeksleme ödülleri kazanabilir. İşlevsel olarak bu, ağ katılımcıları GRT'yi bir İndeksleyiciye delege ettiğinde gerçekleşir. Bu, İndeksleyicilerin İndeksleyici parametrelerine bağlı olarak sorgu ücretleri ve ödüller almasına olanak sağlar. İndeksleme parametreleri, tablonun sağ tarafına tıklanarak veya bir İndeksleyicinin profiline girip "Delegate" düğmesine tıklanarak ayarlanır.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Nasıl İndeksleyici olunacağı hakkında daha fazla bilgi edinmek için [resmi dökümantasyona](/network/indexing) veya [Graph Akademi İndeksleyici kılavuzlarına](https://thegraph.academy/delegators/choosing-indexers/) göz atabilirsiniz.
 
@@ -58,9 +78,13 @@ Nasıl İndeksleyici olunacağı hakkında daha fazla bilgi edinmek için [resmi
 
 ### 2. Küratörler
 
-Küratörler, hangi subgraphlar'ın en yüksek kalitede olduğunu belirlemek için subgraphlar'ı analiz eder. Bir Küratör potansiyel olarak cazip bir subgraph bulduğunda, bağlanma eğrisi üzerinde sinyal vererek onu kürate edebilir. Küratörler bunu yaparak, İndeksleyicilere hangi subgraphlar'ın yüksek kaliteli olduğunu ve indekslenmesi gerektiğini bildirir.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Küratörler topluluk üyeleri, veri kullanıcıları ve hatta GRT tokenlerini bir bağlanma eğrisine yatırarak kendi subgraphlar'ı hakkında sinyal veren subgraph geliştiricileri olabilir. Küratörler GRT yatırarak bir subgraph'ın kürasyon paylarını basarlar. Sonuç olarak Küratörler, sinyal verdikleri subgraph'ın ürettiği sorgu ücretlerinin bir kısmını almaya hak kazanırlar. Bağlanma eğrisi, Küratörleri en yüksek kaliteli veri kaynaklarının küratörlüğünü yapmaya teşvik eder. Bu bölümdeki Küratör tablosu şunları görmenizi sağlayacaktır:
+In the The Curator table listed below you can see:
 
 - Küratör'ün küratörlüğe başladığı tarih
 - Yatırılan GRT sayısı
@@ -68,34 +92,36 @@ Küratörler topluluk üyeleri, veri kullanıcıları ve hatta GRT tokenlerini b
 
 ![Gezgin Gürüntüsü 6](/img/Curation-Overview.png)
 
-Küratör rolü hakkında daha fazla bilgi edinmek istiyorsanız, bunu [Graph Akademi](https://thegraph.academy/curators/) 'nin aşağıdaki bağlantılarını veya [resmi dökümantasyonunu](/network/curating) ziyaret ederek yapabilirsiniz.
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegatörler
 
-Delegatörler, Graph Ağı'nın güvenliğinin ve merkeziyetsizliğinin korunmasında kilit bir rol oynar. GRT tokenlerini bir veya birden fazla indeksleyiciye delege ederek (yani "stake ederek") ağa katılırlar. TDelegatörler olmadan, İndeksleyicilerin önemli ödüller ve ücretler kazanma olasılığı daha düşüktür. Bu nedenle İndeksleyiciler, kazandıkları indeksleme ödüllerinin ve sorgu ücretlerinin bir kısmını Delegatörlere sunarak onları kendilerine delege etmeye teşvik etmeye çalışırlar.
+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.
 
-Delegatörler ise İndeksleyicileri sırasıyla geçmiş performans, indeksleme ödül oranları ve sorgu ücreti kesintileri gibi bir dizi farklı faktöre göre seçerler. Topluluk içinde sahip oldukları itibar da bu konuda bir faktör olabilir! Seçilen indeksleyicilerle [Graph Discord sunucusu](https://discord.gg/graphprotocol) veya [Graph Forum](https://forum.thegraph.com/)'u üzerinden bağlantı kurmanız önerilir!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![Gezgin Gürüntüsü 7](/img/Delegation-Overview.png)
 
-Delegatörler tablosu, topluluktaki aktif Delegatörleri ve aşağıdaki gibi metrikleri görmenizi sağlayacaktır:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Bir Delegatör'ün delege ettiği İndeksleyici sayısı
 - Bir Delegatör'ün orijinal delegasyonu
 - Biriktirdikleri ancak protokolden çekmedikleri ödüller
 - Protokolden çekildiler gerçekleşmiş ödüller
 - Şu anda protokolde bulunan sahip oldukları toplam GRT miktarı
-- En son delegasyon aldıkları tarih
+- The date they last delegated
 
-Nasıl Delegatör olunacağı hakkında daha fazla bilgi edinmek istiyorsanız, başka yere bakmanıza gerek yok! Tek yapmanız gereken [resmi dökümantasyona](/network/delegating) veya [Graph Akademi](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers)'ye bakmak.
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Ağ
 
-Ağ bölümünde, küresel APG'lerin yanı sıra her bir dönem bazına geçme ve ağ metriklerini daha ayrıntılı olarak analiz etme olanaklarını göreceksiniz. Bu ayrıntılar size ağın zaman içinde nasıl performans gösterdiğine dair bir fikir verecektir.
+In this section, you can see global KPIs and view 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
+### Genel Bakış
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - Mevcut toplam ağ payı
 - İndeksleyiciler ve Delegatörler arasındaki pay paylaşımı
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Kürasyon ödülü, enflasyon oranı ve daha fazlası gibi protokol parametreleri
 - Mevcut dönem ödülleri ve ücretleri
 
-Bahsetmeye değer birkaç önemli ayrıntı:
+A few key details to note:
 
-- **Sorgu ücretleri kullanıcılar tarafından üretilen ücretleri temsil eder** ve subgraphlara yönelik tahsisleri kapatıldıktan ve sundukları veriler tüketiciler tarafından doğrulandıktan sonra en az 7 dönemlik bir sürenin ardından (aşağıya bakınız) İndeksleyiciler tarafından talep edilebilir (veya edilemez).
-- **İndeksleme ödülleri, İndeksleyicilerin dönem boyunca ağ ihracından talep ettikleri ödül miktarını temsil eder.** Protokol ihracı sabit olmasına rağmen, ödüller yalnızca İndeksleyiciler indeksledikleri subgraphlara yönelik tahsislerini kapattıklarında basılır. Bu nedenle, her dönem başına ödül sayısı değişir (yani, bazı dönemler boyunca, İndeksleyiciler günlerce açık olan tahsisatları toplu olarak kapatmış olabilir).
+- **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).
 
 ![Gezgin Gürüntüsü 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ Dönemler bölümünde, aşağıdaki gibi metrikleri dönem bazında analiz edeb
   - Aktif dönem, İndeksleyicilerin halihazırda pay tahsis ettiği ve sorgu ücretlerini topladığı dönemdir
   - Uzlaşma dönemleri, bildirim kanallarının uzlaştırıldığı dönemlerdir. Bu, kullanıcıların kendilerine karşı itirazda bulunması halinde İndeksleyicilerin kesintiye maruz kalacağı anlamına gelir.
   - 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, İndeksleyiciler tarafından talep edilecek sorgu ücreti iadesi kalmamış, dolayısıyla sonlandırılmış dönemlerdir.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Gezgin Gürüntüsü 9](/img/Epoch-Stats.png)
 
 ## Kullanıcı Profiliniz
 
-Ağ istatistiklerinden bahsettiğimize göre, şimdi kişisel profilinize geçelim. Kişisel profiliniz, ağa nasıl katılıyor olursanız olun, ağ etkinliğinizi görebileceğiniz yerdir. Kripto cüzdanınız kullanıcı profiliniz olarak işlev görecek ve Kullanıcı Panosu ile şunları görebileceksiniz:
+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:
 
 ### Profile Genel Bakış
 
-Burası yaptığınız tüm mevcut eylemleri görebileceğiniz yerdir. Ayrıca profil bilgilerinizi, açıklamanızı ve web sitenizi de (eğer eklediyseniz) burada bulabilirsiniz.
+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).
 
 ![Gezgin Gürüntüsü 10](/img/Profile-Overview.png)
 
 ### Subgraphlar Sekmesi
 
-Subgraphlar sekmesine tıklarsanız, yayınlanmış subgraphlar'ı göreceksiniz. Bu, test amacıyla CLI ile dağıtılan herhangi bir subgraph'ı içermeyecektir - subgraphlar yalnızca merkeziyetsiz ağda yayınlandıklarında görünecektir.
+In the Subgraphs tab, you’ll see 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.
 
 ![Gezgin Gürüntüsü 11](/img/Subgraphs-Overview.png)
 
 ### İndeksleme Sekmesi
 
-İndeksleme sekmesine tıklarsanız, subgraplar'a yönelik tüm aktif ve geçmiş tahsisleri içeren bir tablonun yanı sıra bir İndeksleyici olarak geçmiş performansınızı analiz edebileceğiniz ve görebileceğiniz grafikler bulacaksınız.
+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.
 
 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:
 
@@ -158,7 +189,9 @@ Bu bölümde ayrıca net İndeksleyici ödülleriniz ve sorgu ücretlerinizle il
 
 ### Delegasyon Sekmesi
 
-Delegatörler Graph Ağı için önem arz etmektedir. Bir Delegatör, sağlıklı ödül getirisi sağlayacak bir İndeksleyici seçmek için bildiklerini kullanmalıdır. Burada, aktif ve geçmiş delegasyonlarınızın ayrıntılarını ve delege ettiğiniz İndeksleyicilerin metriklerini bulabilirsiniz.
+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.
 
 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.
 

From 0819647e5da97adbc5f56ffb52630186e19d9cd3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:53 -0500
Subject: [PATCH 0054/1325] New translations unit-testing-framework.mdx
 (Turkish)

---
 .../tr/developing/unit-testing-framework.mdx  | 200 ++++++++++--------
 1 file changed, 107 insertions(+), 93 deletions(-)

diff --git a/website/pages/tr/developing/unit-testing-framework.mdx b/website/pages/tr/developing/unit-testing-framework.mdx
index 33b6fb12fe52..85ebc99baaae 100644
--- a/website/pages/tr/developing/unit-testing-framework.mdx
+++ b/website/pages/tr/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Birim Testi Framework'ü
 ---
 
-Matchstick, [LimeChain](https://limechain.tech/) tarafından geliştirilen, subgraph geliştiricilerinin eşleştirme mantıklarını bir korumalı alan ortamında test etmelerine ve subgraphlarını güvenle dağıtmalarına olanak tanıyan bir birim testi framework'üdür!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Buradan Başlayın
 
-### Bağımlılıkları yükleyin
+### Install Dependencies
 
-Test yardımcı yöntemlerini kullanmak ve testleri çalıştırmak için aşağıdaki bağımlılıkları yüklemeniz gerekecektir:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node`, PostgreSQL'ye bağlıdır, bu nedenle henüz yüklemediyseniz PostgreSQL yüklemeniz gerekecektir. Aşağıdaki komutları kullanmanızı şiddetle tavsiye ediyoruz, çünkü başka bir şekilde eklemeniz beklenmedik hatalara neden olabilir!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres yükleme komutu:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ En son libpq.5.lib'e bir sembolik bağ oluşturun. _Bu dizini önce oluşturman
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres yükleme komutu (dağıtımınıza bağlı olarak değişir):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Linux için Windows Alt Sistemleri)
+### Using WSL (Windows Subsystem for Linux)
 
 Matchstick'i WSL'de Docker yaklaşımı ve ikili yaklaşımı kullanarak kullanabilirsiniz. WSL biraz alengirli olabileceğinden, aşağıdaki gibi sorunlarla karşılaşırsanız birkaç ipucu verelim
 
@@ -76,7 +85,7 @@ Son olarak, `graph test`'i kullanmayın (global graph-cli yüklemenizi kullanmak
 }
 ```
 
-### Kullanış
+### Using Matchstick
 
 **Matchstick**'i subgraph proje'nizde kullanmak için sadece bir terminal açın, proje'nizin kök(root) klasörüne gidin ve basitçe `graph test [options] <datasource>` - komutunu çalıştırın - bu en son **Matchstick** ikili dosyasını indirir ve belirtilen testi veya test klasöründeki tüm testleri çalıştırır (verikaynağı bayrağı belirtilmezse mevcut tüm testler).
 
@@ -116,7 +125,7 @@ graph test path/to/file.test.ts
 
 `graph-cli 0.25.2`'den itibaren `graph test` `-d` bayrağı ile `matchstick`'i bir docker konteynerinde çalıştırmayı desteklemektedir. Docker uygulaması, [bind mount](https://docs.docker.com/storage/bind-mounts/) kullandığından, `graph test -d` komutu her çalıştırıldığında docker görüntüsünü yeniden oluşturmak zorunda değildir. Alternatif olarak, [matchstick](https://github.com/LimeChain/matchstick#docker-) deposundan docker'ı manuel olarak çalıştırmak için talimatları izleyebilirsiniz.
 
-❗ `graph test -d` forces `docker run` to run with flag `-t`. This must be removed to run inside non-interactive environments (like GitHub CI).
+❗ `graph test -d`, `docker run`'un `-t` bayrağıyla çalışmasını zorlar. Bu, etkileşimli olmayan ortamlar (örneğin, GitHub CI) içinde çalıştırmak için kaldırılmalıdır.
 
 ❗ Daha önce `graph test` çalıştırdıysanız, docker build sırasında aşağıdaki hatayla karşılaşabilirsiniz:
 
@@ -144,9 +153,9 @@ manifestPath: path/to/subgraph.yaml
 
 Ayrıca, "["How to use Matchstick to write unit tests for your subgraphs"](https://www.youtube.com/playlist?list=PLTqyKgxaGF3SNakGQwczpSGVjS_xvOv3h)" konulu video serisine göz atabilirsiniz
 
-## Tests structure
+## Test yapısı
 
-_**IMPORTANT: The test structure described below depens on `matchstick-as` version >=0.5.0**_
+_**ÖNEMLİ: Aşağıda açıklanan test yapısı `matchstick-as` sürümünün >=0.5.0 olmasını gerektirir**_
 
 ### describe()
 
@@ -524,33 +533,33 @@ assertNotNull<T>(value: T)
 entityCount(entityType: string, expectedCount: i32)
 ```
 
-As of version 0.6.0, asserts support custom error messages as well
+Sürüm 0.6.0 itibariyle, assert fonksiyonları özel hata mesajlarını da desteklemektedir
 
 ```typescript
-assert.fieldEquals('Gravatar', '0x123', 'id', '0x123', 'Id should be 0x123')
-assert.equals(ethereum.Value.fromI32(1), ethereum.Value.fromI32(1), 'Value should equal 1')
-assert.notInStore('Gravatar', '0x124', 'Gravatar should not be in store')
-assert.addressEquals(Address.zero(), Address.zero(), 'Address should be zero')
-assert.bytesEquals(Bytes.fromUTF8('0x123'), Bytes.fromUTF8('0x123'), 'Bytes should be equal')
-assert.i32Equals(2, 2, 'I32 should equal 2')
-assert.bigIntEquals(BigInt.fromI32(1), BigInt.fromI32(1), 'BigInt should equal 1')
-assert.booleanEquals(true, true, 'Boolean should be true')
-assert.stringEquals('1', '1', 'String should equal 1')
-assert.arrayEquals([ethereum.Value.fromI32(1)], [ethereum.Value.fromI32(1)], 'Arrays should be equal')
+assert.fieldEquals('Gravatar', '0x123', 'id', '0x123', 'Id 0x123 olmalıdır')
+assert.equals(ethereum.Value.fromI32(1), ethereum.Value.fromI32(1), 'Value 1'e eşit olmalıdır')
+assert.notInStore('Gravatar', '0x124', 'Gravatar store'da olmamalıdır')
+assert.addressEquals(Address.zero(), Address.zero(), 'Adres sıfır olmalıdır')
+assert.bytesEquals(Bytes.fromUTF8('0x123'), Bytes.fromUTF8('0x123'), 'Byte değerleri eşit olmalıdır')
+assert.i32Equals(2, 2, 'I32, 2'ye eşit olmalıdır')
+assert.bigIntEquals(BigInt.fromI32(1), BigInt.fromI32(1), 'BigInt 1'e eşit olmalıdır')
+assert.booleanEquals(true, true, 'Boolean true olmalıdır')
+assert.stringEquals('1', '1', 'String 1'e eşit olmalıdır')
+assert.arrayEquals([ethereum.Value.fromI32(1)], [ethereum.Value.fromI32(1)], 'Array'ler eşit olmalıdır')
 assert.tupleEquals(
-  changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
-  changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
-  'Tuples should be equal',
+ changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
+ changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
+ 'Tuple'lar eşit olmalıdır',
 )
-assert.assertTrue(true, 'Should be true')
-assert.assertNull(null, 'Should be null')
-assert.assertNotNull('not null', 'Should be not null')
-assert.entityCount('Gravatar', 1, 'There should be 2 gravatars')
-assert.dataSourceCount('GraphTokenLockWallet', 1, 'GraphTokenLockWallet template should have one data source')
+assert.assertTrue(true, 'True olmalıdır')
+assert.assertNull(null, 'Null olmalıdır')
+assert.assertNotNull('not null', 'Null olmamalıdır')
+assert.entityCount('Gravatar', 1, '2 gravatar olmalıdır')
+assert.dataSourceCount('GraphTokenLockWallet', 1, 'GraphTokenLockWallet şablonunda bir veri kaynağı olmalıdır')
 assert.dataSourceExists(
-  'GraphTokenLockWallet',
-  Address.zero().toHexString(),
-  'GraphTokenLockWallet should have a data source for zero address',
+ 'GraphTokenLockWallet',
+ Address.zero().toHexString(),
+ 'GraphTokenLockWallet sıfır adresi için bir veri kaynağına sahip olmalıdır',
 )
 ```
 
@@ -877,7 +886,7 @@ Kullanıcılar, bir varlığın depoda olmadığını doğrulayabilirler. Bu fon
 assert.notInStore('Gravatar', '23')
 ```
 
-### Printing the whole store, or single entities from it (for debug purposes)
+### Tüm mağazayı veya tüm mağazadan tek varlıkları yazdırma (hata ayıklama amaçlı)
 
 Bu yardımcı fonksiyon kullanılarak deponun tamamı konsola yazdırılabilir:
 
@@ -887,7 +896,7 @@ import { logStore } from 'matchstick-as/assembly/store'
 logStore()
 ```
 
-As of version 0.6.0, `logStore` no longer prints derived fields, instead users can use the new `logEntity` function. Of course `logEntity` can be used to print any entity, not just ones that have derived fields. `logEntity` takes the entity type, entity id and a `showRelated` flag to indicate if users want to print the related derived entities.
+Sürüm 0.6.0 itibarıyla, `logStore` türetilmiş alanları yazdırmaz. Bunun yerine kullanıcılar yeni `logEntity` fonksiyonunu kullanabilir. Elbette ki `logEntity`, yalnızca türetilmiş alanlara sahip olanları değil, herhangi bir varlığı yazdırmak için kullanılabilir. `logEntity`, varlık türünü, varlık kimliğini ve ilgili türetilmiş varlıkları yazdırmak isteyip istemediğinizi belirten bir `showRelated` bayrağını alır.
 
 ```
 import { logEntity } from 'matchstick-as/assembly/store'
@@ -949,16 +958,16 @@ Kritik hataları kayıt altına almak, testlerin yürütülmesini durduracak ve
 
 ### Türetilmiş alanların test edilmesi
 
-Testing derived fields is a feature which allows users to set a field on a certain entity and have another entity be updated automatically if it derives one of its fields from the first entity.
+Türetilmiş alanları test etme özelliği, belirli bir varlıkta bir alan belirleyip, bu varlıktan türetilmiş bir alan içeriyoren başka bir varlığın otomatik olarak güncellenmesini sağlayan bir özelliktir.
 
-Before version `0.6.0` it was possible to get the derived entities by accessing them as entity fields/properties, like so:
+Sürüm `0.6.0` öncesinde, türetilmiş varlıklarıa varlık alanları/özellikleri olarak erişerek şu şekilde ulaşmak mümkündü:
 
 ```typescript
 let entity = ExampleEntity.load('id')
 let derivedEntity = entity.derived_entity
 ```
 
-As of version `0.6.0`, this is done by using the `loadRelated` function of graph-node, the derived entities can be accessed the same way as in the handlers.
+Sürüm `0.6.0` itibarıyla bu işlem, graph-node’un `loadRelated` fonksiyonu kullanılarak yapılmaktadır. Türetilmiş varlıklara, işleyicilerdekiyle aynı şekilde erişilebilir.
 
 ```typescript
 test('Derived fields example test', () => {
@@ -1000,9 +1009,9 @@ test('Derived fields example test', () => {
 })
 ```
 
-### Testing `loadInBlock`
+### `loadInBlock`'u Test Etme
 
-As of version `0.6.0`, users can test `loadInBlock` by using the `mockInBlockStore`, it allows mocking entities in the block cache.
+Sürüm `0.6.0` itibarıyla, kullanıcılar `loadInBlock` işlevini `mockInBlockStore` kullanarak test edebilir, bu sayede blok önbelleğindeki varlıkları simüle edebilirler.
 
 ```typescript
 import { afterAll, beforeAll, describe, mockInBlockStore, test } from 'matchstick-as'
@@ -1017,12 +1026,12 @@ describe('loadInBlock', () => {
     clearInBlockStore()
   })
 
-  test('Can use entity.loadInBlock() to retrieve entity from cache store in the current block', () => {
+  test('entity.loadInBlock() metodunu kullanarak mevcut bloktaki önbellek depodan varlığı alabilir', () => {
     let retrievedGravatar = Gravatar.loadInBlock('gravatarId0')
     assert.stringEquals('gravatarId0', retrievedGravatar!.get('id')!.toString())
   })
 
-  test("Returns null when calling entity.loadInBlock() if an entity doesn't exist in the current block", () => {
+  test('Varlık mevcut blokta yoksa entity.loadInBlock() çağrıldığında null döndürür', () => {
     let retrievedGravatar = Gravatar.loadInBlock('IDoNotExist')
     assert.assertNull(retrievedGravatar)
   })
@@ -1086,46 +1095,46 @@ test('Data source simple mocking example', () => {
 
 dataSourceMock.resetValues()'in en sonda çağrıldığına dikkat edin. Bunun nedeni değerler değiştirildiğinde hatırlanır ve varsayılan değerlere geri dönmek istiyorsanız sıfırlanmaları gerekir.
 
-### Testing dynamic data source creation
+### Dinamik veri kaynağı oluşturulmasının test edilmesi
 
-As of version `0.6.0`, it is possible to test if a new data source has been created from a template. This feature supports both ethereum/contract and file/ipfs templates. There are four functions for this:
+Sürüm `0.6.0` itibarıyla, yeni bir veri kaynağının bir şablonu temel alarak oluşturulup oluşturulmadığını test etmek mümkündür. Bu özellik hem ethereum/sözleşme hem de dosya/ipfs şablonlarını destekler. Bunun için dört fonksiyon bulunmaktadır:
 
-- `assert.dataSourceCount(templateName, expectedCount)` can be used to assert the expected count of data sources from the specified template
-- `assert.dataSourceExists(templateName, address/ipfsHash)` asserts that a data source with the specified identifier (could be a contract address or IPFS file hash) from a specified template was created
-- `logDataSources(templateName)` prints all data sources from the specified template to the console for debugging purposes
-- `readFile(path)` reads a JSON file that represents an IPFS file and returns the content as Bytes
+- `assert.dataSourceCount(templateName, expectedCount)` belirli bir şablondan beklenen veri kaynağı sayısını doğrulamak için kullanılabilir
+- `assert.dataSourceExists(templateName, address/ipfsHash)` belirli bir şablondan belirtilen kimliğe sahip (bu kimlik sözleşme adresi veya IPFS dosya hash’i olabilir) bir veri kaynağının oluşturulmuş olduğunu doğrular
+- `logDataSources(templateName)`, belirtilen şablonda bulunan tüm veri kaynaklarını hata ayıklama amacıyla konsola yazdırır
+- `readFile(path)`, bir IPFS dosyasını temsil eden JSON dosyasını okur ve içeriği Bytes olarak döndürür
 
-#### Testing `ethereum/contract` templates
+#### `ethereum/contract` şablonlarının test edilmesi
 
 ```typescript
-test('ethereum/contract dataSource creation example', () => {
-  // Assert there are no dataSources created from GraphTokenLockWallet template
+test('ethereum/sözleşme dataSource oluşturma örneği', () => {
+  // GraphTokenLockWallet şablonundan oluşturulmuş veri kaynağı olmadığını doğrula
   assert.dataSourceCount('GraphTokenLockWallet', 0)
 
-  // Create a new GraphTokenLockWallet datasource with address 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
+  // 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A adresiyle yeni bir GraphTokenLockWallet veri kaynağı oluştur
   GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
 
-  // Assert the dataSource has been created
+  // datSource oluşturulduğunu doğrula  
   assert.dataSourceCount('GraphTokenLockWallet', 1)
 
-  // Add a second dataSource with context
+  // İkinci dataSource'u bağlamıyla ekle
   let context = new DataSourceContext()
   context.set('contextVal', Value.fromI32(325))
 
   GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
 
-  // Assert there are now 2 dataSources
+  // Şimdi 2 veri kaynağı olduğunu doğrula
   assert.dataSourceCount('GraphTokenLockWallet', 2)
 
-  // Assert that a dataSource with address "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B" was created
-  // Keep in mind that `Address` type is transformed to lower case when decoded, so you have to pass the address as all lower case when asserting if it exists
+  // "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B" adresine sahip bir veri kaynağının oluşturulduğunu doğrula
+  // `Address` türü çözümlendiğinde küçük harfe dönüştürüldüğünden, doğrulama yaparken adresi tamamen küçük harf olarak geçmelisiniz
   assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
 
   logDataSources('GraphTokenLockWallet')
 })
 ```
 
-##### Example `logDataSource` output
+##### `logDataSource` çıktısı örneği
 
 ```bash
 🛠  {
@@ -1149,11 +1158,11 @@ test('ethereum/contract dataSource creation example', () => {
 }
 ```
 
-#### Testing `file/ipfs` templates
+#### `dosya/ipfs` şemalarını test etme
 
-Similarly to contract dynamic data sources, users can test test file datas sources and their handlers
+Akıllı sözleşme dinamik veri kaynaklarına benzer şekilde kullanıcılar, test dosyası veri kaynaklarını ve bunların işleyicilerini test edebilirler
 
-##### Example `subgraph.yaml`
+##### `subgraph.yaml` örneği
 
 ```yaml
 ...
@@ -1174,27 +1183,27 @@ templates:
           file: ./abis/GraphTokenLockWallet.json
 ```
 
-##### Example `schema.graphql`
+##### `schema.graphql` örneği
 
 ```graphql
 """
-Token Lock Wallets which hold locked GRT
+Kilitli GRT tutan Token Kilit Cüzdanları
 """
 type TokenLockMetadata @entity {
-  "The address of the token lock wallet"
+  "Token kilit cüzdanının adresi"
   id: ID!
-  "Start time of the release schedule"
+  "Serbest bırakma programının başlangıç zamanı"
   startTime: BigInt!
-  "End time of the release schedule"
+  "Serbest bırakma programının bitiş zamanı"
   endTime: BigInt!
-  "Number of periods between start time and end time"
+  "Başlangıç zamanı ile bitiş zamanı arasındaki periyot sayısı"
   periods: BigInt!
-  "Time when the releases start"
+  "Serbest bırakmaların başladığı zaman"
   releaseStartTime: BigInt!
 }
 ```
 
-##### Example `metadata.json`
+##### `metadata.json` örneği
 
 ```json
 {
@@ -1205,13 +1214,14 @@ type TokenLockMetadata @entity {
 }
 ```
 
-##### Example handler
+##### İşleyici örneği
 
 ```typescript
 export function handleMetadata(content: Bytes): void {
-  // dataSource.stringParams() returns the File DataSource CID
-  // stringParam() will be mocked in the handler test
-  // for more info https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
+  // dataSource.stringParams() File Veri Kaynağı CID'sini döndürür
+  // stringParam() işleyici testinde taklit edilecektir
+  // daha fazla bilgi için https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
+process-files
   let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
   const value = json.fromBytes(content).toObject()
 
@@ -1233,7 +1243,7 @@ export function handleMetadata(content: Bytes): void {
 }
 ```
 
-##### Example test
+##### Test örneği
 
 ```typescript
 import { assert, test, dataSourceMock, readFile } from 'matchstick-as'
@@ -1243,32 +1253,32 @@ import { handleMetadata } from '../../src/token-lock-wallet'
 import { TokenLockMetadata } from '../../generated/schema'
 import { GraphTokenLockMetadata } from '../../generated/templates'
 
-test('file/ipfs dataSource creation example', () => {
-  // Generate the dataSource CID from the ipfsHash + ipfs path file
-  // For example QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
+test('dosya/ipfs veri kaynağı oluşturma örneği', () => {
+  // ipfsHash + ipfs dosya yolu kullanılarak veri kaynağı CID'si oluşturulur
+  // Örneğin QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
   const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
   const CID = `${ipfshash}/example.json`
 
-  // Create a new dataSource using the generated CID
+  // Oluşturulan CID kullanılarak yeni bir dataSource oluşturulur
   GraphTokenLockMetadata.create(CID)
 
-  // Assert the dataSource has been created
+  // dataSource oluşturulduğunu doğrula
   assert.dataSourceCount('GraphTokenLockMetadata', 1)
   assert.dataSourceExists('GraphTokenLockMetadata', CID)
   logDataSources('GraphTokenLockMetadata')
 
-  // Now we have to mock the dataSource metadata and specifically dataSource.stringParam()
-  // dataSource.stringParams actually uses the value of dataSource.address(), so we will mock the address using dataSourceMock from  matchstick-as
-  // First we will reset the values and then use dataSourceMock.setAddress() to set the CID
+  // Şimdi dataSource metadatasını ve spesifik olarak dataSource.stringParam()'ı taklit etmemiz gerekiyor
+  // dataSource.stringParams aslında dataSource.address() değerini kullanır, bu yüzden  matchstick-as kütüphanesinden aldığımız dataSourceMock ile adresi taklit edeceğiz
+  // İlk olarak değerleri sıfırlayıp ardından dataSourceMock.setAddress() ile CID'yi atayacağız
   dataSourceMock.resetValues()
   dataSourceMock.setAddress(CID)
 
-  // Now we need to generate the Bytes to pass to the dataSource handler
-  // For this case we introduced a new function readFile, that reads a local json and returns the content as Bytes
+  // Şimdi dataSource işleyicisine geçirmek için Bytes oluşturmalıyız
+  // Bunun yerel bir json dosyasını okuyan ve içeriğini Bytes olarak döndüren readFile fonksiyonunu kullanıyoruz
   const content = readFile(`path/to/metadata.json`)
   handleMetadata(content)
 
-  // Now we will test if a TokenLockMetadata was created
+  // Şimdi bir TokenLockMetadata'nın oluşturulup oluşturulmadığını test edeceğiz
   const metadata = TokenLockMetadata.load(CID)
 
   assert.bigIntEquals(metadata!.endTime, BigInt.fromI32(1))
@@ -1368,22 +1378,26 @@ Tutulan kayıt çıktısı test çalışma süresini içerir. İşte buna bir ö
 
 > Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined
 
-Bu, AssemblyScript tarafından desteklenmeyen `console.log`'u kullandığınız anlamına gelmektedir. Lütfen [Logging API](/developing/graph-ts/api/#logging-api) kullanmayı düşünün
+Bu hata kodunuzda `console.log` kullandığınız anlamına gelir. Bu komut AssemblyScript tarafından desteklenmez. Lütfen [Logging API](/developing/graph-ts/api/#logging-api)'yi kullanmayı düşünün.
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Argümanlardaki uyumsuzluk, `graph-ts` ve `matchstick-as` arasındaki uyumsuzluktan kaynaklanır. Bu gibi sorunları düzeltmenin en iyi yolu her şeyi en son yayınlanan sürüme güncellemektir.
 
+## Ek Kaynaklar
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Geribildirim
 
 Soru, geri bildirim, özellik istekleri veya sadece iletişim kurmak istiyorsanız en iyi yer Matchstick için ayrılmış bir kanal olan 🔥| unit-testing kanalına sahip olduğumuz The Graph Discord'udur.

From 597b3531211ebf45abcc146f7e8aa8076b3af1bf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:54 -0500
Subject: [PATCH 0055/1325] New translations developer-faqs.mdx (Romanian)

---
 .../pages/ro/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/ro/developing/developer-faqs.mdx b/website/pages/ro/developing/developer-faqs.mdx
index 7f4da3639ee0..e783db4c3d8f 100644
--- a/website/pages/ro/developing/developer-faqs.mdx
+++ b/website/pages/ro/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: FAQs al Developerilor
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 68b94b252d8dce6d2dcbd06e005cd05d96580de6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:56 -0500
Subject: [PATCH 0056/1325] New translations developer-faqs.mdx (French)

---
 .../pages/fr/developing/developer-faqs.mdx    | 148 +++++++++---------
 1 file changed, 75 insertions(+), 73 deletions(-)

diff --git a/website/pages/fr/developing/developer-faqs.mdx b/website/pages/fr/developing/developer-faqs.mdx
index e46bbbcfeb19..5d05fd278df2 100644
--- a/website/pages/fr/developing/developer-faqs.mdx
+++ b/website/pages/fr/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: FAQs pour les développeurs
 ---
 
-## 1. Qu'est-ce qu'un subgraph ?
+Cette page résume certaines des questions les plus courantes pour les développeurs construisant sur The Graph.
 
-Un subgraph est une API personnalisée construite sur des données de blockchain. Les subgraphs sont interrogés à l'aide du langage de requête GraphQL et sont déployés sur un nœud de graph à l'aide de Graphe CLI . Dès qu'ils sont déployés et publiés sur le réseau décentralisé de The Graph, Les indexeurs traitent les subgraphs et les rendent disponibles pour être interrogés par les consommateurs de subgraphs.
+## Relatif aux Subgraphs
 
-## 2. Puis-je supprimer mon subgraph ?
+### 1. Qu'est-ce qu'un subgraph ?
 
-Il n'est pas possible de supprimer des subgraphs une fois qu'ils sont créés.
+Un subgraph est une API personnalisée construite sur des données blockchain. Les subgraphs sont interrogés en utilisant le langage de requête GraphQL et sont déployés sur Graph Node en utilisant Graph CLI. Une fois déployés et publiés sur le réseau décentralisé de The Graph, les Indexeurs traitent les subgraphs et les rendent disponibles pour que les consommateurs de subgraphs puissent les interroger.
 
-## 3. Puis-je changer le nom de mon subgraph ?
+### 2. Quelle est la première étape pour créer un subgraph ?
 
-Non. Une fois qu'un subgraph est créé, son nom ne peut plus être modifié. Assurez-vous d'y réfléchir attentivement avant de créer votre subgraph afin qu'il soit facilement consultable et identifiable par d'autres dapps.
+Pour créer avec succès un subgraph, vous devrez installer Graph CLI. Consultez le [guide de démarrage rapide](/quick-start/) pour commencer. Pour des informations détaillées, voir [Création d'un subgraph](/developing/creating-a-subgraph/).
 
-## 4. Puis-je modifier le compte GitHub associé à mon subgraph ?
+### 3. Suis-je toujours en mesure de créer un subgraph si mes smart contracts n'ont pas d'événements ?
 
-Non. Dès qu'un subgraph est créé, le compte GitHub associé ne peut pas être modifié. Assurez-vous d'y réfléchir attentivement avant de créer votre subgraph.
+Il est fortement recommandé de structurer vos smart contracts pour avoir des événements associés aux données que vous souhaitez interroger. Les gestionnaires d'événements du subgraph sont déclenchés par des événements de contrat et constituent le moyen le plus rapide de récupérer des données utiles.
 
-## 5. Suis-je toujours en mesure de créer un subgraph si mes smart contracts n'ont pas d'événements ?
+Si les contrats avec lesquels vous travaillez ne contiennent pas d'événements, votre subgraph peut utiliser des gestionnaires d'appels et de blocs pour déclencher l'indexation. Cependant, ceci n'est pas recommandé, car les performances seront nettement plus lentes.
 
-Il est fortement recommandé de structurer vos smart contracts pour avoir des événements associés aux données que vous souhaitez interroger. Les gestionnaires d'événements du subgraph sont déclenchés par des événements de contrat et constituent le moyen le plus rapide de récupérer des données utiles.
+### 4. Puis-je modifier le compte GitHub associé à mon subgraph ?
+
+Non. Une fois un subgraph créé, le compte GitHub associé ne peut pas être modifié. Veuillez vous assurer de bien prendre en compte ce détail avant de créer votre subgraph.
+
+### 5. Comment mettre à jour un subgraph sur le mainnet ?
 
-Si les contrats avec lesquels vous travaillez ne contiennent pas d'événements, votre subgraph peut utiliser des gestionnaires d'appels et de blocs pour déclencher l'indexation. Bien que cela ne soit pas recommandé, les performances seront considérablement plus lentes.
+Vous pouvez déployer une nouvelle version de votre subgraph sur Subgraph Studio en utilisant la CLI. Cette action maintient votre subgraph privé, mais une fois que vous en êtes satisfait, vous pouvez le publier sur Graph Explorer. Cela créera une nouvelle version de votre subgraph sur laquelle les Curateurs pourront commencer à signaler.
+
+### 6. Est-il possible de dupliquer un subgraph vers un autre compte ou endpoint sans le redéployer ?
+
+Vous devez redéployer le subgraph, mais si l'ID de subgraph (hachage IPFS) ne change pas, il n'aura pas à se synchroniser depuis le début.
 
-## 6. Est-il possible de déployer un subgraph portant le même nom pour plusieurs réseaux ?
+### 7. Comment puis-je appeler une fonction d'un contrat ou accéder à une variable d'état publique depuis mes mappages de subgraph ?
 
-Vous aurez besoin de noms distincts pour plusieurs réseaux. Bien que vous ne puissiez pas avoir différents subgraphs sous le même nom, il existe des moyens pratiques d'avoir une seule base de code pour plusieurs réseaux. Retrouvez plus d'informations à ce sujet dans notre documentation : [Déploiement d'un subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-an-subgraph)
+Consultez `Accès à l'état du contrat intelligent` dans la section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Puis-je importer `ethers.js` ou d'autres bibliothèques JS dans mes mappages de subgraph ?
+
+Actuellement non, car les mappages sont écrits en AssemblyScript.
+
+Une solution alternative possible serait de stocker des données brutes dans des entités et à effectuer une logique nécessitant des bibliothèques JS sur le client.
+
+### 9. Lorsqu'on écoute plusieurs contrats, est-il possible de sélectionner l'ordre des contrats pour écouter les événements ?
+
+Dans un subgraph, les événements sont toujours traités dans l'ordre dans lequel ils apparaissent dans les blocs, que ce soit sur plusieurs contrats ou non.
 
-## 7. En quoi les modèles sont-ils différents des sources de données ?
+### 10. En quoi les modèles sont-ils différents des sources de données ?
 
-Les modèles vous permettent de créer des sources de données à la volée, pendant l'indexation de votre subgraph. Il se peut que votre contrat engendre de nouveaux contrats au fur et à mesure que les gens interagissent avec lui, et puisque vous connaissez la forme de ces contrats (ABI, événements, etc.) à l'avance, vous pouvez définir comment vous souhaitez les indexer dans un modèle et lorsqu'ils sont générés, votre subgraph créera une source de données dynamique en fournissant l'adresse du contrat.
+Les modèles vous permettent de créer rapidement des sources de données , pendant que votre subgraph est en cours d'indexation. Votre contrat peut générer de nouveaux contrats à mesure que les gens interagissent avec lui. Étant donné que vous connaissez la structure de ces contrats (ABI, événements, etc.) à l'avance, vous pouvez définir comment vous souhaitez les indexer dans un modèle. Lorsqu'ils sont générés, votre subgraph créera une source de données dynamique en fournissant l'adresse du contrat.
 
 Consultez la section "Instanciation d'un modèle de source de données" sur : [Modèles de source de données](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. Comment m'assurer que j'utilise la dernière version de graph-node pour mes déploiements locaux ?
+### 11. Est-il possible de configurer un subgraph en utilisant `graph init` de `graph-cli` avec deux contrats ? Ou devrais-je ajouter manuellement une autre source de données dans `subgraph.yaml` après avoir exécuté `graph init` ?
 
-Vous pouvez exécuter la commande suivante :
+Oui. Avec la commande `graph init` elle-même, vous pouvez ajouter plusieurs sources de données en entrant les contrats l'un après l'autre.
 
-```sh
-docker pull graphprotocol/graph-node:dernier
-```
+Vous pouvez également utiliser la commande `graph add` pour ajouter une nouvelle source de données.
 
-**REMARQUE :** docker / docker-compose utilisera toujours la version de graph-node extraite la première fois que vous l'avez exécuté, il est donc important de le faire pour vous assurer que vous êtes à jour avec la dernière version de graph-node.
+### 12. Dans quel ordre les gestionnaires d'événements, de blocs et d'appels sont-ils déclenchés pour une source de données ?
 
-## 9. Comment appeler une fonction de contrat ou accéder à une variable d'état publique à partir de mes mappages de subgraphs ?
+Les gestionnaires d'événements et d'appels sont d'abord classés par index de transaction à l'intérieur du bloc. Les gestionnaires d'événements et d'appels au sein d'une même transaction sont ordonnés selon une convention : d'abord les gestionnaires d'événements, puis les gestionnaires d'appels, chaque type respectant l'ordre défini dans le manifeste. Les gestionnaires de blocs sont exécutés après les gestionnaires d'événements et d'appels, dans l'ordre où ils sont définis dans le manifeste. Ces règles d'ordre sont également susceptibles d'être modifiées.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+Lorsque de nouvelles sources de données dynamiques sont créées, les gestionnaires définis pour les sources de données dynamiques ne commenceront à être traités qu'une fois que tous les gestionnaires de sources de données existantes auront été traités, et ils se répéteront dans la même séquence chaque fois qu'ils seront déclenchés.
 
-## 10. Est-il possible de configurer un subgraph en utilisant `graph init` à partir de `graph-cli` avec deux contrats ? Ou dois-je ajouter manuellement une autre source de données dans `subgraph.yaml` après avoir exécuté `graph init` ?
+### 13. Comment puis-je m'assurer que j'utilise la dernière version de graph-node pour mes déploiements en local ?
 
-Oui. Dans la commande `graph init` elle-même, vous pouvez ajouter plusieurs sources de données en saisissant les contrats l'un après l'autre. Vous pouvez également utiliser la commande `graph add` pour ajouter une nouvelle source de données.
+Vous pouvez exécuter la commande suivante :
 
-## 11. Je souhaite contribuer ou ajouter un problème GitHub. Où puis-je trouver les référentiels open source ?
+```sh
+docker pull graphprotocol/graph-node:dernier
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [l'outil de graph](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Remarque : docker / docker-compose utilisera toujours la version de graph-node qui a été téléchargée la première fois que vous l'avez exécuté, alors assurez-vous d'être à jour avec la dernière version de graph-node.
 
-## 12. Quelle est la méthode recommandée pour créer des identifiants « générés automatiquement » pour une entité lors du traitement des événements ?
+### 14. Quelle est la méthode recommandée pour créer des Ids "autogénérés" pour une entité pendant la gestion des événements ?
 
 Si une seule entité est créée lors de l'événement et s'il n'y a rien de mieux disponible,alors le hachage de transaction + index de journal serait unique. Vous pouvez les masquer en les convertissant en octets, puis en les redirigeant vers `crypto.keccak256`, mais cela ne le rendra pas plus unique.
 
-## 13. Lorsqu'on écoute plusieurs contrats, est-il possible de sélectionner l'ordre des contrats pour écouter les événements ?
+### 15. Puis-je supprimer mon subgraph ?
 
-Dans un subgraph, les événements sont toujours traités dans l'ordre dans lequel ils apparaissent dans les blocs, que ce soit sur plusieurs contrats ou non.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
+
+## Relatif au Réseau
+
+### 16. Quels réseaux sont supportés par The Graph?
+
+Vous pouvez trouver la liste des réseaux supportés [ici](/developing/supported-networks).
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+### 17. Est-il possible de faire la différence entre les réseaux (mainnet, Sepolia, local) dans les gestionnaires d'événements?
 
 Oui. Vous pouvez le faire en important `graph-ts` comme dans l'exemple ci-dessous :
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Prenez-vous en charge les gestionnaires de blocs et d'appels sur Sepolia?
 
-Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
+Oui. Sepolia prend en charge les gestionnaires de blocs, les gestionnaires d'appels et les gestionnaires d'événements. Il convient de noter que les gestionnaires d'événements sont beaucoup plus performants que les deux autres gestionnaires, et ils sont pris en charge sur tous les réseaux compatibles EVM.
 
-## 16. Puis-je importer ethers.js ou d'autres bibliothèques JS dans mes mappages de subgraphs ?
+## En rapport avec l'indexation & les requêtes
 
-Pas pour le moment, car les mappages sont écrits en AssemblyScript. Une autre solution possible consiste à stocker les données brutes dans des entités et à exécuter une logique qui nécessite des bibliothèques JS du client.
+### 19. Est-il possible de spécifier à partir de quel bloc commencer l'indexation?
 
-## 17. Est-il possible de spécifier sur quel bloc démarrer l'indexation ?
+Oui. `dataSources.source.startBlock` dans le fichier `subgraph.yaml` spécifie le numéro du bloc à partir duquel la Source de donnée commence l'indexation. Dans la plupart des cas, nous suggérons d'utiliser le bloc où le contrat a été créé : [Blocs de départ](/developing/creating-a-subgraph#start-blocks)
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+### 20. Quels sont quelques conseils pour augmenter les performances d'indexation? Mon subgraph prend beaucoup de temps à se synchroniser
 
-## 18. Existe-t-il des astuces pour améliorer les performances de l'indexation ? La synchronisation de mon subgraph prend beaucoup de temps
+Oui, vous devriez consulter la fonctionnalité optionnelle de bloc de départ pour commencer l'indexation à partir du bloc où le contrat a été déployé : [Blocs de départ](/developing/creating-a-subgraph#start-blocks)
 
-Oui, vous devriez jeter un coup d'œil à la fonctionnalité optionnelle de bloc de départ pour commencer l'indexation à partir du bloc où le contrat a été déployé : [Blocs de départ](/developing/creating-a-subgraph#start-blocks)
-
-## 19. Existe-t-il un moyen d'interroger directement le subgraph pour déterminer le dernier numéro de bloc qu'il a indexé ?
+### 21. Existe-t-il un moyen d'interroger directement le subgraph pour déterminer le dernier numéro de bloc qu'il a indexé?
 
 Oui ! Essayez la commande suivante, en remplaçant "organization/subgraphName" par l'organisation sous laquelle elle est publiée et le nom de votre subgraphe :
 
@@ -102,44 +121,27 @@ Oui ! Essayez la commande suivante, en remplaçant "organization/subgraphName"
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/ index-node/graphql
 ```
 
-## 20. Quels réseaux sont pris en charge par The Graph ?
-
-Vous pouvez trouver la liste des réseaux supportés [ici](/developing/supported-networks).
-
-## 21. Est-il possible de dupliquer un subgraph sur un autre compte ou point de terminaison sans redéployer ?
-
-Vous devez redéployer le subgraph, mais si l'ID de subgraph (hachage IPFS) ne change pas, il n'aura pas à se synchroniser depuis le début.
-
-## 22. Est-il possible d'utiliser Apollo Federation au-dessus du graph-node ?
-
-La fédération n'est pas encore supportée, bien que nous souhaitions la prendre en charge à l'avenir. Pour le moment, vous pouvez utiliser l'assemblage de schémas, soit sur le client, soit via un service proxy.
-
-## 23. Y a-t-il une limite au nombre d'objets que The Graph peut renvoyer par requête ?
+### 22. Existe-t-il une limite au nombre d'objets que The Graph peut retourner par requête?
 
-Par défaut, les réponses aux requêtes sont limitées à 100 éléments par collection. Si vous souhaitez en recevoir plus, vous pouvez aller jusqu'à 1000 articles par collection et au-delà, vous pouvez paginer avec :
+Par défaut, les réponses aux requêtes sont limitées à 100 éléments par collection. Si vous voulez en recevoir plus, vous pouvez aller jusqu'à 1000 éléments par collection et au-delà, vous pouvez paginer avec :
 
 ```graphql
 quelquesCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. Si mon interface dapp utilise The Graph pour les requêtes, dois-je écrire ma clé de requête directement dans l'interface ? Et si nous payons des frais de requête pour les utilisateurs : les utilisateurs malveillants rendront-ils nos frais de requête très élevés ?
-
-Actuellement, l'approche recommandée pour une dapp consiste à ajouter la clé à l'interface et à l'exposer aux utilisateurs finaux. Cela dit, vous pouvez limiter cette clé à un nom d'hôte, comme _yourdapp.io_ et subgraph. La passerelle est actuellement gérée par Edge & Node. Une partie de la responsabilité d'une passerelle est de surveiller les comportements abusifs et de bloquer le trafic des clients malveillants.
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Rendez-vous sur le service hébergé afin de trouver les subgraphs que vous ou d'autres personnes avez déployés sur le service hébergé. Vous pouvez le trouver [ici](https://thegraph.com/hosted-service).
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-## 26. Will the hosted service start charging query fees?
+Actuellement, l'approche recommandée pour un dapp est d'ajouter la clé au frontend et de l'exposer aux utilisateurs finaux. Cela dit, vous pouvez limiter cette clé à un nom d'hôte, comme _yourdapp.io_ et subgraph. La passerelle est actuellement gérée par Edge & Node. Une partie de la responsabilité d'une passerelle est de surveiller les comportements abusifs et de bloquer le trafic des clients malveillants.
 
-The Graph ne facturera jamais le service hébergé. The Graph est un protocole décentralisé, et faire payer un service centralisé n'est pas conforme aux valeurs du Graphe. Le service hébergé a toujours été une étape temporaire pour aider à passer au réseau décentralisé. Les développeurs disposeront d'un délai suffisant pour passer au réseau décentralisé lorsqu'ils le souhaiteront.
+## Divers
 
-## 27. How do I update a subgraph on mainnet?
+### 24. Est-il possible d'utiliser Apollo Federation sur graph-node?
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+La fédération n'est pas encore supportée. Pour le moment, vous pouvez utiliser la fusion de schémas, soit sur le client, soit via un service proxy.
 
-## 28. Dans quel ordre les gestionnaires d'événements, de blocages et d'appels sont-ils déclenchés pour une source de données ?
+### 25. Je veux contribuer ou ajouter un problème GitHub. Où puis-je trouver les dépôts open source?
 
-Les gestionnaires d'événements et d'appels sont d'abord classés par index de transaction à l'intérieur du bloc. Les gestionnaires d'événements et d'appels au sein d'une même transaction sont ordonnés selon une convention : d'abord les gestionnaires d'événements, puis les gestionnaires d'appels, chaque type respectant l'ordre défini dans le manifeste. Les gestionnaires de blocs sont exécutés après les gestionnaires d'événements et d'appels, dans l'ordre où ils sont définis dans le manifeste. Ces règles d'ordre sont également susceptibles d'être modifiées.
-
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [l'outil de graph](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 9306e3d1d879cddca6d53b01e8af106a5309a979 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:57 -0500
Subject: [PATCH 0057/1325] New translations developer-faqs.mdx (Spanish)

---
 .../pages/es/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/es/developing/developer-faqs.mdx b/website/pages/es/developing/developer-faqs.mdx
index 55357e42a4ef..3cf0a885e79c 100644
--- a/website/pages/es/developing/developer-faqs.mdx
+++ b/website/pages/es/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Preguntas Frecuentes de los Desarrolladores
 ---
 
-## 1. ¿Qué es un subgrafo?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-Un subgrafo es una API personalizada construida sobre datos de blockchain. Los subgrafos se consultan mediante el lenguaje de consulta GraphQL y son deployados en un Graph Node usando Graph CLI. Una vez deployados y publicados en la red descentralizada de The Graph, los indexadores procesan los subgrafos y los ponen a disposición de los consumidores de subgrafos para que los consulten.
+## Subgraph Related
 
-## 2. ¿Puedo eliminar mi subgrafo?
+### 1. ¿Qué es un subgrafo?
 
-No es posible eliminar los subgrafos una vez creados.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. ¿Puedo cambiar el nombre de mi subgrafo?
+### 2. What is the first step to create a subgraph?
 
-No. Una vez que se crea un subgrafo, no se puede cambiar el nombre. Asegúrate de pensar en esto cuidadosamente antes de crear tu subgrafo para que sea fácil de buscar e identificar por otras dApps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. ¿Puedo cambiar la cuenta de GitHub asociada con mi subgrafo?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Una vez que se crea un subgrafo, la cuenta de GitHub asociada no puede ser modificada. Asegúrate de pensarlo bien antes de crear tu subgrafo.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. ¿Todavía puedo crear un subgrafo si mis contratos inteligentes no tienen eventos?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-Es muy recomendable que estructures tus contratos inteligentes para tener eventos asociados a los datos que te interesa consultar. Los handlers de eventos en el subgrafo son activados por los eventos del contrato y son, con mucho, la forma más rápida de recuperar datos útiles.
+### 4. ¿Puedo cambiar la cuenta de GitHub asociada con mi subgrafo?
 
-Si los contratos con los que estás trabajando no contienen eventos, tu subgrafo puede utilizar handlers de llamadas y bloques para activar la indexación. Aunque esto no se recomienda, ya que el rendimiento será significativamente más lento.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. ¿Es posible deployar un subgrafo con el mismo nombre para varias redes?
+### 5. How do I update a subgraph on mainnet?
 
-Necesitarás nombres separados para varias redes. Si bien no puedes tener diferentes subgrafos con el mismo nombre, existen formas convenientes de tener una base de código única para varias redes. Encuentra más sobre esto en nuestra documentación: [Redeploying a Subgraph](/implementación/implementación-de-un-subgráfico-a-alojamiento#reimplementación-de-un-subgráfico)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. ¿En qué se diferencian las plantillas de las fuentes de datos?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Las plantillas te permiten crear fuentes de datos sobre la marcha, mientras tu subgrafo está indexando. Puede darse el caso de que tu contrato genere nuevos contratos a medida que la gente interactúe con él, y dado que conoces la forma de esos contratos (ABI, eventos, etc.) por adelantado puedes definir cómo quieres indexarlos en una plantilla y cuando se generen tu subgrafo creará una fuente de datos dinámica proporcionando la dirección del contrato.
+Tienes que volver a realizar el deploy del subgrafo, pero si el ID del subgrafo (hash IPFS) no cambia, no tendrá que sincronizarse desde el principio.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Dentro de un subgrafo, los eventos se procesan siempre en el orden en que aparecen en los bloques, independientemente de que sea a través de múltiples contratos o no.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Consulta la sección "Instantiating a data source template" en: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. ¿Cómo puedo asegurarme de que estoy utilizando la última versión de graph-node para mis deploys locales?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-Puedes ejecutar el siguiente comando:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTA:** docker/docker-compose siempre utilizará la versión de graph-node que se sacó la primera vez que se ejecutó, por lo que es importante hacer esto para asegurarse de que estás al día con la última versión de graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. ¿Cómo llamo a una función de contrato o accedo a una variable de estado pública desde mis mapeos de subgrafos?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. ¿Es posible configurar un subgrafo usando `graph init` de `graph-cli` con dos contratos? ¿O debo agregar manualmente otra fuente de datos en `subgraph.yaml` después de ejecutar `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+Puedes ejecutar el siguiente comando:
 
-## 11. Quiero contribuir o agregar un problema de GitHub. ¿Dónde puedo encontrar los repositorios de código abierto?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. ¿Cuál es la forma recomendada para crear ids "autogeneradas" para una entidad al manejar eventos?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 Si sólo se crea una entidad durante el evento y si no hay nada mejor disponible, entonces el hash de la transacción + el índice del registro serían únicos. Puedes ofuscar esto convirtiendo eso en Bytes y luego pasándolo por `crypto.keccak256` pero esto no lo hará más único.
 
-## Cuando se escuchan varios contratos, ¿es posible seleccionar el orden de los contratos para escuchar los eventos?
+### 15. Can I delete my subgraph?
 
-Dentro de un subgrafo, los eventos se procesan siempre en el orden en que aparecen en los bloques, independientemente de que sea a través de múltiples contratos o no.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+Puedes encontrar la lista de redes admitidas [aquí](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Sí. Puedes hacerlo importando `graph-ts` como en el ejemplo siguiente:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. ¿Puedo importar ethers.js u otras bibliotecas JS en mis mappings de subgrafos?
-
-Actualmente no, ya que los mapeos se escriben en AssemblyScript. Una posible solución alternativa a esto es almacenar los datos en bruto en entidades y realizar la lógica que requiere las bibliotecas JS en el cliente.
+## Indexing & Querying Related
 
-## 17. ¿Es posible especificar en qué bloque comenzar a indexar?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. ¿Hay algunos consejos para aumentar el rendimiento de la indexación? Mi subgrafo está tardando mucho en sincronizarse
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Sí, debes echar un vistazo a la función de bloque de inicio opcional para comenzar a indexar desde el bloque en el que se implementó el contrato: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. ¿Hay alguna forma de consultar el subgrafo directamente para determinar el último número de bloque que ha indexado?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 ¡Sí es posible! Prueba el siguiente comando, sustituyendo "organization/subgraphName" por la organización bajo la que se publica y el nombre de tu subgrafo:
 
@@ -102,44 +121,27 @@ Sí, debes echar un vistazo a la función de bloque de inicio opcional para come
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. ¿Qué redes son compatibles con The Graph?
-
-Puedes encontrar la lista de redes admitidas [aquí](/developing/supported-networks).
-
-## 21. ¿Es posible duplicar un subgrafo en otra cuenta o endpoint sin volver a realizar el deploy?
-
-Tienes que volver a realizar el deploy del subgrafo, pero si el ID del subgrafo (hash IPFS) no cambia, no tendrá que sincronizarse desde el principio.
-
-## 22. ¿Es posible usar Apollo Federation encima de graph-node?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-Federation aún no es compatible, aunque queremos apoyarla en el futuro. Por el momento, algo que se puede hacer es utilizar el stitching de esquemas, ya sea en el cliente o a través de un servicio proxy.
-
-## 23. ¿Existe un límite en el número de objetos que The Graph puede devolver por consulta?
-
-Por defecto, las respuestas a las consultas están limitadas a 100 elementos por colección. Si quieres recibir más, puedes llegar hasta 1000 elementos por colección y más allá, puedes paginar con:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. Si mi interfaz de dapp usa The Graph para realizar consultas, ¿debo escribir mi clave de consulta directamente en la interfaz? ¿Qué pasa si pagamos tarifas de consulta para los usuarios? ¿Los usuarios malintencionados harán que nuestras tarifas de consulta sean muy altas?
-
-Actualmente, el enfoque recomendado para una dapp es añadir la clave al frontend y exponerla a los usuarios finales. Dicho esto, puedes limitar esa clave a un nombre de host, como _yourdapp.io_ y subgrafo. La gateway se ejecuta actualmente por Edge & Node. Parte de la responsabilidad de un gateway es monitorear el comportamiento abusivo y bloquear el tráfico de clientes maliciosos.
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From ca83f1e28d7b9c127dfa160996cc24f874b39dc1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:58 -0500
Subject: [PATCH 0058/1325] New translations developer-faqs.mdx (Arabic)

---
 .../pages/ar/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/ar/developing/developer-faqs.mdx b/website/pages/ar/developing/developer-faqs.mdx
index 1758e9f909b6..01aa712bb83c 100644
--- a/website/pages/ar/developing/developer-faqs.mdx
+++ b/website/pages/ar/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: الأسئلة الشائعة للمطورين
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-لا يمكن حذف ال Subgraph بمجرد إنشائها.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-لا. بمجرد إنشاء ال Subgraph ، لا يمكن تغيير الاسم. تأكد من التفكير بعناية قبل إنشاء ال Subgraph الخاص بك حتى يسهل البحث عنه والتعرف عليه من خلال ال Dapps الأخرى.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-لا. بمجرد إنشاء ال Subgraph ، لا يمكن تغيير حساب GitHub المرتبط. تأكد من التفكير بعناية قبل إنشاء ال Subgraph الخاص بك.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+يجب عليك إعادة نشر ال الفرعيةرسم بياني ، ولكن إذا لم يتغير الفرعيةرسم بياني (ID (IPFS hash ، فلن يضطر إلى المزامنة من البداية.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+ضمن ال Subgraph ، تتم معالجة الأحداث دائمًا بالترتيب الذي تظهر به في الكتل ، بغض النظر عما إذا كان ذلك عبر عقود متعددة أم لا.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-يمكنك تشغيل الأمر التالي:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**ملاحظة:** سيستخدم docker / docker-compose دائما أي إصدار من graph-node تم سحبه في المرة الأولى التي قمت بتشغيلها ، لذلك من المهم القيام بذلك للتأكد من أنك محدث بأحدث إصدار من graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+يمكنك تشغيل الأمر التالي:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 إذا تم إنشاء كيان واحد فقط أثناء الحدث ولم يكن هناك أي شيء متاح بشكل أفضل ، فسيكون hash الإجراء + فهرس السجل فريدا. يمكنك إبهامها عن طريق تحويلها إلى Bytes ثم تمريرها عبر `crypto.keccak256` ولكن هذا لن يجعلها فريدة من نوعها.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-ضمن ال Subgraph ، تتم معالجة الأحداث دائمًا بالترتيب الذي تظهر به في الكتل ، بغض النظر عما إذا كان ذلك عبر عقود متعددة أم لا.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 نعم. يمكنك القيام بذلك عن طريق استيراد `graph-ts` كما في المثال أدناه:
 
@@ -78,23 +99,21 @@ Yes. On `graph init` command itself you can add multiple datasources by entering
 ()dataSource.address
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-ليس حاليًا ، حيث تتم كتابة ال mappings في AssemblyScript. أحد الحلول البديلة الممكنة لذلك هو تخزين البيانات الأولية في الكيانات وتنفيذ المنطق الذي يتطلب مكتبات JS على ال client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 نعم! جرب الأمر التالي ، مع استبدال "Organization / subgraphName" بالمؤسسة واسم الـ subgraph الخاص بك:
 
@@ -102,19 +121,7 @@ Yes, you should take a look at the optional start block feature to start indexin
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-يجب عليك إعادة نشر ال الفرعيةرسم بياني ، ولكن إذا لم يتغير الفرعيةرسم بياني (ID (IPFS hash ، فلن يضطر إلى المزامنة من البداية.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-لم يتم دعم Federation بعد ، على الرغم من أننا نريد دعمه في المستقبل. و في الوقت الحالي ، الذي يمكنك القيام به هو استخدام schema stitching ، إما على client أو عبر خدمة البروكسي.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From b2d809608cf573bccc72c49690540f12bef73abc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:31:59 -0500
Subject: [PATCH 0059/1325] New translations developer-faqs.mdx (Czech)

---
 .../pages/cs/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/cs/developing/developer-faqs.mdx b/website/pages/cs/developing/developer-faqs.mdx
index 828debf0f7a4..429f18be662c 100644
--- a/website/pages/cs/developing/developer-faqs.mdx
+++ b/website/pages/cs/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: FAQs pro vývojáře
 ---
 
-## 1. Co je to podgraf?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-Podgraf je vlastní API postavené na datech blockchainu. Podgrafy jsou dotazovány pomocí dotazovacího jazyka GraphQL a jsou nasazeny do uzlu Graf pomocí Graf CLI. Po nasazení a zveřejnění v decentralizované síti Graf zpracovávají indexery podgrafy a zpřístupňují je k dotazování konzumentům podgrafů.
+## Subgraph Related
 
-## 2. Mohu svůj podgraf smazat?
+### 1. Co je to podgraf?
 
-Jednou vytvořené podgrafy není možné odstranit.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Mohu změnit název podgrafu?
+### 2. What is the first step to create a subgraph?
 
-Ne. Jakmile je podgraf vytvořen, nelze jeho název změnit. Před vytvořením podgrafu si to důkladně promyslete, aby byl snadno vyhledatelný a identifikovatelný ostatními dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Mohu změnit účet GitHub přidružený k mému podgrafu?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-Ne. Jakmile je podgraf vytvořen, nelze přidružený účet GitHub změnit. Než vytvoříte podgraf, důkladně si to promyslete.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Mohu vytvořit podgraf i v případě, že moje chytré smlouvy nemají události?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-Důrazně doporučujeme, abyste své chytré kontrakty strukturovali tak, aby měly události spojené s daty, na která se chcete dotazovat. Obsluhy událostí v podgrafu jsou spouštěny událostmi smlouva a jsou zdaleka nejrychlejším způsobem, jak získat užitečná data.
+### 4. Mohu změnit účet GitHub přidružený k mému podgrafu?
 
-Pokud smlouva, se kterými pracujete, neobsahují události, můžete ke spuštění indexování použít obsluhy volání a bloků. To se však nedoporučuje, protože výkon bude výrazně nižší.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Je možné nasadit jeden podgraf se stejným názvem pro více sítí?
+### 5. How do I update a subgraph on mainnet?
 
-Pro více sítí budete potřebovat samostatné názvy. I když nemůžete mít různé podgrafy pod stejným názvem, existují pohodlné způsoby, jak mít jednu kódovou základnu pro více sítí. Více informací o tom najdete v naší dokumentaci: [přemístění podgrafu](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. Jak se liší šablony od zdrojů dat?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Šablony umožňují vytvářet zdroje dat za běhu, zatímco se podgraf indexuje. Může se stát, že vaše smlouva bude vytvářet nové smlouvy, jak s ní budou lidé interagovat, a protože znáte tvar těchto smluv (ABI, události atd.) předem, můžete definovat, jak je chcete indexovat v šabloně, a když se vytvoří, váš podgraf vytvoří dynamický zdroj dat dodáním adresy smlouvy.
+Podgraf musíte znovu nasadit, ale pokud se ID podgrafu (hash IPFS) nezmění, nebude se muset synchronizovat od začátku.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+V rámci podgrafu se události zpracovávají vždy v pořadí, v jakém se objevují v blocích, bez ohledu na to, zda se jedná o více smluv.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Podívejte se do části "Instancování šablony zdroje dat" na: [Šablony datových zdrojů](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. Jak se ujistím, že pro místní nasazení používám nejnovější verzi graph-node?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-Můžete spustit následující příkaz:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**POZNÁMKA:** docker / docker-compose vždy použije tu verzi graf uzlu, která byla stažena při prvním spuštění, takže je důležité to udělat, abyste se ujistili, že máte nejnovější verzi graf uzlu.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. Jak mohu z mapování podgrafů zavolat smluvní funkci nebo přistupovat k veřejné stavové proměnné?
+Obsluhy událostí a volání jsou nejprve seřazeny podle indexu transakce v rámci bloku. Obsluhy událostí a volání v rámci téže transakce jsou seřazeny podle konvence: nejprve obsluhy událostí, pak obsluhy volání, přičemž každý typ dodržuje pořadí, v jakém jsou definovány v manifestu. Obsluhy bloků se spouštějí po obsluhách událostí a volání v pořadí, v jakém jsou definovány v manifestu. I tato pravidla řazení se mohou měnit.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+Při vytváření nových dynamických zdrojů dat se obslužné rutiny definované pro dynamické zdroje dat začnou zpracovávat až po zpracování všech existujících obslužných rutin zdrojů dat a budou se opakovat ve stejném pořadí, kdykoli budou spuštěny.
 
-## 10. Je možné vytvořit podgraf pomocí `graph init` z `graph-cli` se dvěma smlouvami? Nebo mám po spuštění `graph init` ručně přidat další datový zdroj v `subgraph.yaml`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Ano. V samotném příkazu `graph init` můžete přidat více datových zdrojů zadáním smluv za sebou. Pro přidání nového datového zdroje můžete také použít příkaz `graph add`.
+Můžete spustit následující příkaz:
 
-## 11. Chci přispět nebo přidat problém na GitHub. Kde najdu repozitáře s otevřeným zdrojovým kódem?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. Jaký je doporučený způsob vytváření "automaticky generovaných" ids pro entity při zpracování událostí?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 Pokud je během události vytvořena pouze jedna entita a pokud není k dispozici nic lepšího, pak by hash transakce + index protokolu byly jedinečné. Můžete je obfuskovat tak, že je převedete na bajty a pak je proženete přes `crypto.keccak256`, ale tím se jejich jedinečnost nezvýší.
 
-## 13. Je možné při poslechu více smluv zvolit pořadí smlouvy, ve kterém se mají události poslouchat?
+### 15. Can I delete my subgraph?
 
-V rámci podgrafu se události zpracovávají vždy v pořadí, v jakém se objevují v blocích, bez ohledu na to, zda se jedná o více smluv.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+Seznam podporovaných sítí najdete [zde](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Ano, můžete to provést importováním `graph-ts` podle níže uvedeného příkladu:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Mohu do mapování podgrafů importovat ethers.js nebo jiné JS knihovny?
-
-V současné době ne, protože mapování jsou zapsána v AssemblyScript. Jedním z možných alternativních řešení je ukládat surová data do entit a logiku, která vyžaduje knihovny JS, provádět na klientovi.
+## Indexing & Querying Related
 
-## 17. Je možné určit, od kterého bloku se má indexování spustit?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Existují nějaké tipy, jak zvýšit výkon indexování? Synchronizace mého podgrafu trvá velmi dlouho
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Ano, měli byste se podívat na volitelnou funkci start bloku, která umožňuje zahájit indexování od bloku, ve kterém byla smlouva nasazena: [Start bloky](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Existuje způsob, jak se přímo zeptat podgrafu a zjistit poslední číslo bloku, který indexoval?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Ano! Vyzkoušejte následující příkaz, přičemž "organization/subgraphName" nahraďte názvem organizace, pod kterou je publikován, a názvem vašeho podgrafu:
 
@@ -102,44 +121,27 @@ Ano! Vyzkoušejte následující příkaz, přičemž "organization/subgraphName
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. Jaké sítě podporuje Graf?
-
-Seznam podporovaných sítí najdete [zde](/developing/supported-networks).
-
-## 21. Je možné duplikovat podgraf do jiného účtu nebo koncového bodu, aniž by bylo nutné provést nové nasazení?
-
-Podgraf musíte znovu nasadit, ale pokud se ID podgrafu (hash IPFS) nezmění, nebude se muset synchronizovat od začátku.
-
-## 22. Je možné použít Apollo Federation nad graph-node?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-Federace zatím není podporována, i když ji chceme v budoucnu podporovat. V současné době můžete použít sešívání schémat, a to buď na klientovi, nebo prostřednictvím služby proxy.
-
-## 23. Je nějak omezeno, kolik objektů může Graf vrátit na jeden dotaz?
-
-Ve výchozím nastavení jsou odpovědi na dotazy omezeny na 100 položek na kolekci. Pokud chcete získat více, můžete jít až na 1000 položek na kolekci a nad tuto hranici můžete stránkovat pomocí:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. Pokud můj frontend dapp používá pro dotazování The Graph, musím svůj dotazovací klíč zapsat přímo do frontend? Co když budeme za uživatele platit poplatky za dotazování - způsobí zlomyslní uživatelé, že naše poplatky za dotazování budou velmi vysoké?
-
-V současné době je doporučeným přístupem pro dapp přidání klíče do frontendu a jeho zpřístupnění koncovým uživatelům. Přitom můžete tento klíč omezit na název hostitele, například _yourdapp.io_ a podgraf. Bránu v současné době provozuje Edge & Node. Součástí odpovědnosti brány je monitorování zneužití a blokování provozu od škodlivých klientů.
-
-## 25. Kde najdu svůj aktuální podgraf v hostované službě?
-
-Přejděte do hostované služby, abyste našli podgrafy, které jste vy nebo jiní uživatelé nasadili do hostované služby. Najdete ji [zde](https://thegraph.com/hosted-service).
-
-## 26. Začne hostovaná služba účtovat poplatky za dotazy?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-Graf nikdy nebude účtovat poplatky za hostovanou službu. Graf je decentralizovaný protokol a zpoplatnění centralizované služby není v souladu s hodnotami Graf. Hostovaná služba byla vždy dočasným krokem, který měl pomoci dostat se k decentralizované síti. Vývojáři budou mít dostatek času přejít na decentralizovanou síť, jak jim to bude vyhovovat.
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. Jak mohu aktualizovat podgraf v síti mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. V jakém pořadí se spouštějí obsluhy událostí, bloků a volání pro zdroj dat?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Obsluhy událostí a volání jsou nejprve seřazeny podle indexu transakce v rámci bloku. Obsluhy událostí a volání v rámci téže transakce jsou seřazeny podle konvence: nejprve obsluhy událostí, pak obsluhy volání, přičemž každý typ dodržuje pořadí, v jakém jsou definovány v manifestu. Obsluhy bloků se spouštějí po obsluhách událostí a volání v pořadí, v jakém jsou definovány v manifestu. I tato pravidla řazení se mohou měnit.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-Při vytváření nových dynamických zdrojů dat se obslužné rutiny definované pro dynamické zdroje dat začnou zpracovávat až po zpracování všech existujících obslužných rutin zdrojů dat a budou se opakovat ve stejném pořadí, kdykoli budou spuštěny.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From dd1ac7f871a5af328f616596e2f56e0916d8a893 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:00 -0500
Subject: [PATCH 0060/1325] New translations developer-faqs.mdx (German)

---
 .../pages/de/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/de/developing/developer-faqs.mdx b/website/pages/de/developing/developer-faqs.mdx
index b4af2c711bc8..244aae52d0f4 100644
--- a/website/pages/de/developing/developer-faqs.mdx
+++ b/website/pages/de/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Developer FAQs
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 6a79d6412e6e8f457a17502eaf0e15dc25d22b51 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:01 -0500
Subject: [PATCH 0061/1325] New translations developer-faqs.mdx (Italian)

---
 .../pages/it/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/it/developing/developer-faqs.mdx b/website/pages/it/developing/developer-faqs.mdx
index b4af2c711bc8..244aae52d0f4 100644
--- a/website/pages/it/developing/developer-faqs.mdx
+++ b/website/pages/it/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Developer FAQs
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 14f826890b79f9501de86739aa965d92b885366d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:02 -0500
Subject: [PATCH 0062/1325] New translations developer-faqs.mdx (Japanese)

---
 .../pages/ja/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/ja/developing/developer-faqs.mdx b/website/pages/ja/developing/developer-faqs.mdx
index 81b14f3a8117..c62608db9d9e 100644
--- a/website/pages/ja/developing/developer-faqs.mdx
+++ b/website/pages/ja/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: 開発者 FAQ
 ---
 
-## 1. サブグラフとは
+This page summarizes some of the most common questions for developers building on The Graph.
 
-サブグラフは、ブロックチェーンデータを基に構築されたカスタムAPIです。サブグラフはGraphQLクエリ言語を使ってクエリされ、Graph CLIを使ってGraph Nodeにデプロイされます。デプロイされ、The Graphの分散型ネットワークに公開されると、インデクサーはサブグラフを処理し、サブグラフの消費者がクエリできるようにします。
+## Subgraph Related
 
-## 2. サブグラフを削除できますか?
+### 1. サブグラフとは
 
-一度作成したサブグラフの削除はできません。
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. サブグラフ名を変更できますか?
+### 2. What is the first step to create a subgraph?
 
-一度作成したサブグラフの名前を変更することはできません。サブグラフを作成する際には、他の dapps から検索しやすく、識別しやすい名前になるよう、よく考えてから作成してください。
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. サブグラフに関連付けられている GitHub アカウントを変更できますか?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-一度作成したサブグラフに関連する GitHub のアカウントは変更できません。サブグラフを作成する前に、この点をよく考えてください。
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. スマート コントラクトにイベントがない場合でもサブグラフを作成できますか?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-スマートコントラクトを構成して、クエリしたいデータに関連するイベントを持つことを強くお勧めします。サブグラフ内のイベントハンドラは、コントラクトのイベントによってトリガされ、有用なデータを取得するための圧倒的に速い方法です。
+### 4. サブグラフに関連付けられている GitHub アカウントを変更できますか?
 
-使用しているコントラクトにイベントが含まれていない場合、サブグラフはコールハンドラとブロックハンドラを使用してインデックス作成をトリガすることができます。しかし、パフォーマンスが大幅に低下するため、これは推奨されません。
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. 複数のネットワークに同じ名前の 1 つのサブグラフを展開することは可能ですか?
+### 5. How do I update a subgraph on mainnet?
 
-複数のネットワークには別々の名前が必要です。同じ名前で異なるサブグラフを持つことはできませんが、単一のコードベースで複数のネットワークに対応する便利な方法があります。詳しくはドキュメントをご覧ください: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. テンプレートとデータ ソースの違いは何ですか?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-テンプレートは、サブグラフがインデックスを作成している間に、その場でデータソースを作成することができます。また、コントラクトの形状（ABI、イベントなど）を前もって知っているので、テンプレートでどのようにインデックスを作成するかを定義することができ、コントラクトが作成されると、サブグラフはコントラクトのアドレスを供給することで動的なデータソースを作成します。
+サブグラフを再デプロイする必要がありますが、サブグラフの ID（IPFS ハッシュ）が変わらなければ、最初から同期する必要はありません。
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+サブグラフ内では、複数のコントラクトにまたがっているかどうかにかかわらず、イベントは常にブロックに表示される順序で処理されます。
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 データソース・テンプレートのインスタンス化」のセクションをご覧ください: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates)
 
-## 8. ローカル展開に最新バージョンのグラフノードを使用していることを確認するにはどうすればよいですか?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-以下のコマンドを実行してください:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**注:** docker / docker-compose は、最初に実行したときにプルされた graph-node のバージョンを常に使用しますので、最新版の graph-node を使用していることを確認するために、このコマンドを実行することが重要です。
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. コントラクト関数を呼び出したり、サブグラフ マッピングから公開状態変数にアクセスするにはどうすればよいですか?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. 2 つのコントラクトを持つ `graph-cli` から `graph init` を使用してサブグラフをセットアップすることは可能ですか?または、`graph init` を実行した後、`subgraph.yaml` に別のデータソースを手動で追加する必要がありますか?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+以下のコマンドを実行してください:
 
-## 11. GitHub の問題に貢献または追加したい。オープンソースのリポジトリはどこにありますか?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. イベントを処理するときに、エンティティの「自動生成」Id を作成するための推奨される方法は何ですか?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 もし、イベント中に 1 つのエンティティしか作成されず、他に利用できるものがなければ、トランザクションハッシュ＋ログインデックスがユニークになります。Bytes に変換して`crypto.keccak256`に通すことで難読化することができますが、これでは一意性は高まりません。
 
-## 13. 複数の契約を聞く場合、契約順を選択してイベントを聞くことはできますか?
+### 15. Can I delete my subgraph?
 
-サブグラフ内では、複数のコントラクトにまたがっているかどうかにかかわらず、イベントは常にブロックに表示される順序で処理されます。
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+対応ネットワークの一覧は[こちら](/developing/supported-networks)で確認できます。
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 はい、以下の例のように`graph-ts`をインポートすることで可能です。
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. サブグラフ マッピングに ethers.js または他の JS ライブラリをインポートできますか?
-
-マッピングは AssemblyScript で書かれているため、現在はできません。代替案としては、生データをエンティティに格納し、JS ライブラリを必要とするロジックをクライアントで実行することが考えられます。
+## Indexing & Querying Related
 
-## 17. インデックス作成を開始するブロックを指定することはできますか?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. インデックス作成のパフォーマンスを向上させるためのヒントはありますか? サブグラフの同期に非常に時間がかかる
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-はい、コントラクトがデプロイされたブロックからインデックス作成を開始するオプションのスタートブロック機能をご利用ください: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. サブグラフに直接クエリを実行して、インデックスが作成された最新のブロック番号を特定する方法はありますか?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 はい、あります。organization/subgraphName」を公開先の組織とサブグラフの名前に置き換えて、以下のコマンドを実行してみてください:
 
@@ -102,44 +121,27 @@ Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the n
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. The Graph はどのネットワークをサポートしていますか?
-
-対応ネットワークの一覧は[こちら](/developing/supported-networks)で確認できます。
-
-## 21. 再デプロイせずにサブグラフを別のアカウントまたはエンドポイントに複製することは可能ですか?
-
-サブグラフを再デプロイする必要がありますが、サブグラフの ID（IPFS ハッシュ）が変わらなければ、最初から同期する必要はありません。
-
-## 22. グラフノード上で Apollo Federation を使用することは可能ですか?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-将来的にはサポートしたいと考えていますが、フェデレーションはまだサポートされていません。現時点でできることは、クライアント上またはプロキシサービス経由でスキーマステッチを使用することです。
-
-## 23. グラフがクエリごとに返すことができるオブジェクトの数に制限はありますか?
-
-デフォルトでは、クエリの応答は 1 つのコレクションにつき 100 アイテムに制限されています。それ以上の数を受け取りたい場合は、1 コレクションあたり 1000 アイテムまで、それ以上は以下のようにページネーションすることができます:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. dapp フロントエンドがクエリに The Graph を使用する場合、クエリ キーをフロントエンドに直接書き込む必要がありますか? ユーザーにクエリ料金を支払う場合はどうなりますか? 悪意のあるユーザーによってクエリ料金が非常に高くなることはありますか?
-
-現在、dapp の推奨されるアプローチは、キーをフロントエンドに追加し、それをエンド ユーザーに公開することです。とはいえ、そのキーを _yourdapp.io_ や subgraph.ゲートウェイは現在 Edge & によって実行されています。ノード。ゲートウェイの責任の一部は、不正行為を監視し、悪意のあるクライアントからのトラフィックをブロックすることです。
-
-## 25. ホスティングサービス上の現在のサブグラフはどこで見ることができますか？
-
-自分または他の人がホストされたサービスにデプロイしたサブグラフを見つけるには、ホストされたサービスに移動します。 [こちら](https://thegraph.com/hosted-service)でご覧いただけます。
-
-## 26. ホスティングサービスはクエリ料金を請求するようになりますか？
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-Graph は、ホストされるサービスに対して料金を請求することはありません。 Graph は分散型プロトコルであり、集中型サービスに対する課金は The Graph の価値観と一致していません。ホスト型サービスは常に、分散型ネットワークにアクセスするための一時的なステップでした。開発者には、快適に分散ネットワークにアップグレードするのに十分な時間があります。
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. メインネットのサブグラフを更新するには？
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From dc7ad95e70a36344f8616d1fefec8577b6c63336 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:04 -0500
Subject: [PATCH 0063/1325] New translations developer-faqs.mdx (Korean)

---
 .../pages/ko/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/ko/developing/developer-faqs.mdx b/website/pages/ko/developing/developer-faqs.mdx
index b4af2c711bc8..244aae52d0f4 100644
--- a/website/pages/ko/developing/developer-faqs.mdx
+++ b/website/pages/ko/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Developer FAQs
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 763e9923180664b2e9db3699fd17330de6b68e8e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:05 -0500
Subject: [PATCH 0064/1325] New translations developer-faqs.mdx (Dutch)

---
 .../pages/nl/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/nl/developing/developer-faqs.mdx b/website/pages/nl/developing/developer-faqs.mdx
index b9cd3035c35e..6e49c4271720 100644
--- a/website/pages/nl/developing/developer-faqs.mdx
+++ b/website/pages/nl/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Ontwikkelaar FAQs
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 0b8b97768b86225df7ee0928bc5dc735f36e5b97 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:06 -0500
Subject: [PATCH 0065/1325] New translations developer-faqs.mdx (Polish)

---
 .../pages/pl/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/pl/developing/developer-faqs.mdx b/website/pages/pl/developing/developer-faqs.mdx
index ce139b51a9d0..97f851a2d0c8 100644
--- a/website/pages/pl/developing/developer-faqs.mdx
+++ b/website/pages/pl/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: FAQs dla developerów
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From ede37447cfc6a17e4927deb61f05bf9d25c8626c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:07 -0500
Subject: [PATCH 0066/1325] New translations developer-faqs.mdx (Portuguese)

---
 .../pages/pt/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/pt/developing/developer-faqs.mdx b/website/pages/pt/developing/developer-faqs.mdx
index 62729dbd0af0..1c04ef6523c0 100644
--- a/website/pages/pt/developing/developer-faqs.mdx
+++ b/website/pages/pt/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Perguntas Frequentes dos Programadores
 ---
 
-## 1. O que é um subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-Um subgraph é uma API personalizada construída em dados de blockchains. Subgraphs são consultados com a linguagem GraphQL e lançados a um Graph Node usando o Graph CLI. Quando lançados e editados à rede descentralizada do The Graph, os Indexadores processam subgraphs e os disponibilizam para serem consultados em query por consumidores de subgraphs.
+## Subgraph Related
 
-## 2. Posso apagar o meu subgraph?
+### 1. O que é um subgraph?
 
-Não é possível apagar subgraphs após a sua criação.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Posso mudar o nome do meu subgraph?
+### 2. What is the first step to create a subgraph?
 
-Não. Quando um subgraph é criado, não é possível mudar o seu nome. Pense com cuidado antes de criar o seu subgraph para poder ser facilmente buscável e identificável por outros dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Posso mudar a conta do GitHub associada ao meu subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-Não. Quando um subgraph é criado, não há mais como mudar a conta do GitHub associada a ele. Pense nisto com cuidado antes de criar o seu subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Eu ainda posso criar um subgraph se os meus contratos inteligentes não tiverem eventos?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-É altamente recomendado que estruture os seus contratos inteligentes para terem eventos associados com dados que tens interesse de consultar em query. Handlers de eventos no subgraph são ativados por eventos de contratos e são, de longe, a forma mais rápida de conseguir dados úteis.
+### 4. Posso mudar a conta do GitHub associada ao meu subgraph?
 
-Se os contratos com os quais trabalha não contêm eventos, o seu subgraph pode usar handlers de chamadas e blocos para ativar o indexing. Porém, isto não é recomendado, porque retarda muito o desempenho do subgraph.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. É possível lançar um subgraph com o mesmo nome para várias redes?
+### 5. How do I update a subgraph on mainnet?
 
-Precisará fazer nomes separados para várias redes. Enquanto não podes ter subgraphs diferentes sob o mesmo nome, há várias maneiras convenientes de ter uma única base de código para várias redes. Leia mais na nossa documentação: [Como Relançar um Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. Quais são as diferenças entre modelos e fontes de dados?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Modelos (templates) permitem criar fontes de dados na hora, enquanto o seu subgraph está no processo de indexação. Pode ser que o seu contrato gerará novos contratos enquanto as pessoas interagem com ele, e como queres saber o formato destes contratos (ABI, eventos, etc.) à vista, pode definir como quer indexá-los em um modelo; e quando gerados, o seu subgraph criará uma fonte de dados dinâmica ao fornecer o endereço do contrato.
+Deve relançar o subgraph, mas se a ID do subgraph (hash IPFS) não mudar, ele não precisará sincronizar do começo.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Confira o estado `Access to smart contract` dentro da seção [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Dentro de um subgraph, os eventos são sempre processados na ordem em que aparecem nos blocos, mesmo sendo ou não através de vários contratos.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Confira a seção "como instanciar um modelo de fontes de dados" em: [Modelos de fontes de dados](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. Como posso garantir que estou a usar a versão mais recente do graph-node para os meus lançamentos locais?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-Podes executar o seguinte comando:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTA:** O docker / docker-compose sempre usará a versão do graph-node que foi puxada na primeira vez que a executou, então é importante fazer isto para garantir que está em dia com a versão mais recente do graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. Como chamo uma função de contrato ou acesso uma variável de estado público dos meus mapeamentos de subgraph?
+Primeiro, handlers de eventos e chamadas são organizados pelo índice de transações dentro do bloco. Handlers de evento e chamada dentro da mesma transação são organizados com uma convenção: handlers de eventos primeiro e depois handlers de chamadas, com cada tipo a respeitar a ordem em que são definidos no manifest. Handlers de blocos são executados após handlers de eventos e chamadas, na ordem em que são definidos no manifest. Estas regras de organizações estão sujeitas a mudanças.
 
-Confira o estado `Access to smart contract` dentro da seção [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+Com a criação de novas fontes de dados dinâmicas, os handlers definidos para fontes de dados dinâmicas só começarão a processar após o processamento dos handlers das fontes, e se repetirão na mesma sequência sempre que acionados.
 
-## 10. É possível preparar um subgraph através de `graph init` a partir do `graph-cli` com dois contratos? Ou devo adicionar, manualmente, outra fonte de dados no `subgraph.yaml` após executar o `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Sim. No próprio comando `graph init`, é possível adicionar várias fontes de dados ao inserir contratos um após o outro. O comando `graph add` também pode adicionar uma nova fonte de dados.
+Podes executar o seguinte comando:
 
-## 11. Quero contribuir ou adicionar um problema no GitHub. Onde posso encontrar os repositórios de código aberto?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. Qual é a forma recomendada de construir ids "autogeradas" para uma entidade ao lidar com eventos?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 Se só uma entidade for criada durante o evento e não houver nada melhor disponível, então o hash da transação + o index do log será original. Podes ofuscá-los ao converter aquilo em Bytes e então o colocar pelo `crypto.keccak256`, mas isto não o fará mais original.
 
-## 13. Ao escutar vários contratos, é possível selecionar a ordem do contrato para escutar eventos?
+### 15. Can I delete my subgraph?
 
-Dentro de um subgraph, os eventos são sempre processados na ordem em que aparecem nos blocos, mesmo sendo ou não através de vários contratos.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. É possível diferenciar entre redes (mainnet, Sepolia, local) de dentro de handlers de eventos?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+Veja a lista das redes apoiadas [aqui](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Sim. Isto é possível ao importar o `graph-ts` como no exemplo abaixo:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Vocês apoiam handlers de bloco e chamada no Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Sim. O Sepolia apoia handlers de blocos, chamadas e eventos. Vale notar que handlers de eventos têm desempenho muito melhor do que os outros dois e têm apoio em todas as redes compatíveis com EVMs.
 
-## 16. Posso importar ethers.js ou outras bibliotecas JS nos meus mapeamentos de subgraph?
-
-Não no momento, já que mapeamentos são escritos em AssemblyScript. Outra solução seria armazenar dados puros em entidades e desempenhar lógicas que requerem bibliotecas JS no cliente.
+## Indexing & Querying Related
 
-## 17. É possível especificar em qual bloco começar a indexação?
+### 19. Is it possible to specify what block to start indexing on?
 
-Sim. `dataSources.source.startBlock` no arquivo `subgraph.yaml` especifica o número do bloco que a fonte de dados começa a indexar. Na maioria dos casos, sugerimos usar o bloco no qual o contrato foi criado: [Blocos de início](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Alguma dica para aumentar o desempenho da indexação? O meu subgraph demora muito para sincronizar
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Sim. Confira o recurso opcional de bloco inicial (start blcok) para começar a indexar do bloco em que o contrato foi lançado: [Blocos iniciais](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Há como consultar diretamente o subgraph para determinar o número do último bloco que ele indexou?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Sim! Execute o seguinte comando, com "organization/subgraphName" substituído com a organização sob a qual ele foi publicado e o nome do seu subgraph:
 
@@ -102,44 +121,27 @@ Sim! Execute o seguinte comando, com "organization/subgraphName" substituído co
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. Quais redes são apoiadas pelo The Graph?
-
-Veja a lista das redes apoiadas [aqui](/developing/supported-networks).
-
-## 21. É possível duplicar um subgraph para outra conta ou ponto final sem relançá-lo?
-
-Deve relançar o subgraph, mas se a ID do subgraph (hash IPFS) não mudar, ele não precisará sincronizar do começo.
-
-## 22. É possível usar a Apollo Federation em cima do graph-node?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-A Federation ainda tem apoio, mas queremos apoiá-la no futuro. No momento, vale usar costura de schemas no cliente ou através de um serviço proxy.
-
-## 23. Há um limite de quantos objetos o Graph pode retornar por consulta?
-
-Normalmente, respostas a consultas são limitadas a 100 itens por coleção. Se quiser receber mais, pode subir para até 1000 itens por coleção; além disto, pode paginar com:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. Se a frontend do meu dApp usa o The Graph para consultas, eu preciso escrever a minha chave de query diretamente no frontend? E se pagarmos taxas de query para utilizadores — utilizadores maliciosos podem aumentar muito estas taxas?
-
-Atualmente, a abordagem recomendada para um dApp é adicionar a chave ao frontend e expô-la para utilizadores finais. Dito isto, pode limitar aquela chave a um hostname, como _seudapp.io_ e um subgraph. A gateway está atualmente a ser executada pelo Edge & Node. Parte da responsabilidade de uma gateway é monitorar comportamentos abusivos e bloquear tráfego de clientes maliciosos.
-
-## 25. Onde encontro o meu subgraph atual no serviço hospedado?
-
-Vá para o Serviço Hospedado para achar subgraphs lançados por você ou outros ao Serviço Hospedado. Veja [aqui](https://thegraph.com/hosted-service).
-
-## 26. O serviço hospedado começará a cobrar taxas de query?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-The Graph nunca cobrará pelo Serviço Hospedado. Este é um protocolo descentralizado, e cobrar por um serviço centralizado não condiz com os valores do Graph. O Serviço Hospedado sempre foi um degrau temporário para chegar à rede descentralizada; os programadores terão tempo suficiente para migrar à rede descentralizada quando estiverem preparados.
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. Como atualizar um subgraph na mainnet?
+## Miscellaneous
 
-Se for um programador de subgraph, você pode lançar uma nova versão do seu subgraph ao Subgraph Studio com a CLI. O subgraph será privado até lá, mas se estiver contente com ele, você pode publicá-lo no Graph Explorer descentralizado. Isto criará uma nova versão do seu subgraph em que Curadores podem começar a sinalizar.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. Em qual ordem os handlers de evento, bloco e chamada são ativados para uma fonte de dados?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Primeiro, handlers de eventos e chamadas são organizados pelo índice de transações dentro do bloco. Handlers de evento e chamada dentro da mesma transação são organizados com uma convenção: handlers de eventos primeiro e depois handlers de chamadas, com cada tipo a respeitar a ordem em que são definidos no manifest. Handlers de blocos são executados após handlers de eventos e chamadas, na ordem em que são definidos no manifest. Estas regras de organizações estão sujeitas a mudanças.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-Com a criação de novas fontes de dados dinâmicas, os handlers definidos para fontes de dados dinâmicas só começarão a processar após o processamento dos handlers das fontes, e se repetirão na mesma sequência sempre que acionados.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 4bd3ec8c3a555b61a0c879550b61cb889689324e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:08 -0500
Subject: [PATCH 0067/1325] New translations developer-faqs.mdx (Swedish)

---
 .../pages/sv/developing/developer-faqs.mdx    | 148 +++++++++---------
 1 file changed, 75 insertions(+), 73 deletions(-)

diff --git a/website/pages/sv/developing/developer-faqs.mdx b/website/pages/sv/developing/developer-faqs.mdx
index 4c799cd8c0c5..907509ee9f9d 100644
--- a/website/pages/sv/developing/developer-faqs.mdx
+++ b/website/pages/sv/developing/developer-faqs.mdx
@@ -2,99 +2,118 @@
 title: Vanliga frågor för utvecklare
 ---
 
-## 1. Vad är en subgraf?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-En subgraf är en anpassad API byggd på blockkedjedata. Subgrafer frågas med hjälp av GraphQL-frågespråket och distribueras till en Graph Node med hjälp av Graph CLI. När de har distribuerats och publicerats till The Graphs decentraliserade nätverk, bearbetar Indexers subgrafer och gör dem tillgängliga för frågekonsumenter av subgrafer.
+## Subgraph Related
 
-## 2. Kan jag ta bort min subgraf?
+### 1. Vad är en subgraf?
 
-Det är inte möjligt att ta bort subgrafer efter att de har skapats.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Kan jag ändra namnet på min subgraf?
+### 2. What is the first step to create a subgraph?
 
-Nej. När en subgraf har skapats kan namnet inte ändras. Se till att tänka noga på detta innan du skapar din subgraf så att den är lätt sökbar och identifierbar av andra dappar.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Kan jag ändra det GitHub-konto som är kopplat till min subgraf?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-Nej. När en subgraf har skapats kan det associerade GitHub-kontot inte ändras. Tänk noggrant på detta innan du skapar din subgraf.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Kan jag fortfarande skapa en subgraf om mina smarta kontrakt inte har händelser?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-Det rekommenderas starkt att strukturera dina smarta kontrakt så att de har händelser som är kopplade till data du är intresserad av att fråga. Händelsehanterare i subgrafen utlöses av kontrakthändelser och är överlägset det snabbaste sättet att hämta användbar data.
+### 4. Kan jag ändra det GitHub-konto som är kopplat till min subgraf?
 
-Om de kontrakt du arbetar med inte innehåller händelser kan din subgraf använda sig av uppropshanterare och blockhanterare för att utlösa indexering. Detta rekommenderas dock inte, eftersom prestandan kommer att vara betydligt långsammare.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Är det möjligt att distribuera en subgraf med samma namn för flera nätverk?
+### 5. How do I update a subgraph on mainnet?
 
-Du behöver separata namn för flera nätverk. Även om du inte kan ha olika subgrafer under samma namn finns det bekväma sätt att ha en enda kodbas för flera nätverk. Läs mer om detta i vår dokumentation: [Omdistribuera en subgraf](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. Hur skiljer sig mallar från datakällor?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Mallar låter dig skapa datakällor på flykt medan din subgraf indexerar. Det kan vara så att ditt kontrakt kommer att skapa nya kontrakt när människor interagerar med det, och eftersom du känner till formen av dessa kontrakt (ABI, händelser osv.) i förväg kan du definiera hur du vill indexera dem i en mall och när de skapas kommer din subgraf att skapa en dynamisk datakälla genom att tillhandahålla kontraktsadressen.
+Du måste distribuera om subgrafen, men om subgrafens ID (IPFS-hash) inte ändras behöver den inte synkroniseras från början.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Inom en subgraf behandlas händelser alltid i den ordning de visas i blocken, oavsett om det är över flera kontrakt eller inte.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Kolla in avsnittet "Instansiera en mall för datakälla" på: [Mallar för datakällor](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. Hur ser jag till att jag använder den senaste versionen av graph-node för mina lokala distributioner?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-Du kan köra följande kommando:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**OBS:** Docker / docker-compose kommer alltid att använda den graph-node-version som hämtades första gången du körde det, så det är viktigt att göra detta för att se till att du är uppdaterad med den senaste versionen av graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. Hur anropar jag en kontraktsfunktion eller får åtkomst till en offentlig statisk variabel från mina subgraf-mappningar?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Är det möjligt att ställa in en subgraf med hjälp av `graph init` från `graph-cli` med två kontrakt? Eller bör jag manuellt lägga till en annan datakälla i `subgraph.yaml` efter att jag har kört `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+Du kan köra följande kommando:
 
-## 11. Jag vill bidra eller lägga till ett GitHub-ärende. Var hittar jag öppna källkodsrepository?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. Vad är det rekommenderade sättet att bygga "automatiskt genererade" ID för en entitet när man hanterar händelser?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 Om endast en entitet skapas under händelsen och om inget bättre är tillgängligt, skulle transaktionshashen + loggindexet vara unikt. Du kan förvränga dessa genom att konvertera dem till bytes och sedan skicka dem genom `crypto.keccak256`, men detta kommer inte att göra dem mer unika.
 
-## 13. När du lyssnar på flera kontrakt, är det möjligt att välja kontraktsordningen för att lyssna på händelser?
+### 15. Can I delete my subgraph?
 
-Inom en subgraf behandlas händelser alltid i den ordning de visas i blocken, oavsett om det är över flera kontrakt eller inte.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+Du kan hitta listan över de stödda nätverken [här](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Ja, du kan göra detta genom att importera `graph-ts` enligt exemplet nedan:
 
 ```javascript
-import { dataSource } from '@graphprotocol/graph-ts'
+import { dataSource } from "@graphprotocol/graph-ts"
 
 dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Kan jag importera ethers.js eller andra JS-bibliotek i mina subgraf-mappningar?
-
-För närvarande inte, eftersom mappningar är skrivna i AssemblyScript. En möjlig alternativ lösning på detta är att lagra rådata i enheter och utföra logik som kräver JS-bibliotek på klienten.
+## Indexing & Querying Related
 
-## 17. Är det möjligt att specificera vilket block som ska börja indexera?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Finns det några tips för att öka prestandan vid indexering? Min subgraf tar väldigt lång tid att synkronisera
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Ja, du bör titta på den valfria funktionen för startblock för att börja indexera från det block där kontraktet distribuerades: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Finns det ett sätt att direkt fråga subgrafen för att ta reda på det senaste blocknumret den har indexerat?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Ja! Prova följande kommando och ersätt "organization/subgraphName" med organisationen under vilken den är publicerad och namnet på din subgraf:
 
@@ -102,44 +121,27 @@ Ja! Prova följande kommando och ersätt "organization/subgraphName" med organis
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. Vilka nätverk stöds av The Graph?
-
-Du kan hitta listan över de stödda nätverken [här](/developing/supported-networks).
-
-## 21. Är det möjligt att duplicera en subgraf till ett annat konto eller en annan slutpunkt utan att distribuera om?
-
-Du måste distribuera om subgrafen, men om subgrafens ID (IPFS-hash) inte ändras behöver den inte synkroniseras från början.
-
-## 22. Är det möjligt att använda Apollo Federation ovanpå graph-node?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-Federation stöds ännu inte, även om vi planerar att stödja det i framtiden. För närvarande kan du använda schema stitching, antingen på klienten eller via en proxytjänst.
-
-## 23. Finns det en begränsning för hur många objekt The Graph kan returnera per fråga?
-
-Som standard är frågesvar begränsade till 100 objekt per samling. Om du vill ha fler kan du gå upp till 1000 objekt per samling och bortom det kan du paginera med:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. Om min dapp-frontänd använder The Graph för frågor, måste jag skriva in min frågenyckel direkt i frontänden? Vad händer om vi betalar frågeavgifter för användare – kommer skadliga användare att orsaka mycket höga frågeavgifter?
-
-För närvarande är det rekommenderade tillvägagångssättet för en dapp att lägga till nyckeln i frontänden och exponera den för slutanvändare. Med det sagt kan du begränsa den nyckeln till en värdnamn, som _yourdapp.io_ och subgraphen. Gatewayen drivs för närvarande av Edge & Node. En del av gatewayens ansvar är att övervaka missbruk och blockera trafik från skadliga klienter.
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Gå till hosted service för att hitta subgrafer som du eller andra har distribuerat till hosted service. Du hittar den [här](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-The Graph kommer aldrig ta ut avgifter för hosted service. The Graph är en decentraliserad protokoll, och att ta ut avgifter för en centraliserad tjänst är inte i linje med The Graphs värderingar. Hosted service var alltid ett tillfälligt steg för att hjälpa till att nå det decentraliserade nätverket. Utvecklare kommer att ha tillräckligt med tid att uppgradera till det decentraliserade nätverket när de är bekväma med det.
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From aec48064c2ebaa730fccb295f6dd1ffce75bb774 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:09 -0500
Subject: [PATCH 0068/1325] New translations benefits.mdx (French)

---
 website/pages/fr/network/benefits.mdx | 102 +++++++++++++-------------
 1 file changed, 51 insertions(+), 51 deletions(-)

diff --git a/website/pages/fr/network/benefits.mdx b/website/pages/fr/network/benefits.mdx
index 30eb7202be81..702f6c0a5a86 100644
--- a/website/pages/fr/network/benefits.mdx
+++ b/website/pages/fr/network/benefits.mdx
@@ -11,7 +11,7 @@ Voici une analyse :
 
 ## Pourquoi devriez-vous utiliser le réseau Graph
 
-- Significantly lower monthly costs
+- Des coûts mensuels nettement réduits
 - 0 $ de frais de configuration de l'infrastructure
 - Disponibilité supérieure
 - Accès à des centaines d’indexeurs indépendants à travers le monde
@@ -21,61 +21,61 @@ Voici une analyse :
 
 ### Une structure & de coûts faible et plus flexible
 
-No contracts. No monthly fees. Only pay for the queries you use—with an average cost-per-query of $40 per million queries (~$0.00004 per query). Queries are priced in USD and paid in GRT or credit card.
-
-Query costs may vary; the quoted cost is the average at time of publication (March 2024).
-
-## Low Volume User (less than 100,000 queries per month)
-
-| Cost Comparison | Auto-hébergé | The Graph Network |
-| :-: | :-: | :-: |
-| Coût mensuel du serveur\* | 350 $ au mois | 0 $ |
-| Frais de requête | + 0 $ | $0 per month |
-| Temps d'ingénierie<sup>†</sup> | 400 $ au mois | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
-| Requêtes au mois | Limité aux capacités infra | 100,000 (Free Plan) |
-| Tarif par requête | 0 $ | $0<sup>‡</sup> |
-| Les infrastructures | Centralisée | Décentralisée |
-| La redondance géographique | 750$+ par nœud complémentaire | Compris |
-| Temps de disponibilité | Variable | + 99.9% |
-| Total des coûts mensuels | <span className="highlight-row" />+ 750 $ | 0 $ |
-
-## Medium Volume User (~3M queries per month)
-
-| Comparaison de coût | Auto-hébergé | The Graph Network |
-| :-: | :-: | :-: |
-| Coût mensuel du serveur\* | 350 $ au mois | 0 $ |
-| Frais de requête | 500 $ au mois | $120 per month |
-| Temps d'ingénierie<sup>†</sup> | 800 $ au mois | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
-| Requêtes au mois | Limité aux capacités infra | ~3,000,000 |
-| Tarif par requête | 0 $ | $0.00004 |
-| L'infrastructure | Centralisée | Décentralisée |
-| Frais d'ingénierie | 200 $ au mois | Compris |
-| La redondance géographique | 1 200 $ coût total par nœud supplémentaire | Compris |
-| Temps de disponibilité | Variable | + 99.9% |
-| Total des coûts mensuels | <span className="highlight-row" /> + 1650 $ | $120 |
-
-## High Volume User (~30M queries per month)
-
-| Comparaison des coûts | Auto-hébergé | The Graph Network |
-| :-: | :-: | :-: |
-| Coût mensuel du serveur\* | 1100 $ au mois, par nœud | 0 $ |
-| Frais de requête | 4000 $ | $1,200 per month |
-| Nombre de nœuds obligatoires | 10 | Sans objet |
-| Temps d'ingénierie<sup>†</sup> | 6000 $ ou plus au mois | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
-| Requêtes au mois | Limité aux capacités infra | ~30,000,000 |
-| Tarif par requête | 0 $ | $0.00004 |
-| L'infrastructure | Centralisée | Décentralisée |
-| La redondance géographique | 1 200 $ de coûts totaux par nœud supplémentaire | Compris |
-| Temps de disponibilité | Variable | + 99.9% |
-| Total des coûts mensuels | <span className="highlight-row" /> + 11 000 $ | $1,200 |
+Pas de contrat. Pas de frais mensuels. Vous ne payez que pour les requêtes que vous utilisez, avec un coût moyen par requête de 40 $ par million de requêtes (~0,00004 $ par requête). Les requêtes sont facturées en USD et payées en GRT ou par carte de crédit.
+
+Les coûts d'interrogation peuvent varier ; le coût indiqué est la moyenne au moment de la publication (mars 2024).
+
+## Utilisateur à faible volume (moins de 100 000 requêtes par mois)
+
+|        Cost Comparison         |               Auto-hébergé                |                              The Graph Network                              |
+|:------------------------------:|:-----------------------------------------:|:---------------------------------------------------------------------------:|
+|  Coût mensuel du serveur\*   |               350 $ au mois               |                                     0 $                                     |
+|        Frais de requête        |                   + 0 $                   |                                 0$ par mois                                 |
+| Temps d'ingénierie<sup>†</sup> |               400 $ au mois               | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
+|        Requêtes au mois        |        Limité aux capacités infra         |                           100 000 (Plan Gratuit)                            |
+|       Tarif par requête        |                    0 $                    |                               0$<sup>‡</sup>                                |
+|      Les infrastructures       |                Centralisée                |                                Décentralisée                                |
+|   La redondance géographique   |       750$+ par nœud complémentaire       |                                   Compris                                   |
+|     Temps de disponibilité     |                 Variable                  |                                   + 99.9%                                   |
+|    Total des coûts mensuels    | <span className="highlight-row" />+ 750 $ |                                     0 $                                     |
+
+## Utilisateur à volume moyen (~3M requêtes par mois)
+
+|      Comparaison de coût       |                Auto-hébergé                 |                              The Graph Network                              |
+|:------------------------------:|:-------------------------------------------:|:---------------------------------------------------------------------------:|
+|  Coût mensuel du serveur\*   |                350 $ au mois                |                                     0 $                                     |
+|        Frais de requête        |                500 $ au mois                |                                120$ par mois                                |
+| Temps d'ingénierie<sup>†</sup> |                800 $ au mois                | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
+|        Requêtes au mois        |         Limité aux capacités infra          |                                 ~3,000,000                                  |
+|       Tarif par requête        |                     0 $                     |                                  $0.00004                                   |
+|        L'infrastructure        |                 Centralisée                 |                                Décentralisée                                |
+|       Frais d'ingénierie       |                200 $ au mois                |                                   Compris                                   |
+|   La redondance géographique   | 1 200 $ coût total par nœud supplémentaire  |                                   Compris                                   |
+|     Temps de disponibilité     |                  Variable                   |                                   + 99.9%                                   |
+|    Total des coûts mensuels    | <span className="highlight-row" /> + 1650 $ |                                    120$                                     |
+
+## Utilisateur à volume élevé (~30M requêtes par mois)
+
+|     Comparaison des coûts      |                  Auto-hébergé                   |                              The Graph Network                              |
+|:------------------------------:|:-----------------------------------------------:|:---------------------------------------------------------------------------:|
+|  Coût mensuel du serveur\*   |            1100 $ au mois, par nœud             |                                     0 $                                     |
+|        Frais de requête        |                     4000 $                      |                              1 200 $ par mois                               |
+|  Nombre de nœuds obligatoires  |                       10                        |                                 Sans objet                                  |
+| Temps d'ingénierie<sup>†</sup> |             6000 $ ou plus au mois              | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
+|        Requêtes au mois        |           Limité aux capacités infra            |                                 ~30,000,000                                 |
+|       Tarif par requête        |                       0 $                       |                                  0.00004$                                   |
+|        L'infrastructure        |                   Centralisée                   |                                Décentralisée                                |
+|   La redondance géographique   | 1 200 $ de coûts totaux par nœud supplémentaire |                                   Compris                                   |
+|     Temps de disponibilité     |                    Variable                     |                                   + 99.9%                                   |
+|    Total des coûts mensuels    |  <span className="highlight-row" /> + 11 000 $  |                                   1,200$                                    |
 
 \*y compris les coûts de sauvegarde : $50-$ à 100 dollars au mois
 
 <sup>†</sup>Temps d'ingénierie basé sur une hypothèse de 200 $ de l'heure
 
-<sup>‡</sup>Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries.
+<sup>‡</sup>Reflète le coût pour le consommateur de données. Les frais de requête sont toujours payés aux Indexeurs pour les requêtes du Plan Gratuit.
 
-Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet.
+Les coûts estimés sont uniquement pour les subgraphs Ethereum Mainnet - les coûts sont encore plus élevés lorsqu'on héberge soi-même un `graph-node` sur d'autres réseaux. Certains utilisateurs peuvent avoir besoin de mettre à jour leur subgraph vers une nouvelle version. En raison des frais de gaz Ethereum, une mise à jour coûte ~50 $ au moment de la rédaction. Notez que les frais de gaz sur [Arbitrum](/arbitrum/arbitrum-faq) sont considérablement plus bas que ceux d'Ethereum mainnet.
 
 Émettre un signal sur un subgraph est un cout net, nul optionnel et unique (par exemple, 1 000 $ de signal peuvent être conservés sur un subgraph, puis retirés - avec la possibilité de gagner des revenus au cours du processus).
 
@@ -89,4 +89,4 @@ Le réseau décentralisé du Graph permet aux utilisateurs d'accéder à une red
 
 En résumé : Le réseau de graphs est moins coûteux, plus facile à utiliser et produit des résultats supérieurs à ceux obtenus par l'exécution locale d'un `nœud de graphs`.
 
-Commencez à utiliser le réseau The Graph dès aujourd'hui, et apprenez comment [mettre à niveau votre subgraph vers le réseau décentralisé de The Graph](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From f0957ef584163c7385c353b7eac3e34dd0bed25c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:10 -0500
Subject: [PATCH 0069/1325] New translations graphql-api.mdx (French)

---
 website/pages/fr/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/fr/querying/graphql-api.mdx b/website/pages/fr/querying/graphql-api.mdx
index 9bbc39b6b69b..d6965cc4cc87 100644
--- a/website/pages/fr/querying/graphql-api.mdx
+++ b/website/pages/fr/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: API GraphQL
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Requêtes
+## Qu'est-ce que GraphQL ?
 
-Dans votre schéma de subgraph, vous définissez des types appelés `Entités`. Pour chaque type `Entity`, un champ `entity` et `entities` sera généré sur le type `Query` de niveau supérieur. Notez que `query` n'a pas besoin d'être inclus en haut de la requête `graphql` lors de l'utilisation de The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Exemples
 
@@ -21,7 +29,7 @@ Requête pour une seule entité `Token` définie dans votre schéma :
 }
 ```
 
-> **Remarque :** Lors d'une requête pour une seule entité, le champ `id` est obligatoire et il doit s'agir d'une chaîne.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Interrogez toutes les entités `Token` :
 
@@ -36,7 +44,10 @@ Interrogez toutes les entités `Token` :
 
 ### Tri
 
-Lors de l'interrogation d'une collection, le paramètre `orderBy` peut être utilisé pour trier selon un attribut spécifique. De plus, `orderDirection` peut être utilisé pour spécifier le sens du tri, `asc` pour ascendant ou `desc` pour décroissant.
+When querying a collection, you may:
+
+- 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.
 
 #### Exemple
 
@@ -53,7 +64,7 @@ Lors de l'interrogation d'une collection, le paramètre `orderBy` peut être uti
 
 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 d'entités imbriquées.
 
-Dans l'exemple suivant, nous trions les jetons en fonction de leur nom propre:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -72,11 +83,12 @@ Dans l'exemple suivant, nous trions les jetons en fonction de leur nom propre:
 
 ### Pagination
 
-Lors de l'interrogation d'une collection, le paramètre `first` peut être utilisé pour paginer depuis le début de la collection. Il convient de noter que l'ordre de tri par défaut est par ID dans l'ordre alphanumérique croissant, et non par heure de création.
-
-De plus, le paramètre `skip` peut être utilisé pour ignorer 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.
+When querying a collection, it's best to:
 
-Les requêtes doivent éviter d'utiliser de très grandes valeurs de `skip` car elles fonctionnent généralement mal. Pour récupérer un grand nombre d'éléments, il est préférable de parcourir les entités sur la base d'un attribut, comme le montre le dernier exemple.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Exemple utilisant `first`
 
@@ -108,7 +120,7 @@ Interrogez 10 entités `Token`, décalées de 10 places depuis le début de la
 
 #### Exemple utilisant `first` et `id_ge`
 
-Si un client a besoin de récupérer un grand nombre d'entités, il est beaucoup plus performant de baser les requêtes sur un attribut et de filtrer par cet attribut. Par exemple, un client récupérerait un grand nombre de jetons en utilisant cette requête :
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -119,11 +131,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-La première fois, il enverrait la requête avec `lastID = ""`, et pour les requêtes suivantes, il définirait `lastID` sur l'attribut `id` du dernier entité dans la demande précédente. Cette approche fonctionnera nettement mieux que l'utilisation de valeurs `skip` croissantes.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtration
 
-Vous pouvez utiliser le paramètre `where` dans vos requêtes pour filtrer différentes propriétés. Vous pouvez filtrer sur plusieurs valeurs dans le paramètre `where`.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Exemple utilisant `where`
 
@@ -157,7 +170,7 @@ Vous pouvez utiliser des suffixes comme `_gt`, `_lte` pour comparer les valeurs
 
 #### Exemple de filtrage par bloc
 
-Vous pouvez également filtrer les entités par `_change_block(number_gte: Int)` - cela filtre les entités qui ont été mises à jour dans ou après le bloc spécifié.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Cela peut être utile si vous cherchez à récupérer uniquement les entités qui ont changé, par exemple depuis la dernière fois que vous avez interrogé. Ou bien, il peut être utile d'étudier ou de déboguer la façon dont les entités changent dans votre subgraph (si combiné avec un filtre de bloc, vous pouvez isoler uniquement les entités qui ont changé dans un bloc spécifique).
 
@@ -195,7 +208,7 @@ Depuis Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releas
 
 ##### Opérateur `AND`
 
-Dans l'exemple suivant, nous filtrons les défis (Challenges) dont le résultat et le numéro `number` supérieur ou égal à `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -210,7 +223,7 @@ Dans l'exemple suivant, nous filtrons les défis (Challenges) dont le résultat
 ```
 
 > **Sucre syntaxique :** Vous pouvez simplifier la requête ci-dessus en supprimant l'opérateur `et` en passant une sous-expression séparée par des virgules.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -225,7 +238,7 @@ Dans l'exemple suivant, nous filtrons les défis (Challenges) dont le résultat
 
 ##### Opérateur `OR`
 
-Dans l'exemple suivant, nous filtrons les défis dont le résultat réussi (`outcome` `succeeded`) ou le numéro (`number`) est supérieur ou égal à `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -280,9 +293,9 @@ _change_block(numéro_gte : Int)
 
 Vous pouvez interroger l'état de vos entités non seulement pour le dernier bloc, qui est la valeur par défaut, mais également pour un bloc arbitraire du passé. Le bloc dans lequel une requête doit se produire peut être spécifié soit par son numéro de bloc, soit par son hachage de bloc en incluant un argument `block` dans les champs de niveau supérieur des requêtes.
 
-Le résultat d'une telle requête ne changera pas au fil du temps, c'est-à-dire qu'une requête portant sur un certain bloc passé renverra le même résultat quel que soit le moment où elle est exécutée, à l'exception d'une requête portant sur un bloc très proche de la tête de la chaîne, dont le résultat pourrait changer s'il s'avérait que ce bloc ne se trouvait pas sur la chaîne principale et que la chaîne était réorganisée. Une fois qu'un bloc peut être considéré comme définitif, le résultat de la requête ne changera pas.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Il convient de noter que l'implémentation actuelle est encore sujette à certaines limitations qui pourraient violer ces garanties. L'implémentation ne peut pas toujours dire qu'un bloc donné n'est pas du tout sur la chaîne principale, ou que le résultat d'une requête par bloc de hachage pour un bloc qui ne peut pas encore être considéré comme final peut être influencé par une réorganisation du bloc qui se déroule en même temps que la requête. Ils n'affectent pas les résultats des requêtes par hachage 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.
+> 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.
 
 #### Exemple
 
@@ -324,12 +337,12 @@ Les champs de requête de recherche en texte `intégral`, fournissent une Api de
 
 Opérateurs de recherche en texte intégral :
 
-| Symbole | Opérateur | Description |
-| --- | --- | --- |
-| `&` | `And` | Pour combiner plusieurs termes de recherche dans un filtre pour les entités incluant tous les termes fournis |
-| &#x7c; | `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                                           |
+| &#x7c;     | `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
 
@@ -378,11 +391,11 @@ Graph Node met en œuvre une validation [basée sur les spécifications](https:/
 
 ## Schema
 
-Le schéma de votre source de données, c'est-à-dire les types d'entités, les valeurs et les relations disponibles pour l'interrogation, est défini par le [Langage de définition d'interface GraphQL (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-Les schémas GraphQL définissent généralement des types racine pour les `requêtes`, les `abonnements` et les `mutations`. Le graphe 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 inclus dans le manifeste de votre subgraph.
+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:** 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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 11c24e062a939f6d513c53ac13b8b98db1f56f22 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:11 -0500
Subject: [PATCH 0070/1325] New translations developing.mdx (Turkish)

---
 website/pages/tr/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/tr/network/developing.mdx b/website/pages/tr/network/developing.mdx
index 46b76f6632b6..ce6923c88215 100644
--- a/website/pages/tr/network/developing.mdx
+++ b/website/pages/tr/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Geliştirme
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Genel Bakış
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Yerel olarak geliştirme
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Ağda Yayınlama
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### İndekslemeyi Teşvik Eden Sinyal
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Sorgulama & Uygulama Geliştirme
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Subgraphları Güncelleme
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Subgraph Geliştiricisi yükseltmeye hazır olduğunda, subgraphlarını yeni sürüme yönlendirmek için bir işlem başlatabilir. Subgraph'ın güncellenmesi, her sinyali yeni sürüme geçirir (sinyali uygulayan kullanıcının "otomatik geçiş" seçeneğini seçtiğini varsayarsak) ve bu da bir geçiş kesintisine neden olur. Bu sinyal geçişi, İndeksleyicilerin subgraph'ı yeni sürümünü indekslemeye başlamasını sağlamalıdır, böylece yakında sorgulama için kullanılabilir hale gelecektir.
-
-### Subgraphları Kullanımdan Kaldırma
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Çeşitli Geliştirici Rolleri
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Geliştiriciler ve Ağ Ekonomisi
-
-Geliştiriciler ağda önemli bir ekonomik aktördür, indekslemeyi teşvik amacıyla GRT kilitlerler ve en önemlisi ağın birincil değer değişimi olan subgraphları sorgularlar. Subgraph geliştiricileri ayrıca bir subgraph güncellendiğinde GRT yakarlar.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 570c93b79332c0e7ce030bd1b742586393bd9528 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:12 -0500
Subject: [PATCH 0071/1325] New translations graphql-api.mdx (Russian)

---
 website/pages/ru/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/ru/querying/graphql-api.mdx b/website/pages/ru/querying/graphql-api.mdx
index e98676fb9a27..2553a41b50ec 100644
--- a/website/pages/ru/querying/graphql-api.mdx
+++ b/website/pages/ru/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: API GraphQL
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Запросы
+## What is GraphQL?
 
-В Вашей схеме субграфа Вы определяете типы, называемые `Entities`. Для каждого типа `Entity` поле `entity` и `entities` будет создано для типа `Query` верхнего уровня. Обратите внимание, что `query` не нужно включать в начало запроса `graphql` при использовании The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Примеры
 
@@ -21,7 +29,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 }
 ```
 
-> **Примечание.** При запросе одного объекта поле `id` является обязательным и должно быть строкой.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Запрос всех объектов `Токен`:
 
@@ -36,7 +44,10 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### Сортировка
 
-При запросе коллекции параметр `orderBy` может использоваться для сортировки по определенному атрибуту. Кроме того, `orderDirection` можно использовать для указания направления сортировки, `asc` по возрастанию или `desc` по убыванию.
+When querying a collection, you may:
+
+- 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.
 
 #### Пример
 
@@ -53,7 +64,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 Начиная с Graph Node, объекты [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) можно сортировать на основе вложенных содержаний.
 
-В следующем примере мы сортируем токены по имени их владельца:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### Пагинация
 
-При запросе коллекции параметр `first` можно использовать для разбиения на страницы с начала коллекции. Стоит отметить, что порядок сортировки по умолчанию осуществляется по идентификатору в восходящем алфавитно-цифровом порядке, а не по времени создания.
-
-Кроме того, параметр `skip` можно использовать для пропуска объектов и разбивки на страницы. Например, `first:100` показывает первые 100 объектов, а `first:100, skip:100` показывает следующие 100 объектов.
+When querying a collection, it's best to:
 
-В запросах следует избегать использования очень больших значений `skip`, так как они обычно плохо работают. Для извлечения большого количества элементов гораздо лучше просматривать объекты на основе атрибута, как показано в последнем примере.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Пример использования `first`
 
@@ -106,7 +118,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 #### Пример использования `first` и `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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-В первый раз он будет отправлять запрос с `lastID = ""`, а для последующих запросов будет устанавливать `lastID` в атрибут `id` последнего объекта в предыдущем запросе. Этот подход будет работать значительно лучше, чем увеличение значений `skip`.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Фильтрация
 
-Вы можете использовать параметр `where` в своих запросах для фильтрации различных свойств. В параметре `where` можно фильтровать несколько значений.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Пример использования `where`
 
@@ -155,7 +168,7 @@ query manyTokens($lastID: String) {
 
 #### Пример фильтрации блока
 
-Вы также можете фильтровать объекты по `_change_block(number_gte: Int)` — этот код фильтрует объекты, которые были обновлены в указанном блоке или после него.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Это может быть полезно, если Вы хотите получить только объекты, которые изменились, например, с момента последнего опроса. Или, в качестве альтернативы, может быть полезно исследовать или отладить изменнения объектов в Вашем субграфе (в сочетании с фильтрацией блоков Вы можете изолировать только объекты, которые изменились в определенном блоке).
 
@@ -193,7 +206,7 @@ query manyTokens($lastID: String) {
 
 ##### Оператор `AND`
 
-В следующем примере мы отфильтровываем задачи с `outcome` `succeeded` и `number` больше или равным `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ query manyTokens($lastID: String) {
 ```
 
 > **Syntactic sugar:**. Вы можете упростить приведенный выше запрос, удалив оператор `and`, передав подвыражение, разделенное запятыми.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ query manyTokens($lastID: String) {
 
 ##### Оператор `OR`
 
-В следующем примере мы отфильтровываем задачи с `outcome` `succeeded` или `number` больше или равным `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 Вы можете запрашивать состояние своих объектов не только для последнего блока, который используется по умолчанию, но и для произвольного блока в прошлом. Блок, в котором должен выполняться запрос, можно указать либо по номеру блока, либо по его хэшу, включив аргумент `block` в поля верхнего уровня запросов.
 
-Результат такого запроса не изменится со временем, т.е. запрос к конкретному прошлому блоку будет возвращать один и тот же результат каждый раз при его выполнении, за исключением того, когда Вы запрашиваете блок, очень близкий к началу цепочки, результат в этом случае может измениться, если этот блок окажется не в основной сети и сеть будет реорганизована. После того как блок можно будет считать окончательным, результат запроса не изменится.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Обратите внимание, что текущая реализация имеет определенные ограничения, которые могут нарушить эти гарантии. На данный момент не всегда можно определить, что заданный хэш блока вообще не находится в основной цепочке или что на результат запроса по хэшу блока для блока, который нельзя считать окончательным, может повлиять реорганизация блока, которая происходит одновременно с запросом. Это не влияет на результаты запросов по хэшу блока, когда известно, что блок в конечном итоге находится в основной цепочке. Здесь подробно описана [эта проблема](https://github.com/graphprotocol/graph-node/issues/1405).
+> 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.
 
 #### Пример
 
@@ -322,12 +335,12 @@ _change_block(number_gte: Int)
 
 Полнотекстовые поисковые операторы:
 
-| Символ | Оператор | Описание |
-| --- | --- | --- |
-| `&` | `And` | Для объединения нескольких условий поиска в фильтр для объектов, которые включают все указанные условия |
-| &#x7c; | `Or` | Запросы с несколькими условиями поиска, разделенные оператором or, вернут все объекты, которые соответствуют любому из предоставленных условий |
-| `<->` | `Follow by` | Укажите расстояние между двумя словами. |
-| `:*` | `Prefix` | Используйте поисковый запрос по префиксу, чтобы найти слова с соответствующим префиксом (необходимо 2 символа) |
+| Символ      | Оператор    | Описание                                                                                                                                       |
+| ----------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
+| `&`     | `And`       | Для объединения нескольких условий поиска в фильтр для объектов, которые включают все указанные условия                                        |
+| &#x7c;      | `Or`        | Запросы с несколькими условиями поиска, разделенные оператором or, вернут все объекты, которые соответствуют любому из предоставленных условий |
+| `<->` | `Follow by` | Укажите расстояние между двумя словами.                                                                                                        |
+| `:*`        | `Prefix`    | Используйте поисковый запрос по префиксу, чтобы найти слова с соответствующим префиксом (необходимо 2 символа)                                 |
 
 #### Примеры
 
@@ -376,11 +389,11 @@ Graph Node реализует [на основе спецификаций](https
 
 ## Схема
 
-Схема Вашего источника данных, то есть типы объектов, значения и отношения, доступные для запроса, определяется с помощью [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-Схемы GraphQL обычно определяют корневые типы для `queries`, `subscriptions` и `mutations`. The Graph поддерживает только `queries`. Корневой тип `Query` для вашего субграфа автоматически создается из схемы GraphQL, включенной в манифест вашего субграфа.
+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 не подвергается мутации, поскольку ожидается, что разработчики будут выполнять транзакции непосредственно в базовом блокчейне из своих приложений.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Объекты
 

From 036c6893136f72175d969e81306a91c1c4143c74 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:13 -0500
Subject: [PATCH 0072/1325] New translations developing.mdx (Russian)

---
 website/pages/ru/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/ru/network/developing.mdx b/website/pages/ru/network/developing.mdx
index 9e4ae18cd0f5..c412422e4035 100644
--- a/website/pages/ru/network/developing.mdx
+++ b/website/pages/ru/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Жизненный цикл подграфа
+## Обзор
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From ce8d9fe7dfe6a04730681362af42d5e5d78bc97e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:14 -0500
Subject: [PATCH 0073/1325] New translations developing.mdx (Romanian)

---
 website/pages/ro/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/ro/network/developing.mdx b/website/pages/ro/network/developing.mdx
index 1b76eb94ccca..6ba33f6d916c 100644
--- a/website/pages/ro/network/developing.mdx
+++ b/website/pages/ro/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Overview
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From afd15a91dca6efd12fd7852e7cda14580f694df9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:15 -0500
Subject: [PATCH 0074/1325] New translations developing.mdx (Spanish)

---
 website/pages/es/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/es/network/developing.mdx b/website/pages/es/network/developing.mdx
index 223472818228..9f172dd06432 100644
--- a/website/pages/es/network/developing.mdx
+++ b/website/pages/es/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Desarrollando
 ---
 
-Los desarrolladores representan el lado de la demanda del ecosistema The Graph. Los developers construyen subgrafos y los publican en The Graph Network. A continuación, consultan los subgrafos activos con GraphQL para potenciar sus aplicaciones.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Ciclo de vida de un Subgrafo
+## Descripción
 
-Los subgrafos deployados en la red tienen un ciclo de vida definido.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Construir a nivel local
+On The Graph, you can:
 
-Al igual que con todo el desarrollo de subgrafos, se comienza con el desarrollo y prueba local. Los desarrolladores pueden utilizar la misma configuración local tanto si construyen para The Graph Network, el Servicio Alojado o un Graph Node local, aprovechando `graph-cli` y `graph-ts` para construir su subgrafo. Se anima a los desarrolladores a utilizar herramientas como [Matchstick](https://github.com/LimeChain/matchstick) para realizar pruebas unitarias y mejorar la solidez de sus subgrafos.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Existen ciertas limitaciones en The Graph Network, en términos de características y soporte de red. Solo los subgrafos en [redes suportadas](/developing/supported-networks) obtienen recompensas de indexación, y los subgrafos que obtienen datos de IPFS tampoco son elegibles.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publicar a la red
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-Cuando el desarrollador está satisfecho con su subgrafo, puede publicarlo en The Graph Network. Esta es una acción on-chain, que registra el subgrafo para que pueda ser descubierto por los Indexadores. Los subgrafos publicados tienen su correspondiente NFT, que es fácilmente transferible. El subgrafo publicado tiene metadatos asociados, que proporcionan a otros participantes de la red un contexto e información útiles.
+### What are subgraphs?
 
-### Señalar para fomentar la indexación
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Es poco probable que los subgrafos publicados sean recogidos por los Indexadores sin la adición de la señal. La señal es GRT bloqueado asociado a un subgrafo determinado, que indica a los Indexadores que un subgrafo determinado recibirá un volumen de consultas, y también contribuye a las recompensas de indexación disponibles por procesarlo. Los desarrolladores de subgrafos generalmente añadirán una señal a su subgrafo para fomentar la indexación. Los Curadores de terceros también pueden señalar un subgrafo determinado, si consideran que el subgrafo puede generar un volumen de consultas.
-
-### Consultas & desarrollo de aplicaciones
-
-Una vez que un subgrafo ha sido procesado por los Indexadores y está disponible para su consulta, los desarrolladores pueden empezar a utilizar el subgrafo en sus aplicaciones. Los desarrolladores consultan los subgrafos a través de una Gateway, que reenvía sus consultas a un Indexador que haya procesado el subgrafo, pagando las tarifas de consulta en GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecar un Subgrafo
-
-En algún momento un developer puede decidir que ya no necesita un subgrafo publicado. En ese momento pueden deprecar el subgrafo, lo que devuelve cualquier GRT señalada a los Curadores.
-
-### Diversos roles de desarrollador
-
-Algunos desarrolladores participarán en el ciclo de vida completo de los subgrafos en la red, publicando, consultando e iterando sobre sus propios subgrafos. Algunos se centrarán en el desarrollo de subgrafos, creando APIs abiertas en las que otros puedan basarse. Otros pueden centrarse en la aplicación, consultando subgrafos deployados por otros.
-
-### Desarrolladores y economía de la red
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From ee396c145815ab3cd550f8b0f2d6a4f65c79f904 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:17 -0500
Subject: [PATCH 0075/1325] New translations developing.mdx (Arabic)

---
 website/pages/ar/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/ar/network/developing.mdx b/website/pages/ar/network/developing.mdx
index 638f2b5af282..6f456be01c17 100644
--- a/website/pages/ar/network/developing.mdx
+++ b/website/pages/ar/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## دورة حياة الـ Subgraph
+## نظره عامة
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 2bc16b7037e38b7450bb6c7b71315aed1f3175b2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:18 -0500
Subject: [PATCH 0076/1325] New translations developing.mdx (Czech)

---
 website/pages/cs/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/cs/network/developing.mdx b/website/pages/cs/network/developing.mdx
index 6d508e4a3b7a..106792c6b4ed 100644
--- a/website/pages/cs/network/developing.mdx
+++ b/website/pages/cs/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Vývoj
 ---
 
-Vývojáři jsou poptávkovou stranou ekosystému Grafu. Vývojáři vytvářejí podgrafy a publikují je v síti Graf. Poté se dotazují na živé podgrafy pomocí GraphQL, aby mohli využívat své aplikace.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Životní cyklus podgrafů
+## Přehled
 
-Podgrafy nasazené do sítě mají definovaný životní cyklus.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Stavět lokálně
+On The Graph, you can:
 
-Stejně jako při vývoji všech podgrafů se začíná lokálním vývojem a testováním. Vývojáři mohou používat stejné místní nastavení, ať už vytvářejí pro síti Graf, hostovanou službu nebo místní uzel Grafu, a využívat při vytváření podgrafu `graph-cli` a `graph-ts`. Vývojářům se doporučuje používat nástroje, jako je [Matchstick](https://github.com/LimeChain/matchstick), pro testování jednotek, aby zvýšili robustnost svých podgrafů.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Síť Graf má určitá omezení, pokud jde o funkce a podporu sítě. Odměny za indexaci získají pouze podgrafy na [podporovaných sítích](/developing/supported-networks) a odměny za indexaci nemohou získat ani podgrafy, které načítají data z IPFS.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publikovat v síti
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-Jakmile je vývojář se svým podgrafem spokojen, může jej zveřejnit v síti Grafu. Jedná se o akci v řetězci, která zaregistruje podgraf tak, aby jej indexery mohly objevit. Zveřejněné podgrafy mají odpovídající NFT, který je pak snadno přenositelný. Zveřejněný podgraf má přiřazená metadata, která poskytují ostatním účastníkům sítě užitečný kontext a informace.
+### What are subgraphs?
 
-### Signál na podporu indexování
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Publikované podgrafy pravděpodobně nebudou zachyceny indexátory bez přidání signálu. Signál je uzamčený GRT spojený s daným podgrafem, který indikuje indexátorům, že daný podgraf obdrží objem dotazů, a také přispívá k indexačním odměnám, které jsou k dispozici pro jeho zpracování. Vývojáři podgrafů obvykle přidávají ke svým podgrafům signál, aby podpořili indexování. Kurátoři třetích stran mohou také signalizovat daný podgraf, pokud se domnívají, že podgraf bude pravděpodobně vytvářet objem dotazů.
-
-### Dotazování & Vývoj aplikací
-
-Jakmile je podgraf zpracován indexery a je k dispozici pro dotazování, mohou jej vývojáři začít používat ve svých aplikacích. Vývojáři se dotazují na podgrafy prostřednictvím brány, která jejich dotazy předává indexeru, jenž podgraf zpracoval, a platí poplatky za dotazy v GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Jakmile je vývojář podgrafu připraven k aktualizaci, může iniciovat transakci, která jeho podgraf nasměruje na novou verzi. Aktualizace podgrafu migruje jakýkoli signál na novou verzi (za předpokladu, že uživatel, který signál aplikoval, zvolil "automatickou migraci"), čímž také vzniká migrační daň. Tato migrace signálu by měla přimět indexátory, aby začaly indexovat novou verzi podgrafu, takže by měl být brzy k dispozici pro dotazování.
-
-### Vyřazování podgrafů
-
-V určitém okamžiku se vývojář může rozhodnout, že publikovaný podgraf již nepotřebuje. V tu chvíli může podgraf vyřadit, čímž se kurátorům vrátí všechny signalizované GRT.
-
-### Různorodé role vývojáře
-
-Někteří vývojáři se zapojí do celého životního cyklu podgrafů v síti, publikují, dotazují se a iterují své vlastní podgrafy. Někteří se mohou zaměřit na vývoj podgrafů a vytvářet otevřené API, na kterém mohou stavět ostatní. Někteří se mohou zaměřit na aplikace a dotazovat se na podgrafy, které nasadili jiní.
-
-### Vývojáři a síťová ekonomika
-
-Vývojáři jsou v síti klíčovým ekonomickým subjektem, který blokuje GRT, aby podpořil indexování, a hlavně se dotazuje na podgrafy, což je hlavní výměna hodnot v síti. Vývojáři podgrafů také spalují GRT, kdykoli je podgraf aktualizován.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 431578fb4e9b8cd2e8deac2ee38edfd2dd2b3544 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:19 -0500
Subject: [PATCH 0077/1325] New translations developing.mdx (German)

---
 website/pages/de/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/de/network/developing.mdx b/website/pages/de/network/developing.mdx
index 1b76eb94ccca..6ba33f6d916c 100644
--- a/website/pages/de/network/developing.mdx
+++ b/website/pages/de/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Overview
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From e8a30ecbc9577bed5f7114c29e0333b10eb4442d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:20 -0500
Subject: [PATCH 0078/1325] New translations developing.mdx (Italian)

---
 website/pages/it/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/it/network/developing.mdx b/website/pages/it/network/developing.mdx
index 55dba24dc9a1..919c18774f11 100644
--- a/website/pages/it/network/developing.mdx
+++ b/website/pages/it/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Sviluppo
 ---
 
-Gli sviluppatori sono il lato della domanda di The Graph Ecosystem. Gli sviluppatori costruiscono subgraph e li pubblicano su The Graph Network. Quindi, fanno query sui subgraph in tempo reale con GraphQL per alimentare le loro applicazioni.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Ciclo di vita dei subgraph
+## Panoramica
 
-I subgraph distribuiti nella rete hanno un ciclo di vita definito.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Costruire a livello locale
+On The Graph, you can:
 
-Come per lo sviluppo di tutti i subgraph, si inizia con lo sviluppo e il test in locale. Gli sviluppatori possono usare la stessa configurazione locale sia che stiano costruendo per The Graph Network, per il hosted service o per un Graph Node locale, sfruttando `graph-cli` and `graph-ts` per costruire il loro subgraph. Gli sviluppatori sono incoraggiati a usare strumenti come [Matchstick](https://github.com/LimeChain/matchstick) per i test unitari, per migliorare la solidità dei loro subgraph.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Ci sono alcuni vincoli su The Graph Network, in termini di funzionalità e supporto di rete. Solo i subgraph su [reti supportate](/developing/supported-networks) otterranno ricompense per l'indicizzazione e i subgraph che recuperano dati da IPFS non sono ammissibili.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Pubblicare nella rete
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-Quando lo sviluppatore è soddisfatto del suo subgraph, può pubblicarlo su The Graph Network. Si tratta di un'azione on-chain, che registra il subgraph in modo che possa essere scoperto dagli Indexer. I subgraph pubblicati hanno un NFT corrispondente, che è poi facilmente trasferibile. Il subgraph pubblicato ha metadati associati, che forniscono agli altri partecipanti alla rete un contesto e informazioni utili.
+### What are subgraphs?
 
-### Segnale per incoraggiare l'indicizzazione
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-È improbabile che i subgraph pubblicati vengano raccolti dagli Indexer senza l'aggiunta di un segnale. Il segnale è un GRT bloccato associato a un determinato subgraph, che indica agli Indexer che un dato subgraph riceverà un volume di query, inoltre contribuisce anche ai premi di indicizzazione disponibili per la sua elaborazione. Gli sviluppatori di subgraph aggiungono generalmente un segnale al loro subgraph, per incoraggiarne l'indicizzazione. Anche i Curator di terze parti possono aggiungere un segnale a un determinato subgraph, se ritengono che il subgraph possa generare un volume di query.
-
-### Query e sviluppo di applicazioni
-
-Una volta che un subgraph è stato elaborato dagli Indexer ed è disponibile per fare query, gli sviluppatori possono iniziare a utilizzare il subgraph nelle loro applicazioni. Gli sviluppatori fanno query di subgraph tramite un gateway, che inoltra le loro queries a un Indexer che ha elaborato il subgraph, pagando le tariffe di query in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Aggiornare i subgraph
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Una volta che lo sviluppatore del sottografo è pronto per l'aggiornamento, può avviare una transazione per puntare il suo subgraph alla nuova versione. L'aggiornamento del subgraph migra qualsiasi segnale alla nuova versione (supponendo che l'utente che ha applicato il segnale abbia selezionato "auto-migrate"), il che comporta anche una tassa di migrazione. La migrazione del segnale dovrebbe indurre gli Indexer a iniziare l'indicizzazione della nuova versione del subgraph, che dovrebbe quindi diventare presto disponibile per le query.
-
-### Deprecazione dei Subgraph
-
-A un certo punto uno sviluppatore può decidere di non aver più bisogno di un subgraph pubblicato. A quel punto può deprecare il subgraph, restituendo ai Curator ogni GRT segnalato.
-
-### Diversi Ruoli dello Sviluppatore
-
-Alcuni sviluppatori si occuperanno dell'intero ciclo di vita dei subgraph sulla rete, pubblicando, facendo query e iterando i propri subgraph. Alcuni si concentreranno sullo sviluppo di subgraph, costruendo API aperte su cui altri potranno basarsi. Alcuni possono concentrarsi sulle applicazioni, interrogando i subgraph distribuiti da altri.
-
-### Sviluppatori ed economia di rete
-
-Gli sviluppatori sono un attore economico fondamentale nella rete, in quanto bloccano i GRT per incoraggiare l'indicizzazione e, soprattutto, le query dei subgraph, che rappresenta il principale scambio di valore della rete. Anche gli sviluppatori di subgraph bruciano GRT ogni volta che un subgraph viene aggiornato.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 1c2d373f1e2955c13ae28ac0b09ef2fb6f7b8ebc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:21 -0500
Subject: [PATCH 0079/1325] New translations developing.mdx (Japanese)

---
 website/pages/ja/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/ja/network/developing.mdx b/website/pages/ja/network/developing.mdx
index beca8747424f..669f37f571f2 100644
--- a/website/pages/ja/network/developing.mdx
+++ b/website/pages/ja/network/developing.mdx
@@ -2,52 +2,29 @@
 title: 現像
 ---
 
-開発者は、The Graphのエコシステムの需要側である。開発者はサブグラフを構築し、それをThe Graph Networkに公開する。そして、アプリケーションを動かすために、GraphQLでサブグラフをクエリします。
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## サブグラフのライフサイクル
+## 概要
 
-ネットワークに配置されたサブグラフは、ライフサイクルが定義されています。
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### ローカルでビルド
+On The Graph, you can:
 
-すべてのサブグラフ開発と同様に、ローカルでの開発とテストから始まります。開発者は、`graph-cli` と `graph-ts` を利用して、The Graph Network、ホステッド サービス、またはローカル グラフ ノードのいずれを構築する場合でも、同じローカル セットアップを使用して構築できます。サブグラフ。開発者は、[Matchstick](https://github.com/LimeChain/matchstick) などのツールを単体テストに使用して、サブグラフの堅牢性を向上させることをお勧めします。
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> The Graph Network には、機能とネットワーク サポートに関して一定の制約があります。 [サポートされているネットワーク](/developing/supported-networks)のサブグラフのみがインデックス作成の報酬を獲得できます。また、IPFS からデータを取得するサブグラフも資格がありません。
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### ネットワークに公開
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-開発者がサブグラフに満足したら、それをグラフネットワークに公開することができます。これはオンチェーンアクションであり、インデックス作成者が発見できるようにサブグラフを登録します。公開されたサブグラフは対応するNFTを持ち、これは簡単に転送できます。公開されたサブグラフには関連するメタデータがあり、他のネットワーク参加者に有用なコンテキストと情報を提供します。
+### What are subgraphs?
 
-### 索引作成を促すシグナル
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-公開されたサブグラフは、シグナルを追加しないとインデックス作成者に拾われにくいです。シグナルは、与えられたサブグラフに関連するロックされたGRTで、与えられたサブグラフがクエリー量を受け取ることをインデックス作成者に示し、またその処理に利用できるインデックス作成報酬に寄与します。サブグラフの開発者は、インデックス作成を促進するために、一般的にそのサブグラフにシグナルを追加する。サードパーティのキュレーターも、そのサブグラフがクエリ量を増加させると判断した場合、そのサブグラフにシグナルを追加することができます。
-
-### クエリ& アプリケーション開発
-
-サブグラフがインデクサーによって処理され、クエリに使用できるようになると、開発者はアプリケーションでサブグラフの使用を開始できます。開発者は、サブグラフを処理したインデクサーにクエリを転送するゲートウェイを介してサブグラフにクエリを実行し、GRT でクエリ料金を支払います。
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### サブグラフの更新
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-サブグラフ開発者は、更新の準備が完了すると、トランザクションを開始してサブグラフを新しいバージョンに向けることができます。サブグラフを更新すると、すべてのシグナルが新しいバージョンに移行されます (シグナルを適用したユーザーが「自動移行」を選択したと仮定します)。これには移行税もかかります。このシグナルの移行により、インデクサーは新しいバージョンのサブグラフのインデックス作成を開始するよう促されるため、すぐにクエリに使用できるようになるはずです。
-
-### サブグラフの廃止
-
-ある時点で、開発者は公開されたサブグラフが不要になったと判断することがあります。そのとき、開発者はサブグラフを非推奨とし、キュレータにシグナライズされたGRTを返します
-
-### 多様な開発者の役割
-
-開発者の中には、ネットワーク上のサブグラフのライフサイクルに関与し、自分のサブグラフを公開し、クエリし、反復する者もいる。サブグラフの開発に重点を置き、他の人が構築できるオープンなAPIを構築する人もいます。また、アプリケーションに焦点を当て、他の人が配置したサブグラフをクエリすることもあります。
-
-### 開発者とネットワーク経済学
-
-開発者はネットワークにおける主要な経済的主体であり、インデックス作成を促進するために GRT をロックアップし、ネットワークの主要な価値交換であるサブグラフのクエリを非常に重要にしています。サブグラフ開発者は、サブグラフが更新されるたびに GRT も書き込みます。
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From e6251e2dde39184a61047d378dfdf5df2e77db30 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:22 -0500
Subject: [PATCH 0080/1325] New translations developing.mdx (Korean)

---
 website/pages/ko/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/ko/network/developing.mdx b/website/pages/ko/network/developing.mdx
index 1b76eb94ccca..6ba33f6d916c 100644
--- a/website/pages/ko/network/developing.mdx
+++ b/website/pages/ko/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Overview
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From fb183a6fdb0b5fb45181677385420a4cedfa9cb9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:23 -0500
Subject: [PATCH 0081/1325] New translations developing.mdx (Dutch)

---
 website/pages/nl/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/nl/network/developing.mdx b/website/pages/nl/network/developing.mdx
index 351296bb6d9d..e280e2be1058 100644
--- a/website/pages/nl/network/developing.mdx
+++ b/website/pages/nl/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Ontwikkelen
 ---
 
-Ontwikkelaars zijn de vraagzijde van The Graph ecosysteem. Ontwikkelaars bouwen subgraphs en publiceren deze naar het Graph Netwerk. Vervolgens sturen ze query's naar de subgraphs met GraphQL om hun applicaties aan te sturen.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Levenscyclus
+## Overview
 
-Subgraphs op het netwerk hebben een gedefinieerde levenscyclus.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Lokaal Bouwen
+On The Graph, you can:
 
-Net als bij alle subgraph-ontwikkeling, begint het met lokaal ontwikkelen en testen. Ontwikkelaars kunnen dezelfde lokale setup gebruiken, ongeacht of ze bouwen voor het Graph-netwerk, de hosted service of een lokale Graph Node, waarbij ze `graph-cli` en `graph-ts` gebruiken om hun subgraph te bouwen. Ontwikkelaars wordt aangemoedigd om tools zoals [Matchstick](https://github.com/LimeChain/matchstick) te gebruiken voor unit testing om de robuustheid van hun subgraphs te verbeteren.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Er zijn bepaalde beperkingen op The Graph-netwerk, qua functies en netwerkondersteuning. Alleen subgraphs op [ondersteunde netwerken](/developing/supported-networks) komen in aanmerking voor indexeringsbeloningen, en subgraphs die data ophalen uit IPFS komen niet in aanmerking.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publiceren op het netwerk
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-Wanneer de ontwikkelaars tevreden zijn met hun subgraph, kunnen ze deze publiceren op The Graph-netwerk. Dit is een on-chain actie, die de subgraph registreert zodat deze door Indexers kan worden ontdekt. Gepubliceerde subgraphs hebben een bijbehorende NFT, die gemakkelijk overdraagbaar is. De gepubliceerde subgraph heeft bijbehorende metadata, die andere netwerkdeelnemers context en informatie bieden.
+### What are subgraphs?
 
-### Signaal Geven om Indexering te Stimuleren
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Gepubliceerde subgraphs worden waarschijnlijk niet opgepikt door Indexers zonder toevoeging van signaal. Signaal is vergrendelde GRT die is gekoppeld aan een gegeven subgraph die aan Indexeerders aangeeft dat een bepaalde subgraph queryvolume zal ontvangen, dit draagt ook bij aan de indexeringsbeloningen die beschikbaar zijn voor het verwerken ervan. Subgraph-ontwikkelaars zullen over het algemeen signaal toevoegen aan hun eigen subgraph, om indexering aan te moedigen. Derde partij Curatoren kunnen ook signaal geven op een bepaalde subgraph, als zij van mening zijn dat de subgraph waarschijnlijk queryvolume zal genereren.
-
-### Query's versturen & Applicatieontwikkeling
-
-Zodra een subgraph is verwerkt door Indexers en beschikbaar is voor bevraging, kunnen ontwikkelaars de subgraph in hun applicaties gaan gebruiken. Ontwikkelaars bevragen subgraphs via een gateway, die hun queries doorstuurt naar een Indexer die de subgraph heeft verwerkt, en betalen querykosten in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Subgraphs Bijwerken
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Zodra de Subgraph-ontwikkelaar klaar is om bij te werken, kunnen ze een transactie starten om hun subgraph naar de nieuwe versie te wijzen. Het bijwerken van de subgraph migreert elk signaal naar de nieuwe versie (ervan uitgaande dat de gebruiker die het signaal heeft toegepast, "auto-migrate" heeft geselecteerd), wat ook een migratiebelasting met zich meebrengt. Deze signaalmigratie zou Indexers moeten aanzetten om de nieuwe versie van de subgraph te gaan indexeren, dus deze zou snel beschikbaar moeten zijn voor queries.
-
-### Subgraphs Uitfaseren
-
-Op een gegeven moment kan een ontwikkelaar besluiten dat ze een gepubliceerde subgraph niet langer nodig hebben. Op dat moment kunnen ze de subgraph uitfaseren, wat eventuele gesignaleerde GRT aan de Curatoren retourneert.
-
-### Diverse Ontwikkelaarsrollen
-
-Sommige ontwikkelaars zullen zich bezighouden met de volledige subgraph-levenscyclus op het netwerk, publiceren, bevragen en itereren op hun eigen subgraphs. Sommigen kunnen zich richten op subgraph-ontwikkeling, het bouwen van open API's waar anderen op kunnen bouwen. Sommigen kunnen zich richten op applicatieontwikkeling, en bevragen subgraphs die door anderen zijn geïmplementeerd.
-
-### Ontwikkelaars en Netwerkeconomie
-
-Ontwikkelaars zijn een belangrijke economische speler in het netwerk die GRT vastzetten om indexering te stimuleren en cruciaal zijn voor het bevragen van subgraphs, wat de primaire waarde-uitwisseling van het netwerk is. Subgraph-ontwikkelaars verbranden ook GRT wanneer een subgraph wordt bijgewerkt.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 88876dfc22dac0eca797357b0dc84a5271da99cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:24 -0500
Subject: [PATCH 0082/1325] New translations developing.mdx (Polish)

---
 website/pages/pl/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/pl/network/developing.mdx b/website/pages/pl/network/developing.mdx
index 1b76eb94ccca..6ba33f6d916c 100644
--- a/website/pages/pl/network/developing.mdx
+++ b/website/pages/pl/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Overview
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 9035c2b2ceb10329f03915c76ce57cbea257cc82 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:25 -0500
Subject: [PATCH 0083/1325] New translations developing.mdx (Portuguese)

---
 website/pages/pt/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/pt/network/developing.mdx b/website/pages/pt/network/developing.mdx
index 2cdc95f3b451..815de9d39c85 100644
--- a/website/pages/pt/network/developing.mdx
+++ b/website/pages/pt/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Programação
 ---
 
-Os programadores representam o lado de demanda do ecossistema do The Graph, constroem subgraphs e os editam à Graph Network. Então, eles consultam subgraphs ao vivo com queries no GraphQL, para abastecer os seus aplicativos.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Ciclo de Vida de um Subgraph
+## Visão geral
 
-Os subgraphs lançados à rede têm um ciclo de vida definido.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Construção local
+On The Graph, you can:
 
-Assim como toda programação de subgraph, ela começa com desenvolvimento e testes locais. Os programadores podem usar o mesmo setup local para construir o seu subgraph — seja ao construir para a Graph Network, o serviço hospedado, ou um Graph Node local, com `graph-cli` e o `graph-ts`. Vale usar ferramentas como o [Matchstick](https://github.com/LimeChain/matchstick) para testes de unidades, para deixar os subgraphs mais robustos.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Há alguns limites de apoio a recursos e redes na Graph Network. Só subgraphs em [redes apoiadas](/developing/supported-networks) ganharão recompensas de indexação, e subgraphs que retiram dados do IPFS também não têm direito a estas.
+### What is GraphQL?
 
-### Lançamento no Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Uma vez definido, o subgraph pode ser construído e lançado ao [Subgraph Studio](/deploying/subgraph-studio-faqs/). Este é um ambiente sandbox que indexará o subgraph lançado, e o disponibilizará para programação e testes (com rate limit). Com isto, os programadores têm a oportunidade de verificar que o seu subgraph funciona como esperado, sem qualquer erro na indexação.
+### Developer Actions
 
-### Edição na rede
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-Quando o programador estiver satisfeito com o seu subgraph, pode editá-lo na Graph Network. Esta é uma ação on-chain, que registra o subgraph para que ele seja descoberto por Indexadores. Os subgraphs publicados têm NFTs correspondente, que são então facilmente transferíveis. Um subgraph editado tem metadados associados, que fornecem contexto e informações úteis a outros participantes da rede.
+### What are subgraphs?
 
-### Sinalização para incentivar indexação
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Subgraphs editados têm poucas chances de ser detectados por Indexadores sem a adição do sinal — um montante de GRT trancado associado a um subgraph, que indica aos Indexadores que um certo subgraph receberá volume de queries e também contribui às recompensas de indexação disponíveis por processá-los. Os programadores de subgraph geralmente adicionam o sinal ao próprio subgraph, para incentivar indexações. Curadores terceiros também podem sinalizar em um certo subgraph, se acharem que tem altas chances de movimentar o volume de queries.
-
-### Programação de Aplicativos & Queries
-
-Quando um subgraph for processado pelos Indexadores e aberto a queries, os programadores podem começar a usar o subgraph nos seus aplicativos. Os programadores consultam subgraphs através de um gateway, que encaminha as suas consultas a um Indexador que processou o subgraph com uma taxa de query em GRT.
-
-Para poder fazer queries, os programadores devem gerar uma chave de API no Subgraph Studio. Esta chave deve ser bancada com GRT, para pagar taxas de query. Dá para configurar uma taxa máxima de query, para controlar os seus custos e limitar a sua chave de API a um único subgraph ou domínio de origem. O Subgraph Studio fornece dados aos programadores sobre o seu uso temporal de chaves de API.
-
-Os programadores também podem expressar uma preferência de Indexador ao gateway, por exemplo, ao preferir Indexadores com resposta de query mais rápida, ou cujos dados são mais atualizados. Estes controlos são programados no Subgraph Studio.
-
-### Atualização de Subgraphs
-
-Após um tempo, um programador de subgraphs pode querer atualizar o seu subgraph, talvez para consertar um erro ou adicionar funcionalidades. O programador pode lançar uma(s) nova(s) versão (versões) do seu subgraph ao Subgraph Studio, para fins de programação e testes com rate limit.
-
-Quando o Programador de Subgraph estiver pronto, ele pode iniciar uma transação para apontar seu subgraph à nova versão. Atualizar o subgraph migra qualquer sinal à versão nova (presumindo que o utilizador que aplicou o sinal selecionou "migrar automaticamente"), o que também incorre uma taxa de migração. Este sinal de migração deve incentivar os Indexadores a começar a indexar a nova versão do subgraph, para que ele logo fique aberto a queries.
-
-### Depreciação de Subgraphs
-
-Em algum ponto, pode um programador decidir que ele não precisa mais de um subgraph editado. Naquele ponto, ele pode depreciar o subgraph, o que devolve qualquer GRT sinalizado aos Curadores.
-
-### Outros Papeis de Programadores
-
-Alguns programadores engajarão com o ciclo de vida completo do subgraph na rede, com edição, queries, e iterações em seus próprios subgraphs. Alguns podem focar em programação de subgraphs, a construir APIs abertas que outros podem elaborar. Alguns podem focar em aplicativos, a consultar subgraphs lançados por outros.
-
-### Programadores e Economia da Rede
-
-Programadores são agentes económicos importantes na rede, que trancam GRT para incentivar a indexação e fazem queries cruciais em subgraphs — a principal troca de valor da rede. Os programadores de subgraphs também queimam GRT quando um subgraph é atualizado.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 87638d654cff724e246f338d8bf3903193c9b80b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:26 -0500
Subject: [PATCH 0084/1325] New translations contracts.mdx (French)

---
 website/pages/fr/network/contracts.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/fr/network/contracts.mdx b/website/pages/fr/network/contracts.mdx
index 6abd80577ced..b9b33f2c14d7 100644
--- a/website/pages/fr/network/contracts.mdx
+++ b/website/pages/fr/network/contracts.mdx
@@ -1,26 +1,26 @@
 ---
-title: Protocol Contracts
+title: Contrats du Protocole
 ---
 
 import { ProtocolContractsTable } from '@/src/contracts'
 
-Below are the deployed contracts which power The Graph Network. Visit the official [contracts repository](https://github.com/graphprotocol/contracts) to learn more.
+Ci-dessous, les contrats déployés qui alimentent The Graph Network. Visitez le [dépôt officiel des contrats](https://github.com/graphprotocol/contracts) pour en savoir plus.
 
 ## Arbitrum
 
-This is the principal deployment of The Graph Network.
+Il s'agit du déploiement principal de The Graph Network.
 
 <ProtocolContractsTable networkId={42161} />
 
-## Mainnet
+## Réseau principal
 
-This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum.
+Il s'agissait du déploiement initial de The Graph Network. [En savoir plus](/arbitrum/arbitrum-faq) sur la mise à l'échelle de The Graph avec Arbitrum.
 
 <ProtocolContractsTable networkId={1} />
 
 ## Arbitrum Sepolia
 
-This is the primary testnet for The Graph Network. Testnet is predominantly used by core developers and ecosystem participants for testing purposes. There are no guarantees of service or availability on The Graph's testnets.
+Il s'agit du testnet principal pour The Graph Network. Le testnet est principalement utilisé par les développeurs principaux et les participants de l'écosystème à des fins de test. Il n'y a aucune garantie de service ou de disponibilité sur les testnets de The Graph.
 
 <ProtocolContractsTable networkId={421614} />
 

From 68828abb6408bdb02996532f0485eeec83a77a17 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:27 -0500
Subject: [PATCH 0085/1325] New translations subgraphs.mdx (French)

---
 website/pages/fr/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/fr/subgraphs.mdx b/website/pages/fr/subgraphs.mdx
index 27b452211477..2d86a8dea5b8 100644
--- a/website/pages/fr/subgraphs.mdx
+++ b/website/pages/fr/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Flux du cycle de vie des subgraphes
+
+Voici un aperçu général du cycle de vie d'un subgraph :
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 1a301b384f4237f3ffc93e6dd20330eb5454edd6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:28 -0500
Subject: [PATCH 0086/1325] New translations subgraphs.mdx (Turkish)

---
 website/pages/tr/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/tr/subgraphs.mdx b/website/pages/tr/subgraphs.mdx
index 27b452211477..4feb5d9d52c3 100644
--- a/website/pages/tr/subgraphs.mdx
+++ b/website/pages/tr/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Subgraph'ler
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Yaşam Döngüsü
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From b14a5b0ca412dd7fdeaad44973868713834658d1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:29 -0500
Subject: [PATCH 0087/1325] New translations subgraphs.mdx (Russian)

---
 website/pages/ru/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/ru/subgraphs.mdx b/website/pages/ru/subgraphs.mdx
index 27b452211477..a53e52db48ec 100644
--- a/website/pages/ru/subgraphs.mdx
+++ b/website/pages/ru/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Субграфы
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Жизненный цикл подграфа
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From ce1f2520517407619db87319fa1a920bb4d825a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:30 -0500
Subject: [PATCH 0088/1325] New translations delete-a-subgraph.mdx (Romanian)

---
 website/pages/ro/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/ro/managing/delete-a-subgraph.mdx b/website/pages/ro/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/ro/managing/delete-a-subgraph.mdx
+++ b/website/pages/ro/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 0e91c158105fd93d6a64b6a9a0f06f3ff2092f75 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:31 -0500
Subject: [PATCH 0089/1325] New translations delete-a-subgraph.mdx (French)

---
 website/pages/fr/managing/delete-a-subgraph.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/website/pages/fr/managing/delete-a-subgraph.mdx b/website/pages/fr/managing/delete-a-subgraph.mdx
index 68ef0a37da75..5e69052e4f4b 100644
--- a/website/pages/fr/managing/delete-a-subgraph.mdx
+++ b/website/pages/fr/managing/delete-a-subgraph.mdx
@@ -6,10 +6,12 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 
 > Deleting your subgraph will remove all published versions from The Graph Network, but it will remain visible on Graph Explorer and Subgraph Studio for users who have signaled on it.
 
-## Step-by-Step
+## Étape par Étape
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Les curateurs ne seront plus en mesure de signaler le subgraph.
+- Les Curateurs qui ont déjà signalé sur le subgraph peuvent retirer leur signal à un prix moyen par action.
 - Deleted subgraphs will show an error message.

From d620a0925c4901add1bdc13f782878553f1e8d8a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:32 -0500
Subject: [PATCH 0090/1325] New translations delete-a-subgraph.mdx (Spanish)

---
 website/pages/es/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/es/managing/delete-a-subgraph.mdx b/website/pages/es/managing/delete-a-subgraph.mdx
index 68ef0a37da75..0bd18777b42f 100644
--- a/website/pages/es/managing/delete-a-subgraph.mdx
+++ b/website/pages/es/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- Los Curadores ya no podrán señalar en el subgrafo.
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 3534c88ab8bd939b864ac2cb31f8ce9e5bdc06f0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:33 -0500
Subject: [PATCH 0091/1325] New translations delete-a-subgraph.mdx (Arabic)

---
 website/pages/ar/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/ar/managing/delete-a-subgraph.mdx b/website/pages/ar/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/ar/managing/delete-a-subgraph.mdx
+++ b/website/pages/ar/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 96ce0a78292547aedb66a96a2991adeb89b93c9e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:34 -0500
Subject: [PATCH 0092/1325] New translations delete-a-subgraph.mdx (Czech)

---
 website/pages/cs/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/cs/managing/delete-a-subgraph.mdx b/website/pages/cs/managing/delete-a-subgraph.mdx
index 68ef0a37da75..fb6241fd8526 100644
--- a/website/pages/cs/managing/delete-a-subgraph.mdx
+++ b/website/pages/cs/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- Kurátoři již nebudou moci signalizovat na podgrafu.
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 56b8932342ed639c87a7f6177def75a811c8318b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:35 -0500
Subject: [PATCH 0093/1325] New translations delete-a-subgraph.mdx (German)

---
 website/pages/de/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/de/managing/delete-a-subgraph.mdx b/website/pages/de/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/de/managing/delete-a-subgraph.mdx
+++ b/website/pages/de/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 06835348bac365b8b21af64b37a97f62f502fd22 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:36 -0500
Subject: [PATCH 0094/1325] New translations delete-a-subgraph.mdx (Italian)

---
 website/pages/it/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/it/managing/delete-a-subgraph.mdx b/website/pages/it/managing/delete-a-subgraph.mdx
index 68ef0a37da75..fa27461c260a 100644
--- a/website/pages/it/managing/delete-a-subgraph.mdx
+++ b/website/pages/it/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- I Curator non potranno più segnalare il subgraph.
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 5a206f9d41766a2d050bc5cd9b7f563170a13d06 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:37 -0500
Subject: [PATCH 0095/1325] New translations delete-a-subgraph.mdx (Japanese)

---
 website/pages/ja/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/ja/managing/delete-a-subgraph.mdx b/website/pages/ja/managing/delete-a-subgraph.mdx
index 68ef0a37da75..39822d28a77e 100644
--- a/website/pages/ja/managing/delete-a-subgraph.mdx
+++ b/website/pages/ja/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- キュレーターは、サブグラフにシグナルを送ることができなくなります。
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 04886cc5be9c446866c68315bc2a81904c1ad16d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:38 -0500
Subject: [PATCH 0096/1325] New translations delete-a-subgraph.mdx (Korean)

---
 website/pages/ko/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/ko/managing/delete-a-subgraph.mdx b/website/pages/ko/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/ko/managing/delete-a-subgraph.mdx
+++ b/website/pages/ko/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 5fd90aa3fb446f58cef0cdb5fa48e94bc2ea8dd0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:39 -0500
Subject: [PATCH 0097/1325] New translations delete-a-subgraph.mdx (Dutch)

---
 website/pages/nl/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/nl/managing/delete-a-subgraph.mdx b/website/pages/nl/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/nl/managing/delete-a-subgraph.mdx
+++ b/website/pages/nl/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 784bb8f681cb80d9b6f2531979addf3c0b26b9e1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:40 -0500
Subject: [PATCH 0098/1325] New translations delete-a-subgraph.mdx (Polish)

---
 website/pages/pl/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/pl/managing/delete-a-subgraph.mdx b/website/pages/pl/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/pl/managing/delete-a-subgraph.mdx
+++ b/website/pages/pl/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 860d9ae7cb048a00f4a5bc241a15a3f94e00940a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:41 -0500
Subject: [PATCH 0099/1325] New translations delete-a-subgraph.mdx (Portuguese)

---
 website/pages/pt/managing/delete-a-subgraph.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/website/pages/pt/managing/delete-a-subgraph.mdx b/website/pages/pt/managing/delete-a-subgraph.mdx
index 68ef0a37da75..e25db56bdcf3 100644
--- a/website/pages/pt/managing/delete-a-subgraph.mdx
+++ b/website/pages/pt/managing/delete-a-subgraph.mdx
@@ -6,10 +6,12 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 
 > Deleting your subgraph will remove all published versions from The Graph Network, but it will remain visible on Graph Explorer and Subgraph Studio for users who have signaled on it.
 
-## Step-by-Step
+## Passo a Passo
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Os curadores não poderão mais sinalizar no subgraph depreciado.
+- Curadores que já sinalizaram no subgraph poderão retirar a sua sinalização a um preço de ação normal.
 - Deleted subgraphs will show an error message.

From 488837e49ccbd63cff4cdc3ed166c8876c8d8ada Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:42 -0500
Subject: [PATCH 0100/1325] New translations delete-a-subgraph.mdx (Russian)

---
 website/pages/ru/managing/delete-a-subgraph.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/website/pages/ru/managing/delete-a-subgraph.mdx b/website/pages/ru/managing/delete-a-subgraph.mdx
index 68ef0a37da75..68d7658f63f9 100644
--- a/website/pages/ru/managing/delete-a-subgraph.mdx
+++ b/website/pages/ru/managing/delete-a-subgraph.mdx
@@ -6,10 +6,12 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 
 > Deleting your subgraph will remove all published versions from The Graph Network, but it will remain visible on Graph Explorer and Subgraph Studio for users who have signaled on it.
 
-## Step-by-Step
+## Пошаговое руководство
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Кураторы больше не смогут сигналить на сабграф.
+- Кураторы, уже подавшие сигнал на субграф, могут отозвать свой сигнал по средней цене доли.
 - Deleted subgraphs will show an error message.

From b1b757ede81ef5d99942f6ec7463244d4db79f6e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:43 -0500
Subject: [PATCH 0101/1325] New translations index.json (Romanian)

---
 website/pages/ro/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/ro/index.json b/website/pages/ro/index.json
index d8d6eba4a0f2..63c3c940c6fb 100644
--- a/website/pages/ro/index.json
+++ b/website/pages/ro/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explorează subgrafurile și interacționează cu protocolul"
-      },
-      "hostedService": {
-        "title": "Serviciu găzduit",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 066a6df5f860f5076cb75d4fe755e44adb28d2ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:44 -0500
Subject: [PATCH 0102/1325] New translations index.json (French)

---
 website/pages/fr/index.json | 20 ++++++++------------
 1 file changed, 8 insertions(+), 12 deletions(-)

diff --git a/website/pages/fr/index.json b/website/pages/fr/index.json
index c94d94f541f8..dd7f5b249c72 100644
--- a/website/pages/fr/index.json
+++ b/website/pages/fr/index.json
@@ -1,13 +1,13 @@
 {
   "title": "Commencer",
-  "intro": "Découvrez The Graph, un protocole décentralisé pour indexer et interroger les données des blockchains.",
+  "intro": "Découvrez The Graph, un protocole décentralisé d'indexation et d'interrogation des données provenant des blockchains.",
   "shortcuts": {
     "aboutTheGraph": {
-      "title": "À propos du Graph",
+      "title": "À propos de The Graph",
       "description": "En savoir plus sur The Graph"
     },
     "quickStart": {
-      "title": "Début rapide",
+      "title": "Démarrage rapide",
       "description": "Lancez-vous et commencez avec The Graph"
     },
     "developerFaqs": {
@@ -15,8 +15,8 @@
       "description": "Questions fréquemment posées"
     },
     "queryFromAnApplication": {
-      "title": "Requête d'une application",
-      "description": "Apprenez à exécuter vos requêtes d'une application"
+      "title": "Requête depuis une application",
+      "description": "Apprenez à exécuter vos requêtes à partir d'une application"
     },
     "createASubgraph": {
       "title": "Créer un subgraph",
@@ -25,7 +25,7 @@
   },
   "networkRoles": {
     "title": "Les divers rôles du réseau",
-    "description": "Découvrez les rôles réseau de The Graph.",
+    "description": "Découvrez les divers rôles du réseau The Graph.",
     "roles": {
       "developer": {
         "title": "Développeur",
@@ -56,16 +56,12 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explorer les subgraphs et interagir avec le protocole"
-      },
-      "hostedService": {
-        "title": "Service hébergé",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },
   "supportedNetworks": {
     "title": "Réseaux pris en charge",
-    "description": "The Graph supports the following networks.",
-    "footer": "For more details, see the {0} page."
+    "description": "The Graph prend en charge les réseaux suivants.",
+    "footer": "Pour plus de détails, consultez la page {0}."
   }
 }

From d64078576743ee84cfb2f1efaa2f977def00d981 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:45 -0500
Subject: [PATCH 0103/1325] New translations index.json (Spanish)

---
 website/pages/es/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/es/index.json b/website/pages/es/index.json
index 7abab377ea71..0fd4bc82e691 100644
--- a/website/pages/es/index.json
+++ b/website/pages/es/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explora los distintos subgrafos e interactua con el protocolo"
-      },
-      "hostedService": {
-        "title": "Servicio Alojado",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From f69563f6ac8010e9dfbd6253cdbb3a3256aa2d31 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:46 -0500
Subject: [PATCH 0104/1325] New translations developer-faqs.mdx (Ukrainian)

---
 .../pages/uk/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/uk/developing/developer-faqs.mdx b/website/pages/uk/developing/developer-faqs.mdx
index 0ace9cbee870..68f141868759 100644
--- a/website/pages/uk/developing/developer-faqs.mdx
+++ b/website/pages/uk/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: FAQ для розробників
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-It is not possible to delete subgraphs once they are created.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-No. Once a subgraph is created, the name cannot be changed. Make sure to think of this carefully before you create your subgraph so it is easily searchable and identifiable by other dapps.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-No. Once a subgraph is created, the associated GitHub account cannot be changed. Make sure to think of this carefully before you create your subgraph.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-You can run the following command:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**NOTE:** docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so it is important to do this to make sure you are up to date with the latest version of graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+You can run the following command:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Yes. You can do this by importing `graph-ts` as per the example below:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Not currently, as mappings are written in AssemblyScript. One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
 
@@ -102,19 +121,7 @@ Yes! Try the following command, substituting "organization/subgraphName" with th
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation is not supported yet, although we do want to support it in the future. At the moment, something you can do is use schema stitching, either on the client or via a proxy service.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From cd9769cc5fb5db9a3488dbf0684175019d1b0560 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:47 -0500
Subject: [PATCH 0105/1325] New translations developer-faqs.mdx (Chinese
 Simplified)

---
 .../pages/zh/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/zh/developing/developer-faqs.mdx b/website/pages/zh/developing/developer-faqs.mdx
index e223135992e7..8b62385e49c4 100644
--- a/website/pages/zh/developing/developer-faqs.mdx
+++ b/website/pages/zh/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: 开发者常见问题
 ---
 
-## 什么是子图？
+This page summarizes some of the most common questions for developers building on The Graph.
 
-子图是基于区块链数据构建的自定义API。子图使用GraphQL查询语言进行查询，并使用Graph CLI部署到Graph节点。一旦部署并发布到Graph的去中心化网络，索引人就会处理子图，并使其可供子图消费者查询。
+## Subgraph Related
 
-## 2. 我可以删除我的子图吗？
+### 什么是子图？
 
-子图一旦创建就无法删除。
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. 我可以更改我的子图名称吗？
+### 2. What is the first step to create a subgraph?
 
-不可以。一旦创建子图，就不能更改名称。 请务必在创建子图之前仔细考虑这一点，以便其他 dapp 可以轻松搜索和识别它。
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. 我可以更改与我的子图关联的 GitHub 账户吗？
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-不可以。一旦创建了子图，就不能更改关联的 GitHub 账户。 在创建子图之前，请务必仔细考虑这一点。
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. 如果我的智能合约没有事件，还能创建子图吗？
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-强烈建议您构建智能合约，以使事件与您有兴趣查询的数据相关联。 子图中的事件处理程序由合约事件触发，是迄今为止检索有用数据的最快方式。
+### 4. 我可以更改与我的子图关联的 GitHub 账户吗？
 
-如果您正在使用的合约不包含事件，您的子图可以使用调用和区块处理程序来触发索引。 因为这样做会严重影响性能，所以不建议。
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. 是否可以在多个网络上部署同名的子图？
+### 5. How do I update a subgraph on mainnet?
 
-在多个网络的情况下，您将需要不同的名称。 虽然您不能在同一个名称下拥有不同的子图，但有一些方便的方法可以为多个网络提供一个代码库。 请在我们的文档中找到更多相关信息：[重新部署子图](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. 模板与数据源有何不同？
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-模板允许您在子图索引时动态创建数据源。 当人们与之交互时，您的合约可能会产生新的合约，并且由于您预先知道这些合同的架构（ABI、事件等），您可以定义您希望如何在模板中索引它们，当这些合约创建您的子图时将通过提供合约地址来创建动态数据源。
+您必须重新部署子图，但如果子图 ID（IPFS hash）没有更改，则不必从头开始同步。
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+在子图中，无论是否跨多个合约，事件始终按照它们在区块中出现的顺序进行处理的。
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 请查看“实例化数据源模板”部分：[数据源模板](/developing/creating-a-subgraph#data-source-templates)。
 
-## 8. 如何确保我使用最新版本的 graph-node 进行本地部署？
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-您可以运行以下命令：
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**注意：** docker / docker-compose 将始终使用您第一次运行时提取的任何 graph-node 版本，因此执行此操作非常重要，可以确保您使用的是最新版本的 graph-node。
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. 如何从我的子图映射中调用合约函数，或访问公共状态变量？
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. 是否可以使用 `graph-cli` 中的 `graph init` 和两个合约来设置子图？ 还是应该在运行 `graph init` 之后在 `subgraph.yaml` 中手动添加另一个数据源？
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+您可以运行以下命令：
 
-## 11. 我想向 GitHub 贡献代码或者添加 issue，在哪里可以找到相关代码？
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [图节点](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. 在处理事件时，为实体构建“自动生成”id 的推荐方法是什么？
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 如果在事件期间只创建了一个实体并且没有更好的其他方法，那么交易hash + 日志索引的组合是唯一的。 您可以先将其转换为字节，然后将调用 `crypto.keccak256` 来混淆这些内容，但这不会使其更加独特。
 
-## 13、监听多个合约时，是否可以选择监听事件的合约顺序？
+### 15. Can I delete my subgraph?
 
-在子图中，无论是否跨多个合约，事件始终按照它们在区块中出现的顺序进行处理的。
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+您可以在[这里](/developing/supported-networks)找到支持的网络列表。
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 是的。 您可以按照以下示例通过导入 `graph-ts` 来做到这一点：
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. 我可以将 ethers.js 或其他 JS 库导入我的子图映射吗？
-
-目前不能，因为映射是用 AssemblyScript 编写的。 一种可能的替代解决方案是将原始数据存储在实体中，并在客户端执行需要 JS 库的逻辑。
+## Indexing & Querying Related
 
-## 17. 是否可以指定从哪个特定区块开始索引？
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. 有没有一些提高索引性能的技巧？ 子图需要很长时间才能同步。
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-是的，您应该看看可选的起始区块功能，以便从部署合约的区块开始索引：[起始区块](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. 有没有办法直接查询子图，来确定它索引的最新区块号是多少？
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 是的！ 请尝试以下命令，并将“organization/subgraphName”替换为发布的组织和子图名称：
 
@@ -102,44 +121,27 @@ Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the n
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. Graph 支持哪些网络？
-
-您可以在[这里](/developing/supported-networks)找到支持的网络列表。
-
-## 21. 是否可以在不重新部署的情况下，将子图复制到另一个账户或端点？
-
-您必须重新部署子图，但如果子图 ID（IPFS hash）没有更改，则不必从头开始同步。
-
-## 22. 可以在 graph节点之上使用 Apollo Federation 吗？
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-虽然我们确实希望在未来支持联合(Federation)，但目前还不支持。 目前，您可以在客户端或通过代理服务使用模式拼接。
-
-## 23. Graph 每次查询可以返回多少个对象有限制吗？
-
-默认情况下，每个集合的查询响应限制为 100 个项目。 如果您想收到更多，则每个收藏最多可以包含 1000 个项目，并且可以使用以下查询进行分页：
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. 如果我的 dapp 前端使用Graph 进行查询，我是否需要将我的查询密钥直接写入前端？ 如果我们为用户支付查询费用，恶意用户会不会导致我们的查询费用非常高？
-
-目前，推荐的 dapp 方法是将密钥添加到前端并将其公开给最终用户。 也就是说，您可以将该键限制为主机名，例如 _yourdapp.io_ 和子图。 网关目前由 Edge & Node 运营。 网关的部分职责是监控滥用行为，并阻止来自恶意客户端的流量。
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-请前往托管服务，查找您或其他人部署到托管服务的子图。 您可以在[这里](https://thegraph.com/hosted-service)找到托管服务。
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-Graph 永远不会对托管服务收费。 Graph 是一个去中心化的协议，中心化服务的收费与 Graph 的价值观不一致。 托管服务始终是帮助进入去中心化网络的临时步骤。 开发人员将有足够的时间在他们适宜时迁移到去中心化网络。
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [图节点](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From a880d4d749c4c16bf6748fe27e0a7f434883ceb8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:48 -0500
Subject: [PATCH 0106/1325] New translations developer-faqs.mdx (Urdu
 (Pakistan))

---
 .../pages/ur/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/ur/developing/developer-faqs.mdx b/website/pages/ur/developing/developer-faqs.mdx
index 5070304b0f43..27c0a08a2147 100644
--- a/website/pages/ur/developing/developer-faqs.mdx
+++ b/website/pages/ur/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: ڈویلپر کے اکثر پوچھے گئے سوالات
 ---
 
-## سب گراف کیا ہے؟
+This page summarizes some of the most common questions for developers building on The Graph.
 
-سب گراف ایک کسٹم API ہے جو بلاکچین ڈیٹا پر بنا ہے. سب گرافس کا GraphQL کی کیوری لینگویج کا استعمال ہوتے ہوۓ کیوری ہوتا ہے اور گراف CLI کا استعمال ہوتے ہوۓ گراف نوڈ پر تعینات ہوتے ہیں. گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر تعینات اور شائع ہونے کے بعد، انڈیکسرز سب گراف پر کارروائی کرتے ہیں اور انہیں سب گراف صارفین کے لیے کیوری کرنے کے لیے دستیاب کرتے ہیں.
+## Subgraph Related
 
-## 2. کیا میں اپنا سب گراف ختم کر سکتا ہوں
+### سب گراف کیا ہے؟
 
-ایک بار سب گرافس بن جائیں تو ان کو ختم کرنا ممکن نہیں ہے.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. کیا میں اپنے سب گراف کا نام تبدیل کر سکتا ہوں؟
+### 2. What is the first step to create a subgraph?
 
-نہیں. ایک بار سب گراف بن جاۓ، اس کا نام بدل نہیں سکتا. اپنا سب گراف بنانے سے پہلے اس کے بارے میں احتیاط سے سوچنا یقینی بنائیں تاکہ یہ دوسرے ڈی ایپس کے ذریعے آسانی سے تلاش اور شناخت کے قابل ہو.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. کیا میں گٹ ہب کا اکاونٹ بدل سکتا ہوں جو میرے سب گراف کے ساتھ وابستہ ہے؟
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-نہیں. ایک بار سب گراف بن جاۓ، متعلقہ گٹ ہب اکاؤنٹ کو تبدیل نہیں کیا جا سکتا. اپنا سب گراف بنانے سے پہلے اس کے بارے میں احتیاط سے سوچنا یقینی بنائیں.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. کیا میں اب بھی ایک سب گراف بنانے کے قابل ہوں اگر میرے سمارٹ کنٹریکٹ میں ایونٹس نہ ہوں؟
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-یہ انتہائی سفارش کی جاتی ہے کہ آپ اپنے سمارٹ کنٹریکٹس کو ایونٹس کے لیے تشکیل دیں اس ڈیٹا سے وابستہ جس سے آپ کیوری کرنے میں دلچسپی رکھتے ہیں۔ سب گراف میں ایونٹ ہینڈلرز کنٹریکٹ کے واقعات سے متحرک ہوتے ہیں اور مفید ڈیٹا کو بازیافت کرنے کا اب تک کا تیز ترین طریقہ ہے.
+### 4. کیا میں گٹ ہب کا اکاونٹ بدل سکتا ہوں جو میرے سب گراف کے ساتھ وابستہ ہے؟
 
-اگر آپ جن کنٹریکٹس کے ساتھ کام کر رہے ہیں ان میں ایونٹس شامل نہیں ہیں، تو آپ کا سب گراف انڈیکسنگ کو متحرک کرنے کے لیے کال اور بلاک ہینڈلرز کا استعمال کر سکتا ہے۔ اگرچہ اس کی سفارش نہیں کی جاتی ہے، کیونکہ کارکردگی کافی سست ہوگی.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. کیا متعدد نیٹ ورکس کے لیے ایک نام کے ساتھ ایک سب گراف تعینات کرنا ممکن ہے؟
+### 5. How do I update a subgraph on mainnet?
 
-آپ کو متعدد نیٹ ورکس کے لیے الگ الگ ناموں کی ضرورت ہوگی۔ اگرچہ آپ کے پاس ایک ہی نام کے تحت مختلف سب گراف نہیں ہوسکتے ہیں، متعدد نیٹ ورکس کے لیے ایک کوڈ بیس رکھنے کے آسان طریقے ہیں۔ ہماری دستاویزات میں اس کے بارے میں مزید معلومات حاصل کریں: [سب گراف کو دوبارہ تعینات کرنا](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. ٹیمپلیٹس ڈیٹا سورسز سے کیسے مختلف ہے؟
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-ٹیمپلیٹس آپ کو پرواز پر ڈیٹا کے ذرائع بنانے کی اجازت دیتے ہیں، جب کہ آپ کا سب گراف انڈیکس کر رہا ہوتا ہے۔ ایسا ہو سکتا ہے کہ آپ کا کنٹریکٹ نئے کنٹریکٹس کو جنم دے گا کیونکہ لوگ اس کے ساتھ تعامل کرتے ہیں، اور چونکہ آپ ان کنٹریکٹس (ABI، ایونٹس وغیرہ) کی شکل کو پہلے ہی جانتے ہیں، آپ اس بات کی وضاحت کر سکتے ہیں کہ آپ انہیں ٹیمپلیٹ میں کیسے ترتیب دینا چاہتے ہیں اور وہ کب آپ کا سب گراف کنٹریکٹ ایڈریس فراہم کرکے ایک متحرک ڈیٹا سورس بنائے گا.
+آپ کو سب گراف کو دوبارہ تعینات کرنا ہوگا، لیکن اگر سب گراف ID (IPFS ہیش) تبدیل نہیں ہوتا ہے، تو اسے شروع سے مطابقت پذیر نہیں ہونا پڑے گا.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+سب گراف کے اندر، ایونٹس کو ہمیشہ اسی ترتیب سے پروسیس کیا جاتا ہے جس ترتیب سے وہ بلاکس میں ظاہر ہوتے ہیں، قطع نظر اس کے کہ یہ متعدد کنٹریکٹس میں ہے یا نہیں.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 [ڈیٹا سورس ٹیمپلیٹس](/developing/creating-a-subgraph#data-source-templates) پر "ڈیٹا سورس ٹیمپلیٹ کو تیز کرنا" سیکشن دیکھیں.
 
-## 8. میں یہ کیسے یقینی بنا سکتا ہوں کہ میں اپنی مقامی تعیناتیوں کے لیے گراف نوڈ کا تازہ ترین ورژن استعمال کر رہا ہوں؟
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-آپ زیل میں دی گئ کمانڈ چلا سکتے ہیں:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**نوٹ:** docker / docker-compose ہمیشہ استعمال کرے گا جو بھی گراف نوڈ ورژن آپ نے پہلی بار چلاتے وقت کھینچا تھا، لہذا یہ یقینی بنانے کے لیے یہ کرنا ضروری ہے کہ آپ گراف نوڈ کے تازہ ترین ورژن کے ساتھ اپ ٹو ڈیٹ ہیں.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. میں کنٹریکٹ فنکشن کو کیسے کال کر سکتا ہوں یا اپنے سب گراف میپنگ سے پبلک سٹیٹ متغیر تک کیسے رسائ حاصل کر سکتا ہوں؟
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. کیا دو کنٹریکٹس کے ساتھ `graph init` سے `graph` کا استعمال کرتے ہوئے سب گراف ترتیب دینا ممکن ہے؟ یا مجھے `graph init` چلانے کے بعد دستی طور پر `subgraph.yaml` میں دوسرا ڈیٹا سورس شامل کرنا چاہیے؟
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+آپ زیل میں دی گئ کمانڈ چلا سکتے ہیں:
 
-## 11. میں تعاون کرنا چاہتا ہوں یا گٹ ہب اشو شامل کرنا چاہتا ہوں۔ مجھے اوپن سورس ریپوزٹریز کہاں سے مل سکتی ہیں؟
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. ایونٹس کو سنبھالتے وقت کسی ہستی کے لیے "خود کار طریقے سے تیار کردہ" آئی ڈیز بنانے کا تجویز کردہ طریقہ کیا ہے؟
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 اگر ایونٹ کے دوران صرف ایک ہستی بنائی جاتی ہے اور اگر اس سے بہتر کوئی چیز دستیاب نہیں ہے، تو ٹرانزیکشن ہیش + لاگ انڈیکس منفرد ہوگا۔ آپ اسے بائٹس میں تبدیل کرکے اور پھر اسے `crypto.keccak256` کے ذریعے پائپ کر کے مبہم کر سکتے ہیں لیکن یہ اسے مزید منفرد نہیں بنائے گا.
 
-## 13. متعدد کنٹریکٹس کو سنتے وقت، کیا ایونٹس کو سننے کے لیے کنٹریکٹ آرڈر کو منتخب کرنا ممکن ہے؟
+### 15. Can I delete my subgraph?
 
-سب گراف کے اندر، ایونٹس کو ہمیشہ اسی ترتیب سے پروسیس کیا جاتا ہے جس ترتیب سے وہ بلاکس میں ظاہر ہوتے ہیں، قطع نظر اس کے کہ یہ متعدد کنٹریکٹس میں ہے یا نہیں.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+آپ کو تعاون یافتہ نیٹ ورکس کی فہرست [یہاں](/developing/supported-networks) مل سکتی ہے.
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 جی ہاں. آپ ذیل کی مثال کے مطابق `graph-ts` درآمد کر کے ایسا کر سکتے ہیں:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. کیا میں ethers.js یا دوسری JS لائبریریز کو اپنے سب گراف میپنگس میں درآمد کر سکتا ہوں?
-
-فی الحال نہیں، جیسا کہ میپنگ اسمبلی اسکرپٹ میں لکھی جاتی ہے۔ اس کا ایک ممکنہ متبادل حل یہ ہے کہ خام ڈیٹا کو اداروں میں اسٹور کیا جائے اور وہ منطق انجام دی جائے جس کے لیے کلائنٹ پر JS لائبریریوں کی ضرورت ہو.
+## Indexing & Querying Related
 
-## 17. کیا یہ وضاحت کرنا ممکن ہے کہ کس بلاک پر انڈیکسنگ شروع کرنی ہے؟
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. کیا انڈیکسنگ کی کارکردگی کو بڑھانے کے لیے کچھ نکات ہیں؟ میرا سب گراف مطابقت پزیر ہونے میں بہت زیادہ وقت لے رہا ہے
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-ہاں، آپ کو اس بلاک سے انڈیکسنگ شروع کرنے کے لیے اختیاری اسٹارٹ بلاک کی خصوصیت پر ایک نظر ڈالنی چاہیے جس میں کنٹریکٹ تعینات کیا گیا تھا: [اسٹارٹ بلاکس](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. کیا سب گراف سے براہ رست کیوری کرنے کا کوئ طریقہ ہے تاکہ اس نے جو تازہ ترین بلاک نمبر ترتیب دیا ہو اس کا تعین کیا جا سکے؟
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 جی ہاں! مندرجہ ذیل کمانڈ کو آزمائیں، "تنظیم/سب گراف نام" کو اس کے تحت شائع ہونے والی تنظیم کے ساتھ تبدیل کرتے ہوئے اور آپ کے سب گراف کا نام:
 
@@ -102,44 +121,27 @@ Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the n
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. گراف کن نیٹ ورکس کو سپورٹ کرتا ہے؟
-
-آپ کو تعاون یافتہ نیٹ ورکس کی فہرست [یہاں](/developing/supported-networks) مل سکتی ہے.
-
-## 21. کیا یہ ممکن ہے کہ سب گراف کو دوسرے اکاؤنٹ یا اینڈ پوائنٹ پر دوبارہ تعینات کیے بغیر نقل کیا جائے؟
-
-آپ کو سب گراف کو دوبارہ تعینات کرنا ہوگا، لیکن اگر سب گراف ID (IPFS ہیش) تبدیل نہیں ہوتا ہے، تو اسے شروع سے مطابقت پذیر نہیں ہونا پڑے گا.
-
-## 22. کیا گراف نوڈ کے اوپر اپالو فیڈریشن کا استعمال کرنا ممکن ہے؟
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-فیڈریشن کو ابھی تک سپورٹ نہیں کیا گیا ہے، حالانکہ ہم مستقبل میں اس کی حمایت کرنا چاہتے ہیں۔ اس وقت، آپ جو کچھ کر سکتے ہیں وہ ہے اسکیما سٹیچنگ کا استعمال، یا تو کلائنٹ پر یا پراکسی سروس کے ذریعے.
-
-## 23. کیا اس بات کی کوئ حد ہے کہ گراف فی کیوری کتنے آبجیکٹ واپس کر سکتا ہے؟
-
-پہلے سے طے شدہ طور پر، سوالات کے جوابات فی مجموعہ 100 آئٹمز تک محدود ہیں۔ اگر آپ مزید وصول کرنا چاہتے ہیں، تو آپ فی مجموعہ 1000 آئٹمز تک جا سکتے ہیں اور اس سے آگے، آپ اس کے ساتھ صفحہ بندی کر سکتے ہیں:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. اگر میرا ڈیپ فرنٹ اینڈ کیوری کرنے کے لیے گراف کا استعمال کرتا ہے، تو مجھے اپنی کیوری کی کلید براہ راست فرنٹ اینڈ کیوری کی ضرورت ہے؟ کیا اگر ہم صارفین کے لیے کیوری کی فیس ادا کرتے ہیں - کیا بدنیتی پر مبنی صارفین ہماری کیوری کی فیس کو بہت زیادہ کرنے کا سبب بنیں گے؟
-
-فی الحال، ڈیپ کے لیے تجویز کردہ طریقہ یہ ہے کہ کلید کو فرنٹ اینڈ میں شامل کیا جائے اور اسے اختتامی صارفین کے سامنے لایا جائے۔ اس نے کہا، آپ اس کلید کو میزبان نام تک محدود کر سکتے ہیں، جیسے _yourdapp.io_ اور سب گراف۔ گیٹ وے فی الحال ایج اور نوڈ گیٹ وے کی ذمہ داری کا حصہ بدسلوکی پر نظر رکھنا اور بدسلوکی والے کلائنٹس سے ٹریفک کو روکنا ہے.
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-سب گراف تلاش کرنے کے لیے ہوسٹڈ سروس کی طرف جائیں جو آپ یا دوسروں نے ہوسٹڈ سروس میں تعینات کیے ہیں۔ آپ اسے [یہاں](https://thegraph.com/hosted-service) تلاش کر سکتے ہیں۔
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-گراف ہوسٹڈ سروس کے لیے کبھی بھی پیسے نہیں لے گا۔ گراف ایک ڈیسینٹرالائزڈ پروٹوکول ہے، اور سینٹرالائزڈ سروسز کے لیے پیسے لینا گراف کی اقدار کے ساتھ موافق نہیں ہے۔ ہوسٹڈ سروس ہمیشہ سے ہی ایک عارضی قدم ہوتا ہے تاکہ ڈیسینترالائزڈ نیٹ ورک تک پہنچنے میں مدد کی جا سکے۔ ڈویلپرز کے پاس ڈیسینٹرالائزڈ نیٹ ورک میں اپ گریڈ کرنے کے لیے کافی وقت ہوگا کیونکہ وہ آرام دہ ہیں۔
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 3bf56f99649688106f61f696dbcdfe951e72bf23 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:50 -0500
Subject: [PATCH 0107/1325] New translations developer-faqs.mdx (Vietnamese)

---
 .../pages/vi/developing/developer-faqs.mdx    | 142 +++++++++---------
 1 file changed, 72 insertions(+), 70 deletions(-)

diff --git a/website/pages/vi/developing/developer-faqs.mdx b/website/pages/vi/developing/developer-faqs.mdx
index 9fd66e6afc9b..202cab4c4ff2 100644
--- a/website/pages/vi/developing/developer-faqs.mdx
+++ b/website/pages/vi/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: Câu hỏi thường gặp dành cho nhà phát triển
 ---
 
-## 1. What is a subgraph?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using the Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available to be queried by subgraph consumers.
+## Subgraph Related
 
-## 2. Can I delete my subgraph?
+### 1. What is a subgraph?
 
-Không thể xóa các subgraph sau khi chúng được tạo.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. Can I change my subgraph name?
+### 2. What is the first step to create a subgraph?
 
-Không. Khi một subgraph được tạo, không thể thay đổi tên. Hãy đảm bảo suy nghĩ kỹ về điều này trước khi bạn tạo subgraph của mình để các dapp khác có thể dễ dàng tìm kiếm và nhận dạng được.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. Can I change the GitHub account associated with my subgraph?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-Không. Sau khi tạo subgraph, không thể thay đổi tài khoản GitHub được liên kết. Hãy đảm bảo suy nghĩ kỹ về điều này trước khi bạn tạo subgraph của mình.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. Am I still able to create a subgraph if my smart contracts don't have events?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are by far the fastest way to retrieve useful data.
+### 4. Can I change the GitHub account associated with my subgraph?
 
-If the contracts you are working with do not contain events, your subgraph can use call and block handlers to trigger indexing. Although this is not recommended, as performance will be significantly slower.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. Is it possible to deploy one subgraph with the same name for multiple networks?
+### 5. How do I update a subgraph on mainnet?
 
-You will need separate names for multiple networks. While you can't have different subgraphs under the same name, there are convenient ways of having a single codebase for multiple networks. Find more on this in our documentation: [Redeploying a Subgraph](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. How are templates different from data sources?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-Templates allow you to create data sources on the fly, while your subgraph is indexing. It might be the case that your contract will spawn new contracts as people interact with it, and since you know the shape of those contracts (ABI, events, etc) upfront you can define how you want to index them in a template and when they are spawned your subgraph will create a dynamic data source by supplying the contract address.
+Bạn phải triển khai lại subgraph, nhưng nếu ID subgraph (mã băm IPFS) không thay đổi, nó sẽ không phải đồng bộ hóa từ đầu.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Trong một subgraph, các sự kiện luôn được xử lý theo thứ tự chúng xuất hiện trong các khối, bất kể điều đó có qua nhiều hợp đồng hay không.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
 
-## 8. How do I make sure I'm using the latest version of graph-node for my local deployments?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-Bạn có thể chạy lệnh sau:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-docker pull graphprotocol/graph-node:latest
-```
+You can also use `graph add` command to add a new dataSource.
 
-**LƯU Ý:** docker / docker-compose sẽ luôn sử dụng bất kỳ phiên bản graph-node nào được kéo vào lần đầu tiên bạn chạy nó, vì vậy điều quan trọng là phải làm điều này để đảm bảo bạn được cập nhật phiên bản mới nhất của graph-node.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. How do I call a contract function or access a public state variable from my subgraph mappings?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another datasource in `subgraph.yaml` after running `graph init`?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+Bạn có thể chạy lệnh sau:
 
-## 11. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+```sh
+docker pull graphprotocol/graph-node:latest
+```
 
-- [graph-node](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 Nếu chỉ một thực thể được tạo trong sự kiện và nếu không có gì tốt hơn khả dụng, thì chỉ mục log + băm giao dịch sẽ là duy nhất. Bạn có thể làm xáo trộn chúng bằng cách chuyển đổi nó thành Byte và sau đó chuyển nó qua`crypto.keccak256` nhưng điều này sẽ không làm cho nó độc đáo hơn.
 
-## 13. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+### 15. Can I delete my subgraph?
 
-Trong một subgraph, các sự kiện luôn được xử lý theo thứ tự chúng xuất hiện trong các khối, bất kể điều đó có qua nhiều hợp đồng hay không.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 Đúng. Bạn có thể thực hiện việc này bằng cách nhập `graph-ts` theo ví dụ bên dưới:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. Can I import ethers.js or other JS libraries into my subgraph mappings?
-
-Hiện tại thì không, vì các ánh xạ được viết bằng AssemblyScript. Một giải pháp thay thế khả thi cho điều này là lưu trữ dữ liệu thô trong các thực thể và thực hiện logic yêu cầu thư viện JS trên máy khách.
+## Indexing & Querying Related
 
-## 17. Is it possible to specify what block to start indexing on?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. Are there some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-Yes, you should take a look at the optional start block feature to start indexing from the block that the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 Có! Hãy thử lệnh sau, thay thế "organization/subgraphName" bằng tổ chức dưới nó được xuất bản và tên của subgraph của bạn:
 
@@ -102,19 +121,7 @@ Có! Hãy thử lệnh sau, thay thế "organization/subgraphName" bằng tổ c
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
 ```
 
-## 20. What networks are supported by The Graph?
-
-You can find the list of the supported networks [here](/developing/supported-networks).
-
-## 21. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
-
-Bạn phải triển khai lại subgraph, nhưng nếu ID subgraph (mã băm IPFS) không thay đổi, nó sẽ không phải đồng bộ hóa từ đầu.
-
-## 22. Is this possible to use Apollo Federation on top of graph-node?
-
-Federation chưa được hỗ trợ, mặc dù chúng tôi muốn hỗ trợ nó trong tương lai. Hiện tại, điều bạn có thể làm là sử dụng tính năng ghép lược đồ, trên máy khách hoặc thông qua dịch vụ proxy.
-
-## 23. Is there a limit to how many objects The Graph can return per query?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
 By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
@@ -122,24 +129,19 @@ By default, query responses are limited to 100 items per collection. If you want
 someCollection(first: 1000, skip: <number>) { ... }
 ```
 
-## 24. If my dapp frontend uses The Graph for querying, do I need to write my query key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
 Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
-
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
-
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 13dcc7333b5d1d1d1e07c26863d612374c91e182 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:51 -0500
Subject: [PATCH 0108/1325] New translations developer-faqs.mdx (Marathi)

---
 .../pages/mr/developing/developer-faqs.mdx    | 146 +++++++++---------
 1 file changed, 74 insertions(+), 72 deletions(-)

diff --git a/website/pages/mr/developing/developer-faqs.mdx b/website/pages/mr/developing/developer-faqs.mdx
index 82680a88f462..1507d740d45b 100644
--- a/website/pages/mr/developing/developer-faqs.mdx
+++ b/website/pages/mr/developing/developer-faqs.mdx
@@ -2,72 +2,93 @@
 title: विकसक वारंवार विचारले जाणारे प्रश्न
 ---
 
-## 1. सबग्राफ म्हणजे काय?
+This page summarizes some of the most common questions for developers building on The Graph.
 
-सबग्राफ हा ब्लॉकचेन डेटावर तयार केलेला कस्टम API आहे. ग्राफक्यूएल क्वेरी भाषेचा वापर करून सबग्राफ्स विचारले जातात आणि ग्राफ सीएलआय वापरून ग्राफ नोडमध्ये तैनात केले जातात. एकदा द ग्राफच्या विकेंद्रीकृत नेटवर्कवर तैनात आणि प्रकाशित झाल्यानंतर, इंडेक्सर्स सबग्राफवर प्रक्रिया करतात आणि सबग्राफ ग्राहकांद्वारे विचारण्यासाठी त्यांना उपलब्ध करून देतात.
+## Subgraph Related
 
-## 2. मी माझा सबग्राफ हटवू शकतो?
+### 1. सबग्राफ म्हणजे काय?
 
-एकदा सबग्राफ तयार केल्यावर ते हटवणे शक्य नाही.
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
 
-## 3. मी माझे सबग्राफ नाव बदलू शकतो का?
+### 2. What is the first step to create a subgraph?
 
-नाही. एकदा सबग्राफ तयार केल्यावर नाव बदलता येत नाही. तुम्ही तुमचा सबग्राफ तयार करण्यापूर्वी याचा काळजीपूर्वक विचार केल्याचे सुनिश्चित करा जेणेकरून ते इतर डॅप्सद्वारे सहजपणे शोधता येईल आणि ओळखता येईल.
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
 
-## 4. मी माझ्या सबग्राफशी संबंधित गिटहब खाते बदलू शकतो का?
+### 3. Can I still create a subgraph if my smart contracts don't have events?
 
-नाही. एकदा सबग्राफ तयार केल्यावर, संबंधित GitHub खाते बदलता येत नाही. तुमचा सबग्राफ तयार करण्यापूर्वी याचा काळजीपूर्वक विचार करा.
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
 
-## 5. माझ्या स्मार्ट कॉन्ट्रॅक्टमध्ये इव्हेंट नसल्यास मी सबग्राफ तयार करू शकतो का?
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
 
-तुम्‍हाला क्‍वेरी करण्‍यात स्वारस्य असलेल्‍या डेटाशी संबंधित इव्‍हेंट असण्‍यासाठी तुम्‍ही तुमच्‍या स्‍मार्ट कॉन्ट्रॅक्टची रचना करण्‍याची शिफारस केली जाते. सबग्राफमधील इव्हेंट हँडलर कॉन्ट्रॅक्ट इव्हेंटद्वारे ट्रिगर केले जातात आणि उपयुक्त डेटा पुनर्प्राप्त करण्याचा सर्वात जलद मार्ग आहे.
+### 4. मी माझ्या सबग्राफशी संबंधित गिटहब खाते बदलू शकतो का?
 
-जर तुम्ही काम करत असलेल्या करारांमध्ये इव्हेंट्स नसतील, तर तुमचा सबग्राफ इंडेक्सिंग ट्रिगर करण्यासाठी कॉल आणि ब्लॉक हँडलर वापरू शकतो. जरी याची शिफारस केलेली नाही, कारण कार्यप्रदर्शन लक्षणीयरीत्या हळू होईल.
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
 
-## 6. एकाधिक नेटवर्कसाठी समान नावाचा एक सबग्राफ तैनात करणे शक्य आहे का?
+### 5. How do I update a subgraph on mainnet?
 
-तुम्हाला एकाधिक नेटवर्कसाठी स्वतंत्र नावांची आवश्यकता असेल. तुमच्याकडे एकाच नावाखाली वेगवेगळे सबग्राफ असू शकत नसले तरी, एकाधिक नेटवर्कसाठी एकच कोडबेस ठेवण्याचे सोयीचे मार्ग आहेत. आमच्या दस्तऐवजात याबद्दल अधिक शोधा: [सबग्राफ पुन्हा तैनात करणे](/deploying/deploying-a-subgraph-to-hosted#redeploying-a-subgraph)
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
 
-## 7. डेटा स्रोतांपेक्षा टेम्पलेट वेगळे कसे आहेत?
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
 
-तुमचा सबग्राफ इंडेक्स करत असताना टेम्प्लेट्स तुम्हाला फ्लायवर डेटा स्रोत तयार करण्याची परवानगी देतात. असे असू शकते की तुमचा करार नवीन करार तयार करेल कारण लोक त्याच्याशी संवाद साधतील आणि तुम्हाला त्या करारांचे स्वरूप (एबीआय, इव्हेंट इ.) आधीच माहित असल्याने तुम्ही ते टेम्पलेटमध्ये कसे अनुक्रमित करायचे आणि ते केव्हा ते परिभाषित करू शकता. तुमचा सबग्राफ कराराचा पत्ता पुरवून डायनॅमिक डेटा स्रोत तयार करेल.
+तुम्हाला सबग्राफ पुन्हा तैनात करावा लागेल, परंतु सबग्राफ आयडी (IPFS हॅश) बदलत नसल्यास, त्याला सुरुवातीपासून सिंक करण्याची गरज नाही.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+सबग्राफमध्‍ये, इव्‍हेंट नेहमी ब्लॉकमध्‍ये दिसण्‍याच्‍या क्रमाने संसाधित केले जातात, ते एकाधिक कॉन्ट्रॅक्टमध्‍ये असले किंवा नसले तरीही.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
 
 [डेटा स्रोत टेम्पलेट्स](/developing/creating-a-subgraph#data-source-templates) यावर "डेटा स्त्रोत टेम्पलेट इन्स्टंटिएटिंग करणे" विभाग पहा.
 
-## 8. मी माझ्या स्थानिक उपयोजनांसाठी ग्राफ-नोडची नवीनतम आवृत्ती वापरत असल्याची खात्री कशी करावी?
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
 
-तुम्ही खालील आदेश चालवू शकता:
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
 
-```sh
-डॉकर पुल ग्राफप्रोटोकॉल/ग्राफ-नोड:नवीनतम
-```
+You can also use `graph add` command to add a new dataSource.
 
-**सूचना:** डॉकर/डॉकर-कंपोज तुम्ही पहिल्यांदा चालवताना जी ग्राफ-नोड आवृत्ती काढली होती ती नेहमी वापरेल, त्यामुळे तुम्ही नवीनतम आवृत्तीसह अद्ययावत आहात याची खात्री करण्यासाठी हे करणे महत्त्वाचे आहे. ग्राफ-नोडचे.
+### 12. In what order are the event, block, and call handlers triggered for a data source?
 
-## 9. मी माझ्या सबग्राफ मॅपिंगमधून कॉन्ट्रॅक्ट फंक्शन कसे कॉल करू किंवा सार्वजनिक स्टेट व्हेरिएबलमध्ये प्रवेश कसा करू?
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
 
-Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
 
-## 10. दोन करारांसह `graph-cli` वरून `graph init` वापरून सबग्राफ सेट करणे शक्य आहे का? किंवा `graph init` चालवल्यानंतर `subgraph.yaml` मध्ये मी व्यक्तिचलितपणे दुसरा डेटासोर्स जोडायचा?
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
 
-Yes. On `graph init` command itself you can add multiple datasources by entering contracts one after the other. You can also use `graph add` command to add new datasource.
+तुम्ही खालील आदेश चालवू शकता:
 
-## 11. मला GitHub समस्या योगदान किंवा जोडायचे आहे. मी ओपन सोर्स रिपॉजिटरीज कुठे शोधू शकतो?
+```sh
+डॉकर पुल ग्राफप्रोटोकॉल/ग्राफ-नोड:नवीनतम
+```
 
-- [आलेख नोड](https://github.com/graphprotocol/graph-node)
-- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
-- [graph-docs](https://github.com/graphprotocol/docs)
-- [graph-client](https://github.com/graphprotocol/graph-client)
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
 
-## 12. इव्हेंट हाताळताना एखाद्या घटकासाठी "स्वयंजनित" आयडी तयार करण्याचा शिफारस केलेला मार्ग कोणता आहे?
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
 
 कार्यक्रमादरम्यान फक्त एकच अस्तित्व तयार केले असल्यास आणि त्यापेक्षा चांगले काही उपलब्ध नसल्यास, व्यवहार हॅश + लॉग इंडेक्स अद्वितीय असेल. तुम्ही ते बाइट्समध्ये रूपांतरित करून आणि नंतर `crypto.keccak256` द्वारे पाइपिंग करून त्यांना अस्पष्ट करू शकता परंतु यामुळे ते अधिक अद्वितीय होणार नाही.
 
-## 13. एकाधिक करार ऐकताना, कार्यक्रम ऐकण्यासाठी कॉन्ट्रॅक्ट ऑर्डर निवडणे शक्य आहे का?
+### 15. Can I delete my subgraph?
 
-सबग्राफमध्‍ये, इव्‍हेंट नेहमी ब्लॉकमध्‍ये दिसण्‍याच्‍या क्रमाने संसाधित केले जातात, ते एकाधिक कॉन्ट्रॅक्टमध्‍ये असले किंवा नसले तरीही.
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
 
-## 14. Is it possible to differentiate between networks (mainnet, Sepolia, local) from within event handlers?
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+तुम्ही समर्थित नेटवर्कची सूची [येथे](/developing/supported-networks) शोधू शकता.
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
 
 होय. तुम्ही खालील उदाहरणानुसार `graph-ts` इंपोर्ट करून हे करू शकता:
 
@@ -78,23 +99,21 @@ dataSource.network()
 dataSource.address()
 ```
 
-## 15. Do you support block and call handlers on Sepolia?
+### 18. Do you support block and call handlers on Sepolia?
 
 Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
 
-## 16. मी माझ्या सबग्राफ मॅपिंगमध्ये ethers.js किंवा इतर JS लायब्ररी आयात करू शकतो का?
-
-असेंब्लीस्क्रिप्टमध्ये मॅपिंग लिहिल्याप्रमाणे सध्या नाही. यावर एक संभाव्य पर्यायी उपाय म्हणजे घटकांमध्ये कच्चा डेटा संग्रहित करणे आणि क्लायंटवर JS लायब्ररी आवश्यक असलेले तर्क करणे.
+## Indexing & Querying Related
 
-## 17. कोणत्या ब्लॉकवर अनुक्रमणिका सुरू करायची हे निर्दिष्ट करणे शक्य आहे का?
+### 19. Is it possible to specify what block to start indexing on?
 
-Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 18. इंडेक्सिंगची कार्यक्षमता वाढवण्यासाठी काही टिपा आहेत का? माझा सबग्राफ समक्रमित होण्यासाठी खूप वेळ घेत आहे
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
 
-होय, कॉन्ट्रॅक्ट तैनात केलेल्या ब्लॉकमधून अनुक्रमणिका सुरू करण्यासाठी तुम्ही पर्यायी स्टार्ट ब्लॉक वैशिष्ट्यावर एक नजर टाकली पाहिजे: [स्टार्ट ब्लॉक्स](/developing/creating-a-subgraph#start-blocks)
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
 
-## 19. सबग्राफला अनुक्रमित केलेला नवीनतम ब्लॉक क्रमांक निश्चित करण्यासाठी थेट क्वेरी करण्याचा कोणताही मार्ग आहे का?
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
 
 होय! खालील आदेश वापरून पहा, "संस्था/सबग्राफनेम" च्या जागी त्याखालील संस्था प्रकाशित झाली आहे आणि तुमच्या सबग्राफचे नाव:
 
@@ -102,44 +121,27 @@ Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the n
 curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { साखळी { नवीनतम ब्लॉक { hash number }}}"}' https://api.thegraph.com/ index-node/graphql
 ```
 
-## 20. ग्राफद्वारे कोणते नेटवर्क समर्थित आहेत?
-
-तुम्ही समर्थित नेटवर्कची सूची [येथे](/developing/supported-networks) शोधू शकता.
-
-## 21. पुनर्नियोजन न करता उपग्राफ दुसर्‍या खात्यावर किंवा एंडपॉइंटवर डुप्लिकेट करणे शक्य आहे का?
-
-तुम्हाला सबग्राफ पुन्हा तैनात करावा लागेल, परंतु सबग्राफ आयडी (IPFS हॅश) बदलत नसल्यास, त्याला सुरुवातीपासून सिंक करण्याची गरज नाही.
-
-## 22. ग्राफ-नोडच्या शीर्षस्थानी अपोलो फेडरेशन वापरणे शक्य आहे का?
+### 22. Is there a limit to how many objects The Graph can return per query?
 
-फेडरेशन अद्याप समर्थित नाही, जरी आम्हाला भविष्यात समर्थन करायचे आहे. याक्षणी, तुम्ही क्लायंटवर किंवा प्रॉक्सी सेवेद्वारे, स्कीमा स्टिचिंग वापरू शकता.
-
-## 23. प्रत्येक क्वेरीमध्ये आलेख किती वस्तू परत करू शकतो याची मर्यादा आहे का?
-
-डीफॉल्टनुसार, क्वेरी प्रतिसाद प्रति संग्रह 100 आयटमपर्यंत मर्यादित आहेत. तुम्हाला अधिक प्राप्त करायचे असल्यास, तुम्ही प्रति संग्रह 1000 आयटमपर्यंत जाऊ शकता आणि त्यापलीकडे तुम्ही यासह पृष्ठांकन करू शकता:
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
 
 ```graphql
 काही संकलन(प्रथम: 1000, वगळा: <संख्या>) { ... }
 ```
 
-## 24. जर माझे dapp फ्रंटएंड क्वेरींगसाठी आलेख वापरत असेल, तर मला माझी क्वेरी की थेट फ्रंटएंडमध्ये लिहावी लागेल का? आम्ही वापरकर्त्यांसाठी क्वेरी शुल्क भरल्यास काय - दुर्भावनापूर्ण वापरकर्त्यांमुळे आमच्या क्वेरी शुल्क खूप जास्त असेल?
-
-सध्या, dapp साठी शिफारस केलेला दृष्टीकोन म्हणजे फ्रंटएंडमध्ये की जोडणे आणि अंतिम वापरकर्त्यांसमोर ते उघड करणे. ते म्हणाले, तुम्ही ती की होस्टनावावर मर्यादित करू शकता, जसे की _yourdapp.io_ आणि सबग्राफ. गेटवे सध्या एज द्वारे चालवले जात आहे & नोड. गेटवेच्या जबाबदारीचा एक भाग म्हणजे अपमानास्पद वर्तनासाठी निरीक्षण करणे आणि दुर्भावनापूर्ण क्लायंटकडून रहदारी अवरोधित करणे.
-
-## 25. Where do I go to find my current subgraph on the hosted service?
-
-Head over to the hosted service in order to find subgraphs that you or others deployed to the hosted service. You can find it [here](https://thegraph.com/hosted-service).
-
-## 26. Will the hosted service start charging query fees?
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
 
-The Graph will never charge for the hosted service. The Graph is a decentralized protocol, and charging for a centralized service is not aligned with The Graph’s values. The hosted service was always a temporary step to help get to the decentralized network. Developers will have a sufficient amount of time to upgrade to the decentralized network as they are comfortable.
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
 
-## 27. How do I update a subgraph on mainnet?
+## Miscellaneous
 
-If you’re a subgraph developer, you can deploy a new version of your subgraph to Subgraph Studio using the CLI. It’ll be private at that point, but if you’re happy with it, you can publish to the decentralized Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+### 24. Is it possible to use Apollo Federation on top of graph-node?
 
-## 28. In what order are the event, block, and call handlers triggered for a data source?
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
 
-Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
 
-When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+- [आलेख नोड](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 7208cc6ce7c569bf72bf73e1a39c98a83c3daca1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:52 -0500
Subject: [PATCH 0109/1325] New translations developer-faqs.mdx (Swahili)

---
 .../pages/sw/developing/developer-faqs.mdx    | 147 ++++++++++++++++++
 1 file changed, 147 insertions(+)
 create mode 100644 website/pages/sw/developing/developer-faqs.mdx

diff --git a/website/pages/sw/developing/developer-faqs.mdx b/website/pages/sw/developing/developer-faqs.mdx
new file mode 100644
index 000000000000..244aae52d0f4
--- /dev/null
+++ b/website/pages/sw/developing/developer-faqs.mdx
@@ -0,0 +1,147 @@
+---
+title: Developer FAQs
+---
+
+This page summarizes some of the most common questions for developers building on The Graph.
+
+## Subgraph Related
+
+### 1. What is a subgraph?
+
+A subgraph is a custom API built on blockchain data. Subgraphs are queried using the GraphQL query language and are deployed to a Graph Node using The Graph CLI. Once deployed and published to The Graph's decentralized network, Indexers process subgraphs and make them available for subgraph consumers to query.
+
+### 2. What is the first step to create a subgraph?
+
+To successfully create a subgraph, you will need to install The Graph CLI. Review the [Quick Start](/quick-start/) to get started. For detailed information, see [Creating a Subgraph](/developing/creating-a-subgraph/).
+
+### 3. Can I still create a subgraph if my smart contracts don't have events?
+
+It is highly recommended that you structure your smart contracts to have events associated with data you are interested in querying. Event handlers in the subgraph are triggered by contract events and are the fastest way to retrieve useful data.
+
+If the contracts you work with do not contain events, your subgraph can use call and block handlers to trigger indexing. However, this is not recommended, as performance will be significantly slower.
+
+### 4. Can I change the GitHub account associated with my subgraph?
+
+No. Once a subgraph is created, the associated GitHub account cannot be changed. Please make sure to carefully consider this before creating your subgraph.
+
+### 5. How do I update a subgraph on mainnet?
+
+You can deploy a new version of your subgraph to Subgraph Studio using the CLI. This action maintains your subgraph private, but once you’re happy with it, you can publish to Graph Explorer. This will create a new version of your subgraph that Curators can start signaling on.
+
+### 6. Is it possible to duplicate a subgraph to another account or endpoint without redeploying?
+
+You have to redeploy the subgraph, but if the subgraph ID (IPFS hash) doesn't change, it won't have to sync from the beginning.
+
+### 7. How do I call a contract function or access a public state variable from my subgraph mappings?
+
+Take a look at `Access to smart contract` state inside the section [AssemblyScript API](/developing/graph-ts/api/#access-to-smart-contract-state).
+
+### 8. Can I import `ethers.js` or other JS libraries into my subgraph mappings?
+
+Not currently, as mappings are written in AssemblyScript.
+
+One possible alternative solution to this is to store raw data in entities and perform logic that requires JS libraries on the client.
+
+### 9. When listening to multiple contracts, is it possible to select the contract order to listen to events?
+
+Within a subgraph, the events are always processed in the order they appear in the blocks, regardless of whether that is across multiple contracts or not.
+
+### 10. How are templates different from data sources?
+
+Templates allow you to create data sources quickly, while your subgraph is indexing. Your contract might spawn new contracts as people interact with it. Since you know the shape of those contracts (ABI, events, etc.) upfront, you can define how you want to index them in a template. When they are spawned, your subgraph will create a dynamic data source by supplying the contract address.
+
+Check out the "Instantiating a data source template" section on: [Data Source Templates](/developing/creating-a-subgraph#data-source-templates).
+
+### 11. Is it possible to set up a subgraph using `graph init` from `graph-cli` with two contracts? Or should I manually add another dataSource in `subgraph.yaml` after running `graph init`?
+
+Yes. On `graph init` command itself you can add multiple dataSources by entering contracts one after the other.
+
+You can also use `graph add` command to add a new dataSource.
+
+### 12. In what order are the event, block, and call handlers triggered for a data source?
+
+Event and call handlers are first ordered by transaction index within the block. Event and call handlers within the same transaction are ordered using a convention: event handlers first then call handlers, each type respecting the order they are defined in the manifest. Block handlers are run after event and call handlers, in the order they are defined in the manifest. Also these ordering rules are subject to change.
+
+When new dynamic data source are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+### 13. How do I make sure I'm using the latest version of graph-node for my local deployments?
+
+You can run the following command:
+
+```sh
+docker pull graphprotocol/graph-node:latest
+```
+
+> Note: docker / docker-compose will always use whatever graph-node version was pulled the first time you ran it, so make sure you're up to date with the latest version of graph-node.
+
+### 14. What is the recommended way to build "autogenerated" ids for an entity when handling events?
+
+If only one entity is created during the event and if there's nothing better available, then the transaction hash + log index would be unique. You can obfuscate these by converting that to Bytes and then piping it through `crypto.keccak256` but this won't make it more unique.
+
+### 15. Can I delete my subgraph?
+
+Yes, you can [delete](/managing/delete-a-subgraph/) and [transfer](/managing/transfer-a-subgraph/) your subgraph.
+
+## Network Related
+
+### 16. What networks are supported by The Graph?
+
+You can find the list of the supported networks [here](/developing/supported-networks).
+
+### 17. Is it possible to differentiate between networks (mainnet, Sepolia, local) within event handlers?
+
+Yes. You can do this by importing `graph-ts` as per the example below:
+
+```javascript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+dataSource.network()
+dataSource.address()
+```
+
+### 18. Do you support block and call handlers on Sepolia?
+
+Yes. Sepolia supports block handlers, call handlers and event handlers. It should be noted that event handlers are far more performant than the other two handlers, and they are supported on every EVM-compatible network.
+
+## Indexing & Querying Related
+
+### 19. Is it possible to specify what block to start indexing on?
+
+Yes. `dataSources.source.startBlock` in the `subgraph.yaml` file specifies the number of the block that the dataSource starts indexing from. In most cases, we suggest using the block where the contract was created: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+
+### 20. What are some tips to increase the performance of indexing? My subgraph is taking a very long time to sync
+
+Yes, you should take a look at the optional start block feature to start indexing from the block where the contract was deployed: [Start blocks](/developing/creating-a-subgraph#start-blocks)
+
+### 21. Is there a way to query the subgraph directly to determine the latest block number it has indexed?
+
+Yes! Try the following command, substituting "organization/subgraphName" with the organization under it is published and the name of your subgraph:
+
+```sh
+curl -X POST -d '{ "query": "{indexingStatusForCurrentVersion(subgraphName: \"organization/subgraphName\") { chains { latestBlock { hash number }}}}"}' https://api.thegraph.com/index-node/graphql
+```
+
+### 22. Is there a limit to how many objects The Graph can return per query?
+
+By default, query responses are limited to 100 items per collection. If you want to receive more, you can go up to 1000 items per collection and beyond that, you can paginate with:
+
+```graphql
+someCollection(first: 1000, skip: <number>) { ... }
+```
+
+### 23. If my dapp frontend uses The Graph for querying, do I need to write my API key into the frontend directly? What if we pay query fees for users – will malicious users cause our query fees to be very high?
+
+Currently, the recommended approach for a dapp is to add the key to the frontend and expose it to end users. That said, you can limit that key to a hostname, like _yourdapp.io_ and subgraph. The gateway is currently being run by Edge & Node. Part of the responsibility of a gateway is to monitor for abusive behavior and block traffic from malicious clients.
+
+## Miscellaneous
+
+### 24. Is it possible to use Apollo Federation on top of graph-node?
+
+Federation is not supported yet. At the moment, you can use schema stitching, either on the client or via a proxy service.
+
+### 25. I want to contribute or add a GitHub issue. Where can I find the open source repositories?
+
+- [graph-node](https://github.com/graphprotocol/graph-node)
+- [graph-tooling](https://github.com/graphprotocol/graph-tooling)
+- [graph-docs](https://github.com/graphprotocol/docs)
+- [graph-client](https://github.com/graphprotocol/graph-client)

From 08062303c8be6ff4125ab900e38ce0c04a1a3ed5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:53 -0500
Subject: [PATCH 0110/1325] New translations about.mdx (Romanian)

---
 website/pages/ro/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/ro/about.mdx b/website/pages/ro/about.mdx
index 8828bb922110..ad19563a31d2 100644
--- a/website/pages/ro/about.mdx
+++ b/website/pages/ro/about.mdx
@@ -2,46 +2,66 @@
 title: Despre The Graph
 ---
 
-This page will explain what The Graph is and how you can get started.
-
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Projects with complex smart contracts like [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it really difficult to read anything other than basic data directly from the blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+### How The Graph Functions
 
-**Indexing blockchain data is really, really hard.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## How The Graph Works
+- 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.
 
-The Graph learns what and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph description defines the smart contracts of interest for a subgraph, the events in those contracts to pay attention to, and how to map event data to data that The Graph will store in its database.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Once you have written a `subgraph manifest`, you use the Graph CLI to store the definition in IPFS and tell the indexer to start indexing data for that subgraph.
+- 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+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.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From cf089189f496b1b1652d5d33c1fe9cbd03c05f97 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:54 -0500
Subject: [PATCH 0111/1325] New translations near.mdx (Romanian)

---
 website/pages/ro/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ro/cookbook/near.mdx b/website/pages/ro/cookbook/near.mdx
index a4f27caf6f3c..f2509e44e84c 100644
--- a/website/pages/ro/cookbook/near.mdx
+++ b/website/pages/ro/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 9c8c4357099291dda4d7b8b48762cb8228186456 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:55 -0500
Subject: [PATCH 0112/1325] New translations unit-testing-framework.mdx
 (Romanian)

---
 .../ro/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/ro/developing/unit-testing-framework.mdx b/website/pages/ro/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/ro/developing/unit-testing-framework.mdx
+++ b/website/pages/ro/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 2defad18196eab6b21c4f6d8c6065513ce281e4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:57 -0500
Subject: [PATCH 0113/1325] New translations about.mdx (French)

---
 website/pages/fr/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/fr/about.mdx b/website/pages/fr/about.mdx
index ded4167cf102..36904a652bd4 100644
--- a/website/pages/fr/about.mdx
+++ b/website/pages/fr/about.mdx
@@ -2,46 +2,66 @@
 title: À propos de The Graph
 ---
 
-Cette page expliquera ce qu'est The Graph et comment vous pouvez commencer.
-
 ## Qu’est-ce que The Graph ?
 
-The Graph est un protocole décentralisé pour l'indexation et l'interrogation de données blockchain. The Graph permet d'interroger des données qui sont difficiles à interroger directement.
+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.
+
+## Comprendre les fondamentaux
+
+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.
+
+### Défis sans The Graph⁠
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Pourquoi est-ce un problème ?
+
+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.
+
+Une alternative serait de configurer votre propre serveur, de traiter les transactions, de les stocker dans une base de données et de créer une API pour interroger les données. Cependant, cette solution est [coûteuse en ressources](/network/benefits/), nécessite une maintenance constante, présente un point de défaillance unique et compromet d'importantes propriétés de securité essentiels à la décentralisation.
+
+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.
 
-Les projets avec des contrats intelligents complexes comme [Uniswap](https://uniswap.org/) et des projets NFT comme [Bored Ape](https://boredapeyachtclub.com/) Yacht Club stockent des données sur la blockchain Ethereum. La façon dont ces données sont stockées rend leur lecture difficile au-delà de quelques informations simples.
+## The Graph apporte une solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+The Graph répond à ce défi grâce à un protocole décentralisé qui indexe les données de la blockchain et permet de les interroger de manière efficace et performantes. Ces API (appelées "subgraphs" indexés) peuvent ensuite être interrogées via une API standard GraphQL.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-Vous pouvez également créer votre propre serveur, y traiter les transactions, les enregistrer dans une base de données et créer un point de terminaison d'API par-dessus tout cela afin d'interroger les données. Cependant, cette option est [consommatrice de ressources](/network/benefits/), nécessite une maintenance, présente un point de défaillance unique et brise d'importantes propriétés de sécurité requises pour la décentralisation.
+### Comment fonctionne The Graph⁠
 
-**L’indexation des données blockchain est vraiment très difficile.**
+Indexer les données de la blockchain est une tâche complexe, mais The Graph la simplifie. Il apprend à indexer les données d'Ethereum en utilisant des subgraphs. Les subgraphs sont des API personnalisées construites sur les données de la blockchain qui extraient, traitent et stockent ces données pour qu'elles puissent être interrogées facilement via GraphQL.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Spécificités⁠
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph utilise des descriptions de subgraph, qui sont connues sous le nom de "manifeste de subgraph" à l'intérieur du subgraph.
 
-## Fonctionnement du Graph
+- Ce manifeste définit les contrats intelligents intéressants pour un subgraph, les événements spécifiques à surveiller au sein de ces contrats, et la manière de mapper les données de ces événements aux données que The Graph stockera dans sa base de données.
 
-The Graph apprend quoi et comment indexer les données Ethereum en fonction des descriptions de subgraphs, connues sous le nom de manifeste de subgraph. La description du subgraph définit les contrats intelligents d'intérêt pour un subgraph, les événements de ces contrats auxquels il faut prêter attention et comment mapper les données d'événement aux données que The Graph stockera dans sa base de données.
+- Lors de la création d'un subgraph, vous devez rédiger ce manifeste.
 
-Une fois que vous avez écrit un `manifeste de subgraph`, vous utilisez le Graph CLI pour stocker la définition dans IPFS et vous indiquez par la même occasion à l'indexeur de commencer à indexer les données pour ce subgraph.
+- Une fois le `manifeste du subgraph` écrit, vous pouvez utiliser l'outil en ligne de commande Graph CLI pour stocker la définition en IPFS et demander à un Indexeur de commencer à indexer les données pour ce subgraph.
 
-Ce diagramme donne plus de détails sur le flux de données une fois qu'un manifeste de subgraph a été déployé, traitant des transactions Ethereum :
+Le schéma ci-dessous illustre plus en détail le flux de données après le déploiement d'un manifeste de subgraph avec des transactions Ethereum.
 
 ![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. Parallèlement, Le nœud de The Graph scanne continuellement Ethereum à la recherche de nouveaux blocs et de nouvelles données intéressantes pour votre subgraph.
-4. The Graph Node trouve alors les événements Ethereum d'intérêt pour votre subgraph dans ces blocs et vient exécuter les corrélations correspondantes que vous avez fournies. Le gestionnaire de corrélation se définit comme un module WASM qui crée ou met à jour les entités de données que le nœud de The Graph stocke en réponse aux événements Ethereum.
-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.
+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.  Parallèlement, Le nœud de The Graph scanne continuellement Ethereum à la recherche de nouveaux blocs et de nouvelles données intéressantes pour votre subgraph.
+4.  The Graph Node trouve alors les événements Ethereum d'intérêt pour votre subgraph dans ces blocs et vient exécuter les corrélations correspondantes que vous avez fournies. Le gestionnaire de corrélation se définit comme un module WASM qui crée ou met à jour les entités de données que le nœud de The Graph stocke en réponse aux événements Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+Les sections suivantes proposent une exploration plus approfondie des subgraphs, de leur déploiement et de la manière d'interroger les données.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+Avant de créer votre propre subgraph, il est conseillé de visiter Graph Explorer et d'examiner certains des subgraphs déjà déployés. Chaque page de subgraph comprend un playground (un espace de test) GraphQL, vous permettant d'interroger ses données.

From 0fc43bfa24d15f2cc32da29033be1dfb1f034af4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:58 -0500
Subject: [PATCH 0114/1325] New translations near.mdx (French)

---
 website/pages/fr/cookbook/near.mdx | 62 +++++++++++++++---------------
 1 file changed, 31 insertions(+), 31 deletions(-)

diff --git a/website/pages/fr/cookbook/near.mdx b/website/pages/fr/cookbook/near.mdx
index 4296699b5744..e922801be61e 100644
--- a/website/pages/fr/cookbook/near.mdx
+++ b/website/pages/fr/cookbook/near.mdx
@@ -37,7 +37,7 @@ La définition d'un subgraph comporte trois aspects :
 
 **schema.graphql** : un fichier de schéma qui définit quelles données sont stockées pour votre subgraph, et comment les interroger via GraphQL. Les exigences pour les subgraphs NEAR sont couvertes par la [documentation existante](/developing/creating-a-subgraph#the-graphql-schema).
 
-**Mappages AssemblyScript :** [Code AssemblyScript](/developing/graph-ts/api) qui traduit les données d'événement en entités définies dans votre schéma. La prise en charge de NEAR introduit des types de données spécifiques à NEAR et une nouvelle fonctionnalité d'analyse JSON.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 Lors du développement du subgraph, il y a deux commandes clés :
 
@@ -51,23 +51,23 @@ $ graph build # génère le Web Assembly à partir des fichiers AssemblyScript,
 Le manifeste de subgraph (`subgraph.yaml`) identifie les sources de données pour le subgraph, les déclencheurs d'intérêt et les fonctions qui doivent être exécutées en réponse à ces déclencheurs. Voici un exemple de manifeste de subgraph pour un subgraph NEAR:
 
 ```yaml
-specVersion: 0.0.2
-schema:
-  file: ./src/schema.graphql # lien vers le fichier de schéma
-dataSources:
-  - kind: near
-    network: near-mainnet
-    source:
-      account: app.good-morning.near # Cette source de données surveillera ce compte
-      startBlock: 10662188 # Requis pour NEAR
-    mapping:
-      apiVersion: 0.0.5
-      language: wasm/assemblyscript
-      blockHandlers:
-        - handler: handleNewBlock # le nom de la fonction dans le fichier de mapping
-      receiptHandlers:
-        - handler: handleReceipt # le nom de la fonction dans le fichier de mappage
-      file: ./src/mapping.ts # lien vers le fichier contenant les mappings Assemblyscript
+specVersion : 0.0.2
+schema :
+  file : ./src/schema.graphql # lien vers le fichier de schéma
+dataSources :
+  - kind : near
+    network : near-mainnet
+    source :
+      account : app.good-morning.near # Cette source de données surveillera ce compte
+      startBlock : 10662188 # Requis pour NEAR
+    mapping :
+      apiVersion : 0.0.5
+      language : wasm/assemblyscript
+      blockHandlers :
+        - handler : handleNewBlock # le nom de la fonction dans le fichier de mapping
+      receiptHandlers :
+        - handler : handleReceipt # le nom de la fonction dans le fichier de mappage
+      file : ./src/mapping.ts # lien vers le fichier contenant les mappings Assemblyscript
 ```
 
 - Les subgraphs NEAR introduisent un nouveau `type` de source de données (`near`)
@@ -77,12 +77,12 @@ dataSources:
 
 ```yaml
 comptes:
-  préfixes:
-    - application
-    - bien
-  suffixes:
-    - matin.près
-    - matin.testnet
+   préfixes :
+     - application
+     - bien
+   suffixes :
+     - matin.près
+     - matin.testnet
 ```
 
 Les fichiers de données NEAR prennent en charge deux types de gestionnaires :
@@ -98,7 +98,7 @@ La définition du schema décrit la structure de la base de données de subgraph
 
 Les gestionnaires de traitement des événements sont écrits dans l'[AssemblyScript](https://www.assemblyscript.org/).
 
-L'indexation NEAR introduit des types de données spécifiques à NEAR dans l'[API AssemblyScript](/developing/graph-ts/api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ Ces types sont passés au bloc & gestionnaires de reçus :
 - Les gestionnaires de blocs reçoivent un `Block`
 - Les gestionnaires de reçus reçoivent un `ReceiptWithOutcome`
 
-Sinon, le reste de l'[API AssemblyScript](/developing/graph-ts/api) est disponible pour les développeurs de subgraphs NEAR pendant l'exécution du mapping.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-Cela inclut une nouvelle fonction d'analyse JSON - les journaux sur NEAR sont fréquemment émis sous forme de JSON stringifiés. Une nouvelle fonction `json.fromString(...)` est disponible dans le cadre de l'[API JSON](/developing/graph-ts/api#json-api) pour permettre aux développeurs pour traiter facilement ces journaux.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## Déploiement d'un subgraph NEAR
 
@@ -194,8 +194,8 @@ La configuration du nœud dépend de l'endroit où le subgraph est déployé.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Nœud Graph local ( en fonction de la configuration par défaut)
@@ -258,8 +258,8 @@ Si un `compte` est spécifié, il correspondra uniquement au nom exact du compte
 
 ```yaml
 comptes:
-  suffixes:
-    - mintbase1.near
+   suffixes :
+     - mintbase1.near
 ```
 
 ### Les subgraphs NEAR peuvent-ils faire des appels de view aux comptes NEAR pendant les mappings?

From 79ddbb8c0dfba9da8b89da3828f43409d14b3a51 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:32:59 -0500
Subject: [PATCH 0115/1325] New translations unit-testing-framework.mdx
 (French)

---
 .../fr/developing/unit-testing-framework.mdx  | 212 +++++++++---------
 1 file changed, 106 insertions(+), 106 deletions(-)

diff --git a/website/pages/fr/developing/unit-testing-framework.mdx b/website/pages/fr/developing/unit-testing-framework.mdx
index efd4a4ae780d..b0ec41e8b131 100644
--- a/website/pages/fr/developing/unit-testing-framework.mdx
+++ b/website/pages/fr/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Cadre pour les tests unitaires
 ---
 
-Matchstick est un cadre de test unitaire, développé par [LimeChain](https://limechain.tech/), qui permet aux développeurs de subgraphs de tester leur logique de cartographie dans un environnement de type bac à sable et de déployer leurs subgraphs en toute confiance !
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Démarrage
 
-### Installer les dépendances
+### Install Dependencies
 
-Pour utiliser les méthodes d'assistance aux tests et exécuter les tests, vous devrez installer les dépendances suivantes :
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` dépend de PostgreSQL, donc si vous ne l'avez pas déjà, vous devrez l'installer. Nous vous conseillons vivement d'utiliser les commandes ci-dessous, car l'ajouter d'une autre manière peut provoquer des erreurs inattendues !
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
 
-#### Le MacOS
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-Commande d'installation Postgres :
+#### Using MacOS
+
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Créez un lien symbolique vers la dernière libpq.5.lib _Vous devrez peut-être
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Commande d'installation de Postgres (dépend de votre distribution) :
+Installation command (depends on your distro):
 
 ```sh
 sudo apt installer postgresql
 ```
 
-### WSL (Système Windows pour Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 Vous pouvez utiliser Matchstick sur WSL en utilisant à la fois l'approche Docker et l'approche binaire. Comme WSL peut être un peu délicat, voici quelques conseils au cas où vous rencontreriez des problèmes tels que
 
@@ -76,7 +85,7 @@ Et en conclussion, n'utilisez pas `graph test` (qui utilise votre installation g
 }
 ```
 
-### Usage
+### Using Matchstick
 
 Pour utiliser **Matchstick** dans votre projet de subgraph, il suffit d'ouvrir un terminal, de naviguer vers le dossier racine de votre projet et d'exécuter simplement `graph test [options] <datasource>` - il télécharge le dernier binaire **Matchstick** et exécute le test spécifié ou tous les tests dans un dossier de test (ou tous les tests existants si aucun datasource flag n'est spécifié).
 
@@ -116,7 +125,7 @@ graph test path/to/file.test.ts
 
 À partir de `graph-cli 0.25.2`, la commande `graph test` prend en charge l'exécution de `matchstick` dans un conteneur Docker avec le `-d</0. > drapeau. L'implémentation de Docker utilise <a href="https://docs.docker.com/storage/bind-mounts/">bind mount</a> afin de ne pas avoir à reconstruire l'image Docker à chaque fois que la commande <code>graph test -d` est exécutée. Vous pouvez également suivre les instructions du référentiel [matchstick](https://github.com/LimeChain/matchstick#docker-) pour exécuter Docker manuellement.
 
-❗ `graph test -d` forces `docker run` to run with flag `-t`. This must be removed to run inside non-interactive environments (like GitHub CI).
+❗ `graph test -d` force `docker run` à s'exécuter avec le paramètre `-t`. Cela doit être supprimé pour s'exécuter dans des environnements non interactifs (comme GitHub CI).
 
 ❗ En cas d'exécution préalable de `graph test`, vous risquez de rencontrer l'erreur suivante lors de la construction de docker :
 
@@ -144,9 +153,9 @@ Vous pouvez tester et jouer avec les exemples de ce guide en clonant le repo [De
 
 Vous pouvez également consulter la série de vidéos sur [« comment utiliser Matchstick pour écrire des tests unitaires pour vos subgraphs »](https://www.youtube.com/playlist?list=PLTqyKgxaGF3SNakGQwczpSGVjS_xvOv3h)
 
-## Tests structure
+## Structure des tests
 
-_**IMPORTANT: The test structure described below depens on `matchstick-as` version >=0.5.0**_
+_**IMPORTANT: La structure de test décrite ci-dessous dépend de la version `matchstick-as` version >=0.5.0**_
 
 ### décrivez()
 
@@ -524,33 +533,33 @@ assertNotNull<T>(value: T)
 entityCount(entityType: string, expectedCount: i32)
 ```
 
-As of version 0.6.0, asserts support custom error messages as well
+À partir de la version 0.6.0, les assertions supportent également les messages d'erreur personnalisés
 
 ```typescript
-assert.fieldEquals('Gravatar', '0x123', 'id', '0x123', 'Id should be 0x123')
-assert.equals(ethereum.Value.fromI32(1), ethereum.Value.fromI32(1), 'Value should equal 1')
-assert.notInStore('Gravatar', '0x124', 'Gravatar should not be in store')
-assert.addressEquals(Address.zero(), Address.zero(), 'Address should be zero')
-assert.bytesEquals(Bytes.fromUTF8('0x123'), Bytes.fromUTF8('0x123'), 'Bytes should be equal')
-assert.i32Equals(2, 2, 'I32 should equal 2')
-assert.bigIntEquals(BigInt.fromI32(1), BigInt.fromI32(1), 'BigInt should equal 1')
-assert.booleanEquals(true, true, 'Boolean should be true')
-assert.stringEquals('1', '1', 'String should equal 1')
-assert.arrayEquals([ethereum.Value.fromI32(1)], [ethereum.Value.fromI32(1)], 'Arrays should be equal')
+assert.fieldEquals('Gravatar', '0x123', 'id', '0x123', 'L'Id doit être 0x123')
+assert.equals(ethereum.Value.fromI32(1), ethereum.Value.fromI32(1), 'La valeur doit être égale à 1')
+assert.notInStore('Gravatar', '0x124', 'Gravatar ne doit pas être dans le magasin')
+assert.addressEquals(Address.zero(), Address.zero(), 'L'adresse doit être zéro')
+assert.bytesEquals(Bytes.fromUTF8('0x123'), Bytes.fromUTF8('0x123'), 'Les Bytes doivent être égaux')
+assert.i32Equals(2, 2, 'I32 doit être égal à 2')
+assert.bigIntEquals(BigInt.fromI32(1), BigInt.fromI32(1), 'BigInt doit être égal à 1')
+assert.booleanEquals(true, true, 'Le booléen doit être vrai')
+assert.stringEquals('1', '1', 'La chaîne de caractère doit être égale à 1')
+assert.arrayEquals([ethereum.Value.fromI32(1)], [ethereum.Value.fromI32(1)], 'Les tableaux doivent être égaux')
 assert.tupleEquals(
   changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
   changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
-  'Tuples should be equal',
+  'Les tuples doivent être égaux',
 )
-assert.assertTrue(true, 'Should be true')
-assert.assertNull(null, 'Should be null')
-assert.assertNotNull('not null', 'Should be not null')
-assert.entityCount('Gravatar', 1, 'There should be 2 gravatars')
-assert.dataSourceCount('GraphTokenLockWallet', 1, 'GraphTokenLockWallet template should have one data source')
+assert.assertTrue(true, 'Doit être vrai')
+assert.assertNull(null, 'Doit être nul')
+assert.assertNotNull('pas nul', 'Ne doit pas être nul')
+assert.entityCount('Gravatar', 1, 'Il devrait y avoir 2 gravatars')
+assert.dataSourceCount('GraphTokenLockWallet', 1, 'Le modèle(template) GraphTokenLockWallet doit avoir une source de données')
 assert.dataSourceExists(
   'GraphTokenLockWallet',
   Address.zero().toHexString(),
-  'GraphTokenLockWallet should have a data source for zero address',
+  'GraphTokenLockWallet doit avoir une source de données pour l'adresse zéro',
 )
 ```
 
@@ -877,7 +886,7 @@ Les utilisateurs peuvent affirmer qu'une entité n'existe pas dans le magasin. L
 assert.notInStore('Gravatar', '23')
 ```
 
-### Printing the whole store, or single entities from it (for debug purposes)
+### Affichage de tout le magasin ou d'entités individuelles (à des fins de débogage)
 
 Vous pouvez imprimer l'intégralité du magasin sur la console à l'aide de cette fonction d'assistance:
 
@@ -887,7 +896,7 @@ import { logStore } from 'matchstick-as/assembly/store'
 logStore()
 ```
 
-As of version 0.6.0, `logStore` no longer prints derived fields, instead users can use the new `logEntity` function. Of course `logEntity` can be used to print any entity, not just ones that have derived fields. `logEntity` takes the entity type, entity id and a `showRelated` flag to indicate if users want to print the related derived entities.
+À partir de la version 0.6.0, `logStore` n'affiche plus les champs dérivés, les utilisateurs peuvent utiliser la nouvelle fonction `logEntity`. Bien sûr, `logEntity` peut être utilisé pour afficher n'importe quelle entité, pas seulement celles qui ont des champs dérivés. `logEntity` prend le type d'entité, l'Id de l'entité et un paramètre `showRelated` pour indiquer si les utilisateurs veulent afficher les entités dérivées liées.
 
 ```
 import { logEntity } from 'matchstick-as/assembly/store'
@@ -941,7 +950,7 @@ Les utilisateurs peuvent également simuler une panne critique, comme ceci :
 
 ```typescript
 test('Tout faire exploser', () => {
-  log.critical('Boom!')
+   log.critical('Boom!')
 })
 ```
 
@@ -949,16 +958,16 @@ La journalisation des erreurs critiques arrêtera l’exécution des tests et fe
 
 ### Tests dérivés
 
-Testing derived fields is a feature which allows users to set a field on a certain entity and have another entity be updated automatically if it derives one of its fields from the first entity.
+Tester les champs dérivés est une fonctionnalité qui permet aux utilisateurs de définir un champ sur une certaine entité et de faire en sorte qu'une autre entité soit automatiquement mise à jour si elle dérive l'un de ses champs de la première entité.
 
-Before version `0.6.0` it was possible to get the derived entities by accessing them as entity fields/properties, like so:
+Avant la version `0.6.0`, il était possible d'obtenir les entités dérivées en les accédant comme des champs/propriétés d'entité, comme ceci :
 
 ```typescript
 let entity = ExampleEntity.load('id')
 let derivedEntity = entity.derived_entity
 ```
 
-As of version `0.6.0`, this is done by using the `loadRelated` function of graph-node, the derived entities can be accessed the same way as in the handlers.
+À partir de la version `0.6.0`, cela se fait en utilisant la fonction `loadRelated` de graph-node, les entités dérivées peuvent être accessibles de la même manière que dans les gestionnaires.
 
 ```typescript
 test('Derived fields example test', () => {
@@ -1000,9 +1009,9 @@ test('Derived fields example test', () => {
 })
 ```
 
-### Testing `loadInBlock`
+### Test de `loadInBlock`
 
-As of version `0.6.0`, users can test `loadInBlock` by using the `mockInBlockStore`, it allows mocking entities in the block cache.
+Depuis la version `0.6.0`, les utilisateurs peuvent tester `loadInBlock` en utilisant `mockInBlockStore`, ce qui permet de simuler des entités dans le cache du bloc.
 
 ```typescript
 import { afterAll, beforeAll, describe, mockInBlockStore, test } from 'matchstick-as'
@@ -1017,12 +1026,12 @@ describe('loadInBlock', () => {
     clearInBlockStore()
   })
 
-  test('Can use entity.loadInBlock() to retrieve entity from cache store in the current block', () => {
+  test('On peut utiliser  entity.loadInBlock() pour récupérer l'entité dans le cache du bloc actuel', () => {
     let retrievedGravatar = Gravatar.loadInBlock('gravatarId0')
     assert.stringEquals('gravatarId0', retrievedGravatar!.get('id')!.toString())
   })
 
-  test("Returns null when calling entity.loadInBlock() if an entity doesn't exist in the current block", () => {
+  test("Renvoie null lors de l'appel de entity.loadInBlock() si une entité n'existe pas dans le bloc actuel", () => {
     let retrievedGravatar = Gravatar.loadInBlock('IDoNotExist')
     assert.assertNull(retrievedGravatar)
   })
@@ -1086,46 +1095,39 @@ test('Exemple moqueur simple de source de données', () => {
 
 Notez que dataSourceMock.resetValues() est appelé à la fin. C'est parce que les valeurs sont mémorisées lorsqu'elles sont modifiées et doivent être réinitialisées si vous voulez revenir aux valeurs par défaut.
 
-### Testing dynamic data source creation
+### Test de la création dynamique de sources de données
 
-As of version `0.6.0`, it is possible to test if a new data source has been created from a template. This feature supports both ethereum/contract and file/ipfs templates. There are four functions for this:
+Depuis la version `0.6.0`, il est possible de tester si une nouvelle source de données a été créée à partir d'un modèle. Cette fonctionnalité prend en charge les modèles ethereum/contrat et file/ipfs. Il existe quatre fonctions pour cela :
 
-- `assert.dataSourceCount(templateName, expectedCount)` can be used to assert the expected count of data sources from the specified template
-- `assert.dataSourceExists(templateName, address/ipfsHash)` asserts that a data source with the specified identifier (could be a contract address or IPFS file hash) from a specified template was created
-- `logDataSources(templateName)` prints all data sources from the specified template to the console for debugging purposes
-- `readFile(path)` reads a JSON file that represents an IPFS file and returns the content as Bytes
+- `assert.dataSourceCount(templateName, expectedCount)` peut être utilisée pour affirmer le nombre attendu de sources de données à partir du modèle spécifié
+- `assert.dataSourceExists(templateName, address/ipfsHash)` affirme qu'une source de données avec l'identifiant spécifié (qui peut être une adresse de contrat ou un hash de fichier IPFS) a été créée à partir d'un modèle spécifié
+- `logDataSources(templateName)` affiche toutes les sources de données à partir du modèle spécifié dans la console à des fins de débogage
+- `readFile(path)` lit un fichier JSON qui représente un fichier IPFS et retourne le contenu sous forme de Bytes
 
-#### Testing `ethereum/contract` templates
+#### Test des modèles `ethereum/contract`
 
 ```typescript
-test('ethereum/contract dataSource creation example', () => {
-  // Assert there are no dataSources created from GraphTokenLockWallet template
+test('ethereum/contract dataSource creation example', () =>  {
+  // affirme qu'aucune source de données n'est créée à partir du modèle GraphTokenLockWallet
   assert.dataSourceCount('GraphTokenLockWallet', 0)
-
-  // Create a new GraphTokenLockWallet datasource with address 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
+  // Crée une nouvelle source de données GraphTokenLockWallet avec l'adresse 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
   GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
-
-  // Assert the dataSource has been created
+  // affirme que la source de données a été créée
   assert.dataSourceCount('GraphTokenLockWallet', 1)
-
-  // Add a second dataSource with context
+  // Ajoute une seconde source de données avec contexte
   let context = new DataSourceContext()
   context.set('contextVal', Value.fromI32(325))
-
   GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
-
-  // Assert there are now 2 dataSources
+  // Vérifie qu'il y a maintenant 2 sources de données
   assert.dataSourceCount('GraphTokenLockWallet', 2)
-
-  // Assert that a dataSource with address "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B" was created
-  // Keep in mind that `Address` type is transformed to lower case when decoded, so you have to pass the address as all lower case when asserting if it exists
+  // affirme qu'une source de données avec l'adresse "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B" a été créée
+  // Gardez à l'esprit que le type `Address` est transformé en minuscules lors du décodage, vous devez donc passer l'adresse en minuscules lorsque vous affirmez son existence
   assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
-
   logDataSources('GraphTokenLockWallet')
 })
 ```
 
-##### Example `logDataSource` output
+##### Exemple de sortie de `logDataSource`
 
 ```bash
 🛠  {
@@ -1146,19 +1148,18 @@ test('ethereum/contract dataSource creation example', () => {
       }
     }
   }
-}
 ```
 
-#### Testing `file/ipfs` templates
+#### Test des modèles `file/ipfs`
 
-Similarly to contract dynamic data sources, users can test test file datas sources and their handlers
+De même que les sources de données dynamiques de contrat, les utilisateurs peuvent tester les fichiers sources de données test et leurs gestionnaires
 
-##### Example `subgraph.yaml`
+##### Exemple `subgraph.yaml`
 
 ```yaml
 ...
 templates:
- - kind: file/ipfs
+  - kind: file/ipfs
     name: GraphTokenLockMetadata
     network: mainnet
     mapping:
@@ -1174,27 +1175,27 @@ templates:
           file: ./abis/GraphTokenLockWallet.json
 ```
 
-##### Example `schema.graphql`
+##### Exemple de fichier `schema.graphql`
 
 ```graphql
 """
-Token Lock Wallets which hold locked GRT
+Portefeuilles de verrouillage de jetons qui contiennent des GRT verrouillés
 """
 type TokenLockMetadata @entity {
-  "The address of the token lock wallet"
+  "L'adresse du portefeuille de blocage des jetons"
   id: ID!
-  "Start time of the release schedule"
+  "Heure de début du calendrier de sortie"
   startTime: BigInt!
-  "End time of the release schedule"
+  "Heure de fin du calendrier de sortie""
   endTime: BigInt!
-  "Number of periods between start time and end time"
+  "Nombre de périodes entre l'heure de début et l'heure de fin"
   periods: BigInt!
-  "Time when the releases start"
+  "Heure à laquelle commence la sortie"
   releaseStartTime: BigInt!
 }
 ```
 
-##### Example `metadata.json`
+##### Exemple de fichier `metadata.json`
 
 ```json
 {
@@ -1205,72 +1206,67 @@ type TokenLockMetadata @entity {
 }
 ```
 
-##### Example handler
+##### Exemple de gestionnaire
 
 ```typescript
 export function handleMetadata(content: Bytes): void {
-  // dataSource.stringParams() returns the File DataSource CID
-  // stringParam() will be mocked in the handler test
-  // for more info https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
+  // dataSource.stringParams() renvoie le CID du fichier de source de donnée
+  // stringParam() sera simulé dans le test du gestionnaire
+  // pour plus d'informations https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
   let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
   const value = json.fromBytes(content).toObject()
-
   if (value) {
     const startTime = value.get('startTime')
     const endTime = value.get('endTime')
     const periods = value.get('periods')
     const releaseStartTime = value.get('releaseStartTime')
-
-    if (startTime && endTime && periods && releaseStartTime) {
+   if (startTime && endTime && periods && releaseStartTime) {
       tokenMetadata.startTime = startTime.toBigInt()
       tokenMetadata.endTime = endTime.toBigInt()
       tokenMetadata.periods = periods.toBigInt()
       tokenMetadata.releaseStartTime = releaseStartTime.toBigInt()
     }
-
     tokenMetadata.save()
   }
 }
 ```
 
-##### Example test
+##### Exemple de test
 
 ```typescript
 import { assert, test, dataSourceMock, readFile } from 'matchstick-as'
 import { Address, BigInt, Bytes, DataSourceContext, ipfs, json, store, Value } from '@graphprotocol/graph-ts'
-
 import { handleMetadata } from '../../src/token-lock-wallet'
 import { TokenLockMetadata } from '../../generated/schema'
 import { GraphTokenLockMetadata } from '../../generated/templates'
 
-test('file/ipfs dataSource creation example', () => {
-  // Generate the dataSource CID from the ipfsHash + ipfs path file
-  // For example QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
+test('exemple de création de source de données file/ipfs', () =>  {
+  // Générer le CID de la source de données à partir du ipfsHash + chemin du fichier du ipfs
+  // Par exemple QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
   const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
   const CID = `${ipfshash}/example.json`
 
-  // Create a new dataSource using the generated CID
+  // Création d'une nouvelle source de données en utilisant le CID généré
   GraphTokenLockMetadata.create(CID)
 
-  // Assert the dataSource has been created
+  // Affirmer que la source de données a été créée
   assert.dataSourceCount('GraphTokenLockMetadata', 1)
   assert.dataSourceExists('GraphTokenLockMetadata', CID)
   logDataSources('GraphTokenLockMetadata')
 
-  // Now we have to mock the dataSource metadata and specifically dataSource.stringParam()
-  // dataSource.stringParams actually uses the value of dataSource.address(), so we will mock the address using dataSourceMock from  matchstick-as
-  // First we will reset the values and then use dataSourceMock.setAddress() to set the CID
+  // Maintenant, nous devons simuler les métadonnées de la source de données et plus particulièrement dataSource.stringParam()
+  // dataSource.stringParams utilise en fait la valeur de dataSource.address(), donc nous allons simuler l'adresse en utilisant dataSourceMock de matchstick-as
+  // Tout d'abord, nous allons réinitialiser les valeurs et ensuite utiliser dataSourceMock.setAddress() pour définir le CID
   dataSourceMock.resetValues()
   dataSourceMock.setAddress(CID)
 
-  // Now we need to generate the Bytes to pass to the dataSource handler
-  // For this case we introduced a new function readFile, that reads a local json and returns the content as Bytes
-  const content = readFile(`path/to/metadata.json`)
+  // Maintenant, nous devons générer les Bytes à passer au gestionnaire de la source de données
+  // Pour ce cas, nous avons introduit une nouvelle fonction readFile, qui lit un json local et renvoie le contenu sous forme de Bytes
+  const content = readFile('path/to/metadata.json')
   handleMetadata(content)
 
-  // Now we will test if a TokenLockMetadata was created
+  // Maintenant, nous allons tester si un TokenLockMetadata a été créé
   const metadata = TokenLockMetadata.load(CID)
-
   assert.bigIntEquals(metadata!.endTime, BigInt.fromI32(1))
   assert.bigIntEquals(metadata!.periods, BigInt.fromI32(1))
   assert.bigIntEquals(metadata!.releaseStartTime, BigInt.fromI32(1))
@@ -1368,22 +1364,26 @@ La sortie du journal inclut la durée de l’exécution du test. Voici un exempl
 
 > Critique : impossible de créer WasmInstance à partir d'un module valide avec un contexte : importation inconnue : wasi_snapshot_preview1::fd_write n'a pas été défini
 
-Cela signifie que vous avez utilisé `console.log` dans votre code, ce qui n'est pas pris en charge par AssemblyScript. Veuillez envisager d'utiliser l'[API Logging](/developing/graph-ts/api/#logging-api)
+Ceci signifie que vous avez utilisé `console.log` dans votre code, ce qui n'est pas pris en charge par AssemblyScript. Veuillez envisager d'utiliser l'[API de journalisation](/developing/graph-ts/api/#logging-api)
 
 > ERREUR TS2554 : attendu ? arguments, mais j'ai eu ?.
->
+> 
 > renvoyer le nouveau ethereum.Block (defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt) ;
->
+> 
 > dans ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > renvoyer un nouveau ethereum.Transaction (defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt) ;
->
+> 
 > dans ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 L'inadéquation des arguments est causée par une inadéquation entre `graph-ts` et `matchstick-as`. La meilleure façon de résoudre des problèmes comme celui-ci est de tout mettre à jour vers la dernière version publiée.
 
+## Ressources additionnelles
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Réaction
 
 Si vous avez des questions, des commentaires, des demandes de fonctionnalités ou si vous souhaitez simplement nous contacter, le meilleur endroit serait The Graph Discord où nous avons une chaîne dédiée à Matchstick, appelée 🔥| tests unitaires.

From e94bcae085d85107ec1da168362426bcc4b1da27 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:01 -0500
Subject: [PATCH 0116/1325] New translations about.mdx (Spanish)

---
 website/pages/es/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/es/about.mdx b/website/pages/es/about.mdx
index c745dcedd131..8b1a092a77b5 100644
--- a/website/pages/es/about.mdx
+++ b/website/pages/es/about.mdx
@@ -2,46 +2,66 @@
 title: Acerca de The Graph
 ---
 
-En esta página se explica qué es The Graph y cómo puedes empezar a utilizarlo.
-
 ## Que es The Graph?
 
-The Graph es un protocolo descentralizado que permite indexar y consultar datos de la blockchain. The Graph permite consultar datos los cuales son difíciles de consultar directamente.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Los proyectos con contratos inteligentes complejos como [Uniswap](https://uniswap.org/) y las iniciativas de NFTs como [Bored Ape Yacht Club](https://boredapeyachtclub.com/) almacenan los datos en la blockchain de Ethereum, lo que hace realmente difícil leer algo más que los datos básicos directamente desde la blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-También podrías crear tu propio servidor, procesar las transacciones allí, guardarlas en una base de datos y construir un punto de conexión de API encima de todo eso para consultar los datos. Sin embargo, esta opción [requiere muchos recursos](/network/benefits/), necesita mantenimiento, presenta un único punto de fallo y compromete las propiedades de seguridad importantes necesarias para la descentralización.
+### How The Graph Functions
 
-**Indexar los datos de la blockchain es muy, muy difícil.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## ¿Cómo funciona The Graph?
+- 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.
 
-The Graph aprende, qué y cómo indexar los datos de Ethereum, basándose en las descripciones de los subgrafos, conocidas como el manifiesto de los subgrafos. La descripción del subgrafo define los contratos inteligentes de interés para este subgrafo, los eventos en esos contratos a los que prestar atención, y cómo mapear los datos de los eventos a los datos que The Graph almacenará en su base de datos.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Una vez que has escrito el `subgraph manifest`, utilizas el CLI de The Graph para almacenar la definición en IPFS y decirle al indexador que empiece a indexar los datos de ese subgrafo.
+- 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.
 
-Este diagrama ofrece más detalles sobre el flujo de datos una vez que se ha deployado en el manifiesto para un subgrafo, que trata de las transacciones en Ethereum:
+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 escanea continuamente la red de Ethereum en busca de nuevos bloques y los datos de tu subgrafo que puedan contener.
-4. Graph Node encuentra los eventos de la red Ethereum, a fin de proveerlos en tu subgrafo mediante estos bloques y ejecuta los mapping handlers que proporcionaste. El mapeo (mapping) es un módulo WASM que crea o actualiza las entidades de datos que Graph Node almacena en respuesta a los eventos de Ethereum.
-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.
+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 escanea continuamente la red de Ethereum en busca de nuevos bloques y los datos de tu subgrafo que puedan contener.
+4.  Graph Node encuentra los eventos de la red Ethereum, a fin de proveerlos en tu subgrafo mediante estos bloques y ejecuta los mapping handlers que proporcionaste. El mapeo (mapping) es un módulo WASM que crea o actualiza las entidades de datos que Graph Node almacena en respuesta a los eventos de Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 6f10eff9263fd86faa8a9b2ea9d18fb59dd36965 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:02 -0500
Subject: [PATCH 0117/1325] New translations near.mdx (Spanish)

---
 website/pages/es/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/es/cookbook/near.mdx b/website/pages/es/cookbook/near.mdx
index 2d31f4a2c31b..f915ec580057 100644
--- a/website/pages/es/cookbook/near.mdx
+++ b/website/pages/es/cookbook/near.mdx
@@ -37,7 +37,7 @@ Hay tres aspectos de la definición de subgrafo:
 
 **schema.graphql:** un archivo de esquema que define qué datos se almacenan para su subgrafo y cómo consultarlos a través de GraphQL. Los requisitos para los subgrafos NEAR están cubiertos por [la documentación existente](/developing/creating-a-subgraph#the-graphql-schema).
 
-**Asignaciones de AssemblyScript:** [Código de AssemblyScript](/developing/graph-ts/api) que traduce los datos del evento a las entidades definidas en su esquema. La compatibilidad con NEAR introduce tipos de datos específicos de NEAR y una nueva funcionalidad de análisis de JSON.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 Durante el desarrollo del subgrafo hay dos comandos clave:
 
@@ -98,7 +98,7 @@ La definición de esquema describe la estructura de la base de datos de subgrafo
 
 Los handlers para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/).
 
-La indexación NEAR introduce tipos de datos específicos de NEAR en la [API de AssemblyScript](/developing/graph-ts/api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ Estos tipos se pasan a block & handlers de recibos:
 - Los handlers de bloques recibirán un `Block`
 - Los handlers de recibos recibirán un `ReceiptWithOutcome`
 
-De lo contrario, el resto de la [API de AssemblyScript](/developing/graph-ts/api) está disponible para los desarrolladores de subgrafos NEAR durante la ejecución del mapeo.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-Esto incluye una nueva función de análisis de JSON: los registros en NEAR se emiten con frecuencia como JSON en cadena. Una nueva función `json.fromString(...)` está disponible como parte de la [API JSON](/developing/graph-ts/api#json-api) para permitir a los desarrolladores para procesar fácilmente estos registros.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## Deployando un subgrafo NEAR
 
@@ -194,8 +194,8 @@ La configuración del nodo dependerá de dónde se implemente el subgrafo.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Graph Node Local (basado en la configuración predeterminada)

From 445edce1abed75269cbfd8b74b6f40d578c6026b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:04 -0500
Subject: [PATCH 0118/1325] New translations unit-testing-framework.mdx
 (Spanish)

---
 .../es/developing/unit-testing-framework.mdx  | 45 ++++++++++++-------
 1 file changed, 29 insertions(+), 16 deletions(-)

diff --git a/website/pages/es/developing/unit-testing-framework.mdx b/website/pages/es/developing/unit-testing-framework.mdx
index 6522e0531914..68c3ff849637 100644
--- a/website/pages/es/developing/unit-testing-framework.mdx
+++ b/website/pages/es/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Marco de Unit Testing
 ---
 
-¡Matchstick es un marco de unit testing, desarrollado por [LimeChain](https://limechain.tech/), que permite a los developers de subgrafos probar su lógica de mapeo en un entorno sandbox y deployar sus subgrafos con confianza!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Empezando
 
-### Instalar dependencias
+### Install Dependencies
 
-Para utilizar los métodos auxiliares de prueba y ejecutar las pruebas, deberás instalar las siguientes dependencias:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depende de PostgreSQL, por lo que si aún no lo tienes, deberás instalarlo. ¡Recomendamos ampliamente usar los comandos a continuación, ya que agregarlos de otra manera puede causar errores inesperados!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Comando de instalación de Postgres:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Crea un symlynk al último libpq.5.lib _Es posible que primero debas crear este
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Comando de instalación de Postgres (depende de tu distribución):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Subsistema de Windows para Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 Puedes usar Matchstick en WSL tanto con el enfoque de Docker como con el enfoque binario. Ya que WSL puede ser un poco complicado, aquí hay algunos consejos en caso de que encuentres problemas como
 
@@ -76,7 +85,7 @@ Y finalmente, no uses `graph test` (que usa tu instalación global de graph-cli
 }
 ```
 
-### Uso
+### Using Matchstick
 
 Para usar **Matchstick** en tu proyecto de subgrafo simplemente abre una terminal, navega a la carpeta raíz de tu proyecto y simplemente ejecuta `graph test [options] <datasource> `: descarga el binario **Matchstick** más reciente y ejecuta la prueba especificada o todas las pruebas en una carpeta de prueba (o todas las pruebas existentes si no se especifica un indicador de fuente de datos).
 
@@ -1368,22 +1377,26 @@ La salida del log incluye la duración de la ejecución de la prueba. Aquí hay
 
 > Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined
 
-Esto significa que has utilizado `console.log` en tu código, que no es compatible con AssemblyScript. Considera usar la [API de registro](/developing/graph-ts/api/#logging-api)
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 La falta de coincidencia en los argumentos se debe a la falta de coincidencia en `graph-ts` y `matchstick-as`. La mejor manera de solucionar problemas como este es actualizar todo a la última versión publicada.
 
+## Recursos Adicionales
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Comentario
 
 Si tiene preguntas, comentarios, solicitudes de funciones o simplemente deseas comunicarte, el mejor lugar sería The Graph Discord, donde tenemos un canal dedicado para Matchstick, llamado 🔥| unit-testing.

From 78fb487034350500aef160f283d6694ca33c480c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:05 -0500
Subject: [PATCH 0119/1325] New translations developing.mdx (Swedish)

---
 website/pages/sv/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/sv/network/developing.mdx b/website/pages/sv/network/developing.mdx
index 7509edd5cffb..c726ffb0c5a0 100644
--- a/website/pages/sv/network/developing.mdx
+++ b/website/pages/sv/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Utveckling
 ---
 
-Utvecklare utgör efterfrågesidan av The Graph-ekosystemet. Utvecklare bygger undergrafer och publicerar dem på The Graph Nätverk. Därefter frågar de levande undergrafer med GraphQL för att driva sina applikationer.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgrafens Livscykel
+## Översikt
 
-Undergrafer som distribueras till nätverket har en definierad livscykel.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Bygg lokalt
+On The Graph, you can:
 
-Precis som med all subgrafutveckling börjar det med lokal utveckling och testning. Utvecklare kan använda samma lokala uppsättning oavsett om de bygger för The Graph Nätverk, den värdade tjänsten eller en lokal Graph Node, genom att använda `graph-cli` och `graph-ts` för att bygga sin subgraf. Utvecklare uppmuntras att använda verktyg som [Matchstick](https://github.com/LimeChain/matchstick) för enhetstestning för att förbättra robustheten hos sina subgrafer.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Det finns vissa begränsningar på The Graf Nätverk, i termer av funktioner och nätverksstöd. Endast subgrafer på [stödda nätverk](/developing/supported-networks) kommer att tjäna indexbelöningar, och subgrafer som hämtar data från IPFS är heller inte kvalificerade.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publicera till Nätverket
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-När utvecklaren är nöjd med sin subgraf kan de publicera den på The Graf Nätverk. Detta är en on-chain-åtgärd, som registrerar subgrafen så att den kan upptäckas av Indexers. Publicerade subgrafer har en motsvarande NFT, som sedan kan överföras enkelt. Den publicerade subgrafen har associerad metadata, som ger andra nätverksdeltagare användbar sammanhang och information.
+### What are subgraphs?
 
-### Signal för Att Främja Indexering
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Publicerade subgrafer kommer troligen inte att plockas upp av Indexers utan tillsats av signal. Signal är låst GRT som är associerat med en given subgraf, vilket indikerar för Indexers att en given subgraf kommer att få frågevolym och bidrar också till de indexbelöningar som är tillgängliga för att bearbeta den. Subgrafutvecklare lägger vanligtvis till signal i sin subgraf för att främja indexering. Tredje part Curators kan också signalera på en given subgraf om de anser att subgrafen sannolikt kommer att generera frågevolym.
-
-### Frågor & Applikationsutveckling
-
-När en subgraf har bearbetats av Indexers och är tillgänglig för frågor kan utvecklare börja använda subgrafen i sina applikationer. Utvecklare frågar subgrafer via en gateway, som vidarebefordrar deras frågor till en Indexer som har bearbetat subgrafen och betalar frågeavgifter i GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Uppdatering av Subgrafer
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-När Subgrafutvecklaren är redo att uppdatera kan de initiera en transaktion för att peka sin subgraf till den nya versionen. Att uppdatera subgrafen migrerar all signal till den nya versionen (förutsatt att användaren som tillämpade signalen valde "auto-migrera"), vilket också medför en migrationsavgift. Denna signalmigration bör få Indexers att börja indexera den nya versionen av subgrafen, så den borde snart bli tillgänglig för frågor.
-
-### Avveckling av Subgrafer
-
-Vid någon punkt kan en utvecklare besluta att de inte längre behöver en publicerad subgraf. Vid den tidpunkten kan de avveckla subgrafen, vilket returnerar all signalerad GRT till Curators.
-
-### Olika Utvecklarroller
-
-Vissa utvecklare kommer att engagera sig i hela subgrafens livscykel på nätverket, publicera, fråga och iterera på sina egna subgrafer. Vissa kanske fokuserar på subgrafutveckling, bygger öppna API: er som andra kan bygga på. Vissa kan vara applikationsinriktade och fråga subgrafer som har distribuerats av andra.
-
-### Utvecklare och Nätverksekonomi
-
-Utvecklare är en nyckelaktör i nätverket ekonomiskt sett, låser upp GRT för att främja indexering och viktigast av allt, frågar subgrafer, vilket är nätverkets primära värdeutbyte. Subgrafutvecklare bränner också GRT varje gång en subgraf uppdateras.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 816911a0c3b339ba87a5773dc3e20b7dc3c027f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:06 -0500
Subject: [PATCH 0120/1325] New translations developing.mdx (Ukrainian)

---
 website/pages/uk/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/uk/network/developing.mdx b/website/pages/uk/network/developing.mdx
index 867bcb966f11..51dd2c70e7e5 100644
--- a/website/pages/uk/network/developing.mdx
+++ b/website/pages/uk/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Розробка
 ---
 
-Розробники — це джерело попиту в екосистемі Graph. Розробники створюють підграфи та розміщують їх в мережі Graph. Потім вони налаштовують коректну роботу підграфів по роботі з запитами, з допомогою GraphQL, аби забезпечити роботу своїх додатків.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Overview
 
-Запущені в мережі підграфи мають визначений життєвий цикл.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-Як і будь-яка інша розробка підграфів, вона починається з локальної розробки та тестування. Розробники можуть використовувати ті ж самі локальні налаштування, незалежно від того, чи створюють вони для мережі Graph, хостинговий сервіс або локальну Graph ноду, використовуючи при цьому `graph-cli` та `graph-ts` для створення свого підграфа. Розробникам рекомендується використовувати такі інструменти, як [Matchstick](https://github.com/LimeChain/matchstick) для модульного тестування, аби підвищити надійність своїх підграфів.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Існують певні обмеження для мережі The Graph з точки зору можливостей і підтримки різних мереж. Тільки підграфи у [мережах, які підтримуються](/developing/supported-networks) отримають винагороду за індексацію, а підграфи, які отримують дані з IPFS, не мають права на отримання винагороди.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-Коли розробник повністю задоволений своїм підграфом, він може розмістити його в The Graph Network. Ця дія відбувається в основній мережі, де проходить реєстрація підграфа таким чином, щоб його могли знайти індексатори. Опубліковані підграфи мають відповідний NFT, який потім легко передається. Опублікований підграф має пов'язані з ним метадані, які надають іншим учасникам мережі потрібний довідковий матеріал та інформацію.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Опубліковані підграфи навряд чи будуть підтримуватись індексаторами без наявності сигналу. Сигнал — це заблоковані GRT, приналежні до даного підграфа, які вказують індексаторам на те, що даний підграф буде мати змогу опрацьовувати великий обсяг запитів, а також сприяти отриманню винагород за індексацію, які можна отримати за обробку запитів. Розробники субграфів, як правило, додають сигнал до свого підграфа, щоб заохочувати проведення індексації. Сторонні куратори також можуть подавати сигнал на певний підграф, якщо вони вважають, що такий підграф може сприяти зростанню обсягу запитів в майбутньому.
-
-### Querying & Application Development
-
-Після того, як підграф підтримується індексаторами та доступний для запитів, розробники можуть починати використовувати підграф у своїх додатках. Розробники запитують підграфи через шлюз, який перенаправляє їхні запити до індексатора, який підтримує підграф, оплачуючи збір за запити в GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-У певний момент розробник може вирішити, що йому більше не потрібен опублікований підграф. У цей момент він може видалити підграф, який повертає будь-яку суму токенів GRT кураторам, які використували їх для подачі сигналу.
-
-### Diverse Developer Roles
-
-Деякі розробники будуть брати участь у повному життєвому циклі субграфів у мережі, публікуючи, запитуючи та ітеруючи свої власні підграфи. Деякі з них можуть зосередитися на розробці субграфів, створюючи відкриті API, на яких можуть базуватися інші. Деякі можуть бути орієнтовані на додатки, запитуючи підграфи, розміщені іншими.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 758fd3549167b909356dc363452b9a48c7fa5abe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:07 -0500
Subject: [PATCH 0121/1325] New translations developing.mdx (Chinese
 Simplified)

---
 website/pages/zh/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/zh/network/developing.mdx b/website/pages/zh/network/developing.mdx
index 97b241bcb081..c69562f7cb5f 100644
--- a/website/pages/zh/network/developing.mdx
+++ b/website/pages/zh/network/developing.mdx
@@ -2,52 +2,29 @@
 title: 开发
 ---
 
-开发人员是 Graph 生态系统的需求方。开发人员构建子图并将其发布到图形Graph网络。然后，它们使用 GraphQL 查询实时子图，以便为应用程序助力。
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## 子图生命周期
+## 概述
 
-部署到网络中的子图有一个确定的生命周期。
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### 本地建造
+On The Graph, you can:
 
-与所有子图开发一样，它从本地开发和测试开始。开发人员可以使用相同的本地设置，无论是为Graph 网络、托管服务还是本地 Graph 节点构建，都可以利用`graph-cli` 和 `graph-ts`构建子图。鼓励开发人员使用[Matchstick](https://github.com/LimeChain/matchstick)等工具进行单元测试，以提高子图的可靠性。
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> Graph网络在功能和网络支持方面存在一定限制。只有[支持的网络](/developing/supported-networks)上的子图才能获得索引奖励，从IPFS获取数据的子图也不符合条件。
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### 发布到网络
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-当开发人员对他们的子图感到满意时，他们可以将其发布到 Graph网络。这是一个链上操作，它注册子图，以便索引人可以发现它。已发布的子图具有相应的 NFT，这样就很容易转移。已发布的子图具有关联的元数据，这些元数据为其他网络参与者提供有用的背景和信息。
+### What are subgraphs?
 
-### 鼓励索引的信号
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-索引人不可能在不添加信号的情况下获取已发布的子图。信号被锁定与给定子图相关联的 GRT，它向索引人指示给定子图将接收查询量，并且还有助于处理它的索引奖励。子图开发人员通常会向他们的子图添加信号，以鼓励索引。如果第三方策展人认为某个子图可能驱动查询量，他们也可以在给定的子图上发出信号。
-
-### 查询& 应用开发
-
-一旦子图被索引者处理并用于查询，开发人员就可以开始在其应用程序中使用该子图。开发人员通过网关查询子图，该网关将他们的查询转发给处理子图的索引者，并以 GRT 支付查询费用。
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### 升级子图
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-一旦子图开发人员准备升级，他们就可以发起一个交易，将子图指向新版本。升级子图将任何信号迁移到新版本(假设应用该信号的用户选择了“自动迁移”) ，这也会带来迁移税。这种信号迁移应该会提示索引者开始为子图的新版本建立索引，因此它应该很快就可以用于查询。
-
-### 弃用子图
-
-在某种程度上，开发人员可能决定不再需要已发布的子图。在这一点上，他们可能不赞成子图，它将任何有信号的 GRT 返回给管理员。
-
-### 不同的开发人员角色
-
-一些开发人员将参与网络上子图的整个生命周期，在他们自己的子图上发布、查询和迭代。有些可能专注于子图开发，构建其他人可以构建的开放 API。有些可能是专注于应用程序的，查询由其他人部署的子图。
-
-### 开发商与网络经济
-
-开发人员是网络中关键的经济参与者，锁定 GRT 以鼓励索引，关键是查询子图，这是网络的主要价值交换。每当子图升级时，子图开发人员也会销毁GRT。
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 8e12dbfb024371cf747eb8758078c781964105a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:08 -0500
Subject: [PATCH 0122/1325] New translations developing.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/ur/network/developing.mdx b/website/pages/ur/network/developing.mdx
index 68572a2ad8f9..47f6552c33b8 100644
--- a/website/pages/ur/network/developing.mdx
+++ b/website/pages/ur/network/developing.mdx
@@ -2,52 +2,29 @@
 title: ڈویلپنگ
 ---
 
-ڈویلپرز گراف ایکو سسٹم کا مطلبہ کرنے والا پہلو ہے. ڈویلپرز گرافس بناتے ہیں اور گراف نیٹ ورک میں شائع کرتے ہیں. پھر، وہ اپنی ایپلیکیشنز کو طاقت دینے کے لیے GraphQL کے ساتھ لائیو سب گرافس سے کیوری کرتے ہیں.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## سب گراف لائف سائیکل
+## جائزہ
 
-نیٹ ورک پر تعینات سب گراف کا ایک متعین لائف سائیکل ہوتا ہے.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### مقامی طور پر تعمیر کریں
+On The Graph, you can:
 
-جیسا کہ تمام سب گراف کی ترقی کے ساتھ ، یہ مقامی تعمیر اور جانچ کے ساتھ شروع ہوتا ہے.ڈویلپرز ایک ہی مقامی سیٹ اپ کا استعمال کر سکتے ہیں چاہے وہ گراف نیٹ ورک، ہوسٹڈ سروس یا مقامی گراف نوڈ کے لیے تعمیر کر رہے ہوں، `graph-cli` اور `graph-ts` کا فائدہ اٹھاتے ہوئے سب گراف۔ ڈویلپرز کی حوصلہ افزائی کی جاتی ہے کہ وہ اپنے سب گراف کی مضبوطی کو بہتر بنانے کے لیے یونٹ ٹیسٹنگ کے لیے [Matchstick](https://github.com/LimeChain/matchstick) جیسے ٹولز استعمال کریں.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> گراف نیٹ ورک پر خصوصیت اور نیٹ ورک سپورٹ کے لحاظ سے کچھ رکاوٹیں ہیں۔ صرف [تعاون یافتہ نیٹ ورکس](/developing/supported-networks) پر سب گرافس ہی انڈیکسنگ انعامات حاصل کریں گے، اور وہ سب گراف جو IPFS سے ڈیٹا حاصل کرتے ہیں وہ بھی اہل نہیں ہیں.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### نیٹ ورک پر شائع کریں
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-جب ڈویلپر اپنی سب گراف سے خوش ہوتا ہے، وہ اسے گراف نیٹ ورک پر شائع کر سکتے ہیں.یہ ایک آن چین ایکشن ہے،جو سب گراف کو رجسٹر کرتا ہے تاکہ اسے انڈیکسرز کے ذریعے دریافت کیا جا سکے۔شائع شدہ سب گراف میں متعلقہ NFT ہے،جو پھر آسانی سے قابل منتقلی ہوتا ہے۔ شائع شدہ سب گراف میں میٹا ڈیٹا سے وابستہ ہے،جو نیٹ ورک کے دوسرے شرکاء کو مفید سیاق و سباق اور معلومات فراہم کرتا ہے.
+### What are subgraphs?
 
-### انڈیکسنگ کی حوصلہ افزائی کا سگنل
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-شائع شدہ سب گرافس سگنل کے اضافے کے بغیر انڈیکسرز کے ذریعہ اٹھائے جانے کا امکان نہیں ہے۔ سگنل ایک دیے گئےسب گراف کے ساتھ منسلک GRT مقفل ہے،جوانڈیکسرز کو اشارہ کرتا ہے کہ دیۓ گے سب گراف کو کیوری کا حجم موصول ہوگا،اور اس پر کارروائی کرنے کے لیے دستیاب انڈیکسنگ کے انعامات میں بھی حصہ ڈالتا ہے۔سب گراف ڈویلپرز عام طور پر اپنے سب گراف میں سگنل شامل کریں گے،انڈیکسنگی کی حوصلہ افزائی کے لیے. تھرڈ پارٹی کیوریٹر بھی دیے گئےسب گراف پر اشارہ کر سکتے ہیں،اگر وہ سب گراف کو کیوری کے حجم کو چلانے کا امکان سمجھتے ہیں.
-
-### کیوری کرنا اور ایپلیکیشن ڈویلپمنٹ
-
-یک بار جب انڈیکسرز کے ذریعہ سب گراف پر کارروائی ہو جائے اور کیوری کے لیے دستیاب ہو جائے،ڈویلپرز اپنی ایپلی کیشنز میں سب گراف استعمال کرنا شروع کرسکتے ہیں. ڈویلپرز ایک گیٹ وے کے ذریعے سب گرافس سے کیوری کرتے ہیں،جو ان کی کیوریز کو انڈیکسر کو بھیجتا ہے جس نے سب گراف پر کارروائی کی ہے،GRT میں کیوری کی فیس ادا کرنا.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### سب گرافس کو اپ ڈیٹ کرنا
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-ایک بار جب سب گراف ڈویلپر اپ گریڈ کرنے کے لیے تیار ہو جائے، وہ اپنےسب گراف کو نئے ورزن کی طرف اشارہ کرنے کے لیے ٹرانزیکشن شروع کر سکتے ہیں۔ سب گراف کو اپ ڈیٹ کرنے سے کسی بھی سگنل کو نئے ورزن میں منتقل کیا جاتا ہے (یہ فرض کرتے ہوئے کہ صارف جس نے سگنل کو "آٹو مائیگریٹ" منتخب کیا ہے)، جس پرمنتقلی ٹیکس بھی لاگو ہوتا ہے۔ اس سگنل کی منتقلی سے انڈیکسرز کو سب گراف کے نئے ورزن کی انڈیکسنگ شروع کرنے کا اشارہ کرنا چاہیے، اس لیے اسے جلد ہی کیوری کے لیے دستیاب ہونا چاہیے.
-
-### سب گراف کو فرسودہ کرنا
-
-کسی وقت ایک ڈویلپر فیصلہ کر سکتا ہے کہ انہیں اب شائع شدہ سب گراف کی ضرورت نہیں ہے۔اس وقت وہ سب گراف کو فرسودہ کر سکتے ہیں، جو کیوریٹرز کو کوئی بھی سگنل شدہ GRT واپس کرتا ہے.
-
-### متنوع ڈویلپر کے کردار
-
-کچھ ڈویلپرز نیٹ ورک پر مکمل سب گراف لائف سائیکل کے ساتھ مشغول ہوں گے، ان کے اپنے سب گراف پر اشاعت، کیوری اور تکرار کریں گے۔کچھ سب گراف کی ترقی پر توجہ مرکوز کر سکتے ہیں،کھلے APIs کی تعمیر جس پر دوسرے بنا سکتے ہیں۔کچھ ایپلیکیشن فوکسڈ ہو سکتے ہیں، دوسروں کے ذریعے تعینات کردہ سب گرافس سے کیوری کرتے ہیں.
-
-### ڈویلپرز اور نیٹ ورک اکنامکس
-
-ڈویلپر نیٹ ورک میں ایک اہم اقتصادی اداکار ہیں، انڈیکسنگ کی حوصلہ افزائی کے لیے GRT کو لاک اپ کرنا، اور سب گرافس کو اہم طور پر کیوری کرنا، جو کہ نیٹ ورک کا بنیادی ویلیو ایکسچینج ہے۔ جب بھی سب گراف کو اپ ڈیٹ کیا جاتا ہے تو سب گراف ڈویلپر GRT کو بھی جلا دیتے ہیں۔
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From afa68b12e05a6da414094d66159090135395e9f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:09 -0500
Subject: [PATCH 0123/1325] New translations developing.mdx (Vietnamese)

---
 website/pages/vi/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/vi/network/developing.mdx b/website/pages/vi/network/developing.mdx
index 1b76eb94ccca..0a4e23fcbf00 100644
--- a/website/pages/vi/network/developing.mdx
+++ b/website/pages/vi/network/developing.mdx
@@ -2,52 +2,29 @@
 title: Developing
 ---
 
-Developers are the demand side of The Graph ecosystem. Developers build subgraphs and publish them to The Graph Network. Then, they query live subgraphs with GraphQL in order to power their applications.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## Subgraph Lifecycle
+## Tổng quan
 
-Subgraphs deployed to the network have a defined lifecycle.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### Build locally
+On The Graph, you can:
 
-As with all subgraph development, it starts with local development and testing. Developers can use the same local setup whether they are building for The Graph Network, the hosted service or a local Graph Node, leveraging `graph-cli` and `graph-ts` to build their subgraph. Developers are encouraged to use tools such as [Matchstick](https://github.com/LimeChain/matchstick) for unit testing to improve the robustness of their subgraphs.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> There are certain constraints on The Graph Network, in terms of feature and network support. Only subgraphs on [supported networks](/developing/supported-networks) will earn indexing rewards, and subgraphs which fetch data from IPFS are also not eligible.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### Publish to the Network
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-When the developer is happy with their subgraph, they can publish it to The Graph Network. This is an on-chain action, which registers the subgraph so that it is discoverable by Indexers. Published subgraphs have a corresponding NFT, which is then easily transferable. The published subgraph has associated metadata, which provides other network participants with useful context and information.
+### What are subgraphs?
 
-### Signal to Encourage Indexing
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-Published subgraphs are unlikely to be picked up by Indexers without the addition of signal. Signal is locked GRT associated with a given subgraph, which indicates to Indexers that a given subgraph will receive query volume, and also contributes to the indexing rewards available for processing it. Subgraph developers will generally add signal to their subgraph, in order to encourage indexing. Third party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
-
-### Querying & Application Development
-
-Once a subgraph has been processed by Indexers and is available for querying, developers can start to use the subgraph in their applications. Developers query subgraphs via a gateway, which forwards their queries to an Indexer who has processed the subgraph, paying query fees in GRT.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### Deprecating Subgraphs
-
-At some point a developer may decide that they no longer need a published subgraph. At that point they may deprecate the subgraph, which returns any signalled GRT to the Curators.
-
-### Diverse Developer Roles
-
-Some developers will engage with the full subgraph lifecycle on the network, publishing, querying and iterating on their own subgraphs. Some may be focused on subgraph development, building open APIs which others can build on. Some may be application focused, querying subgraphs deployed by others.
-
-### Developers and Network Economics
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 07452e4ad4d010fa09ddeb92c19429fc2ec6a420 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:10 -0500
Subject: [PATCH 0124/1325] New translations developing.mdx (Marathi)

---
 website/pages/mr/network/developing.mdx | 53 +++++++------------------
 1 file changed, 15 insertions(+), 38 deletions(-)

diff --git a/website/pages/mr/network/developing.mdx b/website/pages/mr/network/developing.mdx
index 9206b99c72cf..7ba2e1c2211a 100644
--- a/website/pages/mr/network/developing.mdx
+++ b/website/pages/mr/network/developing.mdx
@@ -2,52 +2,29 @@
 title: विकसनशील
 ---
 
-डेव्हलपर्स ही ग्राफ इकोसिस्टमची मागणीची बाजू आहे. विकसक सबग्राफ तयार करतात आणि ग्राफ नेटवर्कवर प्रकाशित करतात. त्यानंतर, ते त्यांच्या अनुप्रयोगांना सामर्थ्य देण्यासाठी GraphQL सह थेट सबग्राफ्सची क्वेरी करतात.
+To start coding right away, go to [Developer Quick Start](/quick-start/).
 
-## सबग्राफ लाइफसायकल
+## सविश्लेषण
 
-नेटवर्कवर उपयोजित सबग्राफ्समध्ये एक परिभाषित जीवनचक्र असते.
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
 
-### स्थानिक पातळीवर तयार करा
+On The Graph, you can:
 
-सर्व उपग्राफ विकासाप्रमाणे, हे स्थानिक विकास आणि चाचणीसह सुरू होते. डेव्हलपर समान स्थानिक सेटअप वापरू शकतात मग ते ग्राफ नेटवर्क, होस्ट केलेल्या सेवेसाठी किंवा स्थानिक ग्राफ नोडसाठी, `ग्राफ-क्ली` आणि `ग्राफ-टीएस` चा वापर करत असतील. सबग्राफ विकसकांना त्यांच्या सबग्राफची मजबूती सुधारण्यासाठी युनिट चाचणीसाठी [मॅचस्टिक](https://github.com/LimeChain/matchstick) सारखी साधने वापरण्यास प्रोत्साहित केले जाते.
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
 
-> ग्राफ नेटवर्कवर वैशिष्ट्य आणि नेटवर्क समर्थनाच्या बाबतीत काही मर्यादा आहेत. केवळ [समर्थित नेटवर्क](/developing/supported-networks) वरील सबग्राफ अनुक्रमित पुरस्कार मिळवतील आणि IPFS कडून डेटा आणणारे सबग्राफ देखील पात्र नाहीत.
+### What is GraphQL?
 
-### Deploy to Subgraph Studio
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
 
-Once defined, the subgraph can be built and deployed to [Subgraph Studio](/deploying/subgraph-studio-faqs/). Subgraph Studio is a sandbox environment which will index the deployed subgraph and make it available for rate-limited development and testing. This gives developers an opportunity to verify that their subgraph does not encounter any indexing errors, and works as expected.
+### Developer Actions
 
-### नेटवर्कवर प्रकाशित करा
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
 
-जेव्हा विकसक त्यांच्या सबग्राफसह आनंदी असतो, तेव्हा ते ग्राफ नेटवर्कवर प्रकाशित करू शकतात. ही एक ऑन-चेन क्रिया आहे, जी सबग्राफची नोंदणी करते जेणेकरून ते इंडेक्सर्सद्वारे शोधता येईल. प्रकाशित सबग्राफमध्ये संबंधित NFT असतो, जो नंतर सहजपणे हस्तांतरित करता येतो. प्रकाशित सबग्राफमध्ये मेटाडेटा संबद्ध आहे, जो इतर नेटवर्क सहभागींना उपयुक्त संदर्भ आणि माहिती प्रदान करतो.
+### What are subgraphs?
 
-### इंडेक्सिंगला प्रोत्साहन देण्यासाठी सिग्नल
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
 
-प्रकाशित सबग्राफ इंडेक्सर्सद्वारे सिग्नल जोडल्याशिवाय उचलले जाण्याची शक्यता नाही. सिग्नल हा दिलेल्या सबग्राफशी संबंधित GRT लॉक केलेला आहे, जो निर्देशांककर्त्यांना सूचित करतो की दिलेल्या सबग्राफला क्वेरी व्हॉल्यूम प्राप्त होईल आणि त्यावर प्रक्रिया करण्यासाठी उपलब्ध अनुक्रमणिका बक्षिसेमध्ये देखील योगदान होते. इंडेक्सिंगला प्रोत्साहन देण्यासाठी सबग्राफ डेव्हलपर सामान्यतः त्यांच्या सबग्राफमध्ये सिग्नल जोडतील. तृतीय पक्ष क्युरेटर्स दिलेल्या सबग्राफवर सिग्नल देखील करू शकतात, जर त्यांना सबग्राफ क्वेरी व्हॉल्यूम वाढवण्याची शक्यता वाटत असेल.
-
-### चौकशी & अनुप्रयोग विकास
-
-इंडेक्सर्सद्वारे सबग्राफवर प्रक्रिया केल्यानंतर आणि क्वेरीसाठी उपलब्ध झाल्यानंतर, विकासक त्यांच्या अनुप्रयोगांमध्ये सबग्राफ वापरण्यास प्रारंभ करू शकतात. विकासक गेटवेद्वारे सबग्राफ्सची क्वेरी करतात, जे त्यांच्या क्वेरी GRT मध्ये क्वेरी शुल्क भरून सबग्राफवर प्रक्रिया केलेल्या इंडेक्सरकडे पाठवतात.
-
-In order to make queries, developers must generate an API key, which can be done in Subgraph Studio. This API key must be funded with GRT, in order to pay query fees. Developers can set a maximum query fee, in order to control their costs, and limit their API key to a given subgraph or origin domain. Subgraph Studio provides developers with data on their API key usage over time.
-
-Developers are also able to express an Indexer preference to the gateway, for example preferring Indexers whose query response is faster, or whose data is most up to date. These controls are set in Subgraph Studio.
-
-### Updating Subgraphs
-
-After a time a subgraph developer may want to update their subgraph, perhaps fixing a bug or adding new functionality. The subgraph developer may deploy new version(s) of their subgraph to Subgraph Studio for rate-limited development and testing.
-
-Once the Subgraph Developer is ready to update, they can initiate a transaction to point their subgraph at the new version. Updating the subgraph migrates any signal to the new version (assuming the user who applied the signal selected "auto-migrate"), which also incurs a migration tax. This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
-
-### उपग्राफ नापसंत करत आहे
-
-एखाद्या वेळी विकासक ठरवू शकतो की त्यांना यापुढे प्रकाशित सबग्राफची आवश्यकता नाही. त्या वेळी ते सबग्राफचे अवमूल्यन करू शकतात, जे क्युरेटर्सना कोणतेही सिग्नल केलेले GRT परत करतात.
-
-### विविध विकासक भूमिका
-
-काही डेव्हलपर नेटवर्कवरील पूर्ण सबग्राफ लाइफसायकलमध्ये व्यस्त राहतील, त्यांच्या स्वतःच्या सबग्राफवर प्रकाशित, क्वेरी आणि पुनरावृत्ती करतील. काही सबग्राफ डेव्हलपमेंटवर लक्ष केंद्रित करू शकतात, ओपन API तयार करू शकतात ज्यावर इतर तयार करू शकतात. काही अनुप्रयोग केंद्रित असू शकतात, इतरांनी उपयोजित केलेल्या सबग्राफची चौकशी करतात.
-
-### विकसक आणि नेटवर्क इकॉनॉमिक्स
-
-Developers are a key economic actor in the network, locking up GRT in order to encourage indexing, and crucially querying subgraphs, which is the network's primary value exchange. Subgraph developers also burn GRT whenever a subgraph is updated.
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From 76e6e58f6858b8839b46f788239a21d1a85ae3df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:11 -0500
Subject: [PATCH 0125/1325] New translations developing.mdx (Swahili)

---
 website/pages/sw/network/developing.mdx | 30 +++++++++++++++++++++++++
 1 file changed, 30 insertions(+)
 create mode 100644 website/pages/sw/network/developing.mdx

diff --git a/website/pages/sw/network/developing.mdx b/website/pages/sw/network/developing.mdx
new file mode 100644
index 000000000000..6ba33f6d916c
--- /dev/null
+++ b/website/pages/sw/network/developing.mdx
@@ -0,0 +1,30 @@
+---
+title: Developing
+---
+
+To start coding right away, go to [Developer Quick Start](/quick-start/).
+
+## Overview
+
+As a developer, you need data to build and power your dapp. Querying and indexing blockchain data is challenging, but The Graph provides a solution to this issue.
+
+On The Graph, you can:
+
+1.  Create, deploy, and publish subgraphs to The Graph using Graph CLI and [Subgraph Studio](https://thegraph.com/studio/).
+2.  Use GraphQL to query existing subgraphs.
+
+### What is GraphQL?
+
+- [GraphQL](https://graphql.org/learn/) is the query language for APIs and a runtime for executing those queries with your existing data. The Graph uses GraphQL to query subgraphs.
+
+### Developer Actions
+
+- Query subgraphs built by other developers in [The Graph Network](https://thegraph.com/explorer) and integrate them into your own dapps.
+- Create custom subgraphs to fulfill specific data needs, allowing improved scalability and flexibility for other developers.
+- Deploy, publish and signal your subgraphs within The Graph Network.
+
+### What are subgraphs?
+
+A subgraph is a custom API built on blockchain data. It extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL.
+
+Check out the documentation on [subgraphs](/subgraphs/) to learn specifics.

From af0916355fa0c3bfc7152ee324e2e68f9588002b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:12 -0500
Subject: [PATCH 0126/1325] New translations graphql-api.mdx (Romanian)

---
 website/pages/ro/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/ro/querying/graphql-api.mdx b/website/pages/ro/querying/graphql-api.mdx
index 2bbc71b5bb9c..d8671e53a77c 100644
--- a/website/pages/ro/querying/graphql-api.mdx
+++ b/website/pages/ro/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### Example
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | Description |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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                                |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From cc3ba68e4e3ca94833ac5e09d9a59599bc15fe10 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:14 -0500
Subject: [PATCH 0127/1325] New translations api.mdx (Romanian)

---
 website/pages/ro/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/ro/developing/graph-ts/api.mdx b/website/pages/ro/developing/graph-ts/api.mdx
index 46442dfa941e..8fc1f4b48b61 100644
--- a/website/pages/ro/developing/graph-ts/api.mdx
+++ b/website/pages/ro/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API Reference
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Built-in Types
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Handling Reverted Calls
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Encoding/Decoding ABI
 

From 0a31ee3203aa50023b66e237a071aa7104b5ead2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:15 -0500
Subject: [PATCH 0128/1325] New translations api.mdx (French)

---
 website/pages/fr/developing/graph-ts/api.mdx | 447 ++++++++++---------
 1 file changed, 228 insertions(+), 219 deletions(-)

diff --git a/website/pages/fr/developing/graph-ts/api.mdx b/website/pages/fr/developing/graph-ts/api.mdx
index 842054226e4d..1fecf7dd1dd4 100644
--- a/website/pages/fr/developing/graph-ts/api.mdx
+++ b/website/pages/fr/developing/graph-ts/api.mdx
@@ -2,47 +2,49 @@
 title: API AssemblyScript
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Remarque : Si vous avez créé un subgraph avant la version `graph-cli`/`graph-ts` `0.22.0`, alors vous utilisez une ancienne version d'AssemblyScript. Il est recommandé de consulter le [`Guide de Migration `] (/release-notes/assemblyscript-migration-guide).
 
-Cette page documente les API intégrées qui peuvent être utilisées lors de l'écriture de mappages de subgraphs. Deux types d'API sont disponibles prêtes à l'emploi :
+Découvrez quelles APIs intégrées peuvent être utilisées lors de l'écriture des mappages de subgraph. Il existe deux types d'APIs disponibles par défaut :
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- La [Bibliothèque TypeScript de The Graph](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code généré à partir des fichiers du subgraph par `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+Vous pouvez également ajouter d'autres bibliothèques comme dépendances, à condition qu'elles soient compatibles avec [AssemblyScript] (https://github.com/AssemblyScript/assemblyscript).
+
+Étant donné que les mappages de langage sont écrits en AssemblyScript, il est utile de consulter les fonctionnalités de langage et de bibliothèque standard dans le du [wiki AssemblyScript] (https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Référence API
 
-The `@graphprotocol/graph-ts` library provides the following APIs:
+La bibliothèque `@graphprotocol/graph-ts` fournit les API suivantes :
 
-- An `ethereum` API for working with Ethereum smart contracts, events, blocks, transactions, and Ethereum values.
-- A `store` API to load and save entities from and to the Graph Node store.
-- A `log` API to log messages to the Graph Node output and Graph Explorer.
-- An `ipfs` API to load files from IPFS.
-- A `json` API to parse JSON data.
-- A `crypto` API to use cryptographic functions.
+- Une API `ethereum` pour travailler avec les contrats intelligents Ethereum, les événements, les blocs, les transactions et les valeurs Ethereum.
+- Une API `store` pour charger et enregistrer des entités depuis et vers le magasin Graph Node.
+- Une API `log` pour enregistrer des messages dans la sortie Graph Node et Graph Explorer.
+- Une API `ipfs` pour charger des fichiers depuis IPFS.
+- Une API `json` pour analyser les données JSON.
+- Une API `crypto` pour utiliser des fonctions cryptographiques.
 - Primitives de bas niveau pour traduire entre différents systèmes de types tels que Ethereum, JSON, GraphQL et AssemblyScript.
 
 ### Versions
 
-The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
+La `apiVersion` dans le manifeste du subgraph spécifie la version de l'API de mappage exécutée par Graph Node pour un subgraph donné.
 
-| Version | Notes de version |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Notes de version                                                                                                                                                                                                                                                                     |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  0.0.9  | Ajout de nouvelles fonctions hôtes [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                              |
+|  0.0.8  | Ajout de la validation pour l'existence des champs dans le schéma lors de l'enregistrement d'une entité.                                                                                                                                                                             |
+|  0.0.7  | Ajout des classes `TransactionReceipt` et `Log`aux types Ethereum<br />Ajout du champ `receipt` à l'objet Ethereum Event                                                                                                                                                             |
+|  0.0.6  | Ajout du champ `nonce` à l'objet Ethereum Transaction<br />Ajout de `baseFeePerGas` à l'objet Ethereum Block                                                                                                                                                                         |
+|  0.0.5  | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/release-notes/assemblyscript-migration-guide))<br />. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` |
+|  0.0.4  | Ajout du champ `functionSignature` à l'objet Ethereum SmartContractCall                                                                                                                                                                                                              |
+|  0.0.3  | Ajout du champ `from` à l'objet Ethereum Call<br />`etherem.call.address` est renommé en `ethereum.call.to`                                                                                                                                                                          |
+|  0.0.2  | Ajout du champ `input` à l'objet Ethereum Transaction                                                                                                                                                                                                                                |
 
 ### Types intégrés
 
-Documentation on the base types built into AssemblyScript can be found in the [AssemblyScript wiki](https://www.assemblyscript.org/types.html).
+La documentation sur les types de base intégrés dans AssemblyScript se trouve dans le [wiki AssemblyScript](https://www.assemblyscript.org/types.html).
 
-The following additional types are provided by `@graphprotocol/graph-ts`.
+Les types additionnels suivants sont fournis par `@graphprotocol/graph-ts`.
 
 #### ByteArray
 
@@ -50,26 +52,26 @@ The following additional types are provided by `@graphprotocol/graph-ts`.
 import { ByteArray } from '@graphprotocol/graph-ts'
 ```
 
-`ByteArray` represents an array of `u8`.
+`ByteArray` représente un tableau de `u8`.
 
 _Construction_
 
-- `fromI32(x: i32): ByteArray` - Decomposes `x` into bytes.
-- `fromHexString(hex: string): ByteArray` - Input length must be even. Prefixing with `0x` is optional.
+- `fromI32(x: i32): ByteArray` - Décompose `x` en octets.
+- `fromHexString(hex: string): ByteArray` - La longueur de la saisie doit être paire. Le préfixe `0x` est optionnel.
 
-_Type conversions_
+_Conversions de type_
 
-- `toHexString(): string` - Converts to a hex string prefixed with `0x`.
-- `toString(): string` - Interprets the bytes as a UTF-8 string.
-- `toBase58(): string` - Encodes the bytes into a base58 string.
-- `toU32(): u32` - Interprets the bytes as a little-endian `u32`. Throws in case of overflow.
-- `toI32(): i32` - Interprets the byte array as a little-endian `i32`. Throws in case of overflow.
+- `toHexString(): string` - Convertit en une chaîne de caractères hexadécimale ayant comme préfixe `0x`.
+- `toString(): string` - Interprète les octets comme une chaîne UTF-8.
+- toBase58(): string\` - Encode les octets en une chaîne de caractères de type base58.
+- `toU32(): u32` - Interprète les octets comme un `u32` en little-endian. Envoie une exception en cas de dépassement.
+- `toI32(): i32` - Interprète le tableau d'octets comme un `i32` en little-endian. Envoie une exception en cas de dépassement.
 
-_Operators_
+_Operateurs_
 
-- `equals(y: ByteArray): bool` – can be written as `x == y`.
-- `concat(other: ByteArray) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by `other`
-- `concatI32(other: i32) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by the byte representation of `other`
+- `equals(y: ByteArray): bool` – peut être écrit comme `x == y`.
+- `concat(other: ByteArray) : ByteArray` - renvoie un nouveau `ByteArray` constitué de `this` directement suivi par `other`
+- `concatI32(other: i32) : ByteArray` - retourne un nouveau `ByteArray` constitué de `this` directement suivi par la représentation en octets de `other`
 
 #### BigDecimal
 
@@ -77,32 +79,32 @@ _Operators_
 import { BigDecimal } from '@graphprotocol/graph-ts'
 ```
 
-`BigDecimal` is used to represent arbitrary precision decimals.
+`BigDecimal` est utilisé pour représenter des décimales à précision arbitraire.
 
-> Note: [Internally](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal` is stored in [IEEE-754 decimal128 floating-point format](https://en.wikipedia.org/wiki/Decimal128_floating-point_format), which supports 34 decimal digits of significand. This makes `BigDecimal` unsuitable for representing fixed-point types that can span wider than 34 digits, such as a Solidity [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) or equivalent.
+> Remarque: [En interne](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal` est stocké au format [IEEE-754 décimal128 à virgule flottante](https://en.wikipedia.org/wiki/Decimal128_floating-point_format), qui supporte 34 chiffres significatifs. Cela rend `BigDecimal` inapproprié pour représenter des types à virgule fixe pouvant dépasser 34 chiffres, comme un Solidity [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) ou équivalent.
 
 _Construction_
 
-- `constructor(bigInt: BigInt)` – creates a `BigDecimal` from an `BigInt`.
-- `static fromString(s: string): BigDecimal` – parses from a decimal string.
+- `constructor(bigInt: BigInt)` – crée un `BigDecimal` à partir d'un `BigInt`.
+- `static fromString(s: string): BigDecimal` – analyse à partir d'une chaîne de caractères décimaux.
 
-_Type conversions_
+_Conversions de type_
 
-- `toString(): string` – prints to a decimal string.
+- `toString(): string` – affiche en une chaîne de caractères décimaux.
 
 _Math_
 
-- `plus(y: BigDecimal): BigDecimal` – can be written as `x + y`.
-- `minus(y: BigDecimal): BigDecimal` – can be written as `x - y`.
-- `times(y: BigDecimal): BigDecimal` – can be written as `x * y`.
-- `div(y: BigDecimal): BigDecimal` – can be written as `x / y`.
-- `equals(y: BigDecimal): bool` – can be written as `x == y`.
-- `notEqual(y: BigDecimal): bool` – can be written as `x != y`.
-- `lt(y: BigDecimal): bool` – can be written as `x < y`.
-- `le(y: BigDecimal): bool` – can be written as `x <= y`.
-- `gt(y: BigDecimal): bool` – can be written as `x > y`.
-- `ge(y: BigDecimal): bool` – can be written as `x >= y`.
-- `neg(): BigDecimal` - can be written as `-x`.
+- `plus(y: BigDecimal): BigDecimal` – peut être écrit comme `x + y`.
+- `minus(y: BigDecimal): BigDecimal` – peut être écrit comme `x - y`.
+- `times(y: BigDecimal): BigDecimal` – peut être écrit comme `x * y`.
+- `div(y: BigDecimal): BigDecimal` – peut être écrit comme `x / y`.
+- `equals(y: BigDecimal): bool` – peut être écrit comme `x == y`.
+- `notEqual(y: BigDecimal): bool` – peut être écrit comme `x != y`.
+- `lt(y: BigDecimal): bool` – peut être écrit comme `x < y`.
+- `le(y: BigDecimal): bool` – peut être écrit comme `x <= y`.
+- `gt(y: BigDecimal): bool` – peut être écrit comme `x > y`.
+- `ge(y: BigDecimal): bool` – peut être écrit comme `x >= y`.
+- `neg(): BigDecimal` - peut être écrit comme `-x`.
 
 #### BigInt
 
@@ -110,53 +112,53 @@ _Math_
 importer { BigInt } depuis '@graphprotocol/graph-ts'
 ```
 
-`BigInt` is used to represent big integers. This includes Ethereum values of type `uint32` to `uint256` and `int64` to `int256`. Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.
+`BigInt` est utilisé pour représenter de grands entiers. Cela inclut les valeurs Ethereum de type `uint32` à `uint256` et `int64` à`int256`. Tout ce qui est en dessous de `uint32`, tel que `int32`, `uint24` ou `int8` est représenté sous forme de `i32`.
 
-The `BigInt` class has the following API:
+La classe `BigInt` possède l'API suivante :
 
 _Construction_
 
-- `BigInt.fromI32(x: i32): BigInt` – creates a `BigInt` from an `i32`.
+- `BigInt.fromI32(x: i32): BigInt` – crée un `BigInt` à partir d'un `i32`.
 
-- `BigInt.fromString(s: string): BigInt`– Parses a `BigInt` from a string.
+- `BigInt.fromString(s: string): BigInt`– Analyse un `BigInt` à partir d'une chaîne de caractères.
 
-- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` – Interprets `bytes` as an unsigned, little-endian integer. If your input is big-endian, call `.reverse()` first.
+- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` – Interprète `bytes` comme un entier non signé en little-endian. Si votre saisie est en big-endian, appelez d'abord `.reverse()`.
 
-- `BigInt.fromSignedBytes(x: Bytes): BigInt` – Interprets `bytes` as a signed, little-endian integer. If your input is big-endian, call `.reverse()` first.
+- `BigInt.fromSignedBytes(x: Bytes): BigInt` – Interprète `bytes` comme un entier signé en little-endian. Si votre saisie est en big-endian, appelez d'abord `.reverse()`.
 
-  _Type conversions_
+  _Conversions de type_
 
-- `x.toHex(): string` – turns `BigInt` into a string of hexadecimal characters.
+- `x.toHex(): string` – transforme `BigInt` en une chaîne de caractères hexadécimaux.
 
-- `x.toString(): string` – turns `BigInt` into a decimal number string.
+- `x.toString(): string` – transforme`BigInt` en une chaîne de caractères de nombres décimaux.
 
-- `x.toI32(): i32` – returns the `BigInt` as an `i32`; fails if the value does not fit into `i32`. It's a good idea to first check `x.isI32()`.
+- `x.toI32(): i32` – renvoie le `BigInt` comme un `i32`; échoue si la valeur ne rentre pas dans un `i32`. Il est conseillé de vérifier d'abord `x.isI32()`.
 
-- `x.toBigDecimal(): BigDecimal` - converts into a decimal with no fractional part.
+- `x.toBigDecimal(): BigDecimal` - convertit en un nombre décimal sans virgule.
 
 _Math_
 
-- `x.plus(y: BigInt): BigInt` – can be written as `x + y`.
-- `x.minus(y: BigInt): BigInt` – can be written as `x - y`.
-- `x.times(y: BigInt): BigInt` – can be written as `x * y`.
-- `x.div(y: BigInt): BigInt` – can be written as `x / y`.
-- `x.mod(y: BigInt): BigInt` – can be written as `x % y`.
-- `x.equals(y: BigInt): bool` – can be written as `x == y`.
-- `x.notEqual(y: BigInt): bool` – can be written as `x != y`.
-- `x.lt(y: BigInt): bool` – can be written as `x < y`.
-- `x.le(y: BigInt): bool` – can be written as `x <= y`.
-- `x.gt(y: BigInt): bool` – can be written as `x > y`.
-- `x.ge(y: BigInt): bool` – can be written as `x >= y`.
-- `x.neg(): BigInt` – can be written as `-x`.
-- `x.divDecimal(y: BigDecimal): BigDecimal` – divides by a decimal, giving a decimal result.
-- `x.isZero(): bool` – Convenience for checking if the number is zero.
-- `x.isI32(): bool` – Check if the number fits in an `i32`.
-- `x.abs(): BigInt` – Absolute value.
+- `x.plus(y: BigInt): BigInt` – peut être écrit comme `x + y`.
+- `x.minus(y: BigInt): BigInt` – peut être écrit comme `x - y`.
+- `x.times(y: BigInt): BigInt` – peut être écrit comme `x * y`.
+- `x.div(y: BigInt): BigInt` – peut être écrit comme `x / y`.
+- `x.mod(y: BigInt): BigInt` – peut être écrit comme `x % y`.
+- `x.equals(y: BigInt): bool` – peut être écrit comme `x == y`.
+- `x.notEqual(y: BigInt): bool` – peut être écrit comme `x != y`.
+- `x.lt(y: BigInt): bool` – peut être écrit comme `x < y`.
+- `x.le(y: BigInt): bool` – peut être écrit comme `x <= y`.
+- `x.gt(y: BigInt): bool` – peut être écrit comme `x > y`.
+- `x.ge(y: BigInt): bool` – peut être écrit comme `x >= y`.
+- `x.neg(): BigInt` – peut être écrit comme `-x`.
+- `x.divDecimal(y: BigDecimal): BigDecimal` – divise par un nombre décimal, donnant un résultat décimal.
+- `x.isZero(): bool` – Est pratique pour vérifier si le nombre est zéro.
+- `x.isI32(): bool` – Vérifie si le nombre rentre dans un `i32`.
+- `x.abs(): BigInt` – Valeur absolue.
 - `x.pow(exp: u8): BigInt` – Exponentiation.
-- `bitOr(x: BigInt, y: BigInt): BigInt` – can be written as `x | y`.
-- `bitAnd(x: BigInt, y: BigInt): BigInt` – can be written as `x & y`.
-- `leftShift(x: BigInt, bits: u8): BigInt` – can be written as `x << y`.
-- `rightShift(x: BigInt, bits: u8): BigInt` – can be written as `x >> y`.
+- `bitOr(x: BigInt, y: BigInt): BigInt` – peut être écrit comme `x | y`.
+- `bitAnd(x: BigInt, y: BigInt): BigInt` – peut être écrit comme `x & y`.
+- `leftShift(x: BigInt, bits: u8): BigInt` – peut être écrit comme `x << y`.
+- `rightShift(x: BigInt, bits: u8): BigInt` – peut être écrit comme `x >> y`.
 
 #### TypedMap
 
@@ -164,15 +166,15 @@ _Math_
 import { TypedMap } from '@graphprotocol/graph-ts'
 ```
 
-`TypedMap` can be used to store key-value pairs. See [this example](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
+`TypedMap` peut être utilisé pour stocker des paires clé-valeur. Consultez [cet exemple](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
 
-The `TypedMap` class has the following API:
+La classe `TypedMap` possède l'API suivante :
 
-- `new TypedMap<K, V>()` – creates an empty map with keys of type `K` and values of type `V`
-- `map.set(key: K, value: V): void` – sets the value of `key` to `value`
-- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – returns the key-value pair for a `key` or `null` if the `key` does not exist in the map
-- `map.get(key: K): V | null` – returns the value for a `key` or `null` if the `key` does not exist in the map
-- `map.isSet(key: K): bool` – returns `true` if the `key` exists in the map and `false` if it does not
+- `new TypedMap<K, V>()` – crée une carte vide avec des clés de type `K` et des valeurs de type `V`
+- `map.set(key: K, value: V): void` – définit la valeur de `key` à `value`
+- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – renvoie la paire clé-valeur pour une `key` ou `null` si la `key` n'existe pas dans la carte
+- `map.get(key: K): V | null` – renvoie la valeur pour une `key` ou `null` si la `key` n'existe pas dans la carte
+- `map.isSet(key: K): bool` – renvoie `true` si la `key` existe dans la carte et `false` si ce n'est pas le cas
 
 #### Octets
 
@@ -180,25 +182,25 @@ The `TypedMap` class has the following API:
 import { Bytes } from '@graphprotocol/graph-ts'
 ```
 
-`Bytes` is used to represent arbitrary-length arrays of bytes. This includes Ethereum values of type `bytes`, `bytes32`, etc.
+`Bytes` est utilisé pour représenter des tableaux d'octets de longueur arbitraire. Ceci inclut les valeurs Ethereum de type `bytes`, `bytes32`, etc.
 
-The `Bytes` class extends AssemblyScript's [Uint8Array](https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) and this supports all the `Uint8Array` functionality, plus the following new methods:
+La classe `Bytes` hérite de [Uint8Array](https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) d'AssemblyScript et prend en charge toutes les fonctionnalités de `Uint8Array` ainsi que les nouvelles méthodes suivantes :
 
 _Construction_
 
-- `fromHexString(hex: string) : Bytes` - Convert the string `hex` which must consist of an even number of hexadecimal digits to a `ByteArray`. The string `hex` can optionally start with `0x`
-- `fromI32(i: i32) : Bytes` - Convert `i` to an array of bytes
+- `fromHexString(hex: string) : Bytes` - Convertit la chaîne de caractères `hex` qui doit comporter un nombre pair de chiffres hexadécimaux en un `ByteArray`. La chaîne de caractères `hex` peut de façon optionnelle commencer par `0x`
+- `fromI32(i: i32) : Bytes` - Convertit `i` en un tableau de d'octets
 
-_Type conversions_
+_Conversions de type_
 
-- `b.toHex()` – returns a hexadecimal string representing the bytes in the array
-- `b.toString()` – converts the bytes in the array to a string of unicode characters
-- `b.toBase58()` – turns an Ethereum Bytes value to base58 encoding (used for IPFS hashes)
+- `b.toHex()` – renvoie une chaîne de caractères hexadécimale représentant les octets dans le tableau
+- `b.toString()` – convertit les octets dans le tableau en une chaîne de caractères unicode
+- `b.toBase58()` – convertit une valeur Ethereum Bytes en codage de type base58 (utilisé pour les hachages IPFS)
 
-_Operators_
+_Operateurs_
 
-- `b.concat(other: Bytes) : Bytes` - - return new `Bytes` consisting of `this` directly followed by `other`
-- `b.concatI32(other: i32) : ByteArray` - return new `Bytes` consisting of `this` directly follow by the byte representation of `other`
+- `b.concat(other: Bytes) : Bytes` - - renvoie un nouveau `Bytes` constitué de `this` suivi directement de `other`
+- `b.concatI32(other: i32) : ByteArray` - renvoie un nouveau `Bytes` constitué de `this` suivi directement de la représentation en octets de `other`
 
 #### Addresse
 
@@ -206,12 +208,12 @@ _Operators_
 import { Address } du '@graphprotocol/graph-ts'
 ```
 
-`Address` extends `Bytes` to represent Ethereum `address` values.
+`Address` hérite de `Bytes` pour représenter les valeurs `address` d'Ethereum.
 
-It adds the following method on top of the `Bytes` API:
+Cela ajoute la méthode suivante en plus de l'API `Bytes` :
 
-- `Address.fromString(s: string): Address` – creates an `Address` from a hexadecimal string
-- `Address.fromBytes(b: Bytes): Address` – create an `Address` from `b` which must be exactly 20 bytes long. Passing in a value with fewer or more bytes will result in an error
+- `Address.fromString(s: string): Address` – crée une `Address` à partir d'une chaîne de caractères hexadécimale
+- `Address.fromBytes(b: Bytes): Address` – crée une `Address` à partir de `b` qui doit avoir exactement 20 octets de long. Passer une valeur avec moins ou plus d'octets entraînera une erreur
 
 ### Store API
 
@@ -219,9 +221,9 @@ It adds the following method on top of the `Bytes` API:
 import { store } from '@graphprotocol/graph-ts'
 ```
 
-The `store` API allows to load, save and remove entities from and to the Graph Node store.
+L'API `store` permet de charger, sauvegarder et supprimer des entités dans et depuis le magasin Graph Node.
 
-Entities written to the store map one-to-one to the `@entity` types defined in the subgraph's GraphQL schema. To make working with these entities convenient, the `graph codegen` command provided by the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) generates entity classes, which are subclasses of the built-in `Entity` type, with property getters and setters for the fields in the schema as well as methods to load and save these entities.
+Les entités écrites dans le magasin correspondent directement aux types `@entity` définis dans le schéma GraphQL du subgraph. Pour faciliter le travail avec ces entités, la commande `graph codegen` fournie par [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) génère des classes d'entités, qui sont des sous-classes du type `Entity` intégré, avec des accesseurs et des mutateurs pour les champs du schéma ainsi que des méthodes pour charger et sauvegarder ces entités.
 
 #### Création d'entités
 
@@ -250,9 +252,11 @@ export function handleTransfer(event: TransferEvent): void {
 }
 ```
 
-When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
+Lorsqu'un événement `Transfer` est rencontré lors du traitement de la blockchain, il est transmis au gestionnaire d'événements `handleTransfer` en utilisant le type `Transfer` généré (ayant pour pseudonyme `TransferEvent` ici pour éviter un conflit de nom avec le type d'entité). Ce type permet d'accéder à des données telles que la transaction parente de l'événement et ses paramètres.
+
+Chaque entité doit avoir un ID unique pour éviter les collisions avec d'autres entités. Il est assez courant que les paramètres des événements incluent un identifiant unique pouvant être utilisé.
 
-Chaque entité doit avoir un identifiant unique pour éviter les collisions avec d'autres entités. Il est assez courant que les paramètres d'événement incluent un identifiant unique pouvant être utilisé. Remarque : L'utilisation du hachage de transaction comme ID suppose qu'aucun autre événement dans la même transaction ne crée d'entités avec ce hachage comme ID.
+> Remarque : utiliser le hash de la transaction comme ID suppose qu'aucun autre événement dans la même transaction ne crée d'entités avec ce hash comme ID.
 
 #### Chargement d'entités depuis le magasin
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Utiliser l'entité Transfer comme précédemment
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+Comme l'entité peut ne pas encore exister dans le magasin, la méthode `load` renvoie une valeur de type `Transfer | null`. Il peut être nécessaire de vérifier le cas `null` avant d'utiliser la valeur.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Remarque : Le chargement des entités n'est nécessaire que si les modifications apportées dans le mappage dépendent des données précédentes d'une entité. Consultez la section suivante pour savoir les deux façons de mettre à jour les entités existantes.
 
 #### Recherche d'entités créées dans un bloc
 
-As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
+Depuis `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 et `@graphprotocol/graph-cli` v0.49.0 la méthode `loadInBlock` est disponible pour tous les types d'entités.
 
-L'API du magasin facilite la récupération des entités créées ou mises à jour dans le bloc actuel. Une situation typique est qu'un gestionnaire crée une transaction à partir d'un événement en chaîne et qu'un gestionnaire ultérieur souhaite accéder à cette transaction si elle existe. Dans le cas où la transaction n'existe pas, le ubgraph devra se rendre dans la base de données juste pour découvrir que l'entité n'existe pas ; si l'auteur du subgraph sait déjà que l'entité doit avoir été créée dans le même bloc, l'utilisation de loadInBlock évite cet aller-retour dans la base de données. Pour certains subgraphs, ces recherches manquées peuvent contribuer de manière significative au temps d'indexation.
+L'API store facilite la récupération des entités qui ont été créées ou mises à jour dans le bloc actuel. Une situation typique est qu'un gestionnaire crée une transaction à partir d'un événement on-chain, et qu'un gestionnaire ultérieur souhaite accéder à cette transaction si elle existe.
+
+- Dans le cas où la transaction n'existe pas, le subgraph devra interroger la base de données pour découvrir que l'entité n'existe pas. Si l'auteur du subgraph sait déjà que l'entité doit avoir été créée dans le même bloc, utiliser `loadInBlock` évite ce détour par la base de données.
+- Pour certains subgraphs, ces recherches infructueuses peuvent contribuer de manière significative au temps d'indexation.
 
 ```typescript
 let id = event.transaction.hash // ou de toute autre manière dont l'ID est construit
@@ -288,11 +295,11 @@ if (transfer == null) {
 // Utiliser l'entité Transfer comme auparavant
 ```
 
-> Note: If there is no entity created in the given block, `loadInBlock` will return `null` even if there is an entity with the given ID in the store.
+> Remarque : S'il n'y a pas d'entité créée dans le bloc donné, `loadInBlock` renverra `null` même s'il y a une entité avec l'ID donné dans le magasin.
 
 #### Recherche d'entités dérivées
 
-As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 and `@graphprotocol/graph-cli` v0.51.0 the `loadRelated` method is available.
+Depuis `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 et`@graphprotocol/graph-cli` v0.51.0 la méthode `loadRelated` est disponible.
 
 Cela permet de charger des champs d'entités dérivés à partir d'un gestionnaire d'événements. Par exemple, étant donné le schéma suivant :
 
@@ -309,7 +316,7 @@ type Holder @entity {
 }
 ```
 
-The following code will load the `Token` entity that the `Holder` entity was derived from:
+Le code suivant chargera l'entité `Token` dont l'entité `Holder`est dérivée :
 
 ```typescript
 let holder = Holder.load('test-id')
@@ -321,8 +328,8 @@ let tokens = holder.tokens.load()
 
 Il existe deux manières de mettre à jour une entité existante :
 
-1. Load the entity with e.g. `Transfer.load(id)`, set properties on the entity, then `.save()` it back to the store.
-2. Simply create the entity with e.g. `new Transfer(id)`, set properties on the entity, then `.save()` it to the store. If the entity already exists, the changes are merged into it.
+1. Chargez l'entité avec, par exemple, `Transfer.load(id)`, définissez des propriétés sur l'entité, puis `.save()` pour la sauvegarder dans le magasin.
+2. Créez simplement l'entité avec, par exemple, `new Transfer(id)`, séfinissez des propriétés sur l'entité, puis `.save()` pour la sauvegarder dans le magasin. Si l'entité existe déjà, les modifications y sont fusionnées.
 
 La modification des propriétés est simple dans la plupart des cas, grâce aux paramètres de propriétés générés :
 
@@ -340,9 +347,9 @@ transfer.from.unset()
 transfer.from = null
 ```
 
-This only works with optional properties, i.e. properties that are declared without a `!` in GraphQL. Two examples would be `owner: Bytes` or `amount: BigInt`.
+Ceci ne fonctionne qu'avec des propriétés optionnelles, c'est-à-dire des propriétés déclarées sans `!` dans GraphQL. Deux exemples seraient `owner: Bytes` ou `amount: BigInt`.
 
-Updating array properties is a little more involved, as the getting an array from an entity creates a copy of that array. This means array properties have to be set again explicitly after changing the array. The following assumes `entity` has a `numbers: [BigInt!]!` field.
+La mise à jour des propriétés de tableau est un peu plus complexe, car obtenir un tableau à partir d'une entité crée une copie de ce tableau. Cela signifie que les propriétés de tableau doivent être définies à nouveau explicitement après la modification du tableau. Ce qui suit suppose que `entity` a un champ `numbers: [BigInt!]!` .
 
 ```typescript
 // Cela ne fonctionnera pas
@@ -358,7 +365,7 @@ entity.save()
 
 #### Supprimer des entités du magasin
 
-There is currently no way to remove an entity via the generated types. Instead, removing an entity requires passing the name of the entity type and the entity ID to `store.remove`:
+Il n'y a actuellement aucun moyen de supprimer une entité via les types générés. Au lieu de cela, la suppression d'une entité nécessite de passer le nom du type d'entité et l'ID de l'entité à `store.remove`:
 
 ```typescript
 import { store } from '@graphprotocol/graph-ts'
@@ -373,9 +380,9 @@ L'API Ethereum donne accès aux contrats intelligents, aux variables d'état pub
 
 #### Prise en charge des types Ethereum
 
-As with entities, `graph codegen` generates classes for all smart contracts and events used in a subgraph. For this, the contract ABIs need to be part of the data source in the subgraph manifest. Typically, the ABI files are stored in an `abis/` folder.
+Comme pour les entités, `graph codegen` génère des classes pour tous les contrats intelligents et événements utilisés dans un subgraph. Pour cela, les ABIs des contrats doivent faire partie de la source de données dans le manifeste du subgraph. En général, les fichiers ABI sont stockés dans un dossier `abis/` .
 
-With the generated classes, conversions between Ethereum types and the [built-in types](#built-in-types) take place behind the scenes so that subgraph authors do not have to worry about them.
+Avec les classes générées, les conversions entre les types Ethereum et [les types intégrés](#built-in-types) se font en arrière-plan afin que les auteurs de subgraph n'aient pas à s'en soucier.
 
 L’exemple suivant illustre cela. Étant donné un schéma de subgraph comme
 
@@ -388,7 +395,7 @@ type Transfer @entity {
 }
 ```
 
-and a `Transfer(address,address,uint256)` event signature on Ethereum, the `from`, `to` and `amount` values of type `address`, `address` and `uint256` are converted to `Address` and `BigInt`, allowing them to be passed on to the `Bytes!` and `BigInt!` properties of the `Transfer` entity:
+et une signature d'événement `Transfer(address,address,uint256)` sur Ethereum, les valeurs `from`, `to` et`amount` de type `address`, `address` et `uint256` sont enverties en `Address` et `BigInt`, leur permettant d'être passées aux propriétés `Bytes!` et `BigInt!` de l'entité `Transfer` :
 
 ```typescript
 let id = event.transaction.hash
@@ -401,7 +408,7 @@ transfer.save()
 
 #### Événements et données de bloc/transaction
 
-Ethereum events passed to event handlers, such as the `Transfer` event in the previous examples, not only provide access to the event parameters but also to their parent transaction and the block they are part of. The following data can be obtained from `event` instances (these classes are a part of the `ethereum` module in `graph-ts`):
+Les événements Ethereum passés aux gestionnaires d'événements, comme l'événement `Transfer` dans les exemples précédents, fournissent non seulement l'accès aux paramètres de l'événement, mais également à leur transaction parente et au bloc auquel ils appartiennent. Les données suivantes peuvent être obtenues à partir des instances d' `event` (ces classes font partie du module `ethereum` dans `graph-ts`):
 
 ```typescript
 class Event {
@@ -476,7 +483,7 @@ class Log {
 
 #### Accès à l'état du contrat intelligent
 
-The code generated by `graph codegen` also includes classes for the smart contracts used in the subgraph. These can be used to access public state variables and call functions of the contract at the current block.
+Le code généré par `graph codegen` inclut également des classes pour les contrats intelligents utilisés dans le subgraph. Celles-ci peuvent être utilisées pour accéder aux variables d'état publiques et appeler des fonctions du contrat au bloc actuel.
 
 Un modèle courant consiste à accéder au contrat dont provient un événement. Ceci est réalisé avec le code suivant :
 
@@ -495,15 +502,17 @@ export function handleTransfer(event: TransferEvent) {
 }
 ```
 
-`Transfer` is aliased to `TransferEvent` here to avoid a naming conflict with the entity type
+`Transfer` est remplacé par `TransferEvent` ici pour éviter un conflit de nommage avec le type d'entité
 
-As long as the `ERC20Contract` on Ethereum has a public read-only function called `symbol`, it can be called with `.symbol()`. For public state variables a method with the same name is created automatically.
+Tant que le `ERC20Contract` sur Ethereum a une fonction publique en lecture seule appelée `symbol`, elle peut être appelée avec `.symbol()`. Pour les variables d'état publiques, une méthode du même nom est créée automatiquement.
 
 Tout autre contrat faisant partie du subgraph peut être importé à partir du code généré et peut être lié à une adresse valide.
 
 #### Gestion des appels retournés
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+Si les méthodes en lecture seule de votre contrat peuvent échouer, vous devez gérer cela en appelant la méthode de contrat générée préfixée par `try_`.
+
+- Par exemple, le contrat Gravity expose la méthode `gravatarToOwner` . Ce code serait capable de gérer une erreur dans cette méthode :
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,11 +524,11 @@ if (callResult.reverted) {
 }
 ```
 
-Notez qu'un nœud Graph connecté à un client Geth ou Infura peut ne pas détecter tous les retours, si vous comptez sur cela, nous vous recommandons d'utiliser un nœud Graph connecté à un client Parity.
+> Remarque : Un Graph Node connecté à un client Geth ou Infura peut ne pas détecter toutes les réversions (reverts). Si vous en dépendez, nous recommandons d'utiliser un Graph Node connecté à un client Parity.
 
 #### Encodage/décodage ABI
 
-Data can be encoded and decoded according to Ethereum's ABI encoding format using the `encode` and `decode` functions in the `ethereum` module.
+Les données peuvent être encodées et décodées selon le format de codage ABI d'Ethereum en utilisant les fonctions `encode` et `decode` du module `ethereum`.
 
 ```typescript
 import { Address, BigInt, ethereum } from '@graphprotocol/graph-ts'
@@ -538,33 +547,33 @@ let decoded = ethereum.decode('(address,uint256)', encoded)
 
 Pour plus d'informations:
 
-- [ABI Spec](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
-- Encoding/decoding [Rust library/CLI](https://github.com/rust-ethereum/ethabi)
-- More [complex example](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
+- [Spécifications ABI](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
+- Encodage/décodage [bibliothèque Rust/CLI] (https://github.com/rust-ethereum/ethabi)
+- Exemple [plus complexe](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
 
-#### Balance of an Address
+#### Solde d'une adresse
 
-The native token balance of an address can be retrieved using the `ethereum` module. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`. The `getBalance()` retrieves the balance of the specified address as of the end of the block in which the event is triggered.
+Le solde de jetons natifs d'une adresse peut être récupéré en utilisant le module `ethereum`. Cette fonctionnalité est disponible à partir de `apiVersion: 0.0.9` définie dans `subgraph.yaml`. La fonction `getBalance()` récupère le solde de l'adresse spécifiée à la fin du bloc où l'événement est déclenché.
 
 ```typescript
 import { ethereum } from '@graphprotocol/graph-ts'
 
 let address = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
-let balance = ethereum.getBalance(address) // returns balance in BigInt
+let balance = ethereum.getBalance(address) // renvoie le solde en BigInt
 ```
 
-#### Check if an Address is a Contract or EOA
+#### Vérifier si une adresse est une adresse de contrat intelligent ou une adresse détenue par des personnes (EOA)
 
-To check whether an address is a smart contract address or an externally owned address (EOA), use the `hasCode()` function from the `ethereum` module which will return `boolean`. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`.
+Pour vérifier si une adresse est une adresse de contrat intelligent ou une adresse détenue extérieurement (EOA), utilisez la fonction `hasCode()` du module `ethereum` qui retournera un `boolean`. Cette fonctionnalité est disponible à partir de `apiVersion: 0.0.9` qui est définie dans `subgraph.yaml`.
 
 ```typescript
 import { ethereum } from '@graphprotocol/graph-ts'
 
 let contractAddr = Address.fromString('0x2E645469f354BB4F5c8a05B3b30A929361cf77eC')
-let isContract = ethereum.hasCode(contractAddr).inner // returns true
+let isContract = ethereum.hasCode(contractAddr).inner // renvoie true
 
 let eoa = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
-let isContract = ethereum.hasCode(eoa).inner // returns false
+let isContract = ethereum.hasCode(eoa).inner // renvoie false
 ```
 
 ### Logging API
@@ -573,17 +582,17 @@ let isContract = ethereum.hasCode(eoa).inner // returns false
 import { log } from '@graphprotocol/graph-ts'
 ```
 
-The `log` API allows subgraphs to log information to the Graph Node standard output as well as Graph Explorer. Messages can be logged using different log levels. A basic format string syntax is provided to compose log messages from argument.
+L'API `log` permet aux subgraphs d'enregistrer des informations sur la sortie standard de Graph Node ainsi que sur Graph Explorer. Les messages peuvent être enregistrés en utilisant différents niveaux de journalisation. Une syntaxe de chaîne de caractère de format de base est fournie pour composer des messages de journal à partir de l'argument.
 
-The `log` API includes the following functions:
+L'API `log` inclut les fonctions suivantes :
 
-- `log.debug(fmt: string, args: Array<string>): void` - logs a debug message.
-- `log.info(fmt: string, args: Array<string>): void` - logs an informational message.
-- `log.warning(fmt: string, args: Array<string>): void` - logs a warning.
-- `log.error(fmt: string, args: Array<string>): void` - logs an error message.
-- `log.critical(fmt: string, args: Array<string>): void` – logs a critical message _and_ terminates the subgraph.
+- `log.debug(fmt: string, args: Array<string>): void` - enregistre un message de débogage.
+- `log.info(fmt: string, args: Array<string>): void` - enregistre un message d'information.
+- `log.warning(fmt: string, args: Array<string>): void` - enregistre un avertissement.
+- `log.error(fmt: string, args: Array<string>): void` - enregistre un message d'erreur.
+- `log.critical(fmt: string, args: Array<string>): void` – enregistre un message critique _et_ met fin au subgraph.
 
-The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
+L'API `log` prend une chaîne de caractères de format et un tableau de valeurs de chaîne de caractères. Elle remplace ensuite les espaces réservés par les valeurs de chaîne de caractères du tableau. Le premier espace réservé `{}` est remplacé par la première valeur du tableau, le second `{}` est remplacé par la deuxième valeur, et ainsi de suite.
 
 ```typescript
 log.info('Message à afficher : {}, {}, {}', [value.toString(), anotherValue.toString(), 'déjà une chaîne'])
@@ -593,7 +602,7 @@ log.info('Message à afficher : {}, {}, {}', [value.toString(), anotherValue.to
 
 ##### Enregistrer une seule valeur
 
-In the example below, the string value "A" is passed into an array to become`['A']` before being logged:
+Dans l'exemple ci-dessous, la valeur de chaîne de caractères "A" est passée dans un tableau pour devenir `['A']` avant d'être enregistrée:
 
 ```typescript
 let myValue = 'A'
@@ -619,7 +628,7 @@ export function handleSomeEvent(event: SomeEvent): void {
 
 #### Journalisation de plusieurs entrées d'un tableau existant
 
-Each entry in the arguments array requires its own placeholder `{}` in the log message string. The below example contains three placeholders `{}` in the log message. Because of this, all three values in `myArray` are logged.
+Chaque entrée dans le tableau des arguments nécessite son propre espace réservé `{}` dans la chaîne de caractères du message de log. L'exemple ci-dessous contient trois espaces réservés `{}` dans le message de log. À cause de cela, toutes les trois valeurs dans `myArray` sont enregistrées.
 
 ```typescript
 let myArray = ['A', 'B', 'C']
@@ -663,7 +672,7 @@ export function handleSomeEvent(event: SomeEvent): void {
 import { ipfs } from '@graphprotocol/graph-ts'
 ```
 
-Smart contracts occasionally anchor IPFS files on chain. This allows mappings to obtain the IPFS hashes from the contract and read the corresponding files from IPFS. The file data will be returned as `Bytes`, which usually requires further processing, e.g. with the `json` API documented later on this page.
+Les contrats intelligents ancrent occasionnellement des fichiers IPFS sur la blockchain. Cela permet aux mappages d'obtenir les hashs IPFS du contrat et de lire les fichiers correspondants à partir d'IPFS. Les données du fichier seront retournées sous forme de `Bytes`, ce qui nécessite généralement un traitement supplémentaire, par exemple avec l'API `json` documentée plus loin sur cette page.
 
 Étant donné un hachage ou un chemin IPFS, la lecture d'un fichier depuis IPFS se fait comme suit :
 
@@ -678,9 +687,9 @@ let path = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile'
 let data = ipfs.cat(path)
 ```
 
-**Note:** `ipfs.cat` is not deterministic at the moment. If the file cannot be retrieved over the IPFS network before the request times out, it will return `null`. Due to this, it's always worth checking the result for `null`.
+**Remarque:** `ipfs.cat` n'est pas déterministe pour le moment. Si le fichier ne peut pas être récupéré sur le réseau IPFS avant l'expiration de la demande, il retournera `null`. Pour cette raison, il est toujours utile de vérifier le résultat pour `null`.
 
-It is also possible to process larger files in a streaming fashion with `ipfs.map`. The function expects the hash or path for an IPFS file, the name of a callback, and flags to modify its behavior:
+Il est également possible de traiter des fichiers plus volumineux en streaming avec `ipfs.map`. La fonction s'attend à recevoir un hash ou à un chemin pour un fichier IPFS, le nom d'un callback, et des indicateurs pour modifier son comportement :
 
 ```typescript
 import { JSONValue, Value } from '@graphprotocol/graph-ts'
@@ -710,9 +719,9 @@ ipfs.map('Qm...', 'processItem', Value.fromString('parentId'), ['json'])
 ipfs.mapJSON('Qm...', 'processItem', Value.fromString('parentId'))
 ```
 
-The only flag currently supported is `json`, which must be passed to `ipfs.map`. With the `json` flag, the IPFS file must consist of a series of JSON values, one value per line. The call to `ipfs.map` will read each line in the file, deserialize it into a `JSONValue` and call the callback for each of them. The callback can then use entity operations to store data from the `JSONValue`. Entity changes are stored only when the handler that called `ipfs.map` finishes successfully; in the meantime, they are kept in memory, and the size of the file that `ipfs.map` can process is therefore limited.
+Le seul indicateur actuellement pris en charge est `json`, qui doit être passé à `ipfs.map`. Avec l'indicateur `json` , le fichier IPFS doit consister en une série de valeurs JSON, une valeur par ligne. L'appel à `ipfs.map` lira chaque ligne du fichier, la désérialisera en un `JSONValue` et appellera le callback pour chacune d'entre elles. Le callback peut alors utiliser des opérations des entités pour stocker des données à partir du `JSONValue`. Les modifications d'entité ne sont enregistrées que lorsque le gestionnaire qui a appelé `ipfs.map` se termine avec succès ; en attendant, elles sont conservées en mémoire, et la taille du fichier que `ipfs.map` peut traiter est donc limitée.
 
-On success, `ipfs.map` returns `void`. If any invocation of the callback causes an error, the handler that invoked `ipfs.map` is aborted, and the subgraph is marked as failed.
+En cas de succès, `ipfs.map` renvoie `void`. Si une invocation du callback provoque une erreur, le gestionnaire qui a invoqué `ipfs.map` est interrompu et le subgraph marqué comme échoué.
 
 ### Crypto API
 
@@ -720,7 +729,7 @@ On success, `ipfs.map` returns `void`. If any invocation of the callback causes
 import { crypto } from '@graphprotocol/graph-ts'
 ```
 
-The `crypto` API makes a cryptographic functions available for use in mappings. Right now, there is only one:
+L'API `crypto` rend des fonctions cryptographiques disponibles pour une utilisation dans les mappages. Actuellement, il n'y en a qu'une seule :
 
 - `crypto.keccak256(input: ByteArray): ByteArray`
 
@@ -730,14 +739,14 @@ The `crypto` API makes a cryptographic functions available for use in mappings.
 import { json, JSONValueKind } from '@graphprotocol/graph-ts'
 ```
 
-JSON data can be parsed using the `json` API:
+Les données JSON peuvent être analysées en utilisant l'API `json`:
 
-- `json.fromBytes(data: Bytes): JSONValue` – parses JSON data from a `Bytes` array interpreted as a valid UTF-8 sequence
-- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – safe version of `json.fromBytes`, it returns an error variant if the parsing failed
-- `json.fromString(data: string): JSONValue` – parses JSON data from a valid UTF-8 `String`
-- `json.try_fromString(data: string): Result<JSONValue, boolean>` – safe version of `json.fromString`, it returns an error variant if the parsing failed
+- `json.fromBytes(data: Bytes): JSONValue` – analyse les données JSON à partir d'un tableau `Bytes` interprété comme une séquence UTF-8 valide
+- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – version sécurisée de `json.fromBytes`, elle renvoie une variante d'erreur si l'analyse échoue
+- `json.fromString(data: string): JSONValue` – analyse les données JSON à partir d'une `String` UTF-8 valide
+- `json.try_fromString(data: string): Result<JSONValue, boolean>` – version sécurisée de `json.fromString`, elle renvoie une variante d'erreur si l'analyse échoue
 
-The `JSONValue` class provides a way to pull values out of an arbitrary JSON document. Since JSON values can be booleans, numbers, arrays and more, `JSONValue` comes with a `kind` property to check the type of a value:
+La classe `JSONValue` fournit un moyen d'extraire des valeurs d'un document JSON arbitraire. Étant donné que les valeurs JSON peuvent être des booléens, des nombres, des tableaux et plus encore, `JSONValue` est accompagné d'une propriété `kind` pour vérifier le type d'une valeur :
 
 ```typescript
 let value = json.fromBytes(...)
@@ -746,63 +755,63 @@ if (value.kind == JSONValueKind.BOOL) {
 }
 ```
 
-In addition, there is a method to check if the value is `null`:
+De plus, il existe une méthode pour vérifier si la valeur est `null`:
 
 - `value.isNull(): boolean`
 
-When the type of a value is certain, it can be converted to a [built-in type](#built-in-types) using one of the following methods:
+Lorsque le type d'une valeur est certain, il peut être converti en un [type intégré](#built-in-types) n utilisant l'une des méthodes suivantes :
 
 - `value.toBool(): boolean`
 - `value.toI64(): i64`
 - `value.toF64(): f64`
 - `value.toBigInt(): BigInt`
 - `value.toString(): string`
-- `value.toArray(): Array<JSONValue>` - (and then convert `JSONValue` with one of the 5 methods above)
+- `value.toArray(): Array<JSONValue>` - (et ensuite convertir `JSONValue` avec l'une des 5 méthodes ci-dessus)
 
 ### Référence des conversions de types
 
-| Source(s)            | Destination          | Conversion function          |
-| -------------------- | -------------------- | ---------------------------- |
-| Address              | Bytes                | none                         |
-| Address              | String               | s.toHexString()              |
-| BigDecimal           | String               | s.toString()                 |
-| BigInt               | BigDecimal           | s.toBigDecimal()             |
-| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex() |
-| BigInt               | String (unicode)     | s.toString()                 |
-| BigInt               | i32                  | s.toI32()                    |
-| Boolean              | Boolean              | none                         |
-| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
-| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)  |
-| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex() |
-| Bytes                | String (unicode)     | s.toString()                 |
-| Bytes                | String (base58)      | s.toBase58()                 |
-| Bytes                | i32                  | s.toI32()                    |
-| Bytes                | u32                  | s.toU32()                    |
-| Bytes                | JSON                 | json.fromBytes(s)            |
-| int8                 | i32                  | none                         |
-| int32                | i32                  | none                         |
-| int32                | BigInt               | BigInt.fromI32(s)            |
-| uint24               | i32                  | none                         |
-| int64 - int256       | BigInt               | none                         |
-| uint32 - uint256     | BigInt               | none                         |
-| JSON                 | boolean              | s.toBool()                   |
-| JSON                 | i64                  | s.toI64()                    |
-| JSON                 | u64                  | s.toU64()                    |
-| JSON                 | f64                  | s.toF64()                    |
-| JSON                 | BigInt               | s.toBigInt()                 |
-| JSON                 | string               | s.toString()                 |
-| JSON                 | Array                | s.toArray()                  |
-| JSON                 | Object               | s.toObject()                 |
-| String               | Address              | Address.fromString(s)        |
-| Bytes                | Address              | Address.fromBytes(s)         |
-| String               | BigInt               | BigInt.fromString(s)         |
-| String               | BigDecimal           | BigDecimal.fromString(s)     |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
+| Source(s)             | Destination          | Fonctions de conversion          |
+| --------------------- | -------------------- | -------------------------------- |
+| Address               | Bytes                | aucune                           |
+| Address               | String               | s.toHexString()                  |
+| BigDecimal            | String               | s.toString()                     |
+| BigInt                | BigDecimal           | s.toBigDecimal()                 |
+| BigInt                | String (hexadecimal) | s.toHexString() or s.toHex()     |
+| BigInt                | String (unicode)     | s.toString()                     |
+| BigInt                | i32                  | s.toI32()                        |
+| Boolean               | Boolean              | aucune                           |
+| Bytes (signé)         | BigInt               | BigInt.fromSignedBytes(s)        |
+| Bytes (non signé)     | BigInt               | BigInt.fromUnsignedBytes(s)      |
+| Bytes                 | String (hexadecimal) | s.toHexString() or s.toHex()     |
+| Bytes                 | String (unicode)     | s.toString()                     |
+| Bytes                 | String (base58)      | s.toBase58()                     |
+| Bytes                 | i32                  | s.toI32()                        |
+| Bytes                 | u32                  | s.toU32()                        |
+| Bytes                 | JSON                 | json.fromBytes(s)                |
+| int8                  | i32                  | aucune                           |
+| int32                 | i32                  | aucune                           |
+| int32                 | BigInt               | BigInt.fromI32(s)                |
+| uint24                | i32                  | aucune                           |
+| int64 - int256        | BigInt               | aucune                           |
+| uint32 - uint256      | BigInt               | aucune                           |
+| JSON                  | boolean              | s.toBool()                       |
+| JSON                  | i64                  | s.toI64()                        |
+| JSON                  | u64                  | s.toU64()                        |
+| JSON                  | f64                  | s.toF64()                        |
+| JSON                  | BigInt               | s.toBigInt()                     |
+| JSON                  | string               | s.toString()                     |
+| JSON                  | Array                | s.toArray()                      |
+| JSON                  | Object               | s.toObject()                     |
+| String                | Address              | Address.fromString(s)            |
+| Bytes                 | Address              | Address.fromBytes(s)             |
+| String                | BigInt               | BigInt.fromString(s)             |
+| String                | BigDecimal           | BigDecimal.fromString(s)         |
+| String (hexadecimal)  | Bytes                | ByteArray.fromHexString(s)       |
+| String (UTF-8)        | Bytes                | ByteArray.fromUTF8(s)            |
 
 ### Métadonnées de la source de données
 
-You can inspect the contract address, network and context of the data source that invoked the handler through the `dataSource` namespace:
+Vous pouvez inspecter l'adresse du contrat, le réseau et le contexte de la source de données qui a invoqué le gestionnaire grâce un namespace `dataSource` :
 
 - `dataSource.address(): Address`
 - `dataSource.network(): string`
@@ -810,7 +819,7 @@ You can inspect the contract address, network and context of the data source tha
 
 ### Entité et DataSourceContext
 
-The base `Entity` class and the child `DataSourceContext` class have helpers to dynamically set and get fields:
+La classe de base `Entity` et la classe enfant `DataSourceContext` disposent d'assistants pour définir et récupérer dynamiquement des champs :
 
 - `setString(key: string, value: string): void`
 - `setI32(key: string, value: i32): void`
@@ -827,9 +836,9 @@ The base `Entity` class and the child `DataSourceContext` class have helpers to
 
 ### DataSourceContext in Manifest
 
-The `context` section within `dataSources` allows you to define key-value pairs that are accessible within your subgraph mappings. The available types are `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`.
+La section `context` de `dataSources` vous permet de définir des paires clé-valeur qui sont accessibles dans vos mappages de subgraphs. Les types disponibles sont `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, et `BigInt`.
 
-Here is a YAML example illustrating the usage of various types in the `context` section:
+Voici un exemple YAML illustrant l'utilisation de différents types dans la section `context` :
 
 ```yaml
 dataSources:
@@ -869,13 +878,13 @@ dataSources:
         data: '1000000000000000000000000'
 ```
 
-- `Bool`: Specifies a Boolean value (`true` or `false`).
-- `String`: Specifies a String value.
-- `Int`: Specifies a 32-bit integer.
-- `Int8`: Specifies an 8-bit integer.
-- `BigDecimal`: Specifies a decimal number. Must be quoted.
-- `Bytes`: Specifies a hexadecimal string.
-- `List`: Specifies a list of items. Each item needs to specify its type and data.
-- `BigInt`: Specifies a large integer value. Must be quoted due to its large size.
+- `Bool` : Spécifie une valeur booléenne (`true` ou `false`).
+- `String` : Spécifie une valeur de type chaîne de caractères.
+- `Int` : Spécifie un nombre entier de 32 bits.
+- `Int8` : Spécifie un entier de 8 bits.
+- `BigDecimal` : Spécifie un nombre décimal. Doit être entre mis guillemets.
+- `Bytes` : Spécifie une chaîne de caractères hexadécimale.
+- `List` : Spécifie une liste d'éléments. Chaque élément doit spécifier son type et ses données.
+- `BigInt` : Spécifie une grande valeur entière. Elle doit être mise entre guillemets en raison de sa grande taille.
 
 Ce contexte est ensuite accessible dans vos fichiers de mappage de subgraphs, permettant des subgraphs plus dynamiques et configurables.

From 4589d661f27562136f94c05276eb0c30e279531a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:16 -0500
Subject: [PATCH 0129/1325] New translations delete-a-subgraph.mdx (Swedish)

---
 website/pages/sv/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/sv/managing/delete-a-subgraph.mdx b/website/pages/sv/managing/delete-a-subgraph.mdx
index 68ef0a37da75..eb286c4e4fc3 100644
--- a/website/pages/sv/managing/delete-a-subgraph.mdx
+++ b/website/pages/sv/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- Kuratorer kommer inte längre kunna signalera på subgrafet.
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 08f47056317146749137f405da70040012e695da Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:17 -0500
Subject: [PATCH 0130/1325] New translations delete-a-subgraph.mdx (Turkish)

---
 website/pages/tr/managing/delete-a-subgraph.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/website/pages/tr/managing/delete-a-subgraph.mdx b/website/pages/tr/managing/delete-a-subgraph.mdx
index 68ef0a37da75..02bef8483798 100644
--- a/website/pages/tr/managing/delete-a-subgraph.mdx
+++ b/website/pages/tr/managing/delete-a-subgraph.mdx
@@ -6,10 +6,12 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 
 > Deleting your subgraph will remove all published versions from The Graph Network, but it will remain visible on Graph Explorer and Subgraph Studio for users who have signaled on it.
 
-## Step-by-Step
+## Adım Adım
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Küratörler artık subgraph'e sinyal veremeyecek.
+- Subgraph'e halihazırda sinyal vermiş küratörler, sinyallerini ortalama hisse fiyatından geri çekebilir.
 - Deleted subgraphs will show an error message.

From 1a8d44ec87e34c990bda78533b968e0f25cac214 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:18 -0500
Subject: [PATCH 0131/1325] New translations delete-a-subgraph.mdx (Ukrainian)

---
 website/pages/uk/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/uk/managing/delete-a-subgraph.mdx b/website/pages/uk/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/uk/managing/delete-a-subgraph.mdx
+++ b/website/pages/uk/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From e1581691101a444de02ab26d2850af88493ed1d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:19 -0500
Subject: [PATCH 0132/1325] New translations delete-a-subgraph.mdx (Chinese
 Simplified)

---
 website/pages/zh/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/zh/managing/delete-a-subgraph.mdx b/website/pages/zh/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1b2d8ab4ba7b 100644
--- a/website/pages/zh/managing/delete-a-subgraph.mdx
+++ b/website/pages/zh/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- 策展人将无法再对该子图发出信号。
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 60b96202bddcd39e231055a2483307f21381d67f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:20 -0500
Subject: [PATCH 0133/1325] New translations delete-a-subgraph.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/ur/managing/delete-a-subgraph.mdx b/website/pages/ur/managing/delete-a-subgraph.mdx
index 68ef0a37da75..c58c2c829e1d 100644
--- a/website/pages/ur/managing/delete-a-subgraph.mdx
+++ b/website/pages/ur/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- کیوریٹرز اب سب گراف پر سگنل نہیں دے سکیں گے.
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 9ffbfa5cd58a32147b7deb6080bfa3d06a36ec63 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:21 -0500
Subject: [PATCH 0134/1325] New translations delete-a-subgraph.mdx (Vietnamese)

---
 website/pages/vi/managing/delete-a-subgraph.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/vi/managing/delete-a-subgraph.mdx b/website/pages/vi/managing/delete-a-subgraph.mdx
index 68ef0a37da75..1807741026ae 100644
--- a/website/pages/vi/managing/delete-a-subgraph.mdx
+++ b/website/pages/vi/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)

From 7525a09aea742fca75982bc22185e3c0ed5a6b20 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:22 -0500
Subject: [PATCH 0135/1325] New translations delete-a-subgraph.mdx (Marathi)

---
 website/pages/mr/managing/delete-a-subgraph.mdx | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/website/pages/mr/managing/delete-a-subgraph.mdx b/website/pages/mr/managing/delete-a-subgraph.mdx
index 68ef0a37da75..e8b5118eb2fc 100644
--- a/website/pages/mr/managing/delete-a-subgraph.mdx
+++ b/website/pages/mr/managing/delete-a-subgraph.mdx
@@ -9,7 +9,9 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ## Step-by-Step
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
+- क्युरेटर यापुढे सबग्राफवर सिग्नल करू शकणार नाहीत.
 - Curators that already signaled on the subgraph can withdraw their signal at an average share price.
 - Deleted subgraphs will show an error message.

From 506be9457aa7cc8d052028e64d62313b8403fdb9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:22 -0500
Subject: [PATCH 0136/1325] New translations delete-a-subgraph.mdx (Hindi)

---
 website/pages/hi/managing/delete-a-subgraph.mdx | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/website/pages/hi/managing/delete-a-subgraph.mdx b/website/pages/hi/managing/delete-a-subgraph.mdx
index 68ef0a37da75..e30dcc591775 100644
--- a/website/pages/hi/managing/delete-a-subgraph.mdx
+++ b/website/pages/hi/managing/delete-a-subgraph.mdx
@@ -6,10 +6,12 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 
 > Deleting your subgraph will remove all published versions from The Graph Network, but it will remain visible on Graph Explorer and Subgraph Studio for users who have signaled on it.
 
-## Step-by-Step
+## चरण-दर-चरण
 
 1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
 2. Click on the three-dots to the right of the "publish" button.
+
 3. Click on the option to "delete this subgraph":
 
    ![Delete-subgraph](/img/Delete-subgraph.png)
@@ -24,6 +26,6 @@ Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
 ### Important Reminders
 
 - Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- क्यूरेटर अब सबग्राफ पर संकेत नहीं दे पाएंगे।
+- Subgraph पर पहले से संकेत कर चुके Curators औसत शेयर मूल्य पर अपना संकेत वापस ले सकते हैं।
 - Deleted subgraphs will show an error message.

From d920e4f146b0f72a85b5a94a6c219c98149ecd52 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:24 -0500
Subject: [PATCH 0137/1325] New translations delete-a-subgraph.mdx (Swahili)

---
 .../pages/sw/managing/delete-a-subgraph.mdx   | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 website/pages/sw/managing/delete-a-subgraph.mdx

diff --git a/website/pages/sw/managing/delete-a-subgraph.mdx b/website/pages/sw/managing/delete-a-subgraph.mdx
new file mode 100644
index 000000000000..1807741026ae
--- /dev/null
+++ b/website/pages/sw/managing/delete-a-subgraph.mdx
@@ -0,0 +1,31 @@
+---
+title: Delete a Subgraph
+---
+
+Delete your subgraph using [Subgraph Studio](https://thegraph.com/studio/).
+
+> Deleting your subgraph will remove all published versions from The Graph Network, but it will remain visible on Graph Explorer and Subgraph Studio for users who have signaled on it.
+
+## Step-by-Step
+
+1. Visit the subgraph's page on [Subgraph Studio](https://thegraph.com/studio/).
+
+2. Click on the three-dots to the right of the "publish" button.
+
+3. Click on the option to "delete this subgraph":
+
+   ![Delete-subgraph](/img/Delete-subgraph.png)
+
+4. Depending on the subgraph's status, you will be prompted with various options.
+
+   - If the subgraph is not published, simply click “delete” and confirm.
+   - If the subgraph is published, you will need to confirm on your wallet before the subgraph can be deleted from Studio. If a subgraph is published to multiple networks, such as testnet and mainnet, additional steps may be required.
+
+> If the owner of the subgraph has signal on it, the signaled GRT will be returned to the owner.
+
+### Important Reminders
+
+- Once you delete a subgraph, it will **not** appear on Graph Explorer's homepage. However, users who have signaled on it will still be able to view it on their profile pages and remove their signal.
+- Curators will not be able to signal on the subgraph anymore.
+- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
+- Deleted subgraphs will show an error message.

From 64233bfb63eea62be48fd4eb47a18b781db112c3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:25 -0500
Subject: [PATCH 0138/1325] New translations subgraphs.mdx (Romanian)

---
 website/pages/ro/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/ro/subgraphs.mdx b/website/pages/ro/subgraphs.mdx
index 27b452211477..42c1e806f822 100644
--- a/website/pages/ro/subgraphs.mdx
+++ b/website/pages/ro/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 4ca6bc20592cd70c0b62eda28c93771e4aea1c6e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:26 -0500
Subject: [PATCH 0139/1325] New translations transfer-to-the-graph.mdx
 (Romanian)

---
 website/pages/ro/cookbook/transfer-to-the-graph.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/ro/cookbook/transfer-to-the-graph.mdx b/website/pages/ro/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..6a5d2c2793f3 100644
--- a/website/pages/ro/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/ro/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 

From 787cebd916e3b490f03390cc85a1db717326300c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:27 -0500
Subject: [PATCH 0140/1325] New translations advanced.mdx (Romanian)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/ro/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/ro/developing/creating-a-subgraph/advanced.mdx b/website/pages/ro/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..3a08ddab7066
--- /dev/null
+++ b/website/pages/ro/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 7338b78bfcf9abe979aa809e0bb1bdfa0a508ab6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:28 -0500
Subject: [PATCH 0141/1325] New translations assemblyscript-mappings.mdx
 (Romanian)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/ro/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/ro/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ro/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/ro/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From d657a926a6f6bbea1cc24699a47b09459816b7d2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:29 -0500
Subject: [PATCH 0142/1325] New translations install-the-cli.mdx (Romanian)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..7da774ac392c
--- /dev/null
+++ b/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Creează un Subgraf
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 7b7f8883f79f9f53b2eb7bdf12695574095100bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:30 -0500
Subject: [PATCH 0143/1325] New translations ql-schema.mdx (Romanian)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From e7d52fc68261bab0735e1ac1d3b396f8b3dbcd0c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:31 -0500
Subject: [PATCH 0144/1325] New translations subgraph-manifest.mdx (Romanian)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/ro/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/ro/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ro/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..f282f3946e75
--- /dev/null
+++ b/website/pages/ro/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From f718e7e5de92202976615c95b8f83aa9495a23c8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:32 -0500
Subject: [PATCH 0145/1325] New translations transfer-to-the-graph.mdx (French)

---
 .../pages/fr/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/fr/cookbook/transfer-to-the-graph.mdx b/website/pages/fr/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..3ffe317f8063 100644
--- a/website/pages/fr/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/fr/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Exemple
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Ressources additionnelles
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 4e59cd64d0a05863e806aa94c78b7118a0d981fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:33 -0500
Subject: [PATCH 0146/1325] New translations advanced.mdx (French)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/fr/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/fr/developing/creating-a-subgraph/advanced.mdx b/website/pages/fr/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..7416cd495bcf
--- /dev/null
+++ b/website/pages/fr/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Aperçu
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Séries chronologiques et agrégations
+
+Les séries chronologiques et les agrégations permettent à votre subgraph de suivre des statistiques telles que le prix moyen journalier, le total des transferts par heure, etc.
+
+Cette fonctionnalité introduit deux nouveaux types d'entités de subgraph. Les entités de séries chronologiques enregistrent des points de données avec des horodatages. Les entités d'agrégation effectuent des calculs pré-déclarés sur les points de données des séries chronologiques sur une base horaire ou quotidienne, puis stockent les résultats pour un accès facile via GraphQL.
+
+### Exemple de schéma
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Définition des Séries Chronologiques et des Agrégations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Intervalles d'Agrégation disponibles
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Fonctions d'Agrégation disponibles
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Exemple de requête d'Agrégations
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Remarque:
+
+Pour utiliser les Séries Chronologiques et les Agrégations, un subgraph doit avoir une spec Version ≥1.1.0. Notez que cette fonctionnalité pourrait subir des changements significatifs affectant la compatibilité rétroactive.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Erreurs non fatales
+
+Les erreurs d'indexation sur les subgraphs déjà synchronisés entraîneront, par défaut, l'échec du subgraph et l'arrêt de la synchronisation. Les subgraphs peuvent également être configurés pour continuer la synchronisation en présence d'erreurs, en ignorant les modifications apportées par le gestionnaire qui a provoqué l'erreur. Cela donne aux auteurs de subgraphs le temps de corriger leurs subgraphs pendant que les requêtes continuent d'être traitées sur le dernier bloc, bien que les résultats puissent être incohérents en raison du bogue à l'origine de l'erreur. Notez que certaines erreurs sont toujours fatales. Pour être non fatale, l'erreur doit être connue pour être déterministe.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+L'activation des erreurs non fatales nécessite la définition de l'indicateur de fonctionnalité suivant sur le manifeste du subgraph :
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## File Data Sources de fichiers IPFS/Arweave
+
+Les sources de données de fichiers sont une nouvelle fonctionnalité de subgraph permettant d'accéder aux données hors chaîne pendant l'indexation de manière robuste et extensible. Les sources de données de fichiers prennent en charge la récupération de fichiers depuis IPFS et Arweave.
+
+> Cela jette également les bases d’une indexation déterministe des données hors chaîne, ainsi que de l’introduction potentielle de données arbitraires provenant de HTTP.
+
+### Aperçu
+
+Plutôt que de récupérer les fichiers "ligne par ligne" pendant l'exécution du gestionnaire, ceci introduit des modèles qui peuvent être générés comme nouvelles sources de données pour un identifiant de fichier donné. Ces nouvelles sources de données récupèrent les fichiers, réessayant en cas d'échec, et exécutant un gestionnaire dédié lorsque le fichier est trouvé.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Guide de mise à niveau
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Ajouter un nouveau type d'entité qui sera mis à jour lorsque des fichiers seront trouvés
+
+Les sources de données de fichier ne peuvent pas accéder ni mettre à jour les entités basées sur une chaîne, mais doivent mettre à jour les entités spécifiques au fichier.
+
+Cela peut impliquer de diviser les champs des entités existantes en entités distinctes, liées entre elles.
+
+Entité combinée d'origine :
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Nouvelle entité scindée :
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Si la relation est 1:1 entre l'entité parent et l'entité de source de données de fichier résultante, le modèle le plus simple consiste à lier l'entité parent à une entité de fichier résultante en utilisant le CID IPFS comme recherche. Contactez Discord si vous rencontrez des difficultés pour modéliser vos nouvelles entités basées sur des fichiers !
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Il s'agit de la source de données qui sera générée lorsqu'un fichier d'intérêt est identifié.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Créer un nouveau gestionnaire pour traiter les fichiers
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Exemple de gestionnaire :
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Générer des sources de données de fichiers si nécessaire
+
+Vous pouvez désormais créer des sources de données de fichiers lors de l'exécution de gestionnaires basés sur une chaîne :
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+L'exemple:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//Cet exemple de code concerne un sous-graphe de Crypto coven. Le hachage ipfs ci-dessus est un répertoire contenant les métadonnées des jetons pour toutes les NFT de l'alliance cryptographique.
+
+export function handleTransfer(event : TransferEvent) : void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //Ceci crée un chemin vers les métadonnées pour un seul Crypto coven NFT. Il concatène le répertoire avec "/" + nom de fichier + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+Cela créera une nouvelle source de données de fichier, qui interrogera le point d'extrémité IPFS ou Arweave configuré du nœud de graphique, en réessayant si elle n'est pas trouvée. Lorsque le fichier est trouvé, le gestionnaire de la source de données de fichier est exécuté.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Félicitations, vous utilisez des sources de données de fichiers !
+
+#### Déployer vos subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+Les entités et les gestionnaires de sources de données de fichiers sont isolés des autres entités du subgraph, ce qui garantit que leur exécution est déterministe et qu'il n'y a pas de contamination des sources de données basées sur des chaînes. Pour être plus précis :
+
+- Les entités créées par les sources de données de fichiers sont immuables et ne peuvent pas être mises à jour
+- Les gestionnaires de sources de données de fichiers ne peuvent pas accéder à des entités provenant d'autres sources de données de fichiers
+- Les entités associées aux sources de données de fichiers ne sont pas accessibles aux gestionnaires basés sur des chaînes
+
+> Cette contrainte ne devrait pas poser de problème pour la plupart des cas d'utilisation, mais elle peut en compliquer certains. N'hésitez pas à nous contacter via Discord si vous rencontrez des problèmes pour modéliser vos données basées sur des fichiers dans un subgraph !
+
+En outre, il n'est pas possible de créer des sources de données à partir d'une source de données de fichier, qu'il s'agisse d'une source de données onchain ou d'une autre source de données de fichier. Cette restriction pourrait être levée à l'avenir.
+
+#### Meilleures pratiques
+
+Si vous liez des métadonnées NFT aux jetons correspondants, utilisez le hachage IPFS des métadonnées pour référencer une entité Metadata à partir de l'entité Token. Enregistrez l'entité Metadata en utilisant le hachage IPFS comme identifiant.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Nous travaillons à l'amélioration de la recommandation ci-dessus, afin que les requêtes ne renvoient que la version "la plus récente"
+
+#### Problèmes connus
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Exemples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Les Références
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Filtres d'Arguments indexés / Filtres de Topics
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Les filtres de topics, également connus sous le nom de filtres d'arguments indexés, sont une fonctionnalité puissante dans les subgraphs qui permettent aux utilisateurs de filtrer précisément les événements de la blockchain en fonction des valeurs de leurs arguments indexés.
+
+- Ces filtres aident à isoler des événements spécifiques intéressants parmi le vaste flux d'événements sur la blockchain, permettant aux subgraphs de fonctionner plus efficacement en se concentrant uniquement sur les données pertinentes.
+
+- Ceci est utile pour créer des subgraphs personnels qui suivent des adresses spécifiques et leurs interactions avec divers contrats intelligents sur la blockchain.
+
+### Comment fonctionnent les filtres de Topics
+
+Lorsqu'un contrat intelligent émet un événement, tous les arguments marqués comme indexés peuvent être utilisés comme filtres dans le manifeste d'un subgraph. Ceci permet au subgraph d'écouter de façon sélective les événements qui correspondent à ces arguments indexés.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Déclaration de l'événement avec des paramètres indexés pour les adresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Fonction pour simuler le transfert de tokens
+    function transfer(address to, uint256 value) public {
+        // Emission de l'événement Transfer avec from, to, et value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+Dans cet exemple:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration dans les subgraphs
+
+Les filtres de topics sont définis directement dans la configuration du gestionnaire d'évènement situé dans le manifeste du subgraph. Voici comment ils sont configurés :
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+Dans cette configuration :
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Chaque topic peut avoir une ou plusieurs valeurs, et un événement n'est traité que s'il correspond à l'une des valeurs de chaque rubrique spécifiée.
+
+#### Logique des Filtres
+
+- Au sein d'une même Topic: La logique fonctionne comme une condition OR. L'événement sera traité s'il correspond à l'une des valeurs listées dans une rubrique donnée.
+- Entre différents Topics: La logique fonctionne comme une condition AND. Un événement doit satisfaire toutes les conditions spécifiées à travers les différents topics pour déclencher le gestionnaire associé.
+
+#### Exemple 1 : Suivi des transferts directs de l'adresse A à l'adresse B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+Dans cette configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Exemple 2 : Suivi des transactions dans les deux sens entre deux ou plusieurs adresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+Dans cette configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- Le subgraph indexera les transactions qui se produisent dans les deux sens entre plusieurs adresses, permettant une surveillance complète des interactions impliquant toutes les adresses.
+
+## Déclaration eth_call
+
+> Remarque : Il s'agit d'une fonctionnalité expérimentale qui n'est pas encore disponible dans une version stable de Graph Node. Vous ne pouvez l'utiliser que dans Subgraph Studio ou sur votre nœud auto-hébergé.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+Cette fonctionnalité permet de :
+
+- Améliorer de manière significative les performances de la récupération des données de la blockchain Ethereum en réduisant le temps total pour plusieurs appels et en optimisant l'efficacité globale du subgraph.
+- Permet une récupération plus rapide des données, entraînant des réponses de requête plus rapides et une meilleure expérience utilisateur.
+- Réduire les temps d'attente pour les applications qui doivent réunir des données de plusieurs appels Ethereum, rendant le processus de récupération des données plus efficace.
+
+### Concepts clés
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Exécution en parallèle : Au lieu d'attendre la fin d'un appel avant de commencer le suivant, plusieurs appels peuvent être initiés simultanément.
+- Efficacité temporelle : Le temps total nécessaire pour tous les appels passe de la somme des temps d'appel individuels (séquentiels) au temps pris par l'appel le plus long (parallèle).
+
+#### Scenario without Declarative `eth_calls`
+
+Imaginez que vous ayez un subgraph qui doit effectuer trois appels Ethereum pour récupérer des données sur les transactions, le solde et les avoirs en jetons d'un utilisateur.
+
+Traditionnellement, ces appels pourraient être effectués de manière séquentielle :
+
+1. Appel 1 (Transactions) : Prend 3 secondes
+2. Appel 2 (Solde) : Prend 2 secondes
+3. Appel 3 (Avoirs en jetons) : Prend 4 secondes
+
+Temps total pris = 3 + 2 + 4 = 9 secondes
+
+#### Scenario with Declarative `eth_calls`
+
+Avec cette fonctionnalité, vous pouvez déclarer que ces appels soient exécutés en parallèle :
+
+1. Appel 1 (Transactions) : Prend 3 secondes
+2. Appel 2 (Solde) : Prend 2 secondes
+3. Appel 3 (Avoirs en jetons) : Prend 4 secondes
+
+Puisque ces appels sont exécutés en parallèle, le temps total pris est égal au temps pris par l'appel le plus long.
+
+Temps total pris = max (3, 2, 4) = 4 secondes
+
+#### Comment ça marche
+
+1. Définition déclarative : Dans le manifeste du subgraph, vous déclarez les appels Ethereum d'une manière indiquant qu'ils peuvent être exécutés en parallèle.
+2. Moteur d'exécution parallèle : Le moteur d'exécution de Graph Node reconnaît ces déclarations et exécute les appels simultanément.
+3. Agrégation des résultats : Une fois que tous les appels sont terminés, les résultats sont réunis et utilisés par le subgraph pour un traitement ultérieur.
+
+#### Exemple de configuration dans le manifeste du subgraph
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Détails pour l'exemple ci-dessus :
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Greffe sur des subgraphs existants
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Étant donné que le greffage copie plutôt que l'indexation des données de base, il est beaucoup plus rapide d'amener le susgraph dans le bloc souhaité que l'indexation à partir de zéro, bien que la copie initiale des données puisse encore prendre plusieurs heures pour de très gros subgraphs. Pendant l'initialisation du subgraph greffé, le nœud graphique enregistrera des informations sur les types d'entités qui ont déjà été copiés.
+
+Le subgraph greffé peut utiliser un schéma GraphQL qui n'est pas identique à celui du subgraph de base, mais simplement compatible avec celui-ci. Il doit s'agir d'un schéma de subgraph valide à part entière, mais il peut s'écarter du schéma du subgraph de base des manières suivantes :
+
+- Il ajoute ou supprime des types d'entités
+- Il supprime les attributs des types d'entités
+- Il ajoute des attributs nullables aux types d'entités
+- Il transforme les attributs non nullables en attributs nullables
+- Il ajoute des valeurs aux énumérations
+- Il ajoute ou supprime des interfaces
+- Cela change pour quels types d'entités une interface est implémentée
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 78bf181942d85db0fd923f8d701f1603acff5dcf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:34 -0500
Subject: [PATCH 0147/1325] New translations assemblyscript-mappings.mdx
 (French)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/fr/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/fr/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/fr/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..22d69907dbd2
--- /dev/null
+++ b/website/pages/fr/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Aperçu
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Écriture de mappages
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### ID recommandés pour la création de nouvelles entités
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Traitement des entités ayant des identifiants identiques
+
+Lors de la création et de l'enregistrement d'une nouvelle entité, si une entité avec le même ID existe déjà, les propriétés de la nouvelle entité sont toujours préférées lors du processus de fusion. Cela signifie que l'entité existante sera mise à jour avec les valeurs de la nouvelle entité.
+
+Si une valeur nulle est intentionnellement définie pour un champ de la nouvelle entité avec le même ID, l'entité existante sera mise à jour avec la valeur nulle.
+
+Si aucune valeur n'est définie pour un champ de la nouvelle entité avec le même ID, le champ aura également la valeur null.
+
+## Génération de code
+
+Afin de faciliter et de sécuriser le travail avec les contrats intelligents, les événements et les entités, la CLI Graph peut générer des types AssemblyScript à partir du schéma GraphQL du subgraph et des ABI de contrat inclus dans les sources de données.
+
+Cela se fait avec
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // La classe de contrat :
+  Gravity,
+  // Les classes d'événements :
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 4c79d72d01487886ca0b5fd16d9c5cc792fff5ee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:35 -0500
Subject: [PATCH 0148/1325] New translations install-the-cli.mdx (French)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..b96964966bb9
--- /dev/null
+++ b/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Installation du Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Aperçu
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Démarrage
+
+### Installation du Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+Sur votre machine locale, exécutez l'une des commandes suivantes :
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Créer un subgraph
+
+### À partir d'un contrat existant
+
+La commande suivante crée un subgraph qui indexe tous les événements d'un contrat existant :
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- La commande tente de récupérer l'ABI du contrat depuis Etherscan.
+
+  - Graph CLI repose sur un endpoint RPC public. Bien que des échecs occasionnels soient attendus, les réessais résolvent généralement ce problème. Si les échecs persistent, envisagez d'utiliser un ABI local.
+
+- Si certains arguments optionnels manquent, il vous guide à travers un formulaire interactif.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### À partir d'un exemple de subgraph
+
+La commande suivante initialise un nouveau projet à partir d'un exemple de subgraph :
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Spécificités⁠
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Récupération des ABIs
+
+Le(s) fichier(s) ABI doivent correspondre à votre(vos) contrat(s). Il existe plusieurs façons d'obtenir des fichiers ABI :
+
+- Si vous construisez votre propre projet, vous aurez probablement accès à vos ABI les plus récents.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## Versions disponibles de SpecVersion
+
+| Version | Notes de version                                                                                                                                                         |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Ajout de la prise en charge des gestionnaires d'événement ayant accès aux reçus de transactions.                                                                         |
+|  0.0.4  | Ajout de la prise en charge du management des fonctionnalités de subgraph.                                                                                               |

From 533746bc7507ec05dbe7ec12d9f8eb644c5bccdd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:36 -0500
Subject: [PATCH 0149/1325] New translations ql-schema.mdx (French)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..cbf7c64078a3
--- /dev/null
+++ b/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Aperçu
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Définition des entités
+
+Avant de définir des entités, il est important de prendre du recul et de réfléchir à la manière dont vos données sont structurées et liées.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- Il peut être utile d'imaginer les entités comme des "objets contenant des données", plutôt que comme des événements ou des fonctions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- Par défaut, les entités sont mutables, ce qui signifie que les mappages peuvent charger des entités existantes, les modifier et stocker une nouvelle version de cette entité.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - Si des changements se produisent dans le même bloc où l'entité a été créée, alors les mappages peuvent effectuer des changements sur les entités immuables. Les entités immuables sont beaucoup plus rapides à écrire et à interroger, donc elles devraient être utilisées chaque fois que c'est possible.
+
+#### Bon exemple
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Mauvais exemple
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Champs facultatifs et obligatoires
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Types scalaires intégrés
+
+#### Scalaires pris en charge par GraphQL
+
+Les scalaires suivants sont supportés dans l'API GraphQL :
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Tableau d'octets, représenté sous forme de chaîne hexadécimale. Couramment utilisé pour les hachages et adresses Ethereum.                                                                                       |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+Vous pouvez également créer des énumérations dans un schéma. Les énumérations ont la syntaxe suivante :
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Relations entre entités
+
+Une entité peut avoir une relation avec une ou plusieurs autres entités de votre schéma. Ces relations pourront être parcourues dans vos requêtes. Les relations dans The Graph sont unidirectionnelles. Il est possible de simuler des relations bidirectionnelles en définissant une relation unidirectionnelle à chaque « extrémité » de la relation.
+
+Les relations sont définies sur les entités comme n'importe quel autre champ sauf que le type spécifié est celui d'une autre entité.
+
+#### Relations individuelles
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Relations un-à-plusieurs
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Recherches inversées
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+Pour les relations un-à-plusieurs, la relation doit toujours être stockée du côté « un » et le côté « plusieurs » doit toujours être dérivé. Stocker la relation de cette façon, plutôt que de stocker un tableau d'entités du côté « plusieurs », entraînera des performances considérablement meilleures pour l'indexation et l'interrogation du sous-graphe. En général, le stockage de tableaux d’entités doit être évité autant que possible.
+
+#### Exemple
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Relations plusieurs-à-plusieurs
+
+Pour les relations plusieurs-à-plusieurs, telles que les utilisateurs pouvant appartenir à un nombre quelconque d'organisations, la manière la plus simple, mais généralement pas la plus performante, de modéliser la relation consiste à créer un tableau dans chacune des deux entités impliquées. Si la relation est symétrique, un seul côté de la relation doit être stocké et l’autre côté peut être dérivé.
+
+#### Exemple
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Cette approche nécessite que les requêtes descendent vers un niveau supplémentaire pour récupérer, par exemple, les organisations des utilisateurs :
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+       # ceci est une entité UserOrganization
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Cette manière plus élaborée de stocker des relations plusieurs-à-plusieurs entraînera moins de données stockées pour le subgraph, et donc vers un subgraph qui est souvent considérablement plus rapide à indexer et à interroger.
+
+### Ajouter des commentaires au schéma
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # identifiant unique et clé primaire de l'entité
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Définir les champs de recherche en texte intégral
+
+Les requêtes de recherche en texte intégral filtrent et classent les entités en fonction d'une entrée de recherche de texte. Les requêtes en texte intégral sont capables de renvoyer des correspondances pour des mots similaires en traitant le texte de la requête saisi en radicaux avant de les comparer aux données textuelles indexées.
+
+Une définition de requête en texte intégrale inclut le nom de la requête, le dictionnaire de langue utilisé pour traiter les champs de texte, l'algorithme de classement utilisé pour classer les résultats et les champs inclus dans la recherche. Chaque requête en texte intégral peut s'étendre sur plusieurs champs, mais tous les champs inclus doivent provenir d'un seul type d'entité.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Langues prises en charge
+
+Le choix d'une langue différente aura un effet définitif, bien que parfois subtil, sur l'API de recherche en texte intégral. Les champs couverts par un champ de requête en texte intégral sont examinés dans le contexte de la langue choisie, de sorte que les lexèmes produits par les requêtes d'analyse et de recherche varient d'une langue à l'autre. Par exemple : lorsque vous utilisez le dictionnaire turc pris en charge, "token" est dérivé de "toke", tandis que, bien sûr, le dictionnaire anglais le dérivera de "token".
+
+Dictionnaires de langues pris en charge :
+
+| Code   | Dictionnaire |
+| ------ | ------------ |
+| simple | General      |
+| da     | Danish       |
+| nl     | Dutch        |
+| en     | English      |
+| fi     | Finnish      |
+| fr     | French       |
+| de     | German       |
+| hu     | Hungarian    |
+| it     | Italian      |
+| no     | Norwegian    |
+| pt     | Portugais    |
+| ro     | Romanian     |
+| ru     | Russian      |
+| es     | Spanish      |
+| sv     | Swedish      |
+| tr     | Turkish      |
+
+### Algorithmes de classement
+
+Algorithmes de classement:
+
+| Algorithm     | Description                                                                                           |
+| ------------- | ----------------------------------------------------------------------------------------------------- |
+| rank          | Utilisez la qualité de correspondance (0-1) de la requête en texte intégral pour trier les résultats. |
+| proximitéRang | Similar to rank but also includes the proximity of the matches.                                       |

From 046df4b3985710bc96ac676df22f178aeedc56b6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:37 -0500
Subject: [PATCH 0150/1325] New translations subgraph-manifest.mdx (French)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/fr/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/fr/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/fr/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..a7c76c52d491
--- /dev/null
+++ b/website/pages/fr/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Aperçu
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+Un seul subgraph peut :
+
+- Indexer les données de plusieurs contrats intelligents (mais pas de plusieurs réseaux).
+
+- Indexer des données de fichiers IPFS en utilisant des File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+version spec : 0.0.4
+description : Gravatar pour Ethereum
+référentiel : https://github.com/graphprotocol/graph-tooling
+schéma:
+   fichier : ./schema.graphql
+indexeurConseils :
+   tailler : automatique
+les sources de données:
+   - genre : ethereum/contrat
+     nom: Gravité
+     réseau : réseau principal
+     source:
+       adresse : '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+       abi : Gravité
+       bloc de démarrage : 6175244
+       bloc de fin : 7175245
+     contexte:
+       foo :
+         tapez : Booléen
+         données : vrai
+       bar:
+         tapez : chaîne
+         données : 'barre'
+     cartographie :
+       genre : ethereum/événements
+       Version api : 0.0.6
+       langage : wasm/assemblyscript
+       entités :
+         -Gravatar
+       abis :
+         - nom : Gravité
+           fichier : ./abis/Gravity.json
+       Gestionnaires d'événements :
+         - événement : NewGravatar(uint256,adresse,chaîne,chaîne)
+           gestionnaire : handleNewGravatar
+         - événement : UpdatedGravatar (uint256, adresse, chaîne, chaîne)
+           gestionnaire : handleUpdatedGravatar
+       Gestionnaires d'appels :
+         - fonction : createGravatar(string,string)
+           gestionnaire : handleCreateGravatar
+       gestionnaires de blocs :
+         - gestionnaire : handleBlock
+         - gestionnaire : handleBlockWithCall
+           filtre:
+             genre : appeler
+       fichier : ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Les entrées importantes à mettre à jour pour le manifeste sont :
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Gestionnaires d'événements
+
+Les gestionnaires d'événements dans un subgraph réagissent à des événements spécifiques émis par des contrats intelligents sur la blockchain et déclenchent des gestionnaires définis dans le manifeste du subgraph. Ceci permet aux subgraphs de traiter et de stocker les données des événements selon une logique définie.
+
+### Définition d'un gestionnaire d'événements
+
+Un gestionnaire d'événements est déclaré dans une source de données dans la configuration YAML du subgraph. Il spécifie quels événements écouter et la fonction correspondante à exécuter lorsque ces événements sont détectés.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Filtre de rubrique optionnel qui filtre uniquement les événements avec la rubrique spécifiée.
+```
+
+## Gestionnaires d'appels
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Les gestionnaires d'appels ne se déclencheront que dans l'un des deux cas suivants : lorsque la fonction spécifiée est appelée par un compte autre que le contrat lui-même ou lorsqu'elle est marquée comme externe dans Solidity et appelée dans le cadre d'une autre fonction du même contrat.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Définir un gestionnaire d'appels
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Fonction de cartographie
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+En plus de s'abonner à des événements de contrat ou à des appels de fonction, un subgraph peut souhaiter mettre à jour ses données à mesure que de nouveaux blocs sont ajoutés à la chaîne. Pour y parvenir, un subgraph peut exécuter une fonction après chaque bloc ou après des blocs correspondant à un filtre prédéfini.
+
+### Filtres pris en charge
+
+#### Filtre d'appel
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+L'absence de filtre pour un gestionnaire de bloc garantira que le gestionnaire est appelé à chaque bloc. Une source de données ne peut contenir qu'un seul gestionnaire de bloc pour chaque type de filtre.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Filtre d'interrogation
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Le filtre Once
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Le gestionnaire défini avec le filtre once ne sera appelé qu'une seule fois avant l'exécution de tous les autres gestionnaires. Cette configuration permet au subgraph d'utiliser le gestionnaire comme gestionnaire d'initialisation, effectuant des tâches spécifiques au début de l'indexation.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Fonction de cartographie
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Événements anonymes
+
+Si vous devez traiter des événements anonymes dans Solidity, cela peut être réalisé en fournissant le sujet 0 de l'événement, comme dans l'exemple :
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Reçus de transaction dans les gestionnaires d'événements
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Ordre de déclenchement des gestionnaires
+
+Les déclencheurs d'une source de données au sein d'un bloc sont classés à l'aide du processus suivant :
+
+1. Les déclencheurs d'événements et d'appels sont d'abord classés par index de transaction au sein du bloc.
+2. Les déclencheurs d'événements et d'appels au sein d'une même transaction sont classés selon une convention : les déclencheurs d'événements d'abord, puis les déclencheurs d'appel, chaque type respectant l'ordre dans lequel ils sont définis dans le manifeste.
+3. Les déclencheurs de bloc sont exécutés après les déclencheurs d'événement et d'appel, dans l'ordre dans lequel ils sont définis dans le manifeste.
+
+Ces règles de commande sont susceptibles de changer.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Modèles de sources de données
+
+Un modèle courant dans les contrats intelligents compatibles EVM est l'utilisation de contrats de registre ou d'usine, dans lesquels un contrat crée, gère ou référence un nombre arbitraire d'autres contrats qui ont chacun leur propre état et leurs propres événements.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Source de données pour le contrat principal
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Modèles de source de données pour les contrats créés dynamiquement
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instanciation d'un modèle de source de données
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Commence à indexer l'échange ; `event.params.exchange` est le
+  // adresse du nouveau contrat d'échange
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Si les blocs précédents contiennent des données pertinentes pour la nouvelle source de données, il est préférable d'indexer ces données en lisant l'état actuel du contrat et en créant des entités représentant cet état au moment de la création de la nouvelle source de données.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Blocs de démarrage
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Recherchez le contrat en saisissant son adresse dans la barre de recherche.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Chargez la page des détails de la transaction où vous trouverez le bloc de départ de ce contrat.
+
+## Conseils pour l'indexeur
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. Un nombre spécifique : Fixe une limite personnalisée au nombre de blocs historiques à conserver.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> Le terme "historique" dans ce contexte des subgraphs concerne le stockage des données qui reflètent les anciens états des entités mutables.
+
+L'historique à partir d'un bloc donné est requis pour :
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rembobiner le subgraph jusqu'à ce bloc
+
+Si les données historiques à partir du bloc ont été purgées, les capacités ci-dessus ne seront pas disponibles.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+Pour conserver une quantité spécifique de données historiques :
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+Préserver l'histoire complète des États de l'entité :
+
+```
+indexerHints:
+  prune: never
+```

From cefcdb70960cc0872bd7e82aa9f8b4ed99c7f6a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:38 -0500
Subject: [PATCH 0151/1325] New translations index.json (Arabic)

---
 website/pages/ar/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/ar/index.json b/website/pages/ar/index.json
index f09f7bdca0b3..ef9526840c44 100644
--- a/website/pages/ar/index.json
+++ b/website/pages/ar/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "استكشف ال Subgraphsوتفاعل مع البروتوكول"
-      },
-      "hostedService": {
-        "title": "الخدمة المستضافة (Hosted Service)",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From f50d5ae099c1797cfebc1a71dc9690e84e9aeb24 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:39 -0500
Subject: [PATCH 0152/1325] New translations index.json (Czech)

---
 website/pages/cs/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/cs/index.json b/website/pages/cs/index.json
index a1bae4af6a25..4dd97a91d425 100644
--- a/website/pages/cs/index.json
+++ b/website/pages/cs/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Průzkumník grafů",
         "description": "Prozkoumání podgrafů a interakce s protokolem"
-      },
-      "hostedService": {
-        "title": "Hostovaná služba",
-        "description": "Vytváření a zkoumání podgrafů v hostované službě"
       }
     }
   },

From 51a0d6672497b8365dd93a65a94054f0b6bf540f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:40 -0500
Subject: [PATCH 0153/1325] New translations index.json (German)

---
 website/pages/de/index.json | 10 +++-------
 1 file changed, 3 insertions(+), 7 deletions(-)

diff --git a/website/pages/de/index.json b/website/pages/de/index.json
index 79b15c8d3ca4..a3d38b854804 100644
--- a/website/pages/de/index.json
+++ b/website/pages/de/index.json
@@ -1,5 +1,5 @@
 {
-  "title": "Get Started",
+  "title": "Los geht’s",
   "intro": "Learn about The Graph, a decentralized protocol for indexing and querying data from blockchains.",
   "shortcuts": {
     "aboutTheGraph": {
@@ -56,16 +56,12 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explore subgraphs and interact with the protocol"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },
   "supportedNetworks": {
     "title": "Supported Networks",
-    "description": "The Graph supports the following networks.",
-    "footer": "For more details, see the {0} page."
+    "description": "The Graph unterstützt folgende Netzwerke.",
+    "footer": "Weitere Einzelheiten finden Sie auf der Seite {0}."
   }
 }

From 3e7138810454d7d26eadfd45e829d341b4206dab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:41 -0500
Subject: [PATCH 0154/1325] New translations index.json (Italian)

---
 website/pages/it/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/it/index.json b/website/pages/it/index.json
index ae779150a432..10b8c6a7f7c2 100644
--- a/website/pages/it/index.json
+++ b/website/pages/it/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explore subgraphs and interact with the protocol"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 5d149d0022d10765f1d551834a321e8bd25a1af6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:42 -0500
Subject: [PATCH 0155/1325] New translations about.mdx (Arabic)

---
 website/pages/ar/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/ar/about.mdx b/website/pages/ar/about.mdx
index 7ac49dc47560..7660b0dfd54b 100644
--- a/website/pages/ar/about.mdx
+++ b/website/pages/ar/about.mdx
@@ -2,46 +2,66 @@
 title: حول The Graph
 ---
 
-هذه الصفحة ستشرح The Graph وكيف يمكنك أن تبدأ.
-
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-المشاريع ذات العقود الذكية المعقدة مثل [ Uniswap ](https://uniswap.org/) و NFTs مثل [ Bored Ape Yacht Club ](https://boredapeyachtclub.com/) تقوم بتخزين البيانات على Ethereum blockchain ، مما يجعل من الصعب قراءة أي شيء بشكل مباشر عدا البيانات الأساسية من blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+### How The Graph Functions
 
-**إن فهرسة بيانات الـ blockchain أمر صعب.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## كيف يعمل The Graph
+- 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.
 
-The Graph يفهرس بيانات الإيثيريوم بناء على أوصاف الـ subgraph ، والمعروفة باسم subgraph manifest. حيث أن وصف الـ subgraph يحدد العقود الذكية ذات الأهمية لـ subgraph ، ويحدد الأحداث في تلك العقود التي يجب الانتباه إليها ، وكيفية عمل map لبيانات الحدث إلى البيانات التي سيخزنها The Graph في قاعدة البيانات الخاصة به.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-بمجرد كتابة `subgraph manifest` ، يمكنك استخدام Graph CLI لتخزين التعريف في IPFS وإخبار المفهرس ببدء فهرسة البيانات لذلك الـ subgraph.
+- 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+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 بمسح الـ Ethereum باستمرار بحثا عن الكتل الجديدة وبيانات الـ subgraph الخاص بك.
-4. يعثر الـ Graph Node على أحداث الـ Ethereum لـ subgraph الخاص بك في هذه الكتل ويقوم بتشغيل mapping handlers التي قدمتها. الـ mapping عبارة عن وحدة WASM والتي تقوم بإنشاء أو تحديث البيانات التي يخزنها Graph Node استجابة لأحداث الـ Ethereum.
-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.
+1.  A dapp adds data to Ethereum through a transaction on a smart contract.
+2.  العقد الذكي يصدر حدثا واحدا أو أكثر أثناء معالجة الإجراء.
+3.  يقوم الـ Graph Node بمسح الـ Ethereum باستمرار بحثا عن الكتل الجديدة وبيانات الـ subgraph الخاص بك.
+4.  يعثر الـ Graph Node على أحداث الـ Ethereum لـ subgraph الخاص بك في هذه الكتل ويقوم بتشغيل mapping handlers التي قدمتها. الـ mapping عبارة عن وحدة WASM والتي تقوم بإنشاء أو تحديث البيانات التي يخزنها Graph Node استجابة لأحداث الـ Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 3bc0b6bf2320e59d356574d731353f0176e54580 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:44 -0500
Subject: [PATCH 0156/1325] New translations near.mdx (Arabic)

---
 website/pages/ar/cookbook/near.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/ar/cookbook/near.mdx b/website/pages/ar/cookbook/near.mdx
index 68089d21c7c4..73428b6f6fd5 100644
--- a/website/pages/ar/cookbook/near.mdx
+++ b/website/pages/ar/cookbook/near.mdx
@@ -27,13 +27,13 @@ title: بناء Subgraphs على NEAR
 
 `graphprotocol/graph-ts@` هي مكتبة لأنواع خاصة بـ subgraph.
 
-تطوير NEAR subgraph يتطلب `graph-cli` بإصدار أعلى من `0.23.0` و `graph-ts` بإصدار أعلى من `0.23.0`.
+تطوير NEAR subgraph يتطلب `graph-cli` بإصدار أعلى من ` 0.23.0 ` و `graph-ts` بإصدار أعلى من ` 0.23.0 `.
 
 > Building a NEAR subgraph is very similar to building a subgraph that indexes Ethereum.
 
 هناك ثلاثة جوانب لتعريف الـ subgraph:
 
-**subgraph.yaml:** الـ subgraph manifest ، وتحديد مصادر البيانات ذات الأهمية ، وكيف يجب أن تتم معالجتها.علما أن NEAR هو `نوع` جديد لمصدر البيانات.
+**subgraph.yaml:** الـ subgraph manifest ، وتحديد مصادر البيانات ذات الأهمية ، وكيف يجب أن تتم معالجتها.علما أن NEAR هو ` نوع ` جديد لمصدر البيانات.
 
 **schema.graphql:** a schema file that defines what data is stored for your subgraph, and how to query it via GraphQL. The requirements for NEAR subgraphs are covered by [the existing documentation](/developing/creating-a-subgraph#the-graphql-schema).
 
@@ -163,7 +163,7 @@ class ReceiptWithOutcome {
 These types are passed to block & receipt handlers:
 
 - معالجات الكتلة ستتلقى`Block`
-- معالجات الاستلام ستتلقى`ReceiptWithOutcome`
+- معالجات الاستلام ستتلقى` ReceiptWithOutcome `
 
 Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 1d56f88139bdb08217ebf1e473a194f0eaea26c5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:45 -0500
Subject: [PATCH 0157/1325] New translations unit-testing-framework.mdx
 (Arabic)

---
 .../ar/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/ar/developing/unit-testing-framework.mdx b/website/pages/ar/developing/unit-testing-framework.mdx
index 67407f8349be..67c565e95df8 100644
--- a/website/pages/ar/developing/unit-testing-framework.mdx
+++ b/website/pages/ar/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: اختبار وحدة Framework
 ---
 
-Matchstick هو اختبار وحدة framework ، تم تطويره بواسطة [ LimeChain ](https://limechain.tech/) ، والذي يسمح لمطوري الـ subgraph من اختبار منطق الـ mapping في بيئة sandboxed ونشر الـ subgraphs الخاصة بهم بثقة!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### الاستخدام
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## مصادر إضافية
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 63877fe250f7074e0be641a6307215ecfe44ee34 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:46 -0500
Subject: [PATCH 0158/1325] New translations about.mdx (Czech)

---
 website/pages/cs/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/cs/about.mdx b/website/pages/cs/about.mdx
index 5e95320d27d4..e29bcf5fe650 100644
--- a/website/pages/cs/about.mdx
+++ b/website/pages/cs/about.mdx
@@ -2,46 +2,66 @@
 title: O Grafu
 ---
 
-Tato stránka vysvětlí, co je The Graph a jak můžete začít.
-
 ## Co je Graf?
 
-Grafu je decentralizovaný protokol pro indexování a dotazování dat blockchainu. Graf umožňuje dotazovat se na data, která je obtížné dotazovat přímo.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Projekty se složitými chytrými smlouvami, jako je [Uniswap](https://uniswap.org/), a iniciativy NFT, jako je [Bored Ape Yacht Club](https://boredapeyachtclub.com/), ukládají data do blockchainu Etherea, takže je opravdu obtížné číst cokoli jiného než základní data přímo z blockchainu.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-Můžete si také vytvořit vlastní server, zpracovávat na něm transakce, ukládat je do databáze a nad tím vším vytvořit koncový bod API pro dotazování na data. Tato možnost je však [náročná na zdroje](/network/benefits/), vyžaduje údržbu, představuje jediný bod selhání a porušuje důležité bezpečnostní vlastnosti potřebné pro decentralizaci.
+### How The Graph Functions
 
-**Indexování blockchainových dat je opravdu, ale opravdu těžké.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Jak funguje graf
+- 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.
 
-Grafu se učí, co a jak indexovat data Ethereu, m na základě popisů podgrafů, známých jako manifest podgrafu. Popis podgrafu definuje chytré smlouvy, které jsou pro podgraf zajímavé, události v těchto smlouvách, kterým je třeba věnovat pozornost, a způsob mapování dat událostí na data, která Grafu uloží do své databáze.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Jakmile napíšete `manifest podgrafu`, použijete Graph CLI k uložení definice do IPFS a řeknete indexeru, aby začal indexovat data pro tento podgraf.
+- 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.
 
-Tento diagram podrobněji popisuje tok dat po nasazení podgraf manifestu, který se zabývá transakcemi Ethereum:
+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. Uzel grafu neustále vyhledává nové bloky Ethereum a data pro váš podgraf, která mohou obsahovat.
-4. Uzel grafu v těchto blocích vyhledá události Etherea pro váš podgraf a spustí vámi zadané mapovací obsluhy. Mapování je modul WASM, který vytváří nebo aktualizuje datové entity, které Uzel grafu ukládá v reakci na události Ethereum.
-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.
+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.  Uzel grafu neustále vyhledává nové bloky Ethereum a data pro váš podgraf, která mohou obsahovat.
+4.  Uzel grafu v těchto blocích vyhledá události Etherea pro váš podgraf a spustí vámi zadané mapovací obsluhy. Mapování je modul WASM, který vytváří nebo aktualizuje datové entity, které Uzel grafu ukládá v reakci na události Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Než začnete psát vlastní podgraf, můžete se podívat do [Graph Explorer](https://thegraph.com/explorer) a prozkoumat některé z již nasazených podgrafů. Stránka každého podgrafu obsahuje hřiště, které vám umožní dotazovat se na data daného podgrafu pomocí GraphQL.
+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.

From 7aee11df1b59fa23fe79efd39ba5c78540ba52f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:47 -0500
Subject: [PATCH 0159/1325] New translations near.mdx (Czech)

---
 website/pages/cs/cookbook/near.mdx | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/website/pages/cs/cookbook/near.mdx b/website/pages/cs/cookbook/near.mdx
index 3044e8d66d81..ac95d0149954 100644
--- a/website/pages/cs/cookbook/near.mdx
+++ b/website/pages/cs/cookbook/near.mdx
@@ -6,7 +6,7 @@ Tato příručka je úvodem do vytváření subgrafů indexujících chytré kon
 
 ## Co je NEAR?
 
-[NEAR](https://near.org/) is a smart contract platform for building decentralized applications. Visit the [official documentation](https://docs.near.org/concepts/basics/protocol) for more information.
+[NEAR](https://near.org/) je platforma pro chytré smlouvy, která slouží k vytváření decentralizovaných aplikací. Další informace najdete v [oficiální dokumentaci](https://docs.near.org/concepts/basics/protocol).
 
 ## Co jsou podgrafy NEAR?
 
@@ -17,7 +17,7 @@ Podgrafy jsou založeny na událostech, což znamená, že naslouchají událost
 - Obsluhy bloků: jsou spouštěny při každém novém bloku.
 - Obsluhy příjmu: spouštějí se pokaždé, když je zpráva provedena na zadaném účtu.
 
-[From the NEAR documentation](https://docs.near.org/build/data-infrastructure/lake-data-structures/receipt):
+[Z dokumentace NEAR](https://docs.near.org/build/data-infrastructure/lake-data-structures/receipt):
 
 > Příjemka je jediným objektem, který lze v systému použít. Když na platformě NEAR hovoříme o "zpracování transakce", znamená to v určitém okamžiku "použití účtenky".
 
@@ -37,7 +37,7 @@ Definice podgrafů má tři aspekty:
 
 **schema.graphql:** soubor se schématem, který definuje, jaká data jsou uložena pro váš podgraf, a jak je možné je dotazovat pomocí GraphQL. Požadavky na podgrafy NEAR jsou pokryty [existující dokumentací](/developing/creating-a-subgraph#the-graphql-schema).
 
-**Mapování v jazyce AssemblyScript:** [Kód jazyka AssemblyScript](/developing/graph-ts/api), který převádí data událostí na entity definované ve vašem schématu. Podpora NEAR zavádí datové typy specifické pro NEAR a nové funkce pro parsování JSON.
+**Mapování AssemblyScript:** [Kód AssemblyScript](/developing/graph-ts/api), který převádí data událostí na entity definované ve vašem schématu. Podpora NEAR zavádí datové typy specifické pro NEAR a nové funkce pro parsování JSON.
 
 Při vývoji podgrafů existují dva klíčové příkazy:
 
@@ -71,8 +71,8 @@ dataSources:
 ```
 
 - Podgrafy NEAR představují nový `druh` zdroje dat (`near`)
-- The `network` should correspond to a network on the hosting Graph Node. On Subgraph Studio, NEAR's mainnet is `near-mainnet`, and NEAR's testnet is `near-testnet`
-- NEAR data sources introduce an optional `source.account` field, which is a human-readable ID corresponding to a [NEAR account](https://docs.near.org/concepts/protocol/account-model). This can be an account or a sub-account.
+- `Síť` by měla odpovídat síti v hostitelském uzlu Graf. V Podgraf Studio je hlavní síť NEAR `near-mainnet` a testovací síť NEAR je `near-testnet`
+- Zdroje dat NEAR zavádějí volitelné pole `source.account`, které je čitelným ID odpovídajícím [účtu NEAR](https://docs.near.org/concepts/protocol/account-model). Může to být účet nebo podúčet.
 - NEAR datové zdroje představují alternativní volitelné pole `source.accounts`, které obsahuje volitelné přípony a předpony. Musí být specifikována alespoň jedna z předpony nebo přípony, které odpovídají jakémukoli účtu začínajícímu nebo končícímu uvedenými hodnotami. Příklad níže by odpovídal: `[app|good].*[morning.near|morning.testnet]`. Pokud je potřeba pouze seznam předpon nebo přípon, druhé pole lze vynechat.
 
 ```yaml
@@ -88,7 +88,7 @@ accounts:
 Zdroje dat NEAR podporují dva typy zpracovatelů:
 
 - `blockHandlers`: spustí se na každém novém bloku NEAR. Není vyžadován žádný `source.account`.
-- `receiptHandlers`: run on every receipt where the data source's `source.account` is the recipient. Note that only exact matches are processed ([subaccounts](https://docs.near.org/tutorials/crosswords/basics/add-functions-call#create-a-subaccount) must be added as independent data sources).
+- `receiptHandlers`: spustí se na každé příjemce, kde je `účet zdroje dat` příjemcem. Všimněte si, že se zpracovávají pouze přesné shody ([podúčty](https://docs.near.org/tutorials/crosswords/basics/add-functions-call#create-a-subaccount) musí být přidány jako nezávislé zdroje dat).
 
 ### Definice schématu
 
@@ -98,7 +98,7 @@ Definice schématu popisuje strukturu výsledné databáze podgrafů a vztahy me
 
 Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/).
 
-Indexování NEAR zavádí do rozhraní [AssemblyScript API](/developing/graph-ts/api) datové typy specifické pro NEAR.
+Indexování NEAR zavádí do [API AssemblyScript](/developing/graph-ts/api) datové typy specifické pro NEAR.
 
 ```typescript
 
@@ -165,9 +165,9 @@ Tyto typy jsou předány do block & obsluha účtenek:
 - Obsluhy bloků obdrží `Block`
 - Obsluhy příjmu obdrží `ReceiptWithOutcome`
 
-Jinak je zbytek [AssemblyScript API](/developing/graph-ts/api) dostupný vývojářům podgrafů NEAR během provádění mapování.
+V opačném případě mají vývojáři podgrafů NEAR během provádění mapování k dispozici zbytek [AssemblyScript API](/developing/graph-ts/api).
 
-To zahrnuje novou funkci parsování JSON - záznamy na NEAR jsou často vysílány ve formě zřetězených JSON. Nová funkce `json.fromString(...)` je k dispozici jako součást [JSON API](/developing/graph-ts/api#json-api), které umožňuje vývojářům snadno zpracovávat tyto záznamy.
+To zahrnuje novou funkci pro parsování JSON - log na NEAR jsou často emitovány jako serializované JSONs. Nová funkce `json.fromString(...)` je k dispozici jako součást [JSON API](/developing/graph-ts/api#json-api), která umožňuje vývojářům snadno zpracovávat tyto log.
 
 ## Nasazení podgrafu NEAR
 
@@ -194,8 +194,8 @@ Konfigurace uzlů závisí na tom, kde je podgraf nasazen.
 ### Podgraf Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Místní uzel grafu (na základě výchozí konfigurace)
@@ -232,7 +232,7 @@ Koncový bod GraphQL pro podgrafy NEAR je určen definicí schématu se stávaj
 
 ## Příklady podgrafů
 
-Here are some example subgraphs for reference:
+Zde je několik příkladů podgrafů:
 
 [NEAR bloky](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
 

From 88ea31411d8d3a7067a143a6998d3c3bf0f10385 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:48 -0500
Subject: [PATCH 0160/1325] New translations unit-testing-framework.mdx (Czech)

---
 .../cs/developing/unit-testing-framework.mdx  | 45 ++++++++++++-------
 1 file changed, 29 insertions(+), 16 deletions(-)

diff --git a/website/pages/cs/developing/unit-testing-framework.mdx b/website/pages/cs/developing/unit-testing-framework.mdx
index 45decf979c6f..066874060887 100644
--- a/website/pages/cs/developing/unit-testing-framework.mdx
+++ b/website/pages/cs/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Rámec pro testování jednotek
 ---
 
-Matchstick je framework pro jednotkové testování vyvinutý společností [LimeChain](https://limechain.tech/), který umožňuje vývojářům podgrafu testovat logika mapování v prostředí sandbox a spolehlivě nasazovat své podgraf!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Začínáme
 
-### Instalace závislostí
+### Install Dependencies
 
-Abyste mohli používat pomocné metody testy a spouštět testy, je třeba nainstalovat následující závislosti:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` závisí na PostgreSQL, takže pokud jej ještě nemáte, musíte si jej nainstalovat. Důrazně doporučujeme použít níže uvedené příkazy, protože jeho přidání jiným způsobem může způsobit neočekávané chyby!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Instalační příkaz Postgres:
+Installation command:
 
 ```sh
 brew instalovat postgresql
@@ -30,15 +39,15 @@ Vytvoření symlinku na nejnovější verzi libpq.5.lib _Musíte nejprve vytvoř
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Instalační příkaz Postgres (závisí na distribuci):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Subsystém Windows pro Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 Matchstick můžete na WSL používat jak pomocí přístupu Docker, tak pomocí binárního přístupu. Protože WSL může být trochu složitější, přinášíme několik tipů pro případ, že narazíte na problémy, jako např
 
@@ -76,7 +85,7 @@ A konečně, nepoužívejte `graph test` (který používá globální instalaci
 }
 ```
 
-### Použití
+### Using Matchstick
 
 Pro použití **Matchsticku** v projektu subgrafu stačí otevřít terminál, přejít do kořenové složky projektu a jednoduše spustit `graph test [options] <datasource>` - stáhne se nejnovější binární soubor **Matchsticku** a spustí se zadaný test nebo všechny testy ve složce testů (nebo všechny existující testy, pokud není zadán příznak datasource).
 
@@ -1368,22 +1377,26 @@ Výstup protokolu obsahuje dobu trvání test. Zde je příklad:
 
 > Kritické: Nelze vytvořit WasmInstance z platného modulu s kontextem: neznámý import: wasi_snapshot_preview1::fd_write nebyl definován
 
-To znamená, že jste ve svém kódu použili `console.log`, což není podporováno jazykem AssemblyScript. Zvažte prosím použití [Logging API](/developing/graph-ts/api/#logging-api)
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Neshoda v argumentech je způsobena neshodou v `graph-ts` a `matchstick-as`. Nejlepší způsob, jak opravit problémy, jako je tento, je aktualizovat vše na nejnovější vydanou verzi.
 
+## Další zdroje
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Zpětná vazba
 
 Pokud máte nějaké dotazy, zpětnou vazbu, požadavky na funkce nebo se jen chcete ozvat, nejlépe na Graf Discord, kde máme pro Matchstick vyhrazený kanál s názvem 🔥| unit-testing.

From d60cb315cadf690e9c9bbc3af2000dc6222d33ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:49 -0500
Subject: [PATCH 0161/1325] New translations about.mdx (German)

---
 website/pages/de/about.mdx | 70 ++++++++++++++++++++++++--------------
 1 file changed, 45 insertions(+), 25 deletions(-)

diff --git a/website/pages/de/about.mdx b/website/pages/de/about.mdx
index 36c6a49f8fbc..8c088d6a53d1 100644
--- a/website/pages/de/about.mdx
+++ b/website/pages/de/about.mdx
@@ -1,47 +1,67 @@
 ---
-title: About The Graph
+title: Über The Graph
 ---
 
-This page will explain what The Graph is and how you can get started.
+## Was ist The Graph?
 
-## What is The Graph?
+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.
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+## Grundlagen verstehen
 
-Projects with complex smart contracts like [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it really difficult to read anything other than basic data directly from the blockchain.
+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.
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+### Herausforderungen ohne The Graph
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+- 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**.
 
-**Indexing blockchain data is really, really hard.**
+- 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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+- 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 provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+### Warum ist das ein Problem?
 
-## How The Graph Works
+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.
 
-The Graph learns what and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph description defines the smart contracts of interest for a subgraph, the events in those contracts to pay attention to, and how to map event data to data that The Graph will store in its database.
+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](/network/benefits/), muss gewartet werden, stellt einen Single Point of Failure dar und bricht wichtige Sicherheitseigenschaften, die für die Dezentralisierung erforderlich sind.
 
-Once you have written a `subgraph manifest`, you use the Graph CLI to store the definition in IPFS and tell the indexer to start indexing data for that 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+## The Graph bietet eine Lösung
 
-![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png)
+The Graph löst diese Herausforderung mit einem dezentralen Protokoll, das 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.
 
-The flow follows these steps:
+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.
 
-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.
+### Die Funktionsweise von The Graph
 
-## Next Steps
+Die Indizierung von Blockchain-Daten ist sehr schwierig, aber The Graph macht es einfach. The Graph lernt, wie man Ethereum-Daten mit Hilfe von Subgraphen indiziert. Subgraphs 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.
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+#### Besonderheiten
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+- The Graph verwendet Subgraph-Beschreibungen, die als Subgraph Manifest innerhalb des Subgraphen bekannt sind.
+
+- Die Beschreibung des Subgraphs beschreibt die Smart Contracts, die für einen Subgraph von Interesse sind, die Ereignisse innerhalb dieser Verträge, auf die man sich konzentrieren sollte, 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 Subgraph Manifest schreiben.
+
+- Nachdem Sie das `Subgraph Manifest` geschrieben haben, können Sie das Graph CLI verwenden, um die Definition im IPFS zu speichern und einen Indexer anzuweisen, mit der Indizierung der Daten für diesen Subgraphen zu beginnen.
+
+Das nachstehende Diagramm enthält detailliertere Informationen über den Datenfluss, nachdem ein Subgraph Manifest mit Ethereum-Transaktionen bereitgestellt worden ist.
+
+![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 Subgraphen.
+4.  Graph Node findet Ethereum-Ereignisse für Ihren Subgraphen in diesen Blöcken 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 eingehender behandelt.
+
+Bevor Sie Ihren eigenen Subgraphen schreiben, sollten Sie den [Graph Explorer](https://thegraph.com/explorer) erkunden und sich einige der bereits vorhandenen Subgraphen ansehen. Die Seite jedes Subgraphen enthält eine GraphQL- Playground, mit der Sie seine Daten abfragen können.

From 6dec412dbf23a1fa11fbe879361c070a5b5c53bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:51 -0500
Subject: [PATCH 0162/1325] New translations near.mdx (German)

---
 website/pages/de/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/de/cookbook/near.mdx b/website/pages/de/cookbook/near.mdx
index 0b5436f36152..6ab983b22272 100644
--- a/website/pages/de/cookbook/near.mdx
+++ b/website/pages/de/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 3c496e3e5e67c3d94fb395af1d269b094b50dc2c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:52 -0500
Subject: [PATCH 0163/1325] New translations unit-testing-framework.mdx
 (German)

---
 .../de/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/de/developing/unit-testing-framework.mdx b/website/pages/de/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/de/developing/unit-testing-framework.mdx
+++ b/website/pages/de/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 267108d94c8ba213cc53a3cd4b40063a88b3448c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:53 -0500
Subject: [PATCH 0164/1325] New translations about.mdx (Italian)

---
 website/pages/it/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/it/about.mdx b/website/pages/it/about.mdx
index 6c93da5503e5..d1cfbfad3b82 100644
--- a/website/pages/it/about.mdx
+++ b/website/pages/it/about.mdx
@@ -2,46 +2,66 @@
 title: Informazioni su The Graph
 ---
 
-Questa pagina spiega cos'è iThe Graph e come si può iniziare.
-
 ## Che cos'è The Graph?
 
-Il Graph è un protocollo decentralizzato per l'indicizzazione e query delle dati della blockchain. Il Graph permette di effettuare query dei dati difficili da effettuare query direttamente.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-I progetti con smart contract complessi come [Uniswap](https://uniswap.org/) e le iniziative NFT come [Bored Ape Yacht Club](https://boredapeyachtclub.com/) memorizzano i dati sulla blockchain di Ethereum, rendendo davvero difficile leggere qualcosa di diverso dai dati di base direttamente dalla blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-Si potrebbe anche creare un proprio server, elaborare le transazioni, salvarle in un database e creare un endpoint API per effettuare query dai dati. Tuttavia, questa opzione richiede [molte risorse](/network/benefits/), necessita di manutenzione, presenta un singolo punto di guasto e infrange importanti proprietà di sicurezza necessarie per la decentralizzazione.
+### How The Graph Functions
 
-**L'indicizzazione dei dati della blockchain è molto, molto difficile.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Come funziona il Graph
+- 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.
 
-The Graph impara cosa e come indicizzare i dati di Ethereum in base alle descrizioni dei subgraph, note come manifesto del subgraph. La descrizione del subgraph definisce gli smart contract di interesse per un subgraph, gli eventi di quei contratti a cui prestare attenzione e come mappare i dati degli eventi ai dati che The Graph memorizzerà nel suo database.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Una volta scritto un `subgraph manifest`, si usa la Graph CLI per memorizzare la definizione in IPFS e dire all'Indexer di iniziare l'indicizzazione dei dati per quel subgraph.
+- 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.
 
-Questo diagramma fornisce maggiori dettagli sul flusso di dati una volta che è stato distribuito un subgraph manifest, che tratta le transazioni Ethereum:
+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 scansiona continuamente Ethereum alla ricerca di nuovi blocchi e dei dati del vostro subgraph che possono contenere.
-4. Graph Node trova gli eventi Ethereum per il vostro subgraph in questi blocchi ed esegue i gestori di mappatura che avete fornito. La mappatura è un modulo WASM che crea o aggiorna le entità di dati che Graph Node memorizza in risposta agli eventi Ethereum.
-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.
+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 scansiona continuamente Ethereum alla ricerca di nuovi blocchi e dei dati del vostro subgraph che possono contenere.
+4.  Graph Node trova gli eventi Ethereum per il vostro subgraph in questi blocchi ed esegue i gestori di mappatura che avete fornito. La mappatura è un modulo WASM che crea o aggiorna le entità di dati che Graph Node memorizza in risposta agli eventi Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 742266a0d162db0948881576eabca9ef61772111 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:54 -0500
Subject: [PATCH 0165/1325] New translations graphql-api.mdx (Spanish)

---
 website/pages/es/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/es/querying/graphql-api.mdx b/website/pages/es/querying/graphql-api.mdx
index 2086e994cd0a..e0281d0b1bdc 100644
--- a/website/pages/es/querying/graphql-api.mdx
+++ b/website/pages/es/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: API GraphQL
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Consultas
+## What is GraphQL?
 
-En tu esquema de subgrafos defines tipos llamados `Entities`. Por cada tipo de `Entity`, se generará un campo `entity` y `entities` en el nivel superior del tipo `Query`. Ten en cuenta que no es necesario incluir `query` en la parte superior de la consulta `graphql` cuando se utiliza The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Ejemplos
 
@@ -21,7 +29,7 @@ Consulta por un solo `Token` definido en tu esquema:
 }
 ```
 
-> **Nota:** Cuando se consulta una sola entidad, el campo `id` es obligatorio y debe ser un string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Consulta todas las entidades `Token`:
 
@@ -36,7 +44,10 @@ Consulta todas las entidades `Token`:
 
 ### Clasificación
 
-Al consultar una colección, el parámetro `orderBy` puede utilizarse para ordenar por un atributo específico. Además, el `orderDirection` se puede utilizar para especificar la dirección de orden, `asc` para ascendente o `desc` para descendente.
+When querying a collection, you may:
+
+- 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.
 
 #### Ejemplo
 
@@ -53,7 +64,7 @@ Al consultar una colección, el parámetro `orderBy` puede utilizarse para orden
 
 A partir de Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0), las entidades se pueden ordenar con base en entidades anidadas.
 
-En el siguiente ejemplo, ordenamos los tokens por el nombre de su propietario:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ En el siguiente ejemplo, ordenamos los tokens por el nombre de su propietario:
 
 ### Paginación
 
-Al consultar una colección, el parámetro `first` puede utilizarse para paginar desde el principio de la colección. Cabe destacar que el orden por defecto es por ID en orden alfanumérico ascendente, no por tiempo de creación.
-
-Además, el parámetro `skip` puede utilizarse para saltar entidades y paginar. por ejemplo, `first:100` muestra las primeras 100 entidades y `first:100, skip:100` muestra las siguientes 100 entidades.
+When querying a collection, it's best to:
 
-Las consultas deben evitar el uso de valores de `skip` muy grandes, ya que suelen tener un rendimiento deficiente. Para recuperar un gran número de elementos, es mucho mejor para paginar recorrer las entidades basándose en un atributo, como se muestra en el último ejemplo.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Ejemplo usando `first`
 
@@ -106,7 +118,7 @@ Consulta 10 entidades `Token`, desplazadas 10 lugares desde el principio de la c
 
 #### Ejemplo usando `first` y `id_ge`
 
-Si un cliente necesita recuperar un gran número de entidades, es mucho más eficaz basar las consultas en un atributo y filtrar por ese atributo. Por ejemplo, un cliente podría recuperar un gran número de tokens utilizando esta consulta:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-La primera vez, enviaría la consulta con `lastID = ""`, y para las siguientes peticiones establecería `lastID` al atributo `id` de la última entidad de la petición anterior. Este enfoque tendrá un rendimiento significativamente mejor que el uso de valores crecientes de `skip`.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtrado
 
-Puedes utilizar el parámetro `where` en tus consultas para filtrar por diferentes propiedades. Puedes filtrar por múltiples valores dentro del parámetro `where`.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Ejemplo usando `where`
 
@@ -155,7 +168,7 @@ Puedes utilizar sufijos como `_gt`, `_lte` para la comparación de valores:
 
 #### Ejemplo de filtrado de bloques
 
-También puedes filtrar entidades por el `_change_block(number_gte: Int)`: esto filtra las entidades que se actualizaron en o después del bloque especificado.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Esto puede ser útil si buscas obtener solo las entidades que han cambiado, por ejemplo, desde la última vez que realizaste una encuesta. O, alternativamente, puede ser útil para investigar o depurar cómo cambian las entidades en tu subgrafo (si se combina con un filtro de bloque, puedes aislar solo las entidades que cambiaron en un bloque específico).
 
@@ -193,7 +206,7 @@ A partir de Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/r
 
 ##### Operador `AND`
 
-En el siguiente ejemplo, estamos filtrando desafíos con `coutcome` `succeeded` y `number` mayor o igual a `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ En el siguiente ejemplo, estamos filtrando desafíos con `coutcome` `succeeded`
 ```
 
 > **Azúcar sintáctico**: Puedes simplificar la consulta anterior eliminando el operador `and` pasando una subexpresión separada por comas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ En el siguiente ejemplo, estamos filtrando desafíos con `coutcome` `succeeded`
 
 ##### Operador `OR`
 
-En el siguiente ejemplo, estamos filtrando desafíos con `coutcome` `succeeded` y `number` mayor o igual a `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 Puedes consultar el estado de tus entidades no solo para el último bloque, que es el predeterminado, sino también para un bloque arbitrario en el pasado. El bloque en el que debe ocurrir una consulta se puede especificar por su número de bloque o su hash de bloque al incluir un argumento `block` en los campos de nivel superior de las consultas.
 
-El resultado de dicha consulta no cambiará con el tiempo, por ejemplo, consultar en un determinado bloque anterior devolverá el mismo resultado sin importar cuándo se ejecute, con la excepción de que si consultas en un bloque muy cerca de la cabecera de la cadena Ethereum, el resultado podría cambiar si ese bloque resulta no estar en la cadena principal y la cadena se reorganiza. Una vez que un bloque puede considerarse final, el resultado de la consulta no cambiará.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Ten en cuenta que la implementación actual todavía está sujeta a ciertas limitaciones que podrían violar estas garantías. La implementación no siempre puede demostrar que un hash de bloque dado no está en la cadena principal, o que el resultado de una consulta por hash de bloque para un bloque que no puede considerarse final aún podría estar influenciado por una reorganización de bloque que se ejecuta simultáneamente con la consulta. Esto no afecta los resultados de consultas por hash de bloque cuando el bloque es final y se sabe que está en la cadena principal. [Este problema](https://github.com/graphprotocol/graph-node/issues/1405) explica en detalle cuáles son estas limitaciones.
+> 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
 
@@ -322,12 +335,12 @@ Las consultas de búsqueda de texto completo tienen un campo obligatorio, `text`
 
 Operadores de búsqueda de texto completo:
 
-| 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 |
-| &#x7c; | `O` | 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. |
-| `:*` | `Prefijo` | 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                                                |
+| &#x7c;      | `O`         | 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.                                                                                                                         |
+| `:*`        | `Prefijo`   | Utilice el término de búsqueda del prefijo para encontrar palabras cuyo prefijo coincida (se requieren 2 caracteres.)                                               |
 
 #### Ejemplos
 
@@ -376,11 +389,11 @@ Graph Node implementa una validación [basada en especificaciones](https://spec.
 
 ## Esquema
 
-El esquema de tu fuente de datos, es decir, los tipos de entidad, los valores y las relaciones que están disponibles para consultar, se definen a través de [GraphQL Interface Definition Language (IDL)](https://facebook.github.io/graphql/draft/# sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-Los esquemas de GraphQL generalmente definen tipos raíz para `queries`, `subscriptions` y `mutations`. The Graph solo admite `queries`. El tipo raíz `Query` para tu subgrafo se genera automáticamente a partir del esquema de GraphQL que se incluye en tu manifiesto de subgrafo.
+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).
 
-> **Nota:** nuestra API no expone mutaciones porque se espera que los desarrolladores emitan transacciones directamente contra la cadena de bloques subyacente desde sus aplicaciones.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entidades
 

From aa1b628a77892569cced52e5cda5717b79390d04 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:56 -0500
Subject: [PATCH 0166/1325] New translations graphql-api.mdx (Arabic)

---
 website/pages/ar/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/ar/querying/graphql-api.mdx b/website/pages/ar/querying/graphql-api.mdx
index 2d2efb6008c2..258471c1d9d4 100644
--- a/website/pages/ar/querying/graphql-api.mdx
+++ b/website/pages/ar/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## الاستعلامات
+## What is GraphQL?
 
-في مخطط الـ subgraph الخاص بك ، يمكنك تعريف أنواع وتسمى `Entities`. لكل نوع من `Entity` ، سيتم إنشاء حقل `entity` و `entities` في المستوى الأعلى من نوع `Query`. لاحظ أنه لا يلزم تضمين `query` أعلى استعلام `graphql` عند استخدام The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### مثال
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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.
 
 #### مثال
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| رمز | عامل التشغيل | الوصف |
-| --- | --- | --- |
-| `&` | `And` | لدمج عبارات بحث متعددة في فلتر للكيانات التي تتضمن جميع العبارات المتوفرة |
-| &#x7c; | `أو` | الاستعلامات التي تحتوي على عبارات بحث متعددة مفصولة بواسطة عامل التشغيل or ستعيد جميع الكيانات المتطابقة من أي عبارة متوفرة |
-| `<->` | `Follow by` | يحدد المسافة بين كلمتين. |
-| `:*` | `Prefix` | يستخدم عبارة البحث prefix للعثور على الكلمات التي تتطابق بادئتها (مطلوب حرفان.) |
+| رمز         | عامل التشغيل | الوصف                                                                                                                       |
+| ----------- | ------------ | --------------------------------------------------------------------------------------------------------------------------- |
+| `&`     | `And`        | لدمج عبارات بحث متعددة في فلتر للكيانات التي تتضمن جميع العبارات المتوفرة                                                   |
+| &#x7c;      | `أو`         | الاستعلامات التي تحتوي على عبارات بحث متعددة مفصولة بواسطة عامل التشغيل or ستعيد جميع الكيانات المتطابقة من أي عبارة متوفرة |
+| `<->` | `Follow by`  | يحدد المسافة بين كلمتين.                                                                                                    |
+| `:*`        | `Prefix`     | يستخدم عبارة البحث prefix للعثور على الكلمات التي تتطابق بادئتها (مطلوب حرفان.)                                             |
 
 #### Examples
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## المخطط
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 57ab4818e4d5275496e8707ee200f3512b2994b3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:57 -0500
Subject: [PATCH 0167/1325] New translations graphql-api.mdx (Czech)

---
 website/pages/cs/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/cs/querying/graphql-api.mdx b/website/pages/cs/querying/graphql-api.mdx
index e1c7f3e566f7..16b65fe32b1e 100644
--- a/website/pages/cs/querying/graphql-api.mdx
+++ b/website/pages/cs/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Dotazy
+## What is GraphQL?
 
-Ve schématu podgrafu definujete typy nazvané `Entity`. Pro každý typ `Entity` bude na nejvyšší úrovni typu `Query` vygenerováno pole `entity` a `entity`. Všimněte si, že `dotaz` nemusí být při použití Grafu zahrnut na vrcholu `graphql` dotazu.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Příklady
 
@@ -21,7 +29,7 @@ Dotaz na jednu entitu `Token` definovanou ve vašem schématu:
 }
 ```
 
-> **Poznámka:** Při dotazování na jednu entitu je pole `id` povinné a musí to být řetězec.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Dotaz na všechny entity `Token`:
 
@@ -36,7 +44,10 @@ Dotaz na všechny entity `Token`:
 
 ### Třídění
 
-Při dotazování na kolekci lze parametr `orderBy` použít k seřazení podle určitého atributu. Kromě toho lze pomocí parametru `orderDirection` určit směr řazení, `asc` pro vzestupné nebo `desc` pro sestupné.
+When querying a collection, you may:
+
+- 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.
 
 #### Příklad
 
@@ -53,7 +64,7 @@ Při dotazování na kolekci lze parametr `orderBy` použít k seřazení podle
 
 Od verze Uzel grafu [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) lze entity třídit na základě vnořených entit.
 
-V následujícím příkladu seřadíme tokeny podle jména jejich vlastníka:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ V následujícím příkladu seřadíme tokeny podle jména jejich vlastníka:
 
 ### Stránkování
 
-Při dotazování na kolekci lze parametr `První` použít pro stránkování od začátku kolekce. Stojí za zmínku, že výchozí řazení je podle ID ve vzestupném alfanumerickém pořadí, nikoli podle času vytvoření.
-
-Dále lze parametr `skip` použít k přeskočení entit a stránkování, např. `first:100` zobrazí prvních 100 entit a `first:100, skip:100` zobrazí dalších 100 entit.
+When querying a collection, it's best to:
 
-Dotazy by se měly vyvarovat používání velmi velkých hodnot `přeskočit`, protože mají obecně nízkou výkonnost. Pro získání velkého počtu položek je mnohem lepší procházet entity na základě atributu, jak je uvedeno v posledním příkladu.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Příklad s použitím `first`
 
@@ -106,7 +118,7 @@ Dotaz na 10 entit `Token`, posunutých o 10 míst od začátku kolekce:
 
 #### Příklad s použitím `first` a `id_ge`
 
-Pokud klient potřebuje získat velký počet entit, je mnohem výkonnější založit dotazy na atributu a filtrovat podle něj. Klient by například pomocí tohoto dotazu získal velký počet tokenů:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-Poprvé by odeslal dotaz s `lastID = ""` a při dalších požadavcích by nastavil `lastID` na atribut `id` poslední entity v předchozím požadavku. Tento přístup bude fungovat podstatně lépe než použití rostoucích hodnot `skip`.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtrování
 
-Pomocí parametru `where` můžete v dotazech filtrovat různé vlastnosti. V rámci parametru `kde` můžete filtrovat podle více hodnot.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Příklad s použitím `where`
 
@@ -155,7 +168,7 @@ Pro porovnání hodnot můžete použít přípony jako `_gt`, `_lte`:
 
 #### Příklad pro filtrování bloků
 
-Entity můžete filtrovat také pomocí `_change_block(number_gte: Int)` - filtruje entity, které byly aktualizovány v zadaném bloku nebo po něm.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 To může být užitečné, pokud chcete načíst pouze entity, které se změnily například od posledního dotazování. Nebo může být užitečná pro zkoumání nebo ladění změn entit v podgrafu (v kombinaci s blokovým filtrem můžete izolovat pouze entity, které se změnily v určitém bloku).
 
@@ -193,7 +206,7 @@ Od verze Uzel grafu [`v0.30.0`](https://github.com/graphprotocol/graph-node/rele
 
 ##### Operátor `AND`
 
-V následujícím příkladu filtrujeme výzvy s `outcome` `succeeded` a `number` větším nebo rovným `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ V následujícím příkladu filtrujeme výzvy s `outcome` `succeeded` a `number
 ```
 
 > **Syntaktický cukr:** Výše uvedený dotaz můžete zjednodušit odstraněním operátoru `a` předáním podvýrazu odděleného čárkami.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ V následujícím příkladu filtrujeme výzvy s `outcome` `succeeded` a `number
 
 ##### Operátor `OR`
 
-V následujícím příkladu filtrujeme výzvy s `outcome` `succeeded` nebo `number` větším nebo rovným `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 Můžete se dotazovat na stav entit nejen pro nejnovější blok, což je výchozí nastavení, ale také pro libovolný blok v minulosti. Blok, u kterého má dotaz proběhnout, lze zadat buď číslem bloku, nebo jeho blokovým hashem, a to tak, že do polí toplevel dotazů zahrnete argument `blok`.
 
-Výsledek takového dotazu se v průběhu času nemění, tj. dotaz na určitý minulý blok vrátí stejný výsledek bez ohledu na to, kdy je proveden, s výjimkou toho, že pokud se dotazujete na blok velmi blízko hlavy řetězce, výsledek se může změnit, pokud se ukáže, že tento blok není v hlavním řetězci a řetězec se reorganizuje. Jakmile lze blok považovat za konečný, výsledek dotazu se nezmění.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Všimněte si, že současná implementace stále podléhá určitým omezením, která by mohla tyto záruky porušit. Implementace nemůže vždy zjistit, že daný blokový hash vůbec není v hlavním řetězci, nebo že výsledek dotazu podle blokového hashe na blok, který ještě nelze považovat za finální, může být ovlivněn reorganizací bloku probíhající současně s dotazem. Neovlivňují výsledky dotazů podle blokové hash, pokud je blok finální a je známo, že je v hlavním řetězci. [Toto Problém ](https://github.com/graphprotocol/graph-node/issues/1405) podrobně vysvětluje, jaká jsou tato omezení.
+> 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
 
@@ -322,12 +335,12 @@ Fulltextové vyhledávací dotazy mají jedno povinné pole `text` pro zadání
 
 Operátory fulltextového vyhledávání:
 
-| Symbol | Operátor | Popis |
-| --- | --- | --- |
-| `&` | `a` | Pro kombinaci více vyhledávacích výrazů do filtru pro entity, které obsahují všechny zadané výrazy |
-| &#x7c; | `Nebo` | 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                                                                                                                         |
+| ----------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
+| `&`     | `a`         | Pro kombinaci více vyhledávacích výrazů do filtru pro entity, které obsahují všechny zadané výrazy                            |
+| &#x7c;      | `Nebo`      | 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
 
@@ -376,11 +389,11 @@ Uzel grafu implementuje ověření [založené na specifikacích](https://spec.g
 
 ## Schema
 
-Schéma datového zdroje - tj. typy entit, hodnoty a vztahy, které jsou k dispozici pro dotazování - jsou definovány pomocí [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-Schéma GraphQL obecně definují kořenové typy pro `dotazy`, `odběry` a `mutace`. Graf podporuje pouze `dotazy`. Kořenový typ `Dotaz` pro váš podgraf je automaticky vygenerován ze schématu GraphQL, které je součástí manifestu podgrafu.
+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).
 
-> **Poznámka:** Naše API nevystavuje mutace, protože se očekává, že vývojáři budou vydávat transakce přímo proti podkladovému blockchainu ze svých aplikací.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 9dc0dbc27111e128a5bd87fc2e9d52e17d0ace05 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:58 -0500
Subject: [PATCH 0168/1325] New translations graphql-api.mdx (German)

---
 website/pages/de/querying/graphql-api.mdx | 91 +++++++++++++----------
 1 file changed, 52 insertions(+), 39 deletions(-)

diff --git a/website/pages/de/querying/graphql-api.mdx b/website/pages/de/querying/graphql-api.mdx
index c1831e3117e6..abe9db8cc7f4 100644
--- a/website/pages/de/querying/graphql-api.mdx
+++ b/website/pages/de/querying/graphql-api.mdx
@@ -1,16 +1,24 @@
 ---
-title: GraphQL API
+title: GraphQL-API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Beispiele
 
-Query for a single `Token` entity defined in your schema:
+Die Abfrage für eine einzelne `Token`-Entität, die in Ihrem Schema definiert ist:
 
 ```graphql
 {
@@ -21,9 +29,9 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
-Query all `Token` entities:
+Die Abfrage für alle `Token`-Entitäten:
 
 ```graphql
 {
@@ -34,11 +42,14 @@ Query all `Token` entities:
 }
 ```
 
-### Sorting
+### Sortierung
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
 
-#### Example
+- 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.
+
+#### Beispiel
 
 ```graphql
 {
@@ -49,11 +60,11 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 }
 ```
 
-#### Example for nested entity sorting
+#### Beispiel für die Sortierung verschachtelter Entitäten
 
-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.
+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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -66,19 +77,20 @@ In the following example, we sort the tokens by the name of their owner:
 }
 ```
 
-> Currently, you can sort by one-level deep `String` or `ID` types on `@entity` and `@derivedFrom` fields. Unfortunately, [sorting by interfaces on one level-deep entities](https://github.com/graphprotocol/graph-node/pull/4058), sorting by fields which are arrays and nested entities is not yet supported.
+> Derzeit können Sie in den Feldern `@entity` und `@derivedFrom` nach einstufig tiefen `String`- oder `ID`-Typen sortieren. Leider ist das [Sortieren nach Schnittstellen auf Entitäten mit einer Tiefe von einer Ebene](https://github.com/graphprotocol/graph-node/pull/4058), das Sortieren nach Feldern, die Arrays und verschachtelte Entitäten sind, noch nicht unterstützt.
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
+#### Ein Beispiel für die Verwendung von `first`
 
-Query the first 10 tokens:
+Die Abfrage für die ersten 10 Token:
 
 ```graphql
 {
@@ -89,7 +101,7 @@ 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.
+Um Gruppen von Entitäten in der Mitte einer Sammlung abzufragen, kann der Parameter `skip` in Verbindung mit dem Parameter `first` verwendet werden, um eine bestimmte Anzahl von Entitäten beginnend am Anfang der Sammlung zu überspringen.
 
 #### Example using `first` and `skip`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND`-Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | Beschreibung |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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    | Beschreibung                                                                                                                         |
+| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
+| &#x7c;      | `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.)                                                 |
 
 #### Beispiele
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 95e1db9b6550a33421ea94003ff334611529c1d0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:33:59 -0500
Subject: [PATCH 0169/1325] New translations api.mdx (Spanish)

---
 website/pages/es/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/es/developing/graph-ts/api.mdx b/website/pages/es/developing/graph-ts/api.mdx
index b2309f29cc83..6660507ae768 100644
--- a/website/pages/es/developing/graph-ts/api.mdx
+++ b/website/pages/es/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-Esta página documenta qué API integradas se pueden usar al escribir mappings de subgrafos. Hay dos tipos de API disponibles listas para usar:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Referencias de API
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Notas del lanzamiento |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Notas del lanzamiento                                                                                                                                                                                                                         |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Tipos Incorporados
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Cada entidad debe tener un identificador único para evitar colisiones con otras entidades. Es bastante común que los parámetros de los eventos incluyan un identificador único que pueda ser utilizado. Nota: El uso del hash de la transacción como ID asume que ningún otro evento en la misma transacción crea entidades con este hash como ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Carga de entidades desde el store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Buscando entidades creadas dentro de un bloque
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-La API de almacenamiento facilita la recuperación de entidades que se crearon o actualizaron en el bloque actual. Una situación típica para esto es cuando un handler crea una Transacción a partir de algún evento en la cadena, y un handler posterior quiere acceder a esta transacción si existe. En el caso de que la transacción no exista, el subgrafo tendrá que ir a la base de datos solo para averiguar que la entidad no existe; si el autor del subgrafo ya sabe que la entidad debe haber sido creada en el mismo bloque, el uso de loadInBlock evita este viaje de ida y vuelta a la base de datos. Para algunos subgrafos, estas búsquedas perdidas pueden contribuir significativamente al tiempo de indexación.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Cualquier otro contrato que forme parte del subgrafo puede ser importado desde e
 
 #### Tratamiento de las Llamadas Revertidas
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Ten en cuenta que un nodo Graph conectado a un cliente Geth o Infura puede no detectar todas las reversiones, si confías en esto te recomendamos que utilices un nodo Graph conectado a un cliente Parity.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Codificación/Descodificación ABI
 

From 8bc79c75d2975f90276d9bc4f929e3a72bac1b15 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:00 -0500
Subject: [PATCH 0170/1325] New translations api.mdx (Arabic)

---
 website/pages/ar/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/ar/developing/graph-ts/api.mdx b/website/pages/ar/developing/graph-ts/api.mdx
index 15fa02b9b2ba..544f2118f489 100644
--- a/website/pages/ar/developing/graph-ts/api.mdx
+++ b/website/pages/ar/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-هذه الصفحة توثق APIs المضمنة التي يمكن استخدامها عند كتابة subgraph mappings. يتوفر نوعان من APIs خارج الصندوق:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## مرجع API
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| الاصدار | ملاحظات الإصدار |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| الاصدار | ملاحظات الإصدار                                                                                                                                                                                                                               |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### الأنواع المضمنة (Built-in)
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### تحميل الكيانات من المخزن
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### معالجة الاستدعاءات المعادة
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### تشفير/فك تشفير ABI
 

From acd9588f6ba7a3ae8549e2310178c16a857bccb1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:02 -0500
Subject: [PATCH 0171/1325] New translations api.mdx (Czech)

---
 website/pages/cs/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/cs/developing/graph-ts/api.mdx b/website/pages/cs/developing/graph-ts/api.mdx
index d812f220a91b..624e5b95d141 100644
--- a/website/pages/cs/developing/graph-ts/api.mdx
+++ b/website/pages/cs/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Poznámka: pokud jste vytvořili subgraf před verzí `graph-cli`/`graph-ts` `0.22.0`, používáte starší verzi jazyka AssemblyScript, doporučujeme se podívat do [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-Tato stránka dokumentuje, jaké vestavěné API lze použít při psaní mapování podgrafů. Dva druhy API jsou k dispozici hned po vybalení:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- kód generovaný ze souborů podgrafů pomocí `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-Jako závislosti je možné přidat i další knihovny, pokud jsou kompatibilní s [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Vzhledem k tomu, že mapování je psáno v tomto jazyce, je [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) dobrým zdrojem informací o funkcích jazyka a standardních knihoven.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Reference API
 
@@ -27,16 +29,16 @@ Knihovna `@graphprotocol/graph-ts` poskytuje následující API:
 
 `apiVersion` v manifestu podgrafu určuje verzi mapovacího API, kterou pro daný podgraf používá uzel Graf.
 
-| Verze | Poznámky vydání |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity. |
-| 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum\<0/Přidání pole `receipt` do objektu Ethereum událost |
-| 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction<br />Přidáno `baseFeePerGas` do objektu Ethereum bloku |
+| Verze | Poznámky vydání                                                                                                                                                                                                                  |
+| :---: | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                     |
+| 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity.                                                                                                                                                                      |
+| 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum<0/Přidání pole `receipt` do objektu Ethereum událost                                                                                                                  |
+| 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction<br />Přidáno `baseFeePerGas` do objektu Ethereum bloku                                                                                                                      |
 | 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` |
-| 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall |
-| 0.0.3 | Do objektu Ethereum Call přidáno pole `from`<br />`etherem.call.address` přejmenováno na `ethereum.call.to` |
-| 0.0.2 | Přidání pole `input` do objektu Ethereum Transackce |
+| 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall                                                                                                                                                           |
+| 0.0.3 | Do objektu Ethereum Call přidáno pole `from`<br />`etherem.call.address` přejmenováno na `ethereum.call.to`                                                                                                                      |
+| 0.0.2 | Přidání pole `input` do objektu Ethereum Transackce                                                                                                                                                                              |
 
 ### Vestavěné typy
 
@@ -145,7 +147,7 @@ _Math_
 - `x.notEqual(y: BigInt): bool` –lze zapsat jako `x != y`.
 - `x.lt(y: BigInt): bool` – lze zapsat jako `x < y`.
 - `x.le(y: BigInt): bool` – lze zapsat jako `x <= y`.
-- `x.gt(y: BigInt): bool` – lze zapsat jako `x > y`.
+- `x.gt(y: BigInt): bool` – lze zapsat jako   `x > y`.
 - `x.ge(y: BigInt): bool` – lze zapsat jako `x >= y`.
 - `x.neg(): BigInt` – lze zapsat jako `-x`.
 - `x.divDecimal(y: BigDecimal): BigDecimal` – dělí desetinným číslem, čímž získá desetinný výsledek.
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 Pokud se při zpracování řetězce vyskytne událost `Transfer`, je předána obsluze události `handleTransfer` pomocí vygenerovaného typu `Transfer` (zde alias `TransferEvent`, aby nedošlo ke konfliktu názvů s typem entity). Tento typ umožňuje přístup k datům, jako je nadřazená transakce události a její parametr.
 
-Každá entita musí mít jedinečné ID, aby nedocházelo ke kolizím s jinými entitami. Je poměrně běžné, že parametry událostí obsahují jedinečný identifikátor, který lze použít. Poznámka: Použití hashe transakce jako ID předpokládá, že žádné jiné události ve stejné transakci nevytvářejí entity s tímto hashem jako ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Načítání entity z úložiště
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Použijte entitu Transfer jako dříve
 ```
 
-Protože entita ještě nemusí v ukládat existovat, metoda `load` vrátí hodnotu typu `Transfer | null`. Proto může být nutné před použitím hodnoty zkontrolovat, zda se nejedná o případ `null`.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Poznámka:** Načtení entit je nutné pouze v případě, že změny provedené v mapování závisí na předchozích datech entity. Dva způsoby aktualizace existujících entit naleznete v následující části.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Vyhledávání entit vytvořených v rámci bloku
 
 Od verzí `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 a `@graphprotocol/graph-cli` v0.49.0 je metoda `loadInBlock` dostupná pro všechny typy entit.
 
-API úložiště usnadňuje načítání entit, které byly vytvořeny nebo aktualizovány v aktuálním bloku. Typickou situací je, že jeden obslužný program vytvoří transakci z nějaké události v řetězci a pozdější obslužný program chce k této transakci přistupovat, pokud existuje. V případě, že transakce neexistuje, bude muset podgraf jít do databáze, jen aby zjistil, že entita neexistuje; pokud autor podgrafu již ví, že entita musela být vytvořena v tomtéž bloku, použitím funkce loadInBlock se této okružní cestě do databáze vyhne. U některých podgrafů mohou tato zmeškaná vyhledávání významně přispět k prodloužení doby indexace.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Jakákoli jiná smlouva, která je součástí podgrafu, může být importován
 
 #### Zpracování vrácených volání
 
-Pokud se metody vaší smlouvy určené pouze pro čtení mohou vrátit, měli byste to řešit voláním vygenerované metody smlouvy s předponou `try_`. Například kontrakt Gravity vystavuje metodu `gravatarToOwner`. Tento kód by byl schopen zvládnout revert v této metodě:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Všimněte si, že uzel Graf připojený ke klientovi Geth nebo Infura nemusí detekovat všechny reverty, pokud na to spoléháte, doporučujeme použít uzel Graf připojený ke klientovi Parity.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Kódování/dekódování ABI
 

From cc7c0b4562a96f5fb0f3c9ef61599b508d75790e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:03 -0500
Subject: [PATCH 0172/1325] New translations api.mdx (German)

---
 website/pages/de/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/de/developing/graph-ts/api.mdx b/website/pages/de/developing/graph-ts/api.mdx
index c2f994f31006..020d37ade7f7 100644
--- a/website/pages/de/developing/graph-ts/api.mdx
+++ b/website/pages/de/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API Reference
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Built-in Types
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Handling Reverted Calls
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Encoding/Decoding ABI
 

From ce7225aa34ddfd3d9d3e685dd14f2340d8eb57e3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:04 -0500
Subject: [PATCH 0173/1325] New translations subgraphs.mdx (Spanish)

---
 website/pages/es/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/es/subgraphs.mdx b/website/pages/es/subgraphs.mdx
index 27b452211477..f41177ea6fbf 100644
--- a/website/pages/es/subgraphs.mdx
+++ b/website/pages/es/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Subgrafos
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Ciclo de vida de un Subgrafo
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From adc208fb7de8869d1932e1b37d0fcfc7db94419c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:05 -0500
Subject: [PATCH 0174/1325] New translations transfer-to-the-graph.mdx
 (Spanish)

---
 .../pages/es/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/es/cookbook/transfer-to-the-graph.mdx b/website/pages/es/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..d86f6f31fc62 100644
--- a/website/pages/es/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/es/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Ejemplo
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Recursos Adicionales
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 12d3e59962076676925cc398284282a9cadfbb8a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:06 -0500
Subject: [PATCH 0175/1325] New translations advanced.mdx (Spanish)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/es/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/es/developing/creating-a-subgraph/advanced.mdx b/website/pages/es/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..01332c56e82f
--- /dev/null
+++ b/website/pages/es/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Descripción
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Errores no fatales
+
+Los errores de indexación en subgrafos ya sincronizados provocarán, por defecto, que el subgrafo falle y deje de sincronizarse. Los subgrafos pueden ser configurados de manera alternativa para continuar la sincronización en presencia de errores, ignorando los cambios realizados por el handler que provocó el error. Esto da a los autores de los subgrafos tiempo para corregir sus subgrafos mientras las consultas continúan siendo servidas contra el último bloque, aunque los resultados serán posiblemente inconsistentes debido al bug que provocó el error. Nótese que algunos errores siguen siendo siempre fatales, para que el error no sea fatal debe saberse que es deterministico.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Para activar los errores no fatales es necesario establecer el siguiente indicador en el manifiesto del subgrafo:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> Esto también establece las bases para la indexación determinista de datos off-chain, así como la posible introducción de datos arbitrarios procedentes de HTTP.
+
+### Descripción
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Añadir un nuevo tipo de entidad que se actualizará cuando se encuentren archivos
+
+Las fuentes de datos de archivos no pueden acceder a entidades basadas en cadenas ni actualizarlas, pero deben actualizar entidades específicas de archivos.
+
+Esto puede significar dividir campos de entidades existentes en entidades separadas, vinculadas entre sí.
+
+Entidad combinada original:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Nueva, entidad dividida:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Si la relación es 1:1 entre la entidad padre y la entidad fuente de datos de archivo resultante, el patrón más sencillo es vincular la entidad padre a una entidad de archivo resultante utilizando el CID IPFS como búsqueda. Pónte en contacto con nosotros en Discord si tienes dificultades para modelar tus nuevas entidades basadas en archivos!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Esta es la fuente de datos que se generará cuando se identifique un archivo de interés.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Crear un nuevo handler para procesar archivos
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Ejemplo de handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Generar fuentes de datos de archivos cuando sea necesario
+
+Ahora puedes crear fuentes de datos de archivos durante la ejecución de handlers basados en cadenas:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Ejemplo:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+¡Felicitaciones, estás utilizando fuentes de datos de archivos!
+
+#### Deploy de tus subgrafos
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitaciones
+
+Los handlers y entidades de fuentes de datos de archivos están aislados de otras entidades del subgrafo, asegurando que son deterministas cuando se ejecutan, y asegurando que no se contaminan las fuentes de datos basadas en cadenas. En concreto:
+
+- Las entidades creadas por File Data Sources son inmutables y no pueden actualizarse
+- Los handlers de File Data Source no pueden acceder a entidades de otras fuentes de datos de archivos
+- Los handlers basados en cadenas no pueden acceder a las entidades asociadas a File Data Sources
+
+> Aunque esta restricción no debería ser problemática para la mayoría de los casos de uso, puede introducir complejidad para algunos. Si tienes problemas para modelar tus datos basados en archivos en un subgrafo, ponte en contacto con nosotros a través de Discord!
+
+Además, no es posible crear fuentes de datos a partir de una File Data Source, ya sea una fuente de datos on-chain u otra File Data Source. Es posible que esta restricción se elimine en el futuro.
+
+#### Mejores Prácticas
+
+Si estás vinculando metadatos NFT a los tokens correspondientes, utiliza el hash IPFS de los metadatos para hacer referencia a una entidad Metadata desde la entidad Token. Guarda la entidad de metadatos utilizando el hash IPFS como ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Estamos trabajando para mejorar la recomendación anterior, de modo que las consultas sólo devuelvan la versión "más reciente"
+
+#### Problemas conocidos
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Ejemplos
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Referencias
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting sobre subgrafos existentes
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Debido a que el grafting copia en lugar de indexar los datos base, es mucho más rápido llevar el subgrafo al bloque deseado que indexar desde cero, aunque la copia inicial de los datos aún puede llevar varias horas para subgrafos muy grandes. Mientras se inicializa el subgrafo grafted, Graph Node registrará información sobre los tipos de entidad que ya han sido copiados.
+
+El subgrafo grafteado puede utilizar un esquema GraphQL que no es idéntico al del subgrafo base, sino simplemente compatible con él. Tiene que ser un esquema de subgrafo válido por sí mismo, pero puede diferir del esquema del subgrafo base de las siguientes maneras:
+
+- Agrega o elimina tipos de entidades
+- Elimina los atributos de los tipos de entidad
+- Agrega atributos anulables a los tipos de entidad
+- Convierte los atributos no anulables en atributos anulables
+- Añade valores a los enums
+- Agrega o elimina interfaces
+- Cambia para qué tipos de entidades se implementa una interfaz
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 1b557c2c8784e2840239aa70bb5993f1041987f0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:08 -0500
Subject: [PATCH 0176/1325] New translations assemblyscript-mappings.mdx
 (Spanish)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/es/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/es/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/es/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..792a6521f82d
--- /dev/null
+++ b/website/pages/es/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Descripción
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Escribir Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### ID recomendados para la creación de nuevas entidades
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Generación de código
+
+Para que trabajar con contratos inteligentes, eventos y entidades sea fácil y seguro desde el punto de vista de los tipos, Graph CLI puede generar tipos AssemblyScript a partir del esquema GraphQL del subgrafo y de las ABIs de los contratos incluidas en las fuentes de datos.
+
+Esto se hace con
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From f95d3cbc0e76292e1bad3f2f5493ea332419113f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:09 -0500
Subject: [PATCH 0177/1325] New translations install-the-cli.mdx (Spanish)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..9a754fb67035
--- /dev/null
+++ b/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Instalar The Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Descripción
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Empezando
+
+### Instalar The Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+En tu dispositivo, ejecuta alguno de los siguientes comandos:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Crear un Subgrafo
+
+### Desde un Contrato Existente
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### De un Subgrafo de Ejemplo
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+Los archivos ABI deben coincidir con tu(s) contrato(s). Hay varias formas de obtener archivos ABI:
+
+- Si estás construyendo tu propio proyecto, es probable que tengas acceso a tus ABIs más actuales.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Notas del lanzamiento                                                                                                                                                    |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 421f8d63fe0beed752e08e9cadb4acb3291dfe5a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:10 -0500
Subject: [PATCH 0178/1325] New translations ql-schema.mdx (Spanish)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/es/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..168d008294ed
--- /dev/null
+++ b/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Descripción
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Un buen ejemplo
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Un mal ejemplo
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Campos opcionales y obligatorios
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Tipos de Scalars incorporados
+
+#### GraphQL admite Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Tipo         | Descripción                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, representado como un string hexadecimal. Comúnmente utilizado para los hashes y direcciones de Ethereum.                                                                                             |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+También puedes crear enums dentro de un esquema. Los enums tienen la siguiente sintaxis:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Relaciones entre Entidades
+
+Una entidad puede tener una relación con otra u otras entidades de su esquema. Estas relaciones pueden ser recorridas en sus consultas. Las relaciones en The Graph son unidireccionales. Es posible simular relaciones bidireccionales definiendo una relación unidireccional en cada "extremo" de la relación.
+
+Las relaciones se definen en las entidades como cualquier otro campo, salvo que el tipo especificado es el de otra entidad.
+
+#### Relaciones Uno a Uno
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Relaciones one-to-many
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Búsquedas Inversas
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+En el caso de las relaciones one-to-many, la relación debe almacenarse siempre en el lado "one", y el lado "many" debe derivarse siempre. Almacenar la relación de esta manera, en lugar de almacenar una array de entidades en el lado "many", resultará en un rendimiento dramáticamente mejor tanto para la indexación como para la consulta del subgrafo. En general, debe evitarse, en la medida de lo posible, el almacenamiento de arrays de entidades.
+
+#### Ejemplo
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Relaciones de many-to-many
+
+Para las relaciones de many-to-many, como los usuarios pueden pertenecer a cualquier número de organizaciones, la forma más directa, pero generalmente no la más eficaz, de modelar la relación es en un array en cada una de las dos entidades implicadas. Si la relación es simétrica, sólo es necesario almacenar un lado de la relación y el otro puede derivarse.
+
+#### Ejemplo
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Este enfoque requiere que las consultas desciendan a un nivel adicional para recuperar, por ejemplo, las organizaciones para los usuarios:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Esta forma más elaborada de almacenar las relaciones many-to-many se traducirá en menos datos almacenados para el subgrafo y, por tanto, en un subgrafo que suele ser mucho más rápido de indexar y consultar.
+
+### Agregar comentarios al esquema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Definición de campos de búsqueda de texto completo
+
+Las consultas de búsqueda de texto completo filtran y clasifican las entidades basándose en una entrada de búsqueda de texto. Las consultas de texto completo pueden devolver coincidencias de palabras similares procesando el texto de la consulta en stems antes de compararlo con los datos del texto indexado.
+
+La definición de una consulta de texto completo incluye el nombre de la consulta, el diccionario lingüístico utilizado para procesar los campos de texto, el algoritmo de clasificación utilizado para ordenar los resultados y los campos incluidos en la búsqueda. Cada consulta de texto completo puede abarcar varios campos, pero todos los campos incluidos deben ser de un solo tipo de entidad.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Idiomas admitidos
+
+La elección de un idioma diferente tendrá un efecto definitivo, aunque a veces sutil, en la API de búsqueda de texto completo. Los campos cubiertos por un campo de consulta de texto completo se examinan en el contexto de la lengua elegida, por lo que los lexemas producidos por las consultas de análisis y búsqueda varían de un idioma a otro. Por ejemplo: al utilizar el diccionario turco compatible, "token" se convierte en "toke", mientras que el diccionario inglés lo convierte en "token".
+
+Diccionarios de idiomas admitidos:
+
+| Code   | Diccionario |
+| ------ | ----------- |
+| simple | General     |
+| da     | Danish      |
+| nl     | Dutch       |
+| en     | English     |
+| fi     | Finnish     |
+| fr     | French      |
+| de     | German      |
+| hu     | Hungarian   |
+| it     | Italian     |
+| no     | Norwegian   |
+| pt     | Portugués   |
+| ro     | Romanian    |
+| ru     | Russian     |
+| es     | Spanish     |
+| sv     | Swedish     |
+| tr     | Turkish     |
+
+### Algoritmos de Clasificación
+
+Algoritmos admitidos para ordenar los resultados:
+
+| Algorithm           | Description                                                                                        |
+| ------------------- | -------------------------------------------------------------------------------------------------- |
+| rank                | Usa la calidad de coincidencia (0-1) de la consulta de texto completo para ordenar los resultados. |
+| rango de proximidad | Similar to rank but also includes the proximity of the matches.                                    |

From 1f390cc0a686dd4c988c75dc4fbfc7859e49f0e1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:11 -0500
Subject: [PATCH 0179/1325] New translations subgraph-manifest.mdx (Spanish)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/es/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/es/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/es/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..d8d4f07fd43a
--- /dev/null
+++ b/website/pages/es/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Descripción
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Las entradas importantes a actualizar para el manifiesto son:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Los call handlers solo se activarán en uno de estos dos casos: cuando la función especificada sea llamada por una cuenta distinta del propio contrato o cuando esté marcada como externa en Solidity y sea llamada como parte de otra función en el mismo contrato.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Definición de un Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Función mapeo
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Handlers de bloques
+
+Además de suscribirse a eventos del contracto o calls de funciones, un subgrafo puede querer actualizar sus datos a medida que se añaden nuevos bloques a la cadena. Para ello, un subgrafo puede ejecutar una función después de cada bloque o después de los bloques que coincidan con un filtro predefinido.
+
+### Filtros admitidos
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+La ausencia de un filtro para un handler de bloque asegurará que el handler sea llamado en cada bloque. Una fuente de datos solo puede contener un handler de bloque para cada tipo de filtro.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Función mapeo
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Eventos anónimos
+
+Si necesitas procesar eventos anónimos en Solidity, puedes hacerlo proporcionando el tema 0 del evento, como en el ejemplo:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Recepción de transacciones en Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+Las triggers de una fuente de datos dentro de un bloque se ordenan mediante el siguiente proceso:
+
+1. Las triggers de eventos y calls se ordenan primero por el índice de la transacción dentro del bloque.
+2. Los triggers de eventos y calls dentro de la misma transacción se ordenan siguiendo una convención: primero los triggers de eventos y luego los de calls, respetando cada tipo el orden en que se definen en el manifiesto.
+3. Las triggers de bloques se ejecutan después de las triggers de eventos y calls, en el orden en que están definidos en el manifiesto.
+
+Estas normas de orden están sujetas a cambios.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Plantillas para fuentes de datos
+
+Un patrón común en los contratos inteligentes de Ethereum es el uso de contratos de registro o fábrica, donde un contrato crea, gestiona o hace referencia a un número arbitrario de otros contratos que tienen cada uno su propio estado y eventos.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Fuente de Datos para el Contrato Principal
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Plantillas de fuentes de datos para contratos creados dinámicamente
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instanciación de una plantilla de fuente de datos
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Si los bloques anteriores contienen datos relevantes para la nueva fuente de datos, lo mejor es indexar esos datos leyendo el estado actual del contrato y creando entidades que representen ese estado en el momento de crear la nueva fuente de datos.
+
+### Contexto de la fuente de datos
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Bloques iniciales
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Busca el contrato introduciendo su dirección en la barra de búsqueda.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Carga la página de detalles de la transacción, donde encontrarás el bloque inicial de ese contrato.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 169aa1428684e183ca2102b45cc30d68b978e400 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:12 -0500
Subject: [PATCH 0180/1325] New translations subgraphs.mdx (Arabic)

---
 website/pages/ar/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/ar/subgraphs.mdx b/website/pages/ar/subgraphs.mdx
index 27b452211477..d770a7cb9c57 100644
--- a/website/pages/ar/subgraphs.mdx
+++ b/website/pages/ar/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## دورة حياة الـ Subgraph
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 03de44a18c4aef8507f3836c1aa09dca8f6dab2d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:13 -0500
Subject: [PATCH 0181/1325] New translations transfer-to-the-graph.mdx (Arabic)

---
 .../pages/ar/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ar/cookbook/transfer-to-the-graph.mdx b/website/pages/ar/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..5c0446fa7fda 100644
--- a/website/pages/ar/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/ar/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### مثال
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### مصادر إضافية
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 7f0b7f11e333251015d2f546ad5eaf63cee92683 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:14 -0500
Subject: [PATCH 0182/1325] New translations advanced.mdx (Arabic)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/ar/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/ar/developing/creating-a-subgraph/advanced.mdx b/website/pages/ar/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..04984ebb31a6
--- /dev/null
+++ b/website/pages/ar/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## نظره عامة
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## أخطاء غير فادحة
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### نظره عامة
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### المراجع
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting على Subgraphs موجودة
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- يضيف أو يزيل أنواع الكيانات
+- يزيل الصفات من أنواع الكيانات
+- يضيف صفات nullable لأنواع الكيانات
+- يحول صفات non-nullable إلى صفات nullable
+- يضيف قيما إلى enums
+- يضيف أو يزيل الواجهات
+- يغير للكيانات التي يتم تنفيذ الواجهة لها
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From ba90df37431ac222cf1c588e1113133aebdc5460 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:15 -0500
Subject: [PATCH 0183/1325] New translations assemblyscript-mappings.mdx
 (Arabic)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/ar/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/ar/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ar/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2518d7620204
--- /dev/null
+++ b/website/pages/ar/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## نظره عامة
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## كتابة الـ Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### الـ IDs الموصى بها لإنشاء كيانات جديدة
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## توليد الكود
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+'import { Gravatar } from '../generated/schema
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From b5f45e557cb6bb141aeb858f0e74aaca4d70fd97 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:16 -0500
Subject: [PATCH 0184/1325] New translations install-the-cli.mdx (Arabic)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..4aa9caae2a28
--- /dev/null
+++ b/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: قم بتثبيت Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## نظره عامة
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### قم بتثبيت Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## إنشاء الـ Subgraph
+
+### من عقد موجود
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### من مثال Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+يجب أن تتطابق ملف (ملفات) ABI مع العقد (العقود) الخاصة بك. هناك عدة طرق للحصول على ملفات ABI:
+
+- إذا كنت تقوم ببناء مشروعك الخاص ، فمن المحتمل أن تتمكن من الوصول إلى أحدث ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| الاصدار | ملاحظات الإصدار                                                                                                                                                          |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 696e7e2ed7739dbcdad8b084c2b8fda8016efe8a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:18 -0500
Subject: [PATCH 0185/1325] New translations ql-schema.mdx (Arabic)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..b66db45260f0
--- /dev/null
+++ b/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## نظره عامة
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### مثال جيد
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### مثال سيئ
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### الحقول الاختيارية والمطلوبة
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+'Null value resolved for non-null field 'name
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### أنواع المقاييس المضمنة
+
+#### المقاييس المدعومة من GraphQL
+
+The following scalars are supported in the GraphQL API:
+
+| النوع        | الوصف                                                                                                                                                                                                            |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | مصفوفة Byte ، ممثلة كسلسلة سداسية عشرية. يشيع استخدامها في Ethereum hashes وعناوينه.                                                                                                                             |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### علاقات الكيانات
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### العلاقات واحد-لواحد
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### علاقات واحد-لمتعدد
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### البحث العكسي
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### مثال
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### علاقات متعدد_لمتعدد
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### مثال
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### إضافة تعليقات إلى المخطط (schema)
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## تعريف حقول البحث عن النص الكامل
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## اللغات المدعومة
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | القاموس    |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### خوارزميات التصنيف
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | استخدم جودة مطابقة استعلام النص-الكامل (0-1) لترتيب النتائج.            |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From ddcf777b2ebf7f9f4b1dc37d4dcf5b283de08829 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:19 -0500
Subject: [PATCH 0186/1325] New translations subgraph-manifest.mdx (Arabic)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/ar/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/ar/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ar/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..8c36c56b624a
--- /dev/null
+++ b/website/pages/ar/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## نظره عامة
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+الإدخالات الهامة لتحديث manifest هي:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## معالجات الاستدعاء(Call Handlers)
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### تعريف معالج الاستدعاء
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### دالة الـ Mapping
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## معالجات الكتلة
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### الفلاتر المدعومة
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### دالة الـ Mapping
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## أحداث الـ مجهول
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+يتم ترتيب المشغلات (triggers) لمصدر البيانات داخل الكتلة باستخدام العملية التالية:
+
+1. يتم ترتيب triggers الأحداث والاستدعاءات أولا من خلال فهرس الإجراء داخل الكتلة.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. يتم تشغيل مشغلات الكتلة بعد مشغلات الحدث والاستدعاء، بالترتيب المحدد في الـ manifest.
+
+قواعد الترتيب هذه عرضة للتغيير.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## قوالب مصدر البيانات
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### مصدر البيانات للعقد الرئيسي
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### قوالب مصدر البيانات للعقود التي تم إنشاؤها ديناميكيا
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### إنشاء قالب مصدر البيانات
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> إذا كانت الكتل السابقة تحتوي على بيانات ذات صلة بمصدر البيانات الجديد ، فمن الأفضل فهرسة تلك البيانات من خلال قراءة الحالة الحالية للعقد وإنشاء كيانات تمثل تلك الحالة في وقت إنشاء مصدر البيانات الجديد.
+
+### سياق مصدر البيانات
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## كتل البدء
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. ابحث عن العقد بإدخال عنوانه في شريط البحث.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. قم بتحميل صفحة تفاصيل الإجراء(transaction) حيث ستجد كتلة البدء لذلك العقد.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 17e6f8bfc7f9c5c742f526055016ce2be806dad2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:20 -0500
Subject: [PATCH 0187/1325] New translations subgraphs.mdx (Czech)

---
 website/pages/cs/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/cs/subgraphs.mdx b/website/pages/cs/subgraphs.mdx
index 27b452211477..386ea043e174 100644
--- a/website/pages/cs/subgraphs.mdx
+++ b/website/pages/cs/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Podgrafy
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Životní cyklus podgrafů
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From d6573989f5f8c8fd7492aa16ecf099eb158e79c2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:21 -0500
Subject: [PATCH 0188/1325] New translations transfer-to-the-graph.mdx (Czech)

---
 .../pages/cs/cookbook/transfer-to-the-graph.mdx  | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/cs/cookbook/transfer-to-the-graph.mdx b/website/pages/cs/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..e0b9a1fbfe53 100644
--- a/website/pages/cs/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/cs/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -31,7 +31,7 @@ You must have [Node.js](https://nodejs.org/) and a package manager of your choic
 
 On your local machine, run the following command:
 
-Using [npm](https://www.npmjs.com/):
+Použitím [npm](https://www.npmjs.com/):
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Příklad
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Další zdroje
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From b2a48df4f4961cc06cbfba293e7b66c15ac0d914 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:22 -0500
Subject: [PATCH 0189/1325] New translations advanced.mdx (Czech)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/cs/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/cs/developing/creating-a-subgraph/advanced.mdx b/website/pages/cs/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..fc663d24324b
--- /dev/null
+++ b/website/pages/cs/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Přehled
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Nefatální
+
+Chyby indexování v již synchronizovaných podgrafech ve výchozím nastavení způsobí selhání podgrafy a zastavení synchronizace. Podgrafy lze alternativně nakonfigurovat tak, aby pokračovaly v synchronizaci i při přítomnosti chyb, a to ignorováním změn provedených obslužnou rutinou, která chybu vyvolala. To dává autorům podgrafů čas na opravu jejich podgrafů, zatímco dotazy jsou nadále obsluhovány proti poslednímu bloku, ačkoli výsledky mohou být nekonzistentní kvůli chybě, která chybu způsobila. Všimněte si, že některé chyby jsou stále fatální. Aby chyba nebyla fatální, musí být známo, že je deterministická.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Povolení nefatálních chyb vyžaduje nastavení následujícího příznaku funkce v manifestu podgraf:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+Zdroje dat souborů jsou novou funkcí podgrafu pro přístup k datům mimo řetězec během indexování robustním a rozšiřitelným způsobem. Zdroje souborových dat podporují načítání souborů ze systému IPFS a z Arweave.
+
+> To také vytváří základ pro deterministické indexování dat mimo řetězec a potenciální zavedení libovolných dat ze zdrojů HTTP.
+
+### Přehled
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Průvodce upgradem
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Přidání nového typu entity, který bude aktualizován při nalezení souborů
+
+Zdroje dat souborů nemohou přistupovat k entitám založeným na řetězci ani je aktualizovat, ale musí aktualizovat entity specifické pro soubor.
+
+To může znamenat rozdělení polí ze stávajících entit do samostatných entit, které budou vzájemně propojeny.
+
+Původní kombinovaný entita:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Nové, rozdělená entit:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Pokud je vztah mezi nadřazenou entitou a entitou výsledného zdroje dat souboru 1:1, je nejjednodušším vzorem propojení nadřazené entity s entitou výsledného souboru pomocí CID IPFS jako vyhledávacího prvku. Pokud máte potíže s modelováním nových entit založených na souborech, ozvěte se na Discord!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Jedná se o zdroj dat, který bude vytvořen při identifikaci souboru zájmu.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Vytvoření nové obslužné pro zpracování souborů
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Příklad 
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn zdrojů dat souborů v případě potřeby
+
+Nyní můžete vytvářet zdroje dat souborů během provádění obslužných založených na řetězci:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Příklad:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+Tím se vytvoří nový zdroj dat souborů, který bude dotazovat nakonfigurovaný koncový bod IPFS nebo Arweave grafického uzlu a v případě nenalezení se pokusí o opakování. Když je soubor nalezen, spustí se obslužná zdroje dat souboru.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Gratulujeme, používáte souborové zdroje dat!
+
+#### Nasazení podgrafů
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Omezení
+
+Zpracovatelé a entity zdrojů dat souborů jsou izolovány od ostatních entit podgrafů, což zajišťuje, že jsou při provádění deterministické a nedochází ke kontaminaci zdrojů dat založených na řetězci. Přesněji řečeno:
+
+- Entity vytvořené souborovými zdroji dat jsou neměnné a nelze je aktualizovat
+- Obsluhy zdrojů dat souborů nemohou přistupovat k entita z jiných zdrojů dat souborů
+- K entita přidruženým k datovým zdrojům souborů nelze přistupovat pomocí zpracovatelů založených na řetězci
+
+> Ačkoli by toto omezení nemělo být pro většinu případů použití problematické, pro některé může představovat složitost. Pokud máte problémy s modelováním dat založených na souborech v podgrafu, kontaktujte nás prosím prostřednictvím služby Discord!
+
+Kromě toho není možné vytvářet zdroje dat ze zdroje dat souborů, ať už se jedná o zdroj dat v řetězci nebo jiný zdroj dat souborů. Toto omezení může být v budoucnu zrušeno.
+
+#### Osvědčené postupy
+
+Pokud propojovat metadata NFT s odpovídajícími tokeny, použijte hash IPFS metadat k odkazu na entita Metadata z entity Token. Uložte entitu Metadata s použitím hashe IPFS jako ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Pracujeme na zlepšení výše uvedeného doporučení, aby dotazy vracely pouze "nejnovější" verzi
+
+#### Známé problémy
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Příklady
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Odkazy:
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Roubování na existující podgrafy
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Protože se při roubování základní data spíše kopírují než indexují, je mnohem rychlejší dostat podgraf do požadovaného bloku než při indexování od nuly, i když počáteční kopírování dat může u velmi velkých podgrafů trvat i několik hodin. Během inicializace roubovaného podgrafu bude uzel Graf Uzel zaznamenávat informace o typů entit, které již byly zkopírovány.
+
+Roubované podgraf může používat schéma GraphQL, které není totožné se schématem základního podgrafu, ale je s ním pouze kompatibilní. Musí to být platné schéma podgrafu jako takové, ale může se od schématu základního podgrafu odchýlit následujícími způsoby:
+
+- Přidává nebo odebírá typy entit
+- Odstraňuje atributy z typů entit
+- Přidává nulovatelné atributy k typům entit
+- Mění nenulovatelné atributy na nulovatelné atributy
+- Přidává hodnoty de enums
+- Přidává nebo odebírá rozhraní
+- Mění se, pro které typy entit je rozhraní implementováno
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 340e97be3dc666b023049b90923908b696f2e89c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:24 -0500
Subject: [PATCH 0190/1325] New translations assemblyscript-mappings.mdx
 (Czech)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/cs/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/cs/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/cs/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..fad0d6ebaa1a
--- /dev/null
+++ b/website/pages/cs/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Přehled
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Psát mapování
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Doporučené IDa pro vytváření nových Entity
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Zpracování entit se stejnými ID
+
+Pokud při vytváření a ukládání nové entity již existuje entita se stejným ID, jsou při slučování vždy upřednostněny vlastnosti nové entity. To znamená, že existující entita bude aktualizována hodnotami z nové entity.
+
+Pokud je pro pole v nové entitě se stejným ID záměrně nastavena nulová hodnota, bude stávající entita aktualizována s nulovou hodnotou.
+
+Pokud není pro pole v nové entitě se stejným ID nastavena žádná hodnota, bude pole rovněž nulové.
+
+## Generování kódu
+
+Aby byla práce s inteligentními smlouvami, událostmi a entitami snadná a typově bezpečná, může Graf CLI generovat typy AssemblyScript ze schématu GraphQL podgrafu a ABI smluv obsažených ve zdrojích dat.
+
+To se provádí pomocí
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 7d578d55cfe87cf1b774c606ef00fa4bd1ef9609 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:25 -0500
Subject: [PATCH 0191/1325] New translations install-the-cli.mdx (Czech)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..e03ed92103bf
--- /dev/null
+++ b/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Instalace Graf CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Přehled
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Začínáme
+
+### Instalace Graf CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+V místním počítači spusťte jeden z následujících příkazů:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Vytvoření podgrafu
+
+### Ze stávající smlouvy
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### Z příkladu podgrafu
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+Soubor(y) ABI se musí shodovat s vaší smlouvou. Soubory ABI lze získat několika způsoby:
+
+- Pokud vytváříte vlastní projekt, budete mít pravděpodobně přístup k nejaktuálnějším ABI.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Verze | Poznámky vydání                                                                                                                                                          |
+| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
+| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |

From df2007c45f6ac0a1f560277a64eee8b19be9ae4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:26 -0500
Subject: [PATCH 0192/1325] New translations ql-schema.mdx (Czech)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..b284541e1b5e
--- /dev/null
+++ b/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Přehled
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Dobrý příklad
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Špatný příklad
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Nepovinná a povinná pole
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Vyřešení nulové hodnoty pro pole 'name', které není nulové
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Vestavěné typy skalárů
+
+#### Podporované skaláry GraphQL
+
+The following scalars are supported in the GraphQL API:
+
+| Typ          | Popis                                                                                                                                                                                                            |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Pole bajtů reprezentované jako hexadecimální řetězec. Běžně se používá pro hashe a adresy Ethereum.                                                                                                              |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+Výčty můžete vytvářet také v rámci schématu. Syntaxe enumů je následující:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Vztahy entit
+
+Entita může mít vztah k jedné nebo více jiným entitám ve vašem schématu. Tyto vztahy lze procházet v dotazech. Vztahy v Graf jsou jednosměrné. Obousměrné vztahy je možné simulovat definováním jednosměrného vztahu na obou "koncích" vztahu.
+
+Vztahy se definují u entit stejně jako u jiných polí s tím rozdílem, že zadaný typ je typ jiné entity.
+
+#### Vztahy jeden na jednoho
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Vztahy jeden k mnoha
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Zpětné vyhledávání
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+U vztahů typu "jeden k mnoha" by měl být vztah vždy uložen na straně "jeden" a strana "mnoho" by měla být vždy odvozena. Uložení vztahu tímto způsobem namísto uložení pole entit na straně "mnoho" povede k výrazně lepšímu výkonu jak při indexování, tak při dotazování na podgraf. Obecně platí, že ukládání polí entit je třeba se vyhnout, pokud je to praktické.
+
+#### Příklad
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Vztahy mnoho k mnoha
+
+Pro vztahy mnoho-více, jako jsou uživatelé, z nichž každý může patřit do libovolného počtu organizací, je nejjednodušší, ale obecně ne nejvýkonnější, modelovat vztah jako pole v každé z obou zúčastněných entit. Pokud je vztah symetrický, je třeba uložit pouze jednu stranu vztahu a druhou stranu lze odvodit.
+
+#### Příklad
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Tento přístup vyžaduje, aby dotazy sestupovaly do další úrovně, aby bylo možné získat například organizace pro uživatele:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Tento propracovanější způsob ukládání vztahů mnoho-více vede k menšímu množství dat uložených pro podgraf, a tedy k podgrafu, který je často výrazně rychlejší při indexování a dotazování.
+
+### Přidání komentářů do schématu
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Definování polí fulltextového vyhledávání
+
+Fulltextové vyhledávací dotazy filtrují a řadí entity na základě textového vyhledávacího vstupu. Fulltextové dotazy jsou schopny vracet shody podobných slov tím, že zpracovávají vstupní text dotazu do kmenů před jejich porovnáním s indexovanými textovými daty.
+
+Definice fulltextového dotazu obsahuje název dotazu, jazykový slovník použitý ke zpracování textových polí, algoritmus řazení použitý k seřazení výsledků a pole zahrnutá do vyhledávání. Každý fulltextový dotaz může zahrnovat více polí, ale všechna zahrnutá pole musí být z jednoho typu entity.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Podporované jazyky
+
+Výběr jiného jazyka bude mít na rozhraní API fulltextového vyhledávání rozhodující, i když někdy nenápadný vliv. Pole zahrnutá do pole fulltextového dotazu jsou zkoumána v kontextu zvoleného jazyka, takže lexémy vytvořené analýzou a vyhledávacími dotazy se v jednotlivých jazycích liší. Například: při použití podporovaného tureckého slovníku je "token" odvozeno od "toke", zatímco anglický slovník jej samozřejmě odvozuje od "token".
+
+Podporované jazykové slovníky:
+
+| Code       | Slovník    |
+| ---------- | ---------- |
+| jednoduchý | General    |
+| da         | Danish     |
+| nl         | Dutch      |
+| en         | English    |
+| fi         | Finnish    |
+| fr         | French     |
+| de         | German     |
+| hu         | Hungarian  |
+| it         | Italian    |
+| no         | Norwegian  |
+| pt         | Portuguese |
+| ro         | Romanian   |
+| ru         | Russian    |
+| es         | Spanish    |
+| sv         | Swedish    |
+| tr         | Turkish    |
+
+### Algoritmy řazení
+
+Podporované algoritmy pro řazení výsledků:
+
+| Algorithm     | Description                                                              |
+| ------------- | ------------------------------------------------------------------------ |
+| rank          | Pro seřazení výsledků použijte kvalitu shody (0-1) fulltextového dotazu. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.          |

From 780bfe3fc04f735875a4b91e63ceeb0115e05772 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:28 -0500
Subject: [PATCH 0193/1325] New translations subgraph-manifest.mdx (Czech)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/cs/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/cs/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/cs/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..84ff104974cf
--- /dev/null
+++ b/website/pages/cs/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Přehled
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Důležité položky, které je třeba v manifestu aktualizovat, jsou:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Zpracovatelé hovorů
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Obsluhy volání se spustí pouze v jednom ze dvou případů: když je zadaná funkce volána jiným účtem než samotnou smlouvou nebo když je v Solidity označena jako externí a volána jako součást jiné funkce ve stejné smlouvě.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Definice obsluhy volání
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Funkce mapování
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Obsluha bloků
+
+Kromě přihlášení k událostem smlouvy nebo volání funkcí může podgraf chtít aktualizovat svá data, když jsou do řetězce přidány nové bloky. Za tímto účelem může podgraf spustit funkci po každém bloku nebo po blocích, které odpovídají předem definovanému filtru.
+
+### Podporované filtry
+
+#### Filtr volání
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+Protože pro obsluhu bloku neexistuje žádný filtr, zajistí, že obsluha bude volána každý blok. Zdroj dat může obsahovat pouze jednu blokovou obsluhu pro každý typ filtru.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Filtr dotazování
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Jednou Filtr
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Definovaný obslužná rutina s filtrem once bude zavolána pouze jednou před spuštěním všech ostatních rutin. Tato konfigurace umožňuje, aby podgraf používal obslužný program jako inicializační obslužný, který provádí specifické úlohy na začátku indexování.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Funkce mapování
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymní události
+
+Pokud potřebujete v Solidity zpracovávat anonymní události, lze toho dosáhnout zadáním tématu 0 události, jak je uvedeno v příkladu:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Potvrzení transakcí v obslužných rutinách událostí
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Pořadí spouštěcích Handlers
+
+Spouštěče pro zdroj dat v rámci bloku jsou seřazeny podle následujícího postupu:
+
+1. Spouštěče událostí a volání jsou nejprve seřazeny podle indexu transakce v rámci bloku.
+2. Spouštěče událostí a volání v rámci jedné transakce jsou seřazeny podle konvence: nejprve spouštěče událostí a poté spouštěče volání, přičemž každý typ dodržuje pořadí, v jakém jsou definovány v manifestu.
+3. Spouštěče bloků jsou spuštěny po spouštěčích událostí a volání, v pořadí, v jakém jsou definovány v manifestu.
+
+Tato pravidla objednávání se mohou změnit.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Šablony zdrojů dat
+
+Běžným vzorem v inteligentních smlouvách kompatibilních s EVM je používání registrů nebo továrních smluv, kdy jedna smlouva vytváří, spravuje nebo odkazuje na libovolný počet dalších smluv, z nichž každá má svůj vlastní stav a události.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Zdroj dat pro hlavní smlouvu
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Šablony zdrojů dat pro dynamicky vytvářené smlouvy
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instancování šablony zdroje dat
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Pokud předchozí bloky obsahují data relevantní pro nový zdroj dat, je nejlepší tato data indexovat načtením aktuálního stavu smlouvy a vytvořením entit reprezentujících tento stav v době vytvoření nového zdroje dat.
+
+### Kontext zdroje dat
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Výchozí bloky
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Vyhledejte smlouvu zadáním její adresy do vyhledávacího řádku.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Načtěte stránku s podrobnostmi o transakci, kde najdete počáteční blok pro danou smlouvu.
+
+## Tipy indexátor
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prořezávat
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. Konkrétní číslo: Nastaví vlastní limit počtu historických bloků, které se mají zachovat.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+Uchování určitého množství historických dat:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+Zachování kompletní historie entitních států:
+
+```
+indexerHints:
+  prune: never
+```

From d4a66daa111ba28f6254a4b39dd2b71c24c07fad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:29 -0500
Subject: [PATCH 0194/1325] New translations subgraphs.mdx (German)

---
 website/pages/de/subgraphs.mdx | 91 +++++++++++++++++++++++++---------
 1 file changed, 68 insertions(+), 23 deletions(-)

diff --git a/website/pages/de/subgraphs.mdx b/website/pages/de/subgraphs.mdx
index 27b452211477..58cf1e9f6498 100644
--- a/website/pages/de/subgraphs.mdx
+++ b/website/pages/de/subgraphs.mdx
@@ -1,41 +1,86 @@
 ---
-title: Subgraphs
+title: Subgraphen
 ---
 
-## What is a Subgraph?
+## Was ist ein Subgraph?
 
-A subgraph is a custom, open API that extracts data from a blockchain, processes it, and stores it so it can be easily queried via GraphQL.
+Ein Subgraph ist eine benutzerdefinierte, offene API, die Daten aus einer Blockchain extrahiert, verarbeitet und so speichert, dass sie einfach über GraphQL abgefragt werden können.
 
-### Subgraph Capabilities
+### Subgraph-Fähigkeiten
 
-- **Access Data:** Subgraphs enable the querying and indexing of blockchain data for web3.
-- **Build:** Developers can build, deploy, and publish subgraphs to The Graph Network. To get started, check out the subgraph developer [Quick Start](quick-start/).
-- **Index & Query:** Once a subgraph is indexed, anyone can query it. Explore and query all subgraphs published to the network in [Graph Explorer](https://thegraph.com/explorer).
+- **Zugangsdaten:** Subgraphs ermöglichen die Abfrage und Indizierung von Blockchain-Daten für web3.
+- **Build:** Entwickler können Subgraphs für The Graph Network erstellen, bereitstellen und veröffentlichen. Um loszulegen, schauen Sie sich den Subgraph Entwickler [Quick Start](quick-start/) an.
+- **Index & Abfrage:** Sobald ein Subgraph indiziert ist, kann jeder ihn abfragen. Alle im Netzwerk veröffentlichten Subgraphen können im [Graph Explorer] (https://thegraph.com/explorer) untersucht und abgefragt werden.
 
-## Inside a Subgraph
+## Innerhalb eines Subgraph
 
-The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+Das Subgraph-Manifest, `subgraph.yaml`, definiert die Smart Contracts und das Netzwerk, die Ihr Subgraph indizieren wird, die Ereignisse aus diesen Verträgen, auf die geachtet werden soll, und wie die Ereignisdaten auf Entitäten abgebildet werden, die Graph Node speichert und abfragen kann.
 
-The **subgraph definition** consists of the following files:
+Die **Subgraph-Definition** besteht aus den folgenden Dateien:
 
-- `subgraph.yaml`: Contains the subgraph manifest
+- subgraph.yaml": Enthält das Manifest des Subgraphen
 
-- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+- schema.graphql": Ein GraphQL-Schema, das die für Ihren Subgraph gespeicherten Daten definiert und festlegt, wie sie über GraphQL abgefragt werden können
 
-- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
+- mapping.ts\`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) Code, der die Ereignisdaten in die in Ihrem Schema definierten Entitäten übersetzt
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+Um mehr über die einzelnen Komponenten eines Subgraphs zu erfahren, lesen Sie bitte [Erstellen eines Subgraphs](/developing/creating-a-subgraph/).
 
-## Subgraph Development
+## Subgraph Lebenszyklus
 
-1. [Create a subgraph](/developing/creating-a-subgraph/)
-2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/)
-3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio)
-4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
-5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
+Hier ist ein allgemeiner Überblick über den Lebenszyklus eines Subgraphs:
 
-## Subgraph Lifecycle
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
-Here is a general overview of a subgraph’s lifecycle:
+## Subgraph Entwicklung
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+1. [Einen Subgraph erstellen](/entwickeln/einen-subgraph-erstellen/)
+2. [Einen Subgraph bereitstellen](/deploying/deploying-a-subgraph-to-studio/)
+3. [Testen eines Subgraphen](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio)
+4. [Einen Subgraph veröffentlichen](/publishing/publishing-a-subgraph/)
+5. [Signal auf einem Subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
+
+### Build locally
+
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
+
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 337ff8320f11cf870a87b16deabe6b6c966b4742 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:30 -0500
Subject: [PATCH 0195/1325] New translations transfer-to-the-graph.mdx (German)

---
 .../pages/de/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/de/cookbook/transfer-to-the-graph.mdx b/website/pages/de/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..3844b7a94142 100644
--- a/website/pages/de/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/de/cookbook/transfer-to-the-graph.mdx
@@ -12,15 +12,15 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
 ### Create a Subgraph in Subgraph Studio
 
-- Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+- Gehen Sie zu [Subgraph Studio] (https://thegraph.com/studio/) und verbinden Sie Ihre Wallet.
 - Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
 
 > Note: After publishing, the subgraph name will be editable but requires on-chain action each time, so name it properly.
@@ -31,7 +31,7 @@ You must have [Node.js](https://nodejs.org/) and a package manager of your choic
 
 On your local machine, run the following command:
 
-Using [npm](https://www.npmjs.com/):
+Verwendung von [npm](https://www.npmjs.com/):
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 

From 11c7dc5d913d0576fede7c24fa30cad61324e982 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:31 -0500
Subject: [PATCH 0196/1325] New translations advanced.mdx (German)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/de/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/de/developing/creating-a-subgraph/advanced.mdx b/website/pages/de/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..6a27f4a235a0
--- /dev/null
+++ b/website/pages/de/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Beispiele
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From bb34d5daa4a662571fd727c7660332ee23bf50e6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:33 -0500
Subject: [PATCH 0197/1325] New translations assemblyscript-mappings.mdx
 (German)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/de/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/de/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/de/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/de/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From c3161d1ebc70a382209702ed5f95955e2aa12a7b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:34 -0500
Subject: [PATCH 0198/1325] New translations install-the-cli.mdx (German)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..6b68f875fdd2
--- /dev/null
+++ b/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+Führen Sie einen der folgenden Befehle auf Ihrem lokalen Computer aus:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Create a Subgraph
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Besonderheiten
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From bdbd6d2baaa3f5040655dba64de2bd027578e52f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:35 -0500
Subject: [PATCH 0199/1325] New translations ql-schema.mdx (German)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/de/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From f8bc827a9ee6805862d6690749cadc2bd11d7dba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:36 -0500
Subject: [PATCH 0200/1325] New translations subgraph-manifest.mdx (German)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/de/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/de/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/de/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..0adbd44216a0
--- /dev/null
+++ b/website/pages/de/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+Das Subgraph-Manifest, `subgraph.yaml`, definiert die Smart Contracts und das Netzwerk, die Ihr Subgraph indizieren wird, die Ereignisse aus diesen Verträgen, auf die geachtet werden soll, und wie die Ereignisdaten auf Entitäten abgebildet werden, die Graph Node speichert und abfragen kann.
+
+Die **Subgraph-Definition** besteht aus den folgenden Dateien:
+
+- subgraph.yaml": Enthält das Manifest des Subgraphen
+
+- schema.graphql": Ein GraphQL-Schema, das die für Ihren Subgraph gespeicherten Daten definiert und festlegt, wie sie über GraphQL abgefragt werden können
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph-Fähigkeiten
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From e7b2a5986ac14dc8716f8bd1eb7da33261da6869 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:37 -0500
Subject: [PATCH 0201/1325] New translations index.json (Japanese)

---
 website/pages/ja/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/ja/index.json b/website/pages/ja/index.json
index 55ca30b1bf39..7e8c957541eb 100644
--- a/website/pages/ja/index.json
+++ b/website/pages/ja/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "グラフエクスプローラ",
         "description": "サブグラフの探索とプロトコルとの対話"
-      },
-      "hostedService": {
-        "title": "ホステッド サービス",
-        "description": "ホスティングサービスでのサブグラフの作成と探索"
       }
     }
   },

From d21dcd05c38db18f530cefab7e5dbe549c96cd12 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:38 -0500
Subject: [PATCH 0202/1325] New translations index.json (Korean)

---
 website/pages/ko/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/ko/index.json b/website/pages/ko/index.json
index cf306c8bfd31..7b5de0b796fd 100644
--- a/website/pages/ko/index.json
+++ b/website/pages/ko/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explore subgraphs and interact with the protocol"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 8a33b411c87e82676a8b46383786e149be6ec7d2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:39 -0500
Subject: [PATCH 0203/1325] New translations index.json (Dutch)

---
 website/pages/nl/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/nl/index.json b/website/pages/nl/index.json
index 29aad7f6c047..357c0bbf8d61 100644
--- a/website/pages/nl/index.json
+++ b/website/pages/nl/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Verkenner",
         "description": "Verken subgraphs en interacteer met het protocol"
-      },
-      "hostedService": {
-        "title": "Gehoste Dienst",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From f307bff3e86b66ee355d16ba2fd0e96a218d6d79 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:40 -0500
Subject: [PATCH 0204/1325] New translations near.mdx (Italian)

---
 website/pages/it/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/it/cookbook/near.mdx b/website/pages/it/cookbook/near.mdx
index 36d5ba913b3d..1d2edfe873eb 100644
--- a/website/pages/it/cookbook/near.mdx
+++ b/website/pages/it/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 8f322cec1305539e3335dea0d9b735fd9c6e0f6b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:42 -0500
Subject: [PATCH 0205/1325] New translations unit-testing-framework.mdx
 (Italian)

---
 .../it/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/it/developing/unit-testing-framework.mdx b/website/pages/it/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/it/developing/unit-testing-framework.mdx
+++ b/website/pages/it/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 97b9bb458ca927938ffd1ec1cc36a11df5301a0b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:43 -0500
Subject: [PATCH 0206/1325] New translations about.mdx (Japanese)

---
 website/pages/ja/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/ja/about.mdx b/website/pages/ja/about.mdx
index 564163774630..db8864a69b0f 100644
--- a/website/pages/ja/about.mdx
+++ b/website/pages/ja/about.mdx
@@ -2,46 +2,66 @@
 title: The Graphについて
 ---
 
-このページでは、「The Graph」とは何か、どのようにして始めるのかを説明します。
-
 ## とは「ザ・グラフ」
 
-グラフは、ブロックチェーン データのインデックス作成とクエリを行うための分散型プロトコルです。
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-[Uniswap](https://uniswap.org/)のような複雑なスマートコントラクトを持つプロジェクトや、[Bored Ape Yacht Club](https://boredapeyachtclub.com/) のような NFT の取り組みでは、Ethereum のブロックチェーンにデータを保存しているため、基本的なデータ以外をブロックチェーンから直接読み取ることは実に困難です。
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-独自のサーバーを構築し、そこでトランザクションを処理してデータベースに保存し、その上に API エンドポイントを構築してデータをクエリすることもできます。ただし、このオプションは[リソース集約的](/network/benefits/)であり、メンテナンスが必要であり、単一障害点が存在し、分散化に必要な重要なセキュリティ プロパティが壊れます。
+### How The Graph Functions
 
-**ブロックチェーンデータのインデックス作成は非常に困難です。**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## The Graph の仕組み
+- 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.
 
-The Graph は、サブグラフマニフェストと呼ばれるサブグラフ記述に基づいて、Ethereum のデータに何をどのようにインデックスするかを学習します。 サブグラフマニフェストは、そのサブグラフで注目すべきスマートコントラクト、注目すべきコントラクト内のイベント、イベントデータと The Graph がデータベースに格納するデータとのマッピング方法などを定義します。
+- When creating a subgraph, you need to write a subgraph manifest.
 
-`サブグラフのマニフェスト`を書いたら、グラフの CLI を使ってその定義を IPFS に保存し、インデクサーにそのサブグラフのデータのインデックス作成を開始するように指示します。
+- 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.
 
-この図では、サブグラフ・マニフェストがデプロイされた後のデータの流れについて、Ethereum のトランザクションを扱って詳しく説明しています。
+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 は、Ethereum の新しいブロックと、それに含まれる自分のサブグラフのデータを継続的にスキャンします。
-4. Graph Node は、これらのブロックの中からあなたのサブグラフの Ethereum イベントを見つけ出し、あなたが提供したマッピングハンドラーを実行します。 マッピングとは、イーサリアムのイベントに対応して Graph Node が保存するデータエンティティを作成または更新する WASM モジュールのことです。
-5. Dapp は、ノードの [GraphQL エンドポイント](https://graphql.org/learn/) を使用して、ブロックチェーンからインデックス付けされたデータをグラフ ノードに照会します。グラフ ノードは、ストアのインデックス作成機能を利用して、このデータを取得するために、GraphQL クエリを基盤となるデータ ストアのクエリに変換します。 dapp は、このデータをエンドユーザー向けの豊富な UI に表示し、エンドユーザーはそれを使用して Ethereum で新しいトランザクションを発行します。サイクルが繰り返されます。
+1.  Dapp は、スマート コントラクトのトランザクションを通じて Ethereum にデータを追加します。
+2.  スマートコントラクトは、トランザクションの処理中に 1 つまたは複数のイベントを発行します。
+3.  Graph Node は、Ethereum の新しいブロックと、それに含まれる自分のサブグラフのデータを継続的にスキャンします。
+4.  Graph Node は、これらのブロックの中からあなたのサブグラフの Ethereum イベントを見つけ出し、あなたが提供したマッピングハンドラーを実行します。 マッピングとは、イーサリアムのイベントに対応して Graph Node が保存するデータエンティティを作成または更新する WASM モジュールのことです。
+5.  Dapp は、ノードの [GraphQL エンドポイント](https://graphql.org/learn/) を使用して、ブロックチェーンからインデックス付けされたデータをグラフ ノードに照会します。グラフ ノードは、ストアのインデックス作成機能を利用して、このデータを取得するために、GraphQL クエリを基盤となるデータ ストアのクエリに変換します。 dapp は、このデータをエンドユーザー向けの豊富な UI に表示し、エンドユーザーはそれを使用して Ethereum で新しいトランザクションを発行します。サイクルが繰り返されます。
 
 ## 次のステップ
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 74e6a5f57ea7907156adaed9c43123455da75324 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:45 -0500
Subject: [PATCH 0207/1325] New translations near.mdx (Japanese)

---
 website/pages/ja/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ja/cookbook/near.mdx b/website/pages/ja/cookbook/near.mdx
index 31c22005ed9c..8c5f1625eaeb 100644
--- a/website/pages/ja/cookbook/near.mdx
+++ b/website/pages/ja/cookbook/near.mdx
@@ -37,7 +37,7 @@ NEAR サブグラフの開発には、バージョン`0.23.0`以上の`graph-cli
 
 **schema.graphql:**: サブグラフのためにどのようなデータが保存されているか、そして GraphQL を介してどのようにクエリを行うかを定義するスキーマファイル。NEAR サブグラフの要件は、[既存のドキュメント](/developing/creating-a-subgraph#the-graphql-schema)でカバーされています。
 
-**AssemblyScript Mappings:**: [AssemblyScript code](/developing/graph-ts/api)は、イベントデータから、スキーマで定義されたエンティティに変換するコードです。NEAR サポートでは、NEAR 固有のデータタイプと、新しい JSON パース機能が導入されています。
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 サブグラフの開発には 2 つの重要なコマンドがあります:
 
@@ -98,7 +98,7 @@ NEAR データソースは 2 種類のハンドラーをサポートしていま
 
 イベントを処理するためのハンドラは[AssemblyScript](https://www.assemblyscript.org/)で書かれています。
 
-NEAR インデックスは、[AssemblyScript API](/developing/graph-ts/api)に NEAR 固有のデータタイプを導入します。
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ class ReceiptWithOutcome {
 - ブロックハンドラーは、`Block`を受け取ります
 - レシートハンドラーは`ReceiptWithOutcome`を受け取ります
 
-その他、マッピング実行中の NEAR サブグラフ開発者は、 [AssemblyScript API](/developing/graph-ts/api)の残りの部分を利用できます。
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-これには、新しい JSON parsing function が含まれています。NEAR のログは、頻繁に文字列化された JSON として出力されます。新しい`json.fromString(...)`関数は、開発者がこれらのログを簡単に処理できるように、[JSON API](/developing/graph-ts/api#json-api)の一部として利用できます。
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## NEAR サブグラフの展開
 
@@ -194,8 +194,8 @@ $ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <su
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### ローカル グラフ ノード (デフォルト構成に基づく)

From 472f3121ddbd89d04df5a9440495eee473d7ac6f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:46 -0500
Subject: [PATCH 0208/1325] New translations unit-testing-framework.mdx
 (Japanese)

---
 .../ja/developing/unit-testing-framework.mdx  | 45 ++++++++++++-------
 1 file changed, 29 insertions(+), 16 deletions(-)

diff --git a/website/pages/ja/developing/unit-testing-framework.mdx b/website/pages/ja/developing/unit-testing-framework.mdx
index 2f974da77808..89cbd8222458 100644
--- a/website/pages/ja/developing/unit-testing-framework.mdx
+++ b/website/pages/ja/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: ユニットテストフレームワーク
 ---
 
-Matchstick は[LimeChain](https://limechain.tech/)が開発したユニットテストフレームワークで、サブグラフの開発者がサンドボックス環境でマッピングロジックをテストし、自信を持ってサブグラフをデプロイすることができます!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## はじめに
 
-### 依存関係のインストール
+### Install Dependencies
 
-テストヘルパーメソッドを使用し、テストを実行するためには、以下の依存関係をインストールする必要があります：
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` はPostgreSQLに依存しているので、もしまだ持っていなければ、インストールする必要があります。他の方法で追加すると予期しないエラーが発生する可能性があるので、以下のコマンドを使用することを強くお勧めします！
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgresのインストールコマンド：
+Installation command:
 
 ```sh
 postgresql をインストールします。
@@ -30,15 +39,15 @@ postgresql をインストールします。
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgresのインストールコマンド（お使いのディストロに依存します）。
+Installation command (depends on your distro):
 
 ```sh
 sudo apt postgresql をインストール
 ```
 
-### WSL (Linux 用 Windows サブシステム)
+### Using WSL (Windows Subsystem for Linux)
 
 WSLでは、Dockerアプローチとバイナリアプローチの両方でMatchstickを使用することができます。WSLは少しトリッキーなので、以下のような問題に遭遇した場合のヒントを紹介します。
 
@@ -76,7 +85,7 @@ sudo apt-get install libpq-dev （インストール）
 }
 ```
 
-### 使い方
+### Using Matchstick
 
 **Matchstick** をサブグラフ・プロジェクトで使用するには、ターミナルを開き、プロジェクトのルート・フォルダに移動して、 `graph test [options] <datasource>` と実行するだけで、最新の **Matchstick** バイナリがダウンロードされて、テスト・フォルダにある指定したテストまたは全てのテストが実行されます (datasource flag が指定されていなければ既存の全てのテスト).
 
@@ -1368,22 +1377,26 @@ Global test coverage: 22.2% (2/9 handlers).
 
 > Critical: 有効なモジュールから WasmInstance を作成できない。コンテキストが不明 インポート: wasi_snapshot_preview1::fd_write が定義されていない
 
-これは、コード内で`console.log`を使用していることを意味し、AssemblyScriptではサポートされていません。[Logging API](/developing/graph-ts/api/#logging-api) の利用をご検討ください。
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: 期待された引数は?
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: 期待された引数は?
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 引数の不一致は、`graph-ts`と`matchstick-as`の不一致によって起こります。このような問題を解決する最善の方法は、すべてを最新のリリース版にアップデートすることです。
 
+## その他のリソース
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## フィードバック
 
 質問、フィードバックなどがありましたら、The Graph DiscordにMatchstick専用のチャンネル🔥| unit-testing がありますので、そちらにお問い合わせください。

From 62862c2dc5b707a6ee18e6286b63c828bca98b41 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:47 -0500
Subject: [PATCH 0209/1325] New translations about.mdx (Korean)

---
 website/pages/ko/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/ko/about.mdx b/website/pages/ko/about.mdx
index 36c6a49f8fbc..9c21bf00d08f 100644
--- a/website/pages/ko/about.mdx
+++ b/website/pages/ko/about.mdx
@@ -2,46 +2,66 @@
 title: About The Graph
 ---
 
-This page will explain what The Graph is and how you can get started.
-
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Projects with complex smart contracts like [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it really difficult to read anything other than basic data directly from the blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+### How The Graph Functions
 
-**Indexing blockchain data is really, really hard.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## How The Graph Works
+- 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.
 
-The Graph learns what and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph description defines the smart contracts of interest for a subgraph, the events in those contracts to pay attention to, and how to map event data to data that The Graph will store in its database.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Once you have written a `subgraph manifest`, you use the Graph CLI to store the definition in IPFS and tell the indexer to start indexing data for that subgraph.
+- 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+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.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 3d055c221fabc3152099cfb5390ce20e9eca5996 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:49 -0500
Subject: [PATCH 0210/1325] New translations near.mdx (Korean)

---
 website/pages/ko/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ko/cookbook/near.mdx b/website/pages/ko/cookbook/near.mdx
index a4f27caf6f3c..f2509e44e84c 100644
--- a/website/pages/ko/cookbook/near.mdx
+++ b/website/pages/ko/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 88f70915674079f2b826e876804157a3719d5dae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:50 -0500
Subject: [PATCH 0211/1325] New translations unit-testing-framework.mdx
 (Korean)

---
 .../ko/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/ko/developing/unit-testing-framework.mdx b/website/pages/ko/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/ko/developing/unit-testing-framework.mdx
+++ b/website/pages/ko/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 841b63b33b12240beda36ab46f7602cf9dece3bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:51 -0500
Subject: [PATCH 0212/1325] New translations about.mdx (Dutch)

---
 website/pages/nl/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/nl/about.mdx b/website/pages/nl/about.mdx
index bebff0a938a1..641ff09b8d15 100644
--- a/website/pages/nl/about.mdx
+++ b/website/pages/nl/about.mdx
@@ -2,46 +2,66 @@
 title: Over The Graph
 ---
 
-This page will explain what The Graph is and how you can get started.
-
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Projects with complex smart contracts like [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it really difficult to read anything other than basic data directly from the blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+### How The Graph Functions
 
-**Indexing blockchain data is really, really hard.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## How The Graph Works
+- 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.
 
-The Graph learns what and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph description defines the smart contracts of interest for a subgraph, the events in those contracts to pay attention to, and how to map event data to data that The Graph will store in its database.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Once you have written a `subgraph manifest`, you use the Graph CLI to store the definition in IPFS and tell the indexer to start indexing data for that subgraph.
+- 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+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.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From ad28014b1a3a49d877502d81504c2e69871087b0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:53 -0500
Subject: [PATCH 0213/1325] New translations near.mdx (Dutch)

---
 website/pages/nl/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/nl/cookbook/near.mdx b/website/pages/nl/cookbook/near.mdx
index c5416e3996fd..46090338ae0d 100644
--- a/website/pages/nl/cookbook/near.mdx
+++ b/website/pages/nl/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 2300f40bd35e68f04a00543f4ac077977d106be5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:54 -0500
Subject: [PATCH 0214/1325] New translations unit-testing-framework.mdx (Dutch)

---
 .../nl/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/nl/developing/unit-testing-framework.mdx b/website/pages/nl/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/nl/developing/unit-testing-framework.mdx
+++ b/website/pages/nl/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 4d2b8557fdf9f2802f1d42039bf53b551876fbde Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:55 -0500
Subject: [PATCH 0215/1325] New translations graphql-api.mdx (Italian)

---
 website/pages/it/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/it/querying/graphql-api.mdx b/website/pages/it/querying/graphql-api.mdx
index 27fb075488ec..4c89c5b31f13 100644
--- a/website/pages/it/querying/graphql-api.mdx
+++ b/website/pages/it/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: API GraphQL
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Query
+## What is GraphQL?
 
-Nello schema di subgraph si definiscono tipi chiamati `Entities`. Per ogni tipo di `Entity`, un'`entity` e un campo `entities` saranno generati sul tipo `Query` di livello superiore. Si noti che `query` non deve essere inclusa all'inizio della query `graphql` quando si usa The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Esempi
 
@@ -21,7 +29,7 @@ Eseguire query di una singola entità `Token` definita nello schema:
 }
 ```
 
-> **Nota:** Quando si esegue una query per una singola entità, il campo `id` è obbligatorio e deve essere una stringa.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Eseguire query di tutte le entità `Token`:
 
@@ -36,7 +44,10 @@ Eseguire query di tutte le entità `Token`:
 
 ### Ordinamento
 
-Quando si esegue query di una collezione, il parametro `orderBy` può essere usato per ordinare in base a un attributo specifico. Inoltre, l'opzione `orderDirection` può essere usata per specificare la direzione dell'ordinamento, `asc` per l'ascendente oppure `desc` per il discendente.
+When querying a collection, you may:
+
+- 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.
 
 #### Esempio
 
@@ -53,7 +64,7 @@ Quando si esegue query di una collezione, il parametro `orderBy` può essere usa
 
 A partire da Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) le entità possono essere ordinate sulla base delle entità annidate.
 
-Nell'esempio seguente, ordiniamo i token in base al nome del loro proprietario:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ Nell'esempio seguente, ordiniamo i token in base al nome del loro proprietario:
 
 ### Impaginazione
 
-Quando si esegue una query di una collezione, il parametro `first` può essere usato per impaginare dall'inizio della raccolta. Va notato che l'ordinamento predefinito è per ID in ordine alfanumerico crescente, non per ora di creazione.
-
-Inoltre, il parametro `skip` può essere usato per saltare le entità ed impaginare. Ad esempio, `first:100` mostra le prime 100 entità e `first:100, skip:100` mostra le 100 entità successive.
+When querying a collection, it's best to:
 
-Le query dovrebbero evitare di usare valori `skip` molto grandi, perché in genere hanno un rendimento scarso. Per recuperare un gran numero di elementi, è molto meglio sfogliare le entità in base a un attributo, come mostrato nell'ultimo esempio.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Esempio di utilizzo di `first`
 
@@ -106,7 +118,7 @@ Eseguire query di 10 entità `Token`, sfalsate di 10 posizioni rispetto all'iniz
 
 #### Esempio di utilizzo di `first` e `id_ge`
 
-Se un client deve recuperare un gran numero di entità, è molto più performante basare le query su un attributo e filtrare in base a tale attributo. Ad esempio, un client potrebbe recuperare un gran numero di token utilizzando questa query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-La prima volta, si invierebbe la query con `lastID = ""` e per le richieste successive si imposterebbe `lastID` sull'attributo `id` dell'ultima entità della richiesta precedente. Questo approccio è nettamente migliore rispetto all'utilizzo di valori di `skip` crescenti.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtraggio
 
-È possibile utilizzare il parametro `where` nelle query per filtrare diverse proprietà. È possibile filtrare su più valori all'interno del parametro `where`.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Esempio di utilizzo di `where`
 
@@ -155,7 +168,7 @@ Query con esito `failed`:
 
 #### Esempio di filtraggio dei blocchi
 
-È anche possibile filtrare le entità in base al metodo `_change_block(number_gte: Int)` - questo filtra le entità che sono state aggiornate nel o dopo il blocco specificato.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Questo può essere utile se si vuole recuperare solo le entità che sono cambiate, ad esempio dall'ultima volta che è stato effettuato il polling. In alternativa, può essere utile per indagare o fare il debug di come le entità stanno cambiando nel subgraph (se combinato con un filtro di blocco, è possibile isolare solo le entità che sono cambiate in un blocco specifico).
 
@@ -193,7 +206,7 @@ A partire dalla versione Graph Node [`v0.30.0`](https://github.com/graphprotocol
 
 ##### Operatore `AND`
 
-Nell'esempio seguente, si filtrano le sfide con `outcome` `succeeded` e `number` maggiore o uguale a `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ Nell'esempio seguente, si filtrano le sfide con `outcome` `succeeded` e `number`
 ```
 
 > **Syntactic sugar:** Si può semplificare la query precedente eliminando l'operatore `and` passando una sottoespressione separata da virgole.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ Nell'esempio seguente, si filtrano le sfide con `outcome` `succeeded` e `number`
 
 ##### Operatore `OR`
 
-Nell'esempio seguente, si filtrano le sfide con `outcome` `succeeded` oppure `number` maggiore o uguale a `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 È possibile effetuare query dello stato delle entità non solo per l'ultimo blocco, che è quello predefinito, ma anche per un blocco nel passato. Il blocco in cui deve avvenire una query può essere specificato dal suo numero di blocco o dal suo hash, includendo un argomento `block` nei campi di livello superiore delle query.
 
-Il risultato di una query di questo tipo non cambia nel tempo, cioè la query di un determinato blocco passato restituirà lo stesso risultato indipendentemente dal momento in cui viene eseguita, con l'eccezione che se si fa query di un blocco molto vicino alla testa della catena, il risultato potrebbe cambiare se quel blocco risulta non essere nella catena principale e la catena viene riorganizzata. Una volta che un blocco può essere considerato definitivo, il risultato della query non cambierà.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Si noti che l'attuale implementazione è ancora soggetta ad alcune limitazioni che potrebbero violare queste garanzie. L'implementazione non è sempre in grado di dire che un determinato block hash non è affatto presente nella chain principale, o che il risultato di una query per il block hash per un blocco che non può ancora essere considerato definitivo potrebbe essere influenzato da una riorganizzazione di blocco in corso contemporaneamente alla query. Non influiscono sui risultati delle query in base all'block hash quando il blocco è definitivo e si sa che si trova nella chain principale. [Qui](https://github.com/graphprotocol/graph-node/issues/1405) è spiegato in dettaglio quali sono queste limitazioni.
+> 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
 
@@ -322,12 +335,12 @@ Le query di ricerca fulltext hanno un campo obbligatorio, `text`, per fornire i
 
 Operatori di ricerca fulltext:
 
-| Simbolo | Operatore | Descrizione |
-| --- | --- | --- |
-| `&` | `And` | Per combinare più termini di ricerca in un filtro per le entità che includono tutti i termini forniti |
-| &#x7c; | `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. |
-| `:*` | `Prefisso` | 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                                     |
+| &#x7c;      | `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.                                                                                                     |
+| `:*`        | `Prefisso`  | Utilizzare il termine di ricerca del prefisso per trovare le parole il cui prefisso corrisponde (sono richiesti 2 caratteri.)             |
 
 #### Esempi
 
@@ -376,11 +389,11 @@ Graph Node implementa la validazione [basata sulle specifiche](https://spec.grap
 
 ## Schema
 
-Lo schema dell'origine di dati-- cioè i tipi di entità, i valori e le relazioni disponibili per le query -- sono definiti attraverso [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-Gli schemi GraphQL in genere definiscono i tipi di radice per le `query`, le `sottoscrizioni` e le `mutazioni`. The Graph supporta solo le `query`. Il tipo di `Query` principale per il subgraph viene generato automaticamente dallo schema GraphQL incluso nel manifest del subgraph.
+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).
 
-> **Nota:** La nostra API non espone mutazioni perché gli sviluppatori devono emettere transazioni direttamente contro la blockchain sottostante dalle loro applicazioni.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entità
 

From 01270c38c721b700b09598dcd30a90cf96921a1a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:56 -0500
Subject: [PATCH 0216/1325] New translations graphql-api.mdx (Japanese)

---
 website/pages/ja/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/ja/querying/graphql-api.mdx b/website/pages/ja/querying/graphql-api.mdx
index 204a2fd52e89..839a9bff35f4 100644
--- a/website/pages/ja/querying/graphql-api.mdx
+++ b/website/pages/ja/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## クエリ
+## What is GraphQL?
 
-サブグラフのスキーマには、`Entities`と呼ばれるタイプが定義されています。各`Entity`タイプには、トップレベルの`Query`タイプに`entity`と`entities`フィールドが生成されます。なお、The Graph を使用する際には、`graphql`の`query` の先頭にクエリを含める必要はありません。
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### 例
 
@@ -21,7 +29,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 }
 ```
 
-> **注:** 単一のエンティティを照会する場合、`id` フィールドは必須であり、文字列でなければなりません。
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 すべての `Token` エンティティをクエリします。
 
@@ -36,7 +44,10 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### 並べ替え
 
-コレクションをクエリする場合、`orderBy` パラメータを使用して特定の属性で並べ替えることができます。さらに、`orderDirection` を使用してソート方向を指定できます。昇順の場合は `asc`、降順の場合は `desc` です。
+When querying a collection, you may:
+
+- 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.
 
 #### 例
 
@@ -53,7 +64,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 グラフ ノード [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) の時点で、エンティティを並べ替えることができますネストされたエンティティに基づいています。
 
-次の例では、所有者の名前でトークンを並べ替えます。
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### ページネーション
 
-コレクションをクエリする場合、`first` パラメータを使用して、コレクションの先頭から改ページすることができます。デフォルトのソート順は、作成時間順ではなく、英数字の昇順の ID 順であることに注意してください。
-
-さらに、 `skip` パラメーターを使用してエンティティをスキップし、ページ分割することができます。例えば`first:100` は最初の 100 個のエンティティを示し、`first:100, skip:100` は次の 100 個のエンティティを示します。
+When querying a collection, it's best to:
 
-クエリは一般にパフォーマンスが低いため、非常に大きな `skip` 値を使用しないでください。多数のアイテムを取得するには、最後の例で示したように、属性に基づいてエンティティをページングする方がはるかに優れています。
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### `first` を使用した例
 
@@ -106,7 +118,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 #### `first` と `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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-初めて、`lastID = ""` でクエリを送信し、後続のリクエストでは `lastID` を最後の `id` 属性に設定します。前のリクエストのエンティティ。このアプローチは、`skip` 値を増やして使用するよりもはるかに優れたパフォーマンスを発揮します。
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### フィルタリング
 
-クエリで `where` パラメータを使用して、さまざまなプロパティをフィルタリングできます。 `where` パラメータ内で複数の値をフィルタリングできます。
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### `where` を使用した例
 
@@ -155,7 +168,7 @@ query manyTokens($lastID: String) {
 
 #### ブロックフィルタリングの例
 
-`_change_block(number_gte: Int)` でエンティティをフィルタリングすることもできます - これは、指定されたブロック内またはそれ以降に更新されたエンティティをフィルタリングします。
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 これは、前回のポーリング以降など、変更されたエンティティのみをフェッチする場合に役立ちます。または、サブグラフでエンティティがどのように変化しているかを調査またはデバッグするのに役立ちます (ブロック フィルターと組み合わせると、特定のブロックで変更されたエンティティのみを分離できます)。
 
@@ -193,7 +206,7 @@ Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/
 
 ##### `AND` 演算子
 
-次の例では、`outcome` `succeeded` および `number` が `100` 以上のチャレンジをフィルタリングしています。
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/
 ```
 
 > **シンタックス シュガー:** コンマで区切られた部分式を渡すことで `and` 演算子を削除することで、上記のクエリを簡素化できます。
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/
 
 ##### `OR` 演算子
 
-次の例では、`outcome` `succeeded` または `number` が `100` 以上のチャレンジをフィルタリングしています。
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 デフォルトである最新のブロックだけでなく、過去の任意のブロックについてもエンティティの状態を照会できます。クエリが発生するブロックは、クエリのトップレベル フィールドに `block` 引数を含めることで、ブロック番号またはブロック ハッシュのいずれかで指定できます。
 
-そのようなクエリの結果は時間の経過とともに変化しません。つまり、特定の過去のブロックでクエリを実行しても、いつ実行されたとしても同じ結果が返されます。ただし、チェーンの先頭に非常に近いブロックでクエリを実行する場合を除いては、そのブロックがメインチェーン上にないことが判明し、チェーンが再構築される場合に結果が変わる可能性があります。ブロックが最終的とみなせるようになると、クエリの結果は変わらなくなります。
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-現在の実装には、これらの保証を破る可能性がある特定の制限がまだ存在することに注意してください。実装は常に特定のブロックハッシュがメインチェーン上に存在しないことを判断できるわけではなく、また、まだ最終的とみなせないブロックのブロックハッシュによるクエリの結果が、同時に実行されるブロックの再構築によって影響を受ける可能性があります。これらの制限は、ブロックが最終的であり、メインチェーン上に存在することが確認されている場合には、ブロックハッシュによるクエリの結果に影響を与えません。詳細は[この問題](https://github.com/graphprotocol/graph-node/issues/1405)で説明されています。
+> 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.
 
 #### 例
 
@@ -322,12 +335,12 @@ _change_block(number_gte: Int)
 
 全文検索演算子:
 
-| シンボル | オペレーター | 説明書き |
-| --- | --- | --- |
-| `&` | `と` | 複数の検索語を組み合わせて、指定したすべての検索語を含むエンティティをフィルタリングします。 |
-| &#x7c; | `Or` | 複数の検索語をオペレーターで区切って検索すると、指定した語のいずれかにマッチするすべてのエンティティが返されます。 |
-| `<->` | `Follow by` | 2 つの単語の間の距離を指定します。 |
-| `:*` | `プレフィックス` | プレフィックス検索語を使って、プレフィックスが一致する単語を検索します（2 文字必要） |
+| シンボル        | オペレーター      | 説明書き                                                      |
+| ----------- | ----------- | --------------------------------------------------------- |
+| `&`     | `と`         | 複数の検索語を組み合わせて、指定したすべての検索語を含むエンティティをフィルタリングします。            |
+| &#x7c;      | `Or`        | 複数の検索語をオペレーターで区切って検索すると、指定した語のいずれかにマッチするすべてのエンティティが返されます。 |
+| `<->` | `Follow by` | 2 つの単語の間の距離を指定します。                                        |
+| `:*`        | `プレフィックス`   | プレフィックス検索語を使って、プレフィックスが一致する単語を検索します（2 文字必要）               |
 
 #### 例
 
@@ -376,11 +389,11 @@ _change_block(number_gte: Int)
 
 ## スキーマ
 
-データ ソースのスキーマ、つまりクエリに使用できるエンティティ タイプ、値、および関係は、[GraphQL インターフェイス定義言語 (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System)。
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-GraphQL スキーマは通常、`クエリ`、`サブスクリプション`、および `ミューテーション` のルート タイプを定義します。グラフは `クエリ` のみをサポートします。サブグラフのルート `Query` タイプは、サブグラフ マニフェストに含まれる GraphQL スキーマから自動的に生成されます。
+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 はミューテーションを公開しません。
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### エンティティ
 

From 405be19a2d0e3ea1a601fcf48e59a393b1417141 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:57 -0500
Subject: [PATCH 0217/1325] New translations graphql-api.mdx (Korean)

---
 website/pages/ko/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/ko/querying/graphql-api.mdx b/website/pages/ko/querying/graphql-api.mdx
index 2bbc71b5bb9c..d8671e53a77c 100644
--- a/website/pages/ko/querying/graphql-api.mdx
+++ b/website/pages/ko/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### Example
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | Description |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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                                |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 5b9710bdda2e8169a30001be7a3e3bcaefa25a1e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:34:59 -0500
Subject: [PATCH 0218/1325] New translations graphql-api.mdx (Dutch)

---
 website/pages/nl/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/nl/querying/graphql-api.mdx b/website/pages/nl/querying/graphql-api.mdx
index 2bbc71b5bb9c..d8671e53a77c 100644
--- a/website/pages/nl/querying/graphql-api.mdx
+++ b/website/pages/nl/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### Example
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | Description |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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                                |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 1ee3064b6c57e353345238d90f9126ddf220114a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:00 -0500
Subject: [PATCH 0219/1325] New translations api.mdx (Italian)

---
 website/pages/it/developing/graph-ts/api.mdx | 127 ++++++++++---------
 1 file changed, 68 insertions(+), 59 deletions(-)

diff --git a/website/pages/it/developing/graph-ts/api.mdx b/website/pages/it/developing/graph-ts/api.mdx
index 012b07655db8..4edadedcff5e 100644
--- a/website/pages/it/developing/graph-ts/api.mdx
+++ b/website/pages/it/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: API AssemblyScript
 ---
 
-> Nota: se si hai creato un subgraph prima di `graph-cli`/`graph-ts` versione `0.22.0`, stai usando una versione precedente di AssemblyScript. Consigliamo di dare un'occhiata alla [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-Questa pagina documenta quali API integrate possono essere utilizzate per scrivere mappature di subgraph. Sono disponibili due tipi di API:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- codice generato da file di subgraph da `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-È anche possibile aggiungere altre librerie come dipendenze, purché siano compatibili con [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Poiché questo è il linguaggio in cui sono scritte le mappature, il wiki [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) è una buona fonte per le caratteristiche del linguaggio e delle librerie standard.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Riferimento API
 
@@ -27,16 +29,16 @@ La libreria `@graphprotocol/graph-ts` fornisce le seguenti API:
 
 La `apiVersion` nel manifest del subgraph specifica la versione dell'API di mappatura che viene eseguita da the Graph Node per un dato subgraph.
 
-| Versione | Note di rilascio |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Aggiunte le classi `TransactionReceipt` e `Log` ai tipi di Ethereum<br />Aggiunto il campo `receipt` all'oggetto Ethereum Event |
-| 0.0.6 | Aggiunto il campo `nonce` all'oggetto Ethereum Transaction<br />Aggiunto `baseFeePerGas` all'oggetto Ethereum Block |
-| 0.0.5 | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` |
-| 0.0.4 | Aggiunto il campo `functionSignature` all'oggetto Ethereum SmartContractCall |
-| 0.0.3 | Aggiunto il campo `from` all'oggetto Ethereum Call<br />`etherem.call.address` rinominato in `ethereum.call.to` |
-| 0.0.2 | Aggiunto il campo `input` all'oggetto Ethereum Transaction |
+| Versione | Note di rilascio                                                                                                                                                                                                                                                |
+| :------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|   0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                    |
+|   0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                                    |
+|   0.0.7  | Aggiunte le classi `TransactionReceipt` e `Log` ai tipi di Ethereum<br />Aggiunto il campo `receipt` all'oggetto Ethereum Event                                                                                                                                 |
+|   0.0.6  | Aggiunto il campo `nonce` all'oggetto Ethereum Transaction<br />Aggiunto `baseFeePerGas` all'oggetto Ethereum Block                                                                                                                                             |
+|   0.0.5  | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` |
+|   0.0.4  | Aggiunto il campo `functionSignature` all'oggetto Ethereum SmartContractCall                                                                                                                                                                                    |
+|   0.0.3  | Aggiunto il campo `from` all'oggetto Ethereum Call<br />`etherem.call.address` rinominato in `ethereum.call.to`                                                                                                                                                 |
+|   0.0.2  | Aggiunto il campo `input` all'oggetto Ethereum Transaction                                                                                                                                                                                                      |
 
 ### Tipi integrati
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 Quando un evento `Transfer` viene incontrato durante l'elaborazione della chain, viene passato al gestore dell'evento `handleTransfer` usando il tipo `Transfer` generato (qui alias `TransferEvent` per evitare un conflitto di nomi con il tipo di entità). Questo tipo consente di accedere a dati quali la transazione genitore dell'evento e i suoi parametri.
 
-Ogni entità deve avere un ID univoco per evitare collisioni con altre entità. È abbastanza comune che i parametri degli eventi includano un identificatore unico che può essere utilizzato. Nota: l'uso dell'hash della transazione come ID presuppone che nessun altro evento della stessa transazione crei entità con questo hash come ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Caricare le entità dallo store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-Poiché l'entità potrebbe non esistere ancora nel negozio, il metodo `load` restituisce un valore di tipo `Transfer | null`. Potrebbe quindi essere necessario verificare il caso `null` prima di utilizzare il valore.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Nota: ** Il caricamento delle entità è necessario solo se le modifiche apportate alla mappatura dipendono dai dati precedenti di un'entità. Vedere la sezione successiva per i due modi di aggiornare le entità esistenti.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Ricerca delle entità create all'interno di un blocco
 
 A partire da `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 e `@graphprotocol/graph-cli` v0.49.0 il metodo `loadInBlock` è disponibile per tutti i tipi di entità.
 
-L'API Store facilita il recupero delle entità create o aggiornate nel blocco corrente. Una situazione tipica è quella in cui un gestore crea una transazione da qualche evento sulla catena e un gestore successivo vuole accedere a questa transazione, se esiste. Nel caso in cui la transazione non esista, il subgraph dovrà andare nel database solo per scoprire che l'entità non esiste; se l'autore del subgraph sa già che l'entità deve essere stata creata nello stesso blocco, l'uso di loadInBlock evita questo viaggio nel database. Per alcuni subgraph, queste ricerche mancate possono contribuire in modo significativo al tempo di indicizzazione.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Qualsiasi altro contratto che faccia parte del subgraph può essere importato da
 
 #### Gestione delle chiamate annullate
 
-Se i metodi di sola lettura del contratto possono essere annullati, si deve gestire la situazione chiamando il metodo del contratto generato con il prefisso `try_`. Per esempio, il contratto Gravity espone il metodo `gravatarToOwner`. Questo codice sarebbe in grado di gestire un revert in quel metodo:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Si noti che un Graph node collegato a un client Geth o Infura potrebbe non rilevare tutti i reverts; se si fa affidamento su questo si consiglia di utilizzare un Graph node collegato a un client Parity.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Codifica/decodifica ABI
 
@@ -761,44 +770,44 @@ Quando il tipo di un valore è certo, può essere convertito in un [tipo incorpo
 
 ### Riferimento alle conversioni di tipo
 
-| Fonte(i)             | Destinazione         | Funzione di conversione     |
-| -------------------- | -------------------- | --------------------------- |
-| Address              | Bytes                | none                        |
-| Address              | String               | s.toHexString()             |
-| BigDecimal           | String               | s.toString()                |
-| BigInt               | BigDecimal           | s.toBigDecimal()            |
-| BigInt               | String (hexadecimal) | s.toHexString() o s.toHex() |
-| BigInt               | String (unicode)     | s.toString()                |
-| BigInt               | i32                  | s.toI32()                   |
-| Boolean              | Boolean              | none                        |
-| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)   |
-| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s) |
-| Bytes                | String (hexadecimal) | s.toHexString() o s.toHex() |
-| Bytes                | String (unicode)     | s.toString()                |
-| Bytes                | String (base58)      | s.toBase58()                |
-| Bytes                | i32                  | s.toI32()                   |
-| Bytes                | u32                  | s.toU32()                   |
-| Bytes                | JSON                 | json.fromBytes(s)           |
-| int8                 | i32                  | none                        |
-| int32                | i32                  | none                        |
-| int32                | BigInt               | BigInt.fromI32(s)           |
-| uint24               | i32                  | none                        |
-| int64 - int256       | BigInt               | none                        |
-| uint32 - uint256     | BigInt               | none                        |
-| JSON                 | boolean              | s.toBool()                  |
-| JSON                 | i64                  | s.toI64()                   |
-| JSON                 | u64                  | s.toU64()                   |
-| JSON                 | f64                  | s.toF64()                   |
-| JSON                 | BigInt               | s.toBigInt()                |
-| JSON                 | string               | s.toString()                |
-| JSON                 | Array                | s.toArray()                 |
-| JSON                 | Object               | s.toObject()                |
-| String               | Address              | Address.fromString(s)       |
-| Bytes                | Address              | Address.fromBytes(s)        |
-| String               | BigInt               | BigInt.fromString(s)        |
-| String               | BigDecimal           | BigDecimal.fromString(s)    |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)  |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)       |
+| Fonte(i)             | Destinazione          | Funzione di conversione          |
+| -------------------- | --------------------- | -------------------------------- |
+| Address              | Bytes                 | none                             |
+| Address              | String                | s.toHexString()                  |
+| BigDecimal           | String                | s.toString()                     |
+| BigInt               | BigDecimal            | s.toBigDecimal()                 |
+| BigInt               | String (hexadecimal)  | s.toHexString() o s.toHex()      |
+| BigInt               | String (unicode)      | s.toString()                     |
+| BigInt               | i32                   | s.toI32()                        |
+| Boolean              | Boolean               | none                             |
+| Bytes (signed)       | BigInt                | BigInt.fromSignedBytes(s)        |
+| Bytes (unsigned)     | BigInt                | BigInt.fromUnsignedBytes(s)      |
+| Bytes                | String (hexadecimal)  | s.toHexString() o s.toHex()      |
+| Bytes                | String (unicode)      | s.toString()                     |
+| Bytes                | String (base58)       | s.toBase58()                     |
+| Bytes                | i32                   | s.toI32()                        |
+| Bytes                | u32                   | s.toU32()                        |
+| Bytes                | JSON                  | json.fromBytes(s)                |
+| int8                 | i32                   | none                             |
+| int32                | i32                   | none                             |
+| int32                | BigInt                | BigInt.fromI32(s)                |
+| uint24               | i32                   | none                             |
+| int64 - int256       | BigInt                | none                             |
+| uint32 - uint256     | BigInt                | none                             |
+| JSON                 | boolean               | s.toBool()                       |
+| JSON                 | i64                   | s.toI64()                        |
+| JSON                 | u64                   | s.toU64()                        |
+| JSON                 | f64                   | s.toF64()                        |
+| JSON                 | BigInt                | s.toBigInt()                     |
+| JSON                 | string                | s.toString()                     |
+| JSON                 | Array                 | s.toArray()                      |
+| JSON                 | Object                | s.toObject()                     |
+| String               | Address               | Address.fromString(s)            |
+| Bytes                | Address               | Address.fromBytes(s)             |
+| String               | BigInt                | BigInt.fromString(s)             |
+| String               | BigDecimal            | BigDecimal.fromString(s)         |
+| String (hexadecimal) | Bytes                 | ByteArray.fromHexString(s)       |
+| String (UTF-8)       | Bytes                 | ByteArray.fromUTF8(s)            |
 
 ### Metadati della Data Source
 

From a4f0544600864d5a4dcc1f5f4a743ed040e3f4e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:02 -0500
Subject: [PATCH 0220/1325] New translations api.mdx (Japanese)

---
 website/pages/ja/developing/graph-ts/api.mdx | 129 ++++++++++---------
 1 file changed, 69 insertions(+), 60 deletions(-)

diff --git a/website/pages/ja/developing/graph-ts/api.mdx b/website/pages/ja/developing/graph-ts/api.mdx
index a3ac1026258b..cea9a55eb75c 100644
--- a/website/pages/ja/developing/graph-ts/api.mdx
+++ b/website/pages/ja/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> 注意: `graph-cli`/`graph-ts` のバージョン `0.22.0` より前にサブグラフを作成した場合、古いバージョンのAssemblyScriptを使用しているので、[`マイグレーションガイド`](/release-notes/assemblyscript-migration-guide) を参照することをお勧めします。
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-このページでは、サブグラフのマッピングを記述する際に、どのような組み込み API を使用できるかを説明します。 すぐに使える API は 2 種類あります:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- graph codegenによってサブグラフファイルから生成されたコードです。
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-また、<a href="https://github.com/AssemblyScript/assemblyscript">AssemblyScript</a>との互換性があれば、他のライブラリを依存関係に追加することも可能です。 マッピングはこの言語で書かれているので、言語や標準ライブラリの機能については、 <a href="https://github.com/AssemblyScript/assemblyscript/wiki">AssemblyScript wiki</a>が参考になります。
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API リファレンス
 
@@ -27,16 +29,16 @@ title: AssemblyScript API
 
 サブグラフマニフェストapiVersionは、特定のサブグラフのマッピングAPIバージョンを指定します。このバージョンは、Graph Nodeによって実行されます。
 
-| バージョン | リリースノート |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Ethereum タイプに `TransactionReceipt` と `Log` クラスを追加<br /> Ethereum Event オブジェクトに `receipt` フィールドを追加。 |
-| 0.0.6 | Ethereum Transactionオブジェクトに`nonce`フィールドを追加<br /> Ethereum Blockオブジェクトに`baseFeePerGas`を追加。 |
+| バージョン | リリースノート                                                                                                                                                                                                                                                                 |
+| :---: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                            |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                                            |
+| 0.0.7 | Ethereum タイプに `TransactionReceipt` と `Log` クラスを追加<br /> Ethereum Event オブジェクトに `receipt` フィールドを追加。                                                                                                                                                                      |
+| 0.0.6 | Ethereum Transactionオブジェクトに`nonce`フィールドを追加<br /> Ethereum Blockオブジェクトに`baseFeePerGas`を追加。                                                                                                                                                                               |
 | 0.0.5 | AssemblyScriptはバージョン0.19.10にアップグレードされました（このバージョンアップには変更点が含まれていますので <a href="/release-notes/assemblyscript-migration-guide"><code>Migration Guide</code></a>) をご覧ください）。 <br /><code>ethereum.transaction.gasUsed</code>の名前が<code>ethereum.transaction.gasLimit</code>に変更 |
-| 0.0.4 | Ethereum SmartContractCall オブジェクトにfunctionSignatureフィールドを追加 |
-| 0.0.3 | イーサリアムコールオブジェクトに`from`フィールドを追加<br />`etherem.call.address`を`ethereum.call.to`に変更。 |
-| 0.0.2 | Ethereum Transaction オブジェクトに inputフィールドを追加 |
+| 0.0.4 | Ethereum SmartContractCall オブジェクトにfunctionSignatureフィールドを追加                                                                                                                                                                                                             |
+| 0.0.3 | イーサリアムコールオブジェクトに`from`フィールドを追加<br />`etherem.call.address`を`ethereum.call.to`に変更。                                                                                                                                                                                       |
+| 0.0.2 | Ethereum Transaction オブジェクトに inputフィールドを追加                                                                                                                                                                                                                              |
 
 ### 組み込み型
 
@@ -98,7 +100,7 @@ _Math_
 - div(y: BigDecimal)： BigDecimal`-`x / y\` と書くことができます。
 - equals(y: BigDecimal): bool`-`x == y\` と書くことができます。
 - notEqual(y: BigDecimal): bool`-`x != y\` と書くことができます。
-- lt(y: BigDecimal): bool`-`x \< y\` と書くことができます。
+- lt(y: BigDecimal): bool`-`x < y\` と書くことができます。
 - `le(y: BigDecimal): bool` - `x <= y` と書くことができます。
 - `gt(y: BigDecimal): bool` と書くことができます。
 - `ge(y: BigDecimal): bool`と書くことができます。
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 チェーンの処理中に `Transfer` イベントが発生すると、生成された `Transfer` 型（エンティティ型との名前の衝突を避けるために、ここでは `TransferEvent` のエイリアス）を使用して `handleTransfer` イベントハンドラに渡されます。この型はイベントの親トランザクションやそのパラメータなどのデータにアクセスすることを可能にします。
 
-各エンティティは、他のエンティティとの衝突を避けるために、ユニークな ID を持たなければなりません。 イベントのパラメータには、使用可能な一意の識別子が含まれているのが一般的です。 注：トランザクションのハッシュを ID として使用することは、同じトランザクション内の他のイベントがこのハッシュを ID としてエンティティを作成しないことを前提としています。
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### ストアからのエンティティの読み込み
 
@@ -268,18 +272,21 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-エンティティはまだストアに存在していない可能性があるため、loadメソッドはTransfer | null型の値を返します。 そのため、値を使用する前に、nullのケースをチェックする必要があるかもしれません。
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> Note: エンティティのロードは、マッピングでの変更がエンティティの以前のデータに依存する場合にのみ必要です。 既存のエンティティを更新する 2 つの方法については、次のセクションを参照してください。
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### ブロック内で作成されたエンティティの検索
 
 graph-node v0.31.0、@graphprotocol/graph-ts v0.30.0、および @graphprotocol/graph-cli v0.49.0 以降、 loadInBlock メソッドはすべてのエンティティ タイプで使用できます。
 
-ストア API を使用すると、現在のブロックで作成または更新されたエンティティの取得が容易になります。この一般的な状況は、あるハンドラーがオンチェーン イベントからトランザクションを作成し、後のハンドラーがこのトランザクションが存在する場合にアクセスしようとすることです。トランザクションが存在しない場合、サブグラフはエンティティが存在しないことを確認するためだけにデータベースにアクセスする必要があります。エンティティが同じブロック内に作成されている必要があることをサブグラフの作成者がすでに知っている場合は、loadInBlock を使用すると、このデータベースのラウンドトリップが回避されます。一部のサブグラフでは、これらのルックアップの欠落がインデックス作成時間に大きく影響する可能性があります。
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
-let id = event.transaction.hash // または ID が構築される方法
+let id =event.transaction.hash // または ID が構築される方法
 let transfer = Transfer.loadInBlock(id)
 if (transfer == null) {
   transfer = 新しい転送(id)
@@ -503,7 +510,9 @@ Ethereum の ERC20Contractにsymbolというパブリックな読み取り専用
 
 #### リバートされた呼び出しの処理
 
-コントラクトの読み取り専用メソッドが復帰する可能性がある場合は、try\_を前置して生成されたコントラクトメソッドを呼び出すことで対処しなければなりません。 例えば、Gravity コントラクトではgravatarToOwnerメソッドを公開しています。 このコードでは、そのメソッドの復帰を処理することができます。
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-ただし、Geth や Infura のクライアントに接続された Graph ノードでは、すべてのリバートを検出できない場合があるので、これに依存する場合は Parity のクライアントに接続された Graph ノードを使用することをお勧めします。
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### 符号化/復号化 ABI
 
@@ -761,44 +770,44 @@ if (value.kind == JSONValueKind.BOOL) {
 
 ### タイプ 変換参照
 
-| Source(s)            | Destination          | Conversion function          |
-| -------------------- | -------------------- | ---------------------------- |
-| Address              | Bytes                | none                         |
-| Address              | String               | s.toHexString()              |
-| BigDecimal           | String               | s.toString()                 |
-| BigInt               | BigDecimal           | s.toBigDecimal()             |
-| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex() |
-| BigInt               | String (unicode)     | s.toString()                 |
-| BigInt               | i32                  | s.toI32()                    |
-| Boolean              | Boolean              | none                         |
-| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
-| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)  |
-| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex() |
-| Bytes                | String (unicode)     | s.toString()                 |
-| Bytes                | String (base58)      | s.toBase58()                 |
-| Bytes                | i32                  | s.toI32()                    |
-| Bytes                | u32                  | s.toU32()                    |
-| Bytes                | JSON                 | json.fromBytes(s)            |
-| int8                 | i32                  | none                         |
-| int32                | i32                  | none                         |
-| int32                | BigInt               | Bigint.fromI32(s)            |
-| uint24               | i32                  | none                         |
-| int64 - int256       | BigInt               | none                         |
-| uint32 - uint256     | BigInt               | none                         |
-| JSON                 | boolean              | s.toBool()                   |
-| JSON                 | i64                  | s.toI64()                    |
-| JSON                 | u64                  | s.toU64()                    |
-| JSON                 | f64                  | s.toF64()                    |
-| JSON                 | BigInt               | s.toBigInt()                 |
-| JSON                 | string               | s.toString()                 |
-| JSON                 | Array                | s.toArray()                  |
-| JSON                 | Object               | s.toObject()                 |
-| String               | Address              | Address.fromString(s)        |
-| Bytes                | Address              | Address.fromString(s)        |
-| String               | BigInt               | BigDecimal.fromString(s)     |
-| String               | BigDecimal           | BigDecimal.fromString(s)     |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
+| Source(s)            | Destination          | Conversion function              |
+| -------------------- | -------------------- | -------------------------------- |
+| Address              | Bytes                | none                             |
+| Address              | String               | s.toHexString()                  |
+| BigDecimal           | String               | s.toString()                     |
+| BigInt               | BigDecimal           | s.toBigDecimal()                 |
+| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex()     |
+| BigInt               | String (unicode)     | s.toString()                     |
+| BigInt               | i32                  | s.toI32()                        |
+| Boolean              | Boolean              | none                             |
+| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)        |
+| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)      |
+| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex()     |
+| Bytes                | String (unicode)     | s.toString()                     |
+| Bytes                | String (base58)      | s.toBase58()                     |
+| Bytes                | i32                  | s.toI32()                        |
+| Bytes                | u32                  | s.toU32()                        |
+| Bytes                | JSON                 | json.fromBytes(s)                |
+| int8                 | i32                  | none                             |
+| int32                | i32                  | none                             |
+| int32                | BigInt               | Bigint.fromI32(s)                |
+| uint24               | i32                  | none                             |
+| int64 - int256       | BigInt               | none                             |
+| uint32 - uint256     | BigInt               | none                             |
+| JSON                 | boolean              | s.toBool()                       |
+| JSON                 | i64                  | s.toI64()                        |
+| JSON                 | u64                  | s.toU64()                        |
+| JSON                 | f64                  | s.toF64()                        |
+| JSON                 | BigInt               | s.toBigInt()                     |
+| JSON                 | string               | s.toString()                     |
+| JSON                 | Array                | s.toArray()                      |
+| JSON                 | Object               | s.toObject()                     |
+| String               | Address              | Address.fromString(s)            |
+| Bytes                | Address              | Address.fromString(s)            |
+| String               | BigInt               | BigDecimal.fromString(s)         |
+| String               | BigDecimal           | BigDecimal.fromString(s)         |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)       |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)            |
 
 ### データソースのメタデータ
 

From 58dde2653ceca0ab20250068b58313a0cbc5df2c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:03 -0500
Subject: [PATCH 0221/1325] New translations api.mdx (Korean)

---
 website/pages/ko/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/ko/developing/graph-ts/api.mdx b/website/pages/ko/developing/graph-ts/api.mdx
index 46442dfa941e..8fc1f4b48b61 100644
--- a/website/pages/ko/developing/graph-ts/api.mdx
+++ b/website/pages/ko/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API Reference
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Built-in Types
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Handling Reverted Calls
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Encoding/Decoding ABI
 

From 252fa59d7ced68fabf297a5c66ff50a261b64e33 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:04 -0500
Subject: [PATCH 0222/1325] New translations api.mdx (Dutch)

---
 website/pages/nl/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/nl/developing/graph-ts/api.mdx b/website/pages/nl/developing/graph-ts/api.mdx
index 46442dfa941e..8fc1f4b48b61 100644
--- a/website/pages/nl/developing/graph-ts/api.mdx
+++ b/website/pages/nl/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API Reference
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Built-in Types
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Handling Reverted Calls
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Encoding/Decoding ABI
 

From 8fcfe62712f3716380e0eb977e51beb3b67cf848 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:06 -0500
Subject: [PATCH 0223/1325] New translations subgraphs.mdx (Italian)

---
 website/pages/it/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/it/subgraphs.mdx b/website/pages/it/subgraphs.mdx
index 27b452211477..ba810051a7c4 100644
--- a/website/pages/it/subgraphs.mdx
+++ b/website/pages/it/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Subgraph
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Ciclo di vita del subgraph
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 7b0bdc00c4524377b40bd3b99d62468a80c9a6e4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:06 -0500
Subject: [PATCH 0224/1325] New translations transfer-to-the-graph.mdx
 (Italian)

---
 website/pages/it/cookbook/transfer-to-the-graph.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/it/cookbook/transfer-to-the-graph.mdx b/website/pages/it/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..be40d06f45c0 100644
--- a/website/pages/it/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/it/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Esempio
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 

From f19f2867c313844671b33bce225a1702486948a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:08 -0500
Subject: [PATCH 0225/1325] New translations advanced.mdx (Italian)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/it/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/it/developing/creating-a-subgraph/advanced.mdx b/website/pages/it/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..2638c71c7190
--- /dev/null
+++ b/website/pages/it/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Panoramica
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Errori non fatali
+
+Gli errori di indicizzazione su subgraph già sincronizzati causano, per impostazione predefinita, il fallimento del subgraph e l'interruzione della sincronizzazione. In alternativa, i subgraph possono essere configurati per continuare la sincronizzazione in presenza di errori, ignorando le modifiche apportate dal gestore che ha provocato l'errore. In questo modo gli autori dei subgraph hanno il tempo di correggere i loro subgraph mentre le query continuano a essere servite rispetto al blocco più recente, anche se i risultati potrebbero essere incoerenti a causa del bug che ha causato l'errore. Si noti che alcuni errori sono sempre fatali. Per essere non fatale, l'errore deve essere noto come deterministico.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Per abilitare gli errori non fatali è necessario impostare il seguente flag di caratteristica nel manifesto del subgraph:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+I data source file sono una nuova funzionalità del subgraph per accedere ai dati fuori chain durante l'indicizzazione in modo robusto ed estendibile. I data source file supportano il recupero di file da IPFS e da Arweave.
+
+> Questo pone anche le basi per l'indicizzazione deterministica dei dati fuori chain e per la potenziale introduzione di dati arbitrari provenienti da HTTP.
+
+### Panoramica
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Guida all'aggiornamento
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Aggiungere un nuovo tipo di entità che verrà aggiornato quando verranno trovati dei file
+
+I data sources file non possono accedere o aggiornare le entità basate sulla chain, ma devono aggiornare le entità specifiche del file.
+
+Ciò può significare dividere i campi delle entità esistenti in entità separate, collegate tra loro.
+
+Entità combinata originale:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Entità nuova, divisa:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Se la relazione è 1:1 tra l'entità genitore e l'entità data source file risultante, il modello più semplice è quello di collegare l'entità genitore a un'entità file risultante utilizzando il CID IPFS come lookup. Contattateci su Discord se avete difficoltà a modellare le vostre nuove entità basate su file!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+È l'origine dati che verrà generata quando viene identificato un file di interesse.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Creare un nuovo gestore per elaborare i file
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Esempio di gestore:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Creare i data source file quando necessario
+
+È ora possibile creare i data sources file durante l'esecuzione di gestori a chain:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+Questo creerà una nuova data source file, che interrogherà l'endpoint IPFS o Arweave configurato del Graph Node, ritentando se non viene trovato. Quando il file viene trovato, viene eseguito il gestore del data source file.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulazioni, state usando i data source file!
+
+#### Distribuire i subgraph
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitazioni
+
+I gestori e le entità di data source file sono isolati dalle altre entità del subgraph, assicurando che siano deterministici quando vengono eseguiti e garantendo che non ci sia contaminazione di data source basate sulla chain. Per essere precisi:
+
+- Le entità create di Data Source file sono immutabili e non possono essere aggiornate
+- I gestori di Data Source file non possono accedere alle entità di altre data source file
+- Le entità associate al Data Source file non sono accessibili ai gestori alla chain
+
+> Sebbene questo vincolo non dovrebbe essere problematico per la maggior parte dei casi d'uso, potrebbe introdurre complessità per alcuni. Contattate via Discord se avete problemi a modellare i vostri dati basati su file in un subgraph!
+
+Inoltre, non è possibile creare data source da una data source file, sia essa una data source onchain o un'altra data source file. Questa restrizione potrebbe essere eliminata in futuro.
+
+#### Migliori pratiche
+
+Se si collegano i metadati NFT ai token corrispondenti, utilizzare l'hash IPFS dei metadati per fare riferimento a un'entità Metadata dall'entità Token. Salvare l'entità Metadata usando l'hash IPFS come ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Stiamo lavorando per migliorare la raccomandazione di cui sopra, in modo che le query restituiscano solo la versione "più recente"
+
+#### Problemi conosciuti
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Esempi
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Riferimenti
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting su subgraph esistenti
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Poiché l'innesto copia piuttosto che indicizzare i dati di base, è molto più veloce portare il subgraph al blocco desiderato rispetto all'indicizzazione da zero, anche se la copia iniziale dei dati può richiedere diverse ore per subgraph molto grandi. Mentre il subgraph innestato viene inizializzato, il Graph Node registra le informazioni sui tipi di entità già copiati.
+
+Il grafted subgraph può utilizzare uno schema GraphQL non identico a quello del subgraph di base, ma semplicemente compatibile con esso. Deve essere uno schema di subgraph valido di per sé, ma può discostarsi dallo schema del subgraph di base nei seguenti modi:
+
+- Aggiunge o rimuove i tipi di entità
+- Rimuove gli attributi dai tipi di entità
+- Aggiunge attributi annullabili ai tipi di entità
+- Trasforma gli attributi non nulli in attributi nulli
+- Aggiunge valori agli enum
+- Aggiunge o rimuove le interfacce
+- Cambia per quali tipi di entità viene implementata un'interfaccia
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 0582660c491b62dc388705cdba3779710eaff259 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:09 -0500
Subject: [PATCH 0226/1325] New translations assemblyscript-mappings.mdx
 (Italian)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/it/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/it/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/it/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..23271ae9c85c
--- /dev/null
+++ b/website/pages/it/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Panoramica
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Scrivere le mappature
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### ID consigliati per la creazione di nuove entità
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Generazione del codice
+
+Per rendere semplice e sicuro il lavoro con gli smart contract, gli eventi e le entità, la Graph CLI può generare tipi AssemblyScript dallo schema GraphQL del subgraph e dagli ABI dei contratti inclusi nelle data source.
+
+Questo viene fatto con
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From ebe0fda8553bed3fbaa8b7e83fec72d8eb4b43b3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:10 -0500
Subject: [PATCH 0227/1325] New translations install-the-cli.mdx (Italian)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..fd63493e4eea
--- /dev/null
+++ b/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Installare the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Panoramica
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Installare the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Create a Subgraph
+
+### Da un contratto esistente
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### Da un subgraph di esempio
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+I file ABI devono corrispondere al vostro contratto. Esistono diversi modi per ottenere i file ABI:
+
+- Se state costruendo il vostro progetto, probabilmente avrete accesso alle ABI più recenti.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 03cfdb3243ae027d7a62372a13f36e1c7275fe17 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:11 -0500
Subject: [PATCH 0228/1325] New translations ql-schema.mdx (Italian)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/it/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3445fc2a0ef9
--- /dev/null
+++ b/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Panoramica
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Buon esempio
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Cattivo esempio
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Campi opzionali e obbligatori
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Tipi scalari integrati
+
+#### Scalari supportati da GraphQL
+
+The following scalars are supported in the GraphQL API:
+
+| Tipo         | Descrizione                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, rappresentato come una stringa esadecimale. Comunemente utilizzato per gli hash e gli indirizzi di Ethereum.                                                                                         |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enum
+
+È possibile creare enum anche all'interno di uno schema. Gli enum hanno la seguente sintassi:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Relazioni tra entità
+
+Un'entità può avere una relazione con una o più altre entità dello schema. Queste relazioni possono essere attraversate nelle query. Le relazioni in The Graph sono unidirezionali. È possibile simulare relazioni bidirezionali definendo una relazione unidirezionale su entrambe le "estremità" della relazione.
+
+Le relazioni sono definite sulle entità come qualsiasi altro campo, tranne per il fatto che il tipo specificato è quello di un'altra entità.
+
+#### Rapporti uno-a-uno
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Relazioni uno-a-molti
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Ricerche inverse
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+Per le relazioni uno-a-molti, la relazione deve sempre essere memorizzata sul lato "uno" e il lato "molti" deve sempre essere derivato. Memorizzare la relazione in questo modo, piuttosto che memorizzare un array di entità sul lato "molti", migliorerà notevolmente le prestazioni sia per l'indicizzazione che per l'interrogazione del subgraph. In generale, la memorizzazione di array di entità dovrebbe essere evitata per quanto possibile.
+
+#### Esempio
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Relazioni molti-a-molti
+
+Per le relazioni molti-a-molti, come ad esempio gli utenti che possono appartenere a un numero qualsiasi di organizzazioni, il modo più semplice, ma generalmente non il più performante, di modellare la relazione è come un array in ciascuna delle due entità coinvolte. Se la relazione è simmetrica, è necessario memorizzare solo un lato della relazione e l'altro lato può essere derivato.
+
+#### Esempio
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Questo approccio richiede che le query scendano di un ulteriore livello per recuperare, ad esempio, le organizzazioni degli utenti:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Questo modo più elaborato di memorizzare le relazioni molti-a-molti si traduce in una minore quantità di dati memorizzati per il subgraph e quindi in un subgraph che spesso è molto più veloce da indicizzare e da effettuare query.
+
+### Aggiungere commenti allo schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Definizione dei campi di ricerca fulltext
+
+Le query di ricerca fulltext filtrano e classificano le entità in base a un input di ricerca testuale. Le query full-text sono in grado di restituire corrispondenze per parole simili, elaborando il testo della query in gambi prima di confrontarli con i dati di testo indicizzati.
+
+La definizione di una query fulltext include il nome della query, il dizionario linguistico utilizzato per elaborare i campi di testo, l'algoritmo di classificazione utilizzato per ordinare i risultati e i campi inclusi nella ricerca. Ogni query fulltext può comprendere più campi, ma tutti i campi inclusi devono appartenere a un unico tipo di entità.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Lingue supportate
+
+La scelta di una lingua diversa avrà un effetto definitivo, anche se talvolta sottile, sull'API di ricerca fulltext. I campi coperti da una query fulltext vengono esaminati nel contesto della lingua scelta, quindi i lessemi prodotti dall'analisi e dalle query di ricerca variano da lingua a lingua. Ad esempio, quando si utilizza il dizionario turco supportato, "token" viene ridotto a "toke", mentre il dizionario inglese lo riduce a "token".
+
+Dizionari linguistici supportati:
+
+| Code     | Dizionario |
+| -------- | ---------- |
+| semplice | General    |
+| da       | Danish     |
+| nl       | Dutch      |
+| en       | English    |
+| fi       | Finnish    |
+| fr       | French     |
+| de       | German     |
+| hu       | Hungarian  |
+| it       | Italian    |
+| no       | Norwegian  |
+| pt       | Portoghese |
+| ro       | Romanian   |
+| ru       | Russian    |
+| es       | Spanish    |
+| sv       | Swedish    |
+| tr       | Turkish    |
+
+### Algoritmi di classificazione
+
+Algoritmi supportati per ordinare i risultati:
+
+| Algorithm     | Description                                                                                   |
+| ------------- | --------------------------------------------------------------------------------------------- |
+| rank          | Utilizza la qualità della corrispondenza (0-1) della query fulltext per ordinare i risultati. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                               |

From 8f82da27aabc049407e9d53719962b624d1a8948 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:13 -0500
Subject: [PATCH 0229/1325] New translations subgraph-manifest.mdx (Italian)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/it/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/it/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/it/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..43e510cf1a7a
--- /dev/null
+++ b/website/pages/it/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Panoramica
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Le voci importanti da aggiornare per il manifesto sono:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Gestori di chiamate
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+I gestori di chiamate si attivano solo in uno dei due casi: quando la funzione specificata viene chiamata da un conto diverso dal contratto stesso o quando è contrassegnata come esterna in Solidity e chiamata come parte di un'altra funzione nello stesso contratto.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Definire un gestore di chiamate
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Funzione di mappatura
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Gestori di blocchi
+
+Oltre a sottoscrivere eventi di contratto o chiamate di funzione, un subgraph può voler aggiornare i propri dati quando nuovi blocchi vengono aggiunti alla chain. A tale scopo, un subgraph può eseguire una funzione dopo ogni blocco o dopo i blocchi che corrispondono a un filtro predefinito.
+
+### Filtri supportati
+
+#### Filtro di chiamata
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+L'assenza di un filtro per un gestore di blocchi garantisce che il gestore venga chiamato a ogni blocco. Una data source può contenere un solo gestore di blocchi per ogni tipo di filtro.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Filtro di polling
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Filtro once
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Il gestore definito con il filtro once sarà chiamato una sola volta prima dell'esecuzione di tutti gli altri gestori. Questa configurazione consente al subgraph di utilizzare il gestore come gestore di inizializzazione, eseguendo compiti specifici all'inizio dell'indicizzazione.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Funzione di mappatura
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Eventi anonimi
+
+Se è necessario elaborare eventi anonimi in Solidity, è possibile farlo fornendo l'argomento 0 dell'evento, come nell'esempio:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Ricevute di transazione nei gestori di eventi
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+I trigger per una data source all'interno di un blocco sono ordinati secondo il seguente processo:
+
+1. I trigger di eventi e chiamate sono ordinati prima per indice di transazione all'interno del blocco.
+2. I trigger di eventi e chiamate all'interno della stessa transazione sono ordinati secondo una convenzione: prima i trigger di eventi e poi quelli di chiamate, rispettando l'ordine in cui sono definiti nel manifesto.
+3. I trigger di blocco vengono eseguiti dopo i trigger di evento e di chiamata, nell'ordine in cui sono definiti nel manifesto.
+
+Queste regole di ordinazione sono soggette a modifiche.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Modelli di Data Source
+
+Un modello comune negli smart contract compatibili con EVM è l'uso di contratti di registro o di fabbrica, in cui un contratto crea, gestisce o fa riferimento a un numero arbitrario di altri contratti che hanno ciascuno il proprio stato e i propri eventi.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source per il contratto principale
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Modelli di data source per contratti creati dinamicamente
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Istanziare un modello di data source
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Se i blocchi precedenti contengono dati rilevanti per la nuova data source, è meglio indicizzare tali dati leggendo lo stato attuale del contratto e creando entità che rappresentino tale stato al momento della creazione della nuova data source.
+
+### Contesto del Data Source
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Blocchi di partenza
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Cercare il contratto inserendo l'indirizzo nella barra di ricerca.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Caricare la pagina dei dettagli della transazione, dove si trova il blocco iniziale per quel contratto.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 1155909488e97acbb45fdbfe6e640e6adcec5f30 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:14 -0500
Subject: [PATCH 0230/1325] New translations subgraphs.mdx (Japanese)

---
 website/pages/ja/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/ja/subgraphs.mdx b/website/pages/ja/subgraphs.mdx
index 27b452211477..4801361f96eb 100644
--- a/website/pages/ja/subgraphs.mdx
+++ b/website/pages/ja/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: サブグラフ
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## サブグラフのライフサイクル
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From ac898505859e4f10a1d550fe10233dcf6f9a1963 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:15 -0500
Subject: [PATCH 0231/1325] New translations transfer-to-the-graph.mdx
 (Japanese)

---
 .../pages/ja/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ja/cookbook/transfer-to-the-graph.mdx b/website/pages/ja/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..3b064acb6cd5 100644
--- a/website/pages/ja/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/ja/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### 例
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### その他のリソース
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 03fa8cfbbc74943b21a2068919c115e759f27e79 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:16 -0500
Subject: [PATCH 0232/1325] New translations advanced.mdx (Japanese)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/ja/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/ja/developing/creating-a-subgraph/advanced.mdx b/website/pages/ja/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..6b8fd1fb7db4
--- /dev/null
+++ b/website/pages/ja/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## 概要
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## 致命的でないエラー
+
+すでに同期しているサブグラフのインデックスエラーは、デフォルトではサブグラフを失敗させ、同期を停止させます。サブグラフは、エラーが発生したハンドラーによる変更を無視することで、エラーが発生しても同期を継続するように設定することができます。これにより、サブグラフの作成者はサブグラフを修正する時間を得ることができ、一方でクエリは最新のブロックに対して提供され続けますが、エラーの原因となったバグのために結果が一貫していない可能性があります。なお、エラーの中には常に致命的なものもあり、致命的でないものにするためには、そのエラーが決定論的であることがわかっていなければなりません。
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+非致命的エラーを有効にするには、サブグラフのマニフェストに以下の機能フラグを設定する必要があります:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - fullTextSearch
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+ファイルデータソースは、堅牢で拡張可能な方法でインデックス作成中にオフチェーンデータにアクセスするための新しいサブグラフ機能です。ファイルデータソースは、IPFS および Arweave からのファイルのフェッチをサポートしています。
+
+> また、オフチェーンデータの決定論的なインデックス作成、および任意のHTTPソースデータの導入の可能性についても基礎ができました。
+
+### 概要
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### アップグレードガイド
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### ファイルが見つかったときに更新される新しいエンティティタイプを追加します。
+
+ファファイルが見つかったときに更新される新しいエンティティタイプを追加します。イルデータソースは、チェーンベースのエンティティにアクセスしたり更新することはできませんが、ファイル固有のエンティティを更新する必要があります。
+
+これは、既存のエンティティからフィールドを分離し、別のエンティティにリンクさせることを意味します。
+
+Original combined entity：
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity：
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+親エンティティと結果のファイルデータソースエンティティの間の関係が1：1である場合、最も単純なパターンは、IPFS CIDをルックアップとして使用して、親エンティティを結果のファイルエンティティにリンクすることです。新しいファイルベースのエンティティのモデリングに問題がある場合は、Discordに連絡してください。
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+目的のファイルが特定されたときに生成されるデータソースです。
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### ファイルを処理するハンドラーを新規に作成
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+ハンドラーの例：
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### 必要なときにファイルデータソースを起動する
+
+チェーンベースハンドラーの実行中に、ファイルデータソースを作成できるようになりました：
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+例：
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+これにより、新しいファイル データ ソースが作成され、グラフ ノードの構成済み IPFS または Arweave エンドポイントがポーリングされ、見つからない場合は再試行されます。ファイルが見つかると、ファイルデータソースハンドラが実行されます。
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+おめでとうございます！ファイルデータソースが使用できます。
+
+#### サブグラフのデプロイ
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### 制限事項
+
+ファイルデータソースハンドラおよびエンティティは、他のサブグラフエンティティから分離され、実行時に決定論的であることを保証し、チェーンベースのデータソースを汚染しないことを保証します。具体的には、以下の通りです。
+
+- ファイルデータソースで作成されたエンティティは不変であり、更新することはできません。
+- ファイルデータソースハンドラは、他のファイルデータソースのエンティティにアクセスすることはできません。
+- ファイルデータソースに関連するエンティティは、チェーンベースハンドラーからアクセスできません。
+
+> この制約は、ほとんどのユースケースで問題になることはありませんが、一部のユースケースでは複雑さをもたらすかもしれません。ファイルベースのデータをサブグラフでモデル化する際に問題がある場合は、Discordを通じてご連絡ください。
+
+また、オンチェーンデータソースや他のファイルデータソースからデータソースを作成することはできません。この制限は、将来的に解除される可能性があります。
+
+#### ベストプラクティス
+
+NFT メタデータを対応するトークンにリンクする場合、メタデータの IPFS ハッシュを使用して、トークン エンティティから Metadata エンティティを参照します。IPFSハッシュをIDとして使用してMetadataエンティティを保存します。
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> クエリが「最新版」のみを返すように、上記の推奨事項を改善するよう取り組んでいます。
+
+#### 既知の問題点
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### 例
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### 参考文献
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### 既存のサブグラフへのグラフト
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+グラフトはベースデータのインデックスではなくコピーを行うため、スクラッチからインデックスを作成するよりもサブグラフを目的のブロックに早く到達させることができますが、非常に大きなサブグラフの場合は最初のデータコピーに数時間かかることもあります。グラフトされたサブグラフが初期化されている間、グラフノードは既にコピーされたエンティティタイプに関する情報を記録します。
+
+グラフト化されたサブグラフは、ベースとなるサブグラフのスキーマと同一ではなく、単に互換性のある GraphQL スキーマを使用することができます。また、それ自体は有効なサブグラフのスキーマでなければなりませんが、以下の方法でベースサブグラフのスキーマから逸脱することができます。
+
+- エンティティタイプを追加または削除する
+- エンティティタイプから属性を削除する
+- エンティティタイプに nullable 属性を追加する
+- null 化できない属性を null 化できる属性に変更する
+- enums に値を追加する
+- インターフェースの追加または削除
+- インターフェースがどのエンティティタイプに実装されるかを変更する
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From c8117db941694445cd064f2fe9c9368189748d29 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:17 -0500
Subject: [PATCH 0233/1325] New translations assemblyscript-mappings.mdx
 (Japanese)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/ja/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/ja/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ja/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..50b664c86f3b
--- /dev/null
+++ b/website/pages/ja/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## 概要
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## マッピングの記述
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### 新規エンティティ作成時の推奨 ID
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## コード生成
+
+スマートコントラクト、イベント、エンティティを簡単かつタイプセーフに扱うために、Graph CLIはサブグラフのGraphQLスキーマとデータソースに含まれるコントラクトABIからAssemblyScriptタイプを生成することができます。
+
+これを行うためには
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 0931cc1de51578fb7e39404dcbff08f8c67f64fa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:19 -0500
Subject: [PATCH 0234/1325] New translations install-the-cli.mdx (Japanese)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..9934e852df3a
--- /dev/null
+++ b/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Graph CLI のインストール
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## 概要
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## はじめに
+
+### Graph CLI のインストール
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+ローカル マシンで、次のいずれかのコマンドを実行します。
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## サブグラフの作成
+
+### 既存のコントラクトから
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### サブグラフの例から
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+ABI ファイルは、契約内容と一致している必要があります。ABI ファイルを入手するにはいくつかの方法があります:
+
+- 自分のプロジェクトを構築している場合は、最新の ABI にアクセスできる可能性があります。
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| バージョン | リリースノート                                                                                                                                                                  |
+| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
+| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |

From 6f42bdc7b0d9884dd9f367460e8b258a49a75be7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:20 -0500
Subject: [PATCH 0235/1325] New translations ql-schema.mdx (Japanese)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..17d9779c58f6
--- /dev/null
+++ b/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## 概要
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### 良い例
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### 悪い例
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### 任意フィールドと必須フィールド
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null 以外のフィールド 'name' の null 値が解決されました
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### 組み込みの Scalar タイプ
+
+#### GraphQL がサポートする Scalar
+
+The following scalars are supported in the GraphQL API:
+
+| タイプ          | 説明書き                                                                                                                                                                                                             |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte 配列で、16 進数の文字列で表されます。Ethereum のハッシュやアドレスによく使われます。                                                                                                                                                            |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+スキーマ内に enums を作成することもできます。enums は次のような構文になっています:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### エンティティのリレーションシップ
+
+エンティティは、スキーマ内の 1 つ以上の他のエンティティとリレーションシップを持つことができます。これらの関係は、クエリの中で走査されることがあります。The Graph のリレーションシップは単方向です。リレーションシップのどちらかの "端 "に単方向のリレーションシップを定義することで、双方向のリレーションシップをシミュレートすることができます。
+
+リレーションシップは、指定されたタイプが他のエンティティのものであることを除けば、他のフィールドと同様にエンティティに定義されます。
+
+#### 1 対 1 のリレーションシップ
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### 1 対多のリレーションシップ
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### 逆引き(Reverse lookups)
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+1 対多の関係では、関係は常に「1」側に格納され、「多」側は常に派生されるべきです。「多」側にエンティティの配列を格納するのではなく、このように関係を格納することで、サブグラフのインデックス作成と問い合わせの両方で劇的にパフォーマンスが向上します。一般的に、エンティティの配列を保存することは、現実的に可能な限り避けるべきです。
+
+#### 例
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### 多対多のリレーションシップ
+
+ユーザーがそれぞれ任意の数の組織に所属しているような多対多の関係の場合、関係をモデル化する最も簡単な方法は、関係する 2 つのエンティティのそれぞれに配列として格納することですが、一般的には最もパフォーマンスの高い方法ではありません。対称的な関係であれば、関係の片側のみを保存する必要があり、もう片側は派生させることができます。
+
+#### 例
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+このアプローチでは、例えばユーザーの組織を取得するために、クエリをさらに 1 つのレベルに下げる必要があります:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+このように多対多の関係をより精巧に保存する方法では、サブグラフに保存されるデータが少なくなるため、サブグラフのインデックス作成や問い合わせが劇的に速くなります。
+
+### スキーマへのコメントの追加
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## フルテキスト検索フィールド（Full Text Search）の定義
+
+フルテキスト検索クエリは、テキスト検索入力に基づいてエンティティをフィルタリングし、ランク付けします。フルテキストクエリは、インデックス化されたテキストデータと比較する前に、クエリテキストの入力をステム処理することで、類似した単語のマッチを返すことができます。
+
+フルテキストクエリの定義には、クエリ名、テキストフィールドの処理に使用される言語辞書、結果の順序付けに使用されるランキングアルゴリズム、および検索に含まれるフィールドが含まれます。各フルテキスト・クエリは複数のフィールドにまたがることができますが、含まれるフィールドはすべて単一のエンティティ・タイプのものでなければなりません。
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## 対応言語
+
+異なる言語を選択すると、フルテキスト検索 API に決定的な影響を与えますが、場合によっては微妙な影響もあります。フルテキストクエリフィールドでカバーされるフィールドは、選択された言語のコンテキストで検査されるため、分析や検索クエリで生成される語彙は言語ごとに異なります。たとえば、サポートされているトルコ語辞書を使用した場合、"token "は "toke "にステム処理されますが、もちろん英語辞書では "token "にステム処理されます。
+
+サポートされている言語の辞書:
+
+| Code   | 辞書         |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | ポルトガル語     |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### ランキングアルゴリズム
+
+サポートされている結果の順序付けのアルゴリズム:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | フルテキストクエリのマッチ品質 (0-1) を使用して結果を並べ替えます。                                   |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From fb230ecfa552acc20cccbed0c6320d7d3cc80eb7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:21 -0500
Subject: [PATCH 0236/1325] New translations subgraph-manifest.mdx (Japanese)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/ja/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/ja/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ja/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..76206b5791cb
--- /dev/null
+++ b/website/pages/ja/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## 概要
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+マニフェストを更新する重要な項目は以下の通りです:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## コールハンドラー
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+コールハンドラーは、次の 2 つのケースのいずれかでのみトリガされます：指定された関数がコントラクト自身以外のアカウントから呼び出された場合、または Solidity で外部としてマークされ、同じコントラクト内の別の関数の一部として呼び出された場合。
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### コールハンドラーの定義
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### マッピング関数
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## ブロック・ハンドラー
+
+コントラクトイベントやファンクションコールの購読に加えて、サブグラフは、新しいブロックがチェーンに追加されると、そのデータを更新したい場合があります。これを実現するために、サブグラフは各ブロックの後、あるいは事前に定義されたフィルタにマッチしたブロックの後に、関数を実行することができます。
+
+### 対応フィルター
+
+#### 通話フィルター
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+ブロックハンドラーにフィルターがない場合、ハンドラーはブロックごとに呼び出されます。1 つのデータソースには、各フィルタータイプに対して 1 つのブロックハンドラーしか含めることができません。
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### ポーリングフィルター
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### ワンスフィルター
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Once フィルターを使用して定義されたハンドラーは、他のすべてのハンドラーが実行される前に 1 回だけ呼び出されます。 この構成により、サブグラフはハンドラーを初期化ハンドラーとして使用し、インデックス作成の開始時に特定のタスクを実行できるようになります。
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### マッピング関数
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## 匿名イベント
+
+Solidity で匿名イベントを処理する必要がある場合は、例のようにイベントのトピック 0 を提供することで実現できます:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## イベントハンドラにおけるトランザクションレシーブ
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+ブロック内のデータソースのトリガーは、以下のプロセスを使用して順序付けられます:
+
+1. イベントとコールのトリガーは、ブロック内のトランザクションインデックスで最初に並べられます。
+2. 同じトランザクション内のイベントトリガーとコールトリガーは、マニフェストで定義されている順序にしたがって、イベントトリガーが先、コールトリガーが後という規則で並べられます。
+3. ブロックトリガーは、イベントトリガーとコールトリガーの後に、マニフェストで定義されている順番で実行されます。
+
+これらの順序規則は変更されることがあります。
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## データソーステンプレート
+
+EVM 互換のスマート コントラクトの一般的なパターンは、レジストリ コントラクトまたはファクトリ コントラクトの使用です。1 つのコントラクトが、それぞれ独自の状態とイベントを持つ任意の数の他のコントラクトを作成、管理、または参照します。
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### メインコントラクトのデータソース
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### 動的に作成されるコントラクトのデータソーステンプレート
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### データソーステンプレートのインスタンス化
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> 以前のブロックに新しいデータソースに関連するデータが含まれている場合は、コントラクトの現在の状態を読み取り、新しいデータソースが作成された時点でその状態を表すエンティティを作成することで、そのデータにインデックスを付けることが最善です。
+
+### データソースコンテクスト
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## スタートブロック(start Blocks)
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. 検索バーにアドレスを入力してコントラクトを検索します。
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. トランザクションの詳細ページを読み込んで、そのコントラクトの開始ブロックを見つけます。
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 9c0207f7dcd9fef3a079127a78d0a8640a98f374 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:22 -0500
Subject: [PATCH 0237/1325] New translations subgraphs.mdx (Korean)

---
 website/pages/ko/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/ko/subgraphs.mdx b/website/pages/ko/subgraphs.mdx
index 27b452211477..42c1e806f822 100644
--- a/website/pages/ko/subgraphs.mdx
+++ b/website/pages/ko/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 3fda426bd919c30ea2c2a7232c48149aa3546658 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:23 -0500
Subject: [PATCH 0238/1325] New translations transfer-to-the-graph.mdx (Korean)

---
 website/pages/ko/cookbook/transfer-to-the-graph.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/ko/cookbook/transfer-to-the-graph.mdx b/website/pages/ko/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..6a5d2c2793f3 100644
--- a/website/pages/ko/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/ko/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 

From d15e06bd75472a6ff362e95e678005b9da3daf43 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:24 -0500
Subject: [PATCH 0239/1325] New translations advanced.mdx (Korean)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/ko/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/ko/developing/creating-a-subgraph/advanced.mdx b/website/pages/ko/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..3a08ddab7066
--- /dev/null
+++ b/website/pages/ko/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 86530fcf94b956e07c62af0b38882db3944c1cf1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:25 -0500
Subject: [PATCH 0240/1325] New translations assemblyscript-mappings.mdx
 (Korean)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/ko/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/ko/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ko/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/ko/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 1e40ea280a7fcc99dbbfedf05a3082efa730b303 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:26 -0500
Subject: [PATCH 0241/1325] New translations install-the-cli.mdx (Korean)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..5897ae02b134
--- /dev/null
+++ b/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Create a Subgraph
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 5d8c44430c909cacf9ae2d194b0f18c9e5f34cd4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:28 -0500
Subject: [PATCH 0242/1325] New translations ql-schema.mdx (Korean)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From 52a0a9f0bdda4765be8798abfe976f3bc1269913 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:29 -0500
Subject: [PATCH 0243/1325] New translations subgraph-manifest.mdx (Korean)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/ko/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/ko/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ko/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..f282f3946e75
--- /dev/null
+++ b/website/pages/ko/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 8deee659b5208aa5cd6200459c3588a48d326602 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:30 -0500
Subject: [PATCH 0244/1325] New translations subgraphs.mdx (Dutch)

---
 website/pages/nl/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/nl/subgraphs.mdx b/website/pages/nl/subgraphs.mdx
index 27b452211477..42c1e806f822 100644
--- a/website/pages/nl/subgraphs.mdx
+++ b/website/pages/nl/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 1e87c9c67f00c187b07fe5b7da03944a2f704ac9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:31 -0500
Subject: [PATCH 0245/1325] New translations transfer-to-the-graph.mdx (Dutch)

---
 website/pages/nl/cookbook/transfer-to-the-graph.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/nl/cookbook/transfer-to-the-graph.mdx b/website/pages/nl/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..6a5d2c2793f3 100644
--- a/website/pages/nl/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/nl/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 

From 920e9ed030f17a76b782a762eea9fb6f423b2fcd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:33 -0500
Subject: [PATCH 0246/1325] New translations advanced.mdx (Dutch)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/nl/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/nl/developing/creating-a-subgraph/advanced.mdx b/website/pages/nl/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..3a08ddab7066
--- /dev/null
+++ b/website/pages/nl/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From ba3ec1be18d0a8598973adfd5f2dc66adac7caf7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:34 -0500
Subject: [PATCH 0247/1325] New translations assemblyscript-mappings.mdx
 (Dutch)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/nl/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/nl/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/nl/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/nl/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 68a436a8e8c2eda710f7db3a0fd70893fb762c5b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:35 -0500
Subject: [PATCH 0248/1325] New translations install-the-cli.mdx (Dutch)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..92a75ed476d9
--- /dev/null
+++ b/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Creëer een Subgraph
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From f06ad14806da9eb4982223267d75a27d57ca5530 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:36 -0500
Subject: [PATCH 0249/1325] New translations ql-schema.mdx (Dutch)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From 507584cc0a946c4737489d35ced473c9153edc93 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:37 -0500
Subject: [PATCH 0250/1325] New translations subgraph-manifest.mdx (Dutch)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/nl/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/nl/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/nl/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..f282f3946e75
--- /dev/null
+++ b/website/pages/nl/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 42d05f5f9ae11f9764efde35f6c0c777d29eb875 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:38 -0500
Subject: [PATCH 0251/1325] New translations index.json (Polish)

---
 website/pages/pl/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/pl/index.json b/website/pages/pl/index.json
index 1bb900b640bc..da068b79078f 100644
--- a/website/pages/pl/index.json
+++ b/website/pages/pl/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Eksploruj subgrafy i zacznij korzystać z protokołu"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 4db433afaad85ff093a07b92ff093c0729e2838e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:39 -0500
Subject: [PATCH 0252/1325] New translations index.json (Portuguese)

---
 website/pages/pt/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/pt/index.json b/website/pages/pt/index.json
index 7a9d618567bb..9d8d3f9a08d4 100644
--- a/website/pages/pt/index.json
+++ b/website/pages/pt/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Explore subgraphs e interaja com o protocolo"
-      },
-      "hostedService": {
-        "title": "Serviço Hospedado",
-        "description": "Crie e explore subgraphs no serviço hospedado"
       }
     }
   },

From ce26fc649f411169af822ca6cbe4d90d965760d6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:41 -0500
Subject: [PATCH 0253/1325] New translations index.json (Russian)

---
 website/pages/ru/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/ru/index.json b/website/pages/ru/index.json
index f15e13b3bcb6..6f0d6145cb32 100644
--- a/website/pages/ru/index.json
+++ b/website/pages/ru/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Исследование подграфов и взаимодействие с протоколом"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 76145d32ba7c14c3a673c74bdce04f83a409fad0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:42 -0500
Subject: [PATCH 0254/1325] New translations index.json (Swedish)

---
 website/pages/sv/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/sv/index.json b/website/pages/sv/index.json
index 0bf12ec4ac63..9b056e8960c2 100644
--- a/website/pages/sv/index.json
+++ b/website/pages/sv/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graf Utforskaren",
         "description": "Utforska subgrafer och interagera med protokollet"
-      },
-      "hostedService": {
-        "title": "Värdtjänster",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 93980d2d6d6ec61d2c21d8cfd6fd9bf9130eea7c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:43 -0500
Subject: [PATCH 0255/1325] New translations index.json (Turkish)

---
 website/pages/tr/index.json | 8 ++------
 1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/website/pages/tr/index.json b/website/pages/tr/index.json
index 62480cb894b0..ef3649332398 100644
--- a/website/pages/tr/index.json
+++ b/website/pages/tr/index.json
@@ -56,16 +56,12 @@
       "graphExplorer": {
         "title": "Graph Gezgini",
         "description": "Subgraph'leri keşfedin ve protokolle etkileşime girin"
-      },
-      "hostedService": {
-        "title": "Barındırılan Hizmet",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },
   "supportedNetworks": {
     "title": "Desteklenen Ağlar",
-    "description": "The Graph supports the following networks.",
-    "footer": "For more details, see the {0} page."
+    "description": "The Graph aşağıdaki ağları destekler.",
+    "footer": "Daha fazla detay için {0} sayfasına bakın."
   }
 }

From b588b23f41c9e9490ace810add341d62abc79a0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:45 -0500
Subject: [PATCH 0256/1325] New translations about.mdx (Polish)

---
 website/pages/pl/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/pl/about.mdx b/website/pages/pl/about.mdx
index bc56c6ce8854..f669bb650fd6 100644
--- a/website/pages/pl/about.mdx
+++ b/website/pages/pl/about.mdx
@@ -2,46 +2,66 @@
 title: Więcej o The Graph
 ---
 
-Ta strona ma na celu wyjaśnienie czym jest The Graph i jak możesz zacząć go używać.
-
 ## Co to jest The Graph?
 
-The Graph jest zdecentralizowanym protokołem ideksującym dane na blockchainie i wysyłającym zapytania o te dane. The Graph umożliwia tworzenie zapytań o dane, które są bezpośrenio trudne do odpytania.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Projekty wykorzystujące kompleksowe smart kontrakty jak [Uniswap](https://uniswap.org/) i inicjatywy NFT jak [Bored Ape Yacht Club](https://boredapeyachtclub.com/) przechowują dane na blockchainie Ethereum, co sprawia, że bardzo trudno jest odczytać cokolwiek poza bardzo podstawowymi danymi dezpośrednio z danej sieci blockchain.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-Możesz równieź zbudować własny serwer, przetwarzać na nim tranzakcje, zapisaywać je w bazie danych i wykorzystywać punkt końcowy API w celu tworzenia zapytań o dane. Jednak ta opcja [wymaga dużych nakładów finansowych](/network/benefits/), regularnej konserwacji i utrzymania, a mimo to stanowi ona pojedyńczy punkt podatności na awarię i narusza warunki bezpieczeństwa wymagane w procesie decentralizacji.
+### How The Graph Functions
 
-**Indeksowanie danych na blockchainie jest bardzo, bardzo trudne.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Jak działa The Graph
+- 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.
 
-The Graph uczy się co i jak należy indeksować spośród danych sieci Ethereum na podstawie opisów subgraphów, zwanych manifestami. Opis subgraphu definiuje smart kontrakty, które leżą w obszarze zainteresowania danego subgraphu, zdarzenia w tych kontraktach, na które należy zwracać uwagę, oraz sposób mapowania danych zdarzeń na dane przechowywane w bazie danych The Graph.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Po napisaniu `manifestu subgraphu` można użyć narzędzia Graph CLI, aby przechować definicję w protokole IPFS i poinformować dowolnego indeksera o możliwości rozpoczęcia indeksowania danych dla tego subgraphu.
+- 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.
 
-Ten diagram przedstawia bardziej szczegółowo przepływ danych po wdrożeniu manifestu subgraphu, kiedy mamy do czynienia z transakcjami Ethereum:
+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 nieprzerwanie skanuje sieć Ethereum w poszukiwaniu nowych bloków i danych dla Twojego subgraphu, które mogą one zawierać.
-4. Graph Node znajduje zdarzenia Ethereum dla Twojego subgraphu w tych blokach i uruchamia dostarczone przez Ciebie procedury mapowania. Mapowanie to moduł WASM, który tworzy lub aktualizuje jednostki danych przechowywane przez węzeł Graph Node w odpowiedzi na zdarzenia Ethereum.
-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.
+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 nieprzerwanie skanuje sieć Ethereum w poszukiwaniu nowych bloków i danych dla Twojego subgraphu, które mogą one zawierać.
+4.  Graph Node znajduje zdarzenia Ethereum dla Twojego subgraphu w tych blokach i uruchamia dostarczone przez Ciebie procedury mapowania. Mapowanie to moduł WASM, który tworzy lub aktualizuje jednostki danych przechowywane przez węzeł Graph Node w odpowiedzi na zdarzenia Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 19e460631163d3e382fd2e1c446740c29e544af2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:46 -0500
Subject: [PATCH 0257/1325] New translations near.mdx (Polish)

---
 website/pages/pl/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/pl/cookbook/near.mdx b/website/pages/pl/cookbook/near.mdx
index a4f27caf6f3c..f2509e44e84c 100644
--- a/website/pages/pl/cookbook/near.mdx
+++ b/website/pages/pl/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From be3c231d9f69d3e38fc671fef18e85766538cdea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:47 -0500
Subject: [PATCH 0258/1325] New translations unit-testing-framework.mdx
 (Polish)

---
 .../pl/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/pl/developing/unit-testing-framework.mdx b/website/pages/pl/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/pl/developing/unit-testing-framework.mdx
+++ b/website/pages/pl/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From a118bd02a3f6098d525b9cd8faa3cbf7c811040c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:48 -0500
Subject: [PATCH 0259/1325] New translations about.mdx (Portuguese)

---
 website/pages/pt/about.mdx | 60 +++++++++++++++++++++++++-------------
 1 file changed, 40 insertions(+), 20 deletions(-)

diff --git a/website/pages/pt/about.mdx b/website/pages/pt/about.mdx
index b76fd3f3da93..f244df9f2b9d 100644
--- a/website/pages/pt/about.mdx
+++ b/website/pages/pt/about.mdx
@@ -2,46 +2,66 @@
 title: Sobre o The Graph
 ---
 
-Esta página explicará o que é o The Graph e como pode começar.
-
 ## O que é o The Graph?
 
-O The Graph é um protocolo descentralizado para indexação e queries de dados de blockchains. O The Graph possibilita a consulta de dados que são difíceis de consultar diretamente.
+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.
+
+## Entenda o Básico
 
 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.
 
-No caso do Bored Ape Yacht Club, podemos realizar operações básicas de leitura no [contrato](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code), como buscar o dono de um certo Ape, buscar a URI de conteúdo de um Ape com base na sua ID, ou na reserva total. Isto é possível porque estas operações de leitura são programadas diretamente no contrato inteligente, mas consultas e operações no mundo real mais avançadas, como agregação, busca, relacionamentos, e filtragem não-trivial _não_ são possíveis. Por exemplo, se quiséssemos consultar por Apes que são de um certo endereço, e filtrar por uma das suas características, nós não poderíamos pegar essa informação ao interagir diretamente com o próprio contrato.
+### Desafios sem o The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Por que isto é um problema?
+
+Levariam **horas, ou até mesmo dias**, para que um aplicativo descentralizado (dApp) executado em um navegador conseguisse uma resposta a estas questões simples.
+
+Como alternativa, haveria a opção de construir o seu próprio servidor, processar as transações, salvá-las num banco de dados, e construir um endpoint de API sobre tudo isso tudo para poder fazer o query dos dados. Porém, esta opção [consome muitos recursos](/network/benefits/), precisa de manutenção, apresenta um único ponto de falha, e quebra propriedades de segurança importantes obrigatórias para a descentralização.
+
+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.
+
+## The Graph Providencia uma Solução
+
+O The Graph resolve este desafio com um protocolo descentralizado que indexa e permite queries eficientes e de alto desempenho de dados de blockchain. Estas APIs ("subgraphs" indexados) podem então ser consultados num query com uma API GraphQL padrão.
 
-Para conseguir estes 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. Levariam **horas, ou até mesmo dias,** para que um aplicativo descentralizado (dApp) executado em um navegador conseguisse uma resposta a estas questões simples.
+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.
 
-Também valeria construir o seu próprio servidor, processar as transações lá, salvá-las em um banco de dados, e construir um endpoint de API sobre tudo isso tudo para poder fazer o query dos dados. Porém, esta opção [consome muitos recursos](/network/benefits/), precisa de manutenção, apresenta um único ponto de falha, e quebra propriedades de segurança importantes obrigatórias para a descentralização.
+### Como o The Graph Funciona
 
-**Indexar dados de blockchain é muito, muito difícil.**
+Indexar dados em blockchain é um processo difícil, mas facilitado pelo The Graph. O The Graph aprende como indexar dados no Ethereum com o uso de subgraphs. Subgraphs são APIs personalizadas construídas com dados de blockchain, que extraem, processam e armazenam dados de uma blockchain para poderem ser consultadas suavemente via GraphQL.
 
-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 conceitualmente dificultam a retirada de resultados corretos de queries dos dados da blockchain.
+#### Especificações
 
-O The Graph fornece uma solução com um protocolo descentralizado que indexa e permite queries eficientes e de alto desempenho de dados de blockchain. Estas APIs ("subgraphs" indexados) podem então ser consultados num query com uma API GraphQL padrão. Hoje, há um serviço hospedado, e também um protocolo descentralizado com as mesmas capabilidades. Ambos são apoiados pela implementação de código aberto do [Graph Node](https://github.com/graphprotocol/graph-node).
+- O The Graph usa descrições de subgraph, conhecidas como "manifests de subgraph" dentro do subgraph.
 
-## Como o The Graph Funciona
+- A descrição do subgraph contorna os contratos inteligentes de interesse para o mesmo, os eventos dentro destes contratos para focar, e como mapear dados de evento para dados que o The Graph armazenará no seu banco de dados.
 
-O The Graph aprende quais dados indexar, e como indexar os dados na Ethereum com base em descrições de subgraph — conhecidas como manifests de subgraph. A descrição do subgraph define os contratos inteligentes de interesse para o mesmo, os eventos nestes contratos para prestar atenção, e como mapear dados de evento para dados que o The Graph armazenará no seu banco de dados.
+- Ao criar um subgraph, primeiro é necessário escrever um manifest de subgraph.
 
-Quando tiver escrito um `subgraph manifest`, use o Graph CLI para armazenar a definição no IPFS e mandar o indexador começar a indexar dados para o subgraph.
+- Após escrever o `subgraph manifest`, é possível usar o Graph CLI para armazenar a definição no IPFS e instruir o Indexador para começar a indexar dados para o subgraph.
 
-Este diagrama dá mais detalhes sobre o fluxo de dados quando um manifest de subgraph for lançado, na questão de transações na Ethereum:
+O diagrama abaixo dá informações mais detalhadas sobre o fluxo de dados quando um manifest de subgraph for lançado com transações no Ethereum.
 
 ![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. O Graph Node escaneia continuamente a Ethereum por novos blocos e os dados que podem conter para o seu subgraph.
-4. O Graph Node encontra eventos na Ethereum para o seu subgraph nestes blocos e executa os handlers de mapeamento que forneceu. O mapeamento é um módulo WASM que cria ou atualiza as entidades de dados que o Graph Node armazena em resposta a eventos na Ethereum.
-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.
+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.  O Graph Node escaneia continuamente a Ethereum por novos blocos e os dados que podem conter para o seu subgraph.
+4.  O Graph Node encontra eventos na Ethereum para o seu subgraph nestes blocos e executa os handlers de mapeamento que forneceu. O mapeamento é um módulo WASM que cria ou atualiza as entidades de dados que o Graph Node armazena em resposta a eventos na Ethereum.
+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
 
-As seguintes secções explicam em mais detalhes como definir subgraphs, como lançá-los, e como buscar dados dos indexes que o Graph Node constrói.
+As seguintes secções providenciam um olhar mais íntimo nos subgraphs, na sua publicação e no query de dados.
 
-Antes de começar a escrever o seu próprio subgraph, confira o [Graph Explorer](https://thegraph.com/explorer) e explore alguns dos subgraphs que já foram lançados. A página para cada subgraph contém um playground que permite-lhe consultar os dados desse subgraph com queries no GraphQL.
+Antes de escrever o seu próprio subgraph, é recomendado explorar o [Graph Explorer](https://thegraph.com/explorer) e revir alguns dos subgraphs já publicados. A página de todo subgraph inclui um ambiente de teste em GraphQL que lhe permite consultar os dados dele.

From 17f17f75ec16c532d88058403fc5a389c7509003 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:49 -0500
Subject: [PATCH 0260/1325] New translations near.mdx (Portuguese)

---
 website/pages/pt/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/pt/cookbook/near.mdx b/website/pages/pt/cookbook/near.mdx
index 7cba020a1341..1b7c1254531f 100644
--- a/website/pages/pt/cookbook/near.mdx
+++ b/website/pages/pt/cookbook/near.mdx
@@ -37,7 +37,7 @@ Há três aspectos de definição de subgraph:
 
 **schema.graphql:** um arquivo schema que define quais dados são armazenados para o seu subgraph, e como consultá-los via GraphQL. Os requerimentos para subgraphs no NEAR são cobertos pela [documentação existente](/developing/creating-a-subgraph#the-graphql-schema).
 
-**Mapeamentos do AssemblyScript:** [Código em AssemblyScript](/developing/graph-ts/api) que traduz dos dados do evento às entidades definidas no seu schema. O apoio à NEAR introduz tipos de dados específicos ao NEAR e uma nova funcionalidade de análise de JSON.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 Existem dois comandos importantes durante o desenvolvimento de um subgraph:
 
@@ -98,7 +98,7 @@ A definição do schema descreve a estrutura do banco de dados do subgraph resul
 
 Os handlers para o processamento de eventos são escritos em [AssemblyScript](https://www.assemblyscript.org/).
 
-A indexação da NEAR introduz categorias de dados específicas à plataforma ao [API do AssemblyScript](/developing/graph-ts/api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ Estes tipos são repassados para handlers de blocos e recibos:
 - Handlers de blocos receberão um `Block`
 - Handlers de recibos receberão um `ReceiptWithOutcome`
 
-Caso contrário, o resto da [API do AssemblyScript](/developing/graph-ts/api) está à disposição dos programadores de subgraph no Near, durante a execução dos mapeamentos.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-Isto inclui uma nova função de análise em JSON: logs na NEAR são frequentemente emitidos como JSONs em string. A nova função `json.fromString(...)` está disponível como parte da [API JSON](/developing/graph-ts/api#json-api) para que programadores processem estes logs com facilidade.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## Lançando um Subgraph na NEAR
 
@@ -194,8 +194,8 @@ A configuração do nódulo dependerá de onde o subgraph será lançado.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Graph Node local (baseado na configuração padrão)

From 7fe2921e9c04f466aa14226e97190d01d40cdbe6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:50 -0500
Subject: [PATCH 0261/1325] New translations unit-testing-framework.mdx
 (Portuguese)

---
 .../pt/developing/unit-testing-framework.mdx  | 47 ++++++++++++-------
 1 file changed, 30 insertions(+), 17 deletions(-)

diff --git a/website/pages/pt/developing/unit-testing-framework.mdx b/website/pages/pt/developing/unit-testing-framework.mdx
index cf2b52a41290..c2c04c318f4f 100644
--- a/website/pages/pt/developing/unit-testing-framework.mdx
+++ b/website/pages/pt/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Estrutura de Testes de Unidades
 ---
 
-O Matchstick é uma estrutura de testes de unidades, desenvolvida pela [LimeChain](https://limechain.tech/), que permite que programadores de subgraph testem a sua lógica de mapeamento num ambiente de sandbox e lancem os seus subgraphs com confiança!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Como Começar
 
-### Dependências de instalação
+### Install Dependencies
 
-Para usar os métodos de test helper e executar os testes, instale as seguintes dependências:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ O `graph-node` depende do PostgreSQL, então se ainda não o tens, precisa instalá-lo. Recomendamos fortemente usar os comandos abaixo, pois adicioná-lo de qualquer outra maneira pode causar erros inesperados!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Comando de instalação do Postgres:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Crie um symlink ao último libpq.5.lib _Você pode precisar criar este diretóri
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Comando de instalação do Postgres (depende da sua distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 Pode usar o Matchstick no WSL tanto com a abordagem do Docker quanto com a abordagem binária. Como o WSL pode ser um pouco complicado, aqui estão algumas dicas caso encontre problemas
 
@@ -76,7 +85,7 @@ E finalmente, não use o `graph test` (que usa a sua instalação global do grap
 }
 ```
 
-### Uso
+### Using Matchstick
 
 Para usar o **Matchstick** no seu projeto de subgraph, basta abrir um terminal, navegar à pasta raiz do seu projeto e executar `graph test [options] <datasource>` — este baixa o binário mais recente do **Matchstick**, e executa o teste especificado, ou todos os testes especificados em uma pasta de teste (ou todos os testes existentes se não for especificado nenhum flag de fontes de dados).
 
@@ -1103,7 +1112,7 @@ test('ethereum/contract dataSource creation example', () => {
   assert.dataSourceCount('GraphTokenLockWallet', 0)
 
   // Crie uma nova fonte de dados GraphTokenLockWallet com o endereço
-  0xa16081f360e3847006db660bae1c6d1b2e17ec2a
+  0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
   GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
 
   // Garanta que a dataSource foi criada
@@ -1369,22 +1378,26 @@ A saída do log inclui a duração do teste. Veja um exemplo:
 
 > `Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined`
 
-Isto significa que usou o `console.log` no seu código, que não é apoiado pelo AssemblyScript. Considere usar a [API de Logging](/developing/graph-ts/api/#logging-api)
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > `ERROR TS2554: Expected ? arguments, but got ?.`
->
+> 
 > `return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);`
->
+> 
 > `in ~lib/matchstick-as/assembly/defaults.ts(18,12)`
->
+> 
 > `ERROR TS2554: Expected ? arguments, but got ?.`
->
+> 
 > `return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);`
->
+> 
 > `in ~lib/matchstick-as/assembly/defaults.ts(24,12)`
 
 A diferença nos argumentos é causada pela diferença no `graph-ts` e no `matchstick-as`. Problemas como este são melhor resolvidos ao atualizar tudo para a versão mais recente.
 
+## Outros Recursos
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 Caso tenha qualquer pergunta, opinião, pedidos de recursos, ou só quer entrar em contacto, venha para o Discord do The Graph — lá, temos um canal dedicado ao Matchstick, chamado 🔥| unit-testing.

From 4388f4086973eeaf719ef6ba5d4fa50f850df46c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:52 -0500
Subject: [PATCH 0262/1325] New translations about.mdx (Russian)

---
 website/pages/ru/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/ru/about.mdx b/website/pages/ru/about.mdx
index 9047ad860250..ed071feb2124 100644
--- a/website/pages/ru/about.mdx
+++ b/website/pages/ru/about.mdx
@@ -2,46 +2,66 @@
 title: О The Graph
 ---
 
-На этой странице Вы узнаете что такое протокол The Graph и как приступить к работе.
-
 ## Что такое Graph?
 
-The Graph - это децентрализованный протокол для индексации и запроса данных из блокчейна. The Graph позволяет запрашивать данные, которые сложно запросить напрямую.
+The Graph — это мощный децентрализованный протокол, который позволяет беспрепятственно запрашивать и индексировать данные блокчейна. Это упрощает сложный процесс запроса данных блокчейна, ускоряя и упрощая разработку децентрализованных приложений.
+
+## Понимание основ
+
+Проекты со сложными смарт-контрактами, такие как [Uniswap](https://uniswap.org/), и инициативы по созданию NFT, подобные [Bored Ape Yacht Club](https://boredapeyachtclub.com/), хранят данные в блокчейне Ethereum, что делает практически невозможным непосредственное чтение чего-либо, кроме базовых данных, из блокчейна.
+
+### Сложности, которые могут возникнуть без использования The Graph
+
+В приведенном выше примере, Bored Ape Yacht Club, Вы можете выполнять базовые операции чтения [контракта](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code). Вы можете узнать владельца определенного Ape, прочитать URI контента Ape на основе его идентификатора или узнать общее предложение.
+
+- Это можно сделать, поскольку данные операции чтения запрограммированы непосредственно в самом смарт-контракте. Однако более сложные, конкретные и реальные запросы и операции, такие как агрегирование, поиск, связи и нетривиальная фильтрация, **невозможны**.
+
+- Например, если Вы хотите узнать об Apes, принадлежащих определенному адресу, и уточнить свой поиск на основе конкретной характеристики, Вы не сможете получить эту информацию путем прямого взаимодействия с самим контрактом.
+
+- Чтобы получить больше данных, Вам придется обработать каждое когда-либо созданное событие [`передачи`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746), прочитать метаданные из IPFS, используя идентификатор токена и хэш IPFS, а затем агрегировать их.
+
+### Почему это является проблемой?
+
+Децентрализованному приложению (dapp), запущенному в браузере, потребуются **часы или даже дни**, чтобы получить ответ на эти простые вопросы.
+
+В качестве альтернативы у Вас есть возможность настроить собственный сервер, обрабатывать транзакции, хранить их в базе данных и создать конечную точку API для запроса данных. Однако этот вариант [ресурсоемок](/network/benefits/), требует обслуживания, представляет собой единственную возможную причину сбоя и нарушает важные свойства безопасности, необходимые для децентрализации.
+
+Такие свойства блокчейна, как окончательность, реорганизация чейна и необработанные блоки, усложняют процесс, делая получение точных результатов запроса из данных блокчейна трудоемким и концептуально сложным.
 
-Комплексные и сложные проекты такие, как [Uniswap](https://uniswap.org/) и проекты NFT такие, как [Bored Ape Yacht Club](https://boredapeyachtclub.com/) сохраняют свои данные в блокчейн Ethereum в таком формате, что их сложно обработать посылая запросы непосредственно в блокчейн.
+## The Graph предлагает решение
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+The Graph решает эту проблему с помощью децентрализованного протокола, который индексирует и обеспечивает эффективный и высокопроизводительный запрос данных блокчейна. Эти API (индексированные «субграфы») затем могут быть запрошены с помощью стандартного API GraphQL.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+Сегодня существует децентрализованный протокол, поддерживаемый реализацией с открытым исходным кодом [Graph Node](https://github.com/graphprotocol/graph-node), который обеспечивает этот процесс.
 
-Вы также можете создать свой собственный сервер, обработать там транзакции, сохранить их в базе данных и создать API-конечную точку поверх всего этого, чтобы запрашивать данные. Однако этот вариант требует [больших ресурсов](/network/benefits/), нуждается в обслуживании, представляет собой единую точку отказа и нарушает важные свойства безопасности, необходимые для децентрализации.
+### Как функционирует The Graph
 
-**Индексация данных - это очень трудоемкий процесс.**
+Индексирование данных блокчейна очень сложный процесс, но The Graph упрощает его. The Graph учится индексировать данные Ethereum с помощью субграфов. Субграфы — это пользовательские API, построенные на данных блокчейна, которые извлекают данные из блокчейна, обрабатывают их и сохраняют так, чтобы их можно было легко запрашивать через GraphQL.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Специфические особенности
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- В The Graph используются описания субграфов, которые называются манифестами субграфов внутри субграфа.
 
-## Как работает The Graph
+- В описании субграфа описываются смарт-контракты, представляющие интерес для субграфа, события в этих контрактах, на которых следует сосредоточиться, а также способы сопоставления данных о событиях с данными, которые The Graph будет хранить в своей базе данных.
 
-The Graph протокол узнает что и как индексировать из блокчейна основываясь на инструкциях "subgraph", называемый "subgraph манифест". Subgraph описывает: смарт-контракт, данные которого будут индексироваться, события данного смарт-контракта и как данные будут связаны (структура таблиц базы данных) для сохранения данных в базе данных.
+- При создании субграфа Вам необходимо написать манифест субграфа.
 
-Как только Вы создаете `subgraph манифест`, Вы с помощью Graph CLI сохраняете манифест в сети IPFS и указываете индексатору начинать индексировать данные использую данный субграф.
+- После написания `манифеста субграфа` Вы можете использовать Graph CLI для сохранения определения в IPFS и дать команду индексатору начать индексирование данных для этого субграфа.
 
-Данная диаграмма более детально описывает порядок следования данных после того как subgraph манифест активирован на сети:
+На диаграмме ниже представлена ​​более подробная информация о потоке данных после развертывания манифеста субграфа с транзакциями Ethereum.
 
 ![График, объясняющий потребителям данных, как The Graph использует Graph Node для обслуживания запросов](/img/graph-dataflow.png)
 
 Данные проходят следующий путь:
 
-1. Dapp добавляет данные в Ethereum через транзакцию в смарт-контракте.
-2. Смарт-контракт создает одно или несколько событий обрабатывая транзакции.
-3. TheGraph нода постоянно сканирует блокчейна и обрабатывает каждый новый блок на предмет поиска данных описанных в Вашем субграфе.
-4. The Graph нода затем разбирает события, относящиеся к Вашему субграфу, которые записаны в данном блоке и структурирует их согласно схеме данных описанной в subgraph используя модуль WASM. Затем данные сохраняются в таблицы базы данных Graph Node.
-5. Dapp запрашивает у Graph Node данные, проиндексированные с блокчейна, используя [конечную точку GraphQL](https://graphql.org/learn/) ноды. В свою очередь, Graph Node переводит запросы GraphQL в запросы к его базовому хранилищу данных, чтобы получить эти данные, используя возможности индексации этого хранилища. Dapp отображает эти данные в насыщенном пользовательском интерфейсе для конечных пользователей, который они используют для создания новых транзакций в Ethereum. Цикл повторяется.
+1.  Dapp добавляет данные в Ethereum через транзакцию в смарт-контракте.
+2.  Смарт-контракт генерирует одно или несколько событий во время обработки транзакции.
+3.  Graph Node постоянно сканирует Ethereum на наличие новых блоков и данных для Вашего субграфа, которые они могут содержать.
+4.  The Graph нода затем разбирает события, относящиеся к Вашему субграфу, которые записаны в данном блоке и структурирует их согласно схеме данных описанной в subgraph используя модуль WASM. Затем данные сохраняются в таблицы базы данных Graph Node.
+5.  Dapp запрашивает у Graph Node данные, проиндексированные с блокчейна, используя [конечную точку GraphQL](https://graphql.org/learn/) ноды. В свою очередь, Graph Node переводит запросы GraphQL в запросы к его базовому хранилищу данных, чтобы получить эти данные, используя возможности индексации этого хранилища. Dapp отображает эти данные в насыщенном пользовательском интерфейсе для конечных пользователей, который они используют для создания новых транзакций в Ethereum. Цикл повторяется.
 
 ## Что далее
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+В следующих разделах более подробно рассматриваются субграфы, их развертывание и запросы данных.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+Прежде чем писать собственный субграф, рекомендуется ознакомиться с [Graph Explorer](https://thegraph.com/explorer) и изучить некоторые из уже развернутых субграфов. Страница каждого субграфа включает в себя тестовую площадку GraphQL, позволяющую запрашивать его данные.

From b184d02a88c73869068767734d280225cac17dd3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:53 -0500
Subject: [PATCH 0263/1325] New translations near.mdx (Russian)

---
 website/pages/ru/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ru/cookbook/near.mdx b/website/pages/ru/cookbook/near.mdx
index 15f3d9436a04..f462d71a036a 100644
--- a/website/pages/ru/cookbook/near.mdx
+++ b/website/pages/ru/cookbook/near.mdx
@@ -37,7 +37,7 @@ The Graph предоставляет разработчикам инструме
 
 **schema.graphql:** файл схемы, который определяет, какие данные хранятся для вашего подграфа и как запрашивать их через GraphQL. Требования к подграфам NEAR рассматриваются в [существующей документации](/developing/creating-a-subgraph#the-graphql-schema).
 
-**Сопоставления AssemblyScript:** [Код AssemblyScript](/developing/graph-ts/api), который преобразует данные события в объекты, определенные в вашей схеме. Поддержка NEAR вводит почти специфические типы данных и новые функции синтаксического анализа JSON.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 Во время разработки субграфа есть две ключевые команды:
 
@@ -98,7 +98,7 @@ accounts:
 
 Обработчики событий написаны на языке [AssemblyScript](https://www.assemblyscript.org/).
 
-Индексация NEAR вводит NEAR-специфические типы данных в [AssemblyScript API](/developing/graph-ts/api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ class ReceiptWithOutcome {
 - Обработчики блоков получат `Block`
 - Обработчики квитанций получат `ReceiptWithOutcome`
 
-В противном случае остальная часть [AssemblyScript API](/developing/graph-ts/api) доступна разработчикам NEAR субграфа во время выполнения сопоставления.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-Это включает в себя новую функцию синтаксического анализа JSON - журналы на NEAR часто выдаются в виде stringified JSONs. Новая функция `json.fromString(...)` доступна как часть [JSON API](/developing/graph-ts/api#json-api), позволяющая разработчикам легко обрабатывать эти журналы.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## Развертывание NEAR субграфа
 
@@ -194,8 +194,8 @@ $ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <su
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From aa5805c9d45df286ec82031941735af6cf5b3b0a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:54 -0500
Subject: [PATCH 0264/1325] New translations about.mdx (Swedish)

---
 website/pages/sv/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/sv/about.mdx b/website/pages/sv/about.mdx
index 464822d00a4a..a819e0212c3b 100644
--- a/website/pages/sv/about.mdx
+++ b/website/pages/sv/about.mdx
@@ -2,46 +2,66 @@
 title: Om The Graph
 ---
 
-Denna sida kommer att förklara vad The Graph är och hur du kan komma igång.
-
 ## Vad är The Graph?
 
-The Graph är en decentraliserad protokoll för indexering och frågning av blockkedjedata. The Graph möjliggör frågor på data som är svår att fråga direkt.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Projekt med komplexa smarta kontrakt som [Uniswap](https://uniswap.org/) och NFT-initiativ som [Bored Ape Yacht Club](https://boredapeyachtclub.com/) lagrar data på Ethereum-blockkedjan, vilket gör det mycket svårt att läsa något annat än grundläggande data direkt från blockkedjan.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-Du skulle också kunna bygga din egen server, bearbeta transaktionerna där, spara dem i en databas och skapa en API-slutpunkt ovanpå alltihop för att fråga data. Men den här möjligheten är [resurskrävande](/network/benefits/), kräver underhåll, utgör en enskild felkälla och bryter viktiga säkerhetsegenskaper som krävs för decentralisering.
+### How The Graph Functions
 
-**Indexering av blockkedjedata är verkligen, verkligen svårt.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Hur The Graph Fungerar
+- 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.
 
-The Graf lär sig vad och hur man indexerar Ethereum-data baserat på subgrafbeskrivningar, kända som subgraf-manifestet. Subgrafbeskrivningen definierar de intressanta smarta kontrakten för en subgraf, händelserna i dessa kontrakt att vara uppmärksam på och hur man kartlägger händelsedata till data som The Graf kommer att lagra i sin databas.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-När du har skrivit ett `subgraf-manifest`, använder du Graf CLI för att lagra definitionen i IPFS och talar om för indexeringen att börja indexera data för den subgrafen.
+- 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.
 
-Denna diagram ger mer detaljer om datatillflödet när ett subgraf-manifest har distribuerats och hanterar Ethereum-transaktioner:
+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. Graf Node skannar kontinuerligt Ethereum efter nya block och den data för din subgraf de kan innehålla.
-4. Graf Node hittar Ethereum-händelser för din subgraf i dessa block och kör de kartläggande hanterarna du tillhandahållit. Kartläggningen är en WASM-modul som skapar eller uppdaterar de dataenheter som Graph Node lagrar som svar på Ethereum-händelser.
-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.
+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.  Graf Node skannar kontinuerligt Ethereum efter nya block och den data för din subgraf de kan innehålla.
+4.  Graf Node hittar Ethereum-händelser för din subgraf i dessa block och kör de kartläggande hanterarna du tillhandahållit. Kartläggningen är en WASM-modul som skapar eller uppdaterar de dataenheter som Graph Node lagrar som svar på Ethereum-händelser.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From de37a82558ff909359d8406d8e2e947b5f2c1924 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:55 -0500
Subject: [PATCH 0265/1325] New translations near.mdx (Swedish)

---
 website/pages/sv/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/sv/cookbook/near.mdx b/website/pages/sv/cookbook/near.mdx
index 0f96f29d0789..78fb45077df5 100644
--- a/website/pages/sv/cookbook/near.mdx
+++ b/website/pages/sv/cookbook/near.mdx
@@ -37,7 +37,7 @@ Det finns tre aspekter av subgraf definition:
 
 **schema.graphql:** en schema fil som definierar vilken data som lagras för din subgraf, och hur man frågar den via GraphQL. Kraven för NEAR undergrafer täcks av [den befintliga dokumentationen](/developing/creating-a-subgraph#the-graphql-schema).
 
-**AssemblyScript Mappings:**[AssemblyScript kod](/developing/graph-ts/api) som översätter från händelsedata till de enheter som definieras i ditt schema. NEAR stöd introducerar NEAR specifika datatyper och ny JSON parsnings funktion.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 Under subgrafutveckling finns det två nyckelkommandon:
 
@@ -98,7 +98,7 @@ Schemadefinition beskriver strukturen för den resulterande subgraf databasen oc
 
 Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/).
 
-NEAR indexering introducerar NEAR specifika datatyper till [AssemblyScript API](/developing/graph-ts/api).
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ Dessa typer skickas till block & kvittohanterare:
 - Blockhanterare kommer att få ett `Block`
 - Kvittohanterare kommer att få ett `ReceiptWithOutcome`
 
-Annars är resten av [AssemblyScript API](/developing/graph-ts/api) tillgänglig för NEAR subgraf utvecklare under körning av mappning.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-Detta inkluderar en ny JSON parsnings funktion - loggar på NEAR sänds ofta ut som strängade JSON. En ny funktion `json.fromString(...)` är tillgänglig som en del av [JSON API](/developing/graph-ts/api#json-api) för att tillåta utvecklare för att enkelt bearbeta dessa loggar.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## Utplacera en NEAR Subgraf
 
@@ -194,8 +194,8 @@ Nodkonfigurationen beror på var subgrafen distribueras.
 ### Subgraf Studion
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Lokal graf nod (baserat på standardkonfiguration)

From 39850053a9c896e5dbd149856001bb6da49f6b89 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:56 -0500
Subject: [PATCH 0266/1325] New translations unit-testing-framework.mdx
 (Swedish)

---
 .../sv/developing/unit-testing-framework.mdx  | 47 ++++++++++++-------
 1 file changed, 30 insertions(+), 17 deletions(-)

diff --git a/website/pages/sv/developing/unit-testing-framework.mdx b/website/pages/sv/developing/unit-testing-framework.mdx
index e63db684cea7..03affcca6484 100644
--- a/website/pages/sv/developing/unit-testing-framework.mdx
+++ b/website/pages/sv/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Enhetsprovningsramverk
 ---
 
-Matchstick är ett enhetsprovningsramverk utvecklat av [LimeChain](https://limechain.tech/) som möjliggör för subgraph-utvecklare att testa sin kartläggningslogik i en avskärmad miljö och distribuera sina subgrapher med förtroende!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Komma igång
 
-### Installera beroenden
+### Install Dependencies
 
-För att använda testhjälpmedlen och köra testerna måste du installera följande beroenden:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ graph-node är beroende av PostgreSQL, så om du inte redan har det måste du installera det. Vi rekommenderar starkt att du använder följande kommandon eftersom att lägga till det på något annat sätt kan orsaka oväntade fel!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Kommando för installation av Postgres:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Skapa en symbolisk länk till den senaste libpq.5.lib._ Du kanske behöver skapa
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Kommando för Postgres installation (beroende på din distribution):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 Du kan använda Matchstick i WSL både med Docker-metoden och binärmetoden. Eftersom WSL kan vara lite knepigt, här är några tips om du stöter på problem som
 
@@ -52,7 +61,7 @@ eller
 <PROJECT_PATH>/node_modules/gluegun/build/index.js:13 throw up;
 ```
 
-Se till att du använder en nyare version av Node.js eftersom graph-cli inte längre stöder **v10.19.0**, och det är fortfarande standardversionen för nya Ubuntu-bilder på WSL. Till exempel är Matchstick bekräftat fungerande på WSL med **v18.1.0**. Du kan byta till den antingen via** nvm ** eller genom att uppdatera din globala Node.js. Glöm inte att ta bort `node_modules` och köra `npm install`igen efter att du har uppdaterat Node.js! Sedan, se till att du har **libpq** installerat, du kan göra det genom att köra
+Se till att du använder en nyare version av Node.js eftersom graph-cli inte längre stöder **v10.19.0**, och det är fortfarande standardversionen för nya Ubuntu-bilder på WSL. Till exempel är Matchstick bekräftat fungerande på WSL med **v18.1.0**. Du kan byta till den antingen via** nvm ** eller genom att uppdatera din globala Node.js. Glöm inte att ta bort `node_modules` och köra ` npm install `igen efter att du har uppdaterat Node.js! Sedan, se till att du har **libpq** installerat, du kan göra det genom att köra
 
 ```
 sudo apt-get install libpq-dev
@@ -76,7 +85,7 @@ Och till sist, använd inte `graph test` (som använder din globala installation
 }
 ```
 
-### Användning
+### Using Matchstick
 
 För att använda **Matchstick** i ditt subgrafprojekt öppnar du bara en terminal, navigerar till rotmappen för ditt projekt och kör helt enkelt `graftest [options] <datasource> ` - den laddar ner den senaste **Matchstick**-binären och kör det angivna testet eller alla tester i en testmapp (eller alla befintliga tester om ingen datakällasflagga är angiven).
 
@@ -1368,22 +1377,26 @@ Loggutmatningen innehåller testkörningens varaktighet. Här är ett exempel:
 
 > Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined
 
-Det betyder att du har använt `console.log` i din kod, som inte stöds av AssemblyScript. Överväg att använda [Logging API](/developing/graph-ts/api/#logging-api)
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Motsägelsen i argumenten beror på en motsägelse i `graph-ts` och `matchstick-as`. Det bästa sättet att åtgärda problem som detta är att uppdatera allt till den senaste utgivna versionen.
 
+## Ytterligare resurser
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Respons
 
 Om du har några frågor, feedback, funktionsförfrågningar eller bara vill nå ut, är det bästa stället The Graph Discord där vi har en dedikerad kanal för Matchstick, kallad 🔥| unit-testing.

From ce43020422666ffeb0d6df995cf49e70f984f592 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:58 -0500
Subject: [PATCH 0267/1325] New translations about.mdx (Turkish)

---
 website/pages/tr/about.mdx | 68 ++++++++++++++++++++++++--------------
 1 file changed, 44 insertions(+), 24 deletions(-)

diff --git a/website/pages/tr/about.mdx b/website/pages/tr/about.mdx
index 5858793e7da6..eba9046c6f35 100644
--- a/website/pages/tr/about.mdx
+++ b/website/pages/tr/about.mdx
@@ -2,46 +2,66 @@
 title: Graph Hakkında
 ---
 
-This page will explain what The Graph is and how you can get started.
+## The Graph Nedir?
 
-## What is The Graph?
+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 is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+## Temeller
 
-Projects with complex smart contracts like [Uniswap](https://uniswap.org/) and NFTs initiatives like [Bored Ape Yacht Club](https://boredapeyachtclub.com/) store data on the Ethereum blockchain, making it really difficult to read anything other than basic data directly from the blockchain.
+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.
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+### The Graph Olmadığında Karşılaşılan Zorluklar
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+- 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**.
 
-**Indexing blockchain data is really, really hard.**
+- Ö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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+- 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 provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+### Bu neden bir sorun?
 
-## How The Graph Works
+Bu basit sorulara yanıt almak, tarayıcıda çalışan bir merkeziyetsiz uygulama (dapp) için **saatler, hatta günler ** sürebilir.
 
-The Graph learns what and how to index Ethereum data based on subgraph descriptions, known as the subgraph manifest. The subgraph description defines the smart contracts of interest for a subgraph, the events in those contracts to pay attention to, and how to map event data to data that The Graph will store in its database.
+Alternatif olarak, kendi sunucunuzu kurup işlemleri işleyebilir, bunları bir veri tabanında depolayabilir ve veriyi sorgulamak için bir API uç noktası oluşturabilirsiniz. Ancak, bu seçenek [kaynak açısından maliyetli](/network/benefits/) olup sürekli bakım gerektirir, tek bir arıza noktası oluşturur ve merkeziyetsizliğin gerektirdiği önemli güvenlik özelliklerini ortadan kaldırır.
 
-Once you have written a `subgraph manifest`, you use the Graph CLI to store the definition in IPFS and tell the indexer to start indexing data for that 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+## The Graph'in Sağladığı Çözüm
 
-![A graphic explaining how The Graph uses Graph Node to serve queries to data consumers](/img/graph-dataflow.png)
+The Graph, blokzinciri verilerini endeksleyip verimli, yüksek performanslı sorgulama imkanı sunan merkeziyetsiz bir protokol ile bu zorluğu çözer. Bu endekslenmiş API'lar ("subgraph'ler"), standart bir GraphQL API'ı ile sorgulanabilir.
 
-The flow follows these steps:
+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.
 
-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.
+### The Graph'in Çalışma Şekli
 
-## Next Steps
+Blokzinciri verilerini endekslemek oldukça zordur, ancak The Graph bunu kolaylaştırır. The Graph, Ethereum verilerini nasıl endeksleyeceğini subgraph'ler kullanarak öğrenir. Subgraph'ler, blokzinciri verileri üzerine kurulu özel yapım API'lerdir; bu API'ler blokzincirinden veriyi çıkarır, işler ve sorguların GraphQL ile sorunsuz bir şekilde yapılabilmesi için depolar.
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+#### Ayrıntılar
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+- The Graph, subgraph tanımlarını kullanır; bu tanımlar subgraph içinde subgraph manifestosu olarak bilinir.
+
+- Subgraph tanımı, bir subgraph için ilgili akıllı sözleşmeleri, bu sözleşmelerde odaklanılacak olayları ve bu olay verilerinin The Graph'in veritabanında depolayacağı verilere nasıl eşleneceğini açıklar.
+
+- Subgraph oluştururken bir subgraph manifestosu yazmanız gerekir.
+
+- `Subgraph manifestosunu` yazdıktan sonra, Graph CLI'yi kullanarak tanımı IPFS'e depolayabilir ve bir Indexer'a bu subgraph için veri endekslemeye başlaması talimatını verebilirsiniz.
+
+Aşağıdaki diyagramda, subgraph manifestosunun Ethereum blokzinciri üzerinde yapılan işlemler aracılığıyla yayına alınmasından sonra veri akışının nasıl ilerlediğine dair daha detaylı bilgi bulabilirsiniz.
+
+![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 Düğümü, Ethereum blokzincirini yeni blokları sürekli olarak tarar ve blokların subgraph'iniz için endekslenmesi gereken verileri içerip içermediğini kontrol eder.
+4.  Graph Düğümü, bu bloklarda subgraph'iniz için Ethereum olaylarını bulur ve sağladığınız eşleme işleyicilerini (mapping handler) çalıştırır. Eşleme (mapping), Ethereum olaylarına karşılık olarak Graph Düğümünün depoladığı veri varlıklarını oluşturan veya güncelleyen bir WASM modülüdür.
+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
+
+Sonraki bölümler, subgraph'lere, yayına alınmalarına ve veri sorgulama sürecine daha derin bir bakış sunmaktadır.
+
+Kendi subgraph'inizi yazmadan önce, [Graph Explorer](https://thegraph.com/explorer)'ı keşfetmeniz ve halihazırda yayına alınmış bazı subgraph'leri incelemeniz önerilir. Her subgraph'in sayfasında bir GraphQL playground bulunur. Bu aracı kullanarak subgraph'in verilerine erişebilir ve sorgulamalar yapabilirsiniz.

From 0da8d56b2c4a1419a68aabd70e3a5f06b63fa95d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:35:59 -0500
Subject: [PATCH 0268/1325] New translations graphql-api.mdx (Polish)

---
 website/pages/pl/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/pl/querying/graphql-api.mdx b/website/pages/pl/querying/graphql-api.mdx
index 2bbc71b5bb9c..d8671e53a77c 100644
--- a/website/pages/pl/querying/graphql-api.mdx
+++ b/website/pages/pl/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### Example
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | Description |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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                                |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 7305efeba65d1590d88ee73d57429eb19a10211f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:00 -0500
Subject: [PATCH 0269/1325] New translations graphql-api.mdx (Portuguese)

---
 website/pages/pt/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/pt/querying/graphql-api.mdx b/website/pages/pt/querying/graphql-api.mdx
index 681420e04980..4f64d26bf2a2 100644
--- a/website/pages/pt/querying/graphql-api.mdx
+++ b/website/pages/pt/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: API GraphQL
 ---
 
-Este guia explica a API de Queries GraphQL usada para o Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries (Consultas em query)
+## What is GraphQL?
 
-No schema do seu subgraph, são definidos tipos chamados de `Entities` (Entidade). Para cada tipo de `Entity`, um campo de `entity` e `entities` será gerado no tipo `Query` de alto nível. Note que o `query` não precisa ser incluído no topo da consulta `graphql` ao usar o The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Exemplos
 
@@ -21,7 +29,7 @@ Um query para uma única entidade `Token` definida no seu schema:
 }
 ```
 
-> **Nota:** Ao fazer um query para uma única entidade, é obrigatório um campo `id`; este deve ser um string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Consulte todas as entidades `Token`:
 
@@ -36,7 +44,10 @@ Consulte todas as entidades `Token`:
 
 ### Organização
 
-Ao consultar uma coleção, o parâmetro `orderBy` pode ser usado para organizar por um atributo específico. Além disto, o `orderDirection` serve para especificar a direção de organização, sendo `asc` para ascendente ou `desc` para descendente.
+When querying a collection, you may:
+
+- 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.
 
 #### Exemplo
 
@@ -53,7 +64,7 @@ Ao consultar uma coleção, o parâmetro `orderBy` pode ser usado para organizar
 
 Desde o Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0), as entidades podem ser organizadas com base nas entidades aninhadas.
 
-No seguinte exemplo, organizamos os tokens pelo nome do dono:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ No seguinte exemplo, organizamos os tokens pelo nome do dono:
 
 ### Paginação
 
-Ao consultar uma coleção, o parâmetro `first` (primeiro) serve para paginar do começo da coleção. Vale notar que a ordem de organização padrão é por ID em ordem alfanumérica ascendente, não por hora de criação.
-
-E mais: o parâmetro `skip` serve para pular entidades e paginar. Por ex. `first:100` mostra as primeiras 100 entidades e `first:100, skip:100` mostra as próximas 100.
+When querying a collection, it's best to:
 
-Evite usar valores `skip` muito grandes nos queries, pois estes tendem a ter um mau desempenho. Para resgatar um grande número de itens, é muito melhor paginar por entidades com base num atributo, como visto no último exemplo.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Exemplo com o `first`
 
@@ -106,7 +118,7 @@ Consulte 10 entidades `Token`, deslocada por 10 posições do começo da coleç
 
 #### Exemplo com `first` e `id_ge`
 
-Se um cliente precisar retirar um grande número de entidades, é muito mais eficiente basear consultas num atributo e filtrar pelo mesmo. Por exemplo, um cliente retiraria um número grande de tokens com este query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-Na primeira vez, ele enviaria a consulta com `lastID = ""`, e em pedidos seguintes, configuraria `lastID` no atributo `id` da última entidade no pedido anterior. Este método será mais eficiente do que usar valores `skip` crescentes.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtragem
 
-O parâmetro `where` serve nas suas consultas para filtrar por propriedades diferentes. É possível filtrar em múltiplos valores dentro do parâmetro `where`.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Exemplo com `where`
 
@@ -155,7 +168,7 @@ Pode usar sufixos como `_gt`, `_lte` para comparar valores:
 
 #### Exemplo para filtragem de blocos
 
-Também dá para filtrar entidades pelo `_change_block(number_gte: Int)` — o que filtra entidades atualizadas no bloco especificado ou depois dele.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Isto pode servir caso mire retirar apenas entidades que mudaram, por exemplo, desde a última vez que você pesquisou. Também pode ser bom investigar ou debugar como as entidades mudam no seu subgraph (se combinado com um filtro de blocos, pode isolar apenas entidades que mudaram em um bloco específico).
 
@@ -193,7 +206,7 @@ Desde o Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/relea
 
 ##### Operador `AND`
 
-No seguinte exemplo, filtramos por desafios com `outcome`, `succeeded` e `number` maiores que ou iguais a `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ No seguinte exemplo, filtramos por desafios com `outcome`, `succeeded` e `number
 ```
 
 > **Açúcar sintático**: pode simplificar a consulta acima ao retirar o operador `and`, com o passe de uma subexpressão separada por vírgulas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ No seguinte exemplo, filtramos por desafios com `outcome`, `succeeded` e `number
 
 ##### Operador `OR`
 
-No seguinte exemplo, filtramos por desafios com `outcome`, `succeeded` e `number` maiores que ou iguais a `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 Pode consultar 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 alto de query.
 
-O resultado de um tal query não mudará com o tempo; por ex., queries num certo bloco passado retornarão o mesmo resultado, independente de quando ele for executado. Exceto que, se fizer um query num bloco muito perto do topo da chain, o resultado pode mudar se aquele bloco acabar ausente da chain principal e a chain for reorganizada. Quando um bloco puder ser considerado final, o resultado da consulta não mudará.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note que a implementação atual ainda é 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 uma consulta 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 consulta. [Este inquérito](https://github.com/graphprotocol/graph-node/issues/1405) explica quais são estas limitações em detalhes.
+> 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.
 
 #### Exemplo
 
@@ -322,12 +335,12 @@ Buscas fulltext têm um campo obrigatório, `text`, para ofertar termos de busca
 
 Operadores de busca fulltext:
 
-| Símbolo | Operador | Descrição |
-| --- | --- | --- |
-| `&` | `And` | Para combinar múltiplos termos de busca num filtro para entidades que incluem todos os termos fornecidos |
-| &#x7c; | `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                                                |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ O Graph Node implementa uma validação [baseada em especificação](https://spe
 
 ## Schema
 
-O schema da sua fonte de dados — isto é, os tipos de entidade, valores e relacionamentos disponíveis à consulta — são definidos através da [Linguagem de Definição de Interface GraphQL (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-Os schemas GraphQL geralmente definem tipos de raiz para `queries` (consultas), `subscriptions` (inscrições) e `mutations` (mutações). O The Graph só apoia `queries`. O tipo raiz `Query` para o seu subgraph é gerado automaticamente a partir do schema GraphQL incluído no manifest do seu subgraph.
+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).
 
-> **Nota:** A nossa API não expõe mutações, porque se espera que programadores emitam transações diretamente perante a blockchain subjacente, a partir dos seus aplicativos.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entidades
 

From 5caf39f0de461f3943796c67347c4b51b12e6ea6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:01 -0500
Subject: [PATCH 0270/1325] New translations graphql-api.mdx (Swedish)

---
 website/pages/sv/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/sv/querying/graphql-api.mdx b/website/pages/sv/querying/graphql-api.mdx
index 32e9fbc90032..89b541abf5eb 100644
--- a/website/pages/sv/querying/graphql-api.mdx
+++ b/website/pages/sv/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Förfrågningar
+## What is GraphQL?
 
-I din delgrafig schema definierar du typer som kallas `Entiteter`. För varje typ av `Entitet` kommer ett `entitet`- och `entiteter`-fält att genereras på toppnivån av `Query`-typen. Observera att `query` inte behöver inkluderas högst upp i `graphql`-förfrågan när du använder The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Exempel
 
@@ -21,7 +29,7 @@ Förfrågan efter en enda `Token` -entitet som är definierad i din schema:
 }
 ```
 
-> **Note:** Vid sökning efter en enskild enhet krävs fältet `id`, och det måste vara en sträng.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Fråga alla `Token`-enheter:
 
@@ -36,7 +44,10 @@ Fråga alla `Token`-enheter:
 
 ### Sortering
 
-När du frågar efter en samling kan parametern `orderBy` användas för att sortera efter ett specifikt attribut. Dessutom kan `orderDirection` användas för att ange sorteringsriktningen, `asc` för stigande eller `desc` för fallande.
+When querying a collection, you may:
+
+- 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.
 
 #### Exempel
 
@@ -53,7 +64,7 @@ När du frågar efter en samling kan parametern `orderBy` användas för att sor
 
 Från och med Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) kan entiteter sorteras på basis av nästlade entiteter.
 
-I följande exempel sorterar vi tokens efter namnet på deras ägare:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ I följande exempel sorterar vi tokens efter namnet på deras ägare:
 
 ### Paginering
 
-När du frågar efter en samling kan parametern `first` användas för att paginera från början av samlingen. Det är värt att notera att standardsorteringsordningen är efter ID i stigande alfanumerisk ordning, inte efter skapelsetid.
-
-Vidare kan parametern `skip` användas för att hoppa över enheter och paginera. t.ex. `first:100` visar de första 100 enheterna och `first:100, skip:100` visar de nästa 100 enheterna.
+When querying a collection, it's best to:
 
-Frågor bör undvika att använda mycket stora `skip`-värden eftersom de i allmänhet fungerar dåligt. För att hämta ett stort antal objekt är det mycket bättre att bläddra igenom entiteter baserat på ett attribut som visas i det sista exemplet.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### Exempel med `first`
 
@@ -106,7 +118,7 @@ Fråga 10 `Token`-enheter, förskjutna med 10 platser från början av samlingen
 
 #### Exempel med `first` och `id_ge`
 
-Om en klient behöver hämta ett stort antal entiteter är det mycket mer effektivt att basera frågor på ett attribut och filtrera efter det attributet. En klient kan till exempel hämta ett stort antal tokens med hjälp av den här frågan:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-Första gången skickas frågan med `lastID = ""`, och för efterföljande frågor sätts `lastID` till `id`-attributet för den sista entiteten i den föregående frågan. Detta tillvägagångssätt kommer att fungera betydligt bättre än att använda ökande `skip`-värden.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtrering
 
-Du kan använda parametern `where` i dina frågor för att filtrera efter olika egenskaper. Du kan filtrera på flera värden inom parametern `where`.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### Exempel med `where`
 
@@ -155,7 +168,7 @@ Du kan använda suffix som `_gt`, `_lte` för värdejämförelse:
 
 #### Exempel på blockfiltrering
 
-Du kan också filtrera entiteter efter `_change_block(number_gte: Int)` - detta filtrerar entiteter som uppdaterades i eller efter det angivna blocket.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Detta kan vara användbart om du bara vill hämta enheter som har ändrats, till exempel sedan den senaste gången du pollade. Eller alternativt kan det vara användbart för att undersöka eller felsöka hur enheter förändras i din undergraf (om det kombineras med ett blockfilter kan du isolera endast enheter som ändrades i ett visst block).
 
@@ -193,7 +206,7 @@ Från och med Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node
 
 ##### `OCH` Operator
 
-I följande exempel filtrerar vi efter utmaningar med `utfall` `lyckades` och `nummer` större än eller lika med `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ I följande exempel filtrerar vi efter utmaningar med `utfall` `lyckades` och `n
 ```
 
 > **Syntactic sugar:** Du kan förenkla ovanstående fråga genom att ta bort `and`-operatorn och istället skicka ett underuttryck separerat med kommatecken.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ I följande exempel filtrerar vi efter utmaningar med `utfall` `lyckades` och `n
 
 ##### `OR` Operatör
 
-I följande exempel filtrerar vi efter utmaningar med `outcome` `succeeded` eller `number` större än eller lika med `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 Du kan förfråga tillståndet för dina enheter inte bara för den senaste blocken, som är standard, utan också för en godtycklig block i det förflutna. Blocket vid vilket en förfrågan ska ske kan specifieras antingen med dess blocknummer eller dess blockhash genom att inkludera ett `block`-argument i toppnivåfälten för förfrågningar.
 
-Resultatet av en sådan förfrågan kommer inte att ändras över tid, det vill säga, att förfråga vid en viss tidigare block kommer att returnera samma resultat oavsett när det utförs, med undantag för att om du förfrågar vid ett block mycket nära huvudet av kedjan, kan resultatet ändras om det visar sig att blocket inte är på huvudkedjan och kedjan omorganiseras. När ett block kan anses vara slutgiltigt kommer resultatet av förfrågan inte att ändras.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Observera att den nuvarande implementationen fortfarande är föremål för vissa begränsningar som kan bryta mot dessa garantier. Implementeringen kan inte alltid avgöra om en given blockhash inte alls är på huvudkedjan eller om resultatet av en förfrågan med blockhash för ett block som ännu inte kan anses vara slutgiltigt kan påverkas av en samtidig omorganisering av block. De påverkar inte resultaten av förfrågningar med blockhash när blocket är slutgiltigt och känt att vara på huvudkedjan. [Detta problem](https://github.com/graphprotocol/graph-node/issues/1405) förklarar dessa begränsningar i detalj.
+> 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
 
@@ -322,12 +335,12 @@ Fulltextsökförfrågningar har ett obligatoriskt fält, `text`, för att tillha
 
 Fulltextsökoperatorer:
 
-| Symbol | Operatör | Beskrivning |
-| --- | --- | --- |
-| `&` | `Och` | För att kombinera flera söktermer till ett filter för entiteter som inkluderar alla de angivna termerna |
-| &#x7c; | `Eller` | 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 |
-| `<->` | `Följs av` | 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                                                                                                                                     |
+| ----------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `&`     | `Och`      | För att kombinera flera söktermer till ett filter för entiteter som inkluderar alla de angivna termerna                                         |
+| &#x7c;      | `Eller`    | 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 |
+| `<->` | `Följs av` | Ange avståndet mellan två ord.                                                                                                                  |
+| `:*`        | `Prefix`   | Använd prefixsöktermen för att hitta ord vars prefix matchar (2 tecken krävs.)                                                                  |
 
 #### Exempel
 
@@ -376,11 +389,11 @@ Graph Node implementerar [specifikationsbaserad](https://spec.graphql.org/Octobe
 
 ## Schema
 
-Schemat för din datakälla - det vill säga de entitetstyper, värden och relationer som är tillgängliga för frågor - definieras genom [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-GraphQL-scheman definierar i allmänhet rottyper för `queries`, `subscriptions` och `mutations`. Grafen stöder endast `queries`. Rottypen `Query` för din subgraf genereras automatiskt från GraphQL-schemat som ingår i subgrafmanifestet.
+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:** Vårt API exponerar inte mutationer eftersom utvecklare förväntas utfärda transaktioner direkt mot den underliggande blockkedjan från sina applikationer.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entiteter
 

From c6c8aa1c855dbecdcb51f4976d89c8f680c06989 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:03 -0500
Subject: [PATCH 0271/1325] New translations api.mdx (Polish)

---
 website/pages/pl/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/pl/developing/graph-ts/api.mdx b/website/pages/pl/developing/graph-ts/api.mdx
index 46442dfa941e..8fc1f4b48b61 100644
--- a/website/pages/pl/developing/graph-ts/api.mdx
+++ b/website/pages/pl/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API Reference
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Built-in Types
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Handling Reverted Calls
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Encoding/Decoding ABI
 

From 421b092c0060ddb868a3dbcd610953b35eb202c9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:04 -0500
Subject: [PATCH 0272/1325] New translations api.mdx (Portuguese)

---
 website/pages/pt/developing/graph-ts/api.mdx | 130 ++++++++++---------
 1 file changed, 70 insertions(+), 60 deletions(-)

diff --git a/website/pages/pt/developing/graph-ts/api.mdx b/website/pages/pt/developing/graph-ts/api.mdx
index f60daaf3ce3b..acc557d643ab 100644
--- a/website/pages/pt/developing/graph-ts/api.mdx
+++ b/website/pages/pt/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: API AssemblyScript
 ---
 
-> Nota: Se criou um subgraph antes da versão `0.22.0` do `graph-cli`/`graph-ts`, está a usar uma versão mais antiga do AssemblyScript. Favor conferir o [Guia de Migração](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-Esta página documenta quais APIs embutidas podem ser usadas ao escrever mapeamentos de subgraph. Há dois tipos de API disponíveis do início:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- a [biblioteca do Graph TypeScript](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) e
-- códigos gerados a partir dos arquivos do subgraph por `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-Também é possível adicionar outras bibliotecas como dependências, desde que sejam compatíveis com o [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Como esta é a linguagem na qual são escritos os mapeamentos, a [wiki do AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) é uma boa referência para a linguagem e as características comuns das bibliotecas.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Referência da API
 
@@ -27,16 +29,16 @@ A biblioteca `@graphprotocol/graph-ts` fornece as seguintes APIs:
 
 No manifest do subgraph, `apiVersion` especifica a versão da API de mapeamento, executada pelo Graph Node para um subgraph.
 
-| Versão | Notas de atualização |
-| :-: | --- |
-| 0.0.9 | Adiciona novas funções de host [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adiciona validação para existência de campos no schema ao salvar uma entidade. |
-| 0.0.7 | Classes `TransactionReceipt` e `Log` adicionadas aos tipos do EthereumCampo <br />Campo `receipt` adicionado ao objeto Ethereum Event |
-| 0.0.6 | Campo `nonce` adicionado ao objeto Ethereum TransactionCampo <br />`baseFeePerGas` adicionado ao objeto Ethereum Block |
-| 0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` |
-| 0.0.4 | Campo `functionSignature` adicionado ao objeto Ethereum SmartContractCall |
-| 0.0.3 | Campo `from` adicionado ao objeto Ethereum<br /> `Calletherem.call.address` renomeado para `ethereum.call.to` |
-| 0.0.2 | Campo `input` adicionado ao objeto Ethereum Transaction |
+| Versão | Notas de atualização                                                                                                                                                                                                                      |
+| :----: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9 | Adiciona novas funções de host [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                       |
+|  0.0.8 | Adiciona validação para existência de campos no schema ao salvar uma entidade.                                                                                                                                                            |
+|  0.0.7 | Classes `TransactionReceipt` e `Log` adicionadas aos tipos do EthereumCampo <br />Campo `receipt` adicionado ao objeto Ethereum Event                                                                                                     |
+|  0.0.6 | Campo `nonce` adicionado ao objeto Ethereum TransactionCampo <br />`baseFeePerGas` adicionado ao objeto Ethereum Block                                                                                                                    |
+|  0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` |
+|  0.0.4 | Campo `functionSignature` adicionado ao objeto Ethereum SmartContractCall                                                                                                                                                                 |
+|  0.0.3 | Campo `from` adicionado ao objeto Ethereum<br /> `Calletherem.call.address` renomeado para `ethereum.call.to`                                                                                                                             |
+|  0.0.2 | Campo `input` adicionado ao objeto Ethereum Transaction                                                                                                                                                                                   |
 
 ### Tipos Embutidos
 
@@ -164,7 +166,8 @@ _Matemática_
 import { TypedMap } from '@graphprotocol/graph-ts'
 ```
 
-O `TypedMap` pode servir para armazenar pares de chave e valor (key e value ). Confira [este exemplo](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
+O `TypedMap` pode servir para armazenar pares de chave e valor (key e value
+). Confira [este exemplo](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
 
 A classe `TypedMap` tem a seguinte API:
 
@@ -252,7 +255,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 Quando um evento `Transfer` é encontrado durante o processamento da chain, ele é passado para o handler de evento `handleTransfer` com o tipo `Transfer` gerado (apelidado de `TransferEvent` aqui, para evitar confusões com o tipo de entidade). Este tipo permite o acesso a dados como a transação parente do evento e seus parâmetros.
 
-Cada entidade deve ter um ID única para evitar colisões com outras entidades. É bem comum que parâmetros de eventos incluam um identificador único a ser usado. Nota: usar o mesmo hash de transação como ID presume que nenhum outro evento na mesma transação criará entidades a usar este hash como o ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Como carregar entidades a partir do armazenamento
 
@@ -268,15 +273,18 @@ if (transfer == null) {
 // Use a entidade Transfer como antes
 ```
 
-Como a entidade pode ainda não existir no armazenamento, o método `load` retorna um valor de tipo `Transfer | null`. Portanto, é bom prestar atenção ao caso `null` antes de usar o valor.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Nota:** Só é necessário carregar entidades se as mudanças feitas no mapeamento dependem dos dados anteriores de uma entidade. Veja a próxima seção para ver as duas maneiras de atualizar entidades existentes.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Como consultar entidades criadas dentro de um bloco
 
 Desde o `graph-node` v0.31.0, o `@graphprotocol/graph-ts` v0.30.0 e o `@graphprotocol/graph-cli v0.49.0`, o método `loadInBlock` está disponível em todos os tipos de entidade.
 
-A API do armazenamento facilita o resgate de entidades que foram criadas ou atualizadas no bloco atual. Um caso comum: um handler cria uma Transação de algum evento on-chain, e um handler seguinte quer acessar esta transação caso ela exista. Se a transação não existe, o subgraph deve acessar o banco de dados para descobrir que a entidade não existe; se o autor do subgraph já souber que a entidade deve ter sido criada no mesmo bloco, o uso do loadInBlock evita esta volta pelo banco de dados. Para alguns subgraphs, estas consultas perdidas podem contribuir muito para o tempo de indexação.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // ou como a ID for construída
@@ -503,7 +511,9 @@ Qualquer outro contrato que seja parte do subgraph pode ser importado do código
 
 #### Como Lidar com Chamadas Revertidas
 
-Se os métodos de apenas-leitura do seu contrato forem revertidos, chame o método do contrato gerado prefixado com `try_`. Por exemplo, o contrato do Gravity expõe o método `gravatarToOwner`. Este código poderia lidar com uma reversão naquele método:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +525,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note que um Graph Node conectado a um cliente Geth ou Infura pode não detectar todas as reversões; se depender disto, recomendamos usar um Graph Node conectado a um cliente Parity.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### ABI de Codificação/Decodificação
 
@@ -761,44 +771,44 @@ Quando o tipo de um valor é confirmado, ele pode ser convertido num [tipo embut
 
 ### Referência de Conversões de Tipos
 
-| Fonte(s)             | Destino              | Função de conversão          |
-| -------------------- | -------------------- | ---------------------------- |
-| Address              | Bytes                | nenhum                       |
-| Address              | String               | s.toHexString()              |
-| BigDecimal           | String               | s.toString()                 |
-| BigInt               | BigDecimal           | s.toBigDecimal()             |
-| BigInt               | String (hexadecimal) | s.toHexString() ou s.toHex() |
-| BigInt               | String (unicode)     | s.toString()                 |
-| BigInt               | i32                  | s.toI32()                    |
-| Boolean              | Boolean              | nenhum                       |
-| Bytes (assinado)     | BigInt               | BigInt.fromSignedBytes(s)    |
-| Bytes (não assinado) | BigInt               | BigInt.fromUnsignedBytes(s)  |
-| Bytes                | String (hexadecimal) | s.toHexString() ou s.toHex() |
-| Bytes                | String (unicode)     | s.toString()                 |
-| Bytes                | String (base58)      | s.toBase58()                 |
-| Bytes                | i32                  | s.toI32()                    |
-| Bytes                | u32                  | s.toU32()                    |
-| Bytes                | JSON                 | json.fromBytes(s)            |
-| int8                 | i32                  | nenhum                       |
-| int32                | i32                  | nenhum                       |
-| int32                | BigInt               | BigInt.fromI32(s)            |
-| uint24               | i32                  | nenhum                       |
-| int64 - int256       | BigInt               | nenhum                       |
-| uint32 - uint256     | BigInt               | nenhum                       |
-| JSON                 | boolean              | s.toBool()                   |
-| JSON                 | i64                  | s.toI64()                    |
-| JSON                 | u64                  | s.toU64()                    |
-| JSON                 | f64                  | s.toF64()                    |
-| JSON                 | BigInt               | s.toBigInt()                 |
-| JSON                 | string               | s.toString()                 |
-| JSON                 | Array                | s.toArray()                  |
-| JSON                 | Object               | s.toObject()                 |
-| String               | Address              | Address.fromString(s)        |
-| Bytes                | Address              | Address.fromBytes(s)         |
-| String               | BigInt               | BigInt.fromString(s)         |
-| String               | BigDecimal           | BigDecimal.fromString(s)     |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
+| Fonte(s)                 | Destino              | Função de conversão            |
+| ------------------------ | -------------------- | ------------------------------ |
+| Address                  | Bytes                | nenhum                         |
+| Address                  | String               | s.toHexString()                |
+| BigDecimal               | String               | s.toString()                   |
+| BigInt                   | BigDecimal           | s.toBigDecimal()               |
+| BigInt                   | String (hexadecimal) | s.toHexString() ou s.toHex()   |
+| BigInt                   | String (unicode)     | s.toString()                   |
+| BigInt                   | i32                  | s.toI32()                      |
+| Boolean                  | Boolean              | nenhum                         |
+| Bytes (assinado)         | BigInt               | BigInt.fromSignedBytes(s)      |
+| Bytes (não assinado)     | BigInt               | BigInt.fromUnsignedBytes(s)    |
+| Bytes                    | String (hexadecimal) | s.toHexString() ou s.toHex()   |
+| Bytes                    | String (unicode)     | s.toString()                   |
+| Bytes                    | String (base58)      | s.toBase58()                   |
+| Bytes                    | i32                  | s.toI32()                      |
+| Bytes                    | u32                  | s.toU32()                      |
+| Bytes                    | JSON                 | json.fromBytes(s)              |
+| int8                     | i32                  | nenhum                         |
+| int32                    | i32                  | nenhum                         |
+| int32                    | BigInt               | BigInt.fromI32(s)              |
+| uint24                   | i32                  | nenhum                         |
+| int64 - int256           | BigInt               | nenhum                         |
+| uint32 - uint256         | BigInt               | nenhum                         |
+| JSON                     | boolean              | s.toBool()                     |
+| JSON                     | i64                  | s.toI64()                      |
+| JSON                     | u64                  | s.toU64()                      |
+| JSON                     | f64                  | s.toF64()                      |
+| JSON                     | BigInt               | s.toBigInt()                   |
+| JSON                     | string               | s.toString()                   |
+| JSON                     | Array                | s.toArray()                    |
+| JSON                     | Object               | s.toObject()                   |
+| String                   | Address              | Address.fromString(s)          |
+| Bytes                    | Address              | Address.fromBytes(s)           |
+| String                   | BigInt               | BigInt.fromString(s)           |
+| String                   | BigDecimal           | BigDecimal.fromString(s)       |
+| String (hexadecimal)     | Bytes                | ByteArray.fromHexString(s)     |
+| String (UTF-8)           | Bytes                | ByteArray.fromUTF8(s)          |
 
 ### Metadados de Fontes de Dados
 

From 64adadde7d65ebb99953e1a9c8c150c09ee21337 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:05 -0500
Subject: [PATCH 0273/1325] New translations api.mdx (Swedish)

---
 website/pages/sv/developing/graph-ts/api.mdx | 195 ++++++++++---------
 1 file changed, 107 insertions(+), 88 deletions(-)

diff --git a/website/pages/sv/developing/graph-ts/api.mdx b/website/pages/sv/developing/graph-ts/api.mdx
index 227b7f3ee2bc..2dbb19d8f5cf 100644
--- a/website/pages/sv/developing/graph-ts/api.mdx
+++ b/website/pages/sv/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: API för AssemblyScript
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-Denna sida dokumenterar vilka inbyggda API: er som kan användas när man skriver mappningar av undergrafer. Två typer av API: er är tillgängliga från start:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API-referens
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Versionsanteckningar |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Versionsanteckningar                                                                                                                                                                                                                          |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Inbyggda typer
 
@@ -161,7 +163,7 @@ _Math_
 #### TypedMap
 
 ```typescript
-import { TypedMap } from '@graphprotocol/graph-ts'
+import { TypedMap } from "@graphprotocol/graph-ts";
 ```
 
 `TypedMap` can be used to store key-value pairs. See [this example](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
@@ -177,7 +179,7 @@ The `TypedMap` class has the following API:
 #### Bytes
 
 ```typescript
-import { Bytes } from '@graphprotocol/graph-ts'
+import { Bytes } from "@graphprotocol/graph-ts";
 ```
 
 `Bytes` is used to represent arbitrary-length arrays of bytes. This includes Ethereum values of type `bytes`, `bytes32`, etc.
@@ -203,7 +205,7 @@ _Operators_
 #### Address
 
 ```typescript
-import { Address } from '@graphprotocol/graph-ts'
+import { Address } from "@graphprotocol/graph-ts";
 ```
 
 `Address` extends `Bytes` to represent Ethereum `address` values.
@@ -216,7 +218,7 @@ It adds the following method on top of the `Bytes` API:
 ### Store API
 
 ```typescript
-import { store } from '@graphprotocol/graph-ts'
+import { store } from "@graphprotocol/graph-ts";
 ```
 
 The `store` API allows to load, save and remove entities from and to the Graph Node store.
@@ -229,60 +231,65 @@ Följande är ett vanligt mönster för att skapa entiteter från Ethereum-händ
 
 ```typescript
 // Importera händelseklassen Transfer som genererats från ERC20 ABI
-import { Transfer as TransferEvent } from '../generated/ERC20/ERC20'
+import { Transfer as TransferEvent } from "../generated/ERC20/ERC20";
 
 // Importera entitetstypen Transfer som genererats från GraphQL-schemat
-import { Transfer } from '../generated/schema'
+import { Transfer } from "../generated/schema";
 
 // Händelsehanterare för överföring
 export function handleTransfer(event: TransferEvent): void {
   // Skapa en Transfer-entitet, med transaktionshash som enhets-ID
-  let id = event.transaction.hash
-  let transfer = new Transfer(id)
+  let id = event.transaction.hash;
+  let transfer = new Transfer(id);
 
   // Ange egenskaper för entiteten med hjälp av händelseparametrarna
-  transfer.from = event.params.from
-  transfer.to = event.params.to
-  transfer.amount = event.params.amount
+  transfer.from = event.params.from;
+  transfer.to = event.params.to;
+  transfer.amount = event.params.amount;
 
   // Spara entiteten till lagret
-  transfer.save()
+  transfer.save();
 }
 ```
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Varje entitet måste ha en unik ID för att undvika kollisioner med andra entiteter. Det är ganska vanligt att händelsens parametrar inkluderar en unik identifierare som kan användas. Observera: Att använda transaktionshashen som ID förutsätter att inga andra händelser i samma transaktion skapar entiteter med denna hash som ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Ladda entiteter från lagret
 
 Om en entitet redan finns kan den laddas från lagret med följande:
 
 ```typescript
-let id = event.transaction.hash // eller hur ID konstrueras
-let transfer = Transfer.load(id)
+let id = event.transaction.hash; // eller hur ID konstrueras
+let transfer = Transfer.load(id);
 if (transfer == null) {
-  transfer = new Transfer(id)
+  transfer = new Transfer(id);
 }
 
 // Använd överföringsenheten som tidigare
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Sökning av entiteter skapade inom ett block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-API:et för lagret underlättar hämtningen av entiteter som skapades eller uppdaterades i det aktuella blocket. En vanlig situation för detta är att en hanterare skapar en transaktion från någon händelse på kedjan, och en senare hanterare vill komma åt denna transaktion om den finns. I det fall då transaktionen inte finns, måste subgraphen gå till databasen bara för att ta reda på att entiteten inte finns; om subgraphförfattaren redan vet att entiteten måste ha skapats i samma block, undviker man detta databasbesök genom att använda <code>loadInBlock</code>. För vissa subgrapher kan dessa missade sökningar bidra avsevärt till indexeringstiden.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
-let id = event.transaction.hash // eller hur ID konstrueras
-let transfer = Transfer.loadInBlock(id)
+let id = event.transaction.hash; // eller hur ID konstrueras
+let transfer = Transfer.loadInBlock(id);
 if (transfer == null) {
-  transfer = new Transfer(id)
+  transfer = new Transfer(id);
 }
 
 // Använd överföringsenheten som tidigare
@@ -336,7 +343,7 @@ transfer.amount = ...
 Det är också möjligt att avaktivera egenskaper med en av följande två instruktioner:
 
 ```typescript
-transfer.from.unset()
+transfer.from.unset();
 transfer.from = null
 ```
 
@@ -346,14 +353,14 @@ Updating array properties is a little more involved, as the getting an array fro
 
 ```typescript
 // Detta kommer inte att fungera
-entity.numbers.push(BigInt.fromI32(1))
-entity.save()
+entity.numbers.push(BigInt.fromI32(1));
+entity.save();
 
 // Detta kommer att fungera
-let numbers = entity.numbers
-numbers.push(BigInt.fromI32(1))
-entity.numbers = numbers
-entity.save()
+let numbers = entity.numbers;
+numbers.push(BigInt.fromI32(1));
+entity.numbers = numbers;
+entity.save();
 ```
 
 #### Ta bort entiteter från lagret
@@ -391,12 +398,12 @@ type Transfer @entity {
 and a `Transfer(address,address,uint256)` event signature on Ethereum, the `from`, `to` and `amount` values of type `address`, `address` and `uint256` are converted to `Address` and `BigInt`, allowing them to be passed on to the `Bytes!` and `BigInt!` properties of the `Transfer` entity:
 
 ```typescript
-let id = event.transaction.hash
-let transfer = new Transfer(id)
-transfer.from = event.params.from
-transfer.to = event.params.to
-transfer.amount = event.params.amount
-transfer.save()
+let id = event.transaction.hash;
+let transfer = new Transfer(id);
+transfer.from = event.params.from;
+transfer.to = event.params.to;
+transfer.amount = event.params.amount;
+transfer.save();
 ```
 
 #### Händelser och Block/Transaktionsdata
@@ -482,16 +489,19 @@ En vanlig mönster är att komma åt kontraktet från vilket en händelse härst
 
 ```typescript
 // Importera den genererade kontraktsklassen och den genererade klassen för överföringshändelser
-import { ERC20Contract, Transfer as TransferEvent } from '../generated/ERC20Contract/ERC20Contract'
+import {
+  ERC20Contract,
+  Transfer as TransferEvent,
+} from "../generated/ERC20Contract/ERC20Contract";
 // Importera den genererade entitetsklassen
-import { Transfer } from '../generated/schema'
+import { Transfer } from "../generated/schema";
 
 export function handleTransfer(event: TransferEvent) {
   // Bind kontraktet till den adress som skickade händelsen
-  let contract = ERC20Contract.bind(event.address)
+  let contract = ERC20Contract.bind(event.address);
 
   // Åtkomst till tillståndsvariabler och funktioner genom att anropa dem
-  let erc20Symbol = contract.symbol()
+  let erc20Symbol = contract.symbol();
 }
 ```
 
@@ -503,19 +513,21 @@ Andra kontrakt som är en del av subgraphen kan importeras från den genererade
 
 #### Hantering av återkallade anrop
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
-let gravitera = gravitera.bind(event.address)
-let callResult = gravitera_gravatarToOwner(gravatar)
+let gravitera = gravitera.bind(event.address);
+let callResult = gravitera_gravatarToOwner(gravatar);
 if (callResult.reverted) {
-  log.info('getGravatar reverted', [])
+  log.info("getGravatar reverted", []);
 } else {
-  let owner = callResult.value
+  let owner = callResult.value;
 }
 ```
 
-Observera att en Graf-nod ansluten till en Geth eller Infura klient kanske inte upptäcker alla återkallade anrop. Om du förlitar dig på detta rekommenderar vi att du använder en Graph nod som är ansluten till en Parity klient.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Kodning/Dekodning av ABI
 
@@ -570,7 +582,7 @@ let isContract = ethereum.hasCode(eoa).inner // returns false
 ### API för loggning
 
 ```typescript
-import { log } from '@graphprotocol/graph-ts'
+import { log } from "@graphprotocol/graph-ts";
 ```
 
 The `log` API allows subgraphs to log information to the Graph Node standard output as well as Graph Explorer. Messages can be logged using different log levels. A basic format string syntax is provided to compose log messages from argument.
@@ -586,7 +598,11 @@ The `log` API includes the following functions:
 The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
 
 ```typescript
-log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.toString(), 'already a string'])
+log.info("Message to be displayed: {}, {}, {}", [
+  value.toString(),
+  anotherValue.toString(),
+  "already a string",
+]);
 ```
 
 #### Loggning av ett eller flera värden
@@ -609,11 +625,11 @@ export function handleSomeEvent(event: SomeEvent): void {
 I exemplet nedan loggas endast det första värdet i argument arrayen, trots att arrayen innehåller tre värden.
 
 ```typescript
-let myArray = ['A', 'B', 'C']
+let myArray = ["A", "B", "C"];
 
 export function handleSomeEvent(event: SomeEvent): void {
   // Visar : "Mitt värde är: A" (Även om tre värden skickas till `log.info`)
-  log.info('Mitt värde är: {}', myArray)
+  log.info("Mitt värde är: {}", myArray);
 }
 ```
 
@@ -622,11 +638,14 @@ export function handleSomeEvent(event: SomeEvent): void {
 Each entry in the arguments array requires its own placeholder `{}` in the log message string. The below example contains three placeholders `{}` in the log message. Because of this, all three values in `myArray` are logged.
 
 ```typescript
-let myArray = ['A', 'B', 'C']
+let myArray = ["A", "B", "C"];
 
 export function handleSomeEvent(event: SomeEvent): void {
   // Visar: "Mitt första värde är: A, andra värdet är: B, tredje värdet är: C"
-  log.info('My first value is: {}, second value is: {}, third value is: {}', myArray)
+  log.info(
+    "My first value is: {}, second value is: {}, third value is: {}",
+    myArray
+  );
 }
 ```
 
@@ -637,7 +656,7 @@ För att visa ett specifikt värde i arrayen måste det indexeras och tillhandah
 ```typescript
 export function handleSomeEvent(event: SomeEvent): void {
   // Visar : "Mitt tredje värde är C"
-  log.info('My third value is: {}', [myArray[2]])
+  log.info("My third value is: {}", [myArray[2]]);
 }
 ```
 
@@ -646,21 +665,21 @@ export function handleSomeEvent(event: SomeEvent): void {
 I exemplet nedan loggas blocknummer, blockhash och transaktionshash från en händelse:
 
 ```typescript
-import { log } from '@graphprotocol/graph-ts'
+import { log } from "@graphprotocol/graph-ts";
 
 export function handleSomeEvent(event: SomeEvent): void {
-  log.debug('Block number: {}, block hash: {}, transaction hash: {}', [
+  log.debug("Block number: {}, block hash: {}, transaction hash: {}", [
     event.block.number.toString(), // "47596000"
     event.block.hash.toHexString(), // "0x..."
     event.transaction.hash.toHexString(), // "0x..."
-  ])
+  ]);
 }
 ```
 
 ### IPFS API
 
 ```typescript
-import { ipfs } from '@graphprotocol/graph-ts'
+import { ipfs } from "@graphprotocol/graph-ts"
 ```
 
 Smart contracts occasionally anchor IPFS files on chain. This allows mappings to obtain the IPFS hashes from the contract and read the corresponding files from IPFS. The file data will be returned as `Bytes`, which usually requires further processing, e.g. with the `json` API documented later on this page.
@@ -669,13 +688,13 @@ För att läsa en fil från IPFS med en given IPFS-hash eller sökväg görs fö
 
 ```typescript
 // Placera detta i en händelsehanterare i mappningen
-let hash = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D'
-let data = ipfs.cat(hash)
+let hash = "QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D";
+let data = ipfs.cat(hash);
 
 // Sökvägar som `QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile`
 // som inkluderar filer i kataloger stöds också
-let path = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile'
-let data = ipfs.cat(path)
+let path = "QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile";
+let data = ipfs.cat(path);
 ```
 
 **Note:** `ipfs.cat` is not deterministic at the moment. If the file cannot be retrieved over the IPFS network before the request times out, it will return `null`. Due to this, it's always worth checking the result for `null`.
@@ -683,31 +702,31 @@ let data = ipfs.cat(path)
 It is also possible to process larger files in a streaming fashion with `ipfs.map`. The function expects the hash or path for an IPFS file, the name of a callback, and flags to modify its behavior:
 
 ```typescript
-import { JSONValue, Value } from '@graphprotocol/graph-ts'
+import { JSONValue, Value } from "@graphprotocol/graph-ts";
 
 export function processItem(value: JSONValue, userData: Value): void {
   // Se JSONValue-dokumentationen för mer information om hur man hanterar
   // med JSON-värden
-  let obj = value.toObject()
-  let id = obj.get('id')
-  let title = obj.get('title')
+  let obj = value.toObject();
+  let id = obj.get("id");
+  let title = obj.get("title");
 
   if (!id || !title) {
-    return
+    return;
   }
 
   // Callbacks kan också skapa enheter
-  let newItem = new Item(id)
-  newItem.title = title.toString()
-  newitem.parent = userData.toString() // Ange parent till "parentId"
-  newitem.save()
+  let newItem = new Item(id);
+  newItem.title = title.toString();
+  newitem.parent = userData.toString(); // Ange parent till "parentId"
+  newitem.save();
 }
 
 // Placera detta i en händelsehanterare i mappningen
-ipfs.map('Qm...', 'processItem', Value.fromString('parentId'), ['json'])
+ipfs.map("Qm...", "processItem", Value.fromString("parentId"), ["json"]);
 
 // Alternativt kan du använda `ipfs.mapJSON`.
-ipfs.mapJSON('Qm...', 'processItem', Value.fromString('parentId'))
+ipfs.mapJSON("Qm...", "processItem", Value.fromString("parentId"));
 ```
 
 The only flag currently supported is `json`, which must be passed to `ipfs.map`. With the `json` flag, the IPFS file must consist of a series of JSON values, one value per line. The call to `ipfs.map` will read each line in the file, deserialize it into a `JSONValue` and call the callback for each of them. The callback can then use entity operations to store data from the `JSONValue`. Entity changes are stored only when the handler that called `ipfs.map` finishes successfully; in the meantime, they are kept in memory, and the size of the file that `ipfs.map` can process is therefore limited.
@@ -717,7 +736,7 @@ On success, `ipfs.map` returns `void`. If any invocation of the callback causes
 ### Crypto API
 
 ```typescript
-import { crypto } from '@graphprotocol/graph-ts'
+import { crypto } from "@graphprotocol/graph-ts";
 ```
 
 The `crypto` API makes a cryptographic functions available for use in mappings. Right now, there is only one:
@@ -727,7 +746,7 @@ The `crypto` API makes a cryptographic functions available for use in mappings.
 ### JSON API
 
 ```typescript
-import { json, JSONValueKind } from '@graphprotocol/graph-ts'
+import { json, JSONValueKind } from "@graphprotocol/graph-ts"
 ```
 
 JSON data can be parsed using the `json` API:

From abb2a8351a8c692a519ea211cd146ddfb176835e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:07 -0500
Subject: [PATCH 0274/1325] New translations subgraphs.mdx (Polish)

---
 website/pages/pl/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/pl/subgraphs.mdx b/website/pages/pl/subgraphs.mdx
index 27b452211477..614577e46fb0 100644
--- a/website/pages/pl/subgraphs.mdx
+++ b/website/pages/pl/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Subgrafy
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 3aa8818b06327d33b222b37968e94f378f2b662b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:08 -0500
Subject: [PATCH 0275/1325] New translations transfer-to-the-graph.mdx (Polish)

---
 website/pages/pl/cookbook/transfer-to-the-graph.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/pl/cookbook/transfer-to-the-graph.mdx b/website/pages/pl/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..6a5d2c2793f3 100644
--- a/website/pages/pl/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/pl/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 

From c201fce9f1b604682015b2a52339cafd94155c38 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:09 -0500
Subject: [PATCH 0276/1325] New translations advanced.mdx (Polish)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/pl/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/pl/developing/creating-a-subgraph/advanced.mdx b/website/pages/pl/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..3a08ddab7066
--- /dev/null
+++ b/website/pages/pl/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From aa849aa9b259d4eb892d7a7220f0e9bdf29c717d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:10 -0500
Subject: [PATCH 0277/1325] New translations assemblyscript-mappings.mdx
 (Polish)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/pl/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/pl/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/pl/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/pl/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From c2a8525a42aace639a644ecf6bac761a0ef58ca5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:12 -0500
Subject: [PATCH 0278/1325] New translations install-the-cli.mdx (Polish)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..5665b2730198
--- /dev/null
+++ b/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Jak stworzyć subgraf
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From b648b24c729803c51e9428546ed64a1c5ca12df5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:13 -0500
Subject: [PATCH 0279/1325] New translations ql-schema.mdx (Polish)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From 4cf8fb9042c08b3499d0ca73fb2b59f1a1eccb56 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:14 -0500
Subject: [PATCH 0280/1325] New translations subgraph-manifest.mdx (Polish)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/pl/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/pl/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/pl/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..f282f3946e75
--- /dev/null
+++ b/website/pages/pl/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 404d89e9ed0ac38874d8d1bd9523f3b902094448 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:15 -0500
Subject: [PATCH 0281/1325] New translations subgraphs.mdx (Portuguese)

---
 website/pages/pt/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/pt/subgraphs.mdx b/website/pages/pt/subgraphs.mdx
index 27b452211477..5ca8d4007ec4 100644
--- a/website/pages/pt/subgraphs.mdx
+++ b/website/pages/pt/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Ciclo de Vida de um Subgraph
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 34705abe2a1255bee68f577c98d4919f846ea263 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:16 -0500
Subject: [PATCH 0282/1325] New translations transfer-to-the-graph.mdx
 (Portuguese)

---
 .../pages/pt/cookbook/transfer-to-the-graph.mdx  | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/pt/cookbook/transfer-to-the-graph.mdx b/website/pages/pt/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..7d0d8cda34c4 100644
--- a/website/pages/pt/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/pt/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -31,7 +31,7 @@ You must have [Node.js](https://nodejs.org/) and a package manager of your choic
 
 On your local machine, run the following command:
 
-Using [npm](https://www.npmjs.com/):
+Uso de [npm](https://www.npmjs.com/):
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Exemplo
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Outros Recursos
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From af4417f9eb0a385c6e7badf2fb031fddf18fa9de Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:18 -0500
Subject: [PATCH 0283/1325] New translations advanced.mdx (Portuguese)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/pt/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/pt/developing/creating-a-subgraph/advanced.mdx b/website/pages/pt/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..a46badf10977
--- /dev/null
+++ b/website/pages/pt/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Visão geral
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Séries de Tempo e Agregações
+
+Séries de tempo e agregações permitem que o seu subgraph registre estatísticas como médias diárias de preço, total de transferências por hora, etc.
+
+Este recurso introduz dois novos tipos de entidade de subgraph. Entidades de série de tempo registram pontos de dados com marcações de tempo. Entidades de agregação realizam cálculos pré-declarados nos pontos de dados de Séries de Tempo numa base por hora ou diária, e depois armazenam os resultados para acesso fácil via GraphQL.
+
+### Exemplo de Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Definição de Série de Tempo e Agregações
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Intervalos de Agregação Disponíveis
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Funções de Agregação Disponíveis
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Exemplo de Query de Agregações
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Nota:
+
+Para utilizar Séries de Tempo e Agregações, um subgraph deve ter uma versão de especificação maior que 1.1.0. Note que este recurso pode passar por mudanças significativas que podem afetar a retrocompatibilidade.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Erros não-fatais
+
+Erros de indexação em subgraphs já sincronizados, por si próprios, farão que o subgraph falhe e pare de sincronizar. Os subgraphs podem, de outra forma, ser configurados a continuar a sincronizar na presença de erros, ao ignorar as mudanças feitas pelo handler que provocaram o erro. Isto dá tempo aos autores de subgraphs para corrigir seus subgraphs enquanto queries continuam a ser servidos perante o bloco mais recente, porém os resultados podem ser inconsistentes devido ao bug que causou o erro. Note que alguns erros ainda são sempre fatais. Para ser não-fatais, os erros devem ser confirmados como determinísticos.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Permitir erros não fatais exige a configuração da seguinte feature flag no manifest do subgraph:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## Fontes de Dados de Arquivos em IPFS/Arweave
+
+Fontes de dados de arquivos são uma nova funcionalidade de subgraph para acessar dados off-chain de forma robusta e extensível. As fontes de dados de arquivos apoiam o retiro de arquivos do IPFS e do Arweave.
+
+> Isto também abre as portas para indexar dados off-chain de forma determinística, além de potencialmente introduzir dados arbitrários com fonte em HTTP.
+
+### Visão geral
+
+Em vez de buscar arquivos "em fila" durante a execução do handler, isto introduz modelos que podem ser colocados como novas fontes de dados para um identificador de arquivos. Estas novas fontes de dados pegam os arquivos e tentam novamente caso não obtenham êxito; quando o arquivo é encontrado, executam um handler dedicado.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Guia de atualização
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Adicionar um novo tipo de entidade que será atualizado quando os arquivos forem encontrados
+
+Fontes de dados de arquivos não podem acessar ou atualizar entidades baseadas em chain, mas devem atualizar entidades específicas a arquivos.
+
+Isto pode implicar separar campos de entidades existentes em entidades separadas, ligadas juntas.
+
+Entidade combinada original:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Entidade nova, separada:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Se o relacionamento for perfeitamente proporcional entre a entidade parente e a entidade de fontes de dados de arquivos resultante, é mais simples ligar a entidade parente a uma entidade de arquivos resultante, com a CID IPFS como o assunto de busca. Se tiver dificuldades em modelar suas novas entidades baseadas em arquivos, pergunte no Discord!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Esta é a fonte de dados que será gerada quando um arquivo de interesse for identificado.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Criar um novo handler para processar arquivos
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Exemplo de handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Gerar fontes de dados de arquivos quando for obrigatório
+
+Agora pode criar fontes de dados de arquivos durante a execução de handlers baseados em chain:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Exemplo:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//Este exemplo de código é para um subgraph do Crypto Coven. O hash ipfs acima é um diretório com metadados de tokens para todos os NFTs do Crypto Coven.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //Isto cria um caminho aos metadados para um único NFT do Crypto Coven. Ele concatena o diretório com "/" + nome do arquivo + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+Isto criará uma fonte de dados de arquivos, que avaliará o endpoint de IPFS ou Arweave configurado do Graph Node, e tentará novamente caso não achá-lo. Com o arquivo localizado, o handler da fonte de dados de arquivos será executado.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Parabéns, você está a usar fontes de dados de arquivos!
+
+#### Como lançar os seus Subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitações
+
+Handlers e entidades de fontes de dados de arquivos são isolados de outras entidades de subgraph, o que garante que sejam determinísticos quando executados e que não haja contaminação de fontes de dados baseadas em chain. Especificamente:
+
+- Entidades criadas por Fontes de Dados de Arquivos são imutáveis, e não podem ser atualizadas
+- Handlers de Fontes de Dados de Arquivos não podem acessar entidades de outras fontes de dados de arquivos
+- Entidades associadas com Fontes de Dados de Arquivos não podem ser acessadas por handlers baseados em chain
+
+> Enquanto esta limitação pode não ser problemática para a maioria dos casos de uso, ela pode deixar alguns mais complexos. Se houver qualquer problema neste processo, por favor dê um alô via Discord!
+
+Além disto, não é possível criar fontes de dados de uma fonte de dado de arquivos, seja uma on-chain ou outra fonte de dados de arquivos. Esta restrição poderá ser retirada no futuro.
+
+#### Boas práticas
+
+Caso ligue metadados de NFTs a tokens correspondentes, use o hash IPFS destes para referenciar uma entidade de Metadados da entidade do Token. Salve a entidade de Metadados a usar o hash IPFS como ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Estamos a melhorar a recomendação acima, para que os queries retornem apenas a versão "mais recente"
+
+#### Problemas conhecidos
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Exemplos
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Referências
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Filtros de Argumentos Indexados / Filtros de Tópicos
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Filtros de tópico, também conhecidos como filtros de argumentos indexados, permitem que os utilizadores filtrem eventos de blockchain com alta precisão, em base nos valores dos seus argumentos indexados.
+
+- Estes filtros ajudam a isolar eventos específicos de interesse do fluxo vasto de eventos na blockchain, o que permite que subgraphs operem com mais eficácia ao focarem apenas em dados relevantes.
+
+- Isto serve para criar subgraphs pessoais que rastreiam endereços específicos e as suas interações com vários contratos inteligentes na blockchain.
+
+### Como Filtros de Tópicos Funcionam
+
+Quando um contrato inteligente emite um evento, quaisquer argumentos que forem marcados como indexados podem ser usados como filtros no manifest de um subgraph. Isto permite que o subgraph preste atenção seletiva para eventos que correspondam a estes argumentos indexados.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Declaração de evento com parâmetros indexados para endereços
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Função para simular a transferência de tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+Neste exemplo:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuração em Subgraphs
+
+Filtros de tópicos são definidos diretamente na configuração de handlers de eventos no manifest do subgraph. Veja como eles são configurados:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+Neste cenário:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Cada tópico pode ter um ou mais valores, e um evento só é processado se corresponder a um dos valores em cada tópico especificado.
+
+#### Lógica de Filtro
+
+- Dentro de um Tópico Único: A lógica funciona como uma condição OR. O evento será processado se corresponder a qualquer dos valores listados num tópico.
+- Entre Tópicos Diferentes: A lógica funciona como uma condição AND. Um evento deve atender a todas as condições especificadas em vários tópicos para acionar o handler associado.
+
+#### Exemplo 1: Como Rastrear Transferências Diretas do Endereço A ao Endereço B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+Nesta configuração:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Exemplo 2: Como Rastrear Transações em Qualquer Direção Entre Dois ou Mais Endereços
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Endereço do Remetente
+    topic2: ['0xAddressB', '0xAddressC'] # Endereço do Destinatário
+```
+
+Nesta configuração:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- O subgraph indexará transações que ocorrerem em qualquer direção entre vários endereços, o que permite a monitoria compreensiva de interações que envolverem todos os endereços.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+Esta ferramenta faz o seguinte:
+
+- Aumenta muito o desempenho do retiro de dados da blockchain Ethereum ao reduzir o tempo total para múltiplas chamadas e otimizar a eficácia geral do subgraph.
+- Permite retiros de dados mais rápidos, o que resulta em respostas de query aceleradas e uma experiência de utilizador melhorada.
+- Reduz tempos de espera para aplicativos que precisam agregar dados de várias chamadas no Ethereum, o que aumenta a eficácia do processo de retiro de dados.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Execução Paralela: Ao invés de esperar o término de uma chamada para começar a próxima, várias chamadas podem ser iniciadas simultaneamente.
+- Eficácia de Tempo: O total de tempo levado para todas as chamadas muda da soma dos tempos de chamadas individuais (sequencial) para o tempo levado para a chamada mais longa (paralelo).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagina que tens um subgraph que precisa fazer três chamadas no Ethereum para retirar dados sobre as transações, o saldo e as posses de token de um utilizador.
+
+Tradicionalmente, estas chamadas podem ser realizadas em sequência:
+
+1. Chamada 1 (Transações): Leva 3 segundos
+2. Chamada 2 (Saldo): Leva 2 segundos
+3. Chamada 3 (Posses de Token): Leva 4 segundos
+
+Total de tempo: 3 + 2 + 4 = 9 segundos
+
+#### Scenario with Declarative `eth_calls`
+
+Com esta ferramenta, é possível declarar que estas chamadas sejam executadas em paralelo:
+
+1. Chamada 1 (Transações): Leva 3 segundos
+2. Chamada 2 (Saldo): Leva 2 segundos
+3. Chamada 3 (Posses de Token): Leva 4 segundos
+
+Como estas chamadas são executadas em paralelo, o total de tempo é igual ao tempo gasto pela chamada mais longa.
+
+Total de tempo = max (3, 2, 4) = 4 segundos
+
+#### How it Works
+
+1. Definição Declarativa: No manifest do subgraph, as chamadas no Ethereum são declaradas de maneira que indique que elas possam ser executadas em paralelo.
+2. Motor de Execução Paralela: O motor de execução do Graph Node reconhece estas declarações e executa as chamadas simultaneamente.
+3. Agregação de Resultado: Quando todas as chamadas forem completadas, os resultados são agregados e usados pelo subgraph para mais processos.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Detalhes para o exemplo acima:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Como Enxertar em Subgraphs Existentes
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # ID do subgraph base
+  block: 7345624 # Número do bloco
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Como o enxerto copia em vez de indexar dados base, dirigir o subgraph para o bloco desejado desta maneira é mais rápido que indexar do começo, mesmo que a cópia inicial dos dados ainda possa levar várias horas para subgraphs muito grandes. Enquanto o subgraph enxertado é inicializado, o Graph Node gravará informações sobre os tipos de entidade que já foram copiados.
+
+O subgraph enxertado pode usar um schema GraphQL que não é idêntico ao schema do subgraph base, mas é apenas compatível com ele. Ele deve ser um schema válido no seu próprio mérito, mas pode desviar do schema do subgraph base nas seguintes maneiras:
+
+- Ele adiciona ou remove tipos de entidade
+- Ele retira atributos de tipos de identidade
+- Ele adiciona atributos anuláveis a tipos de entidade
+- Ele transforma atributos não anuláveis em atributos anuláveis
+- Ele adiciona valores a enums
+- Ele adiciona ou remove interfaces
+- Ele muda para quais tipos de entidades uma interface é implementada
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 825c47a0d1fe2b1fbae9aea2a14de3a5f7092a77 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:19 -0500
Subject: [PATCH 0284/1325] New translations assemblyscript-mappings.mdx
 (Portuguese)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/pt/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/pt/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/pt/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..e7d972a9d0bf
--- /dev/null
+++ b/website/pages/pt/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Visão geral
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Como Escrever Mapeamentos
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### IDs Recomendadas para Criar Novas Entidades
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Gestão de entidades com IDs idênticas
+
+Ao criar e salvar uma nova entidade, se já houver uma com a mesma ID, vale sempre usar as propriedades da nova entidade durante o processo de fusão. Isto significa que a entidade existente será atualizada com os valores da entidade nova.
+
+Se um valor nulo for propositadamente determinado para um campo na nova entidade com a mesma ID, a entidade existente será atualizada com o valor nulo.
+
+Se nenhum valor for inserido para um campo na nova entidade com a mesma ID, o campo também resultará em nulo.
+
+## Geração de Código
+
+Para tornar mais fácil e seguro a tipos o trabalho com contratos inteligentes, eventos e entidades, o Graph CLI pode gerar tipos de AssemblyScript a partir do schema GraphQL do subgraph e das ABIs de contratos incluídas nas fontes de dados.
+
+Isto é feito com
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // Classe do contrato:
+  Gravity,
+  // Classes de eventos:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 553e73f1c83ea8728275975f0c46f33e3d1b3e58 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:20 -0500
Subject: [PATCH 0285/1325] New translations install-the-cli.mdx (Portuguese)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..aa88b936bbf8
--- /dev/null
+++ b/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Como instalar o Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Visão geral
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Como Começar
+
+### Como instalar o Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+Execute um dos seguintes comandos na sua máquina local:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Crie um Subgraph
+
+### De um Contrato Existente
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### De um Exemplo de Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Especificações
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+Os arquivos da ABI devem combinar com o(s) seu(s) contrato(s). Há algumas maneiras de obter estes arquivos:
+
+- Caso construa o seu próprio projeto, provavelmente terá acesso às suas ABIs mais recentes.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Versão | Notas de atualização                                                                                                                                                     |
+| :----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5 | Adicionado apoio a handlers de eventos com acesso a recibos de transação.                                                                                                |
+|  0.0.4 | Adicionado apoio à gestão de recursos de subgraph.                                                                                                                       |

From 7834a1c78aaa4d60d45b1f6599b306fc4e81a801 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:21 -0500
Subject: [PATCH 0286/1325] New translations ql-schema.mdx (Portuguese)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..592372b0de60
--- /dev/null
+++ b/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Visão geral
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Bom Exemplo
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Mau Exemplo
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Campos Opcionais e Obrigatórios
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Tipos Embutidos de Escalar
+
+#### Escalares Apoiados pelo GraphQL
+
+The following scalars are supported in the GraphQL API:
+
+| Tipo         | Descrição                                                                                                                                                                                                        |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Arranjo de bytes, representado como string hexadecimal. Usado frequentemente por hashes e endereços no Ethereum.                                                                                                 |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+Também pode criar enums dentro de um schema. Enums têm a seguinte sintaxe:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Relacionamentos de Entidades
+
+Uma entidade pode ter relacionamentos com uma ou mais entidades no seu schema; estes podem ser tratados nas suas consultas. Os relacionamentos no The Graph são unidirecionais, e é possível simular relacionamentos bidirecionais ao definir um relacionamento unidirecional em cada "lado" do relacionamento projetado.
+
+Relacionamentos são definidos em entidades como qualquer outro campo, sendo que o tipo especificado é o de outra entidade.
+
+#### Relacionamentos Um-com-Um
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Relacionamentos Um-com-Vários
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Buscas Reversas
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+Para relacionamentos um-com-vários, o relacionamento sempre deve ser armazenado no lado 'um', e o lado 'vários' deve sempre ser derivado. Armazenar o relacionamento desta maneira, em vez de armazenar um arranjo de entidades no lado 'vários', melhorará dramaticamente o desempenho para o indexing e os queries no subgraph. Em geral, evite armazenar arranjos de entidades enquanto for prático.
+
+#### Exemplo
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Relacionamentos Vários-com-Vários
+
+Para relacionamentos vários-com-vários, como um conjunto de utilizadores em que cada um pertence a qualquer número de organizações, o relacionamento é mais simplesmente — mas não mais eficientemente — modelado como um arranjo em cada uma das duas entidades envolvidas. Se o relacionamento for simétrico, apenas um lado do relacionamento precisa ser armazenado, e o outro lado pode ser derivado.
+
+#### Exemplo
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Esta abordagem requer que os queries desçam a um nível adicional para retirar, por exemplo, as organizações para utilizadores:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # isto é uma entidade UserOrganization
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Esta maneira mais elaborada de armazenar relacionamentos vários-com-vários armazenará menos dados para o subgraph, portanto, o subgraph ficará muito mais rápido de indexar e consultar.
+
+### Como adicionar comentários ao schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # identificador único e chave primária da entidade
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Como Definir Campos de Busca Fulltext
+
+Buscas fulltext filtram e ordenam entidades baseadas num texto inserido. Queries fulltext podem retornar resultados para palavras semelhantes ao processar o texto inserido antes de compará-los aos dados do texto indexado.
+
+Uma definição de query fulltext inclui: o nome do query, o dicionário do idioma usado para processar os campos de texto, o algoritmo de ordem usado para ordenar os resultados, e os campos incluídos na busca. Todo query fulltext pode ter vários campos, mas todos os campos incluídos devem ser de um único tipo de entidade.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Idiomas apoiados
+
+Escolher um idioma diferente terá um efeito definitivo, porém às vezes sutil, na API da busca fulltext. Campos cobertos por um campo de query fulltext serão examinados no contexto do idioma escolhido, para que os lexemas produzidos pela análise e pelos queries de busca variem de idioma para idioma. Por exemplo: ao usar o dicionário turco, "token" é abreviado para "toke" enquanto, claro, o dicionário em inglês o categorizará como "token".
+
+Dicionários apoiados:
+
+| Code   | Dicionário |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Português  |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Algoritmos de Ordem
+
+Algoritmos apoiados para a organização de resultados:
+
+| Algorithm     | Description                                                                       |
+| ------------- | --------------------------------------------------------------------------------- |
+| rank          | Organiza os resultados pela qualidade da correspondência (0-1) da busca fulltext. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                   |

From 52d3e36612bdd094fbef6d9a5953f6a5877d7015 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:22 -0500
Subject: [PATCH 0287/1325] New translations subgraph-manifest.mdx (Portuguese)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/pt/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/pt/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/pt/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..e56c0a59dba8
--- /dev/null
+++ b/website/pages/pt/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Visão geral
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+As entradas importantes para atualizar para o manifest são:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Handlers de Eventos
+
+Handlers de eventos em um subgraph reagem a eventos específicos emitidos por contratos inteligentes na blockchain e acionam handlers definidos no manifest do subgraph. Isto permite que subgraphs processem e armazenem dados conforme a lógica definida.
+
+### Como Definir um Handler de Evento
+
+Um handler de evento é declarado dentro de uma fonte de dados na configuração YAML do subgraph. Ele especifica quais eventos devem ser escutados e a função correspondente a ser executada quando estes eventos forem detetados.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Filtro de tópico opcional que só filtra eventos com o tópico especificado.
+```
+
+## Handlers de chamada
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Handlers de chamadas só serão ativados em um de dois casos: quando a função especificada é chamada por uma conta que não for do próprio contrato, ou quando ela é marcada como externa no Solidity e chamada como parte de outra função no mesmo contrato.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Como Definir um Handler de Chamada
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Função de Mapeamento
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Handlers de Blocos
+
+Além de se inscrever a eventos de contratos ou chamadas para funções, um subgraph também pode querer atualizar os seus dados enquanto novos blocos são afixados à chain. Para isto, um subgraph pode executar uma função após cada bloco, ou após blocos que correspondem a um filtro predefinido.
+
+### Filtros Apoiados
+
+#### Filtro Call
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+A ausência de um filtro para um handler de blocos garantirá que o handler seja chamado a todos os blocos. Uma fonte de dados só pode conter um handler de bloco para cada tipo de filtro.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Filtro Polling
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Filtro Once
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+O handler definido com o filtro once só será chamado uma única vez antes da execução de todos os outros handlers (por isto, o nome "once" / "uma vez"). Esta configuração permite que o subgraph use o handler como um handler de inicialização, para realizar tarefas específicas no começo da indexação.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Função de Mapeamento
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Eventos Anónimos
+
+Caso precise processar eventos anónimos no Solidity, isto é possível ao fornecer o topic 0 do evento, como no seguinte exemplo:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Recibos de Transação em Handlers de Eventos
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Ordem de Handlers de Gatilhos
+
+Os gatilhos para uma fonte de dados dentro de um bloco são ordenados com o seguinte processo:
+
+1. Gatilhos de evento e chamada são, primeiro, ordenados por índice de transação no bloco.
+2. Gatilhos de evento e chamada dentro da mesma transação são ordenados a usar uma convenção: primeiro, gatilhos de evento, e depois, de chamada, cada tipo a respeitar a ordem em que são definidos no manifest.
+3. Gatilhos de blocos são executados após gatilhos de evento e chamada, na ordem em que são definidos no manifest.
+
+Estas regras de organização estão sujeitas à mudança.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Modelos de Fontes de Dados
+
+Um padrão comum em contratos inteligentes compatíveis com EVMs é o uso de contratos de registro ou fábrica. Nisto, um contrato cria, gesta ou refere a um número arbitrário de outros contratos, cada um com o seu próprio estado e eventos.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Fonte de Dados para o Contrato Principal
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Modelos de Fontes de Dados para Contratos Criados Dinamicamente
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... outros campos de fonte para o contrato principal ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Como Instanciar um Modelo de Fontes de Dados
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Comece a indexar a troca; `event.params.exchange` é o
+  // endereço do novo contrato de troca
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Se blocos anteriores conterem dados relevantes à nova fonte, é melhor indexá-los ao ler o estado atual do contrato e criar entidades que representem aquele estado na hora que a nova fonte de dados for criada.
+
+### Contextos de Fontes de Dados
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Blocos Iniciais
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Procure pelo contrato ao inserir o seu endereço na barra de busca.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Carregue a página dos detalhes da transação, onde encontrará o bloco inicial para aquele contrato.
+
+## IndexerHints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. Um número específico: Determina um limite personalizado no número de blocos históricos a guardar.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> O termo "histórico", neste contexto de subgraphs, refere-se ao armazenamento de dados que refletem os estados antigos de entidades mutáveis.
+
+O histórico, desde um bloco especificado, é necessário para:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rebobinar o subgraph de volta àquele bloco
+
+Se os dados históricos desde aquele bloco tiverem passado por pruning, as capacidades acima não estarão disponíveis.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+Para reter uma quantidade específica de dados históricos:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+Para preservar o histórico completo dos estados da entidade:
+
+```
+indexerHints:
+  prune: never
+```

From d47c0316c0fc219149e38556f601bbbefa5e5f62 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:23 -0500
Subject: [PATCH 0288/1325] New translations transfer-to-the-graph.mdx
 (Russian)

---
 .../ru/cookbook/transfer-to-the-graph.mdx     | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/ru/cookbook/transfer-to-the-graph.mdx b/website/pages/ru/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..d44d0e63c45f 100644
--- a/website/pages/ru/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/ru/cookbook/transfer-to-the-graph.mdx
@@ -12,16 +12,16 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
 ### Create a Subgraph in Subgraph Studio
 
-- Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
-- Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
+- Перейдите в [Subgraph Studio](https://thegraph.com/studio/) и подключите свой кошелек.
+- Нажмите "Создать субграф". Рекомендуется называть субграф с использованием Заглавного регистра: "Subgraph Name Chain Name".
 
 > Note: After publishing, the subgraph name will be editable but requires on-chain action each time, so name it properly.
 
@@ -31,7 +31,7 @@ You must have [Node.js](https://nodejs.org/) and a package manager of your choic
 
 On your local machine, run the following command:
 
-Using [npm](https://www.npmjs.com/):
+Использование [npm](https://www.npmjs.com/):
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Пример
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Дополнительные источники
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From ff9250c128b8c7032551aabed0fbc69c8a7af3cc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:25 -0500
Subject: [PATCH 0289/1325] New translations advanced.mdx (Russian)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/ru/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/ru/developing/creating-a-subgraph/advanced.mdx b/website/pages/ru/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..63fdffd404df
--- /dev/null
+++ b/website/pages/ru/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Обзор
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Тайм-серии и агрегации
+
+Тайм-серии и агрегации позволяют Вашему субграфу отслеживать такие статистические данные, как средняя цена за день, общий объем переводов за час и т. д.
+
+Эта функция представляет два новых типа объектов субграфов. Объекты тайм-серий записывают точки данных с временными метками. Объекты агрегирования выполняют заранее объявленные вычисления над точками данных тайм-серий ежечасно или ежедневно, а затем сохраняют результаты для быстрого доступа через GraphQL.
+
+### Пример схемы
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Определение тайм-серий и агрегаций
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Доступные интервалы агрегации
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Доступные функции агрегации
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Пример запроса агрегации
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Примечание:
+
+Чтобы использовать тайм-серии и агрегации, субграф должен иметь версию спецификации ≥1.1.0. Обратите внимание, что эта функция может претерпеть значительные изменения, которые могут повлиять на обратную совместимость.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Неисправимые ошибки
+
+Ошибки индексирования в уже синхронизированных субграфах по умолчанию приведут к сбою субграфа и прекращению синхронизации. В качестве альтернативы субграфы можно настроить на продолжение синхронизации при наличии ошибок, игнорируя изменения, внесенные обработчиком, который спровоцировал ошибку. Это дает авторам субграфов время на исправление своих субграфов, в то время как запросы к последнему блоку продолжают обрабатываться, хотя результаты могут быть противоречивыми из-за бага, вызвавшего ошибку. Обратите внимание на то, что некоторые ошибки всё равно всегда будут фатальны. Чтобы быть нефатальной, ошибка должна быть детерминированной.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Для включения нефатальных ошибок необходимо установить в манифесте субграфа следующий флаг функции:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## Источники файловых данных IPFS/Arweave
+
+Источники файловых данных — это новая функциональность субграфа для надежного и расширенного доступа к данным вне чейна во время индексации. Источники данных файлов поддерживают получение файлов из IPFS и Arweave.
+
+> Это также закладывает основу для детерминированного индексирования данных вне сети, а также потенциального введения произвольных данных из HTTP-источников.
+
+### Обзор
+
+Вместо "встроенного" получения файлов во время выполнения обработчика, это решение вводит шаблоны, которые могут создаваться в качестве новых источников данных для заданного идентификатора файла. Эти новые источники данных загружают файлы, повторяя попытки в случае неудачи, и запускают специальный обработчик при нахождении файла.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Руководство по обновлению
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Добавьте новый тип объекта, который будет обновляться при обнаружении файлов
+
+Источники файловых данных не могут получать доступ к объектам на чейн-основе или обновлять их, но должны обновлять объекты, специфичные для файлов.
+
+Это может означать разделение полей существующих объектов на отдельные объекты, связанные между собой.
+
+Исходный объединенный объект:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Новый разделенный объект:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Если между родительским объектом и результирующим объектом-источником данных существует связь1:1, то наиболее простым вариантом будет связать родительский объект с результирующим файловым объектом, используя в качестве поиска IPFS CID. Свяжитесь с нами в Discord, если у Вас возникли трудности с моделированием новых объектов на основе файлов!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Это источник данных, который будет создан при обнаружении интересующего файла.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Создание нового обработчика для обработки файлов
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Пример обработчика:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Создание файловых источников данных при необходимости
+
+Теперь вы можете создавать файловые источники данных во время выполнения обработчиков на чейн-основе:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Пример:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//Этот пример кода предназначен для сборщика субграфа Crypto. Приведенный выше хеш ipfs представляет собой каталог с метаданными токена для всех NFT криптоковена.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //Это создает путь к метаданным для одного сборщика NFT Crypto. Он объединяет каталог с "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+Это создаст новый источник данных файла, который будет опрашивать настроенную конечную точку IPFS или Arweave Graph Node, повторяя попытку, если она не найдена. Когда файл будет найден, будет выполнен обработчик источника данных файла.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Поздравляем, Вы используете файловые источники данных!
+
+#### Развертывание субграфов
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Ограничения
+
+Обработчики и объекты файловых источников данных изолированы от других объектов субграфа, что гарантирует их детерминированность при выполнении и исключает загрязнение источников данных на чейн-основе. В частности:
+
+- Объекты, созданные с помощью файловых источников данных, неизменяемы и не могут быть обновлены
+- Обработчики файловых источников данных не могут получить доступ к объектам из других файловых источников данных
+- Объекты, связанные с источниками данных файлов, не могут быть доступны обработчикам на чейн-основе
+
+> Хотя это ограничение не должно вызывать проблем в большинстве случаев, для некоторых оно может вызвать сложности. Если у Вас возникли проблемы с моделированием Ваших файловых данных в субграфе, свяжитесь с нами через Discord!
+
+Кроме того, невозможно создать источники данных из файлового источника данных, будь то источник данных onchain или другой файловый источник данных. Это ограничение может быть снято в будущем.
+
+#### Лучшие практики
+
+Если Вы связываете метаданные NFT с соответствующими токенами, используйте хэш IPFS метаданных для ссылки на объект Metadata из объекта Token. Сохраните объект Metadata, используя хэш IPFS в качестве идентификатора.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Мы работаем над улучшением приведенной выше рекомендации, поэтому запросы возвращают только "самую последнюю" версию
+
+#### Известные проблемы
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Примеры
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Ссылки
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Фильтры индексированных аргументов/фильтры тем
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Фильтры по темам, также известные как фильтры по индексированным аргументам, — это мощная функция в субграфах, которая позволяет пользователям точно фильтровать события блокчейна на основе значений их индексированных аргументов.
+
+- Эти фильтры помогают изолировать конкретные интересующие события из огромного потока событий в блокчейне, позволяя субграфам работать более эффективно, сосредотачиваясь только на релевантных данных.
+
+- Это полезно для создания персональных субграфов, отслеживающих конкретные адреса и их взаимодействие с различными смарт-контрактами в блокчейне.
+
+### Как работают фильтры тем
+
+Когда смарт-контракт генерирует событие, любые аргументы, помеченные как индексированные, могут использоваться в манифесте субграфа в качестве фильтров. Это позволяет субграфу выборочно прослушивать события, соответствующие этим индексированным аргументам.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// Идентификатор лицензии SPDX: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Объявление события с индексируемыми параметрами для адресов
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Функция для имитации передачи токенов
+    function transfer(address to, uint256 value) public {
+        // Генерация события Transfer с указанием from, to и value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+В этом примере:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Конфигурация в субграфах
+
+Фильтры тем определяются непосредственно в конфигурации обработчика событий в манифесте субграфа. Вот как они настроены:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+В этой настройке:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Каждая тема может иметь одно или несколько значений, и событие обрабатывается только в том случае, если оно соответствует одному из значений в каждой указанной теме.
+
+#### Логика фильтра
+
+- В рамках одной темы: логика действует как условие OR. Событие будет обработано, если оно соответствует любому из перечисленных значений в данной теме.
+- Между разными темами: логика функционирует как условие AND. Событие должно удовлетворять всем указанным условиям в разных темах, чтобы вызвать соответствующий обработчик.
+
+#### Пример 1. Отслеживание прямых переводов с адреса A на адрес B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+В данной конфигурации:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Пример 2. Отслеживание транзакций в любом направлении между двумя и более адресами
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Адрес отправителя
+    topic2: ['0xAddressB', '0xAddressC'] # Адрес получателя
+```
+
+В данной конфигурации:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- Субграф будет индексировать транзакции, происходящие в любом направлении между несколькими адресами, что позволит осуществлять комплексный мониторинг взаимодействий с участием всех адресов.
+
+## Декларированный eth_call
+
+> Примечание: Это экспериментальная функция, которая пока недоступна в стабильной версии Graph Node. Вы можете использовать её только в Subgraph Studio или на своей локальной ноде.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+Эта функция выполняет следующие действия:
+
+- Значительно повышает производительность получения данных из блокчейна Ethereum за счет сокращения общего времени выполнения нескольких вызовов и оптимизации общей эффективности субграфа.
+- Обеспечивает ускоренное получение данных, что приводит к более быстрому реагированию на запросы и улучшению пользовательского опыта.
+- Сокращает время ожидания для приложений, которым необходимо агрегировать данные из нескольких вызовов Ethereum, что делает процесс получения данных более эффективным.
+
+### Ключевые понятия
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Параллельное выполнение: Вместо того, чтобы ждать завершения одного вызова перед началом следующего, можно инициировать несколько вызовов одновременно.
+- Эффективность использования времени: Общее время, затраченное на все вызовы, изменяется от суммы времени отдельных вызовов (последовательные) до времени, затраченного на самый продолжительный вызов (параллельные).
+
+#### Scenario without Declarative `eth_calls`
+
+Представьте, что у вас есть субграф, которому необходимо выполнить три вызова в Ethereum, чтобы получить данные о транзакциях пользователя, балансе и владении токенами.
+
+Традиционно эти вызовы могут выполняться последовательно:
+
+1. Вызов 1 (Транзакции): Занимает 3 секунды
+2. Вызов 2 (Баланс): Занимает 2 секунды
+3. Вызов 3 (Холдинг токенов): Занимает 4 секунды
+
+Общее затраченное время = 3 + 2 + 4 = 9 секунд
+
+#### Scenario with Declarative `eth_calls`
+
+С помощью этой функции Вы можете объявить, что эти вызовы будут выполняться параллельно:
+
+1. Вызов 1 (Транзакции): Занимает 3 секунды
+2. Вызов 2 (Баланс): Занимает 2 секунды
+3. Вызов 3 (Холдинг токенов): Занимает 4 секунды
+
+Поскольку эти вызовы выполняются параллельно, общее затраченное время равно времени, затраченному на самый длительный вызов.
+
+Общее затраченное время = макс. (3, 2, 4) = 4 секунды
+
+#### Как это работает
+
+1. Декларативное определение: В манифесте субграфа Вы декларируете вызовы Ethereum таким образом, чтобы указать, что они могут выполняться параллельно.
+2. Механизм параллельного выполнения: Механизм выполнения The Graph Node распознает эти объявления и выполняет вызовы одновременно.
+3. Агрегация результатов: После завершения всех вызовов результаты агрегируются и используются субграфом для дальнейшей обработки.
+
+#### Пример конфигурации в манифесте субграфа
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Подробности для приведенного выше примера:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Графтинг (перенос) на существующие субграфы
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Поскольку графтинг копирует, а не индексирует базовые данные, гораздо быстрее перенести субграф в нужный блок, чем индексировать с нуля, хотя для очень больших субграфов копирование исходных данных может занять несколько часов. Пока графтовый субграф инициализируется, узел The Graph будет регистрировать информацию о типах объектов, которые уже были скопированы.
+
+Графтовый субграф может использовать схему GraphQL, которая не идентична схеме базового субграфа, а просто совместима с ней. Она сама по себе должна быть допустимой схемой субграфа, но может отличаться от схемы базового субграфа следующими способами:
+
+- Она добавляет или удаляет типы объектов
+- Она удаляет атрибуты из типов объектов
+- Она добавляет в типы объектов атрибуты с возможностью обнуления
+- Она превращает ненулевые атрибуты в нулевые
+- Она добавляет значения в перечисления
+- Она добавляет или удаляет интерфейсы
+- Она изменяется в зависимости от того, для каких типов объектов реализован тот или иной интерфейс
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 2ff09f2b560dabb82d756601718a6a0367f3e0ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:26 -0500
Subject: [PATCH 0290/1325] New translations assemblyscript-mappings.mdx
 (Russian)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/ru/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/ru/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ru/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..e4c398204f2e
--- /dev/null
+++ b/website/pages/ru/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Обзор
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Написание мэппингов
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Рекомендуемые идентификаторы для создания новых объектов
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Обработка объектов с одинаковыми идентификаторами
+
+При создании и сохранении нового объекта, если объект с таким же идентификатором уже существует, в процессе слияния приоритетны свойства нового объекта. Это означает, что существующий объект будет обновлен значениями из нового объекта.
+
+Если для поля нового объекта с тем же идентификатором намеренно установлено нулевое значение, существующий объект будет обновлен с использованием нулевого значения.
+
+Если для поля в новом объекте с тем же идентификатором не установлено значение, поле также будет иметь значение null.
+
+## Генерация кода
+
+Для упрощения и обеспечения безопасности типов при работе со смарт-контрактами, событиями и объектами Graph CLI может генерировать типы AssemblyScript на основе схемы GraphQL субграфа и ABI контрактов, включенных в источники данных.
+
+Это делается с помощью
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 17dc10137afae6e16fe8e88df25ddc38243746ef Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:27 -0500
Subject: [PATCH 0291/1325] New translations install-the-cli.mdx (Russian)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..bb6722d19f5e
--- /dev/null
+++ b/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Установка Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Обзор
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Начало работы
+
+### Установка Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+Выполните одну из следующих команд на своём локальном компьютере:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Создайте субграф
+
+### Из существующего контракта
+
+Следующая команда создает субграф, индексирующий все события существующего контракта:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- Команда пытается получить ABI контракта из Etherscan.
+
+  - Интерфейс командной строки The Graph использует общедоступную конечную точку RPC. Несмотря на то, что возможны периодические сбои, повторные попытки обычно решают эту проблему. Если сбои продолжаются, рассмотрите возможность использования локального ABI.
+
+- Если какой-либо из необязательных аргументов отсутствует, Вам будет предложено воспользоваться интерактивной формой.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### Из примера подграфа
+
+Следующая команда инициализирует новый проект на примере субграфа:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Специфические особенности
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Получение ABIs
+
+Файл(ы) ABI должен(ы) соответствовать Вашему контракту (контрактам). Существует несколько способов получения файлов ABI:
+
+- Если Вы создаете свой собственный проект, у Вас, скорее всего, будет доступ к наиболее актуальным ABIS.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## Релизы SpecVersion
+
+| Версия | Примечания к релизу                                                                                                                                                      |
+| :----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5 | Добавлена поддержка обработчиков событий, имеющих доступ к чекам транзакций.                                                                                             |
+|  0.0.4 | Добавлена ​​поддержка управления функциями субграфа.                                                                                                                     |

From e18cca8c92295bbd5cf14f23d2d31fcbb7a386cf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:28 -0500
Subject: [PATCH 0292/1325] New translations ql-schema.mdx (Russian)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..0fe26c115582
--- /dev/null
+++ b/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Обзор
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Определение Объектов
+
+Прежде чем определять объекты, важно сделать шаг назад и задуматься над тем, как структурированы и связаны Ваши данные.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- Может быть полезно представить объекты как «объекты, содержащие данные», а не как события или функции.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- По умолчанию объекты изменяемы, то есть мэппинги могут загружать существующие объекты, изменять и сохранять их новую версию.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - Если изменения происходят в том же блоке, в котором был создан объект, то мэппинги могут вносить изменения в неизменяемые объекты. Неизменяемые объекты гораздо быстрее записываются и запрашиваются, поэтому их следует использовать, когда это возможно.
+
+#### Удачный пример
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Неудачный пример
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Дополнительные и обязательные поля
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Встроенные скалярные типы
+
+#### Поддерживаемые GraphQL скаляры
+
+В API GraphQL поддерживаются следующие скаляры:
+
+| Тип          | Описание                                                                                                                                                                                                         |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Массив байтов, представленный в виде шестнадцатеричной строки. Обычно используется для хэшей и адресов Ethereum.                                                                                                 |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Перечисления
+
+Вы также можете создавать перечисления внутри схемы. Перечисления имеют следующий синтаксис:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Связи объектов
+
+Объект может иметь связь с одним или несколькими другими объектами в Вашей схеме. Эти связи могут быть использованы в Ваших запросах. Связи в The Graph являются однонаправленными. Можно смоделировать двунаправленные связи, определив однонаправленную связь на любом "конце" связи.
+
+Связи определяются для объектов точно так же, как и для любого другого поля, за исключением того, что в качестве типа указывается тип другого объекта.
+
+#### Связи "Один к одному"
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Связи "Один ко многим"
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Обратные запросы
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+Для связей "один ко многим" связь всегда должна храниться на стороне "один", а сторона "многие" всегда должна быть производной. Такое сохранение связи, вместо хранения массива объектов на стороне "многие", приведет к значительному повышению производительности как при индексации, так и при запросах к субграфам. В общем, следует избегать хранения массивов объектов настолько, насколько это возможно.
+
+#### Пример
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Связи "Многие ко многим"
+
+Для связей "многие ко многим", таких, например, как пользователи, каждый из которых может принадлежать к любому числу организаций, наиболее простым, но, как правило, не самым производительным способом моделирования связей является создание массива в каждом из двух задействованных объектов. Если связь симметрична, то необходимо сохранить только одну сторону связи, а другая сторона может быть выведена.
+
+#### Пример
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Этот подход требует, чтобы запросы опускались на один дополнительный уровень для получения, например, сведений об организациях для пользователей:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Такой более сложный способ хранения связей "многие ко многим" приведет к уменьшению объема хранимых данных для субграфа и, следовательно, к тому, что субграф будет значительно быстрее индексироваться и запрашиваться.
+
+### Добавление комментариев к схеме
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  #уникальный идентификатор и первичный ключ объекта
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Определение полей полнотекстового поиска
+
+Полнотекстовые поисковые запросы фильтруют и ранжируют объекты на основе введенных данных текстового запроса. Полнотекстовые запросы способны возвращать совпадения по схожим словам путем обработки текста запроса в виде строк перед сравнением с индексированными текстовыми данными.
+
+Определение полнотекстового запроса включает в себя название запроса, словарь языка, используемый для обработки текстовых полей, алгоритм ранжирования, используемый для упорядочивания результатов, и поля, включенные в поиск. Каждый полнотекстовый запрос может охватывать несколько полей, но все включенные поля должны относиться к одному типу объекта.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Поддерживаемые языки
+
+Выбор другого языка окажет решающее, хотя иногда и неуловимое влияние на API полнотекстового поиска. Поля, охватываемые полем полнотекстового запроса, рассматриваются в контексте выбранного языка, поэтому лексемы, полученные в результате анализа и поисковых запросов, варьируются от языка к языку. Например: при использовании поддерживаемого турецкого словаря "token" переводится как "toke", в то время как, конечно, словарь английского языка переводит его в "token".
+
+Поддерживаемые языковые словари:
+
+| Code    | Словарь       |
+| ------- | ------------- |
+| простой | General       |
+| da      | Danish        |
+| nl      | Dutch         |
+| en      | English       |
+| fi      | Finnish       |
+| fr      | French        |
+| de      | German        |
+| hu      | Hungarian     |
+| it      | Italian       |
+| no      | Norwegian     |
+| pt      | Португальский |
+| ro      | Romanian      |
+| ru      | Russian       |
+| es      | Spanish       |
+| sv      | Swedish       |
+| tr      | Turkish       |
+
+### Алгоритмы ранжирования
+
+Поддерживаемые алгоритмы для упорядочивания результатов:
+
+| Algorithm     | Description                                                                                    |
+| ------------- | ---------------------------------------------------------------------------------------------- |
+| rank          | Используйте качество соответствия (0-1) полнотекстового запроса, чтобы упорядочить результаты. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                                |

From bb7472284a3b3bb06c4334c52837ce4aff8b16ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:29 -0500
Subject: [PATCH 0293/1325] New translations subgraph-manifest.mdx (Russian)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/ru/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/ru/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ru/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..4a8f9c3a7aac
--- /dev/null
+++ b/website/pages/ru/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Обзор
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+Один субграф может:
+
+- Индексировать данные из нескольких смарт-контрактов (но не из нескольких сетей).
+
+- Индексировать данные из файлов IPFS с помощью источников файловых данных.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Важными элементами манифеста, которые необходимо обновить, являются:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Обработчики событий
+
+Обработчики событий в субграфе реагируют на конкретные события, генерируемые смарт-контрактами в блокчейне, и запускают обработчики, определенные в манифесте подграфа. Это позволяет субграфам обрабатывать и хранить данные о событиях в соответствии с определенной логикой.
+
+### Определение обработчика событий
+
+Обработчик событий объявлен внутри источника данных в конфигурации YAML субграфа. Он определяет, какие события следует прослушивать, и соответствующую функцию, которую необходимо выполнить при обнаружении этих событий.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Обработчики вызовов
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Обработчики вызовов срабатывают только в одном из двух случаев: когда указанная функция вызывается учетной записью, отличной от самого контракта, или когда она помечена как внешняя в Solidity и вызывается как часть другой функции в том же контракте.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Определение обработчика вызова
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Функция мэппинга
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Обработчики блоков
+
+В дополнение к подписке на события контракта или вызовы функций, субграф может захотеть обновить свои данные по мере добавления в цепочку новых блоков. Чтобы добиться этого, субграф может запускать функцию после каждого блока или после блоков, соответствующих заранее определенному фильтру.
+
+### Поддерживаемые фильтры
+
+#### Фильтр вызовов
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+Отсутствие фильтра для обработчика блоков гарантирует, что обработчик вызывается для каждого блока. Источник данных может содержать только один обработчик блоков для каждого типа фильтра.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Фильтр опроса
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Однократный фильтр
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Определенный обработчик с однократным фильтром будет вызываться только один раз перед запуском всех остальных обработчиков. Эта конфигурация позволяет субграфу использовать обработчик в качестве обработчика инициализации, выполняя определенные задачи в начале индексирования.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Функция мэппинга
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Анонимные события
+
+Если Вам нужно обрабатывать анонимные события в Solidity, это можно сделать, указав тему события 0, как показано в примере:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Подтверждения транзакций в обработчиках событий
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Порядок запуска обработчиков
+
+Триггеры для источника данных внутри блока упорядочиваются с помощью следующего процесса:
+
+1. Триггеры событий и вызовов сначала упорядочиваются по индексу транзакции внутри блока.
+2. Триггеры событий и вызовов в рамках одной транзакции упорядочиваются по следующему принципу: сначала триггеры событий, затем триггеры вызовов, причем для каждого типа соблюдается тот порядок, в котором они определены в манифесте.
+3. Триггеры блоков запускаются после триггеров событий и вызовов в том порядке, в котором они определены в манифесте.
+
+Эти правила оформления заказа могут быть изменены.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Шаблоны источников данных
+
+Распространенным шаблоном в смарт-контрактах, совместимых с EVM, является использование реестровых или заводских контрактов, когда один контракт создает, управляет или ссылается на произвольное количество других контрактов, каждый из которых имеет свое собственное состояние и события.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Источник данных для основного контракта
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Шаблоны источников данных для динамически создаваемых контрактов
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Создание шаблона источника данных
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Если предыдущие блоки содержат данные, относящиеся к новому источнику данных, лучше всего проиндексировать эти данные, считывая текущее состояние контракта и создавая объекты, представляющие это состояние на момент создания нового источника данных.
+
+### Контекст источника данных
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Стартовые блоки
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Найдите контракт, введя его адрес в строке поиска.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Загрузите страницу сведений о транзакции, где Вы найдете начальный блок для этого контракта.
+
+## Подсказки индексатору
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Сокращение
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. Конкретное число: устанавливает индивидуальный лимит на количество сохраняемых исторических блоков.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> Термин «история» в контексте субграфов означает хранение данных, отражающих старые состояния изменяемых объектов.
+
+История данного блока необходима для:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Отката субграфа обратно к этому блоку
+
+Если исторические данные на момент создания блока были удалены, вышеупомянутые возможности будут недоступны.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+Чтобы сохранить определенный объем исторических данных:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+Чтобы сохранить полную историю состояний объекта, выполните следующее:
+
+```
+indexerHints:
+  prune: never
+```

From 420964e3a9788fbebdf68e6250cf9d6c9d424937 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:30 -0500
Subject: [PATCH 0294/1325] New translations subgraphs.mdx (Swedish)

---
 website/pages/sv/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/sv/subgraphs.mdx b/website/pages/sv/subgraphs.mdx
index 27b452211477..ff81ea93c8b9 100644
--- a/website/pages/sv/subgraphs.mdx
+++ b/website/pages/sv/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Subgraffar
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Livscykel för undergrafer
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From aed94651420d2e9dc783a5cf5a8c49f6b16dbcd5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:31 -0500
Subject: [PATCH 0295/1325] New translations transfer-to-the-graph.mdx
 (Swedish)

---
 .../pages/sv/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/sv/cookbook/transfer-to-the-graph.mdx b/website/pages/sv/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..34d7ef222024 100644
--- a/website/pages/sv/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/sv/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Exempel
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Ytterligare resurser
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From b0bf368a509df1d8b55da0a83fd48ec7b8102d85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:33 -0500
Subject: [PATCH 0296/1325] New translations advanced.mdx (Swedish)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/sv/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/sv/developing/creating-a-subgraph/advanced.mdx b/website/pages/sv/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..676c666ff0e8
--- /dev/null
+++ b/website/pages/sv/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Översikt
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Icke dödliga fel
+
+Indexeringsfel på redan synkroniserade delgrafer kommer, som standard, att få delgrafen att misslyckas och sluta synkronisera. Delgrafer kan istället konfigureras för att fortsätta synkroniseringen i närvaro av fel, genom att ignorera ändringarna som orsakades av hanteraren som provocerade felet. Det ger delgrafsförfattare tid att korrigera sina delgrafer medan förfrågningar fortsätter att behandlas mot det senaste blocket, även om resultaten kan vara inkonsekventa på grund av felet som orsakade felet. Observera att vissa fel alltid är dödliga. För att vara icke-dödliga måste felet vara känt för att vara deterministiskt.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Aktivering av icke-dödliga fel kräver att följande funktionsflagga sätts i delgrafens manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+Filbaserade datakällor är en ny delgrafsfunktion för att få tillgång till data utanför kedjan under indexering på ett robust, utökat sätt. Filbaserade datakällor stödjer hämtning av filer från IPFS och från Arweave.
+
+> Detta lägger också grunden för deterministisk indexering av data utanför kedjan, samt möjligheten att introducera godtycklig data som hämtas via HTTP.
+
+### Översikt
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Uppgraderingsguide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Lägg till en ny entitetstyp som kommer att uppdateras när filer hittas
+
+Filbaserade datakällor kan inte komma åt eller uppdatera kedjebaserade entiteter, utan måste uppdatera filspecifika entiteter.
+
+Detta kan innebära att fält från befintliga entiteter separeras i separata entiteter som är kopplade ihop.
+
+Ursprunglig kombinerad entitet:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Ny, delad enhet:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Om relationen är 1:1 mellan föräldraentiteten och den resulterande filbaserade datakälla entiteten är det enklaste mönstret att länka föräldraentiteten till en resulterande filbaserad entitet genom att använda IPFS CID som söknyckel. Kontakta oss på Discord om du har svårt att modellera dina nya filbaserade entiteter!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Detta är datakällan som skapas när en intressant fil identifieras.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Skapa en ny hanterare för att bearbeta filer
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Exempel på hanterare:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Skapa filbaserade datakällor vid behov
+
+Nu kan du skapa filbaserade datakällor under utförandet av kedjebaserade hanterare:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Exempel:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from "../generated/templates";
+
+const ipfshash = "QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm";
+//Denna exempelkod är för en undergraf för kryptosamverkan. Ovanstående ipfs-hash är en katalog med tokenmetadata för alla kryptosamverkande NFT:er.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString());
+  if (!token) {
+    token = new Token(event.params.tokenId.toString());
+    token.tokenID = event.params.tokenId;
+
+    token.tokenURI = "/" + event.params.tokenId.toString() + ".json";
+    const tokenIpfsHash = ipfshash + token.tokenURI;
+    //Detta skapar en sökväg till metadata för en enskild Crypto coven NFT. Den konkaterar katalogen med "/" + filnamn + ".json"
+
+    token.ipfsURI = tokenIpfsHash;
+
+    TokenMetadataTemplate.create(tokenIpfsHash);
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp;
+  token.owner = event.params.to.toHexString();
+  token.save();
+}
+```
+
+Detta kommer att skapa en ny filbaserad datakälla som kommer att övervaka Graph Nodes konfigurerade IPFS- eller Arweave-slutpunkt och försöka igen om den inte hittas. När filen hittas kommer filbaserad datakälla hanteraren att köras.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Grattis, du använder filbaserade datakällor!
+
+#### Distribuera dina delgrafer
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Begränsningar
+
+Filbaserade datakällahanterare och entiteter är isolerade från andra delgrafentiteter, vilket säkerställer att de är deterministiska när de körs och att ingen förorening av kedjebaserade datakällor sker. För att vara specifik:
+
+- Entiteter skapade av Filbaserade datakällor är oföränderliga och kan inte uppdateras
+- Filbaserade datakällahanterare kan inte komma åt entiteter från andra filbaserade datakällor
+- Entiteter associerade med filbaserade datakällor kan inte nås av kedjebaserade hanterare
+
+> Även om denna begränsning inte bör vara problematisk för de flesta användningsfall kan den införa komplexitet för vissa. Var god kontakta oss via Discord om du har problem med att modellera din data baserad på fil i en delgraf!
+
+Dessutom är det inte möjligt att skapa datakällor från en filbaserad datakälla, vare sig det är en datakälla på kedjan eller en annan filbaserad datakälla. Denna begränsning kan komma att hävas i framtiden.
+
+#### Bästa praxis
+
+Om du länkar NFT-metadata till motsvarande token, använd metadata IPFS-hash för att referera till en Metadata-entitet från Token-entiteten. Spara Metadata-entiteten med IPFS-hash som ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Vi arbetar med att förbättra rekommendationen ovan så att förfrågningar endast returnerar den "senaste" versionen
+
+#### Kända problem
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Exempel
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Referenser
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Ympning på befintliga delgrafer
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Eftersom ympning kopierar data istället för att indexera basdata går det mycket snabbare att få delgrafen till det önskade blocket än att indexera från början, även om den initiala datorkopieringen fortfarande kan ta flera timmar för mycket stora delgrafer. Medan den ympade delgrafen initialiseras kommer Graph Node att logga information om de entitetstyper som redan har kopierats.
+
+Den ympade delgrafen kan använda ett GraphQL-schema som inte är identiskt med basdelgrafens, men bara kompatibelt med den. Det måste vara ett giltigt delgrafschema i sig själv, men kan avvika från basdelgrafens schema på följande sätt:
+
+- Den lägger till eller tar bort entitetstyper
+- Den tar bort attribut från entitetstyper
+- Den lägger till nollställbara attribut till entitetstyper
+- Den gör icke-nollställbara attribut till nollställbara attribut
+- Den lägger till värden till enum
+- Den lägger till eller tar bort gränssnitt
+- Den ändrar vilka entitetstyper som ett gränssnitt är implementerat för
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 5cfcc4e3b7e78fa64576d6a812d4d0d39818359a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:34 -0500
Subject: [PATCH 0297/1325] New translations assemblyscript-mappings.mdx
 (Swedish)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..646645e79ccc
--- /dev/null
+++ b/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Översikt
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Skriv Mappningar
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from "../generated/Gravity/Gravity";
+import { Gravatar } from "../generated/schema";
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id);
+  gravatar.owner = event.params.owner;
+  gravatar.displayName = event.params.displayName;
+  gravatar.imageUrl = event.params.imageUrl;
+  gravatar.save();
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id;
+  let gravatar = Gravatar.load(id);
+  if (gravatar == null) {
+    gravatar = new Gravatar(id);
+  }
+  gravatar.owner = event.params.owner;
+  gravatar.displayName = event.params.displayName;
+  gravatar.imageUrl = event.params.imageUrl;
+  gravatar.save();
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Rekommenderade ID:n för att skapa nya entiteter
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Kodgenerering
+
+För att göra det enkelt och typsäkert att arbeta med smarta kontrakt, händelser och entiteter kan Graph CLI generera AssemblyScript-typer från subgrafens GraphQL-schema och kontrakts-ABIn som ingår i datakällorna.
+
+Detta görs med
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from "../generated/Gravity/Gravity";
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from "../generated/schema"
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From e8dffdafe50aa85ae32a4e6703389850a3339080 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:35 -0500
Subject: [PATCH 0298/1325] New translations install-the-cli.mdx (Swedish)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..09b66d92660e
--- /dev/null
+++ b/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Installera Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Översikt
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Komma igång
+
+### Installera Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+Kör ett av följande kommandon på din lokala dator:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Skapa en Subgraf
+
+### Från ett befintligt avtal
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### Från ett exempel på en undergraf
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+ABI-filerna måste matcha ditt/dina kontrakt. Det finns några olika sätt att få ABI-filer:
+
+- Om du bygger ditt eget projekt har du förmodligen tillgång till dina senaste ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Versionsanteckningar                                                                                                                                                     |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 6b8304a87e9e8ce88bf21eb6435d1110a2958b51 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:36 -0500
Subject: [PATCH 0299/1325] New translations ql-schema.mdx (Swedish)

---
 .../creating-a-subgraph/ql-schema.mdx         | 317 ++++++++++++++++++
 1 file changed, 317 insertions(+)
 create mode 100644 website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..7c769d036458
--- /dev/null
+++ b/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,317 @@
+---
+title: The Graph QL Schema
+---
+
+## Översikt
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Bra exempel
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Dåligt exempel
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Valfria och obligatoriska fält
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Inbyggda Skalartyper
+
+#### GraphQL-Stödda Skalartyper
+
+The following scalars are supported in the GraphQL API:
+
+| Typ          | Beskrivning                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Bytematris, representerad som en hexadecimal sträng. Vanligt används för Ethereum-hashar och adresser.                                                                                                           |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+Du kan också skapa enums inom ett schema. Enums har följande syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entitetsrelationer
+
+En entitet kan ha en relation till en eller flera andra entiteter i ditt schema. Dessa relationer kan traverseras i dina frågor. Relationer i The Graph är enriktade. Det är möjligt att simulera dubbelriktade relationer genom att definiera en enriktad relation på antingen den ena "änden" av relationen.
+
+Relationer definieras på entiteter precis som vilket annat fält som helst, förutom att den specificerade typen är en annan entitet.
+
+#### En-till-en-relationer
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### En-till-många-relationer
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Omvända sökningar
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+För en-till-många-relationer bör relationen alltid lagras på 'en'-sidan, och 'många'-sidan bör alltid härledas. Att lagra relationen på detta sätt, istället för att lagra en array av entiteter på 'många'-sidan, kommer att resultera i dramatiskt bättre prestanda både för indexering och för frågning av subgraphen. Generellt sett bör lagring av arrayer av entiteter undvikas så mycket som är praktiskt möjligt.
+
+#### Exempel
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Många-till-många-relationer
+
+För många-till-många-relationer, som till exempel användare som var och en kan tillhöra ett antal organisationer, är det mest raka, men generellt sett inte den mest prestanda-optimerade, sättet att modellera relationen som en array i vardera av de två entiteter som är involverade. Om relationen är symmetrisk behöver bara ena sidan av relationen lagras och den andra sidan kan härledas.
+
+#### Exempel
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Detta tillvägagångssätt kräver att frågorna går ner till ytterligare en nivå för att hämta t. ex. organisationer för användare:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Detta mer avancerade sätt att lagra många-till-många-relationer kommer att leda till att mindre data lagras för subgrafen, och därför till en subgraf som ofta är dramatiskt snabbare att indexera och att fråga.
+
+### Lägga till kommentarer i schemat
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Definiera fält för fulltextsökning
+
+Fulltextsökningar filtrerar och rangordnar entiteter baserat på en textinmatning för sökning. Fulltextförfrågningar kan returnera träffar för liknande ord genom att bearbeta söktexten till stammar innan de jämförs med den indexerade textdata.
+
+En fulltextförfrågningsdefinition inkluderar förfrågningsnamnet, ordboken som används för att bearbeta textfälten, rangordningsalgoritmen som används för att ordna resultaten och fälten som ingår i sökningen. Varje fulltextförfrågan kan omfatta flera fält, men alla inkluderade fält måste vara från en enda entitetstyp.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [
+      {
+        entity: "Band"
+        fields: [{ name: "name" }, { name: "description" }, { name: "bio" }]
+      }
+    ]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Stödda språk
+
+Att välja ett annat språk kommer att ha en definitiv, om än ibland subtil, effekt på fulltext-sök-API:en. Fält som omfattas av en fulltextförfrågningsfunktion granskas i kontexten av det valda språket, så lexem som produceras av analys och sökfrågor varierar från språk till språk. Till exempel: när det används det stödda turkiska ordboken "token" så avstamsas det till "toke", medan engelska ordboken självklart avstammar det till "token".
+
+Stödda språkordböcker:
+
+| Code   | Ordbok       |
+| ------ | ------------ |
+| enkel  | General      |
+| da     | Danish       |
+| nl     | Dutch        |
+| en     | English      |
+| fi     | Finnish      |
+| fr     | French       |
+| de     | German       |
+| hu     | Hungarian    |
+| it     | Italian      |
+| no     | Norwegian    |
+| pt     | Portugisiska |
+| ro     | Romanian     |
+| ru     | Russian      |
+| es     | Spanish      |
+| sv     | Swedish      |
+| tr     | Turkish      |
+
+### Rankningsalgoritmer
+
+Stödda algoritmer för att ordna resultat:
+
+| Algorithm     | Description                                                                        |
+| ------------- | ---------------------------------------------------------------------------------- |
+| rank          | Använd matchningskvaliteten (0-1) från fulltextförfrågan för att ordna resultaten. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                    |

From 56a8f1322d159f78e6e82021ab19f927f560b318 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:37 -0500
Subject: [PATCH 0300/1325] New translations subgraph-manifest.mdx (Swedish)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..eedbf6b73287
--- /dev/null
+++ b/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Översikt
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+De viktiga posterna att uppdatera för manifestet är:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Anropsbehandlare
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Anropsbehandlare utlöses endast i ett av två fall: när den specificerade funktionen anropas av ett konto som inte är kontraktet självt eller när den är markerad som extern i Solidity och anropas som en del av en annan funktion i samma kontrakt.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Definiera en Anropsbehandlare
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: "0x731a10897d267e19b34503ad902d0a29173ba4b1"
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Kartläggningsfunktion
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from "../generated/Gravity/Gravity";
+import { Transaction } from "../generated/schema";
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash;
+  let transaction = new Transaction(id);
+  transaction.displayName = call.inputs._displayName;
+  transaction.imageUrl = call.inputs._imageUrl;
+  transaction.save();
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Blockbehandlare
+
+Förutom att prenumerera på kontrakts händelser eller funktionsanrop kan en subgraf vilja uppdatera sina data när nya block läggs till i kedjan. För att uppnå detta kan en subgraf köra en funktion efter varje block eller efter block som matchar en fördefinierad filter.
+
+### Stödda filter
+
+#### Anropsfilter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+Avsaknaden av ett filter för en blockhanterare kommer att säkerställa att hanteraren kallas för varje block. En datakälla kan endast innehålla en blockhanterare för varje filttyp.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: "0x731a10897d267e19b34503ad902d0a29173ba4b1"
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Undersökningsfilter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### En Gång Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Den definierade hanteraren med filtret once kommer att anropas endast en gång innan alla andra hanterare körs. Denna konfiguration gör det möjligt för subgrafen att använda hanteraren som en initialiseringshanterare, som utför specifika uppgifter i början av indexeringen.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8("initial"));
+  data.data = "Setup data here";
+  data.save();
+}
+```
+
+### Kartläggningsfunktion
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from "@graphprotocol/graph-ts";
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash;
+  let entity = new Block(id);
+  entity.save();
+}
+```
+
+## Anonyma händelser
+
+Om du behöver behandla anonyma händelser i Solidity kan du göra det genom att ange händelsens ämne 0, som i exemplet:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaktionskvitton i Händelsehanterare
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+Utlösarna för en datakälla inom ett block ordnas med hjälp av följande process:
+
+1. Händelse- och anropsutlösare ordnas först efter transaktionsindex inom blocket.
+2. Händelse- och anropsutlösare inom samma transaktion ordnas med hjälp av en konvention: händelseutlösare först, sedan anropsutlösare, varje typ respekterar ordningen de definieras i manifestet.
+3. Blockutlösare körs efter händelse- och anropsutlösare, i den ordning de definieras i manifestet.
+
+Dessa ordningsregler kan komma att ändras.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Datakällmallar
+
+En vanlig mönster i EVM-kompatibla smarta kontrakt är användningen av register- eller fabrikskontrakt, där ett kontrakt skapar, hanterar eller hänvisar till ett godtyckligt antal andra kontrakt som var och en har sin egen stat och händelser.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Datakälla för huvudkontraktet
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: "0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95"
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Datakällmallar för dynamiskt skapade kontrakt
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instansiering av en mall för datakälla
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from "../generated/templates";
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange);
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Om tidigare block innehåller data som är relevanta för den nya datakällan, är det bäst att indexera dessa data genom att läsa kontraktets aktuella status och skapa enheter som representerar denna status vid den tidpunkt då den nya datakällan skapas.
+
+### Kontext för datakälla
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from "../generated/templates";
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext();
+  context.setString("tradingPair", event.params.tradingPair);
+  Exchange.createWithContext(event.params.exchange, context);
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from "@graphprotocol/graph-ts";
+
+let context = dataSource.context();
+let tradingPair = context.getString("tradingPair")
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Startblock
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: "0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95"
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Sök efter kontraktet genom att ange dess adress i sökfältet.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Ladda sidan med transaktionsdetaljer där du hittar startblocket för det kontraktet.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 0bd93fe3daf2dd863ed164e1668c69ee25a7a38b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:39 -0500
Subject: [PATCH 0301/1325] New translations index.json (Ukrainian)

---
 website/pages/uk/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/uk/index.json b/website/pages/uk/index.json
index 3d97cf38ab78..8ecfe9f81e56 100644
--- a/website/pages/uk/index.json
+++ b/website/pages/uk/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "Дослідження субграфів та їх взаємодія з протоколом"
-      },
-      "hostedService": {
-        "title": "Хостинговий сервіс",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From 88edd893682b6eff338056648222021c1ae3081c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:40 -0500
Subject: [PATCH 0302/1325] New translations index.json (Chinese Simplified)

---
 website/pages/zh/index.json | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/website/pages/zh/index.json b/website/pages/zh/index.json
index d835765acd38..7be9a7ca1935 100644
--- a/website/pages/zh/index.json
+++ b/website/pages/zh/index.json
@@ -21,8 +21,7 @@
     "createASubgraph": {
       "title": "创建子图",
       "description": "在子图工作室中创建子图"
-    },
-    "migrateFromHostedService": {}
+    }
   },
   "networkRoles": {
     "title": "网络角色",
@@ -57,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph 浏览器",
         "description": "探索子图并与协议互动"
-      },
-      "hostedService": {
-        "title": "托管服务",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From e4c9001ca95eb1b228e8572fb2615773c5631e1d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:41 -0500
Subject: [PATCH 0303/1325] New translations index.json (Urdu (Pakistan))

---
 website/pages/ur/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/ur/index.json b/website/pages/ur/index.json
index 9fbd9c4b80fe..9065fe445b9a 100644
--- a/website/pages/ur/index.json
+++ b/website/pages/ur/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "گراف ایکسپلورر",
         "description": "سب گرافس کو دریافت کریں اور پروٹوکول کے ساتھ ہم آہنگی کریں"
-      },
-      "hostedService": {
-        "title": "ہوسٹڈ سروس",
-        "description": "ہوسٹڈ سروس پر سب گرافس بنائیں اور دریافت کریں"
       }
     }
   },

From 81a6f9407b948eef1400773d3d02419832d0624e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:42 -0500
Subject: [PATCH 0304/1325] New translations index.json (Vietnamese)

---
 website/pages/vi/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/vi/index.json b/website/pages/vi/index.json
index f8e880b2de89..8d84655f79d8 100644
--- a/website/pages/vi/index.json
+++ b/website/pages/vi/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Trình khám phá Graph",
         "description": "Khám phá các subgraph và tương tác với giao thức"
-      },
-      "hostedService": {
-        "title": "Dịch vụ được lưu trữ",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From f9646f29f2122265f9206ba3d639fa61bf9c8f33 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:43 -0500
Subject: [PATCH 0305/1325] New translations near.mdx (Turkish)

---
 website/pages/tr/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/tr/cookbook/near.mdx b/website/pages/tr/cookbook/near.mdx
index 3ad356c663a8..e55819a7d0e7 100644
--- a/website/pages/tr/cookbook/near.mdx
+++ b/website/pages/tr/cookbook/near.mdx
@@ -37,7 +37,7 @@ Subgraph tanımının üç yönü vardır:
 
 **schema.graphql:** Subgraph'ınız için hangi verilerin depolandığını ve bunlara GraphQL aracılığıyla nasıl sorgu yapılacağını tanımlayan bir şema dosyası. NEAR subgraph gereksinimleri [mevcut belgelendirmede](/developing/creating-a-subgraph#the-graphql-schema) ele alınmıştır.
 
-**AssemblyScript Eşleştirmeleri:** Olay verilerini şemanızda tanımlanan varlıklara çeviren [AssemblyScript kodu](/developing/graph-ts/api). NEAR desteği, NEAR'a özgü veri tiplerini ve yeni JSON ayrıştırma fonksiyonelliğini tanıtır.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 Subgraph geliştirme sırasında iki temel komut bulunmaktadır:
 
@@ -98,7 +98,7 @@ NEAR veri kaynakları iki tür işleyiciyi destekler:
 
 Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır.
 
-NEAR indeksleme,[AssemblyScript API](/developing/graph-ts/api)'sine NEAR'a özgü veri tipleri ekler.
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ Bu türler blok & makbuz işleyicilerine aktarılır:
 - Blok işleyicileri bir `Block` alır
 - Makbuz işleyicileri bir `ReceiptWithOutcome` alır
 
-Aksi takdirde, [AssemblyScript API](/developing/graph-ts/api)'sinin geri kalanı eşleştirme yürütmesi sırasında NEAR subgraph geliştiricileri tarafından kullanılabilir.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-Buna yeni bir JSON ayrıştırma fonksiyonuda dahildir - NEAR'daki kayıtlar sıklıkla dizilmiş JSON'lar olarak yayılır. Yeni bir `json.fromString(...)` fonksiyonu, geliştiricilerin bu kayıtları kolayca işlemesine olanak sağlamak için [JSON API](/developing/graph-ts/api#json-api)'nin bir parçası olarak mevcuttur.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## NEAR Subgraph'ını Dağıtma
 
@@ -194,8 +194,8 @@ Düğüm yapılandırması, subgraph'ın nerede dağıtıldığına bağlı olac
 ### Subgraph Stüdyosu
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Yerel Graph Düğümü (varsayılan yapılandırmaya göre)

From 3b2fb5d476632ff0fd9ed436962c25a51c134755 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:44 -0500
Subject: [PATCH 0306/1325] New translations about.mdx (Ukrainian)

---
 website/pages/uk/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/uk/about.mdx b/website/pages/uk/about.mdx
index 0ee69ee29eca..ebc3f6d6f360 100644
--- a/website/pages/uk/about.mdx
+++ b/website/pages/uk/about.mdx
@@ -2,46 +2,66 @@
 title: Про The Graph
 ---
 
-На цій сторінці ви дізнаєтесь, що таке The Graph і як ви можете розпочати працювати з ним.
-
 ## Що таке The Graph?
 
-The Graph - це децентралізований протокол для індексації та запитів щодо даних блокчейну. The Graph дозволяє робити запити про дані, які важко отримати безпосередньо.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Проєкти зі складними смартконтрактами, такі як [Uniswap](https://uniswap.org/), також НФТ проєкти, до прикладу - [Bored Ape Yacht Club](https://boredapeyachtclub.com/) зберігають свої дані на блокчейні Ethereum. Це робить практично неможливим зчитування будь-чого, окрім основних даних безпосередньо з блокчейну.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-Ви також можете створити власний сервер, обробляти транзакції на ньому, зберігати їх у базі даних і створити на ньому кінцеву точку API для запиту даних. Проте, цей варіант дуже [ресурсозатратний](/network/benefits/), потребує регулярного обслуговування, являє собою єдину точку збою, а також порушує важливі особливості безпеки, що необхідні для децентралізації.
+### How The Graph Functions
 
-**Індексування даних блокчейну це дуже важке заняття.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Як працює The Graph
+- 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.
 
-The Graph вивчає що і як індексувати в даних Ethereum за допомогою описів до підграфів, які називаються підграф маніфестами. Цей опис допомагає визначити смартконтракти, які представляють певний інтерес для підграфа, також події, що відбулись в цих смартконтрактах, на які варто звернути увагу, а також допомагає зіставити дані про ці події з тими даними, які The Graph буде зберігати у своїй базі даних.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Після того як ви написали `підграф маніфест`, використовуйте the Graph CLI, щоб зберегти значення в IPFS і вказати індексатору почати тестування даних для цього підграфа.
+- 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.
 
-На цій діаграмі більш детально показано потік даних, що стосуються транзакцій в Ethereum, одразу після розгортання підграф маніфесту:
+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 постійно сканує Ethereum на наявність нових блоків і даних для вашого підграфа, які вони можуть містити.
-4. Graph Node знаходить події на Ethereum для вашого підграфа в цих блоках і запускає надані вами mapping handlers. Mapping - це модуль WASM, який створює або оновлює структуру даних, що зберігаються у Graph Node у відповідь на події на Ethereum.
-5. Додаток запитує Graph Node про дані, проіндексовані в блокчейні, використовуючи [кінцеву точку GraphQL](https://graphql.org/learn/). The Graph Node, і собі, переводить запити GraphQL в запити до свого базового сховища даних, щоб отримати ці дані, використовуючи можливості індексації сховища. Dapp відображає ці дані в величезному інтерфейсі для кінцевих користувачів, який вони використовують для створення нових транзакцій на Ethereum. Цикл повторюється.
+1.  Додаток відправляє дані в мережу Ethereum через транзакцію в смартконтракті.
+2.  Під час обробки транзакції смартконтракт видає одну або декілька різних подій.
+3.  Graph Node постійно сканує Ethereum на наявність нових блоків і даних для вашого підграфа, які вони можуть містити.
+4.  Graph Node знаходить події на Ethereum для вашого підграфа в цих блоках і запускає надані вами mapping handlers. Mapping - це модуль WASM, який створює або оновлює структуру даних, що зберігаються у Graph Node у відповідь на події на Ethereum.
+5.  Додаток запитує Graph Node про дані, проіндексовані в блокчейні, використовуючи [кінцеву точку GraphQL](https://graphql.org/learn/). The Graph Node, і собі, переводить запити GraphQL в запити до свого базового сховища даних, щоб отримати ці дані, використовуючи можливості індексації сховища. Dapp відображає ці дані в величезному інтерфейсі для кінцевих користувачів, який вони використовують для створення нових транзакцій на Ethereum. Цикл повторюється.
 
 ## Наступні кроки
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 9049fc3d6e45f29881b89f3c1b08d6eefc1fdd4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:46 -0500
Subject: [PATCH 0307/1325] New translations near.mdx (Ukrainian)

---
 website/pages/uk/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/uk/cookbook/near.mdx b/website/pages/uk/cookbook/near.mdx
index 5e01cd954498..3d72ba528304 100644
--- a/website/pages/uk/cookbook/near.mdx
+++ b/website/pages/uk/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Субграф Студія
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From f282627bb6264a06337de6be783e80cea051539c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:47 -0500
Subject: [PATCH 0308/1325] New translations unit-testing-framework.mdx
 (Ukrainian)

---
 .../uk/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/uk/developing/unit-testing-framework.mdx b/website/pages/uk/developing/unit-testing-framework.mdx
index 0898dbdd5638..53a5c43dedcf 100644
--- a/website/pages/uk/developing/unit-testing-framework.mdx
+++ b/website/pages/uk/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Usage
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From c5d5e958945d8f86c3146111f0966822e48bd198 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:48 -0500
Subject: [PATCH 0309/1325] New translations about.mdx (Chinese Simplified)

---
 website/pages/zh/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/zh/about.mdx b/website/pages/zh/about.mdx
index c7f09a215cfd..d057befe67cf 100644
--- a/website/pages/zh/about.mdx
+++ b/website/pages/zh/about.mdx
@@ -2,46 +2,66 @@
 title: 关于 Graph
 ---
 
-本页将解释什么是 Graph，以及你将如何开始。
-
 ## 什么是Graph？
 
-Graph 是一个去中心化的协议，用于索引和查询区块链的数据。 它使查询那些难以直接查询的数据成为可能。
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-像 [Uniswap](https://uniswap.org/)这样具有复杂智能合约的项目，以及像 [Bored Ape Yacht Club](https://boredapeyachtclub.com/) 这样的 NFTs 倡议，都在以太坊区块链上存储数据，因此，除了直接从区块链上读取基本数据外，真的很难。
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-你也可以建立你自己的服务器，在那里处理交易，把它们保存到数据库，并在上面建立一个 API 终端，以便查询数据。 然而，这种选择是[资源密集型的](/network/benefits/)，需要维护，会出现单点故障，并破坏了去中心化化所需的重要安全属性。
+### How The Graph Functions
 
-**为区块链数据编制索引真的非常非常难。**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Graph 是如何工作的
+- 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.
 
-Graph基于子图描述（称为子图清单）学习如何索引以太坊数据。子图描述定义了子图感兴趣的智能合约、要注意的合约中的事件，以及如何将事件数据映射到Graph将存储在其数据库中的数据。
+- When creating a subgraph, you need to write a subgraph manifest.
 
-一旦编写了`子图清单`，就可以使用Graph CLI将定义存储在IPFS中，并告诉索引人开始为该子图的数据编制索引。
+- 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.
 
-此图提供了部署子图清单后用于处理以太坊交易的数据流的更多细节
+The diagram below provides more detailed information about the flow of data after a subgraph manifest has been deployed with Ethereum transactions.
 
 ![一图解释Graph如何使用Graph节点向数据消费者提供查询的图形](/img/graph-dataflow.png)
 
 流程遵循这些步骤：
 
-1. 一个去中心化的应用程序通过智能合约上的交易向以太坊添加数据。
-2. 智能合约在处理交易时，会发出一个或多个事件。
-3. Graph 节点不断扫描以太坊的新区块和它们可能包含的子图的数据。
-4. Graph 节点在这些区块中为你的子图找到以太坊事件并运行你提供的映射处理程序。 映射是一个 WASM 模块，它创建或更新 Graph 节点存储的数据实体，以响应以太坊事件。
-5. 去中心化的应用程序使用Graph节点的[GraphQL 端点](https://graphql.org/learn/)，从区块链的索引中查询 Graph 节点的数据。 Graph 节点反过来将 GraphQL 查询转化为对其底层数据存储的查询，以便利用存储的索引功能来获取这些数据。 去中心化的应用程序在一个丰富的用户界面中为终端用户显示这些数据，他们用这些数据在以太坊上发行新的交易。 就这样周而复始。
+1.  一个去中心化的应用程序通过智能合约上的交易向以太坊添加数据。
+2.  智能合约在处理交易时，会发出一个或多个事件。
+3.  Graph 节点不断扫描以太坊的新区块和它们可能包含的子图的数据。
+4.  Graph 节点在这些区块中为你的子图找到以太坊事件并运行你提供的映射处理程序。 映射是一个 WASM 模块，它创建或更新 Graph 节点存储的数据实体，以响应以太坊事件。
+5.  去中心化的应用程序使用Graph节点的[GraphQL 端点](https://graphql.org/learn/)，从区块链的索引中查询 Graph 节点的数据。 Graph 节点反过来将 GraphQL 查询转化为对其底层数据存储的查询，以便利用存储的索引功能来获取这些数据。 去中心化的应用程序在一个丰富的用户界面中为终端用户显示这些数据，他们用这些数据在以太坊上发行新的交易。 就这样周而复始。
 
 ## 下一步
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From c04ec814c0cf27a7257013d9b3fc6fe6fcb25c53 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:49 -0500
Subject: [PATCH 0310/1325] New translations near.mdx (Chinese Simplified)

---
 website/pages/zh/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/zh/cookbook/near.mdx b/website/pages/zh/cookbook/near.mdx
index df65a6ecb44b..25598b11f46d 100644
--- a/website/pages/zh/cookbook/near.mdx
+++ b/website/pages/zh/cookbook/near.mdx
@@ -37,7 +37,7 @@ NEAR 子图开发需要`0.23.0`以上版本的`graph-cli`，以及 `0.23.0`以
 
 **schema.graphql:** 一个模式文件，定义子图存储的数据以及如何通过 GraphQL 查询数据。NEAR 子图的要求已经在[现有的文档](/developing/creating-a-subgraph#the-graphql-schema)中介绍了。
 
-**AssemblyScript 映射**: 从事件数据转换为模式中定义的实体的[ AssemblyScript 代码](/developing/graph-ts/api)。NEAR 支持引入了特定于 NEAR 的数据类型和新的 JSON 解析功能。
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 在子图开发过程中，有两个关键命令：
 
@@ -98,7 +98,7 @@ NEAR 数据源支持两种类型的处理程序：
 
 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。
 
-NEAR 索引向 [AssemblyScriptAPI](/developing/graph-ts/api) 引入了特定于 NEAR 的数据类型。
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ class ReceiptWithOutcome {
 - 块处理程序将收到 `Block`
 - 收据处理程序将收到 `ReceiptWithOutcome`
 
-否则，在映射执行期间，NEAR 子图开发人员可以使用 [AssemblyScriptAPI](/developing/graph-ts/api) 的其余部分。
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-这包括一个新的 JSON 解析函数—— NEAR 上的日志经常作为带字符串的 JSONs 发出。作为[JSON API](/developing/graph-ts/api#json-api)的一部分，可以使用一个新的 `json.fromString(...)`函数来允许开发人员轻松地处理这些日志。
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## 部署 NEAR 子图
 
@@ -194,8 +194,8 @@ $ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <su
 ### 子图工作室
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### 本地Graph节点（基于默认配置）

From db7bf9e0282b1522a9bf8b89c0c0ad8adb7e7e02 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:51 -0500
Subject: [PATCH 0311/1325] New translations unit-testing-framework.mdx
 (Chinese Simplified)

---
 .../zh/developing/unit-testing-framework.mdx  | 51 ++++++++++++-------
 1 file changed, 32 insertions(+), 19 deletions(-)

diff --git a/website/pages/zh/developing/unit-testing-framework.mdx b/website/pages/zh/developing/unit-testing-framework.mdx
index fcb21ab1244b..f5b3d4e5f28c 100644
--- a/website/pages/zh/developing/unit-testing-framework.mdx
+++ b/website/pages/zh/developing/unit-testing-framework.mdx
@@ -2,43 +2,52 @@
 title: 单元测试框架
 ---
 
-Matchstick 是一个单元测试框架，由[LimeChain](https://limechain.tech/)开发，使子图开发者能够在沙盒环境中测试他们的映射逻辑，并放心地部署他们的子图。
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## 开始
 
-### 安装依赖项
+### Install Dependencies
 
-为了使用测试帮助器方法并运行测试，您需要安装以下依赖项:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` 依赖于 PostgreSQL，因此如果您还没有它，就需要安装它。我们强烈建议使用下面的命令，因为以任何其他方式添加它可能会导致意外的错误！
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres 安装命令:
+Installation command:
 
 ```sh
 brew install postgresql
 ```
 
-创建到最新 libpq.5. lib* 的符号链接，可能需要首先创建这个目录*`/usr/local/opt/postgreql/lib/`
+创建到最新 libpq.5. lib_ 的符号链接，可能需要首先创建这个目录_`/usr/local/opt/postgreql/lib/`
 
 ```sh
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres 安装命令(取决于您的发行版):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL（用于 Linux 的 Windows 子系统）
+### Using WSL (Windows Subsystem for Linux)
 
 可以使用 Docker 方法和二进制方法在 WSL 上使用 Matchstick。由于 WSL 可能有点复杂，所以这里有一些提示，以防您遇到诸如
 
@@ -76,7 +85,7 @@ sudo apt-get install libpq-dev
 }
 ```
 
-### 使用方法
+### Using Matchstick
 
 要在子图项目中使用**Matchstick**，只需打开一个终端，导航到项目的根文件夹，然后简单地运行`graph test [options] <datasource>`-它下载最新的**Matchstick**二进制文件，并在测试文件夹中运行指定的测试或所有测试（如果未指定数据源标志，则运行所有现有测试）。
 
@@ -227,7 +236,7 @@ test("handleNewGravatar() should create a new entity", () => {
 
 例子：
 
-`beforeAll`中的代码将在文件中的*all*测试之前执行一次。
+`beforeAll`中的代码将在文件中的_all_测试之前执行一次。
 
 ```typescript
 import { describe, test, beforeAll } from "matchstick-as/assembly/index"
@@ -287,7 +296,7 @@ describe("handleUpdatedGravatar()", () => {
 
 例子:
 
-`afterAll`中的代码将在文件中的*all*测试之后执行一次。
+`afterAll`中的代码将在文件中的_all_测试之后执行一次。
 
 ```typescript
 import { describe, test, afterAll } from "matchstick-as/assembly/index"
@@ -1368,22 +1377,26 @@ Global test coverage: 22.2% (2/9 handlers).
 
 > 关键：无法从具有背景的有效模块创建WasmInstance：未知导入：wasi_snapshot_preview1:：尚未定义fd_write
 
-这意味着您在代码中使用了`console.log`，而AssemblyScript不支持此选项。请考虑使用[日志API](/developing/graph-ts/api/#logging-api)
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > 返回ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > 返回新ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 参数不匹配是由`graph-ts` and `matchstick-as`不匹配造成的。解决此类问题的最佳方法是将所有内容更新到最新发布的版本。
 
+## 其他资源
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## 反馈
 
 如果您有任何问题、反馈、特征请求或只是想与我们联系，最好的地方是 Graph Discord，我们有一个专门的 Matchstick 频道，名为 🔥| 单元测试。

From 9a7cac9d0504ebcd4ffb7dbb11be549c116555e2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:52 -0500
Subject: [PATCH 0312/1325] New translations about.mdx (Urdu (Pakistan))

---
 website/pages/ur/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/ur/about.mdx b/website/pages/ur/about.mdx
index 128488977220..9d53ba42d773 100644
--- a/website/pages/ur/about.mdx
+++ b/website/pages/ur/about.mdx
@@ -2,46 +2,66 @@
 title: گراف کے بارے میں
 ---
 
-یہ صفحہ وضاحت کرے گا کہ گراف کیا ہے اور آپ کیسے شروع کر سکتے ہیں.
-
 ## گراف کیا ہے؟
 
-گراف بلاکچین ڈیٹا کی انڈیکسنگ اور کیوری کے لیے ایک ڈیسینٹرالائزڈ پروٹوکول ہے۔ گراف ڈیٹا سے کیوری کرنا ممکن بناتا ہے جس سے براہ راست کیوری کرنا مشکل ہے.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-پیچیدہ سمارٹ کنٹریکٹس والے پروجیکٹس جیسے [Uniswap](https://uniswap.org/) اور NFTs کے اقدامات جیسا کہ [بورڈ ایپ یاٹ کلب](https://boredapeyachtclub.com/) ایتھیریم بلاکچین پر ڈیٹا ذخیزہ کرتے ہیں, جس سے بلاکچین سے براہ راست بنیادی ڈیٹا کے علاوہ کچھ بھی پڑھنا کافی مشکل ہوجاتا ہے.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-آپ اپنا سرور بھی بنا سکتے ہیں، وہاں لین دین پر کارروائی کر سکتے ہیں، انہیں ڈیٹا بیس میں محفوظ کر سکتے ہیں، اور ڈیٹا سے کیوری کرنے کے لیے ان سب کے اوپر ایک API اینڈ پوائنٹ بنا سکتے ہیں۔ تاہم، یہ آپشن [وسائل کی گہرائی](/network/benefits/) ہے، دیکھ بھال کی ضرورت ہے، ناکامی کا ایک نقطہ پیش کرتا ہے، اور ڈیسینٹرالائزیشن کے لیے ضروری حفاظتی خصوصیات کو توڑ دیتا ہے.
+### How The Graph Functions
 
-**بلاکچین ڈیٹا کو انڈیکس کرنا بہت، بہت مشکل ہے.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- 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.
 
-ایک بار جب آپ `سب گراف مینی فیسٹ` لکھ لیتے ہیں،آپ IPFS میں تعریف کو ذخیرہ کرنے کے لیے گراف CLI کا استعمال کرتے ہیں اور انڈیکسر سے کہتے ہیں کہ اس سب گراف کے لیے ڈیٹا انڈیکس کرنا شروع کرے.
+- 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.
 
-یہ خاکہ ڈیٹا کے بہاؤ کے بارے میں مزید تفصیل دیتا ہے ایک بار جب سب گراف مینی فیسٹ تعین ہو چکا ہو, ایتھیریم ٹرانزیکشنز سے نمٹتے ہوئے:
+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. گراف نوڈ ایتھیریم کو نئے بلاکس اور آپ کے سب گراف کے ڈیٹا کے لیے مسلسل سکین کرتا ہے.
-4. گراف نوڈ ان بلاکس میں آپ کے سب گراف کے لیے ایتھریم ایونٹس تلاش کرتا ہے اور آپ کے فراہم کردہ میپنگ ہینڈلرز کو چلاتا ہے. میپنگ ایک WASM ماڈیول ہے جو ڈیٹا ہستیوں کو تخلیق یا اپ ڈیٹ کرتا ہے جو ایتھیریم ایونٹس کے جواب میں گراف نوڈ ذخیرہ کرتا ہے.
-5. ڈیپ بلاکچین سے انڈیکس کردہ ڈیٹا کے لیے گراف نوڈ کو کیوری کرتی ہے, نوڈ کے [GraphQL اینڈ پوائنٹ](https://graphql.org/learn/) کا استعمال کرتے ہوئے. گراف نوڈ بدلے میں اس ڈیٹا کو حاصل کرنے کے لیے GraphQL کی کیوریز کو اپنے بنیادی ڈیٹا اسٹور کی کیوریز میں تبدیل کرتا ہے, سٹور کی انڈیکسنگ کی صلاحیتوں کا استعمال کرتے ہوئے. ڈیسینٹرلائزڈ ایپلیکیشن اس ڈیٹا کو صارفین کے لیے ایک بھرپور UI میں دکھاتی ہے, جسے وہ ایتھیریم پر نئی ٹرانزیکشنز جاری کرنے کے لیے استعمال کرتے ہیں. یہ سلسلہ دہرایا جاتا ہے.
+1.  ایک ڈیپ سمارٹ کنٹریکٹ پر ٹرانزیکشن کے ذریعے سے ایتھیریم میں ڈیٹا کا اضافہ کرتی ہے.
+2.  سمارٹ کنٹریکٹ ٹرانزیکشن پر کارروائی کے دوران ایک یا ایک سے زیادہ واقعات کا اخراج کرتا ہے.
+3.  گراف نوڈ ایتھیریم کو نئے بلاکس اور آپ کے سب گراف کے ڈیٹا کے لیے مسلسل سکین کرتا ہے.
+4.  گراف نوڈ ان بلاکس میں آپ کے سب گراف کے لیے ایتھریم ایونٹس تلاش کرتا ہے اور آپ کے فراہم کردہ میپنگ ہینڈلرز کو چلاتا ہے. میپنگ ایک WASM ماڈیول ہے جو ڈیٹا ہستیوں کو تخلیق یا اپ ڈیٹ کرتا ہے جو ایتھیریم ایونٹس کے جواب میں گراف نوڈ ذخیرہ کرتا ہے.
+5.  ڈیپ بلاکچین سے انڈیکس کردہ ڈیٹا کے لیے گراف نوڈ کو کیوری کرتی ہے, نوڈ کے [GraphQL اینڈ پوائنٹ](https://graphql.org/learn/) کا استعمال کرتے ہوئے. گراف نوڈ بدلے میں اس ڈیٹا کو حاصل کرنے کے لیے GraphQL کی کیوریز کو اپنے بنیادی ڈیٹا اسٹور کی کیوریز میں تبدیل کرتا ہے, سٹور کی انڈیکسنگ کی صلاحیتوں کا استعمال کرتے ہوئے. ڈیسینٹرلائزڈ ایپلیکیشن اس ڈیٹا کو صارفین کے لیے ایک بھرپور UI میں دکھاتی ہے, جسے وہ ایتھیریم پر نئی ٹرانزیکشنز جاری کرنے کے لیے استعمال کرتے ہیں. یہ سلسلہ دہرایا جاتا ہے.
 
 ## اگلے مراحل
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From fc1e4c93589502edc98e2e1bb946defcdfa98524 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:53 -0500
Subject: [PATCH 0313/1325] New translations near.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/near.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/ur/cookbook/near.mdx b/website/pages/ur/cookbook/near.mdx
index 9f37ea21f262..30855c266732 100644
--- a/website/pages/ur/cookbook/near.mdx
+++ b/website/pages/ur/cookbook/near.mdx
@@ -37,7 +37,7 @@ NEAR سب گراف ڈیولپمنٹ کے لیے `graph-cli` اوپر والے و
 
 ** schema.graphql:** ایک اسکیما فائل جو اس بات کی وضاحت کرتی ہے کہ آپ کے سب گراف کے لیے کون سا ڈیٹا محفوظ کیا جاتا ہے، اور GraphQL کے ذریعے اس سے کیوری کیسے کیا جائے۔ NEAR سب گراف کے تقاضوں کا احاطہ [موجودہ دستاویزات](/developing/creating-a-subgraph#the-graphql-schema) سے ہوتا ہے.
 
-**اسمبلی اسکرپٹ میپنگس:** [اسمبلی اسکرپٹ کوڈ](/developing/graph-ts/api) جو ایونٹ کے ڈیٹا سے آپ کے اسکیما میں بیان کردہ ہستیوں میں ترجمہ کرتا ہے۔ NEAR سپورٹ NEAR-مخصوص ڈیٹا کی اقسام اور نئی JSON پارسنگ فعالیت کو متعارف کراتی ہے.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 سب گراف کی ترقی کے دوران دو اہم کمانڈز ہیں:
 
@@ -70,7 +70,7 @@ dataSources:
       file: ./src/mapping.ts # link to the file with the Assemblyscript mappings
 ```
 
-- NEAR سب گراف ڈیٹا ماخذ کا ایک نیا `kind` متعارف کراتے ہیں (`near`)
+- NEAR سب گراف ڈیٹا ماخذ کا ایک نیا ` kind ` متعارف کراتے ہیں (`near`)
 - The `network` should correspond to a network on the hosting Graph Node. On Subgraph Studio, NEAR's mainnet is `near-mainnet`, and NEAR's testnet is `near-testnet`
 - NEAR data sources introduce an optional `source.account` field, which is a human-readable ID corresponding to a [NEAR account](https://docs.near.org/concepts/protocol/account-model). This can be an account or a sub-account.
 - NEAR ڈیٹا کے ذرائع ایک متبادل اختیاری `source.accounts` فیلڈ متعارف کراتے ہیں، جس میں اختیاری لاحقے اور سابقے ہوتے ہیں۔ کم از کم سابقہ ​​یا لاحقہ متعین ہونا ضروری ہے، وہ بالترتیب اقدار کی فہرست کے ساتھ شروع یا ختم ہونے والے کسی بھی اکاؤنٹ سے مماثل ہوں گے۔ نیچے دی گئی مثال مماثل ہوگی: `[app|good].*[morning.near|morning.testnet]`۔ اگر صرف سابقوں یا لاحقوں کی فہرست ضروری ہو تو دوسری فیلڈ کو چھوڑا جا سکتا ہے.
@@ -98,7 +98,7 @@ accounts:
 
 پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں.
 
-NEAR انڈیکسنگ NEAR-مخصوص ڈیٹا کی اقسام کو [اسمبلی اسکرپٹ API](/developing/graph-ts/api) میں متعارف کراتی ہے.
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ class ReceiptWithOutcome {
 - بلاک ہینڈلرز کو ایک `Block` ملے گا
 - ریسیپٹ ہینڈلرز کو ایک `ReceiptWithOutcome` ملے گا
 
-بصورت دیگر، باقی [اسمبلی اسکرپٹ API](/developing/graph-ts/api) نقشہ سازی کے عمل کے دوران NEAR سب گراف ڈویلپرز کے لیے دستیاب ہے.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-اس میں ایک نیا JSON پارسنگ فنکشن شامل ہے - NEAR پر لاگز کثرت سے سٹرنگیفائڈ JSONs کے طور پر خارج ہوتے ہیں۔ ڈویلپرز کو اجازت دینے کے لیے ایک نیا `json.fromString(...)` فنکشن [JSON API](/developing/graph-ts/api#json-api) کے حصے کے طور پر دستیاب ہے۔ آسانی سے ان لاگز پر کارروائی کرنے کے لیے.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## NEAR سب گراف کی تعیناتی
 
@@ -194,8 +194,8 @@ $ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <su
 ### سب گراف سٹوڈیو
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### مقامی گراف نوڈ (پہلے سے طے شدہ ترتیب پر مبنی)
@@ -254,7 +254,7 @@ NEAR سپورٹ بیٹا میں ہے، جس کا مطلب ہے کہ API میں 
 
 ### کیا رسید ہینڈلرز اکاؤنٹس اور ان کے سب اکاؤنٹس کو متحرک کریں گے؟
 
-اگر ایک `account` متعین کیا گیا ہے، تو وہ صرف صحیح اکاؤنٹ کے نام سے مماثل ہوگا۔ مثال کے طور پر، اکاؤنٹس اور سب اکاؤنٹس سے ملنے کے لیے مخصوص `prefixes` اور ` suffixes` کے ساتھ، `accounts` فیلڈ کی وضاحت کرکے سب اکاؤنٹس کو ملانا ممکن ہے۔ درج ذیل تمام `mintbase1.near` سب اکاؤنٹس سے مماثل ہوں گے:
+اگر ایک ` account ` متعین کیا گیا ہے، تو وہ صرف صحیح اکاؤنٹ کے نام سے مماثل ہوگا۔ مثال کے طور پر، اکاؤنٹس اور سب اکاؤنٹس سے ملنے کے لیے مخصوص ` prefixes ` اور ` suffixes` کے ساتھ، `accounts` فیلڈ کی وضاحت کرکے سب اکاؤنٹس کو ملانا ممکن ہے۔ درج ذیل تمام `mintbase1.near` سب اکاؤنٹس سے مماثل ہوں گے:
 
 ```yaml
 accounts:

From 8fcc3e19d267f42be9cc39aecfc4c309a311984c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:54 -0500
Subject: [PATCH 0314/1325] New translations unit-testing-framework.mdx (Urdu
 (Pakistan))

---
 .../ur/developing/unit-testing-framework.mdx  | 45 ++++++++++++-------
 1 file changed, 29 insertions(+), 16 deletions(-)

diff --git a/website/pages/ur/developing/unit-testing-framework.mdx b/website/pages/ur/developing/unit-testing-framework.mdx
index 9f84b69bd3fc..23e3d1695189 100644
--- a/website/pages/ur/developing/unit-testing-framework.mdx
+++ b/website/pages/ur/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: یونٹ ٹیسٹنگ فریم ورک
 ---
 
-Matchstick ایک یونٹ ٹیسٹنگ فریم ورک ہے، جسے [LimeChain](https://limechain.tech/) نے تیار کیا ہے، جو سب گراف ڈویلپرز کو اس قابل بناتا ہے کہ وہ سینڈ باکس والے ماحول میں اپنی میپنگ منطق کی جانچ کر سکیں اور اپنے سب گراف کو اعتماد کے ساتھ تعینات کر سکیں!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## شروع ہوا چاہتا ہے
 
-### انحصار انسٹال کریں
+### Install Dependencies
 
-ٹیسٹ مددگار طریقوں کو استعمال کرنے اور ٹیسٹ چلانے کے لیے، آپ کو درج ذیل انحصار کو انسٹال کرنے کی ضرورت ہوگی:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` PostgreSQL پر منحصر ہے، لہذا اگر آپ کے پاس یہ پہلے سے نہیں ہے، تو آپ کو اسے انسٹال کرنا ہوگا۔ ہم نیچے دیے گئے کمانڈز کو استعمال کرنے کا مشورہ دیتے ہیں کیونکہ اسے کسی اور طریقے سے شامل کرنے سے غیر متوقع غلطی ہو سکتی ہے!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres انسٹالیشن کمانڈ:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ brew install postgresql
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres انسٹالیشن کمانڈ (آپ کے ڈسٹرو پر منحصر ہے):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (لی نکس کے لیے ونڈوز سب سسٹم)
+### Using WSL (Windows Subsystem for Linux)
 
 آپ ڈوکر اپروچ اور بائنری اپروچ دونوں کا استعمال کرتے ہوئے WSL پر Matchstick استعمال کر سکتے ہیں۔ جیسا کہ WSL تھوڑا مشکل ہوسکتا ہے، اگر آپ کو اس طرح کے مسائل کا سامنا کرنا پڑتا ہے تو یہاں کچھ تجاویز ہیں
 
@@ -76,7 +85,7 @@ sudo apt-get install libpq-dev
 }
 ```
 
-### استعمال
+### Using Matchstick
 
 اپنے سب گراف پروجیکٹ میں **Matchstick** استعمال کرنے کے لیے بس ایک ٹرمینل کھولیں، اپنے پروجیکٹ کے روٹ فولڈر پر جائیں اور بس `graph test [options] <datasource> ` - یہ تازہ ترین **Matchstick** بائنری ڈاؤن لوڈ کرتا ہے اور مخصوص ٹیسٹ یا ٹیسٹ فولڈر میں تمام ٹیسٹ چلاتا ہے (یا تمام موجودہ ٹیسٹ اگر کوئی ڈیٹا سورس پرچم متعین نہیں ہے).
 
@@ -1368,22 +1377,26 @@ Global test coverage: 22.2% (2/9 handlers).
 
 > Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined
 
-اس کا مطلب ہے کہ آپ نے اپنے کوڈ میں `console.log` استعمال کیا ہے، جو اسمبلی اسکرپٹ سے تعاون یافتہ نہیں ہے۔ براہ کرم [لاگنگ API](/developing/graph-ts/api/#logging-api) استعمال کرنے پر غور کریں
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 دلائل میں عدم مماثلت `graph-ts` اور `matchstick-as` میں عدم مماثلت کی وجہ سے ہوتی ہے۔ اس طرح کے مسائل کو حل کرنے کا بہترین طریقہ یہ ہے کہ ہر چیز کو تازہ ترین جاری کردہ ورژن میں اپ ڈیٹ کیا جائے.
 
+## اضافی وسائل
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## تاثرات
 
 اگر آپ کے پاس کوئی سوال، تاثرات، فیچر کی درخواستیں ہیں یا آپ صرف رابطہ کرنا چاہتے ہیں، تو بہترین جگہ گراف ڈسکورڈ ہوگی جہاں ہمارے پاس Matchstick کے لیے ایک سرشار چینل ہے، جسے 🔥| یونٹ ٹیسٹنگ بلایا جاتا ہے.

From bf2d2818e12256d1a8f95c8e9506cc231fd2df41 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:55 -0500
Subject: [PATCH 0315/1325] New translations about.mdx (Vietnamese)

---
 website/pages/vi/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/vi/about.mdx b/website/pages/vi/about.mdx
index 461f029fbd25..b45ddbbc5c39 100644
--- a/website/pages/vi/about.mdx
+++ b/website/pages/vi/about.mdx
@@ -2,46 +2,66 @@
 title: Về The Graph
 ---
 
-Trang này sẽ giải thích The Graph là gì và cách bạn có thể bắt đầu.
-
 ## What is The Graph?
 
-The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-Các dự án với các hợp đồng thông minh phức tạp như [Uniswap](https://uniswap.org/) và các sáng kiến NFT như [Bored Ape Yacht Club](https://boredapeyachtclub.com/) lưu trữ dữ liệu trên chuỗi khối Ethereum, khiến việc đọc bất kỳ thứ gì khác ngoài dữ liệu cơ bản trực tiếp từ chuỗi khối này thực sự khó khăn.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-You could also build out your own server, process the transactions there, save them to a database, and build an API endpoint on top of it all in order to query the data. However, this option is [resource intensive](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+### How The Graph Functions
 
-**Lập chỉ mục dữ liệu blockchain thực sự rất rất khó.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- The Graph uses subgraph descriptions, which are known as the subgraph manifest inside the subgraph.
 
-## Cách thức hoạt động của The Graph
+- 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.
 
-The Graph tìm hiểu những gì và cách thức lập chỉ mục dữ liệu Ethereum dựa trên mô tả subgraph, được gọi là bản kê khai subgraph (subgraph manifest). Mô tả subgraph xác định các hợp đồng thông minh quan tâm cho một subgraph, các sự kiện trong các hợp đồng đó cần chú ý và cách ánh xạ dữ liệu sự kiện với dữ liệu mà The Graph sẽ lưu trữ trong cơ sở dữ liệu của nó.
+- When creating a subgraph, you need to write a subgraph manifest.
 
-Khi bạn đã viết một `subgraph manifest`, bạn sử dụng Graph CLI để lưu trữ định nghĩa trong IPFS và yêu cầu indexer bắt đầu lập chỉ mục dữ liệu cho subgraph đó.
+- 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.
 
-Biểu đồ này cung cấp chi tiết hơn về luồng dữ liệu khi một tệp kê khai subgraph đã được triển khai, xử lý các giao dịch Ethereum:
+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 liên tục quét Ethereum để tìm các khối mới và dữ liệu cho subgraph của bạn mà chúng có thể chứa.
-4. Graph Node tìm các sự kiện Ethereum cho subgraph của bạn trong các khối này và chạy các trình xử lý ánh xạ mà bạn đã cung cấp. Ánh xạ là một mô-đun WASM tạo hoặc cập nhật các thực thể dữ liệu mà Graph Node lưu trữ để đáp ứng với các sự kiện Ethereum.
-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.
+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 liên tục quét Ethereum để tìm các khối mới và dữ liệu cho subgraph của bạn mà chúng có thể chứa.
+4.  Graph Node tìm các sự kiện Ethereum cho subgraph của bạn trong các khối này và chạy các trình xử lý ánh xạ mà bạn đã cung cấp. Ánh xạ là một mô-đun WASM tạo hoặc cập nhật các thực thể dữ liệu mà Graph Node lưu trữ để đáp ứng với các sự kiện Ethereum.
+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 more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From 1852301c987f998dd2949589f6e5d2be36e9c4a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:56 -0500
Subject: [PATCH 0316/1325] New translations graphql-api.mdx (Turkish)

---
 website/pages/tr/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/tr/querying/graphql-api.mdx b/website/pages/tr/querying/graphql-api.mdx
index ba6149cbdd94..54a450425b25 100644
--- a/website/pages/tr/querying/graphql-api.mdx
+++ b/website/pages/tr/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Örnekler
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Not:** Tek bir varlık için sorgulama yaparken `id` alanı zorunludur ve bir dize olmalıdır.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Tüm `Token` varlıklarını sorgulayın:
 
@@ -36,7 +44,10 @@ Tüm `Token` varlıklarını sorgulayın:
 
 ### Sıralama
 
-Bir koleksiyonu sorgularken, belirli bir niteliğe göre sıralamak için `orderBy` parametresi kullanılabilir. Ayrıca, sıralama yönünü belirtmek için `orderDirection` kullanılabilir; artan için `asc` veya azalan için `desc`.
+When querying a collection, you may:
+
+- 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.
 
 #### Örnek
 
@@ -53,7 +64,7 @@ Bir koleksiyonu sorgularken, belirli bir niteliğe göre sıralamak için `order
 
 Graph Düğümü [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0)'dan itibaren varlıklar iç içe geçmiş varlıklar bazında sıralanabilir.
 
-Aşağıdaki örnekte, tokenleri sahiplerinin adına göre sıralıyoruz:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ Aşağıdaki örnekte, tokenleri sahiplerinin adına göre sıralıyoruz:
 
 ### Sayfalandırma
 
-Bir koleksiyonu sorgularken, koleksiyonun başından itibaren sayfalama yapmak için `first` parametresi kullanılabilir. Varsayılan sıralama düzeninin oluşturma zamanına göre değil, artan alfanümerik düzende ID'ye göre olduğunu belirtmekte fayda var.
-
-Ayrıca, `skip` parametresi varlıkları atlamak ve sayfalandırmak için kullanılabilir. örn. `first:100` ilk 100 varlığı gösterir ve `first:100, skip:100` sonraki 100 varlığı gösterir.
+When querying a collection, it's best to:
 
-Sorgular genellikle kötü performans gösterdiğinden çok büyük `skip` değerleri kullanmaktan kaçınmalıdır. Çok sayıda öğeyi almak için, son örnekte gösterildiği gibi bir özniteliğe dayalı olarak varlıklar arasında sayfa açmak çok daha idealdir.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### `first`'ün kullanımına örnek
 
@@ -106,7 +118,7 @@ Bir koleksiyonun ortasındaki varlık gruplarını sorgulamak için `skip` param
 
 #### `first` ve `id_ge`'nin kullanımına örnek
 
-Bir istemcinin çok sayıda varlığı alması gerekiyorsa, sorguları bir niteliğe dayandırmak ve bu niteliğe göre filtrelemek çok daha performanslıdır. Örneğin, bir istemci bu sorguyu kullanarak çok sayıda token alabilir:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-İlk seferinde, sorguyu `lastID = ""` ile gönderecek ve sonraki istekler için `lastID`'yi önceki istekteki son varlığın `id` niteliğine ayarlayacaktır. Bu yaklaşım, artan `skip` değerleri kullanmaktan önemli ölçüde daha iyi performans gösterecektir.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtreleme
 
-Sorgularınızda `where` parametresini kullanarak farklı özellikler için filtreleme yapabilirsiniz. `where` parametresi içerisinde birden fazla değer için filtreleme yapabilirsiniz.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### `where`'in kullanımına örnek
 
@@ -155,7 +168,7 @@ Değer karşılaştırması için `_gt`, `_lte` gibi son ekler kullanabilirsiniz
 
 #### Blok filtreleme için örnek
 
-Varlıkları `_change_block(number_gte: Int)` ile de filtreleyebilirsiniz. Bu, belirtilen blok içinde veya sonrasında güncellenen varlıkları filtreler.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 Örneğin bu, son yoklamanızdan bu yana yalnızca değişen varlıkları almak istiyorsanız yararlı olabilir. Ya da alternatif olarak, subgraph'ınızda varlıkların nasıl değiştiğini araştırmak veya hata ayıklamak için yararlı olabilir (bir blok filtresiyle birleştirilirse, yalnızca belirli bir blokta değişen varlıkları izole edebilirsiniz).
 
@@ -193,7 +206,7 @@ Graph Düğümü'nün [`v0.30.0`](https://github.com/graphprotocol/graph-node/re
 
 ##### `AND` Operator
 
-Aşağıdaki örnekte, `outcome` değeri `succeeded` olan ve `number` değeri `100`'den büyük veya buna eşit olan zorlukları filtreliyoruz.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ Aşağıdaki örnekte, `outcome` değeri `succeeded` olan ve `number` değeri `1
 ```
 
 > **Syntactic sugar:** Yukarıdaki sorguyu, virgülle ayrılmış bir alt ifade geçirerek, `and` operatörünü kaldırarak basitleştirebilirsiniz.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ Aşağıdaki örnekte, `outcome` değeri `succeeded` olan ve `number` değeri `1
 
 ##### `OR` Operator
 
-Aşağıdaki örnekte, `outcome` değeri `succeeded` olan veya `number` değeri `100` yada daha büyük olan zorlukları filtreliyoruz.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 Varlıklarınızın durumunu yalnızca varsayılan olan en son blok için değil, aynı zamanda geçmişteki rastgele bir blok için de sorgulayabilirsiniz. Bir sorgunun gerçekleşmesi gereken blok, sorguların üst düzey alanlarına bir `block` bağımsız değişkeni eklenerek blok numarası veya blok karması ile belirtilebilir.
 
-Böyle bir sorgunun sonucu zaman içinde değişmeyecektir, yani belirli bir geçmiş blokta sorgu yapmak, ne zaman yürütülürse yürütülsün aynı sonucu verecektir, ancak zincirin başına çok yakın bir blokta sorgu yaptığınız zaman, bu bloğun ana zincirde olmadığı ortaya çıkarsa ve zincir yeniden düzenlenirse sonuç değişebilir. Bir blok nihai olarak kabul edildiğinde takdirde, sorgunun sonucu değişmeyecektir.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Lütfen şunu göz önünde bulundurun ki mevcut uygulama hala belirli sınırlamalara tabidir ve bu garantiyi ihlal edebilir. Uygulama her zaman verilen bir blok hash değerinin ana zincirde olup olmadığını ya da henüz kesinleştirilmemiş bir blok için blok hash değeri ile yapılan sorgunun, sorgu ile eş zamanlı olarak gerçekleşen bir blok yeniden düzenlemesi tarafından etkilenebileceğini bilemeyebilir. Ancak bu durum, blok kesinleştirildiğinde ve ana zincirde bulunduğu biliniyorsa, blok hash değeri ile yapılan sorguların sonuçlarını etkilemez. [Bu sorun](https://github.com/graphprotocol/graph-node/issues/1405), bu sınırlamaların ayrıntılarını detaylı bir şekilde açıklamaktadır.
+> 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.
 
 #### Örnek
 
@@ -322,12 +335,12 @@ Tam metin arama sorgularının kullanması gereken bir zorunlu alanı vardır, b
 
 Tam metin arama operatörleri:
 
-| Symbol | Operator | Tanım |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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    | Tanım                                                                                                                                |
+| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
+| &#x7c;      | `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.)                                                 |
 
 #### Örnekler
 
@@ -376,11 +389,11 @@ Graph Düğümü, [graphql-js referans uygulamasını](https://github.com/graphq
 
 ## Schema
 
-Veri kaynağınızın şeması, sorgulamak için kullanılabilen varlık tipleri, değerler ve ilişkiler [GraphQL Arayüz Tanımlama Dili (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System) aracılığıyla tanımlanır.
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-GraphQL şemaları genellikle `queries`, `subscriptions` ve `mutations` için root tipleri tanımlar. Graph yalnızca `queries` destekler. Subgraph'ınız için root `Query` tipi, subgraph bildiriminize dahil edilen GraphQL şemasından otomatik olarak oluşturulur.
+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).
 
-> **Not:** API'miz mutations tipini açığa çıkarmaz çünkü geliştiricilerin uygulamalarından doğrudan temelindeki blok zincire karşı işlemleri gerçekleştirmeleri beklenir.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Varlıklar
 

From a79fd85223b4949f40abc31bfc9a07ca0ec86ac8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:58 -0500
Subject: [PATCH 0317/1325] New translations graphql-api.mdx (Ukrainian)

---
 website/pages/uk/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/uk/querying/graphql-api.mdx b/website/pages/uk/querying/graphql-api.mdx
index 2bbc71b5bb9c..d8671e53a77c 100644
--- a/website/pages/uk/querying/graphql-api.mdx
+++ b/website/pages/uk/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-In your subgraph schema you define types called `Entities`. For each `Entity` type, an `entity` and `entities` field will be generated on the top-level `Query` type. Note that `query` does not need to be included at the top of the `graphql` query when using The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### Example
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | Description |
-| --- | --- | --- |
-| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `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                                |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From dd4517ba7d712ac5a50aee2788f22250af441820 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:36:59 -0500
Subject: [PATCH 0318/1325] New translations graphql-api.mdx (Chinese
 Simplified)

---
 website/pages/zh/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/zh/querying/graphql-api.mdx b/website/pages/zh/querying/graphql-api.mdx
index 341e78e4ad60..2e4b4a0e6f54 100644
--- a/website/pages/zh/querying/graphql-api.mdx
+++ b/website/pages/zh/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## 查询
+## What is GraphQL?
 
-在您的子图模式中，定义了称为 `Entities` 的类型。 对于每个 `Entity` 类型，将在顶级 `Query` 类型上生成一个 `entity` 和 `entities` 字段。 请注意，使用Graph 时，`query` 不需要包含在 `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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### 例子
 
@@ -21,7 +29,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 }
 ```
 
-> **注意：**查询单个实体时，`id`字段为必填项，而且必须为字符串。
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 查询所有 `Token` 实体：
 
@@ -36,7 +44,10 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### 排序
 
-查询集合时，`orderBy` 参数可用于按特定属性排序。 此外，`orderDirection` 可用于指定排序方向，`asc` 用于升序，而`desc` 用于降序。
+When querying a collection, you may:
+
+- 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.
 
 #### 示例
 
@@ -53,7 +64,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 从Graph 节点 [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0)开始，可以根据嵌套实体对实体进行排序。
 
-在以下示例中，我们根据代币所有者的名称对其进行排序：
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### 分页
 
-查询集合时，可以使用 `first` 参数从集合的开头进行分页。 值得注意的是，默认排序顺序是按 ID 以字母数字升序排列，而不是按创建时间排列。
-
-此外，`skip` 参数可用于跳过实体和分页。 例如 `first:100` 显示前 100 个实体，`first:100, skip:100` 显示接下来的 100 个实体。
+When querying a collection, it's best to:
 
-查询应该避免使用非常大的 `skip` 值，因为它们通常性能表现不佳。 要检索大量项目，最好根据上一个示例中所示的属性对实体进行分页。
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### 使用`first`的示例
 
@@ -106,7 +118,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 #### 使用`first`和`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:
 
 ```graphql
 query manyTokens($lastID: String) {    tokens(first: 1000, where: { id_gt: $lastID }) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {    tokens(first: 1000, where: { id_gt: $last
 }
 ```
 
-第一次，它会发送带有 `lastID = ""` 的查询，对于后续请求，会将 `lastID` 设置为上一个请求中的最后一个实体的`id` 属性。 与简单的提高 `skip` 值相比，这种方法的性能要好得多。
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### 过滤
 
-您可以在查询中使用 `where` 参数来过滤不同的属性。 您可以在 `where` 参数内过滤多个值。
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### 使用`where`的示例
 
@@ -155,7 +168,7 @@ query manyTokens($lastID: String) {    tokens(first: 1000, where: { id_gt: $last
 
 #### 区块过滤示例
 
-您还可以通过` _ change _ block (number _ gte: Int)`过滤实体-这个过滤器在指定的区块中或之后更新的实体。
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 如果您只想获取已经更改的实体，例如自上次轮询以来改变的实体，那么这将非常有用。或者也可以调查或调试子图中实体的变化情况(如果与区块过滤器结合使用，则只能隔离在特定区块中发生变化的实体)。
 
@@ -193,7 +206,7 @@ query manyTokens($lastID: String) {    tokens(first: 1000, where: { id_gt: $last
 
 ##### `AND`运算符
 
-在下面的示例中，我们正在筛选`outcome``succeeded`且`number`大于或等于`100`的挑战。
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ query manyTokens($lastID: String) {    tokens(first: 1000, where: { id_gt: $last
 ```
 
 > **语法糖：**您可以通过传递一个用逗号分隔的子表达式来删除`and`运算符，从而简化上述查询。
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ query manyTokens($lastID: String) {    tokens(first: 1000, where: { id_gt: $last
 
 ##### `OR`运算符
 
-在下面的示例中，我们正在筛选`outcome``succeeded`或`number`大于或等于`100`的挑战。
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 您可以查询实体的状态，不仅查询默认的最新区块，还可以查询过去的任意区块。通过在查询的顶级字段中包含`block`参数，可以通过区块号或区块哈希指定应该发生查询的区块。
 
-这种查询结果不会随着时间的推移而改变，即对过去某个区块的查询，无论何时执行，都将返回相同的结果。唯一的例外是，如果您在非常靠近链头的区块上进行查询，如果该区块不在主链上，并且链被重新组织，则结果可能会改变。 一旦一个区块被确认是最终的区块，那么查询的结果就不会改变。
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-请注意，当前的实现仍然受到某些限制，这些限制可能会违反这些保证。该实现不能总是判断给定的区块哈希根本不在主链上，或者对于一个不能被认为是最终的区块，逐块哈希查询的结果可能会受到与查询同时运行的区块重组的影响。当区块是最终区块并且已知在主链上时，它们不会影响区块哈希查询的结果。[这个](https://github.com/graphprotocol/graph-node/issues/1405)问题详细解释了这些限制是什么。
+> 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.
 
 #### 示例
 
@@ -322,12 +335,12 @@ _change_block(number_gte: Int)
 
 全文搜索运算符：
 
-| 符号   | 运算符      | 描述                                                                   |
-| ------ | ----------- | ---------------------------------------------------------------------- |
-| `&`    | `And`       | 用于将多个搜索词组合到包含所有提供词条的实体的过滤器中                 |
-| &#x7c; | `Or`        | 由 or 运算符分隔的多个搜索词的查询，将返回与任何提供的词匹配的所有实体 |
-| `<->`  | `Follow by` | 指定两个单词之间的距离。                                               |
-| `:*`   | `Prefix`    | 使用前缀搜索词查找前缀匹配的单词（需要 2 个字符）                      |
+| 符号          | 运算符         | 描述                                    |
+| ----------- | ----------- | ------------------------------------- |
+| `&`     | `And`       | 用于将多个搜索词组合到包含所有提供词条的实体的过滤器中           |
+| &#x7c;      | `Or`        | 由 or 运算符分隔的多个搜索词的查询，将返回与任何提供的词匹配的所有实体 |
+| `<->` | `Follow by` | 指定两个单词之间的距离。                          |
+| `:*`        | `Prefix`    | 使用前缀搜索词查找前缀匹配的单词（需要 2 个字符）            |
 
 #### 例子
 
@@ -376,11 +389,11 @@ Graph Node使用[graphql-tools-rs](https://github.com/dotansimha/graphql-tools-r
 
 ## 模式
 
-数据源的模式，即可用于查询的实体类型、值和关系，是通过[GraphQL接口定义语言（IDL）定义](https://facebook.github.io/graphql/draft/#sec-Type-System)的。
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-GraphQL模式通常定义`查询`、`订阅`和`突变`的根类型。Graph仅支持`查询`。子图的根`查询`类型是从子图清单中包含的GraphQL模式自动生成的。
+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 不提供对变种的支持，因为开发人员会从他们的应用程序中直接针对底层区块链发出交易。
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### 实体
 

From aad720728c336f5366a45a7917dffc59848a3201 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:00 -0500
Subject: [PATCH 0319/1325] New translations graphql-api.mdx (Urdu (Pakistan))

---
 website/pages/ur/querying/graphql-api.mdx | 71 ++++++++++++++---------
 1 file changed, 42 insertions(+), 29 deletions(-)

diff --git a/website/pages/ur/querying/graphql-api.mdx b/website/pages/ur/querying/graphql-api.mdx
index 356677089b60..3dfdf8d64d89 100644
--- a/website/pages/ur/querying/graphql-api.mdx
+++ b/website/pages/ur/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## کیوریز
+## What is GraphQL?
 
-اپنے سب گراف اسکیما میں آپ `Entities` نامی اقسام کی وضاحت کرتے ہیں۔ ہر ایک `Entity` قسم کے لیے، ایک `entity` اور `entities` فیلڈ کو اعلی درجے کی `Query` قسم پر تیار کیا جائے گا۔ نوٹ کریں کہ گراف استعمال کرتے وقت `Query` کو `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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### مثالیں
 
@@ -21,7 +29,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 }
 ```
 
-> **نوٹ:** کسی ایک ہستی کے لیے کیوری کرتے وقت، `id` فیلڈ درکار ہے, اور یہ ایک سٹرنگ ہونا چاہیے.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 تمام `Token` اداروں سے کیوری کریں:
 
@@ -36,7 +44,10 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### سورٹنگ
 
-کسی مجموعہ سے کیوری کرتے وقت، `orderBy` پیرامیٹر کو کسی خاص وصف کے مطابق ترتیب دینے کے لیے استعمال کیا جا سکتا ہے۔ اضافی طور پر، ترتیب کی سمت بتانے کے لیے `orderDirection` استعمال کیا جا سکتا ہے، `asc` چڑھنے کے لیے یا `desc` اترنے کے لیے.
+When querying a collection, you may:
+
+- 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.
 
 #### مثال
 
@@ -53,7 +64,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 گراف نوڈ کے مطابق [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) ہستیوں کو ترتیب دیا جا سکتا ہے نیسٹڈ اداروں کی بنیاد پر.
 
-درج ذیل مثال میں، ہم ٹوکنز کو ان کے مالک کے نام سے ترتیب دیتے ہیں:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### صفحہ بندی
 
-کسی مجموعہ سے کیوری کرتے وقت، `first` پیرامیٹر کو مجموعہ کے آغاز سے صفحہ بندی کرنے کے لیے استعمال کیا جا سکتا ہے۔ یہ بات قابل غور ہے کہ ڈیفالٹ ترتیب ترتیب صعودی حرفی ترتیب میں ID کے لحاظ سے ہے ، تخلیق کے وقت سے نہیں.
-
-مزید، `skip` پیرامیٹر کو ہستیوں کو چھوڑنے اور صفحہ بندی کرنے کے لیے استعمال کیا جا سکتا ہے۔ جیسے `first:100` پہلی 100 ہستیوں کو دکھاتا ہے اور `first:100, skip:100` اگلی 100 ہستیوں کو دکھاتا ہے.
+When querying a collection, it's best to:
 
-کیوریز کو بہت بڑی `skip` اقدار کے استعمال سے گریز کرنا چاہیے کیونکہ وہ عام طور پر خراب کارکردگی کا مظاہرہ کرتے ہیں۔ بڑی تعداد میں آئٹمز کو بازیافت کرنے کے لیے، کسی خاصیت کی بنیاد پر ہستیوں کے ذریعے صفحہ بنانا بہت بہتر ہے جیسا کہ آخری مثال میں دکھایا گیا ہے.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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.
 
 #### `first` استعمال کرنے کی مثال
 
@@ -106,7 +118,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 #### `first` اور `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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-پہلی بار، یہ `lastID = ""` کے ساتھ کیوری بھیجے گا، اور اس کے بعد کی درخواستوں کے لیے `lastID` کو آخری کی `id` پچھلی درخواست میں آخری ہستی کے وصف پر سیٹ کرے گا۔ یہ نقطہ نظر `skip` اقدار کو بڑھانے کے مقابلے میں نمایاں طور پر بہتر کارکردگی کا مظاہرہ کرے گا.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### فلٹرنگ
 
-آپ مختلف خصوصیات کو فلٹر کرنے کے لیے اپنے کیوریز میں `where` پیرامیٹر استعمال کر سکتے ہیں۔ آپ `where` پیرامیٹر کے اندر متعدد اقدار پر فلٹر کرسکتے ہیں.
+- You can use the `where` parameter in your queries to filter for different properties.
+- You can filter on multiple values within the `where` parameter.
 
 #### `where` استعمال کرنے کی مثال
 
@@ -155,7 +168,7 @@ query manyTokens($lastID: String) {
 
 #### بلاک فلٹرنگ کی مثال
 
-آپ `_change_block(number_gte: Int)` کے ذریعے بھی ہستیوں کو فلٹر کر سکتے ہیں - یہ ان ہستیوں کو فلٹر کرتا ہے جو مخصوص بلاک میں یا اس کے بعد اپ ڈیٹ ہوئے تھے.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 یہ کارآمد ہو سکتا ہے اگر آپ صرف ان ہستیوں کو لانے کے خواہاں ہیں جو تبدیل ہو چکی ہیں، مثال کے طور پر آخری بار جب آپ نے پول کیا تھا۔ یا متبادل طور پر یہ تحقیق کرنا یا ڈیبگ کرنا مفید ہو سکتا ہے کہ آپ کے سب گراف میں ہستی کیسے تبدیل ہو رہی ہیں (اگر بلاک فلٹر کے ساتھ ملایا جائے تو، آپ صرف ان ہستیوں کو الگ تھلگ کر سکتے ہیں جو ایک مخصوص بلاک میں تبدیل ہوئی ہیں).
 
@@ -193,7 +206,7 @@ query manyTokens($lastID: String) {
 
 ##### `AND` آپریٹر
 
-مندرجہ ذیل مثال میں، ہم `outcome` `succeeded` اور `number` کے ساتھ چیلنجوں کے لیے فلٹر کر رہے ہیں جو `100` سے زیادہ یا اس کے برابر ہیں.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ query manyTokens($lastID: String) {
 ```
 
 > **Syntactic شوگر:** آپ `and` آپریٹر کو ہٹا کر کوما سے الگ کردہ سب اظہار کو پاس کر کے مذکورہ کیوری کو آسان بنا سکتے ہیں.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ query manyTokens($lastID: String) {
 
 ##### `OR` آپریٹر
 
-مندرجہ ذیل مثال میں، ہم `outcome` `succeeded` اور `number` کے ساتھ چیلنجوں کے لیے فلٹر کر رہے ہیں جو `100` سے زیادہ یا اس کے برابر ہیں.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 آپ اپنے ہستیوں کی حالت کے بارے میں نہ صرف تازہ ترین بلاک کے لیے کیوری کر سکتے ہیں، جو پہلے سے طے شدہ ہے، بلکہ ماضی میں کسی آربٹریری بلاک کے لیے بھی۔ جس بلاک پر کیوری ہونا چاہیے اس کی وضاحت یا تو اس کے بلاک نمبر یا اس کے بلاک ہیش سے کیوریز کے ٹاپ لیول فیلڈز میں `block` دلیل شامل کر کے کی جا سکتی ہے.
 
-اس طرح کے کیوری کا نتیجہ وقت کے ساتھ نہیں بدلے گا، یعنی ماضی کے کسی مخصوص بلاک پر کیوریز کرنے سے وہی نتیجہ آئے گا چاہے اس پر عمل کیا جائے، اس استثنا کے ساتھ کہ اگر آپ چین کے سر کے بالکل قریب بلاک پر کیوری کرتے ہیں۔, نتیجہ تبدیل ہو سکتا ہے اگر وہ بلاک مین چین پر نہ ہو اور چین دوبارہ منظم ہو جائے۔ ایک بار جب کسی بلاک کو حتمی سمجھا جائے تو کیوری کا نتیجہ تبدیل نہیں ہوگا.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-نوٹ کریں کہ موجودہ نفاذ اب بھی کچھ حدود کے تابع ہے جو ان ضمانتوں کی خلاف ورزی کر سکتی ہے. نفاذ ہمیشہ یہ نہیں بتا سکتا کہ دیا گیا بلاک ہیش بالکل بھی مین چین پر نہیں ہے، یا یہ کہ کسی بلاک کے لیے بلاک ہیش کے ذریعے کی گئی کیوری کا نتیجہ جسے ابھی تک حتمی نہیں سمجھا جا سکتا ہے، کیوری کے ساتھ ساتھ چلنے والی بلاک کی تنظیم نو سے متاثر ہو سکتا ہے۔ وہ بلاک ہیش کے ذریعے سوالات کے نتائج کو متاثر نہیں کرتے جب بلاک حتمی ہو اور مین چین پر جانا جاتا ہو۔ [یہ مسئلہ](https://github.com/graphprotocol/graph-node/issues/1405) وضاحت کرتا ہے کہ یہ حدود کیا ہیں.
+> 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.
 
 #### مثال
 
@@ -322,12 +335,12 @@ _change_block(number_gte: Int)
 
 فل ٹیکسٹ سرچ آپریٹرز:
 
-| علامت | آپریٹر | تفصیل |
-| --- | --- | --- |
-| `&` | `And` | ایک سے زیادہ تلاش کی اصطلاحات کو ایک فلٹر میں یکجا کرنے کے لیے ان ہستیوں کے لیے جس میں فراہم کردہ تمام اصطلاحات شامل ہوں |
-| &#x7c; | `Or` | Or آپریٹر کے ذریعہ الگ کردہ متعدد تلاش کی اصطلاحات کے ساتھ کیوریز فراہم کردہ شرائط میں سے کسی سے بھی مماثلت کے ساتھ تمام ہستیوں کو واپس کریں گے |
-| `<>` | `Follow by` | دو الفاظ کے درمیان فاصلہ بتائیں. |
-| `:*` | `Prefix` | ایسے الفاظ تلاش کرنے کے لیے پریفکس ​​تلاش کی اصطلاح استعمال کریں جن کا سابقہ ​​مماثل ہو (۲ حروف درکار ہیں.) |
+| علامت      | آپریٹر      | تفصیل                                                                                                                                           |
+| ---------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
+| `&`    | `And`       | ایک سے زیادہ تلاش کی اصطلاحات کو ایک فلٹر میں یکجا کرنے کے لیے ان ہستیوں کے لیے جس میں فراہم کردہ تمام اصطلاحات شامل ہوں                        |
+| &#x7c;     | `Or`        | Or آپریٹر کے ذریعہ الگ کردہ متعدد تلاش کی اصطلاحات کے ساتھ کیوریز فراہم کردہ شرائط میں سے کسی سے بھی مماثلت کے ساتھ تمام ہستیوں کو واپس کریں گے |
+| `<>` | `Follow by` | دو الفاظ کے درمیان فاصلہ بتائیں.                                                                                                                |
+| `:*`       | `Prefix`    | ایسے الفاظ تلاش کرنے کے لیے پریفکس ​​تلاش کی اصطلاح استعمال کریں جن کا سابقہ ​​مماثل ہو (۲ حروف درکار ہیں.)                                     |
 
 #### مثالیں
 
@@ -376,11 +389,11 @@ _change_block(number_gte: Int)
 
 ## سکیما
 
-آپ کے ڈیٹا کے ماخذ کا اسکیما -- یعنی، ہستی کی اقسام، اقدار اور رشتے جو کیوری کے لیے دستیاب ہیں -- کی وضاحت [GraphQL انٹرفیس ڈیفینیشن لینگویج (IDL)](https://facebook.github.io/graphql/draft/# کے ذریعے کی گئی ہے۔ sec-Type-System).
+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 Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
 
-GraphQL اسکیمے عام طور پر `queries`، `subscriptions` اور `mutations` کے لیے جڑ کی اقسام کی وضاحت کرتے ہیں۔ گراف صرف `queries` کو سپورٹ کرتا ہے۔ آپ کے سب گراف کے لیے روٹ `Query` قسم خود بخود GraphQL اسکیما سے تیار ہوتی ہے جو آپ کے سب گراف مینی فیسٹ میں شامل ہے.
+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:** ہمارا API تغیرات کو ظاہر نہیں کرتا ہے کیونکہ ڈویلپرز سے توقع کی جاتی ہے کہ وہ اپنی ایپلیکیشنز سے بنیادی بلاکچین کے خلاف براہ راست ٹرانزیکشن جاری کریں.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### ہستیوں
 
@@ -408,7 +421,7 @@ GraphQL اسکیمے عام طور پر `queries`، `subscriptions` اور `muta
 
 اگر کوئی بلاک فراہم کیا جاتا ہے تو، میٹا ڈیٹا اس بلاک کا ہوتا ہے، اگر تازہ ترین انڈیکسڈ بلاک استعمال نہیں کیا جاتا ہے۔ اگر فراہم کیا گیا ہو، تو بلاک سب گراف کے اسٹارٹ بلاک کے بعد ہونا چاہیے، اور حال ہی میں انڈیکس کیے گئے بلاک سے کم یا اس کے برابر ہونا چاہیے.
 
-`deployment` ایک منفرد ID ہے، جو `subgraph.yaml` فائل کے IPFS CID سے مطابقت رکھتی ہے.
+` deployment ` ایک منفرد ID ہے، جو `subgraph.yaml` فائل کے IPFS CID سے مطابقت رکھتی ہے.
 
 `block` تازہ ترین بلاک کے بارے میں معلومات فراہم کرتا ہے (`_meta` کو بھیجی گئی کسی بھی بلاک کی رکاوٹوں کو مدنظر رکھتے ہوئے):
 

From efc5112fcf9266fca11037a164e7fd36f97e8a46 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:02 -0500
Subject: [PATCH 0320/1325] New translations api.mdx (Turkish)

---
 website/pages/tr/developing/graph-ts/api.mdx | 461 ++++++++++---------
 1 file changed, 235 insertions(+), 226 deletions(-)

diff --git a/website/pages/tr/developing/graph-ts/api.mdx b/website/pages/tr/developing/graph-ts/api.mdx
index 96925980ae4b..b8a4af72cc47 100644
--- a/website/pages/tr/developing/graph-ts/api.mdx
+++ b/website/pages/tr/developing/graph-ts/api.mdx
@@ -2,47 +2,49 @@
 title: AssemblyScript API'si
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Not: Eğer `graph-cli`/`graph-ts` sürüm `0.22.0`'den önce bir subgraph oluşturduysanız, eski bir AssemblyScript sürümünü kullanıyorsunuz demektir. [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide) gözden geçirmeniz önerilir.
 
-Bu sayfa subgraph eşleştirmelerini yazarken bullanılabilen yerleşik API'leri belgelemektedir. Hazır olarak iki çeşit API mevcuttur:
+Subgraph eşlemeleri yazarken kullanılabilecek yerleşik API'leri öğrenin. Hazır olarak sunulan iki tür API mevcuttur:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- [Graph TypeScript kütüphanesi](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Subgraph dosyalarından `graph codegen` tarafından üretilen kod
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+[AssemblyScript](https://github.com/AssemblyScript/assemblyscript) ile uyumlu olduğu sürece diğer kütüphaneleri de bağımlılık olarak ekleyebilirsiniz.
+
+Dil eşlemeleri AssemblyScript ile yazıldığından, [AssemblyScript wiki'sindeki](https://github.com/AssemblyScript/assemblyscript/wiki) dil ve standart kütüphane özelliklerini gözden geçirmek faydalı olacaktır.
 
 ## API Referansı
 
-The `@graphprotocol/graph-ts` library provides the following APIs:
+`@graphprotocol/graph-ts` kütüphanesi aşağıdaki API'leri sağlar:
 
-- An `ethereum` API for working with Ethereum smart contracts, events, blocks, transactions, and Ethereum values.
-- A `store` API to load and save entities from and to the Graph Node store.
-- A `log` API to log messages to the Graph Node output and Graph Explorer.
-- An `ipfs` API to load files from IPFS.
-- A `json` API to parse JSON data.
-- A `crypto` API to use cryptographic functions.
+- Ethereum akıllı sözleşmeleri, olaylar, bloklar, işlemler ve Ethereum değerleriyle çalışmak için bir `ethereum` API'si.
+- Varlıkları Graph Düğümü deposundan yüklemek ve depoya kaydetmek için bir `store` API'si.
+- Graph Düğümü çıktısına ve Graph Gezgini'ne mesaj kaydetmek için bir `log` API'si.
+- IPFS'ten dosyaları yüklemek için bir `ipfs` API'si.
+- JSON verilerini ayrıştırmak için bir `json` API'si.
+- Kriptografik fonksiyonları kullanmak için bir `crypto` API'si.
 - Ethereum, JSON, GraphQL ve AssemblyScript gibi farklı tip sistemler arası çeviri yapmak için düşük seviyeli yazılımlar.
 
 ### Sürümler
 
-The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
+Subgraph manifestosundaki `apiVersion`, bir subgraph için Graph Düğümü tarafından çalıştırılan eşleme (mapping) API'sinin sürümünü belirtir.
 
-| Sürüm | Sürüm Notları |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Sürüm | Sürüm Notları                                                                                                                                                                                                                                                                                                |
+| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 0.0.9 | Yeni host fonksiyonları ekler: [`eth_get_balance`](#balance-of-an-address) ve [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                                                         |
+| 0.0.8 | Bir varlığı kaydederken şemadaki alanların varlığını doğrulama mekanizması ekler.                                                                                                                                                                                                                            |
+| 0.0.7 | Ethereum türlerine `TransactionReceipt` ve `Log` sınıfları eklendi<br />Ethereum Event nesnesine `receipt` alanı eklendi                                                                                                                                                                                     |
+| 0.0.6 | Ethereum Transaction nesnesine `nonce` alanı eklendi<br />Ethereum Block nesnesine `baseFeePerGas` eklendi                                                                                                                                                                                                   |
+| 0.0.5 | AssemblyScript sürümü 0.19.10'a yükseltildi (bu sürümle birlikte uyumluluğu bozabilecek değişiklikler yapılmıştır, lütfen [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide) bölümüne bakın)<br />`ethereum.transaction.gasUsed`, `ethereum.transaction.gasLimit` olarak yeniden adlandırıldı |
+| 0.0.4 | Ethereum SmartContractCall nesnesine `functionSignature` alanı eklendi                                                                                                                                                                                                                                       |
+| 0.0.3 | Ethereum Call nesnesine `from` alanı eklendi<br />`etherem.call.address`, `ethereum.call.to` olarak yeniden adlandırıldı                                                                                                                                                                                     |
+| 0.0.2 | Ethereum Transaction nesnesine `input` alanı eklendi                                                                                                                                                                                                                                                         |
 
 ### Dahili Türler
 
-Documentation on the base types built into AssemblyScript can be found in the [AssemblyScript wiki](https://www.assemblyscript.org/types.html).
+AssemblyScript'e yerleşik olan temel türler hakkında dökümantasyona [AssemblyScript wiki'sinden](https://www.assemblyscript.org/types.html) ulaşabilirsiniz.
 
-The following additional types are provided by `@graphprotocol/graph-ts`.
+Aşağıdaki ek türler `@graphprotocol/graph-ts` tarafından sağlanmaktadır.
 
 #### ByteArray
 
@@ -50,26 +52,26 @@ The following additional types are provided by `@graphprotocol/graph-ts`.
 import { ByteArray } from '@graphprotocol/graph-ts'
 ```
 
-`ByteArray` represents an array of `u8`.
+`ByteArray`, bir `u8` dizisini temsil eder.
 
-_Construction_
+_Oluşturma_
 
-- `fromI32(x: i32): ByteArray` - Decomposes `x` into bytes.
-- `fromHexString(hex: string): ByteArray` - Input length must be even. Prefixing with `0x` is optional.
+- `fromI32(x: i32): ByteArray` - `x` değerini baytlara ayrıştırır.
+- `fromHexString(hex: string): ByteArray` - Girdi uzunluğu çift sayı olmalıdır. `0x` ile başlatmak isteğe bağlıdır.
 
-_Type conversions_
+_Tür Dönüşümleri_
 
-- `toHexString(): string` - Converts to a hex string prefixed with `0x`.
-- `toString(): string` - Interprets the bytes as a UTF-8 string.
-- `toBase58(): string` - Encodes the bytes into a base58 string.
-- `toU32(): u32` - Interprets the bytes as a little-endian `u32`. Throws in case of overflow.
-- `toI32(): i32` - Interprets the byte array as a little-endian `i32`. Throws in case of overflow.
+- `toHexString(): string` - On altılık tabanda bir dizeye (hex string) dönüştürür ve `0x` öneki ekler.
+- `toString(): string` - Baytları UTF-8 dizesi olarak yorumlar.
+- `toBase58(): string` - Baytları base58 dizesine kodlar.
+- `toU32(): u32` - Baytları little-endian bir `u32` olarak yorumlar. Aşım durumunda hata verir.
+- `toI32(): i32` - Bayt dizisini little-endian bir `i32` olarak yorumlar. Aşım durumunda hata verir.
 
-_Operators_
+_Operatörler_
 
-- `equals(y: ByteArray): bool` – can be written as `x == y`.
-- `concat(other: ByteArray) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by `other`
-- `concatI32(other: i32) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by the byte representation of `other`
+- `equals(y: ByteArray): bool` – `x == y` olarak yazılabilir.
+- `concat(other: ByteArray): ByteArray` - `this` dizisinin sonuna `other` dizisini ekleyerek yeni bir `ByteArray` döner.
+- `concatI32(other: i32): ByteArray` - `this` dizisinin sonuna `other`'ın bayt temsili ekleyerek yeni bir `ByteArray` döner.
 
 #### BigDecimal
 
@@ -77,32 +79,32 @@ _Operators_
 import { BigDecimal } from '@graphprotocol/graph-ts'
 ```
 
-`BigDecimal` is used to represent arbitrary precision decimals.
+`BigDecimal`, ondalık sayıları istenildiği kadar doğrulukta temsil etmek için kullanılır.
 
-> Note: [Internally](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal` is stored in [IEEE-754 decimal128 floating-point format](https://en.wikipedia.org/wiki/Decimal128_floating-point_format), which supports 34 decimal digits of significand. This makes `BigDecimal` unsuitable for representing fixed-point types that can span wider than 34 digits, such as a Solidity [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) or equivalent.
+> Not: [Dahili olarak](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal`, [IEEE-754 decimal128 floating-point formatında](https://en.wikipedia.org/wiki/Decimal128_floating-point_format) saklanır ve bu format 34 ondalık basamağa kadar destek sunar. Bu durum, `BigDecimal`'i, 34 basamağı aşabilen sabit noktalı türleri temsil etmek için (örneğin Solidity'deki [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) gibi) uygun olmaktan çıkarır.
 
-_Construction_
+_Oluşturma_
 
-- `constructor(bigInt: BigInt)` – creates a `BigDecimal` from an `BigInt`.
-- `static fromString(s: string): BigDecimal` – parses from a decimal string.
+- `constructor(bigInt: BigInt)` – Bir `BigInt`'ten bir `BigDecimal` oluşturur.
+- `static fromString(s: string): BigDecimal` – Ondalık bir dizeyi ayrıştırır.
 
-_Type conversions_
+_Tür Dönüşümleri_
 
-- `toString(): string` – prints to a decimal string.
+- `toString(): string` – Ondalık bir dize olarak yazdırır.
 
 _Math_
 
-- `plus(y: BigDecimal): BigDecimal` – can be written as `x + y`.
-- `minus(y: BigDecimal): BigDecimal` – can be written as `x - y`.
-- `times(y: BigDecimal): BigDecimal` – can be written as `x * y`.
-- `div(y: BigDecimal): BigDecimal` – can be written as `x / y`.
-- `equals(y: BigDecimal): bool` – can be written as `x == y`.
-- `notEqual(y: BigDecimal): bool` – can be written as `x != y`.
-- `lt(y: BigDecimal): bool` – can be written as `x < y`.
-- `le(y: BigDecimal): bool` – can be written as `x <= y`.
-- `gt(y: BigDecimal): bool` – can be written as `x > y`.
-- `ge(y: BigDecimal): bool` – can be written as `x >= y`.
-- `neg(): BigDecimal` - can be written as `-x`.
+- `plus(y: BigDecimal): BigDecimal` – `x + y` şeklinde yazılabilir.
+- `minus(y: BigDecimal): BigDecimal` – `x - y` şeklinde yazılabilir.
+- `times(y: BigDecimal): BigDecimal` – `x * y` şeklinde yazılabilir.
+- `div(y: BigDecimal): BigDecimal` – `x / y` şeklinde yazılabilir.
+- `equals(y: BigDecimal): bool` – `x == y` şeklinde yazılabilir.
+- `notEqual(y: BigDecimal): bool` – `x != y` şeklinde yazılabilir.
+- `lt(y: BigDecimal): bool` – `x < y` şeklinde yazılabilir.
+- `le(y: BigDecimal): bool` – `x <= y` şeklinde yazılabilir.
+- `gt(y: BigDecimal): bool` – `x > y` şeklinde yazılabilir.
+- `ge(y: BigDecimal): bool` – `x >= y` şeklinde yazılabilir.
+- `neg(): BigDecimal` - `-x` şeklinde yazılabilir.
 
 #### BigInt
 
@@ -110,53 +112,53 @@ _Math_
 import { BigInt } from '@graphprotocol/graph-ts'
 ```
 
-`BigInt` is used to represent big integers. This includes Ethereum values of type `uint32` to `uint256` and `int64` to `int256`. Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.
+`BigInt`, büyük tam sayıları temsil etmek için kullanılır. Buna, Ethereum'daki `uint32` ile `uint256` ve `int64` ile `int256` türlerindeki değerler dahildir. `uint32`'nin altındaki her şey, örneğin `int32`, `uint24` veya `int8`, `i32` olarak temsil edilir.
 
-The `BigInt` class has the following API:
+`BigInt` sınıfı aşağıdaki API'ye sahiptir:
 
-_Construction_
+_Oluşturma_
 
-- `BigInt.fromI32(x: i32): BigInt` – creates a `BigInt` from an `i32`.
+- `BigInt.fromI32(x: i32): BigInt` – Bir `i32`'den bir `BigInt` oluşturur.
 
-- `BigInt.fromString(s: string): BigInt`– Parses a `BigInt` from a string.
+- `BigInt.fromString(s: string): BigInt` – Bir dizeden bir `BigInt` oluşturur.
 
-- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` – Interprets `bytes` as an unsigned, little-endian integer. If your input is big-endian, call `.reverse()` first.
+- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` – `bytes`'i işaretsiz, little-endian bir tamsayı olarak yorumlar. Girdiniz big-endian ise önce `.reverse()` metodunu kullanın.
 
-- `BigInt.fromSignedBytes(x: Bytes): BigInt` – Interprets `bytes` as a signed, little-endian integer. If your input is big-endian, call `.reverse()` first.
+- `BigInt.fromSignedBytes(x: Bytes): BigInt` – `bytes`'i işaretli, little-endian bir tamsayı olarak yorumlar. Girdiniz big-endian ise önce `.reverse()` metodunu kullanın.
 
-  _Type conversions_
+  _Tür Dönüşümleri_
 
-- `x.toHex(): string` – turns `BigInt` into a string of hexadecimal characters.
+- `x.toHex(): dize` – `BigInt`'i on altılık tabanda bir karakter dizesine dönüştürür.
 
-- `x.toString(): string` – turns `BigInt` into a decimal number string.
+- `x.toString(): dize` – `BigInt`'i ondalık tabanda bir dizeye dönüştürür.
 
-- `x.toI32(): i32` – returns the `BigInt` as an `i32`; fails if the value does not fit into `i32`. It's a good idea to first check `x.isI32()`.
+- `x.toI32(): i32` – `BigInt`'i bir `i32` olarak döndürür, değer `i32`'ye sığmazsa hata verir. İlk olarak `x.isI32()` kontrolünü yapmanız önerilir.
 
-- `x.toBigDecimal(): BigDecimal` - converts into a decimal with no fractional part.
+- `x.toBigDecimal(): BigDecimal` – Kesirli kısmı olmayan bir ondalık sayıya dönüştürür.
 
 _Math_
 
-- `x.plus(y: BigInt): BigInt` – can be written as `x + y`.
-- `x.minus(y: BigInt): BigInt` – can be written as `x - y`.
-- `x.times(y: BigInt): BigInt` – can be written as `x * y`.
-- `x.div(y: BigInt): BigInt` – can be written as `x / y`.
-- `x.mod(y: BigInt): BigInt` – can be written as `x % y`.
-- `x.equals(y: BigInt): bool` – can be written as `x == y`.
-- `x.notEqual(y: BigInt): bool` – can be written as `x != y`.
-- `x.lt(y: BigInt): bool` – can be written as `x < y`.
-- `x.le(y: BigInt): bool` – can be written as `x <= y`.
-- `x.gt(y: BigInt): bool` – can be written as `x > y`.
-- `x.ge(y: BigInt): bool` – can be written as `x >= y`.
-- `x.neg(): BigInt` – can be written as `-x`.
-- `x.divDecimal(y: BigDecimal): BigDecimal` – divides by a decimal, giving a decimal result.
-- `x.isZero(): bool` – Convenience for checking if the number is zero.
-- `x.isI32(): bool` – Check if the number fits in an `i32`.
-- `x.abs(): BigInt` – Absolute value.
-- `x.pow(exp: u8): BigInt` – Exponentiation.
-- `bitOr(x: BigInt, y: BigInt): BigInt` – can be written as `x | y`.
-- `bitAnd(x: BigInt, y: BigInt): BigInt` – can be written as `x & y`.
-- `leftShift(x: BigInt, bits: u8): BigInt` – can be written as `x << y`.
-- `rightShift(x: BigInt, bits: u8): BigInt` – can be written as `x >> y`.
+- `x.plus(y: BigInt): BigInt` – `x + y` şeklinde yazılabilir.
+- `x.minus(y: BigInt): BigInt` – `x - y` şeklinde yazılabilir.
+- `x.times(y: BigInt): BigInt` – `x * y` şeklinde yazılabilir.
+- `x.div(y: BigInt): BigInt` – `x / y` şeklinde yazılabilir.
+- `x.mod(y: BigInt): BigInt` – `x % y` şeklinde yazılabilir.
+- `x.equals(y: BigInt): bool` – `x == y` şeklinde yazılabilir.
+- `x.notEqual(y: BigInt): bool` – `x != y` şeklinde yazılabilir.
+- `x.lt(y: BigInt): bool` – `x < y` şeklinde yazılabilir.
+- `x.le(y: BigInt): bool` – `x <= y` şeklinde yazılabilir.
+- `x.gt(y: BigInt): bool` – `x > y` şeklinde yazılabilir.
+- `x.ge(y: BigInt): bool` – `x >= y` şeklinde yazılabilir.
+- `x.neg(): BigInt` – `-x` şeklinde yazılabilir.
+- `x.divDecimal(y: BigDecimal): BigDecimal` – Ondalık bir sayı ile böler ve ondalık bir sonuç döndürür.
+- `x.isZero(): bool` – Sayının sıfır olup olmadığını kontrol etmek için kullanışlı bir metot.
+- `x.isI32(): bool` – Sayının bir `i32`'ye sığıp sığmadığını kontrol eder.
+- `x.abs(): BigInt` – Mutlak değer.
+- `x.pow(exp: u8): BigInt` – Üs alma işlemi.
+- `bitOr(x: BigInt, y: BigInt): BigInt` – `x | y` olarak yazılabilir.
+- `bitAnd(x: BigInt, y: BigInt): BigInt` – `x & y` şeklinde yazılabilir.
+- `leftShift(x: BigInt, bits: u8): BigInt` – `x << y` şeklinde yazılabilir.
+- `rightShift(x: BigInt, bits: u8): BigInt` – `x >> y` şeklinde yazılabilir.
 
 #### TypedMap
 
@@ -164,15 +166,15 @@ _Math_
 import { TypedMap } from '@graphprotocol/graph-ts'
 ```
 
-`TypedMap` can be used to store key-value pairs. See [this example](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
+`TypedMap`, anahtar-değer çiftlerini saklamak için kullanılabilir. [Bu örneği](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51) inceleyebilirsiniz.
 
-The `TypedMap` class has the following API:
+`TypedMap` sınıfının API'si aşağıdaki gibidir:
 
-- `new TypedMap<K, V>()` – creates an empty map with keys of type `K` and values of type `V`
-- `map.set(key: K, value: V): void` – sets the value of `key` to `value`
-- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – returns the key-value pair for a `key` or `null` if the `key` does not exist in the map
-- `map.get(key: K): V | null` – returns the value for a `key` or `null` if the `key` does not exist in the map
-- `map.isSet(key: K): bool` – returns `true` if the `key` exists in the map and `false` if it does not
+- `new TypedMap<K, V>()` – `K` türünde anahtarlar ve `V` türünde değerler içeren boş bir eşlem oluşturur
+- `map.set(key: K, value: V): void` – `key` anahtarının değerini `value` olarak ayarlar
+- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – `key` için anahtar-değer çiftini döndürür, eğer `key` eşlemde mevcut değilse `null` döner
+- `map.get(key: K): V | null` – `key` için değeri döndürür, eğer `key` eşlemde mevcut değilse `null` döner
+- `map.isSet(key: K): bool` – Eğer `key` eşlemde mevcutsa `true`, değilse `false` döner
 
 #### Baytlar
 
@@ -180,25 +182,25 @@ The `TypedMap` class has the following API:
 import { Bytes } from '@graphprotocol/graph-ts'
 ```
 
-`Bytes` is used to represent arbitrary-length arrays of bytes. This includes Ethereum values of type `bytes`, `bytes32`, etc.
+`Bytes`, keyfi uzunluktaki bayt dizilerini temsil etmek için kullanılır. Buna Ethereum'daki `bytes`, `bytes32` gibi türler dahildir.
 
-The `Bytes` class extends AssemblyScript's [Uint8Array](https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) and this supports all the `Uint8Array` functionality, plus the following new methods:
+`Bytes` sınıfı, AssemblyScript'in [Uint8Array](https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) sınıfını genişletir ve `Uint8Array`'in tüm işlevselliğini destekler. Buna ek olarak, aşağıdaki yeni metotlara sahiptir:
 
-_Construction_
+_Oluşturma_
 
-- `fromHexString(hex: string) : Bytes` - Convert the string `hex` which must consist of an even number of hexadecimal digits to a `ByteArray`. The string `hex` can optionally start with `0x`
-- `fromI32(i: i32) : Bytes` - Convert `i` to an array of bytes
+- `fromHexString(hex: string): Bytes` – `hex` dizesini, on altı tabanında çift sayıda basamaktan oluşması koşuluyla bir `ByteArray`'e dönüştürür. `hex` dizesi isteğe bağlı olarak `0x` ile başlayabilir
+- `fromI32(i: i32): Bytes` – `i` değerini bir bayt dizisine dönüştürür
 
-_Type conversions_
+_Tür Dönüşümleri_
 
-- `b.toHex()` – returns a hexadecimal string representing the bytes in the array
-- `b.toString()` – converts the bytes in the array to a string of unicode characters
-- `b.toBase58()` – turns an Ethereum Bytes value to base58 encoding (used for IPFS hashes)
+- `b.toHex()` – dizideki baytları temsil eden on altı tabanında bir dize döndürür
+- `b.toString()` – dizideki baytları Unicode karakterlerinden oluşan bir dizeye dönüştürür
+- `b.toBase58()` – bir Ethereum Bytes değerini base58 kodlamasına (IPFS hash'leri için kullanılır) dönüştürür
 
-_Operators_
+_Operatörler_
 
-- `b.concat(other: Bytes) : Bytes` - - return new `Bytes` consisting of `this` directly followed by `other`
-- `b.concatI32(other: i32) : ByteArray` - return new `Bytes` consisting of `this` directly follow by the byte representation of `other`
+- `b.concat(other: Bytes): Bytes` – `this` dizisinin sonuna `other` dizisini ekleyerek yeni bir `Bytes` döndürür
+- `b.concatI32(other: i32): ByteArray` – `this` dizisinin sonrasına `other`'ın bayt temsilini eklenerek yeni bir `Bytes` döndürür
 
 #### Adres(Address)
 
@@ -206,12 +208,12 @@ _Operators_
 import { Address } from '@graphprotocol/graph-ts'
 ```
 
-`Address` extends `Bytes` to represent Ethereum `address` values.
+`Address`, Ethereum `address` değerlerini temsil etmek için `Bytes` sınıfını genişletir.
 
-It adds the following method on top of the `Bytes` API:
+`Bytes` API'sine ek olarak aşağıdaki metotları sağlar:
 
-- `Address.fromString(s: string): Address` – creates an `Address` from a hexadecimal string
-- `Address.fromBytes(b: Bytes): Address` – create an `Address` from `b` which must be exactly 20 bytes long. Passing in a value with fewer or more bytes will result in an error
+- `Address.fromString(s: dize): Address` – On altılık tabanda bir dizeden bir `Address` oluşturur
+- `Address.fromBytes(b: Bytes): Address` – Tam olarak 20 bayt uzunluğunda olması gereken `b` dizisinden bir `Address` oluşturur. Daha az veya daha fazla bayt içeren bir değer geçildiğinde hata verir
 
 ### Store API
 
@@ -219,9 +221,9 @@ It adds the following method on top of the `Bytes` API:
 import { store } from '@graphprotocol/graph-ts'
 ```
 
-The `store` API allows to load, save and remove entities from and to the Graph Node store.
+`store` API'si, varlıkları Graph Düğümü deposundan yüklemeye, depoya kaydetmeye ve depodan kaldırmaya olanak tanır.
 
-Entities written to the store map one-to-one to the `@entity` types defined in the subgraph's GraphQL schema. To make working with these entities convenient, the `graph codegen` command provided by the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) generates entity classes, which are subclasses of the built-in `Entity` type, with property getters and setters for the fields in the schema as well as methods to load and save these entities.
+Depoya yazılan varlıklar, subgraph'in GraphQL şemasında tanımlanan `@entity` türleriyle bire bir eşleşir. Bu varlıklarla çalışmayı kolaylaştırmak için [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) tarafından sağlanan `graph codegen` komutu varlık sınıfları oluşturur. Varlık sınıfları, şemadaki alanlar için özellik alıcıları ve ayarlayıcılarının yanı sıra bu varlıkları yüklemek ve kaydetmek için metotlar içeren, yerleşik `Entity` türünün alt sınıflarıdır.
 
 #### Unsurların Oluşturulması
 
@@ -239,20 +241,22 @@ export function handleTransfer(event: TransferEvent): void {
   // İşlem hash'ını olay kimliği olarak kullanarak bir Transfer varlığı oluşturun
   let id = event.transaction.hash
   let transfer = new Transfer(id)
-
+  
   // Olay parametrelerini kullanarak varlığın özelliklerini ayarlayın
   transfer.from = event.params.from
   transfer.to = event.params.to
   transfer.amount = event.params.amount
-
+  
   // Varlığı depoya kaydedin
   transfer.save()
-}
+  }
 ```
 
-When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
+Zincir işlenirken bir `Transfer` olayıyla karşılaşıldığında, oluşturulan `Transfer` türü (burada varlık türüyle adlandırma çakışmasını önlemek için `TransferEvent` olarak adlandırılmıştır) kullanılarak `handleTransfer` olay işleyicisine aktarılır. Bu tür, olayın ana işlemi ve parametreleri gibi verilere erişim sağlar.
+
+Her varlık, diğer varlıklarla çakışmayı önlemek için benzersiz bir ID'ye sahip olmalıdır. Genellikle olay parametrelerinin içinde bu iş için kullanılabilecek benzersiz bir tanımlayıcı bulunur.
 
-Çakışmaları önlemek için her varlık benzersiz bir kimliğe sahip olmalıdır. Genellikle olay parametreleri, kullanılabilecek benzersiz bir tanımlayıcı içerir. Not: Kimlik olarak işlem hash'ını kullanmak aynı işlemdeki başka hiçbir olayın bu hash'ı kullanarak kimlik olarak varlık oluşturmayacağını varsayar.
+> Not: ID olarak işlem hash'ini kullanmak, aynı işlemdeki diğer olayların bu hash'i ID olarak kullanarak varlık oluşturmadığını varsayar.
 
 #### Depodan varlık yükleme
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Transfer varlığı önceki gibi kullanılır
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+Varlık henüz depoda mevcut olmayabileceğinden, `load` yöntemi `Transfer | null` türünde bir değer döndürür. Değeri kullanmadan önce `null` olup olmadığını kontrol etmek gerekebilir.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Not: Varlıkları yüklemek, yalnızca, eşlemede yapılan değişikliklerin bir varlığın önceki verilerine bağlı olması durumunda gereklidir. Mevcut varlıkları güncellemenin iki yolunu görmek için bir sonraki bölüme bakın.
 
 #### Bir blok içinde oluşturulan varlıkları arama
 
-As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
+`graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 ve `@graphprotocol/graph-cli` v0.49.0 itibarıyla `loadInBlock` metodu tüm varlık türlerinde kullanılabilir hale gelmiştir.
 
-Store API, mevcut blokta oluşturulan veya güncellenen varlıkların alınmasını kolaylaştırır. Bunun için tipik bir durum, bir işleyicinin zincir üzerindeki bir etkinlikten bir İşlem oluşturması ve daha sonraki bir işleyicinin varsa bu işleme erişmek istemesidir. İşlemin mevcut olmadığı durumda, subgraph sadece varlığın mevcut olmadığını öğrenmek için veritabanına gitmek zorunda kalacaktır; eğer subgraph yazarı varlığın aynı blokta yaratılmış olması gerektiğini zaten biliyorsa, loadInBlock kullanmak bu veritabanı gidiş gelişini önler. Bazı subgraphlar için, bu kaçırılan aramalar indeksleme süresine önemli ölçüde katkıda bulunabilir.
+Store API'si mevcut blokta oluşturulan veya güncellenen varlıkların alınmasına olanak tanır. Bunun tipik bir örneği, bir işleyicinin zincir-üzeri bir olaydan bir işlem oluşturması ve sonraki bir işleyicinin, bu işlem mevcutsa ona erişmek istemesidir.
+
+- Eğer işlem mevcut değilse subgraph sırf varlığın mevcut olmadığını öğrenmek için veritabanına başvurmak zorunda kalacaktır. Ancak, subgraph yazarı varlığın aynı blokta oluşturulmuş olması gerektiğini zaten biliyorsa, `loadInBlock` kullanmak bu veritabanı sorgusunu ortadan kaldırır.
+- Bazı subgraph'lerde bu başarısız aramalar endeksleme süresine önemli ölçüde etki edebilir.
 
 ```typescript
 let id = event.transaction.hash // veya ID nasıl oluşturulurmuşsa
@@ -288,11 +295,11 @@ if (transfer == null) {
 // Transfer varlığını daha önce olduğu gibi kullanın
 ```
 
-> Note: If there is no entity created in the given block, `loadInBlock` will return `null` even if there is an entity with the given ID in the store.
+> Not: Belirtilen blokta bir varlık oluşturulmadıysa, depoda verilen ID'ye sahip bir varlık olsa bile `loadInBlock` yöntemi `null` döndürecektir.
 
 #### Türetilmiş varlıkları arama
 
-As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 and `@graphprotocol/graph-cli` v0.51.0 the `loadRelated` method is available.
+`graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 ve `@graphprotocol/graph-cli` v0.51.0 itibarıyla, `loadRelated` metodu kullanılabilir hale gelmiştir.
 
 Bu, türetilmiş varlık alanlarının bir olay işleyicisi içinden yüklenmesini sağlar. Örneğin, aşağıdaki şema göz önüne alındığında:
 
@@ -309,7 +316,7 @@ type Holder @entity {
 }
 ```
 
-The following code will load the `Token` entity that the `Holder` entity was derived from:
+Aşağıdaki kod, `Holder` varlığının türetildiği `Token` varlığını yükleyecektir:
 
 ```typescript
 let holder = Holder.load('test-id')
@@ -321,8 +328,8 @@ let tokens = holder.tokens.load()
 
 Mevcut bir varlığı güncellemenin iki yolu vardır:
 
-1. Load the entity with e.g. `Transfer.load(id)`, set properties on the entity, then `.save()` it back to the store.
-2. Simply create the entity with e.g. `new Transfer(id)`, set properties on the entity, then `.save()` it to the store. If the entity already exists, the changes are merged into it.
+1. `Transfer.load(id)` ya da benzeri bir metotla varlığı yükleyin, varlık üzerindeki özellikleri ayarlayın ve ardından `.save()` ile tekrar depoya kaydedin.
+2. `new Transfer(id)` ya da benzeri bir metotla varlığı oluşturun, varlık üzerindeki özellikleri ayarlayın ve ardından `.save()` ile depoya kaydedin. Eğer varlık zaten mevcutsa, yapılan değişiklikler mevcut varlıkla birleştirilir.
 
 Oluşturulan özellik ayarlayıcılar sayesinde çoğu durumda özellikerin değiştirilmesi kolaydır:
 
@@ -340,9 +347,9 @@ transfer.from.unset()
 transfer.from = null
 ```
 
-This only works with optional properties, i.e. properties that are declared without a `!` in GraphQL. Two examples would be `owner: Bytes` or `amount: BigInt`.
+Bu yalnızca isteğe bağlı özelliklerle çalışır, yani GraphQL'de `!` olmadan tanımlanan özelliklerle. Örnek olarak, `owner: Bytes` veya `amount: BigInt` verilebilir.
 
-Updating array properties is a little more involved, as the getting an array from an entity creates a copy of that array. This means array properties have to be set again explicitly after changing the array. The following assumes `entity` has a `numbers: [BigInt!]!` field.
+Dizi özelliklerini güncellemek biraz daha karmaşıktır, çünkü bir varlıktan bir dizi almak, o dizinin bir kopyasını oluşturur. Bu sebeple diziyi değiştirdikten sonra dizi özelliklerinin tekrar doğrudan ayarlanması gerekmektedir. Aşağıdaki örnek, `entity`nin bir `numbers: [BigInt!]!` alanına sahip olduğunu varsayar.
 
 ```typescript
 // Bu işe yaramaz
@@ -358,7 +365,7 @@ entity.save()
 
 #### Depodan varlık kaldırma
 
-There is currently no way to remove an entity via the generated types. Instead, removing an entity requires passing the name of the entity type and the entity ID to `store.remove`:
+Şu andabir varlığı oluşturulan türler aracılığıyla kaldırmanın bir yolu yoktur. Bunun yerine, bir varlığı kaldırmak için varlık türünün adını ve varlık ID'sini `store.remove` yöntemine iletmek gerekir:
 
 ```typescript
 import { store } from '@graphprotocol/graph-ts'
@@ -373,9 +380,9 @@ Ethereum API'si, akıllı sözleşmelere, genel durum değişkenlerine, sözleş
 
 #### Ethereum Türleri İçin Destek
 
-As with entities, `graph codegen` generates classes for all smart contracts and events used in a subgraph. For this, the contract ABIs need to be part of the data source in the subgraph manifest. Typically, the ABI files are stored in an `abis/` folder.
+Varlıklarda olduğu gibi `graph codegen`, bir subgraph'te kullanılan tüm akıllı sözleşmeler ve olaylar için sınıflar oluşturur. Bunun için, sözleşme ABI'lerinin subgraph manifestosundaki veri kaynağının bir parçası olması gerekir. ABI dosyaları genelde `abis/` klasöründe saklanır.
 
-With the generated classes, conversions between Ethereum types and the [built-in types](#built-in-types) take place behind the scenes so that subgraph authors do not have to worry about them.
+Oluşturulan sınıflarla sayesinde Ethereum türleri ile [yerleşik türler](#built-in-types) arasındaki dönüşümler arka planda gerçekleşir, böylece subgraph yazarlarının bu dönüşümlerle ilgilenmesine gerek kalmaz.
 
 Aşağıdaki örnek bunu açıklar. Aşağıdaki gibi bir subgraph şeması verildiğinde
 
@@ -388,7 +395,7 @@ type Transfer @entity {
 }
 ```
 
-and a `Transfer(address,address,uint256)` event signature on Ethereum, the `from`, `to` and `amount` values of type `address`, `address` and `uint256` are converted to `Address` and `BigInt`, allowing them to be passed on to the `Bytes!` and `BigInt!` properties of the `Transfer` entity:
+ve Ethereum üzerindeki `Transfer(address,address,uint256)` olay imzası için, sırasıyla `address`, `address` ve `uint256` türlerine sahip`from`, `to` ve `amount` değerleri, `Address` ve `BigInt` türlerine dönüştürülür. Bu sayede, bu değerler `Transfer` varlığındaki `Bytes!` ve `BigInt!` özelliklerine aktarılabilir:
 
 ```typescript
 let id = event.transaction.hash
@@ -401,7 +408,7 @@ transfer.save()
 
 #### Olaylar ve Blok/İşlem Verileri
 
-Ethereum events passed to event handlers, such as the `Transfer` event in the previous examples, not only provide access to the event parameters but also to their parent transaction and the block they are part of. The following data can be obtained from `event` instances (these classes are a part of the `ethereum` module in `graph-ts`):
+Önceki örneklerdeki `Transfer` olayı gibi olay işleyicilere iletilen Ethereum olayları, sadece olay parametrelerine değil, aynı zamanda bu olayların ait olduğu işlem ve blok bilgilerine de erişim sağlar. `event` örneklerinden aşağıdaki veriler elde edilebilir (bu sınıflar `graph-ts` içindeki `ethereum` modülünün bir parçasıdır):
 
 ```typescript
 class Event {
@@ -476,7 +483,7 @@ class Log {
 
 #### Akıllı Sözleşme Durumuna Erişim
 
-The code generated by `graph codegen` also includes classes for the smart contracts used in the subgraph. These can be used to access public state variables and call functions of the contract at the current block.
+`graph codegen` tarafından oluşturulan kod, subgraph'te kullanılan akıllı sözleşmeler için sınıflar da içerir. Bu sınıflar, mevcut blokta sözleşmenin genel durum değişkenlerine erişmek ve sözleşme fonksiyonlarını çağırmak için kullanılabilir.
 
 Yaygın bir model, bir olayın kaynaklandığı sözleşmeye erişmektir. Bu, aşağıdaki kodla elde edilir:
 
@@ -495,15 +502,17 @@ export function handleTransfer(event: TransferEvent) {
 }
 ```
 
-`Transfer` is aliased to `TransferEvent` here to avoid a naming conflict with the entity type
+Burada `Transfer`, varlık türüyle adlandırma çakışmasını önlemek için `TransferEvent` olarak yeniden adlandırılmıştır
 
-As long as the `ERC20Contract` on Ethereum has a public read-only function called `symbol`, it can be called with `.symbol()`. For public state variables a method with the same name is created automatically.
+Ethereum üzerindeki `ERC20Contract` sözleşmesi `symbol` adında herkese açık ve salt okunur bir fonksiyona sahip olduğu sürece, `.symbol()` ile çağrılabilir. Genel durum değişkenleri için otomatik olarak aynı ada sahip bir metot oluşturulur.
 
 Subgraph parçası olan diğer tüm sözleşmelerde oluşturulan koddan içe aktarılabilir ve geçerli bir adrese bağlanabilir.
 
 #### Geri Dönen Çağrıları Yönetme
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+Eğer sözleşmenizin salt okunur metotlarıının başarısız olması (revert) mümkünse, kodunuzu `try_` öneki ile oluşturulmuş sözleşme metodunu çağırarak çözümleyebilirsiniz (handle).
+
+- Örneğin, Gravity sözleşmesi `gravatarToOwner` metodunu dışa açar. Bu kod, metodun başarısızlıkla sonuçlanmasını (revert) çözümleyebilir:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,11 +524,11 @@ if (callResult.reverted) {
 }
 ```
 
-Bir Geth veya Infura istemcisine bağlı bir Graph düğümünün tüm geri dönüşleri algılamayabileceğini unutmayın, bu durumda Parity istemcisine bağlı bir Graph düğümü kullanmanızı öneririz.
+> Not: Geth veya Infura istemcisine bağlı bir Graph Düğümü tüm başarısızlıkları (revert) algılamayabilir. Buna bel bağlıyorsanız Parity istemcisine bağlı bir Graph Düğümü kullanmanızı öneririz.
 
 #### ABI Kodlama/Çözme
 
-Data can be encoded and decoded according to Ethereum's ABI encoding format using the `encode` and `decode` functions in the `ethereum` module.
+Veriler, `ethereum` modülündeki `encode` ve `decode` fonksiyonları kullanılarak Ethereum'un ABI kodlama formatına göre kodlanabilir ve kodu çözülebilir.
 
 ```typescript
 import { Address, BigInt, ethereum } from '@graphprotocol/graph-ts'
@@ -539,32 +548,32 @@ let decoded = ethereum.decode('(address,uint256)', encoded)
 Daha fazla bilgi için:
 
 - [ABI Spec](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
-- Encoding/decoding [Rust library/CLI](https://github.com/rust-ethereum/ethabi)
-- More [complex example](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
+- Kodlama/kod çözme [Rust kütüphanesi/CLI](https://github.com/rust-ethereum/ethabi)
+- Daha [karmaşık bir örnek](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
 
-#### Balance of an Address
+#### Bir Adresin Bakiyesi
 
-The native token balance of an address can be retrieved using the `ethereum` module. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`. The `getBalance()` retrieves the balance of the specified address as of the end of the block in which the event is triggered.
+Bir adresin yerel token bakiyesi `ethereum` modülü kullanılarak elde edilebilir. Bu özellik, `subgraph.yaml` dosyasında tanımlanan `apiVersion: 0.0.9` itibarıyla kullanılabilir. `getBalance()` fonksiyonu, belirtilen adresin olayın tetiklendiği blok sonundaki bakiyesini alır.
 
 ```typescript
 import { ethereum } from '@graphprotocol/graph-ts'
 
 let address = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
-let balance = ethereum.getBalance(address) // returns balance in BigInt
+let balance = ethereum.getBalance(address) // bakiyeyi BigInt olarak döndürür
 ```
 
-#### Check if an Address is a Contract or EOA
+#### Bir Adresin Akıllı Sözleşme veya EOA (Harici Sahipli Hesap) Olup Olmadığını Kontrol Etme
 
-To check whether an address is a smart contract address or an externally owned address (EOA), use the `hasCode()` function from the `ethereum` module which will return `boolean`. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`.
+Bir adresin akıllı sözleşme adresi mi yoksa harici sahipli bir adres (EOA) mi olduğunu kontrol etmek için, `ethereum` modülündeki `hasCode()` fonksiyonu kullanılabilir. Bu fonksiyon `boolean` döner. Bu özellik `subgraph.yaml` dosyasında tanımlanan `apiVersion: 0.0.9` itibarıyla kullanılabilir.
 
 ```typescript
 import { ethereum } from '@graphprotocol/graph-ts'
 
 let contractAddr = Address.fromString('0x2E645469f354BB4F5c8a05B3b30A929361cf77eC')
-let isContract = ethereum.hasCode(contractAddr).inner // returns true
+let isContract = ethereum.hasCode(contractAddr).inner // true döndürür
 
 let eoa = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
-let isContract = ethereum.hasCode(eoa).inner // returns false
+let isContract = ethereum.hasCode(eoa).inner // false döndürür
 ```
 
 ### Logging API
@@ -573,17 +582,17 @@ let isContract = ethereum.hasCode(eoa).inner // returns false
 import { log } from '@graphprotocol/graph-ts'
 ```
 
-The `log` API allows subgraphs to log information to the Graph Node standard output as well as Graph Explorer. Messages can be logged using different log levels. A basic format string syntax is provided to compose log messages from argument.
+`log` API'si, subgraph'lerin bilgileri Graph Düğümü standart çıktısına ve Graph Gezgini'ne kaydetmesine olanak tanır. Mesajlar farklı günlük seviyeleri kullanılarak kaydedilebilir. Verilen argümanlardan günlük mesajlarını oluşturmak için temel bir biçimlendirme dizesi sentaksı sunulmaktadır.
 
-The `log` API includes the following functions:
+`log` API'si aşağıdaki fonksiyonları içerir:
 
-- `log.debug(fmt: string, args: Array<string>): void` - logs a debug message.
-- `log.info(fmt: string, args: Array<string>): void` - logs an informational message.
-- `log.warning(fmt: string, args: Array<string>): void` - logs a warning.
-- `log.error(fmt: string, args: Array<string>): void` - logs an error message.
-- `log.critical(fmt: string, args: Array<string>): void` – logs a critical message _and_ terminates the subgraph.
+- `log.debug(fmt: string, args: Array<string>): void` – bir hata ayıklama mesajı kaydeder.
+- `log.info(fmt: string, args: Array<string>): void` – bir bilgilendirme mesajı kaydeder.
+- `log.warning(fmt: string, args: Array<string>): void` – bir uyarı mesajı kaydeder.
+- `log.error(fmt: string, args: Array<string>): void` – bir hata mesajı kaydeder.
+- `log.critical(fmt: string, args: Array<string>): void` – kritik bir mesaj kaydeder **ve** subgraph'i sonlandırır.
 
-The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
+`log` API'si bir format dizesi ve bir dize değerleri dizisini alır. Daha sonra, dizideki dize değerlerini format dizesindeki yer tutucuların yerine koyar. İlk `{}` yer tutucusu dizideki ilk değerle, ikinci `{}` yer tutucusu ikinci değerle ve bu şekilde devam ederek değiştirilir.
 
 ```typescript
 log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.toString(), 'already a string'])
@@ -593,7 +602,7 @@ log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.
 
 ##### Tek bir değerin loglanması
 
-In the example below, the string value "A" is passed into an array to become`['A']` before being logged:
+Aşağıdaki örnekte, "A" dize değeri, kaydedilmeden önce bir diziye dönüştürülerek `['A']` haline getirilir:
 
 ```typescript
 let myValue = 'A'
@@ -619,7 +628,7 @@ export function handleSomeEvent(event: SomeEvent): void {
 
 #### Mevcut bir diziden birden çok girişi kaydetme
 
-Each entry in the arguments array requires its own placeholder `{}` in the log message string. The below example contains three placeholders `{}` in the log message. Because of this, all three values in `myArray` are logged.
+Argüman dizisindeki her girişin günlük mesajındaki bir yer tutucu `{}` ile eşleşmesi gerekir. Aşağıdaki örnek, günlük mesajında üç yer tutucu `{}` içerir. Bu nedenle, `myArray`'deki üç değerin üçü de loglanır.
 
 ```typescript
 let myArray = ['A', 'B', 'C']
@@ -663,7 +672,7 @@ export function handleSomeEvent(event: SomeEvent): void {
 import { ipfs } from '@graphprotocol/graph-ts'
 ```
 
-Smart contracts occasionally anchor IPFS files on chain. This allows mappings to obtain the IPFS hashes from the contract and read the corresponding files from IPFS. The file data will be returned as `Bytes`, which usually requires further processing, e.g. with the `json` API documented later on this page.
+Akıllı sözleşmeler bazen IPFS dosyalarını zincire sabitler. Bu, eşlemelerin sözleşmeden IPFS hash'lerini almasını ve ilgili dosyaları IPFS'ten okumasını sağlar. Dosya verileri `Bytes` olarak döndürülür ve genellikle daha fazla işleme tabi tutulması gerekir; örneğin, bu sayfada daha sonra belgelenen `json` API'si ile.
 
 IPFS hash'ı veya yolu verildiğinde, bir dosyayı IPFS'den okuma şu şekilde yapılır:
 
@@ -679,9 +688,9 @@ let path = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile'
 let data = ipfs.cat(path)
 ```
 
-**Note:** `ipfs.cat` is not deterministic at the moment. If the file cannot be retrieved over the IPFS network before the request times out, it will return `null`. Due to this, it's always worth checking the result for `null`.
+**Not:** Şu anda `ipfs.cat` deterministik değildir. Eğer dosya, IPFS ağı üzerinden, talebin zaman aşımından önce getirilemezse, fonksiyon `null` döndürür. Bu nedenle, sonucun`null` olup olmadığını kontrol etmek her zaman önemlidir.
 
-It is also possible to process larger files in a streaming fashion with `ipfs.map`. The function expects the hash or path for an IPFS file, the name of a callback, and flags to modify its behavior:
+Ayrıca, daha büyük dosyaları akış halinde işlemek için `ipfs.map` kullanmak da mümkündür. Bu fonksiyon, bir IPFS dosyasının hash'ini veya yolunu, bir geri çağırma işlevinin adını ve davranışını değiştirmek için bayraklar alır:
 
 ```typescript
 import { JSONValue, Value } from '@graphprotocol/graph-ts'
@@ -711,9 +720,9 @@ ipfs.map('Qm...', 'processItem', Value.fromString('parentId'), ['json'])
 ipfs.mapJSON('Qm...', 'processItem', Value.fromString('parentId'))
 ```
 
-The only flag currently supported is `json`, which must be passed to `ipfs.map`. With the `json` flag, the IPFS file must consist of a series of JSON values, one value per line. The call to `ipfs.map` will read each line in the file, deserialize it into a `JSONValue` and call the callback for each of them. The callback can then use entity operations to store data from the `JSONValue`. Entity changes are stored only when the handler that called `ipfs.map` finishes successfully; in the meantime, they are kept in memory, and the size of the file that `ipfs.map` can process is therefore limited.
+Şu anda desteklenen tek bayrak `ipfs.map`'e iletilmesi gereken `json` bayrağıdır. `json` bayrağı ile IPFS dosyası, her satırda bir JSON değeri olacak şekilde bir dizi JSON değerinden oluşmalıdır. `ipfs.map` çağrısı, dosyadaki her satırı okur, bir `JSONValue` olarak ayrıştırır (deserialize eder) ve her biri için geri çağırma (callback) fonksiyonunu çağırır. Geri çağırma fonksiyonu daha sonra `JSONValue`dan gelen verileri depolamak için varlık operasyonlarını kullanabilir. Varlık değişiklikleri yalnızca `ipfs.map`'i çağıran işleyici başarıyla tamamlandığında depolanır; bu sırada değişiklikler bellekte tutulur ve bu nedenle `ipfs.map`'in işleyebileceği dosya boyutu sınırlıdır.
 
-On success, `ipfs.map` returns `void`. If any invocation of the callback causes an error, the handler that invoked `ipfs.map` is aborted, and the subgraph is marked as failed.
+Başarılı olduğunda `ipfs.map`, `void` döndürür. Geri çağırma fonksiyonunun herhangi bir çağrısı bir hataya neden olursa, `ipfs.map`'i çağıran işleyici durdurulur ve subgraph başarısız olarak işaretlenir.
 
 ### Kripto(Crypto) API'si
 
@@ -721,7 +730,7 @@ On success, `ipfs.map` returns `void`. If any invocation of the callback causes
 import { crypto } from '@graphprotocol/graph-ts'
 ```
 
-The `crypto` API makes a cryptographic functions available for use in mappings. Right now, there is only one:
+`crypto` API'si, eşlemelerde kullanılan kriptografik fonksiyonları sağlar. Şu anda yalnızca bir fonksiyon mevcuttur:
 
 - `crypto.keccak256(input: ByteArray): ByteArray`
 
@@ -731,14 +740,14 @@ The `crypto` API makes a cryptographic functions available for use in mappings.
 import { json, JSONValueKind } from '@graphprotocol/graph-ts'
 ```
 
-JSON data can be parsed using the `json` API:
+JSON verileri, `json` API'si kullanılarak ayrıştırılabilir:
 
-- `json.fromBytes(data: Bytes): JSONValue` – parses JSON data from a `Bytes` array interpreted as a valid UTF-8 sequence
-- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – safe version of `json.fromBytes`, it returns an error variant if the parsing failed
-- `json.fromString(data: string): JSONValue` – parses JSON data from a valid UTF-8 `String`
-- `json.try_fromString(data: string): Result<JSONValue, boolean>` – safe version of `json.fromString`, it returns an error variant if the parsing failed
+- `json.fromBytes(data: Bytes): JSONValue` – Geçerli bir UTF-8 sekansı olarak yorumlanan bir `Bytes` dizisinden JSON verisini ayrıştırır
+- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – `json.fromBytes`'in güvenli versiyonu. Ayrıştırma başarısız olursa bir hata döndürür
+- `json.fromString(data: string): JSONValue` – Geçerli bir UTF-8 `String`den JSON verilerini ayrıştırır
+- `json.try_fromString(data: string): Result<JSONValue, boolean>` – `json.fromString`'in güvenli versiyonu. Ayrıştırma başarısız olursa bir hata döndürür
 
-The `JSONValue` class provides a way to pull values out of an arbitrary JSON document. Since JSON values can be booleans, numbers, arrays and more, `JSONValue` comes with a `kind` property to check the type of a value:
+`JSONValue` sınıfı, rastgele bir JSON belgesinden değerleri çekmek için bir yol sağlar. JSON değerleri boolean, sayı, dizi gibi türlerde olabileceği için, `JSONValue` sınıfı bir değerin türünü kontrol etmek için `kind` özelliği ile birlikte gelir:
 
 ```typescript
 let value = json.fromBytes(...)
@@ -747,63 +756,63 @@ if (value.kind == JSONValueKind.BOOL) {
 }
 ```
 
-In addition, there is a method to check if the value is `null`:
+Ayrıca, değerin `null` olup olmadığını kontrol etmek için bir metot da vardır:
 
 - `value.isNull(): boolean`
 
-When the type of a value is certain, it can be converted to a [built-in type](#built-in-types) using one of the following methods:
+Bir değerin türü kesin olduğunda, aşağıdaki yöntemlerden biri kullanılarak [yerleşik türlerden](#built-in-types) birine dönüştürülebilir:
 
 - `value.toBool(): boolean`
 - `value.toI64(): i64`
 - `value.toF64(): f64`
 - `value.toBigInt(): BigInt`
 - `value.toString(): string`
-- `value.toArray(): Array<JSONValue>` - (and then convert `JSONValue` with one of the 5 methods above)
+- `value.toArray(): Array<JSONValue>` – (ve ardından `JSONValue` değerini yukarıdaki 5 metottan biriyle dönüştürün)
 
 ### Tip Dönüşümleri Referansı
 
-| Source(s)         | Destination       | Conversion function          |
-| ----------------- | ----------------- | ---------------------------- |
-| Address           | Bytes             | none                         |
-| Address           | String            | s.toHexString()              |
-| BigDecimal        | String            | s.toString()                 |
-| BigInt            | BigDecimal        | s.toBigDecimal()             |
-| BigInt            | Dizgi (onaltılık) | s.toHexString() or s.toHex() |
-| BigInt            | String (unicode)  | s.toString()                 |
-| BigInt            | i32               | s.toI32()                    |
-| Boolean           | Boolean           | none                         |
-| Bytes (signed)    | BigInt            | BigInt.fromSignedBytes(s)    |
-| Bytes (unsigned)  | BigInt            | BigInt.fromUnsignedBytes(s)  |
-| Bytes             | Dizgi (onaltılık) | s.toHexString() or s.toHex() |
-| Bytes             | String (unicode)  | s.toString()                 |
-| Bytes             | String (base58)   | s.toBase58()                 |
-| Bytes             | i32               | s.toI32()                    |
-| Bytes             | u32               | s.toU32()                    |
-| Bytes             | JSON              | json.fromBytes(s)            |
-| int8              | i32               | none                         |
-| int32             | i32               | none                         |
-| int32             | BigInt            | BigInt.fromI32(s)            |
-| uint24            | i32               | none                         |
-| int64 - int256    | BigInt            | none                         |
-| uint32 - uint256  | BigInt            | none                         |
-| JSON              | boolean           | s.toBool()                   |
-| JSON              | i64               | s.toI64()                    |
-| JSON              | u64               | s.toU64()                    |
-| JSON              | f64               | s.toF64()                    |
-| JSON              | BigInt            | s.toBigInt()                 |
-| JSON              | string            | s.toString()                 |
-| JSON              | Array             | s.toArray()                  |
-| JSON              | Object            | s.toObject()                 |
-| String            | Address           | Address.fromString(s)        |
-| Bytes             | Address           | Address.fromBytes(s)         |
-| String            | BigInt            | BigInt.fromString(s)         |
-| String            | BigDecimal        | BigDecimal.fromString(s)     |
-| Dizgi (onaltılık) | Bytes             | ByteArray.fromHexString(s)   |
-| String (UTF-8)    | Bytes             | ByteArray.fromUTF8(s)        |
+| Kaynak(lar)            | Hedef                | Dönüşüm fonksiyonu           |
+| ---------------------- | -------------------- | ---------------------------- |
+| Address                | Bytes                | yok                          |
+| Address                | String               | s.toHexString()              |
+| BigDecimal             | String               | s.toString()                 |
+| BigInt                 | BigDecimal           | s.toBigDecimal()             |
+| BigInt                 | Dizgi (onaltılık)    | s.toHexString() or s.toHex() |
+| BigInt                 | String (unicode)     | s.toString()                 |
+| BigInt                 | i32                  | s.toI32()                    |
+| Boolean                | Boolean              | yok                          |
+| Bytes (işaretli)       | BigInt               | BigInt.fromSignedBytes(s)    |
+| Bytes (işaretsiz)      | BigInt               | BigInt.fromUnsignedBytes(s)  |
+| Bytes                  | Dizgi (onaltılık)    | s.toHexString() or s.toHex() |
+| Bytes                  | String (unicode)     | s.toString()                 |
+| Bytes                  | String (base58)      | s.toBase58()                 |
+| Bytes                  | i32                  | s.toI32()                    |
+| Bytes                  | u32                  | s.toU32()                    |
+| Bytes                  | JSON                 | json.fromBytes(s)            |
+| int8                   | i32                  | yok                          |
+| int32                  | i32                  | yok                          |
+| int32                  | BigInt               | BigInt.fromI32(s)            |
+| uint24                 | i32                  | yok                          |
+| int64 - int256         | BigInt               | yok                          |
+| uint32 - uint256       | BigInt               | yok                          |
+| JSON                   | boolean              | s.toBool()                   |
+| JSON                   | i64                  | s.toI64()                    |
+| JSON                   | u64                  | s.toU64()                    |
+| JSON                   | f64                  | s.toF64()                    |
+| JSON                   | BigInt               | s.toBigInt()                 |
+| JSON                   | string               | s.toString()                 |
+| JSON                   | Array                | s.toArray()                  |
+| JSON                   | Object               | s.toObject()                 |
+| String                 | Address              | Address.fromString(s)        |
+| Bytes                  | Address              | Address.fromBytes(s)         |
+| String                 | BigInt               | BigInt.fromString(s)         |
+| String                 | BigDecimal           | BigDecimal.fromString(s)     |
+| Dizgi (onaltılık)      | Bytes                | ByteArray.fromHexString(s)   |
+| String (UTF-8)         | Bytes                | ByteArray.fromUTF8(s)        |
 
 ### Veri Kaynağı Meta Verileri
 
-You can inspect the contract address, network and context of the data source that invoked the handler through the `dataSource` namespace:
+`dataSource` ad alanı üzerinden işleyiciyi çağıran veri kaynağının sözleşme adresini, ağını ve bağlamını inceleyebilirsiniz:
 
 - `dataSource.address(): Address`
 - `dataSource.network(): string`
@@ -811,7 +820,7 @@ You can inspect the contract address, network and context of the data source tha
 
 ### Varlık ve VeriKaynağıBağlamı
 
-The base `Entity` class and the child `DataSourceContext` class have helpers to dynamically set and get fields:
+Temel `Entity` sınıfı ve alt sınıf olan `DataSourceContext` sınıfı, alanları dinamik olarak ayarlamak ve almak için yardımcı programlara sahiptir:
 
 - `setString(key: string, value: string): void`
 - `setI32(key: string, value: i32): void`
@@ -828,9 +837,9 @@ The base `Entity` class and the child `DataSourceContext` class have helpers to
 
 ### Manifest'teki DataSourceContext
 
-The `context` section within `dataSources` allows you to define key-value pairs that are accessible within your subgraph mappings. The available types are `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`.
+`dataSources` içindeki `context` bölümü, subgraph eşlemeleriniz içinde erişilebilen anahtar-değer çiftlerini tanımlamanıza olanak tanır. Kullanılabilir türler şunlardır: `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List` ve `BigInt`.
 
-Here is a YAML example illustrating the usage of various types in the `context` section:
+İşte `context` bölümünde çeşitli türlerin kullanımını gösteren bir YAML örneği:
 
 ```yaml
 dataSources:
@@ -870,13 +879,13 @@ dataSources:
         data: '1000000000000000000000000'
 ```
 
-- `Bool`: Specifies a Boolean value (`true` or `false`).
-- `String`: Specifies a String value.
-- `Int`: Specifies a 32-bit integer.
-- `Int8`: Specifies an 8-bit integer.
-- `BigDecimal`: Specifies a decimal number. Must be quoted.
-- `Bytes`: Specifies a hexadecimal string.
-- `List`: Specifies a list of items. Each item needs to specify its type and data.
-- `BigInt`: Specifies a large integer value. Must be quoted due to its large size.
+- `Bool`: Boolean bir değer (`true` veya `false`) belirtir.
+- `String`: Bir String (dize) değeri belirtir.
+- `Int`: 32-bit bir tamsayı belirtir.
+- `Int8`: 8-bit bir tamsayı belirtir.
+- `BigDecimal`: Ondalık bir sayı belirtir. Tırnak içinde yazılması gerekir.
+- `Bytes`: On altılık tabanda (hexadecimal) bir dizeyi belirtir.
+- `List`: Elemanlardan oluşan bir liste belirtir. Her elemanın türü ve verisi belirtilmelidir.
+- `BigInt`: Büyük bir tamsayı değeri belirtir. Büyük boyutu nedeniyle tırnak içinde yazılması gerekir.
 
 Bu bağlama daha sonra subgraph eşleştirme dosyalarınızdan erişilebilir ve böylece daha dinamik ve yapılandırılabilir subgraphlar elde edebilirsiniz.

From 0cec876571b61e8ca370eb50fd2f2901391a7ac6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:03 -0500
Subject: [PATCH 0321/1325] New translations api.mdx (Ukrainian)

---
 website/pages/uk/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/uk/developing/graph-ts/api.mdx b/website/pages/uk/developing/graph-ts/api.mdx
index 46442dfa941e..8fc1f4b48b61 100644
--- a/website/pages/uk/developing/graph-ts/api.mdx
+++ b/website/pages/uk/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API Reference
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Built-in Types
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Handling Reverted Calls
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Encoding/Decoding ABI
 

From 75ebcf1176acddc655bc9b9e0e6e7320997048e2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:04 -0500
Subject: [PATCH 0322/1325] New translations api.mdx (Chinese Simplified)

---
 website/pages/zh/developing/graph-ts/api.mdx | 55 ++++++++++++--------
 1 file changed, 32 insertions(+), 23 deletions(-)

diff --git a/website/pages/zh/developing/graph-ts/api.mdx b/website/pages/zh/developing/graph-ts/api.mdx
index 31c2c0eaf4f5..0bb53153fae9 100644
--- a/website/pages/zh/developing/graph-ts/api.mdx
+++ b/website/pages/zh/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> 注意：如果您在 `graph-cli`/`graph-ts` 版本 `0.22.0` 之前创建了子图，那么您正在使用较旧版本的 AssemblyScript，我们建议查看[`迁移指南`](/release-notes/assemblyscript-migration-guide)。
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-此页面记录了编写子图映射时可以使用的内置 API。有两种开箱即用的 API：
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- 通过 `graph codegen` 生成的子图文件中的代码。
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-也可以添加其他库作为依赖项，只要它们与[AssemblyScript](https://github.com/AssemblyScript/assemblyscript)兼容即可。由于这是语言映射所写的，因此[AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki)是语言和标准库特性的良好来源。
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API 参考
 
@@ -27,16 +29,16 @@ title: AssemblyScript API
 
 子图清单中的 `apiVersion` 指定了由 Graph Node 运行的特定子图的映射 API 版本。
 
-| 版本 | Release 说明 |
-| :-: | --- |
+|   版本  | Release 说明                                                                                                                   |
+| :---: | ---------------------------------------------------------------------------------------------------------------------------- |
 | 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | 添加了 `TransactionReceipt` 和 `Log` 类到以太坊类型。<br />已将 `receipt` 字段添加到Ethereum Event对象。 |
-| 0.0.6 | 向Ethereum Transaction对象添加了 nonce 字段 向 Etherum Block对象添加<br /> baseFeePerGas字段 |
-| 0.0.5 | AssemblyScript 升级到版本 0.19.10(这包括重大更改，参阅 <br />迁移指南)ethereum.transaction.gasUsed 重命名为 ethereum.transaction.gasLimit |
-| 0.0.4 | 已向 Ethereum SmartContractCall对象添加了 `functionSignature` 字段。 |
-| 0.0.3 | 已向Ethereum Call 对象添加了 `from` 字段。<br />`etherem.call.address` 被重命名为 `ethereum.call.to`。 |
-| 0.0.2 | 已向Ethereum Transaction对象添加了 `input` 字段。 |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity.                                                 |
+| 0.0.7 | 添加了 `TransactionReceipt` 和 `Log` 类到以太坊类型。<br />已将 `receipt` 字段添加到Ethereum Event对象。                                           |
+| 0.0.6 | 向Ethereum Transaction对象添加了 nonce 字段 向 Etherum Block对象添加<br /> baseFeePerGas字段                                                |
+| 0.0.5 | AssemblyScript 升级到版本 0.19.10(这包括重大更改，参阅 <br />迁移指南)ethereum.transaction.gasUsed 重命名为 ethereum.transaction.gasLimit           |
+| 0.0.4 | 已向 Ethereum SmartContractCall对象添加了 `functionSignature` 字段。                                                                   |
+| 0.0.3 | 已向Ethereum Call 对象添加了 `from` 字段。<br />`etherem.call.address` 被重命名为 `ethereum.call.to`。                                       |
+| 0.0.2 | 已向Ethereum Transaction对象添加了 `input` 字段。                                                                                      |
 
 ### 内置类型
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 如果在处理链时遇到 Transfer 事件，它会使用生成的 Transfer 类型(别名为 TransferEvent 以避免与实体类型的命名冲突) 传递给 handleTransfer 事件处理器。 此类型允许访问事件的母交易及其参数等数据。
 
-每个实体都必须有一个唯一的 ID 以避免与其他实体发生冲突。 事件参数包含可以使用的唯一标识符是相当常见的。 注意：使用交易hash作为 ID 时， 假定同一交易中没有其他事件创建以该hash作为 ID 的实体。
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### 从存储中加载实体
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-由于实体可能尚未存在于存储中，因此 `load` 方法返回一个类型为 `Transfer | null` 的值。因此，在使用该值之前可能需要检查 `null` 情况。
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **注意:** 只有在映射中的更改依赖于实体的先前数据时，加载实体才是必要的。请参阅下一节，了解更新现有实体的两种方法。
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### 查找在区块中创建的实体
 
 截至 `graph-node` v0.31.0、`@graphprotocol/graph-ts` v0.30.0 和 `@graphprotocol/graph-cli` v0.49.0，所有实体类型上都提供了 `loadInBlock` 方法。
 
-存储API有助于检索在当前区块中创建或更新的实体。这方面的一种典型情况是，一个处理程序从某个链上事件创建一个，之交易后的处理程序希望访问该交易（如果存在）。在交易不存在的情况下，子图必须去数据库才能发现实体不存在；如果子图作者已经知道实体必须是在同一个区块中创建的，那么使用loadInBlock可以避免这种数据库往返。对于某些子图，这些遗漏的查找可能会显著增加索引时间。
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -502,7 +509,9 @@ export function handleTransfer(event: TransferEvent) {
 
 #### 处理重复调用
 
-如果您的合约的只读方法可能回滚，则应通过在生成的合约方法前加上 `try_` 来处理。例如，Gravity 合约暴露了 `gravatarToOwner` 方法。下面的代码可以处理该方法中的回滚：
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -514,7 +523,7 @@ if (callResult.reverted) {
 }
 ```
 
-请注意，连接到 Geth 或 Infura 客户端的 Graph 节点可能无法检测到所有重复使用，如果您依赖于此，我们建议使用连接到 Parity 客户端的 Graph 节点。
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### 编码/解码 ABI
 
@@ -760,19 +769,19 @@ if (value.kind == JSONValueKind.BOOL) {
 
 ### 类型转换参考
 
-| 源类型               | 目标类型             | 转换函数                     |
+| 源类型                  | 目标类型                 | 转换函数                         |
 | -------------------- | -------------------- | ---------------------------- |
 | Address              | Bytes                | none                         |
 | Address              | String               | s.toHexString()              |
 | BigDecimal           | String               | s.toString()                 |
 | BigInt               | BigDecimal           | s.toBigDecimal()             |
-| BigInt               | String (hexadecimal) | s.toHexString() 或 s.toHex() |
+| BigInt               | String (hexadecimal) | s.toHexString() 或 s.toHex()  |
 | BigInt               | String (unicode)     | s.toString()                 |
 | BigInt               | i32                  | s.toI32()                    |
 | Boolean              | Boolean              | none                         |
 | Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
 | Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)  |
-| Bytes                | String (hexadecimal) | s.toHexString() 或 s.toHex() |
+| Bytes                | String (hexadecimal) | s.toHexString() 或 s.toHex()  |
 | Bytes                | String (unicode)     | s.toString()                 |
 | Bytes                | String (base58)      | s.toBase58()                 |
 | Bytes                | i32                  | s.toI32()                    |

From e2af508c16f292eeff2bb29c7d2f17e36ea25943 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:05 -0500
Subject: [PATCH 0323/1325] New translations api.mdx (Urdu (Pakistan))

---
 website/pages/ur/developing/graph-ts/api.mdx | 49 ++++++++++++--------
 1 file changed, 29 insertions(+), 20 deletions(-)

diff --git a/website/pages/ur/developing/graph-ts/api.mdx b/website/pages/ur/developing/graph-ts/api.mdx
index 4229c68d4bfe..a8d423b77148 100644
--- a/website/pages/ur/developing/graph-ts/api.mdx
+++ b/website/pages/ur/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: اسمبلی اسکرپٹ API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-یہ صفحہ دستاویز کرتا ہے کہ سب گراف میپنگ لکھتے وقت کیا بلٹ ان APIs استعمال کیا جا سکتا ہے۔ دو قسم کے APIs باکس سے باہر دستیاب ہیں:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API حوالہ
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| ورزن | جاری کردہ نوٹس |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+|  ورزن | جاری کردہ نوٹس                                                                                                                                                                                                                                |
+| :---: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
 | 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### بلٹ ان اقسام
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-دیگر ہستیوں کے ساتھ ٹکراؤ سے بچنے کے لیے ہر ایک کے پاس ایک منفرد ID ہونا ضروری ہے۔ ایونٹ کے پیرامیٹرز میں ایک منفرد شناخت کنندہ شامل کرنا کافی عام ہے جسے استعمال کیا جا سکتا ہے۔ نوٹ: ٹرانزیکشن ہیش کو ID کے طور پر استعمال کرنے سے یہ فرض ہوتا ہے کہ ایک ہی ٹرانزیکشن میں کوئی اور ایونٹ اس ہیش کے ساتھ ID کے طور پر نہیں بنتا ہے.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### اسٹور سے ہستیوں کو لوڈ کرنا
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### بلاک کے ساتھ تخلیق کردہ ہستیوں کو تلاش کرنا
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-اسٹور API ان ہستیوں کی بازیافت میں سہولت فراہم کرتا ہے جو موجودہ بلاک میں تخلیق یا اپ ڈیٹ کی گئی تھیں۔ اس کے لیے ایک عام صورت حال یہ ہے کہ ایک ہینڈلر کسی آن چین ایونٹ سے ٹرانزیکشن بناتا ہے، اور بعد کا ہینڈلر اس ٹرانزیکشن تک رسائی حاصل کرنا چاہتا ہے اگر یہ موجود ہو۔ ایسی صورت میں جہاں ٹرانزیکشن موجود نہیں ہے، سب گراف کو صرف یہ جاننے کے لیے ڈیٹا بیس میں جانا پڑے گا کہ ہستی موجود نہیں ہے۔ اگر سب گراف مصنف پہلے ہی جانتا ہے کہ ہستی کو اسی بلاک میں بنایا گیا ہو گا، تو loadInBlock کا استعمال اس ڈیٹا بیس راؤنڈ ٹرپ سے گریز کرتا ہے۔ کچھ سب گرافس کے لیے، یہ کھوئی ہوئی تلاشیں انڈیکسنگ کے وقت میں اہم کردار ادا کر سکتی ہیں.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ As long as the `ERC20Contract` on Ethereum has a public read-only function calle
 
 #### واپس آنے والی کالوں کو ہینڈل کرنا
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-نوٹ کریں کہ گیتھ یا انفورا کلائنٹ سے منسلک گراف نوڈ تمام ریورٹس کا پتہ نہیں لگا سکتا، اگر آپ اس پر بھروسہ کرتے ہیں تو ہم پیراٹی کلائنٹ سے منسلک گراف نوڈ استعمال کرنے کی تجویز کرتے ہیں.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### انکوڈنگ/ڈی کوڈنگ ABI
 

From 2d991af335c8a8a01a23b564a9cd870219309c09 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:06 -0500
Subject: [PATCH 0324/1325] New translations transfer-to-the-graph.mdx
 (Turkish)

---
 .../tr/cookbook/transfer-to-the-graph.mdx     | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/tr/cookbook/transfer-to-the-graph.mdx b/website/pages/tr/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..879b63e66039 100644
--- a/website/pages/tr/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/tr/cookbook/transfer-to-the-graph.mdx
@@ -12,16 +12,16 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
 ### Create a Subgraph in Subgraph Studio
 
-- Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
-- Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
+- [Subgraph Studio](https://thegraph.com/studio/)'ya gidin ve cüzdanınızı bağlayın.
+- "Subgraph Oluştur" düğmesine tıklayın. Subgraph'in adını başlık formunda vermeniz önerilir: "Subgraph Adı Ağ Adı".
 
 > Note: After publishing, the subgraph name will be editable but requires on-chain action each time, so name it properly.
 
@@ -31,7 +31,7 @@ You must have [Node.js](https://nodejs.org/) and a package manager of your choic
 
 On your local machine, run the following command:
 
-Using [npm](https://www.npmjs.com/):
+[npm](https://www.npmjs.com/) kullanarak:
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Örnek
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### Ek Kaynaklar
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From ce9a1ff7ffd2315ff5721d654a15b32a52c9a15a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:08 -0500
Subject: [PATCH 0325/1325] New translations advanced.mdx (Turkish)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/tr/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/tr/developing/creating-a-subgraph/advanced.mdx b/website/pages/tr/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..f44cb3bcf88d
--- /dev/null
+++ b/website/pages/tr/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Genel Bakış
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Zaman Serileri ve Toplulaştırmalar
+
+Zaman serileri ve toplulaştırmalar, subgraph'inizin günlük ortalama fiyat, saatlik toplam transferler gibi istatistikleri takip etmesini sağlar.
+
+Bu özellik, iki yeni subgraph varlık türünü tanıtır. Zaman Serisi varlıkları, zaman damgaları ile veri noktalarını kaydeder. Toplulaştırma varlıkları ise saatlik veya günlük bazda Zaman Serisi veri noktaları üzerinde önceden belirlenmiş hesaplamalar yapar ve sonuçları GraphQL üzerinden kolay erişim için saklar.
+
+### Örnek Şema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Zaman Serileri ve Toplulaştırmaları Tanımlama
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Mevcut Toplulaştırma Aralıkları
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Mevcut Toplulaştırma Fonksiyonları
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Örnek Toplulaştırmalar Sorgusu
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Not:
+
+Zaman Serisi ve Toplulaştırmalar özelliklerini kullanmak için, subgraph’inizin spec sürümü ≥1.1.0 olmalıdır. Bu özelliğin, geriye dönük uyumluluğu etkileyebilecek önemli değişikliklerden geçebileceğini unutmayın.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Kritik olmayan hatalar
+
+Halihazırda senkronize edilmiş subgraphlarda indeksleme hataları varsayılan olarak subgraph başarısız olmasına ve senkronizasyonun durmasına neden olur. Hatalara rağmen senkronizasyonun devam etmesi için subgraphlar, hata tetikleyen işleyicinin yapılan değişikliklerini yok sayarak yapılandırılabilir. Bu, subgraph yazarlarının subgraphlarını düzeltmeleri için zaman kazandırırken, sorguların en son blokta sunulmaya devam etmesini sağlar, ancak hata nedeniyle sonuçlar tutarsız olabilir. Bazı hatalar hala her zaman ölümcül olacaktır. Ölümcül olmaması için hatanın belirlenmiş olması gerekmektedir.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Ölümcül olmayan hataların etkinleştirilmesi, subgraph manifestinde aşağıdaki özellik bayrağının ayarlanmasını gerektirir:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave Dosya Veri Kaynakları
+
+Dosya veri kaynakları, indeksleme sırasında zincir dışı verilere sağlam ve genişletilebilir bir şekilde erişmek için yeni bir subgraph fonksiyonudur. Dosya veri kaynakları IPFS'den ve Arweave'den dosya getirmeyi desteklemektedir.
+
+> Bu aynı zamanda zincir dışı verilerinin belirlenebilir indekslenmesi için zemin hazırlar ve keyfi HTTP kaynaklı verilerin tanıtılma potansiyelini de beraberinde getirir.
+
+### Genel Bakış
+
+İşleyici yürütülürken dosyaları “sıra sıra” almak yerine, Dosya Veri Kaynakları, belirli bir dosya kimliği için yeni veri kaynakları olarak kullanılabilecek şablonlar sunar. Bu yeni veri kaynakları dosyaları getirir. Başarısız olurlarsa yeniden denerler ve dosya bulunduğunda bu işe mahsus bir işleyici çalıştırırlar.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Yükseltme rehberi
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Dosyalar bulunduğunda güncellenecek yeni bir varlık türü ekleyin
+
+Dosya veri kaynakları zincir tabanlı varlıklara erişemez veya bunları güncelleyemez, ancak dosya belirli varlıkları güncellemelidir.
+
+Bu, mevcut varlıklardaki alanları ayrı varlıklara bölmeyi gerektirebilir ve bunlar birbirine bağlanabilir.
+
+Özgün birleştirilmiş varlık:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+Yeni, ayrılmış varlık:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+Ana varlık ve sonuç dosya veri kaynak varlığı arasındaki ilişki bire bir ise, en basit kalıp, IPFS CID'yi arama anahtarı olarak kullanarak ana varlığını sonuç dosya varlığına bağlamaktır. Yeni dosya tabanlı varlıklarınızın modellemesiyle ilgili sorun yaşarsanız Discord üzerinden iletişime geçin!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+Bu, ilgi alanı dosyası tespit edildiğinde oluşturulacak veri kaynağıdır.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Dosyaları işlemek için yeni bir işleyici oluşturun
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Örnek işleyici:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Gerektiğinde dosya veri kaynakları oluşturun
+
+Artık zincir tabanlı işleyicilerin yürütülmesi sırasında dosya veri kaynakları oluşturabilirsiniz:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Örnek:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//Bu örnek kod, bir Crypto coven subgraph'ı içindir. Yukarıdaki ipfs hash'ı, tüm kripto NFT'leri için token üst verilerine sahip bir dizindir.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //Bu, tek bir Crypto coven NFT için üst verilere giden bir yol oluşturur. Dizini "/" + dosya adı + ".json" ile birleştirir.
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+Bu, Graph Düğümü'nün yapılandırılmış IPFS veya Arweave uç noktasını sorgulayacak yeni bir veri kaynağı dosyası oluşturacak ve bulunamazsa yeniden deneyecek. Dosya bulunduğunda, dosya veri kaynağı işleyicisi çalıştırılacaktır.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Tebrikler, dosya veri kaynaklarını kullanıyorsunuz!
+
+#### Subgraph'ınızı dağıtma
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Sınırlamalar
+
+Dosya veri kaynağı işleyicileri ve varlıkları yürütüldüklerinde belirleyici olmaları ve zincir tabanlı veri kaynaklarının bozulmasını önlemeleri için, diğer subgraph varlıklarından izole edilir,. Açıkça şunlardır:
+
+- Dosya Veri Kaynakları tarafından oluşturulan varlıklar değiştirilemez ve güncellenemez
+- Dosya Veri Kaynağı işleyicileri, diğer dosya veri kaynaklarından varlıklara erişemez
+- Dosya Veri Kaynaklarıyla ilişkili varlıklara zincir tabanlı işleyicilerden erişilemez
+
+> Bu kısıtlama çoğu kullanım durumu için sorun oluşturmamalıdır, ancak bazı durumlarda karmaşıklıklığa sebep olabilir. Dosya tabanlı verilerinizi bir subgraph'ta modellemekte zorluk yaşarsanız, lütfen Discord üzerinden bizimle iletişime geçin!
+
+Ek olarak, zincir üstü bir veri kaynağı veya başka bir dosya veri kaynağı olsun, bir dosya veri kaynağından veri kaynakları oluşturmak mümkün değildir. Bu kısıtlama gelecekte kaldırılabilir.
+
+#### En iyi uygulamalar
+
+NFT meta verilerini ilgili tokenleri bağlarken, Üst veri varlığına Token varlığından başvurmak için üst verinin IPFS hash değerini kullanın. Üst veri varlığını IPFS hash değerini bir kimlik olarak kullanarak kaydedin.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> Yukarıdaki öneriyi geliştirmeye çalışıyoruz, bu nedenle sorgular yalnızca "en son" sürümü döndürür
+
+#### Bilinen Sorunlar
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Örnekler
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### Referanslar
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Endekslenmiş Argüman Filtreleri / Konu Filtreleri
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Konu filtreleri veya endekslenmiş argüman filtreleri olarak da bilinen bu özellik, subgraph'lerin endekslenmiş argümanlarının değerlerine göre blok zinciri olaylarını hassas bir şekilde filtrelemesine olanak tanır.
+
+- Bu filtreler, blokzincirindeki büyük olay akışından ilgilenilen belirli olayları izole etmeye yardımcı olarak, subgraph'lerin yalnızca alakalı verilere odaklanmasını ve böylece daha verimli çalışmasını sağlar.
+
+- Bu özellik, belirli adresleri ve bunların blokzincirindeki çeşitli akıllı sözleşmelerle olan etkileşimlerini izleyen kişisel subgraph'ler oluşturmak için faydalıdır.
+
+### Konu Filtreleri Nasıl Çalışır
+
+Bir akıllı sözleşme olay yaydığında, endekslenmiş olarak işaretlenen tüm argümanlar bir subgraph'in manifestosunda filtre olarak kullanılabilir. Bu durum, subgraph'in yalnızca ilgili endekslenmiş argümanlara uyan olayları dinleyip diğerlerini görmezden gelmesini sağlar.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Adresler için endekslenmiş parametreleriyle birlikte olay bildirimi
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Token transferini simüle eden fonksiyon
+    function transfer(address to, uint256 value) public {
+        // Transfer olayını from, to ve value ile yayma
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+Bu örnekte:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Subgraph'lerde Yapılandırma
+
+Konu filtreleri, subgraph manifestosunda doğrudan olay işleyici yapılandırması içinde tanımlanır. Yapılandırma örneği:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+Bu bağlamda:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Her konu (topic) bir veya daha fazla değere sahip olabilir ve bir olay yalnızca karşılık geldiği konudaki değerlerden biriyle eşleşiyorsa işlenir.
+
+#### Filtre Mantığı
+
+- Tek Bir Konu İçinde: VEYA koşulu olarak çalışır. Olay, verilen konunun listesindeki herhangi bir değerle eşleşirse işlenecektir.
+- Farklı Konular Arasında: VE koşulu olarak çalışır. Bir olayın ilgili işleyiciyi tetiklemesi için farklı konular arasındaki belirlenmiş tüm koşulları karşılaması gerekir.
+
+#### Örnek 1: Adres A'dan Adres B'ye Doğrudan Transferleri Takip Etme
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+Bu konfigürasyonda:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Örnek 2: İki veya Daha Fazla Adres Arasında Her İki Yönde Gerçekleşen İşlemleri Takip Etme
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+Bu konfigürasyonda:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- Subgraph, birden fazla adres arasında her iki yönde gerçekleşen işlemleri endeksleyerek tüm adresleri içeren etkileşimlerin kapsamlı bir şekilde izlenmesini sağlar.
+
+## Deklare edilmiş eth_call
+
+> Not: Bu, henüz stabil bir Graph Düğümü sürümünde mevcut olmayan deneysel bir özelliktir. Yalnızca Subgraph Studio'da veya sağlayıcılığını kendiniz yaptığınız düğümünüzde kullanabilirsiniz.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+Bu özellik:
+
+- Ethereum blokzincirinden veri getirme performansını önemli ölçüde artırır. Bunu birden fazla çağrı için toplam süreyi azaltarak ve subgraph'in genel verimliliğini optimize ederek yapar.
+- Daha hızlı veri çekmeye olanak tanıyarak, daha hızlı sorgu yanıtları alınmasını ve daha iyi bir kullanıcı deneyimi sağlar.
+- Birden fazla Ethereum çağrısından veri toplaması gereken uygulamalar için bekleme sürelerini azaltarak veri çekme sürecini daha verimli hale getirir.
+
+### Ana Kavramlar
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Paralel Yürütme: Bir çağrıyı başlatmak için diğerinin bitmesini beklemek yerine, birden fazla çağrı aynı anda başlatılabilir.
+- Zaman Verimliliği: Tüm çağrılar için geçen toplam süre, bireysel çağrı sürelerinin toplamından (işlemler ardışık yapıldığında), en uzun çağrının süresine dönüşür (işlemler paralel yapıldığında).
+
+#### Scenario without Declarative `eth_calls`
+
+Bir kullanıcının işlemleri, bakiyesi ve token varlıkları hakkında veri almak için üç Ethereum çağrısı yapması gereken bir subgraph'iniz olduğunu düşünün.
+
+Geleneksel olarak, bu çağrılar ardışık olarak yapılabilir:
+
+1. Çağrı 1 (İşlem geçmişi): 3 saniye sürer
+2. Çağrı 2 (Bakiye): 2 saniye sürer
+3. Çağrı 3 (Token varlıkları): 4 saniye sürer
+
+Toplam geçen süre = 3 + 2 + 4 = 9 saniye
+
+#### Scenario with Declarative `eth_calls`
+
+Bu özellik sayesinde bu çağrıların paralel olarak gerçekleştirileceğini belirtebilirsiniz:
+
+1. Çağrı 1 (İşlem geçmişi): 3 saniye sürer
+2. Çağrı 2 (Bakiye): 2 saniye sürer
+3. Çağrı 3 (Token varlıkları): 4 saniye sürer
+
+Bu çağrılar paralel olarak yürütüldüğünden, toplam süre en uzun süren çağrının süresine eşittir.
+
+Toplam süre = max (3, 2, 4) = 4 saniye
+
+#### Nasıl Çalışır
+
+1. Bildirimsel Tanım: Subgraph manifestosunda, Ethereum çağrılarını paralel olarak çalıştırılabilecek şekilde tanımlarsınız.
+2. Paralel Çalıştırma Motoru: Graph Düğümü'nün yürütme motoru bu bildirimleri tanır ve çağrıları aynı anda çalıştırır.
+3. Sonuçların Birleştirilmesi: Tüm çağrılar tamamlandığında, sonuçlar birleştirilir ve sonraki işlemler için subgraph tarafından kullanılır.
+
+#### Subgraph Manifestosunda Örnek Yapılandırma
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Yukarıdaki örnek için detaylar:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Mevcut Subgraph'ta Graftlama
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Graftlama, temel verileri indekslemek yerine kopyaladığından, subgraph'ı istenen bloğa getirmek sıfırdan indekslemeye nazaran çok daha hızlıdır, ancak ilk veri kopyası çok büyük subgraphlar için yine birkaç saat sürebilir. Graftlanmış subgraph başlatılırken, Graph Düğümü halihazırda kopyalanmış olan varlık türleri hakkında bilgileri kaydedecektir.
+
+Graftlanan subgraph, temel subgraphla tamamen aynı olmayan, ancak onunla uyumlu olan bir GraphQL şeması kullanabilir. Kendi başına geçerli bir subgraph şeması olmalıdır, ancak şu şekillerde temel subgraph şemasından sapabilir:
+
+- Varlık türlerini ekler veya kaldırır
+- Varlık türlerinden öznitelikleri kaldırır
+- Varlık türlerine null yapılabilir öznitelikler ekler
+- Null yapılamayan öznitelikleri null yapılabilir özniteliklere dönüştürür
+- Numaralandırmalara değerler ekler
+- Arayüzleri ekler veya kaldırır
+- Arayüzün hangi varlık türleri için uygulandığını değiştirir
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 3746c9241d4f5c38ca87be7bd24e5502d657e431 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:09 -0500
Subject: [PATCH 0326/1325] New translations assemblyscript-mappings.mdx
 (Turkish)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/tr/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/tr/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/tr/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..d3182334749c
--- /dev/null
+++ b/website/pages/tr/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Genel Bakış
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Eşleştirmeleri Yazma
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Yeni Varlıklar Oluşturmak için Önerilen Kimlikler(IDs)
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Aynı ID'ye sahip varlıkların işlenmesi
+
+Yeni bir varlık oluşturup kaydederken, aynı ID'ye sahip bir varlık zaten mevcutsa, birleştirme sürecinde her zaman yeni varlığın özellikleri tercih edilir. Bu, mevcut varlığın yeni varlıktan gelen değerlerle güncelleneceği anlamına gelir.
+
+Eğer aynı ID'ye sahip yeni bir varlıkta bir alana kasıtlı olarak null değeri atanmışsa, mevcut varlıkta bu alan null değeriyle güncellenir.
+
+Eğer aynı ID'ye sahip yeni bir varlıkta bir alan için değer atanmamışsa, o alan da null olacaktır.
+
+## Kod Oluşturma
+
+Akıllı sözleşmeler, olaylar ve varlıklarla çalışmayı kolay ve tip güvenli hale getirmek amacıyla Graph CLI, subgraph'ın GraphQL şemasından ve veri kaynaklarında bulunan sözleşme ABI'lerinden AssemblyScript türleri oluşturabilir.
+
+Bununla yapılır
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // Kontrat sınıfı:
+  Gravity,
+  // Olayların sınıfları:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From c7ba16d5c15fd163ae9ff12442c662f8e36c0d02 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:10 -0500
Subject: [PATCH 0327/1325] New translations install-the-cli.mdx (Turkish)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..1fc26595c11d
--- /dev/null
+++ b/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Graph CLI'ı Yükleyin
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Genel Bakış
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Buradan Başlayın
+
+### Graph CLI'ı Yükleyin
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+Yerel makinenizde aşağıdaki komutlardan birini çalıştırın:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Subgraph Oluştur
+
+### Mevcut Bir Sözleşmeden
+
+Aşağıdaki komut, mevcut bir sözleşmenin tüm olaylarını endeksleyen bir subgraph oluşturur:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- Bu komut, sözleşme ABI'sini Etherscan’den almaya çalışır.
+
+  - Graph CLI, bir umumi RPC uç noktasına bağlıdır. Ara sıra başarısızlık beklenebilir, ancak genellikle yeniden denemeler sorunu çözer. Sorunlar devam ederse, yerel bir ABI kullanmayı düşünün.
+
+- İsteğe bağlı argümanlar eksikse, komut sizi bir etkileşimli forma yönlendirir.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### Örnek Bir Subgraph'ten
+
+Aşağıdaki komut, örnek bir subgraph'ten yeni bir proje ilklendirir:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Ayrıntılar
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### ABI’lerin Elde Edilmesi
+
+ABI dosya(lar)ı sözleşme(ler) inizle uygun olmalıdır. ABI dosyalarını edinmek için birkaç yol vardır:
+
+- Kendi projenizi oluşturuyorsanız, muhtemelen en güncel ABI'lerinize erişiminiz olacaktır.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Sürümleri
+
+| Sürüm | Sürüm Notları                                                                                                                                                            |
+| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+| 0.0.5 | İşleyicilerin işlem makbuzlarına erişim desteği eklendi.                                                                                                                 |
+| 0.0.4 | Subgraph özelliklerini yönetme desteği eklendi.                                                                                                                          |

From cc183159a02fa9558b8ca1faa8254015b33150d7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:11 -0500
Subject: [PATCH 0328/1325] New translations ql-schema.mdx (Turkish)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..aa158eda5efa
--- /dev/null
+++ b/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Genel Bakış
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Varlıkları Tanımlama
+
+Varlıkları tanımlamadan önce, verilerinizin nasıl yapılandırıldığını ve nasıl bağlantılı olduğunu düşünmek önemlidir.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- Varlıkları, olaylar veya fonksiyonlar yerine “veri içeren nesneler” olarak düşünmek faydalı olabilir.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- Varsayılan olarak, varlıklar değiştirilebilirdir; yani, eşlemeler halihazırda mevcut varlıkları yükleyebilir, onları modifiye edebilir ve o varlığın yeni bir sürümünü saklayabilir.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - Varlığın oluşturulduğu blok içinde değişiklikler gerçekleşirse, eşlemeler değişmez varlıkları değiştirebilir. Değişmez varlıklar çok daha hızlı yazılabilir ve sorgulanabilir olduğundan, mümkün olduğunca kullanılmaları önerilir.
+
+#### İyi Bir Örnek
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Kötü Bir Örnek
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Opsiyonel ve Zorunlu Alanlar
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Gömülü Skaler(Scalar) Türler
+
+#### GraphQL'in Desteklediği Skalerler
+
+GraphQL API'sinde desteklenen skalarlardan bazıları şunlardır:
+
+| Tür          | Tanım                                                                                                                                                                                                            |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte dizisi, onaltılık bir dizgi olarak temsil edilir. Ethereum hash değerleri ve adresleri için yaygın olarak kullanılır.                                                                                       |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Numaralandırmalar
+
+Ayrıca bir şema içinde numaralandırmalar da oluşturabilirsiniz. Numaralandırmalar aşağıdaki sözdizimine sahiptir:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Varlık İlişkileri
+
+Bir varlık, şemanızdaki bir veya daha fazla başka varlıkla ilişkili olabilir. Bu ilişkiler, sorgularınızda çaprazlanabilir. Graph'taki ilişkiler tek yönlüdür. İki yönlü ilişkileri simüle etmek, ilişkinin herhangi biri "son" üzerinde tek yönlü bir ilişki tanımlayarak mümkündür.
+
+İlişkiler, belirtilen türün başka bir varlığın türü olması dışında, diğer tüm alanlarda olduğu gibi varlıklar üzerinde tanımlanır.
+
+#### Bire Bir İlişkiler
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Birden Çoğa İlişkiler
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Tersine Aramalar
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+Birden çoğa ilişkileriiçin, ilişki her zaman 'birden' tarafında depolanmalı ve her zaman 'çoğa' tarafında türetilmelidir. İlişkinin 'çoğa' tarafında bir dizi varlık depolamak yerine bu şekilde saklanması, subgraph indeksleme ve sorgulaması adına önemli ölçüde daha iyi performans sağlayacaktır. Genel olarak, varlık dizilerini depolamaktan mümkün olduğunca sakınılması gerekmektedir.
+
+#### Örnek
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Çoktan Çoğa İlişkiler
+
+Kullanıcıların her birinin birden çok kuruluşa mensup olabileceği gibi çoktan çoğa ilişkilerde, ilişkiyi modellemenin en basit fakat pek verimli olmayan yolu, ilişkide yer alan iki varlıkta da bir dizi olarak saklamaktır. İlişki simetrik ise, ilişkinin yalnızca bir tarafının saklanması gerekir ve diğer taraf türetilebilir.
+
+#### Örnek
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+Bu yaklaşım, örneğin kullanıcılar için kuruluşları almak için sorguların ek bir seviyeye inmesini gerektirir:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Çoktan çoğa ilişkileri depolamanın daha ayrıntılı bu yolu, subgraph için depolanan veri miktarının azalmasına ve bu sonucunda genellikle indekslenmesi ve sorgulanması önemli ölçüde daha hızlı olan bir subgraph sağlayacaktır.
+
+### Şemaya notlar/yorumlar ekleme
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # # varlığın benzersiz tanımlayıcısı ve birincil anahtarı
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Tam Metinde Arama Alanlarını Tanımlama
+
+Tam metinde arama sorguları, metin arama girdisine dayanarak varlıkları filtreler ve sıralar. Tam metin sorguları, sorgu metni girişini indekslenmiş metin verileriyle karşılaştırmadan önce köklere işleyerek benzer kelimeler için eşleşmeler döndürebilir.
+
+Tam metin sorgusu tanımı, sorgu adı, metin alanlarını işlemek için kullanılan dil sözlüğü, sonuçları sıralamak için kullanılan sıralama algoritması ve aramaya dahil edilen alanları içerir. Her tam metin sorgusu birden fazla alana yayılabilir, ancak dahil edilen tüm alanlar tek bir varlık türünden olmalıdır.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Desteklenen diller
+
+Farklı bir dil seçmek, tam metin arama API'sı üzerinde bazen az olsa da kesin bir etkiye sahip olacaktır. Tam metin sorgu alanı tarafından kapsanan alanlar, seçilen dile bağlı olarak incelenir, bu nedenle analiz ve arama sorguları tarafından üretilen sözlükbirimleri dilden dile değişir. Örneğin: desteklenen Türkçe sözlük kullanıldığında "token" kelimesi "toke" olarak kök alınırken, elbette İngilizce sözlük "token" olarak kök alacaktır.
+
+Desteklenen dil sözlükleri:
+
+| Code   | Sözlük     |
+| ------ | ---------- |
+| yalın  | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portekizce |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Algoritmaları Sıralama
+
+Sonuçları sıralamak için desteklenen algoritmalar:
+
+| Algorithm     | Description                                                                         |
+| ------------- | ----------------------------------------------------------------------------------- |
+| rank          | Sonuçları sıralamak için tam metin sorgusunun eşleştirme kalitesini (0-1) kullanın. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                     |

From 39dfe107e1a1d432feface6a18014b48e601d7d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:12 -0500
Subject: [PATCH 0329/1325] New translations subgraph-manifest.mdx (Turkish)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/tr/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/tr/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/tr/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..702a2183dc23
--- /dev/null
+++ b/website/pages/tr/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Genel Bakış
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+Tek bir subgraph:
+
+- Birden fazla akıllı sözleşmeden veri endeksleyebilir (fakat birden fazla ağdan endeksleyemez).
+
+- IPFS dosyalarından Dosya Veri Kaynakları kullanarak veri endeksleyebilir.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Manifest için güncellenmesi gereken önemli girdiler şunlardır:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Olay İşleyicileri
+
+Bir subgraph'in olay işleyicileri, blokzincir üzerindeki akıllı sözleşmeler tarafından yayılan belirli olaylara tepki verir, ve subgraph'in manifesto dosyasında tanımlanan işleyicileri tetikler. Bu, subgraph'lerin tanımlanmış mantığa göre olay verilerini işlemesini ve depolamasını sağlar.
+
+### Olay İşleyici Tanımlama
+
+Bir olay işleyici, subgraph'in YAML yapılandırmasında bir veri kaynağı içinde tanımlanır. Hangi olayların dinleneceğini ve bu olaylar algılandığında hangi fonksiyonun çalıştırılacağını belirtir.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Opsiyonel konu filtresi, sadece verilen konuyu içeren olayları filtreler.
+```
+
+## Çağrı İşleyicileri
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Çağrı işleyicileri yalnızca iki durumdan birinde tetiklenir: belirtilen işlevin sözleşme tarafından değil, başka bir hesap tarafından çağrılması durumunda veya Solidity'de harici olarak işaretlenip aynı sözleşmenin başka bir işlevinin bir parçası olarak çağrılması durumunda yalnızca tetiklenir.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Bir Çağrı İşleyici Tanımlama
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Eşleştirme fonksiyonu
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Blok İşleyicileri
+
+Bir subgraph, sözleşme olaylarına veya işlev çağrılarına abone olmanın yanı sıra, zincire yeni bloklar eklendikçe verilerini güncellemek isteyebilir. Bu işlemi gerçekleştirmek için a subgraph, her blok sonrasında veya önceden tanımlanmış bir filtreye uygun bloklardan sonra bir işlev çalıştırabilir.
+
+### Desteklenen Filtreler
+
+#### Çağrı Filtresi
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+Bir blok işleyicisi için filtre olmaması, işleyicinin her blok için çağrılacağı anlamına gelir. Bir veri kaynağı, her filtre türü için yalnızca bir blok işleyicisi içerebilir.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filtresi
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filtresi
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+Once filtresi ile tanımlanan işleyici, diğer tüm işleyiciler çalışmadan önce yalnızca bir kez çağrılacaktır. Bu yapılandırma, subgraph'ın işleyiciyi indekslemenin başlangıcında belirli görevleri yerine getirmesine olanak sağlayan bir başlatma işleyicisi olarak kullanmasına yarar.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Eşleştirme fonksiyonu
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonim Olaylar
+
+Solidity'de anonim olayları işlemek gerekiyorsa, örnekte olduğu gibi, olayın topic 0'ını sağlayarak bunu başarabilirsiniz:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Olay İşleyicilerinde İşlem Makbuzları
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## İşleyicilerin Tetiklenme Sırası
+
+Bir bloktaki veri kaynağı için tetikleyiciler şu işlemlerle sıralanır:
+
+1. Olay ve çağrı tetikleyicileri, öncelikle bloktaki işlem indeksine göre sıralanır.
+2. Aynı işlemdeki olay ve çağrı tetikleyicileri, bir kurala göre sıralanır: önce olay tetikleyicileri, ardından çağrı tetikleyicileri olmak üzere her tür manifest'te tanımlandıkları sıraya göre sıralanır.
+3. Blok tetikleyicileri, olay ve çağrı tetikleyicilerinden sonra manifest'te tanımlandıkları sırada göre çalıştırılır.
+
+Bu sıralama kuralları değişebilir.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Veri Kaynağı Şablonları
+
+EVM uyumlu akıllı sözleşmelerde yaygın bir model, kayıt (registry) veya fabrika (factory) sözleşmelerinin kullanılmasıdır. Böylece ana sözleşme, kendi durumuna ve olaylarına sahip istenilen sayıda diğer sözleşmeyi oluşturur, yönetir veya bunlara referans verir.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Ana Sözleşme için Veri Kaynağı
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Dinamik Olarak Oluşturulan Sözleşmeler için Veri Kaynağı Şablonları
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Bir Veri Kaynağı Şablonunun Örneklenmesi
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Borsayı indekslemeye başlayın; "event.params.exchange"
+  // yeni borsa sözleşmesinin adresi
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Eğer önceki bloklar, yeni veri kaynağı için ilgili veri içeriyorsa, o veriyi indekslemek için sözleşmenin mevcut durumunu okuyarak ve yeni veri kaynağı oluşturulurken o zaman dilimindeki durumu temsil eden varlıklar oluşturarak yapmak en iyisidir.
+
+### Veri Kaynağı Bağlamı
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Başlangıç Blokları
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Arama çubuğuna adresini girerek sözleşmeyi arayın.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. İşlem detayları sayfasını yükleyin ve bu sözleşme için başlangıç bloğunu bulacaksınız.
+
+## Endeksleyici İpuçları
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Budama
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. Belirli bir sayı: Verilen sayıyı saklanacak tarihsel blok sayısı olarak ayarlar.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> Subgraph'lerde "geçmiş" terimi, bu bağlamda, değiştirilebilir varlıkların eski durumlarına dair verilerin saklanmasıyla ilgilidir.
+
+Verilen bir bloktaki geçmiş, şu durumlar için gereklidir:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Subgraph'i verilen bloka geri sarmak
+
+Eğer verilen bloktaki tarihsel veri budanmışsa yukarıdaki özellikler kullanılamayacaktır.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+Belirli bir miktarda tarihsel veri saklamak için:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+Varlık durumlarının tam geçmişini korumak için:
+
+```
+indexerHints:
+  prune: never
+```

From 3ed73bdbd8858889edf4ca7566337b780624dae9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:13 -0500
Subject: [PATCH 0330/1325] New translations subgraphs.mdx (Ukrainian)

---
 website/pages/uk/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/uk/subgraphs.mdx b/website/pages/uk/subgraphs.mdx
index 27b452211477..1e93ac7c30b8 100644
--- a/website/pages/uk/subgraphs.mdx
+++ b/website/pages/uk/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: Підграфи
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 1df855725b40281c60ff2e34411e3ec56d100209 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:14 -0500
Subject: [PATCH 0331/1325] New translations transfer-to-the-graph.mdx
 (Ukrainian)

---
 website/pages/uk/cookbook/transfer-to-the-graph.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/uk/cookbook/transfer-to-the-graph.mdx b/website/pages/uk/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..6a5d2c2793f3 100644
--- a/website/pages/uk/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/uk/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 

From 4e40fbdaa3785e1b24e348db74c4afb68051775c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:15 -0500
Subject: [PATCH 0332/1325] New translations advanced.mdx (Ukrainian)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/uk/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/uk/developing/creating-a-subgraph/advanced.mdx b/website/pages/uk/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..3a08ddab7066
--- /dev/null
+++ b/website/pages/uk/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 4fab720191343d9fa8a4aebc1e0c64a1343204d4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:19 -0500
Subject: [PATCH 0333/1325] New translations assemblyscript-mappings.mdx
 (Ukrainian)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/uk/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/uk/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/uk/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/uk/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 2e296592ab8edbf82754ba63da3fdbddbee64592 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:20 -0500
Subject: [PATCH 0334/1325] New translations install-the-cli.mdx (Ukrainian)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..46d489f24d76
--- /dev/null
+++ b/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+На вашому локальному комп'ютері запустіть одну з наведених нижче команд:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Створення субграфа
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 496f6365dbb570397f9ca0bbe6f532062fb11b0b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:21 -0500
Subject: [PATCH 0335/1325] New translations ql-schema.mdx (Ukrainian)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From f652e0a14e22233df6dbdde3912f6872884e860e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:23 -0500
Subject: [PATCH 0336/1325] New translations subgraph-manifest.mdx (Ukrainian)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/uk/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/uk/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/uk/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..f282f3946e75
--- /dev/null
+++ b/website/pages/uk/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 7a62dd3213398191514b4f211d6e5b641cd4fd15 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:24 -0500
Subject: [PATCH 0337/1325] New translations subgraphs.mdx (Chinese Simplified)

---
 website/pages/zh/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/zh/subgraphs.mdx b/website/pages/zh/subgraphs.mdx
index 27b452211477..bf8d590fe7e9 100644
--- a/website/pages/zh/subgraphs.mdx
+++ b/website/pages/zh/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: 子图
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 子图生命周期
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 80d63cc1db37ced9b988adf80c16b1c3c668cefe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:25 -0500
Subject: [PATCH 0338/1325] New translations transfer-to-the-graph.mdx (Chinese
 Simplified)

---
 .../pages/zh/cookbook/transfer-to-the-graph.mdx    | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/zh/cookbook/transfer-to-the-graph.mdx b/website/pages/zh/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..5186b6088071 100644
--- a/website/pages/zh/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/zh/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### 示例
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### 其他资源
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 40a481ab2541238581fe385157ecb4187eecdb76 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:27 -0500
Subject: [PATCH 0339/1325] New translations advanced.mdx (Chinese Simplified)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/zh/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/zh/developing/creating-a-subgraph/advanced.mdx b/website/pages/zh/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..d8abf7fb58cc
--- /dev/null
+++ b/website/pages/zh/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## 概述
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## 非致命错误
+
+在默认情况下，已同步子图上的索引错误会导致子图失败并停止同步。 子图也可以配置为忽略引发错误的处理程序所做的更改, 在出现错误时继续同步。 这使子图作者有时间更正他们的子图，同时继续针对最新区块提供查询，尽管由于导致错误的代码问题，结果可能会不一致。 请注意，某些错误仍然总是致命的，要成为非致命错误，首先需要确定相应的错误是确定性的错误。
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+启用非致命错误需要在子图清单上设置以下功能标志：
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+文件数据源是一种新的子图功能，用于以稳健、可扩展的方式在索引期间访问链下数据。文件数据源支持从IPFS和Arweave获取文件。
+
+> 这也为链外数据的确定性索引以及引入任意HTTP源数据奠定了基础。
+
+### 概述
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### 升级指南
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### 添加新的实体类型，当找到文件时将更新该类型
+
+文件数据源不能访问或更新基于链的实体，但必须更新特定于文件的实体。
+
+这可能意味着将现有实体中的字段拆分为单独的实体，并链接在一起。
+
+原始合并实体：
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+新拆分实体：
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+如果母实体与生成的文件数据源实体之间的关系为1:1，则最简单的模式是通过使用IPFS CID作为查找将母实体链接到生成的文件实体。如果您在建模新的基于文件的实体时遇到困难，请联系Discord！
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+这是在识别出感兴趣的文件时生成的数据源。
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### 创建新处理程序以处理文件
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+示例处理程序：
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### 需要时生成文件数据源
+
+现在，您可以在执行基于链的处理程序期间创建文件数据源：
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+例子:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = "QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm"
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+这将创建一个新的文件数据源，该数据源将轮询Graph Node配置的IPFS或Arweave端点，如果未找到文件，则进行重试。当找到文件时，文件数据源处理程序将被执行。
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+祝贺您，您正在使用文件数据源！
+
+#### 将你的子图部署
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### 限制
+
+文件数据源处理程序和实体与其他子图实体隔离，确保它们在执行时是确定的，并确保基于链的数据源不受污染。具体来说:
+
+- 文件数据源创建的实体是不可变的，不能更新
+- 文件数据源处理程序无法访问其他文件数据源中的实体
+- 基于链的处理程序无法访问与文件数据源关联的实体
+
+> 虽然这个约束对于大多数用例不应该是有问题的，但是对于某些用例，它可能会引入复杂性。如果您在子图中基于文件数据建模时遇到问题，请通过 Discord 与我们联系！
+
+此外，不可能从文件数据源创建数据源，无论是线上数据源还是其他文件数据源。这项限制将来可能会取消。
+
+#### 最佳实践
+
+如果要将 NFT 元数据链接到相应的代币，请使用元数据的 IPFS hash从代币实体引用元数据实体。使用 IPFS hash作为 ID 保存元数据实体。
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> 我们正在努力改进上述建议，因此查询只返回“最新”版本。
+
+#### 已知问题
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### 例子
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### 参考
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### 嫁接到现有子图
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+因为嫁接是拷贝而不是索引基础数据，所以子图同步到所需区块比从头开始索引要快得多，尽管对于非常大的子图，初始数据拷贝仍可能需要几个小时。 在初始化嫁接子图时，Graph 节点将记录有关已复制的实体类型的信息。
+
+嫁接子图可以使用一个GraphQL模式，该模式与某个基本子图不同，但仅与基本子图兼容。它本身必须是一个有效的子图模式，但是可以通过以下方式偏离基本子图的模式：
+
+- 它添加或删除实体类型
+- 它从实体类型中删除属性
+- 它将可为空的属性添加到实体类型
+- 它将不可为空的属性转换为可空的属性
+- 它将值添加到枚举类型中
+- 它添加或删除接口
+- 它改变了实现接口的实体类型
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 59343abf393919b39fd4d09784fed192980fd012 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:27 -0500
Subject: [PATCH 0340/1325] New translations assemblyscript-mappings.mdx
 (Chinese Simplified)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/zh/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/zh/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/zh/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..88028e162e55
--- /dev/null
+++ b/website/pages/zh/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## 概述
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## 编写映射
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### 用于创建新实体的推荐 ID
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## 代码生成
+
+为了使与智能合约、事件和实体的代码编写工作变得简单且类型安全，Graph CLI 可以从子图的 GraphQL 模式和数据源中包含的合约 ABI 生成 AssemblyScript 类型。
+
+这可以通过以下命令实现
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 67805c22b1a3978d7ea127438616062af746d163 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:29 -0500
Subject: [PATCH 0341/1325] New translations install-the-cli.mdx (Chinese
 Simplified)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..50df657982d7
--- /dev/null
+++ b/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: 安装 Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## 概述
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## 开始
+
+### 安装 Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+在本地计算机上，运行以下命令之一：
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## 创建子图
+
+### 基于现有合约
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### 基于子图示例
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+ABI 文件必须与您的合约相匹配。 获取 ABI 文件的方法有以下几种：
+
+- 如果您正在构建自己的项目，您可以获取最新的 ABI。
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+|   版本  | Release 说明                                                                                                                                                               |
+| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
+| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |

From 52788cc05e32b1885e6678ec83438f4b9f403b87 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:30 -0500
Subject: [PATCH 0342/1325] New translations ql-schema.mdx (Chinese Simplified)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..d9ca63c76b45
--- /dev/null
+++ b/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## 概述
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### 好代码的例子
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity {
+  id: Id!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### 坏榜样
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### 可选和必选字段
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### 内置标量类型
+
+#### GraphQL 支持的标量
+
+The following scalars are supported in the GraphQL API:
+
+| 类型           | 描述                                                                                                                                                                                                               |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | 字节数组，表示为十六进制字符串。 通常用于以太坊hash和地址。                                                                                                                                                                                 |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### 枚举类型
+
+您还可以在模式中创建枚举类型。 枚举类型具有以下语法：
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### 实体关系
+
+一个实体可能与模式中的一个或多个其他实体发生联系。 您可以在您的查询中遍历这些联系。 Graph 中的联系是单向的。 可以通过在关系的任一“端”上定义单向关系来模拟双向关系。
+
+关系是在实体上定义的，就像任何其他字段一样，除了指定的类型是另一个实体类型。
+
+#### 一对一关系
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### 一对多关系
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### 反向查找
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+对于一对多关系，关系应始终存储在“一”端，而“多”端应始终派生。 以这种方式存储关系，而不是在“多”端存储实体数组，将大大提高索引和查询子图的性能。 通常，应尽可能避免存储实体数组。
+
+#### 示例
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### 多对多关系
+
+对于多对多关系，例如每个可能属于任意数量的组织的用户，对关系建模的最直接，但通常不是最高效的方法，是在所涉及的两个实体中的每一个中定义数组。 如果关系是对称的，则只需要存储关系的一侧联系，就可以导出另一侧。
+
+#### 示例
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+这种方法要求查询下降一个额外的级别来检索，例如，用户的组织：
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+这种存储多对多关系的更精细的方式将导致为子图存储的数据更少，因此子图的索引和查询速度通常会大大加快。
+
+### 向模式添加注释
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## 定义全文搜索字段
+
+全文搜索查询根据文本搜索输入来过滤和排列实体。 通过在与索引文本数据进行比较之前，将查询文本输入处理到词干中，全文查询能够返回相似词的匹配项。
+
+全文查询定义包括查询名称、用于处理文本字段的语言词典、用于对结果进行排序的排序算法，以及搜索中包含的字段。 每个全文查询可能跨越多个字段，但所有包含的字段必须来自单个实体类型。
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## 支持的语言
+
+选择不同的语言将对全文搜索 API 产生明确的（尽管有时是微妙的）影响。 全文查询字段涵盖的字段将会在所选语言的内容中进行检查，因此分析和搜索查询产生的词位因语言而异。 例如：当使用支持的土耳其语词典时，“token”的词干为“toke”，而英语词典当然会认为其词干为“token”。
+
+支持的语言词典：
+
+| Code   | 词典         |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | 葡萄牙语       |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### 排序算法
+
+支持的排序结果算法：
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | 使用全文查询的匹配质量 (0-1) 对结果进行排序。                                              |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From cd2a4cedc64a45c5c38a99020af331fb1c60a0df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:31 -0500
Subject: [PATCH 0343/1325] New translations subgraph-manifest.mdx (Chinese
 Simplified)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/zh/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/zh/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/zh/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..58f782bc4bb7
--- /dev/null
+++ b/website/pages/zh/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## 概述
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+清单中要更新的重要条目是：
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## 调用处理程序
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+调用处理程序只会在以下两种情况之一触发：当指定的函数被合约本身以外的账户调用时，或者当它在 Solidity 中被标记为外部，并作为同一合约中另一个函数的一部分被调用时。
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### 定义调用处理程序
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### 映射函数
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## 区块处理程序
+
+除了订阅合约事件或函数调用之外，子图可能还希望在将新区块附加到链上时更新其数据。 为了实现这一点，子图可以在每个区块之后，或匹配预定义过滤器的区块之后，运行一个函数。
+
+### 支持的过滤器
+
+#### 调用筛选器
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+块处理程序没有过滤器将确保每个块都调用处理程序。对于每种过滤器类型，一个数据源只能包含一个块处理程序。
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### 投票筛选器
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### 一次性筛选器
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+带有 "once filter" 的所定义处理程序将在所有其他处理程序运行之前仅被调用一次。这种配置允许子图将该处理程序用作初始化处理程序，在索引开始时执行特定任务。
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### 映射函数
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## 匿名事件
+
+如果您需要在 Solidity 中处理匿名事件，可以通过提供事件的主题 0 来实现，如示例所示：
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## 事件处理程序中的交易接收
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+区块内数据源的触发器使用以下流程进行排序：
+
+1. 事件和调用触发器首先按区块内的交易索引排序。
+2. 同一交易中的事件和调用触发器使用约定进行排序：首先是事件触发器，然后是调用触发器，每种类型都遵循它们在清单中定义的顺序。
+3. 区块触发器按照它们在清单中定义的顺序，在事件和调用触发器之后运行。
+
+这些排序规则可能会发生变化。
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## 数据源模板
+
+EVM兼容智能合约中的一种常见模式是使用注册表或工厂合约，其中一个合约创建、管理或引用任意数量的其他合约，每个合约都有自己的状态和事件。
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### 主合约的数据源
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### 动态创建合约的数据源模板
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### 实例化数据源模板
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> 如果先前的区块包含与新数据源相关的数据，最好通过读取合约的当前状态，并在创建新数据源时创建表示该状态的实体来索引该数据。
+
+### 数据源背景
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## 起始区块
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. 通过在搜索栏中输入合约地址来搜索合约。
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. 加载交易详情页面，您将在其中找到该合约的起始区块。
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From aafb639870a5a5ad123aae8423f1f013296f0f73 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:32 -0500
Subject: [PATCH 0344/1325] New translations subgraphs.mdx (Urdu (Pakistan))

---
 website/pages/ur/subgraphs.mdx | 55 ++++++++++++++++++++++++++++++----
 1 file changed, 50 insertions(+), 5 deletions(-)

diff --git a/website/pages/ur/subgraphs.mdx b/website/pages/ur/subgraphs.mdx
index 27b452211477..5886281f8274 100644
--- a/website/pages/ur/subgraphs.mdx
+++ b/website/pages/ur/subgraphs.mdx
@@ -1,5 +1,5 @@
 ---
-title: Subgraphs
+title: سب گراف
 ---
 
 ## What is a Subgraph?
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## سب گراف لائف سائیکل
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 33a1e73d19a86a1025ad812b26734c8380dfc544 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:33 -0500
Subject: [PATCH 0345/1325] New translations transfer-to-the-graph.mdx (Urdu
 (Pakistan))

---
 .../pages/ur/cookbook/transfer-to-the-graph.mdx  | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/ur/cookbook/transfer-to-the-graph.mdx b/website/pages/ur/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..b5effc7221d4 100644
--- a/website/pages/ur/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/ur/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -31,7 +31,7 @@ You must have [Node.js](https://nodejs.org/) and a package manager of your choic
 
 On your local machine, run the following command:
 
-Using [npm](https://www.npmjs.com/):
+[npm](https://www.npmjs.com/) کا استعمال:
 
 ```sh
 npm install -g @graphprotocol/graph-cli@latest
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### مثال
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 
@@ -98,7 +98,7 @@ You can create API Keys in Subgraph Studio under the “API Keys” menu at the
 
 Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
 
-### Additional Resources
+### اضافی وسائل
 
 - To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
 - To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From 685791f3ae190cf019bc3318f142f0b185ad6ebc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:34 -0500
Subject: [PATCH 0346/1325] New translations advanced.mdx (Urdu (Pakistan))

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/ur/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/ur/developing/creating-a-subgraph/advanced.mdx b/website/pages/ur/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..f25870d6bdf7
--- /dev/null
+++ b/website/pages/ur/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## جائزہ
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+پہلے سے مطابقت پذیر سب گرافس پر انڈیکسنگ کی غلطیاں، بذریعہ ڈیفالٹ، سب گراف کے ناکام ہونے اور مطابقت پذیری کو روکنے کا سبب بنیں گی. سب گراف کو متبادل طور پر غلطیوں کی موجودگی میں مطابقت پذیری جاری رکھنے کے لیے ترتیب دیا جا سکتا ہے، ہینڈلر کی طرف سے کی گئی تبدیلیوں کو نظر انداز کر کے جس سے خرابی پیدا ہوئی. اس سے سب گراف مصنفین کو اپنے سب گراف کو درست کرنے کا وقت ملتا ہے جب کہ تازہ ترین بلاک کے خلاف کیوریز پیش کی جاتی رہتی ہیں، حالانکہ اس خرابی کی وجہ سے نتائج متضاد ہو سکتے ہیں. نوٹ کریں کہ کچھ غلطیاں اب بھی ہمیشہ مہلک ہوتی ہیں. غیر مہلک ہونے کے لیے، خرابی کو تعییناتی معلوم ہونا چاہیے.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+غیر مہلک غلطیوں کو فعال کرنے کے لیے سب گراف مینی فیسٹ پر درج ذیل خصوصیت کا فلیگ ترتیب دینے کی ضرورت ہے:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+فائل ڈیٹا کے ذرائع ایک مضبوط، قابل توسیع طریقے سے انڈیکسنگ کے دوران آف چین ڈیٹا تک رسائی کے لیے ایک نئی سب گراف کی فعالیت ہے۔ فائل ڈیٹا کے ذرائع IPFS اور Arweave سے فائلیں لانے میں معاونت کرتے ہیں.
+
+> یہ آف چین ڈیٹا کی تعییناتی انڈیکسنگ کے ساتھ ساتھ صوابدیدی HTTP سے حاصل کردہ ڈیٹا کے ممکنہ تعارف کی بنیاد بھی رکھتا ہے.
+
+### جائزہ
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### اپ گریڈ گائیڈ
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### ایک نئے ادارے کی قسم شامل کریں جو فائلیں ملنے پر اپ ڈیٹ ہو جائے گی
+
+فائل ڈیٹا سورسز چین پر مبنی اداروں تک رسائی یا اپ ڈیٹ نہیں کر سکتے ہیں، لیکن فائل کے مخصوص اداروں کو اپ ڈیٹ کرنا ضروری ہے.
+
+اس کا مطلب یہ ہوسکتا ہے کہ موجودہ اداروں سے فیلڈز کو الگ الگ اداروں میں تقسیم کیا جائے، جو آپس میں جڑے ہوئے ہوں.
+
+اصل مشترکہ ادارہ:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+نیا، تقسیم شدہ ادارہ:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+اگر رشتہ پیرنٹ ادارے اور نتیجے میں آنے والی فائل ڈیٹا سورس ہستی کے درمیان 1:1 ہے، تو سادہ ترین نمونہ IPFS CID کو بطور لوک اپ استعمال کر کے پیرنٹ کی ہستی کو نتیجے میں آنے والی فائل ہستی سے جوڑنا ہے۔ اگر آپ کو اپنی نئی فائل پر مبنی ہستیوں کو ماڈل بنانے میں دشواری ہو رہی ہے تو ڈسکورڈ پر رابطہ کریں!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+یہ ڈیٹا سورس ہے جو دلچسپی کی فائل کی شناخت ہونے پر پیدا کیا جائے گا.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### فائلوں پر کارروائی کرنے کے لیے ایک نیا ہینڈلر بنائیں
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+مثالی ہینڈلر:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### ضرورت پڑنے پر فائل ڈیٹا سورسز کو دریافت کریں
+
+اب آپ چین پر مبنی ہینڈلرز کے عمل کے دوران فائل ڈیٹا کے ذرائع بنا سکتے ہیں:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+مثال:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+یہ ایک نیا فائل ڈیٹا سورس بنائے گا، جو گراف نوڈ کے کنفیگر کردہ آئی پی ایف ایس یا Arweave اینڈ پوائنٹ کو پول کرے گا، اگر یہ نہ ملا تو دوبارہ کوشش کریں۔ جب فائل مل جائے گی، فائل ڈیٹا سورس ہینڈلر کو عمل میں لایا جائے گا.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+مبارک ہو، آپ فائل ڈیٹا سورسز استعمال کر رہے ہیں!
+
+#### آپ کے سب گراف کو تعینات کرنا
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### حدود
+
+فائل ڈیٹا سورس کے ہینڈلرز اور ہستیوں کو دیگر سب گراف ہستیوں سے الگ تھلگ کر دیا جاتا ہے، اس بات کو یقینی بناتے ہوئے کہ عمل درآمد کے وقت وہ تعیین پسند ہیں، اور اس بات کو یقینی بناتے ہیں کہ چین پر مبنی ڈیٹا سورسز کی کوئی آلودگی نہ ہو۔ مخصوص ہونا:
+
+- فائل ڈیٹا سورسز کے ذریعے تخلیق کردہ ادارے ناقابل تغیر ہیں، اور انہیں اپ ڈیٹ نہیں کیا جا سکتا
+- فائل ڈیٹا کے ذرائع ہینڈلرز دوسرے فائل ڈیٹا سورسز سے اداروں تک رسائی حاصل نہیں کرسکتے ہیں
+- فائل ڈیٹا کے ذرائع سے وابستہ ہستیوں تک چین پر مبنی ہینڈلرز تک رسائی حاصل نہیں کی جا سکتی ہے
+
+> اگرچہ یہ رکاوٹ زیادہ تر استعمال کے معاملات کے لیے مشکل نہیں ہونی چاہیے، لیکن یہ کچھ لوگوں کے لیے پیچیدگی پیدا کر سکتی ہے۔ براہ کرم ڈسکورڈ کے ذریعے رابطہ کریں اگر آپ کو اپنے فائل پر مبنی ڈیٹا کو سب گراف میں ماڈل کرنے میں مسئلہ درپیش ہے!
+
+مزید برآں، فائل ڈیٹا سورس سے ڈیٹا سورسز بنانا ممکن نہیں ہے، چاہے وہ آن چین ڈیٹا سورس ہو یا کوئی اور فائل ڈیٹا سورس۔ مستقبل میں یہ پابندی ختم ہو سکتی ہے.
+
+#### بہترین طریقے
+
+اگر آپ NFT میٹا ڈیٹا کو متعلقہ ٹوکنز سے جوڑ رہے ہیں، تو ٹوکن ہستی سے میٹا ڈیٹا ہستی کا حوالہ دینے کے لیے میٹا ڈیٹا کے IPFS ہیش کا استعمال کریں۔ آئی پی ایف ایس ہیش کو بطور ID استعمال کرتے ہوئے میٹا ڈیٹا ہستی کو محفوظ کریں.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> ہم مندرجہ بالا سفارش کو بہتر بنانے کے لیے کام کر رہے ہیں، لہذا کیوریز صرف "حالیہ ترین" ورژن واپس کرتے ہیں
+
+#### معلوم مسائل
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### مثالیں
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### حوالہ جات
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### موجودہ سب گرافس پر گرافٹنگ
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+چونکہ گرافٹنگ بیس ڈیٹا کو انڈیکس کرنے کے بجائے کاپی کرتا ہے، شروع سے انڈیکس کرنے کے مقابلے میں مطلوبہ بلاک میں سب گراف حاصل کرنا بہت تیز ہے، حالانکہ ابتدائی ڈیٹا کاپی بہت بڑے سب گراف کے لیے کئی گھنٹے لگ سکتی ہے۔ جب گرافٹ شدہ سب گراف کو شروع کیا جا رہا ہے، گراف نوڈ ان ہستی کی اقسام کے بارے میں معلومات کو لاگ کرے گا جو پہلے ہی کاپی ہو چکی ہیں.
+
+گرافٹڈ سب گراف ایک GraphQL اسکیما استعمال کرسکتا ہے جو بیس سب گراف میں سے ایک سے مماثل نہیں ہے، لیکن اس کے ساتھ محض مطابقت رکھتا ہے۔ یہ اپنے طور پر ایک درست سب گراف سکیما ہونا ضروری ہے، لیکن مندرجہ ذیل طریقوں سے بنیادی سب گراف کے سکیما سے انحراف کر سکتا ہے:
+
+- یہ ہستی کی اقسام کو ڈالتا یا ہٹاتا ہے
+- یہ ہستی کی اقسام سے صفات کو ہٹاتا ہے
+- یہ ہستی کی اقسام میں nullable صفات کا اضافہ کرتا ہے
+- یہ non-nullable صفات کو nullable صفات میں بدل دیتا ہے
+- یہ enums میں اقدار کا اضافہ کرتا ہے
+- یہ انٹرفیس میں اضافہ کرتا یا ہٹاتا ہے
+- یہ ان ہستی کی اقسام کے لیے تبدیل ہوتا ہے جن کے لیے ایک انٹرفیس لاگو کیا جاتا ہے
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From b51c13ba0caa5d65a5a62df1784642e637734838 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:35 -0500
Subject: [PATCH 0347/1325] New translations assemblyscript-mappings.mdx (Urdu
 (Pakistan))

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/ur/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/ur/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/ur/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..28f2936bb14f
--- /dev/null
+++ b/website/pages/ur/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## جائزہ
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## میپنگ لکھنا
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### نئ ہستیوں بنانے کے لیے تجویز کردہ IDs
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## کوڈ تخلیق کرنا
+
+سمارٹ کنٹریکٹس، ایوینٹس اور ہستیوں کے ساتھ کام کرنا آسان اور ٹائپ محفوظ بنانے کے لیے، گراف CLI ڈیٹا کے ذرائع میں شامل سب گراف کے GraphQL اسکیما اور کنٹریکٹ ABIs سے اسمبلی سکرپٹ کی قسمیں تیار کر سکتا ہے.
+
+اس کے ساتھ کیا جاتا ہے
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 3e4775427d86ea0f9e38ca43cf9e0759674adeab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:36 -0500
Subject: [PATCH 0348/1325] New translations install-the-cli.mdx (Urdu
 (Pakistan))

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..df53c1b48b6e
--- /dev/null
+++ b/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: گراف CLI انسٹال کریں
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## جائزہ
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## شروع ہوا چاہتا ہے
+
+### گراف CLI انسٹال کریں
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+اپنی مقامی مشین پر، درج زیل کمانڈز میں سے ایک کو رن کریں:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## سب گراف بنائیں
+
+### ایک موجودہ کنٹریکٹ سے
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### ایک مثالی سب گراف سے
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+ABI فائل (فائلیں) آپ کے کنٹریکٹ (کنٹریکٹس) سے مماثل ہونی چاہیں. ABI کی فائلیں حاصل کرنے کے چند طریقے ہیں:
+
+- اگر آپ اپنا پراجیکٹ خود بنا رہے ہیں، تو ممکنہ طور پر آپ کو اپنے حالیہ ABIs تک رسائی حاصل ہوگی.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+|  ورزن | جاری کردہ نوٹس                                                                                                                                                           |
+| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
+| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |

From 72657299212c85689b7a20087a61d7f5096253f2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:37 -0500
Subject: [PATCH 0349/1325] New translations ql-schema.mdx (Urdu (Pakistan))

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..7838cac596df
--- /dev/null
+++ b/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## جائزہ
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### اچھی مثال
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### بری مثال
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### اختیاری اور مطلوبہ فیلڈز
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+غیر صفر فیلڈ 'name' کے لیے خالی ویلیو حل ہو گئی
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### بلٹ ان اسکیلر اقسام
+
+#### GraphQL حمایت یافتہ اسکیلرز
+
+The following scalars are supported in the GraphQL API:
+
+| قسم          | تفصیل                                                                                                                                                                                                            |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array، ایک ہیکساڈیسیمل سٹرنگ کے طور پر پیش کیا جاتا ہے. عام طور پر Ethereum hashes اور ایڈریسیس کے لیے استعمال ہوتا ہے.                                                                                     |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+آپ اسکیما کے اندر enums بھی بنا سکتے ہیں. Enums میں درج ذیل نحو ہے:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### ہستی کے تعلقات
+
+آپ کے اسکیما میں ایک ہستی کا ایک یا زیادہ دیگر ہستیوں سے تعلق ہو سکتا ہے. یہ تعلق آپ کے کیوریز میں شامل ہو سکتے ہیں۔ گراف میں تعلق یک طرفہ ہوتے ہیں۔ تعلق کے کسی بھی "اختتام" پر یک طرفہ تعلق کی وضاحت کرکے دو طرفہ تعلق کی تقلید کرنا ممکن ہے.
+
+تعلقات کی تعریف کسی دوسری فیلڈ کی طرح ہستیوں پر کی جاتی ہے سوائے اس کے کہ مخصوص کردہ قسم کسی اور ہستی کی ہو.
+
+#### ون-ٹو-ون تعلقات
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### ون-ٹو-مینی تعلقات
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### ریورس لک اپس
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+ون-ٹو-مینی تعلقات کے لیے، تعلق کو ہمیشہ 'ون' سائیڈ پر رکھنا چاہیے، اور 'مینی' سائیڈ کو ہمیشہ اخذ کیا جانا چاہیے۔ 'مینی' سائیڈ پر ہستیوں کی ایک ایرے کو ذخیرہ کرنے کے بجائے اس طرح سے تعلق کو ذخیرہ کرنے کے نتیجے میں سب گراف کی انڈیکسنگ اور کیوریز دونوں کے لیے نمایاں طور پر بہتر کارکردگی ہوگی۔ عام طور پر، ہستیوں کی ایریز کو ذخیرہ کرنے سے اتنا ہی گریز کیا جانا چاہیے جتنا کہ عملی ہو.
+
+#### مثال
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### ون-ٹو-مینی تعلقات
+
+مینی-ٹو-مینی تعلقات کے لیے، جیسے کہ صارفین جن میں سے ہر ایک کا تعلق کسی بھی تعداد میں تنظیموں سے ہو سکتا ہے، سب سے سیدھا، لیکن عام طور پر سب سے زیادہ پرفارمنس نہیں، تعلق کو ماڈل کرنے کا طریقہ شامل دونوں ہستیوں میں سے ہر ایک میں ایک ایرے کے طور پر ہے۔ اگر تعلق ہم آہنگ ہے تو، رشتے کے صرف ایک رخ کو ذخیرہ کرنے کی ضرورت ہے اور دوسری طرف اخذ کیا جا سکتا ہے.
+
+#### مثال
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+اس نقطہ نظر کا تقاضا ہے کہ کیوریز کو بازیافت کرنے کے لیے ایک اضافی سطح پر اتریں، مثال کے طور پر، صارفین کے لیے تنظیمیں:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+Many-to-many تعلقات کو ذخیرہ کرنے کے اس زیادہ وسیع طریقے کے نتیجے میں سب گراف کے لیے کم ڈیٹا ذخیرہ کیا جائے گا، اور اس لیے ایک سب گراف میں جو اکثر نمایاں طور پر انڈیکس اور کیوری کے لیے تیز تر ہوتا ہے.
+
+### اسکیما میں کامینٹس شامل کرنا
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## فل ٹیکسٹ سرچ فیلڈز کی وضاحت کرنا
+
+ٹیکسٹ سرچ ان پٹ کی بنیاد پر فل ٹیکسٹ سرچ کیوریز ہستیوں کو فلٹر اور رینک کرتی ہیں. فل ٹیکسٹ کیوریز انڈیکس شدہ ٹیکسٹ ڈیٹا سے موازنہ کرنے سے پہلے کیوری کے متن کے ان پٹ کو سٹیمز میں پروسیس کرکے ملتے جلتے الفاظ کے میچز واپس کرنے کے قابل ہیں.
+
+فل ٹیکسٹ کیوری کی تعریف میں کیوری کا نام، ٹیکسٹ فیلڈز پر کارروائی کرنے کے لیے استعمال ہونے والی زبات کی لغت، نتائج کو ترتیب دینے کے لیے استعمال ہونے والا رینکنگ ایلگورتھم، اور تلاش میں شامل فیلڈز شامل ہیں. ہر فل ٹیکسٹ کیوری ایک سے زیادہ فیلڈز پر محیط ہو سکتا ہے، لیکن تمام شامل فیلڈز ایک ہی ہستی کی قسم سے ہونے چاہئیں.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## تعاون یافتہ زبانیں ہیں
+
+ایک مختلف زبان کا انتخاب فل ٹیکسٹ کی تلاش کی API پر حتمی، اگرچہ بعض اوقات لطیف، اثر رکھتا ہے۔ فل ٹیکسٹ کیوری والے فیلڈز کا احاطہ منتخب کردہ زبان کے تناظر میں کیا جاتا ہے، اس لیے تجزیہ اور تلاش کی کیوریز کے ذریعہ تیار کردہ لیگزیمز زبان سے دوسری زبان میں مختلف ہوتے ہیں۔ مثال کے طور پر: جب تعاون یافتہ ترکی لغت کا استعمال کرتے ہوئے "ٹوکن" کو "ٹوک" کے لیے سٹیم کیا جاتا ہے، جب کہ، یقیناً، انگریزی لغت اسے "ٹوکن" پر سٹیم کرے گی.
+
+معاون زبانوں کی لغت:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | پرتگالی    |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### درجہ بندی الگورتھم
+
+نتائج ترتیب دینے کے لیے معاون الگورتھم:
+
+| Algorithm     | Description                                                                 |
+| ------------- | --------------------------------------------------------------------------- |
+| rank          | نتائج ترتیب دینے کے لیے فل ٹیکسٹ کیوری کے میچ کوالٹی (1-0) کا استعمال کریں. |
+| قربت کا درجہ  | Similar to rank but also includes the proximity of the matches.             |

From c40167fe1cfaceb952747217ee5872ba42b7c7d9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:38 -0500
Subject: [PATCH 0350/1325] New translations subgraph-manifest.mdx (Urdu
 (Pakistan))

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/ur/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/ur/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/ur/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..d81254c61923
--- /dev/null
+++ b/website/pages/ur/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## جائزہ
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+مینی فیسٹ کے لیے اپ ڈیٹ کرنے کے لیے اہم اندراجات یہ ہیں:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## کال ہینڈلرز
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+کال ہینڈلرز صرف دو صورتوں میں سے ایک میں ٹرگر کریں گے: جب مخصوص کردہ فنکشن کو کنٹریکٹ کے علاوہ کسی دوسرے اکاؤنٹ سے کال جاتا ہے یا جب اسے سولیڈیٹی میں بیرونی کے طور پر نشان زد کیا جاتا ہے اور اسی کنٹریکٹ میں کسی دوسرے فنکشن کے حصے کے طور پر کال کیا جاتا ہے.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### کال ہینڈلر کی تعریف
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### میپنگ فنکشن
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## بلاک ہینڈلرز
+
+کنٹریکٹ ایونٹس یا فنکشن کالز کو سبسکرائب کرنے کے علاوہ، ایک سب گراف اپنے ڈیٹا کو اپ ڈیٹ کرنا چاہتا ہے جیسے جیسے چین میں نئے بلاکس شامل ہوتے ہیں. اس کو حاصل کرنے کے لیے ایک سب گراف ہر بلاک کے بعد یا پہلے سے طے شدہ فلٹر سے مماثل بلاکس کے بعد ایک فنکشن چلا سکتا ہے.
+
+### معاون فلٹرز
+
+#### کال فلٹر
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+بلاک ہینڈلر کے لیے فلٹر کی عدم موجودگی اس بات کو یقینی بنائے گی کہ ہینڈلر کو ہر بلاک کے لیے کال کیا جاتا ہے. ڈیٹا سورس میں ہر فلٹر کی قسم کے لیے صرف ایک بلاک ہینڈلر ہو سکتا ہے.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### پولنگ فلٹر
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### ونس فلٹر
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+ایک بار فلٹر کے ساتھ متعین ہینڈلر کو دوسرے تمام ہینڈلرز کے چلنے سے پہلے صرف ایک بار کال کیا جائے گا۔ یہ کنفیگریشن سب گراف کو انڈیکسنگ کے آغاز میں مخصوص کاموں کو انجام دیتے ہوئے، ہینڈلر کو ابتدائیہ ہینڈلر کے طور پر استعمال کرنے کی اجازت دیتی ہے.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### میپنگ فنکشن
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## گمنام ایونٹس
+
+اگر آپ کو سولیڈیٹی میں گمنام ایوینٹس پر کارروائی کرنے کی ضرورت ہے، تو یہ ایونٹ کا عنوان 0 فراہم کرکے حاصل کیا جاسکتا ہے، جیسا کہ مثال میں:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## ایونٹ ہینڈلرز میں ٹرانزیکشن کی رسیدیں
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+بلاک کے اندر ڈیٹا سورس کے لیے محرکات درج ذیل عمل کا استعمال کرتے ہوئے ترتیب دیے گئے ہیں:
+
+1. ایونٹ اور کال ٹریگرز کو پہلے بلاک کے اندر ٹرانزیکشن انڈیکس سے ترتیب دیا جاتا ہے.
+2. ایک ہی ٹرانزیکشن کے اندر ایونٹ اور کال ٹرگرز کو روایت کا استعمال کرتے ہوئے ترتیب دیا جاتا ہے: پہلے ایونٹ ٹرگرز پھر کال ٹرگرز، ہر قسم اس ترتیب کا احترام کرتی ہے جس کی وضاحت مینی فیسٹ میں کی گئی ہے.
+3. بلاک ٹریگرز ایونٹ اور کال ٹریگرز کے بعد چلائے جاتے ہیں، اس ترتیب میں جس کی وضاحت مینی فیسٹ میں کی گئی ہے.
+
+ترتیب دینے کے یہ اصول تبدیل کیے جا سکتے ہیں.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## ڈیٹا سورس ٹیمپلیٹس
+
+EVM سے مطابقت رکھنے والے سمارٹ کنٹریکٹس میں ایک عام نمونہ رجسٹری یا فیکٹری کنٹریکٹس کا استعمال ہے، جہاں ایک کنٹریکٹ دوسرے کنٹریکٹس کی صوابدیدی تعداد کو تخلیق کرتا ہے، ان کا انتظام کرتا ہے یا حوالہ دیتا ہے جن میں سے ہر ایک کی اپنی ریاست اور واقعات ہوتے ہیں.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### مرکزی کنٹریکٹ کے لیے ڈیٹا سورس
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### متحرک طور پر بنائے گئے کنٹریکٹس کے لیے ڈیٹا سورس ٹیمپلیٹس
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### ڈیٹا سورس ٹیمپلیٹ کو شروع کرنا
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> اگر پہلے والے بلاکس میں نئے ڈیٹا سورس سے متعلقہ ڈیٹا ہوتا ہے، تو یہ بہترین ہے کہ کنٹریکٹ کی موجودہ حالت کو پڑھ کر اور ڈیٹا کا نیا سورس بننے کے وقت اس سٹیٹ کی نمائندگی کرنے والی اینٹیٹیز بنا کر اس ڈیٹا کو انڈیکس کریں.
+
+### ڈیٹا سورس سیاق و سباق
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## بلاکس شروع کریں
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. سرچ بار میں اس کا ایڈریس درج کرکے کنٹریکٹ کو تلاش کریں.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. ٹرانزیکشن کی تفصیلات کا صفحہ لوڈ کریں جہاں آپ کو اس کنٹریکٹ کے لیے اسٹارٹ بلاک ملے گا.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From ca4e16b3931464b92ec3b5d5a3ebd765177120b3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:40 -0500
Subject: [PATCH 0351/1325] New translations index.json (Marathi)

---
 website/pages/mr/index.json | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/website/pages/mr/index.json b/website/pages/mr/index.json
index 2c7aec422d6b..5d50b71571c4 100644
--- a/website/pages/mr/index.json
+++ b/website/pages/mr/index.json
@@ -56,10 +56,6 @@
       "graphExplorer": {
         "title": "Graph Explorer",
         "description": "सबग्राफ एक्सप्लोर करा आणि प्रोटोकॉलशी संवाद साधा"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
       }
     }
   },

From e3ee02503df3cfa2b0c89fe13314528d9982c20c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:41 -0500
Subject: [PATCH 0352/1325] New translations index.json (Hindi)

---
 website/pages/hi/index.json | 24 ++++++++++--------------
 1 file changed, 10 insertions(+), 14 deletions(-)

diff --git a/website/pages/hi/index.json b/website/pages/hi/index.json
index d8621bee93f5..8b2ce2fa9a68 100644
--- a/website/pages/hi/index.json
+++ b/website/pages/hi/index.json
@@ -28,26 +28,26 @@
     "description": "ग्राफ़ की नेटवर्क भूमिकाओं के बारे में जानें।",
     "roles": {
       "developer": {
-        "title": "Developer",
-        "description": "Create a subgraph or use existing subgraphs in a dapp"
+        "title": "डेवलपर",
+        "description": "एक subgraph बनाएं या dapp में मौजूदा subgraph का उपयोग करें"
       },
       "indexer": {
         "title": "Indexer",
-        "description": "Operate a node to index data and serve queries"
+        "description": "कोई नोड संचालित करें ताकि डेटा को इंडेक्स किया जा सके और queries को सर्व किया जा सके"
       },
       "curator": {
         "title": "Curator",
-        "description": "Organize data by signaling on subgraphs"
+        "description": "डेटा को 'signaling' द्वारा subgraphs पर व्यवस्थित करें"
       },
       "delegator": {
         "title": "Delegator",
-        "description": "Secure the network by delegating GRT to Indexers"
+        "description": "नेटवर्क को सुरक्षित करें GRT को Indexers को डेलीगेट करके"
       }
     }
   },
   "readMore": "और जानें",
   "products": {
-    "title": "Products",
+    "title": "उत्पादों",
     "products": {
       "subgraphStudio": {
         "title": "Subgraph Studio",
@@ -55,17 +55,13 @@
       },
       "graphExplorer": {
         "title": "Graph Explorer",
-        "description": "Explore subgraphs and interact with the protocol"
-      },
-      "hostedService": {
-        "title": "Hosted Service",
-        "description": "Create and explore subgraphs on the hosted service"
+        "description": "सबग्राफ़ और प्रोटोकॉल के साथ इंटरैक्ट करें"
       }
     }
   },
   "supportedNetworks": {
-    "title": "Supported Networks",
-    "description": "The Graph supports the following networks.",
-    "footer": "For more details, see the {0} page."
+    "title": "समर्थित नेटवर्क",
+    "description": "The Graph निम्नलिखित नेटवर्क का समर्थन करता है।",
+    "footer": "अधिक जानकारी के लिए, {0} पेज देखें।"
   }
 }

From cf7cfb0040fa5c35679a3bac84d32bc748a8d69a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:42 -0500
Subject: [PATCH 0353/1325] New translations near.mdx (Vietnamese)

---
 website/pages/vi/cookbook/near.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/vi/cookbook/near.mdx b/website/pages/vi/cookbook/near.mdx
index 2f54699539cb..9f56cb19e152 100644
--- a/website/pages/vi/cookbook/near.mdx
+++ b/website/pages/vi/cookbook/near.mdx
@@ -194,8 +194,8 @@ The node configuration will depend on where the subgraph is being deployed.
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### Local Graph Node (based on default configuration)

From 57922d32a5c5b654b368c4954a407e177cea28cc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:43 -0500
Subject: [PATCH 0354/1325] New translations unit-testing-framework.mdx
 (Vietnamese)

---
 .../vi/developing/unit-testing-framework.mdx  | 43 ++++++++++++-------
 1 file changed, 28 insertions(+), 15 deletions(-)

diff --git a/website/pages/vi/developing/unit-testing-framework.mdx b/website/pages/vi/developing/unit-testing-framework.mdx
index fcd3af4a4ae2..7bab8ce8c859 100644
--- a/website/pages/vi/developing/unit-testing-framework.mdx
+++ b/website/pages/vi/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: Unit Testing Framework
 ---
 
-Matchstick is a unit testing framework, developed by [LimeChain](https://limechain.tech/), that enables subgraph developers to test their mapping logic in a sandboxed environment and deploy their subgraphs with confidence!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## Getting Started
 
-### Install dependencies
+### Install Dependencies
 
-In order to use the test helper methods and run the tests, you will need to install the following dependencies:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` depends on PostgreSQL, so if you don't already have it, you will need to install it. We highly advise using the commands below as adding it in any other way may cause unexpected errors!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres installation command:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ Create a symlink to the latest libpq.5.lib _You may need to create this dir firs
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-Postgres installation command (depends on your distro):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (Windows Subsystem for Linux)
+### Using WSL (Windows Subsystem for Linux)
 
 You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
 
@@ -76,7 +85,7 @@ And finally, do not use `graph test` (which uses your global installation of gra
 }
 ```
 
-### Sử dụng
+### Using Matchstick
 
 To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
 
@@ -1371,19 +1380,23 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## Feedback
 
 If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 809b4099d315d1c928f3dae536e472551dafd81e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:44 -0500
Subject: [PATCH 0355/1325] New translations about.mdx (Marathi)

---
 website/pages/mr/about.mdx | 62 +++++++++++++++++++++++++-------------
 1 file changed, 41 insertions(+), 21 deletions(-)

diff --git a/website/pages/mr/about.mdx b/website/pages/mr/about.mdx
index 221d6e16692d..d560ebcd179d 100644
--- a/website/pages/mr/about.mdx
+++ b/website/pages/mr/about.mdx
@@ -2,46 +2,66 @@
 title: ग्राफ बद्दल
 ---
 
-The Graph म्हणजे काय आणि तुम्ही सुरुवात कशी करू शकता हे हे पान स्पष्ट करेल.
-
 ## द ग्राफ म्हणजे काय?
 
-आलेख हे ब्लॉकचेन डेटाचे अनुक्रमणिका आणि क्वेरी करण्यासाठी विकेंद्रित प्रोटोकॉल आहे. ग्राफ थेट क्वेरी करणे कठीण असलेल्या डेटाची क्वेरी करणे शक्य करते.
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
 
-[Uniswap](https://uniswap.org/) सारखे जटिल स्मार्ट करार आणि [Bored Ape Yacht Club< सारखे NFTs उपक्रम असलेले प्रकल्प ](https://boredapeyachtclub.com/) इथरियम ब्लॉकचेनवर डेटा संग्रहित करा, ज्यामुळे ब्लॉकचेनमधून थेट मूलभूत डेटाशिवाय इतर काहीही वाचणे खरोखर कठीण होते.
+## The Graph Provides a Solution
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+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.
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+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.
 
-तुम्ही तुमचा स्वतःचा सर्व्हर तयार करू शकता, तिथल्या व्यवहारांवर प्रक्रिया करू शकता, त्यांना डेटाबेसमध्ये सेव्ह करू शकता आणि डेटाची क्वेरी करण्यासाठी या सर्वांच्या वर API एंडपॉइंट तयार करू शकता. तथापि, हा पर्याय [संसाधन गहन](/network/benefits/) आहे, देखभाल आवश्यक आहे, अपयशाचा एकच बिंदू सादर करतो आणि विकेंद्रीकरणासाठी आवश्यक असलेले महत्त्वाचे सुरक्षा गुणधर्म खंडित करतो.
+### How The Graph Functions
 
-**ब्लॉकचेन डेटा अनुक्रमित करणे खरोखर, खरोखर कठीण आहे.**
+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.
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+#### Specifics
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+- 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.
 
-This diagram gives more detail about the flow of data once a subgraph manifest has been deployed, dealing with Ethereum transactions:
+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. ग्राफ नोड सतत नवीन ब्लॉक्ससाठी इथरियम स्कॅन करतो आणि तुमच्या सबग्राफचा डेटा त्यात असू शकतो.
-4. ग्राफ नोड या ब्लॉक्समध्ये तुमच्या सबग्राफसाठी इथरियम इव्हेंट शोधतो आणि तुम्ही प्रदान केलेले मॅपिंग हँडलर चालवतो. मॅपिंग हे WASM मॉड्यूल आहे जे इथरियम इव्हेंट्सच्या प्रतिसादात ग्राफ नोड संचयित केलेल्या डेटा घटक तयार करते किंवा अद्यतनित करते.
-5. नोडचा [GraphQL एंडपॉइंट](https://graphql.org/learn/) वापरून ब्लॉकचेन वरून अनुक्रमित केलेल्या डेटासाठी dapp ग्राफ नोडची क्वेरी करते. ग्राफ नोड यामधून, स्टोअरच्या इंडेक्सिंग क्षमतांचा वापर करून, हा डेटा मिळविण्यासाठी त्याच्या अंतर्निहित डेटा स्टोअरच्या क्वेरींमध्ये GraphQL क्वेरीचे भाषांतर करतो. dapp हा डेटा अंतिम वापरकर्त्यांसाठी समृद्ध UI मध्ये प्रदर्शित करते, जो ते Ethereum वर नवीन व्यवहार जारी करण्यासाठी वापरतात. चक्राची पुनरावृत्ती होते.
+1.  A dapp स्मार्ट करारावरील व्यवहाराद्वारे इथरियममध्ये डेटा जोडते.
+2.  व्यवहारावर प्रक्रिया करताना स्मार्ट करार एक किंवा अधिक इव्हेंट सोडतो.
+3.  ग्राफ नोड सतत नवीन ब्लॉक्ससाठी इथरियम स्कॅन करतो आणि तुमच्या सबग्राफचा डेटा त्यात असू शकतो.
+4.  ग्राफ नोड या ब्लॉक्समध्ये तुमच्या सबग्राफसाठी इथरियम इव्हेंट शोधतो आणि तुम्ही प्रदान केलेले मॅपिंग हँडलर चालवतो. मॅपिंग हे WASM मॉड्यूल आहे जे इथरियम इव्हेंट्सच्या प्रतिसादात ग्राफ नोड संचयित केलेल्या डेटा घटक तयार करते किंवा अद्यतनित करते.
+5.  नोडचा [GraphQL एंडपॉइंट](https://graphql.org/learn/) वापरून ब्लॉकचेन वरून अनुक्रमित केलेल्या डेटासाठी dapp ग्राफ नोडची क्वेरी करते. ग्राफ नोड यामधून, स्टोअरच्या इंडेक्सिंग क्षमतांचा वापर करून, हा डेटा मिळविण्यासाठी त्याच्या अंतर्निहित डेटा स्टोअरच्या क्वेरींमध्ये GraphQL क्वेरीचे भाषांतर करतो. dapp हा डेटा अंतिम वापरकर्त्यांसाठी समृद्ध UI मध्ये प्रदर्शित करते, जो ते Ethereum वर नवीन व्यवहार जारी करण्यासाठी वापरतात. चक्राची पुनरावृत्ती होते.
 
 ## पुढील पायऱ्या
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+The following sections provide a more in-depth look at subgraphs, their deployment and data querying.
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+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.

From daabb0907cf0b276befe7ecf001066f6f5b293ae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:45 -0500
Subject: [PATCH 0356/1325] New translations near.mdx (Marathi)

---
 website/pages/mr/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/mr/cookbook/near.mdx b/website/pages/mr/cookbook/near.mdx
index b7aa353c2576..efd00f148a8f 100644
--- a/website/pages/mr/cookbook/near.mdx
+++ b/website/pages/mr/cookbook/near.mdx
@@ -37,7 +37,7 @@ This guide is an introduction to building subgraphs indexing smart contracts on
 
 **schema.graphql:** एक स्कीमा फाइल जी तुमच्या सबग्राफसाठी कोणता डेटा संग्रहित केला जातो आणि GraphQL द्वारे त्याची क्वेरी कशी करावी हे परिभाषित करते. जवळच्या सबग्राफसाठी आवश्यकता [विद्यमान दस्तऐवज](/developing/creating-a-subgraph#the-graphql-schema) द्वारे कव्हर केल्या जातात.
 
-**AssemblyScript मॅपिंग:** [AssemblyScript कोड](/developing/graph-ts/api) जो इव्हेंट डेटामधून तुमच्या स्कीमामध्ये परिभाषित केलेल्या घटकांमध्ये अनुवादित करतो. NEAR समर्थन NEAR-विशिष्ट डेटा प्रकार आणि नवीन JSON पार्सिंग कार्यक्षमता सादर करते.
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
 
 सबग्राफ विकासादरम्यान दोन प्रमुख आज्ञा आहेत:
 
@@ -98,7 +98,7 @@ accounts:
 
 इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत.
 
-NEAR अनुक्रमणिका [AssemblyScript API](/developing/graph-ts/api) मध्ये NEAR-विशिष्ट डेटा प्रकारांचा परिचय देते.
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
 
 ```typescript
 
@@ -165,9 +165,9 @@ class ReceiptWithOutcome {
 - ब्लॉक हँडलर्सना एक `ब्लॉक` मिळेल
 - पावती हाताळणाऱ्यांना `ReceiptWithOutcome` मिळेल
 
-अन्यथा, उर्वरित [AssemblyScript API](/developing/graph-ts/api) मॅपिंग अंमलबजावणी दरम्यान जवळच्या सबग्राफ विकसकांसाठी उपलब्ध आहे.
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
-यामध्ये नवीन JSON पार्सिंग फंक्शन समाविष्ट आहे - NEAR वरील लॉग वारंवार स्ट्रिंगिफाइड JSON म्हणून उत्सर्जित केले जातात. एक नवीन `json.fromString(...)`विकासकांना या लॉगवर सहज प्रक्रिया करण्याची अनुमती देण्यासाठी unction [JSON API](/developing/graph-ts/api#json-api) चा भाग म्हणून उपलब्ध आहे.
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
 
 ## NEAR सबग्राफ डिप्लॉय करण्यासाठी
 
@@ -194,8 +194,8 @@ $ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <su
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### स्थानिक आलेख नोड (डीफॉल्ट कॉन्फिगरेशनवर आधारित)

From ca26617177f75012e442451a8f9b9d1111c03af7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:47 -0500
Subject: [PATCH 0357/1325] New translations unit-testing-framework.mdx
 (Marathi)

---
 .../mr/developing/unit-testing-framework.mdx  | 45 ++++++++++++-------
 1 file changed, 29 insertions(+), 16 deletions(-)

diff --git a/website/pages/mr/developing/unit-testing-framework.mdx b/website/pages/mr/developing/unit-testing-framework.mdx
index 38eeb39845b6..00db6cc5372c 100644
--- a/website/pages/mr/developing/unit-testing-framework.mdx
+++ b/website/pages/mr/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: युनिट चाचणी फ्रेमवर्क
 ---
 
-मॅचस्टिक हे एक युनिट चाचणी फ्रेमवर्क आहे, जे [LimeChain](https://limechain.tech/) ने विकसित केले आहे, जे सबग्राफ डेव्हलपरना त्यांच्या मॅपिंग लॉजिकची सँडबॉक्स्ड वातावरणात चाचणी घेण्यास आणि त्यांचे सबग्राफ आत्मविश्वासाने तैनात करण्यास सक्षम करते!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## प्रारंभ करणे
 
-### अवलंबित्व स्थापित करा
+### Install Dependencies
 
-चाचणी मदतनीस पद्धती वापरण्यासाठी आणि चाचण्या चालवण्यासाठी, तुम्हाला खालील अवलंबन स्थापित करणे आवश्यक आहे:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `ग्राफ-नोड` PostgreSQL वर अवलंबून आहे, त्यामुळे तुमच्याकडे ते आधीपासून नसेल, तर तुम्हाला ते इंस्टॉल करावे लागेल. आम्ही खालील आदेश वापरण्याचा सल्ला देतो कारण ते इतर कोणत्याही प्रकारे जोडल्यास अनपेक्षित त्रुटी येऊ शकतात!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-Postgres स्थापना आदेश:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ brew install postgresql
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### लिनक्स
+#### Using Linux
 
-पोस्टग्रेस इंस्टॉलेशन कमांड (तुमच्या डिस्ट्रोवर अवलंबून आहे):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (लिनक्ससाठी विंडोज सबसिस्टम)
+### Using WSL (Windows Subsystem for Linux)
 
 डॉकर दृष्टिकोन आणि बायनरी दृष्टिकोन वापरून तुम्ही WSL वर मॅचस्टिक वापरू शकता. डब्ल्यूएसएल थोडे अवघड असू शकते, यासारख्या समस्या आल्यास येथे काही टिपा आहेत
 
@@ -76,7 +85,7 @@ sudo apt-get install libpq-dev
 }
 ```
 
-### वापर
+### Using Matchstick
 
 तुमच्या सबग्राफ प्रोजेक्टमध्ये **Matchstick** वापरण्यासाठी फक्त एक टर्मिनल उघडा, तुमच्या प्रोजेक्टच्या रूट फोल्डरवर नेव्हिगेट करा आणि फक्त `ग्राफ चाचणी [options] <datasource> ` - ते नवीनतम **Matchstick** बायनरी डाउनलोड करते आणि चाचणी फोल्डरमध्ये निर्दिष्ट चाचणी किंवा सर्व चाचण्या चालवते (किंवा कोणताही डेटासोर्स ध्वज निर्दिष्ट केलेला नसल्यास सर्व विद्यमान चाचण्या).
 
@@ -1368,22 +1377,26 @@ ___ ___ _ _ _ _ _
 
 > गंभीर: संदर्भासह वैध मॉड्यूलमधून WasmInstance तयार करू शकलो नाही: अज्ञात आयात: wasi_snapshot_preview1::fd_write परिभाषित केले गेले नाही
 
-याचा अर्थ तुम्ही तुमच्या कोडमध्ये `console.log` वापरले आहे, जे असेंबलीस्क्रिप्टद्वारे समर्थित नाही. कृपया [लॉगिंग API](/developing/graph-ts/api/#logging-api) वापरण्याचा विचार करा
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > त्रुटी TS2554: अपेक्षित आहे? युक्तिवाद, पण मिळाले?.
->
+> 
 > नवीन ethereum.Transaction परत करा(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 `graph-ts` आणि `matchstick-as` मधील जुळत नसल्यामुळे वितर्कांमधील जुळत नाही. यासारख्या समस्यांचे निराकरण करण्याचा सर्वोत्तम मार्ग म्हणजे नवीनतम रिलीझ केलेल्या आवृत्तीवर सर्वकाही अद्यतनित करणे.
 
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## अभिप्राय
 
 तुमच्याकडे काही प्रश्न, अभिप्राय, वैशिष्ट्य विनंत्या असल्यास किंवा फक्त संपर्क साधायचा असल्यास, सर्वोत्तम ठिकाण म्हणजे The Graph Discord जेथे आमच्याकडे Matchstick साठी एक समर्पित चॅनेल आहे, ज्याला 🔥| युनिट-चाचणी.

From 33c00285d11d644c06297e66eefca33c4a39408a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:48 -0500
Subject: [PATCH 0358/1325] New translations about.mdx (Hindi)

---
 website/pages/hi/about.mdx | 64 +++++++++++++++++++++++++-------------
 1 file changed, 42 insertions(+), 22 deletions(-)

diff --git a/website/pages/hi/about.mdx b/website/pages/hi/about.mdx
index d410edbe8d76..e2937886768f 100644
--- a/website/pages/hi/about.mdx
+++ b/website/pages/hi/about.mdx
@@ -1,47 +1,67 @@
 ---
-title: ग्राफ के बारे में
+title: The Graph के बारे में
 ---
 
-यह पृष्ठ समझाएगा कि ग्राफ़ क्या है और आप कैसे आरंभ कर सकते हैं।
+## What is The Graph?
 
-## ग्राफ क्या है?
+The Graph एक शक्तिशाली विकेंद्रीकृत प्रोटोकॉल है जो ब्लॉकचेन डेटा को आसानी से क्वेरी और इंडेक्स करने में सक्षम बनाता है। यह ब्लॉकचेन डेटा को क्वेरी करने की जटिल प्रक्रिया को सरल बनाता है, जिससे डैप विकास तेज और आसान हो जाता है।
 
-एथेरियम से शुरू होने वाले ब्लॉकचेन से डेटा को अनुक्रमित करने और क्वेरी करने के लिए ग्राफ़ एक विकेन्द्रीकृत प्रोटोकॉल है। यह डेटा को क्वेरी करना संभव बनाता है जिसे सीधे क्वेरी करना मुश्किल होता है।
+## मूल बातें समझना
 
-[Uniswap](https://uniswap.org/) जैसे जटिल स्मार्ट अनुबंध वाले प्रोजेक्ट और [Bored Ape Yacht Club](https://boredapeyachtclub.com/) जैसे NFT पहल एथेरियम ब्लॉकचैन पर डेटा स्टोर करें, जिससे ब्लॉकचैन से सीधे बुनियादी डेटा के अलावा कुछ भी पढ़ना मुश्किल हो जाता है।
+जटिल स्मार्ट कॉन्ट्रैक्ट्स वाले प्रोजेक्ट्स, जैसे [Uniswap](https://uniswap.org/) और NFT इनिशिएटिव्स जैसे [Bored Ape Yacht Club](https://boredapeyachtclub.com/), डेटा को एथेरियम ब्लॉकचेन पर स्टोर करते हैं, जिससे ब्लॉकचेन से सीधे मूलभूत डेटा के अलावा किसी अन्य जानकारी को पढ़ना बहुत कठिन हो जाता है।
 
-In the case of Bored Ape Yacht Club, we can perform basic read operations on [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) like getting the owner of a certain Ape, getting the content URI of an Ape based on their ID, or the total supply. This can be done because these read operations are programmed directly into the smart contract. However, more advanced real-world queries and operations like aggregation, search, relationships, and non-trivial filtering are _not_ possible. For example, if we wanted to query for Apes that are owned by a certain address and filter by one of its characteristics, we would not be able to get that information by interacting directly with the contract itself.
+### The Graph के बिना चुनौतियाँ
 
-To get this 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. It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+उदाहरण के रूप में, Bored Ape Yacht Club के मामले में, आप [the contract](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code) पर बुनियादी रीड ऑपरेशन कर सकते हैं। आप किसी विशेष एपी के मालिक को पढ़ सकते हैं, एपी के ID के आधार पर कंटेंट URI पढ़ सकते हैं, या कुल आपूर्ति को पढ़ सकते हैं।
 
-आप अपना स्वयं का सर्वर भी बना सकते हैं, लेनदेन को वहां संसाधित कर सकते हैं, उन्हें डेटाबेस में सहेज सकते हैं, और डेटा को क्वेरी करने के लिए इन सबसे ऊपर एक एपीआई एंडपॉइंट बना सकते हैं। हालाँकि, यह विकल्प संसाधन गहन है, रखरखाव की आवश्यकता है, विफलता का एक बिंदु प्रस्तुत करता है, और विकेंद्रीकरण के लिए आवश्यक महत्वपूर्ण सुरक्षा गुणों को तोड़ता है।
+- यह संभव है क्योंकि ये पढ़ाई संचालन सीधे स्मार्ट कॉन्ट्रैक्ट में प्रोग्राम किए गए हैं। हालांकि, अधिक उन्नत, विशिष्ट और वास्तविक दुनिया की क्वेरीज़ और संचालन जैसे कि एग्रीगेशन, सर्च, रिलेशनशिप, और जटिल फ़िल्टरिंग, **संभव नहीं हैं**।
 
-**ब्लॉकचेन डेटा को इंडेक्स करना वास्तव में कठिन है।**
+- उदाहरण के लिए, यदि आप किसी विशेष पते द्वारा स्वामित्व वाले Apes के बारे में पूछताछ करना चाहते हैं और किसी विशेष विशेषता के आधार पर अपनी खोज को परिष्कृत करना चाहते हैं, तो आप यह जानकारी सीधे कॉन्ट्रैक्ट के साथ बातचीत करके प्राप्त नहीं कर पाएंगे।
 
-Blockchain properties like finality, chain reorganizations, or uncled blocks complicate this process further. They make it time consuming and conceptually hard to retrieve correct query results from blockchain data.
+- ज्यादा डेटा प्राप्त करने के लिए, आपको हर एक [`transfer`](https://etherscan.io/address/0xbc4ca0eda7647a8ab7c2061c2e118a18a936f13d#code#L1746) इवेंट को प्रोसेस करना होगा, IPFS से Token ID और IPFS हैश का उपयोग करके मेटाडेटा पढ़ना होगा, और फिर उसे संक्षिप्त करना होगा।
 
-The Graph provides a solution 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. Today, there is a hosted service as well as a decentralized protocol with the same capabilities. Both are backed by the open source implementation of [Graph Node](https://github.com/graphprotocol/graph-node).
+### यह एक समस्या क्यों है?
 
-## ग्राफ कैसे काम करता है
+यह सरल सवालों का जवाब पाने में एक ब्राउज़र में चल रही एक विकेन्द्रीकृत एप्लिकेशन (dapp) को **घंटे या यहाँ तक कि दिन** लग सकते हैं।
 
-ग्राफ सीखता है कि सबग्राफ विवरण के आधार पर एथेरियम डेटा को क्या और कैसे अनुक्रमित किया जाए, जिसे सबग्राफ मेनिफेस्ट के रूप में जाना जाता है। सबग्राफ विवरण एक सबग्राफ के लिए ब्याज के स्मार्ट अनुबंधों को परिभाषित करता है, उन अनुबंधों की घटनाओं पर ध्यान देना है, और इवेंट डेटा को उस डेटा से कैसे मैप करना है जिसे ग्राफ़ अपने डेटाबेस में संग्रहीत करेगा।
+वैकल्पिक रूप से, आपके पास अपना स्वयं का सर्वर सेट अप करने, लेनदेन को प्रोसेस करने, उन्हें एक डेटाबेस में स्टोर करने, और डेटा को क्वेरी करने के लिए एक API एन्डपॉइंट बनाने का विकल्प है। हालांकि, यह विकल्प [संसाधन-संवेदनशील](/network/benefits/) है, रखरखाव की आवश्यकता होती है, एकल विफलता बिंदु प्रस्तुत करता है, और विकेंद्रीकरण के लिए आवश्यक महत्वपूर्ण सुरक्षा गुणों को तोड़ता है।
 
-एक बार जब आप `सबग्राफ मेनिफेस्ट` लिख लेते हैं, तो आप IPFS में परिभाषा को स्टोर करने के लिए ग्राफ़ सीएलआई का उपयोग करते हैं और इंडेक्सर को उस सबग्राफ के लिए इंडेक्सिंग डेटा शुरू करने के लिए कहते हैं।
+ब्लॉकचेन की विशेषताएँ, जैसे अंतिमता, चेन पुनर्गठन, और अंकल ब्लॉक्स, प्रक्रिया में जटिलता जोड़ती हैं, जिससे ब्लॉकचेन डेटा से सटीक क्वेरी परिणाम प्राप्त करना समय लेने वाला और अवधारणात्मक रूप से चुनौतीपूर्ण हो जाता है।
 
-एथेरियम लेनदेन से निपटने के लिए, एक बार सबग्राफ मेनिफेस्ट तैनात किए जाने के बाद, यह आरेख डेटा के प्रवाह के बारे में अधिक विवरण देता है:
+## The Graph  एक समाधान प्रदान करता है
+
+The Graph इस चुनौती को एक विकेन्द्रीकृत प्रोटोकॉल के माध्यम से हल करता है जो ब्लॉकचेन डेटा को इंडेक्स करता है और उसकी कुशल और उच्च-प्रदर्शन वाली क्वेरी करने की सुविधा प्रदान करता है। ये एपीआई (इंडेक्स किए गए "सबग्राफ") फिर एक मानक GraphQL एपीआई के साथ क्वेरी की जा सकती हैं।
+
+आज एक विकेंद्रीकृत प्रोटोकॉल है, जो [Graph Node](https://github.com/graphprotocol/graph-node) के ओपन सोर्स इम्प्लीमेंटेशन द्वारा समर्थित है, जो इस प्रक्रिया को सक्षम बनाता है।
+
+### The Graph कैसे काम करता है
+
+ब्लॉकचेन डेटा को इंडेक्स करना बहुत मुश्किल होता है, लेकिन The Graph इसे आसान बना देता है। The Graph सबग्राफ्स का उपयोग करके एथेरियम डेटा को इंडेक्स करना सीखता है। सबग्राफ्स ब्लॉकचेन डेटा पर बनाए गए कस्टम एपीआई होते हैं, जो ब्लॉकचेन से डेटा निकालते हैं, उसे प्रोसेस करते हैं, और उसे इस तरह स्टोर करते हैं ताकि उसे GraphQL के माध्यम से आसानी से क्वेरी किया जा सके।
+
+#### विशिष्टताएँ
+
+- The Graph का उपयोग subgraph विवरणों के लिए करता है, जिन्हें subgraph के अंदर subgraph manifest के रूप में जाना जाता है।
+
+- सबग्राफ विवरण उन स्मार्ट कॉन्ट्रैक्ट्स की रूपरेखा प्रदान करता है जो एक सबग्राफ के लिए महत्वपूर्ण हैं, उन कॉन्ट्रैक्ट्स के भीतर कौन-कौन सी घटनाओं पर ध्यान केंद्रित करना है, और घटना डेटा को उस डेटा से कैसे मैप करना है जिसे The Graph अपने डेटाबेस में संग्रहीत करेगा।
+
+- जब आप एक subgraph बना रहे होते हैं, तो आपको एक subgraph मैनिफेस्ट लिखने की आवश्यकता होती है।
+
+- `Subgraph manifest` लिखने के बाद, आप Graph CLI का उपयोग करके परिभाषा को IPFS में संग्रहीत कर सकते हैं और एक Indexer को उस subgraph के लिए डेटा को इंडेक्स करने का निर्देश दे सकते हैं।
+
+नीचे दिया गया आरेख Ethereum लेनदेन के साथ subgraph मैनिफेस्ट को डिप्लॉय करने के बाद डेटा के प्रवाह के बारे में अधिक विस्तृत जानकारी प्रदान करता है।
 
 ![एक ग्राफ़िक समझाता है कि कैसे ग्राफ़ डेटा उपभोक्ताओं को क्वेरीज़ प्रदान करने के लिए ग्राफ़ नोड का उपयोग करता है](/img/graph-dataflow.png)
 
 प्रवाह इन चरणों का पालन करता है:
 
-1. एक विकेंद्रीकृत एप्लिकेशन स्मार्ट अनुबंध पर लेनदेन के माध्यम से एथेरियम में डेटा जोड़ता है।
-2. लेन-देन संसाधित करते समय स्मार्ट अनुबंध एक या अधिक घटनाओं का उत्सर्जन करता है।
-3. ग्राफ़ नोड लगातार नए ब्लॉकों के लिए एथेरियम को स्कैन करता है और आपके सबग्राफ के डेटा में शामिल हो सकता है।
-4. ग्राफ नोड इन ब्लॉकों में आपके सबग्राफ के लिए एथेरियम ईवेंट ढूंढता है और आपके द्वारा प्रदान किए गए मैपिंग हैंडलर को चलाता है। मैपिंग एक WASM मॉड्यूल है जो एथेरियम घटनाओं के जवाब में ग्राफ़ नोड द्वारा संग्रहीत डेटा संस्थाओं को बनाता या अपडेट करता है।
-5. नोड के [GraphQL समापन बिंदु](https://graphql.org/learn/) का उपयोग करते हुए, विकेन्द्रीकृत एप्लिकेशन ब्लॉकचैन से अनुक्रमित डेटा के लिए ग्राफ़ नोड से पूछताछ करता है। ग्राफ़ नोड बदले में इस डेटा को प्राप्त करने के लिए, स्टोर की इंडेक्सिंग क्षमताओं का उपयोग करते हुए, अपने अंतर्निहित डेटा स्टोर के लिए ग्राफ़कॉल प्रश्नों का अनुवाद करता है। विकेंद्रीकृत एप्लिकेशन इस डेटा को एंड-यूजर्स के लिए एक समृद्ध यूआई में प्रदर्शित करता है, जिसका उपयोग वे एथेरियम पर नए लेनदेन जारी करने के लिए करते हैं। चक्र दोहराता है।
+1.  एक विकेंद्रीकृत एप्लिकेशन स्मार्ट अनुबंध पर लेनदेन के माध्यम से एथेरियम में डेटा जोड़ता है।
+2.  लेन-देन संसाधित करते समय स्मार्ट अनुबंध एक या अधिक घटनाओं का उत्सर्जन करता है।
+3.  ग्राफ़ नोड लगातार नए ब्लॉकों के लिए एथेरियम को स्कैन करता है और आपके सबग्राफ के डेटा में शामिल हो सकता है।
+4.  ग्राफ नोड इन ब्लॉकों में आपके सबग्राफ के लिए एथेरियम ईवेंट ढूंढता है और आपके द्वारा प्रदान किए गए मैपिंग हैंडलर को चलाता है। मैपिंग एक WASM मॉड्यूल है जो एथेरियम घटनाओं के जवाब में ग्राफ़ नोड द्वारा संग्रहीत डेटा संस्थाओं को बनाता या अपडेट करता है।
+5.  नोड के [GraphQL समापन बिंदु](https://graphql.org/learn/) का उपयोग करते हुए, विकेन्द्रीकृत एप्लिकेशन ब्लॉकचैन से अनुक्रमित डेटा के लिए ग्राफ़ नोड से पूछताछ करता है। ग्राफ़ नोड बदले में इस डेटा को प्राप्त करने के लिए, स्टोर की इंडेक्सिंग क्षमताओं का उपयोग करते हुए, अपने अंतर्निहित डेटा स्टोर के लिए ग्राफ़कॉल प्रश्नों का अनुवाद करता है। विकेंद्रीकृत एप्लिकेशन इस डेटा को एंड-यूजर्स के लिए एक समृद्ध यूआई में प्रदर्शित करता है, जिसका उपयोग वे एथेरियम पर नए लेनदेन जारी करने के लिए करते हैं। चक्र दोहराता है।
 
 ## अगले कदम
 
-The following sections provide more detail on how to define subgraphs, how to deploy them, and how to query data from the indexes that Graph Node builds.
+निम्नलिखित अनुभागों में subgraphs, उनके डिप्लॉयमेंट और डेटा क्वेरी करने के तरीके पर अधिक गहराई से जानकारी दी गई है।
 
-Before you start writing your own subgraph, you might want to have a look at [Graph Explorer](https://thegraph.com/explorer) and explore some of the subgraphs that have already been deployed. The page for each subgraph contains a playground that lets you query that subgraph's data with GraphQL.
+अपना खुद का subgraph लिखने से पहले, यह अनुशंसा की जाती है कि आप [Graph Explorer](https://thegraph.com/explorer) को एक्सप्लोर करें और पहले से डिप्लॉय किए गए कुछ subgraphs की समीक्षा करें। प्रत्येक subgraph के पेज में एक GraphQL प्लेग्राउंड शामिल होता है, जिससे आप उसके डेटा को क्वेरी कर सकते हैं।

From a80b85e229d80b53429cc1661021459b58d2f39d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:49 -0500
Subject: [PATCH 0359/1325] New translations near.mdx (Hindi)

---
 website/pages/hi/cookbook/near.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/hi/cookbook/near.mdx b/website/pages/hi/cookbook/near.mdx
index bfa199f5c2bb..6ffcaca61696 100644
--- a/website/pages/hi/cookbook/near.mdx
+++ b/website/pages/hi/cookbook/near.mdx
@@ -37,7 +37,7 @@ NEAR सबग्राफ डेवलपमेंट के लिए `graph-c
 
 **schema.graphql:** एक स्कीमा फ़ाइल जो परिभाषित करती है कि आपके सबग्राफ के लिए कौन सा डेटा इकट्ठा होगा, और इसे ग्राफ़क्यूएल के माध्यम से कैसे क्वेरी करें। NEAR सबग्राफ की आवश्यकताएं [मौजूदा दस्तावेज़ीकरण](/Developing/creating-a-subgraph#the-graphql-schema) द्वारा कवर की गई हैं।
 
-**असेंबलीस्क्रिप्ट मैपिंग:** [असेंबलीस्क्रिप्ट कोड](/developing/graph-ts/api) जो इवेंट डेटा से आपके स्कीमा में परिभाषित इकाइयों में अनुवाद करता है। NEAR समर्थन NEAR-विशिष्ट डेटा प्रकारों और नई JSON पार्सिंग कार्यक्षमता का परिचय देता है।
+**AssemblyScript मापिंग:** [AssemblyScript कोड](/developing/graph-ts/api) जो घटना डेटा को आपकी स्कीमा में परिभाषित संस्थाओं में अनुवादित करता है। NEAR समर्थन NEAR-विशिष्ट डेटा प्रकार और नई JSON पार्सिंग कार्यक्षमता पेश करता है।
 
 सबग्राफ डेवलपमेंट के दौरान दो प्रमुख कमांड होते हैं:
 
@@ -98,7 +98,7 @@ NEAR डेटा स्रोत दो प्रकार के हैंड
 
 इवेंट को प्रोसेस करने के लिए हैंडलर [AssemblyScript](https://www.assemblyscript.org/) में लिखे होते हैं।
 
-NEAR इंडेक्सिंग [AssemblyScript API](/developing/graph-ts/api) के लिए NEAR-विशिष्ट डेटा प्रकारों का परिचय देता है।
+NEAR indexing 'NEAR' के लिए विशिष्ट डेटा प्रकारों को [AssemblyScript API](/developing/graph-ts/api) में पेश करता है।
 
 ```typescript
 
@@ -165,9 +165,9 @@ class ReceiptWithOutcome {
 - ब्लॉक हैंडलर्स को एक `ब्लॉक` प्राप्त होगा
 - रसीद संचालकों को `ReceiptWithOutcome` प्राप्त होगा
 
-अन्यथा, शेष [AssemblyScript API](/developing/graph-ts/api) मैपिंग निष्पादन के दौरान NEAR सबग्राफ डेवलपर्स के लिए उपलब्ध है।
+अन्यथा, [AssemblyScript API](/developing/graph-ts/api) का शेष भाग NEAR subgraph डेवलपर्स के लिए मैपिंग निष्पादन के दौरान उपलब्ध है।
 
-इसमें एक नया JSON पार्सिंग फ़ंक्शन शामिल है - NEAR पर logs अक्सर stringified JSON के रूप में उत्सर्जित होते हैं। एक नया `json.fromString(...)` फ़ंक्शन [JSON API](/developing/graph-ts/api#json-api) के भाग के रूप में डेवलपर्स को अनुमति देने के लिए उपलब्ध है इन logs को आसानी से संसाधित करने के लिए।
+यह एक नई JSON पार्सिंग फ़ंक्शन को शामिल करता है - NEAR पर लॉग अक्सर स्ट्रिंगिफाइड JSONs के रूप में उत्पन्न होते हैं। एक नई `json.fromString(...)` फ़ंक्शन [JSON API](/developing/graph-ts/api#json-api) का हिस्सा के रूप में उपलब्ध है, जिससे डेवलपर्स इन लॉग्स को आसानी से प्रोसेस कर सकते हैं।
 
 ## एक NEAR सबग्राफ की तैनाती
 
@@ -194,8 +194,8 @@ $ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <su
 ### Subgraph Studio
 
 ```sh
-graph auth --studio
-graph deploy --studio <subgraph-name>
+graph auth
+graph deploy <subgraph-name>
 ```
 
 ### स्थानीय ग्राफ़ नोड (डिफ़ॉल्ट कॉन्फ़िगरेशन पर आधारित)

From 7a876c18d94c2e488f6c2ba88794cd341f2f06f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:50 -0500
Subject: [PATCH 0360/1325] New translations unit-testing-framework.mdx (Hindi)

---
 .../hi/developing/unit-testing-framework.mdx  | 49 ++++++++++++-------
 1 file changed, 31 insertions(+), 18 deletions(-)

diff --git a/website/pages/hi/developing/unit-testing-framework.mdx b/website/pages/hi/developing/unit-testing-framework.mdx
index ec23fbef4c88..e0ef7821aec7 100644
--- a/website/pages/hi/developing/unit-testing-framework.mdx
+++ b/website/pages/hi/developing/unit-testing-framework.mdx
@@ -2,23 +2,32 @@
 title: "Unit परीक्षण फ्रेमवर्क प्राप्त करना\nकला"
 ---
 
-माचिस एक इकाई परीक्षण ढांचा है, जिसे [LimeChain](https://limechain.tech/) द्वारा विकसित किया गया है, जो subgraph developers को sandboxed वाले वातावरण में अपने mapping तर्क का परीक्षण करने और आत्मविश्वास के साथ अपने subgraph तैनात करने में सक्षम बनाता है!
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
 
 ## शुरू करना
 
-### निर्भरताएँ स्थापित करें
+### Install Dependencies
 
-परीक्षण सहायक विधियों का उपयोग करने और परीक्षण चलाने के लिए, आपको निम्नलिखित निर्भरताओं को स्थापित करने की आवश्यकता होगी:
+In order to use the test helper methods and run tests, you need to install the following dependencies:
 
 ```sh
 yarn add --dev matchstick-as
 ```
 
-❗ `graph-node` PostgreSQL पर निर्भर करता है, इसलिए यदि आपके पास पहले से यह नहीं है, तो आपको इसे install करना होगा। हम अत्यधिक सलाह देते हैं कि नीचे दिए गए आदेशों का उपयोग करें क्योंकि इसे किसी अन्य तरीके से जोड़ने से अनपेक्षित त्रुटियां हो सकती हैं!
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
 
-#### MacOS
+#### Using MacOS
 
-पोस्टग्रेज इंस्टॉलेशन कमांड:
+Installation command:
 
 ```sh
 brew install postgresql
@@ -30,15 +39,15 @@ brew install postgresql
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
 ```
 
-#### Linux
+#### Using Linux
 
-पोस्टग्रेज इंस्टॉलेशन कमांड (आपके डिस्ट्रो पर निर्भर करता है):
+Installation command (depends on your distro):
 
 ```sh
 sudo apt install postgresql
 ```
 
-### WSL (लिनक्स के लिए विंडोज सबसिस्टम)
+### Using WSL (Windows Subsystem for Linux)
 
 कृपया ध्यान दें, आर्बिट्रम माइग्रेशन पूरा होने पर इसमें सुधार होगा, जिससे नेटवर्क पर भाग लेने के लिए गैस की लागत काफी कम हो जाएगी।...
 
@@ -76,7 +85,7 @@ sudo apt-get install libpq-dev
 }
 ```
 
-### प्रयोग
+### Using Matchstick
 
 अपने सबग्राफ प्रोजेक्ट में **माचिस** का उपयोग करने के लिए बस एक टर्मिनल खोलें, अपने प्रोजेक्ट के रूट फ़ोल्डर में नेविगेट करें और बस `ग्राफ़ टेस्ट [विकल्प] <डेटासोर्स> ` - यह नवीनतम **मैचस्टिक** बाइनरी को डाउनलोड करता है और एक परीक्षण फ़ोल्डर में निर्दिष्ट परीक्षण या सभी परीक्षण चलाता है (या सभी मौजूदा परीक्षण यदि कोई डेटा स्रोत ध्वज निर्दिष्ट नहीं है)।
 
@@ -411,7 +420,7 @@ describe('handleUpdatedGravatars', () => {
 
 उदाहरण:
 
-प्रत्येक परीक्षण के बाद `afterEach` के अंदर का कोड निष्पादित होगा।
+प्रत्येक परीक्षण के बाद ` afterEach ` के अंदर का कोड निष्पादित होगा।
 
 ```typescript
 import { describe, test, beforeEach, afterEach } from "matchstick-as/assembly/index"
@@ -450,7 +459,7 @@ describe("handleUpdatedGravatar", () => {
 })
 ```
 
-उस वर्णन में प्रत्येक परीक्षण के बाद `afterEach` के अंदर का कोड निष्पादित होगा
+उस वर्णन में प्रत्येक परीक्षण के बाद ` afterEach ` के अंदर का कोड निष्पादित होगा
 
 ```typescript
 import { describe, test, beforeEach, afterEach } from "matchstick-as/assembly/index"
@@ -1368,22 +1377,26 @@ Global test coverage: 22.2% (2/9 handlers).
 
 > गंभीर: संदर्भ के साथ मान्य मॉड्यूल से WasmInstance नहीं बना सका: अज्ञात आयात: wasi_snapshot_preview1::fd_write परिभाषित नहीं किया गया है
 
-इसका अर्थ है कि आपने अपने कोड में `console.log` का उपयोग किया है, जो कि असेंबलीस्क्रिप्ट द्वारा समर्थित नहीं है। कृपया [लॉगिंग API](/developing/graph-ts/api/#logging-api) का उपयोग करने पर विचार करें
+इसका मतलब है कि आपने अपने कोड में ``console.log`\` का उपयोग किया है, जिसे AssemblyScript द्वारा सपोर्ट नहीं किया जाता है। कृपया [Logging API](/developing/graph-ts/api/#logging-api) का उपयोग करने पर विचार करें।
 
 > त्रुटि TS2554: अपेक्षित? तर्क, लेकिन मिला ?.
->
+> 
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
->
+> 
 > त्रुटि TS2554: अपेक्षित? तर्क, लेकिन मिला ?.
->
+> 
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
->
+> 
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 तर्कों में बेमेल `ग्राफ़-टीएस` और `मैचस्टिक-एज़` में बेमेल होने के कारण होता है। इस तरह की समस्याओं को ठीक करने का सबसे अच्छा तरीका है कि सभी चीज़ों को नवीनतम रिलीज़ किए गए संस्करण में अपडेट कर दिया जाए.
 
+## अतिरिक्त संसाधन
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
 ## प्रतिक्रिया
 
 यदि आपके पास कोई प्रश्न, प्रतिक्रिया, फीचर अनुरोध है या आप बस पहुंचना चाहते हैं, तो सबसे अच्छी जगह द ग्राफ डिस्कॉर्ड होगी जहां हमारे पास मैचस्टिक के लिए एक समर्पित चैनल है, जिसे 🔥 कहा जाता है| इकाई का परीक्षण।

From 302d466d93a003c743e102250b12e5d79ccdc702 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:51 -0500
Subject: [PATCH 0361/1325] New translations index.json (Swahili)

---
 website/pages/sw/index.json | 67 +++++++++++++++++++++++++++++++++++++
 1 file changed, 67 insertions(+)
 create mode 100644 website/pages/sw/index.json

diff --git a/website/pages/sw/index.json b/website/pages/sw/index.json
new file mode 100644
index 000000000000..7b5de0b796fd
--- /dev/null
+++ b/website/pages/sw/index.json
@@ -0,0 +1,67 @@
+{
+  "title": "Get Started",
+  "intro": "Learn about The Graph, a decentralized protocol for indexing and querying data from blockchains.",
+  "shortcuts": {
+    "aboutTheGraph": {
+      "title": "About The Graph",
+      "description": "Learn more about The Graph"
+    },
+    "quickStart": {
+      "title": "Quick Start",
+      "description": "Jump in and start with The Graph"
+    },
+    "developerFaqs": {
+      "title": "Developer FAQs",
+      "description": "Frequently asked questions"
+    },
+    "queryFromAnApplication": {
+      "title": "Query from an Application",
+      "description": "Learn to query from an application"
+    },
+    "createASubgraph": {
+      "title": "Create a Subgraph",
+      "description": "Use Studio to create subgraphs"
+    }
+  },
+  "networkRoles": {
+    "title": "Network Roles",
+    "description": "Learn about The Graph’s network roles.",
+    "roles": {
+      "developer": {
+        "title": "Developer",
+        "description": "Create a subgraph or use existing subgraphs in a dapp"
+      },
+      "indexer": {
+        "title": "Indexer",
+        "description": "Operate a node to index data and serve queries"
+      },
+      "curator": {
+        "title": "Curator",
+        "description": "Organize data by signaling on subgraphs"
+      },
+      "delegator": {
+        "title": "Delegator",
+        "description": "Secure the network by delegating GRT to Indexers"
+      }
+    }
+  },
+  "readMore": "Read more",
+  "products": {
+    "title": "Products",
+    "products": {
+      "subgraphStudio": {
+        "title": "Subgraph Studio",
+        "description": "Create, manage and publish subgraphs and API keys"
+      },
+      "graphExplorer": {
+        "title": "Graph Explorer",
+        "description": "Explore subgraphs and interact with the protocol"
+      }
+    }
+  },
+  "supportedNetworks": {
+    "title": "Supported Networks",
+    "description": "The Graph supports the following networks.",
+    "footer": "For more details, see the {0} page."
+  }
+}

From 8c1f6d3201d2d89fe1325dec34caf4038b97b287 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:53 -0500
Subject: [PATCH 0362/1325] New translations about.mdx (Swahili)

---
 website/pages/sw/about.mdx | 67 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 67 insertions(+)
 create mode 100644 website/pages/sw/about.mdx

diff --git a/website/pages/sw/about.mdx b/website/pages/sw/about.mdx
new file mode 100644
index 000000000000..9c21bf00d08f
--- /dev/null
+++ b/website/pages/sw/about.mdx
@@ -0,0 +1,67 @@
+---
+title: About The Graph
+---
+
+## What is The Graph?
+
+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
+
+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.
+
+### Challenges Without The Graph
+
+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.
+
+- 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**.
+
+- 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.
+
+- 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.
+
+### Why is this a problem?
+
+It would take **hours or even days** for a decentralized application (dapp) running in a browser to get an answer to these simple questions.
+
+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](/network/benefits/), needs maintenance, presents a single point of failure, and breaks important security properties required for decentralization.
+
+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.
+
+## The Graph Provides a Solution
+
+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.
+
+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.
+
+### How The Graph Functions
+
+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.
+
+#### 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.
+
+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.

From dda9ae479f999b643090bf6906c0f9a8337cd64e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:54 -0500
Subject: [PATCH 0363/1325] New translations near.mdx (Swahili)

---
 website/pages/sw/cookbook/near.mdx | 283 +++++++++++++++++++++++++++++
 1 file changed, 283 insertions(+)
 create mode 100644 website/pages/sw/cookbook/near.mdx

diff --git a/website/pages/sw/cookbook/near.mdx b/website/pages/sw/cookbook/near.mdx
new file mode 100644
index 000000000000..f2509e44e84c
--- /dev/null
+++ b/website/pages/sw/cookbook/near.mdx
@@ -0,0 +1,283 @@
+---
+title: Building Subgraphs on NEAR
+---
+
+This guide is an introduction to building subgraphs indexing smart contracts on the [NEAR blockchain](https://docs.near.org/).
+
+## What is NEAR?
+
+[NEAR](https://near.org/) is a smart contract platform for building decentralized applications. Visit the [official documentation](https://docs.near.org/concepts/basics/protocol) for more information.
+
+## What are NEAR subgraphs?
+
+The Graph gives developers tools to process blockchain events and make the resulting data easily available via a GraphQL API, known individually as a subgraph. [Graph Node](https://github.com/graphprotocol/graph-node) is now able to process NEAR events, which means that NEAR developers can now build subgraphs to index their smart contracts.
+
+Subgraphs are event-based, which means that they listen for and then process on-chain events. There are currently two types of handlers supported for NEAR subgraphs:
+
+- Block handlers: these are run on every new block
+- Receipt handlers: run every time a message is executed at a specified account
+
+[From the NEAR documentation](https://docs.near.org/build/data-infrastructure/lake-data-structures/receipt):
+
+> A Receipt is the only actionable object in the system. When we talk about "processing a transaction" on the NEAR platform, this eventually means "applying receipts" at some point.
+
+## Building a NEAR Subgraph
+
+`@graphprotocol/graph-cli` is a command-line tool for building and deploying subgraphs.
+
+`@graphprotocol/graph-ts` is a library of subgraph-specific types.
+
+NEAR subgraph development requires `graph-cli` above version `0.23.0`, and `graph-ts` above version `0.23.0`.
+
+> Building a NEAR subgraph is very similar to building a subgraph that indexes Ethereum.
+
+There are three aspects of subgraph definition:
+
+**subgraph.yaml:** the subgraph manifest, defining the data sources of interest, and how they should be processed. NEAR is a new `kind` of data source.
+
+**schema.graphql:** a schema file that defines what data is stored for your subgraph, and how to query it via GraphQL. The requirements for NEAR subgraphs are covered by [the existing documentation](/developing/creating-a-subgraph#the-graphql-schema).
+
+**AssemblyScript Mappings:** [AssemblyScript code](/developing/graph-ts/api) that translates from the event data to the entities defined in your schema. NEAR support introduces NEAR-specific data types and new JSON parsing functionality.
+
+During subgraph development there are two key commands:
+
+```bash
+$ graph codegen # generates types from the schema file identified in the manifest
+$ graph build # generates Web Assembly from the AssemblyScript files, and prepares all the subgraph files in a /build folder
+```
+
+### Subgraph Manifest Definition
+
+The subgraph manifest (`subgraph.yaml`) identifies the data sources for the subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example subgraph manifest for a NEAR subgraph:
+
+```yaml
+specVersion: 0.0.2
+schema:
+  file: ./src/schema.graphql # link to the schema file
+dataSources:
+  - kind: near
+    network: near-mainnet
+    source:
+      account: app.good-morning.near # This data source will monitor this account
+      startBlock: 10662188 # Required for NEAR
+    mapping:
+      apiVersion: 0.0.5
+      language: wasm/assemblyscript
+      blockHandlers:
+        - handler: handleNewBlock # the function name in the mapping file
+      receiptHandlers:
+        - handler: handleReceipt # the function name in the mapping file
+      file: ./src/mapping.ts # link to the file with the Assemblyscript mappings
+```
+
+- NEAR subgraphs introduce a new `kind` of data source (`near`)
+- The `network` should correspond to a network on the hosting Graph Node. On Subgraph Studio, NEAR's mainnet is `near-mainnet`, and NEAR's testnet is `near-testnet`
+- NEAR data sources introduce an optional `source.account` field, which is a human-readable ID corresponding to a [NEAR account](https://docs.near.org/concepts/protocol/account-model). This can be an account or a sub-account.
+- NEAR data sources introduce an alternative optional `source.accounts` field, which contains optional suffixes and prefixes. At least prefix or suffix must be specified, they will match the any account starting or ending with the list of values respectively. The example below would match: `[app|good].*[morning.near|morning.testnet]`. If only a list of prefixes or suffixes is necessary the other field can be omitted.
+
+```yaml
+accounts:
+  prefixes:
+    - app
+    - good
+  suffixes:
+    - morning.near
+    - morning.testnet
+```
+
+NEAR data sources support two types of handlers:
+
+- `blockHandlers`: run on every new NEAR block. No `source.account` is required.
+- `receiptHandlers`: run on every receipt where the data source's `source.account` is the recipient. Note that only exact matches are processed ([subaccounts](https://docs.near.org/tutorials/crosswords/basics/add-functions-call#create-a-subaccount) must be added as independent data sources).
+
+### Schema Definition
+
+Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph#the-graphql-schema).
+
+### AssemblyScript Mappings
+
+The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/).
+
+NEAR indexing introduces NEAR-specific data types to the [AssemblyScript API](/developing/graph-ts/api).
+
+```typescript
+
+class ExecutionOutcome {
+      gasBurnt: u64,
+      blockHash: Bytes,
+      id: Bytes,
+      logs: Array<string>,
+      receiptIds: Array<Bytes>,
+      tokensBurnt: BigInt,
+      executorId: string,
+  }
+
+class ActionReceipt {
+      predecessorId: string,
+      receiverId: string,
+      id: CryptoHash,
+      signerId: string,
+      gasPrice: BigInt,
+      outputDataReceivers: Array<DataReceiver>,
+      inputDataIds: Array<CryptoHash>,
+      actions: Array<ActionValue>,
+  }
+
+class BlockHeader {
+      height: u64,
+      prevHeight: u64,// Always zero when version < V3
+      epochId: Bytes,
+      nextEpochId: Bytes,
+      chunksIncluded: u64,
+      hash: Bytes,
+      prevHash: Bytes,
+      timestampNanosec: u64,
+      randomValue: Bytes,
+      gasPrice: BigInt,
+      totalSupply: BigInt,
+      latestProtocolVersion: u32,
+  }
+
+class ChunkHeader {
+      gasUsed: u64,
+      gasLimit: u64,
+      shardId: u64,
+      chunkHash: Bytes,
+      prevBlockHash: Bytes,
+      balanceBurnt: BigInt,
+  }
+
+class Block {
+      author: string,
+      header: BlockHeader,
+      chunks: Array<ChunkHeader>,
+  }
+
+class ReceiptWithOutcome {
+      outcome: ExecutionOutcome,
+      receipt: ActionReceipt,
+      block: Block,
+  }
+```
+
+These types are passed to block & receipt handlers:
+
+- Block handlers will receive a `Block`
+- Receipt handlers will receive a `ReceiptWithOutcome`
+
+Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
+
+This includes a new JSON parsing function - logs on NEAR are frequently emitted as stringified JSONs. A new `json.fromString(...)` function is available as part of the [JSON API](/developing/graph-ts/api#json-api) to allow developers to easily process these logs.
+
+## Deploying a NEAR Subgraph
+
+Once you have a built subgraph, it is time to deploy it to Graph Node for indexing. NEAR subgraphs can be deployed to any Graph Node `>=v0.26.x` (this version has not yet been tagged & released).
+
+Subgraph Studio and the upgrade Indexer on The Graph Network currently supports indexing NEAR mainnet and testnet in beta, with the following network names:
+
+- `near-mainnet`
+- `near-testnet`
+
+More information on creating and deploying subgraphs on Subgraph Studio can be found [here](/deploying/deploying-a-subgraph-to-studio).
+
+As a quick primer - the first step is to "create" your subgraph - this only needs to be done once. On Subgraph Studio, this can be done from [your Dashboard](https://thegraph.com/studio/): "Create a subgraph".
+
+Once your subgraph has been created, you can deploy your subgraph by using the `graph deploy` CLI command:
+
+```sh
+$ graph create --node <graph-node-url> <subgraph-name> # creates a subgraph on a local Graph Node (on Subgraph Studio, this is done via the UI)
+$ graph deploy --node <graph-node-url> --ipfs https://api.thegraph.com/ipfs/ <subgraph-name> # uploads the build files to a specified IPFS endpoint, and then deploys the subgraph to a specified Graph Node based on the manifest IPFS hash
+```
+
+The node configuration will depend on where the subgraph is being deployed.
+
+### Subgraph Studio
+
+```sh
+graph auth
+graph deploy <subgraph-name>
+```
+
+### Local Graph Node (based on default configuration)
+
+```sh
+graph deploy --node http://localhost:8020/ --ipfs http://localhost:5001 <subgraph-name>
+```
+
+Once your subgraph has been deployed, it will be indexed by Graph Node. You can check its progress by querying the subgraph itself:
+
+```graphql
+{
+  _meta {
+    block {
+      number
+    }
+  }
+}
+```
+
+### Indexing NEAR with a Local Graph Node
+
+Running a Graph Node that indexes NEAR has the following operational requirements:
+
+- NEAR Indexer Framework with Firehose instrumentation
+- NEAR Firehose Component(s)
+- Graph Node with Firehose endpoint configured
+
+We will provide more information on running the above components soon.
+
+## Querying a NEAR Subgraph
+
+The GraphQL endpoint for NEAR subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api) for more information.
+
+## Example Subgraphs
+
+Here are some example subgraphs for reference:
+
+[NEAR Blocks](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-blocks)
+
+[NEAR Receipts](https://github.com/graphprotocol/graph-tooling/tree/main/examples/near-receipts)
+
+## FAQ
+
+### How does the beta work?
+
+NEAR support is in beta, which means that there may be changes to the API as we continue to work on improving the integration. Please email near@thegraph.com so that we can support you in building NEAR subgraphs, and keep you up to date on the latest developments!
+
+### Can a subgraph index both NEAR and EVM chains?
+
+No, a subgraph can only support data sources from one chain/network.
+
+### Can subgraphs react to more specific triggers?
+
+Currently, only Block and Receipt triggers are supported. We are investigating triggers for function calls to a specified account. We are also interested in supporting event triggers, once NEAR has native event support.
+
+### Will receipt handlers trigger for accounts and their sub-accounts?
+
+If an `account` is specified, that will only match the exact account name. It is possible to match sub-accounts by specifying an `accounts` field, with `suffixes` and `prefixes` specified to match accounts and sub-accounts, for example the following would match all `mintbase1.near` sub-accounts:
+
+```yaml
+accounts:
+  suffixes:
+    - mintbase1.near
+```
+
+### Can NEAR subgraphs make view calls to NEAR accounts during mappings?
+
+This is not supported. We are evaluating whether this functionality is required for indexing.
+
+### Can I use data source templates in my NEAR subgraph?
+
+This is not currently supported. We are evaluating whether this functionality is required for indexing.
+
+### Ethereum subgraphs support "pending" and "current" versions, how can I deploy a "pending" version of a NEAR subgraph?
+
+Pending functionality is not yet supported for NEAR subgraphs. In the interim, you can deploy a new version to a different "named" subgraph, and then when that is synced with the chain head, you can redeploy to your primary "named" subgraph, which will use the same underlying deployment ID, so the main subgraph will be instantly synced.
+
+### My question hasn't been answered, where can I get more help building NEAR subgraphs?
+
+If it is a general question about subgraph development, there is a lot more information in the rest of the [Developer documentation](/quick-start). Otherwise please join [The Graph Protocol Discord](https://discord.gg/graphprotocol) and ask in the #near channel or email near@thegraph.com.
+
+## References
+
+- [NEAR developer documentation](https://docs.near.org/tutorials/crosswords/basics/set-up-skeleton)

From 0147f7dbc2a46a54bf8b9c092ab3ef04ec4db956 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:55 -0500
Subject: [PATCH 0364/1325] New translations unit-testing-framework.mdx
 (Swahili)

---
 .../sw/developing/unit-testing-framework.mdx  | 1402 +++++++++++++++++
 1 file changed, 1402 insertions(+)
 create mode 100644 website/pages/sw/developing/unit-testing-framework.mdx

diff --git a/website/pages/sw/developing/unit-testing-framework.mdx b/website/pages/sw/developing/unit-testing-framework.mdx
new file mode 100644
index 000000000000..53a5c43dedcf
--- /dev/null
+++ b/website/pages/sw/developing/unit-testing-framework.mdx
@@ -0,0 +1,1402 @@
+---
+title: Unit Testing Framework
+---
+
+Learn how to use Matchstick, a unit testing framework developed by [LimeChain](https://limechain.tech/). Matchstick enables subgraph developers to test their mapping logic in a sandboxed environment and sucessfully deploy their subgraphs.
+
+## Benefits of Using Matchstick
+
+- It's written in Rust and optimized for high performance.
+- It gives you access to developer features, including the ability to mock contract calls, make assertions about the store state, monitor subgraph failures, check test performance, and many more.
+
+## Getting Started
+
+### Install Dependencies
+
+In order to use the test helper methods and run tests, you need to install the following dependencies:
+
+```sh
+yarn add --dev matchstick-as
+```
+
+### Install PostgreSQL
+
+`graph-node` depends on PostgreSQL, so if you don't already have it, then you will need to install it.
+
+> Note: It's highly recommended to use the commands below to avoid unexpected errors.
+
+#### Using MacOS
+
+Installation command:
+
+```sh
+brew install postgresql
+```
+
+Create a symlink to the latest libpq.5.lib _You may need to create this dir first_ `/usr/local/opt/postgresql/lib/`
+
+```sh
+ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
+```
+
+#### Using Linux
+
+Installation command (depends on your distro):
+
+```sh
+sudo apt install postgresql
+```
+
+### Using WSL (Windows Subsystem for Linux)
+
+You can use Matchstick on WSL both using the Docker approach and the binary approach. As WSL can be a bit tricky, here's a few tips in case you encounter issues like
+
+```
+static BYTES = Symbol("Bytes") SyntaxError: Unexpected token =
+```
+
+or
+
+```
+<PROJECT_PATH>/node_modules/gluegun/build/index.js:13 throw up;
+```
+
+Please make sure you're on a newer version of Node.js graph-cli doesn't support **v10.19.0** anymore, and that is still the default version for new Ubuntu images on WSL. For instance Matchstick is confirmed to be working on WSL with **v18.1.0**, you can switch to it either via **nvm** or if you update your global Node.js. Don't forget to delete `node_modules` and to run `npm install` again after updating you nodejs! Then, make sure you have **libpq** installed, you can do that by running
+
+```
+sudo apt-get install libpq-dev
+```
+
+And finally, do not use `graph test` (which uses your global installation of graph-cli and for some reason that looks like it's broken on WSL currently), instead use `yarn test` or `npm run test` (that will use the local, project-level instance of graph-cli, which works like a charm). For that you would of course need to have a `"test"` script in your `package.json` file which can be something as simple as
+
+```json
+{
+  "name": "demo-subgraph",
+  "version": "0.1.0",
+  "scripts": {
+    "test": "graph test",
+    ...
+  },
+  "dependencies": {
+    "@graphprotocol/graph-cli": "^0.56.0",
+    "@graphprotocol/graph-ts": "^0.31.0",
+    "matchstick-as": "^0.6.0"
+  }
+}
+```
+
+### Using Matchstick
+
+To use **Matchstick** in your subgraph project just open up a terminal, navigate to the root folder of your project and simply run `graph test [options] <datasource>` - it downloads the latest **Matchstick** binary and runs the specified test or all tests in a test folder (or all existing tests if no datasource flag is specified).
+
+### CLI options
+
+This will run all tests in the test folder:
+
+```sh
+graph test
+```
+
+This will run a test named gravity.test.ts and/or all test inside of a folder named gravity:
+
+```sh
+graph test gravity
+```
+
+This will run only that specific test file:
+
+```sh
+graph test path/to/file.test.ts
+```
+
+**Options:**
+
+```sh
+-c, --coverage                Run the tests in coverage mode
+-d, --docker                  Run the tests in a docker container (Note: Please execute from the root folder of the subgraph)
+-f, --force                   Binary: Redownloads the binary. Docker: Redownloads the Dockerfile and rebuilds the docker image.
+-h, --help                    Show usage information
+-l, --logs                    Logs to the console information about the OS, CPU model and download url (debugging purposes)
+-r, --recompile               Forces tests to be recompiled
+-v, --version <tag>           Choose the version of the rust binary that you want to be downloaded/used
+```
+
+### Docker
+
+From `graph-cli 0.25.2`, the `graph test` command supports running `matchstick` in a docker container with the `-d` flag. The docker implementation uses [bind mount](https://docs.docker.com/storage/bind-mounts/) so it does not have to rebuild the docker image every time the `graph test -d` command is executed. Alternatively you can follow the instructions from the [matchstick](https://github.com/LimeChain/matchstick#docker-) repository to run docker manually.
+
+❗ `graph test -d` forces `docker run` to run with flag `-t`. This must be removed to run inside non-interactive environments (like GitHub CI).
+
+❗ If you have previously ran `graph test` you may encounter the following error during docker build:
+
+```sh
+  error from sender: failed to xattr node_modules/binary-install-raw/bin/binary-<platform>: permission denied
+```
+
+In this case create a `.dockerignore` in the root folder and add `node_modules/binary-install-raw/bin`
+
+### Configuration
+
+Matchstick can be configured to use a custom tests, libs and manifest path via `matchstick.yaml` config file:
+
+```yaml
+testsFolder: path/to/tests
+libsFolder: path/to/libs
+manifestPath: path/to/subgraph.yaml
+```
+
+### Demo subgraph
+
+You can try out and play around with the examples from this guide by cloning the [Demo Subgraph repo](https://github.com/LimeChain/demo-subgraph)
+
+### Video tutorials
+
+Also you can check out the video series on ["How to use Matchstick to write unit tests for your subgraphs"](https://www.youtube.com/playlist?list=PLTqyKgxaGF3SNakGQwczpSGVjS_xvOv3h)
+
+## Tests structure
+
+_**IMPORTANT: The test structure described below depens on `matchstick-as` version >=0.5.0**_
+
+### describe()
+
+`describe(name: String , () => {})` - Defines a test group.
+
+**_Notes:_**
+
+- _Describes are not mandatory. You can still use test() the old way, outside of the describe() blocks_
+
+Example:
+
+```typescript
+import { describe, test } from "matchstick-as/assembly/index"
+import { handleNewGravatar } from "../../src/gravity"
+
+describe("handleNewGravatar()", () => {
+  test("Should create a new Gravatar entity", () => {
+    ...
+  })
+})
+```
+
+Nested `describe()` example:
+
+```typescript
+import { describe, test } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar } from "../../src/gravity"
+
+describe("handleUpdatedGravatar()", () => {
+  describe("When entity exists", () => {
+    test("updates the entity", () => {
+      ...
+    })
+  })
+
+  describe("When entity does not exists", () => {
+    test("it creates a new entity", () => {
+      ...
+    })
+  })
+})
+```
+
+---
+
+### test()
+
+`test(name: String, () =>, should_fail: bool)` - Defines a test case. You can use test() inside of describe() blocks or independently.
+
+Example:
+
+```typescript
+import { describe, test } from "matchstick-as/assembly/index"
+import { handleNewGravatar } from "../../src/gravity"
+
+describe("handleNewGravatar()", () => {
+  test("Should create a new Entity", () => {
+    ...
+  })
+})
+```
+
+or
+
+```typescript
+test("handleNewGravatar() should create a new entity", () => {
+  ...
+})
+
+
+```
+
+---
+
+### beforeAll()
+
+Runs a code block before any of the tests in the file. If `beforeAll` is declared inside of a `describe` block, it runs at the beginning of that `describe` block.
+
+Examples:
+
+Code inside `beforeAll` will execute once before _all_ tests in the file.
+
+```typescript
+import { describe, test, beforeAll } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+import { Gravatar } from "../../generated/schema"
+
+beforeAll(() => {
+  let gravatar = new Gravatar("0x0")
+  gravatar.displayName = “First Gravatar”
+  gravatar.save()
+  ...
+})
+
+describe("When the entity does not exist", () => {
+  test("it should create a new Gravatar with id 0x1", () => {
+    ...
+  })
+})
+
+describe("When entity already exists", () => {
+  test("it should update the Gravatar with id 0x0", () => {
+    ...
+  })
+})
+```
+
+Code inside `beforeAll` will execute once before all tests in the first describe block
+
+```typescript
+import { describe, test, beforeAll } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+import { Gravatar } from "../../generated/schema"
+
+describe("handleUpdatedGravatar()", () => {
+  beforeAll(() => {
+    let gravatar = new Gravatar("0x0")
+    gravatar.displayName = “First Gravatar”
+    gravatar.save()
+    ...
+  })
+
+  test("updates Gravatar with id 0x0", () => {
+    ...
+  })
+
+  test("creates new Gravatar with id 0x1", () => {
+    ...
+  })
+})
+```
+
+---
+
+### afterAll()
+
+Runs a code block after all of the tests in the file. If `afterAll` is declared inside of a `describe` block, it runs at the end of that `describe` block.
+
+Example:
+
+Code inside `afterAll` will execute once after _all_ tests in the file.
+
+```typescript
+import { describe, test, afterAll } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+import { store } from "@graphprotocol/graph-ts"
+
+afterAll(() => {
+  store.remove("Gravatar", "0x0")
+  ...
+})
+
+describe("handleNewGravatar, () => {
+  test("creates Gravatar with id 0x0", () => {
+    ...
+  })
+})
+
+describe("handleUpdatedGravatar", () => {
+  test("updates Gravatar with id 0x0", () => {
+    ...
+  })
+})
+```
+
+Code inside `afterAll` will execute once after all tests in the first describe block
+
+```typescript
+import { describe, test, afterAll, clearStore } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+
+describe("handleNewGravatar", () => {
+    afterAll(() => {
+    store.remove("Gravatar", "0x1")
+    ...
+    })
+
+  test("It creates a new entity with Id 0x0", () => {
+    ...
+  })
+
+  test("It creates a new entity with Id 0x1", () => {
+    ...
+  })
+})
+
+describe("handleUpdatedGravatar", () => {
+  test("updates Gravatar with id 0x0", () => {
+    ...
+  })
+})
+```
+
+---
+
+### beforeEach()
+
+Runs a code block before every test. If `beforeEach` is declared inside of a `describe` block, it runs before each test in that `describe` block.
+
+Examples: Code inside `beforeEach` will execute before each tests.
+
+```typescript
+import { describe, test, beforeEach, clearStore } from "matchstick-as/assembly/index"
+import { handleNewGravatars } from "./utils"
+
+beforeEach(() => {
+  clearStore() // <-- clear the store before each test in the file
+})
+
+describe("handleNewGravatars, () => {
+  test("A test that requires a clean store", () => {
+    ...
+  })
+
+  test("Second that requires a clean store", () => {
+    ...
+  })
+})
+
+ ...
+```
+
+Code inside `beforeEach` will execute only before each test in the that describe
+
+```typescript
+import { describe, test, beforeEach } from 'matchstick-as/assembly/index'
+import { handleUpdatedGravatar, handleNewGravatar } from '../../src/gravity'
+
+describe('handleUpdatedGravatars', () => {
+  beforeEach(() => {
+    let gravatar = new Gravatar('0x0')
+    gravatar.displayName = 'First Gravatar'
+    gravatar.imageUrl = ''
+    gravatar.save()
+  })
+
+  test('Upates the displayName', () => {
+    assert.fieldEquals('Gravatar', '0x0', 'displayName', 'First Gravatar')
+
+    // code that should update the displayName to 1st Gravatar
+
+    assert.fieldEquals('Gravatar', '0x0', 'displayName', '1st Gravatar')
+    store.remove('Gravatar', '0x0')
+  })
+
+  test('Updates the imageUrl', () => {
+    assert.fieldEquals('Gravatar', '0x0', 'imageUrl', '')
+
+    // code that should changes the imageUrl to https://www.gravatar.com/avatar/0x0
+
+    assert.fieldEquals('Gravatar', '0x0', 'imageUrl', 'https://www.gravatar.com/avatar/0x0')
+    store.remove('Gravatar', '0x0')
+  })
+})
+```
+
+---
+
+### afterEach()
+
+Runs a code block after every test. If `afterEach` is declared inside of a `describe` block, it runs after each test in that `describe` block.
+
+Examples:
+
+Code inside `afterEach` will execute after every test.
+
+```typescript
+import { describe, test, beforeEach, afterEach } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+
+beforeEach(() => {
+  let gravatar = new Gravatar("0x0")
+  gravatar.displayName = “First Gravatar”
+  gravatar.save()
+})
+
+afterEach(() => {
+  store.remove("Gravatar", "0x0")
+})
+
+describe("handleNewGravatar", () => {
+  ...
+})
+
+describe("handleUpdatedGravatar", () => {
+  test("Upates the displayName", () => {
+     assert.fieldEquals("Gravatar", "0x0", "displayName", "First Gravatar")
+
+    // code that should update the displayName to 1st Gravatar
+
+    assert.fieldEquals("Gravatar", "0x0", "displayName", "1st Gravatar")
+  })
+
+  test("Updates the imageUrl", () => {
+    assert.fieldEquals("Gravatar", "0x0", "imageUrl", "")
+
+    // code that should changes the imageUrl to https://www.gravatar.com/avatar/0x0
+
+    assert.fieldEquals("Gravatar", "0x0", "imageUrl", "https://www.gravatar.com/avatar/0x0")
+  })
+})
+```
+
+Code inside `afterEach` will execute after each test in that describe
+
+```typescript
+import { describe, test, beforeEach, afterEach } from "matchstick-as/assembly/index"
+import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+
+describe("handleNewGravatar", () => {
+  ...
+})
+
+describe("handleUpdatedGravatar", () => {
+  beforeEach(() => {
+    let gravatar = new Gravatar("0x0")
+    gravatar.displayName = "First Gravatar"
+    gravatar.imageUrl = ""
+    gravatar.save()
+  })
+
+  afterEach(() => {
+    store.remove("Gravatar", "0x0")
+  })
+
+  test("Upates the displayName", () => {
+     assert.fieldEquals("Gravatar", "0x0", "displayName", "First Gravatar")
+
+    // code that should update the displayName to 1st Gravatar
+
+    assert.fieldEquals("Gravatar", "0x0", "displayName", "1st Gravatar")
+  })
+
+  test("Updates the imageUrl", () => {
+    assert.fieldEquals("Gravatar", "0x0", "imageUrl", "")
+
+    // code that should changes the imageUrl to https://www.gravatar.com/avatar/0x0
+
+    assert.fieldEquals("Gravatar", "0x0", "imageUrl", "https://www.gravatar.com/avatar/0x0")
+  })
+})
+```
+
+## Asserts
+
+```typescript
+fieldEquals(entityType: string, id: string, fieldName: string, expectedVal: string)
+
+equals(expected: ethereum.Value, actual: ethereum.Value)
+
+notInStore(entityType: string, id: string)
+
+addressEquals(address1: Address, address2: Address)
+
+bytesEquals(bytes1: Bytes, bytes2: Bytes)
+
+i32Equals(number1: i32, number2: i32)
+
+bigIntEquals(bigInt1: BigInt, bigInt2: BigInt)
+
+booleanEquals(bool1: boolean, bool2: boolean)
+
+stringEquals(string1: string, string2: string)
+
+arrayEquals(array1: Array<ethereum.Value>, array2: Array<ethereum.Value>)
+
+tupleEquals(tuple1: ethereum.Tuple, tuple2: ethereum.Tuple)
+
+assertTrue(value: boolean)
+
+assertNull<T>(value: T)
+
+assertNotNull<T>(value: T)
+
+entityCount(entityType: string, expectedCount: i32)
+```
+
+As of version 0.6.0, asserts support custom error messages as well
+
+```typescript
+assert.fieldEquals('Gravatar', '0x123', 'id', '0x123', 'Id should be 0x123')
+assert.equals(ethereum.Value.fromI32(1), ethereum.Value.fromI32(1), 'Value should equal 1')
+assert.notInStore('Gravatar', '0x124', 'Gravatar should not be in store')
+assert.addressEquals(Address.zero(), Address.zero(), 'Address should be zero')
+assert.bytesEquals(Bytes.fromUTF8('0x123'), Bytes.fromUTF8('0x123'), 'Bytes should be equal')
+assert.i32Equals(2, 2, 'I32 should equal 2')
+assert.bigIntEquals(BigInt.fromI32(1), BigInt.fromI32(1), 'BigInt should equal 1')
+assert.booleanEquals(true, true, 'Boolean should be true')
+assert.stringEquals('1', '1', 'String should equal 1')
+assert.arrayEquals([ethereum.Value.fromI32(1)], [ethereum.Value.fromI32(1)], 'Arrays should be equal')
+assert.tupleEquals(
+  changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
+  changetype<ethereum.Tuple>([ethereum.Value.fromI32(1)]),
+  'Tuples should be equal',
+)
+assert.assertTrue(true, 'Should be true')
+assert.assertNull(null, 'Should be null')
+assert.assertNotNull('not null', 'Should be not null')
+assert.entityCount('Gravatar', 1, 'There should be 2 gravatars')
+assert.dataSourceCount('GraphTokenLockWallet', 1, 'GraphTokenLockWallet template should have one data source')
+assert.dataSourceExists(
+  'GraphTokenLockWallet',
+  Address.zero().toHexString(),
+  'GraphTokenLockWallet should have a data source for zero address',
+)
+```
+
+## Write a Unit Test
+
+Let's see how a simple unit test would look like using the Gravatar examples in the [Demo Subgraph](https://github.com/LimeChain/demo-subgraph/blob/main/src/gravity.ts).
+
+Assuming we have the following handler function (along with two helper functions to make our life easier):
+
+```typescript
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id.toHex())
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleNewGravatars(events: NewGravatar[]): void {
+  events.forEach((event) => {
+    handleNewGravatar(event)
+  })
+}
+
+export function createNewGravatarEvent(
+  id: i32,
+  ownerAddress: string,
+  displayName: string,
+  imageUrl: string,
+): NewGravatar {
+  let mockEvent = newMockEvent()
+  let newGravatarEvent = new NewGravatar(
+    mockEvent.address,
+    mockEvent.logIndex,
+    mockEvent.transactionLogIndex,
+    mockEvent.logType,
+    mockEvent.block,
+    mockEvent.transaction,
+    mockEvent.parameters,
+  )
+  newGravatarEvent.parameters = new Array()
+  let idParam = new ethereum.EventParam('id', ethereum.Value.fromI32(id))
+  let addressParam = new ethereum.EventParam(
+    'ownderAddress',
+    ethereum.Value.fromAddress(Address.fromString(ownerAddress)),
+  )
+  let displayNameParam = new ethereum.EventParam('displayName', ethereum.Value.fromString(displayName))
+  let imageUrlParam = new ethereum.EventParam('imageUrl', ethereum.Value.fromString(imageUrl))
+
+  newGravatarEvent.parameters.push(idParam)
+  newGravatarEvent.parameters.push(addressParam)
+  newGravatarEvent.parameters.push(displayNameParam)
+  newGravatarEvent.parameters.push(imageUrlParam)
+
+  return newGravatarEvent
+}
+```
+
+We first have to create a test file in our project. This is an example of how that might look like:
+
+```typescript
+import { clearStore, test, assert } from 'matchstick-as/assembly/index'
+import { Gravatar } from '../../generated/schema'
+import { NewGravatar } from '../../generated/Gravity/Gravity'
+import { createNewGravatarEvent, handleNewGravatars } from '../mappings/gravity'
+
+test('Can call mappings with custom events', () => {
+  // Create a test entity and save it in the store as initial state (optional)
+  let gravatar = new Gravatar('gravatarId0')
+  gravatar.save()
+
+  // Create mock events
+  let newGravatarEvent = createNewGravatarEvent(12345, '0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7', 'cap', 'pac')
+  let anotherGravatarEvent = createNewGravatarEvent(3546, '0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7', 'cap', 'pac')
+
+  // Call mapping functions passing the events we just created
+  handleNewGravatars([newGravatarEvent, anotherGravatarEvent])
+
+  // Assert the state of the store
+  assert.fieldEquals('Gravatar', 'gravatarId0', 'id', 'gravatarId0')
+  assert.fieldEquals('Gravatar', '12345', 'owner', '0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7')
+  assert.fieldEquals('Gravatar', '3546', 'displayName', 'cap')
+
+  // Clear the store in order to start the next test off on a clean slate
+  clearStore()
+})
+
+test('Next test', () => {
+  //...
+})
+```
+
+That's a lot to unpack! First off, an important thing to notice is that we're importing things from `matchstick-as`, our AssemblyScript helper library (distributed as an npm module). You can find the repository [here](https://github.com/LimeChain/matchstick-as). `matchstick-as` provides us with useful testing methods and also defines the `test()` function which we will use to build our test blocks. The rest of it is pretty straightforward - here's what happens:
+
+- We're setting up our initial state and adding one custom Gravatar entity;
+- We define two `NewGravatar` event objects along with their data, using the `createNewGravatarEvent()` function;
+- We're calling out handler methods for those events - `handleNewGravatars()` and passing in the list of our custom events;
+- We assert the state of the store. How does that work? - We're passing a unique combination of Entity type and id. Then we check a specific field on that Entity and assert that it has the value we expect it to have. We're doing this both for the initial Gravatar Entity we added to the store, as well as the two Gravatar entities that gets added when the handler function is called;
+- And lastly - we're cleaning the store using `clearStore()` so that our next test can start with a fresh and empty store object. We can define as many test blocks as we want.
+
+There we go - we've created our first test! 👏
+
+Now in order to run our tests you simply need to run the following in your subgraph root folder:
+
+`graph test Gravity`
+
+And if all goes well you should be greeted with the following:
+
+![Matchstick saying “All tests passed!”](/img/matchstick-tests-passed.png)
+
+## Common test scenarios
+
+### Hydrating the store with a certain state
+
+Users are able to hydrate the store with a known set of entities. Here's an example to initialise the store with a Gravatar entity:
+
+```typescript
+let gravatar = new Gravatar('entryId')
+gravatar.save()
+```
+
+### Calling a mapping function with an event
+
+A user can create a custom event and pass it to a mapping function that is bound to the store:
+
+```typescript
+import { store } from 'matchstick-as/assembly/store'
+import { NewGravatar } from '../../generated/Gravity/Gravity'
+import { handleNewGravatars, createNewGravatarEvent } from './mapping'
+
+let newGravatarEvent = createNewGravatarEvent(12345, '0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7', 'cap', 'pac')
+
+handleNewGravatar(newGravatarEvent)
+```
+
+### Calling all of the mappings with event fixtures
+
+Users can call the mappings with test fixtures.
+
+```typescript
+import { NewGravatar } from '../../generated/Gravity/Gravity'
+import { store } from 'matchstick-as/assembly/store'
+import { handleNewGravatars, createNewGravatarEvent } from './mapping'
+
+let newGravatarEvent = createNewGravatarEvent(12345, '0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7', 'cap', 'pac')
+
+let anotherGravatarEvent = createNewGravatarEvent(3546, '0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7', 'cap', 'pac')
+
+handleNewGravatars([newGravatarEvent, anotherGravatarEvent])
+```
+
+```
+export function handleNewGravatars(events: NewGravatar[]): void {
+    events.forEach(event => {
+        handleNewGravatar(event);
+    });
+}
+```
+
+### Mocking contract calls
+
+Users can mock contract calls:
+
+```typescript
+import { addMetadata, assert, createMockedFunction, clearStore, test } from 'matchstick-as/assembly/index'
+import { Gravity } from '../../generated/Gravity/Gravity'
+import { Address, BigInt, ethereum } from '@graphprotocol/graph-ts'
+
+let contractAddress = Address.fromString('0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7')
+let expectedResult = Address.fromString('0x90cBa2Bbb19ecc291A12066Fd8329D65FA1f1947')
+let bigIntParam = BigInt.fromString('1234')
+createMockedFunction(contractAddress, 'gravatarToOwner', 'gravatarToOwner(uint256):(address)')
+  .withArgs([ethereum.Value.fromSignedBigInt(bigIntParam)])
+  .returns([ethereum.Value.fromAddress(Address.fromString('0x90cBa2Bbb19ecc291A12066Fd8329D65FA1f1947'))])
+
+let gravity = Gravity.bind(contractAddress)
+let result = gravity.gravatarToOwner(bigIntParam)
+
+assert.equals(ethereum.Value.fromAddress(expectedResult), ethereum.Value.fromAddress(result))
+```
+
+As demonstrated, in order to mock a contract call and hardcore a return value, the user must provide a contract address, function name, function signature, an array of arguments, and of course - the return value.
+
+Users can also mock function reverts:
+
+```typescript
+let contractAddress = Address.fromString('0x89205A3A3b2A69De6Dbf7f01ED13B2108B2c43e7')
+createMockedFunction(contractAddress, 'getGravatar', 'getGravatar(address):(string,string)')
+  .withArgs([ethereum.Value.fromAddress(contractAddress)])
+  .reverts()
+```
+
+### Mocking IPFS files (from matchstick 0.4.1)
+
+Users can mock IPFS files by using `mockIpfsFile(hash, filePath)` function. The function accepts two arguments, the first one is the IPFS file hash/path and the second one is the path to a local file.
+
+NOTE: When testing `ipfs.map/ipfs.mapJSON`, the callback function must be exported from the test file in order for matchstck to detect it, like the `processGravatar()` function in the test example bellow:
+
+`.test.ts` file:
+
+```typescript
+import { assert, test, mockIpfsFile } from 'matchstick-as/assembly/index'
+import { ipfs } from '@graphprotocol/graph-ts'
+import { gravatarFromIpfs } from './utils'
+
+// Export ipfs.map() callback in order for matchstck to detect it
+export { processGravatar } from './utils'
+
+test('ipfs.cat', () => {
+  mockIpfsFile('ipfsCatfileHash', 'tests/ipfs/cat.json')
+
+  assert.entityCount(GRAVATAR_ENTITY_TYPE, 0)
+
+  gravatarFromIpfs()
+
+  assert.entityCount(GRAVATAR_ENTITY_TYPE, 1)
+  assert.fieldEquals(GRAVATAR_ENTITY_TYPE, '1', 'imageUrl', 'https://i.ytimg.com/vi/MELP46s8Cic/maxresdefault.jpg')
+
+  clearStore()
+})
+
+test('ipfs.map', () => {
+  mockIpfsFile('ipfsMapfileHash', 'tests/ipfs/map.json')
+
+  assert.entityCount(GRAVATAR_ENTITY_TYPE, 0)
+
+  ipfs.map('ipfsMapfileHash', 'processGravatar', Value.fromString('Gravatar'), ['json'])
+
+  assert.entityCount(GRAVATAR_ENTITY_TYPE, 3)
+  assert.fieldEquals(GRAVATAR_ENTITY_TYPE, '1', 'displayName', 'Gravatar1')
+  assert.fieldEquals(GRAVATAR_ENTITY_TYPE, '2', 'displayName', 'Gravatar2')
+  assert.fieldEquals(GRAVATAR_ENTITY_TYPE, '3', 'displayName', 'Gravatar3')
+})
+```
+
+`utils.ts` file:
+
+```typescript
+import { Address, ethereum, JSONValue, Value, ipfs, json, Bytes } from "@graphprotocol/graph-ts"
+import { Gravatar } from "../../generated/schema"
+
+...
+
+// ipfs.map callback
+export function processGravatar(value: JSONValue, userData: Value): void {
+  // See the JSONValue documentation for details on dealing
+  // with JSON values
+  let obj = value.toObject()
+  let id = obj.get('id')
+
+  if (!id) {
+    return
+  }
+
+  // Callbacks can also created entities
+  let gravatar = new Gravatar(id.toString())
+  gravatar.displayName = userData.toString() + id.toString()
+  gravatar.save()
+}
+
+// function that calls ipfs.cat
+export function gravatarFromIpfs(): void {
+  let rawData = ipfs.cat("ipfsCatfileHash")
+
+  if (!rawData) {
+    return
+  }
+
+  let jsonData = json.fromBytes(rawData as Bytes).toObject()
+
+  let id = jsonData.get('id')
+  let url = jsonData.get("imageUrl")
+
+  if (!id || !url) {
+    return
+  }
+
+  let gravatar = new Gravatar(id.toString())
+  gravatar.imageUrl = url.toString()
+  gravatar.save()
+}
+```
+
+### Asserting the state of the store
+
+Users are able to assert the final (or midway) state of the store through asserting entities. In order to do this, the user has to supply an Entity type, the specific ID of an Entity, a name of a field on that Entity, and the expected value of the field. Here's a quick example:
+
+```typescript
+import { assert } from 'matchstick-as/assembly/index'
+import { Gravatar } from '../generated/schema'
+
+let gravatar = new Gravatar('gravatarId0')
+gravatar.save()
+
+assert.fieldEquals('Gravatar', 'gravatarId0', 'id', 'gravatarId0')
+```
+
+Running the assert.fieldEquals() function will check for equality of the given field against the given expected value. The test will fail and an error message will be outputted if the values are **NOT** equal. Otherwise the test will pass successfully.
+
+### Interacting with Event metadata
+
+Users can use default transaction metadata, which could be returned as an ethereum.Event by using the `newMockEvent()` function. The following example shows how you can read/write to those fields on the Event object:
+
+```typescript
+// Read
+let logType = newGravatarEvent.logType
+
+// Write
+let UPDATED_ADDRESS = '0xB16081F360e3847006dB660bae1c6d1b2e17eC2A'
+newGravatarEvent.address = Address.fromString(UPDATED_ADDRESS)
+```
+
+### Asserting variable equality
+
+```typescript
+assert.equals(ethereum.Value.fromString("hello"); ethereum.Value.fromString("hello"));
+```
+
+### Asserting that an Entity is **not** in the store
+
+Users can assert that an entity does not exist in the store. The function takes an entity type and an id. If the entity is in fact in the store, the test will fail with a relevant error message. Here's a quick example of how to use this functionality:
+
+```typescript
+assert.notInStore('Gravatar', '23')
+```
+
+### Printing the whole store, or single entities from it (for debug purposes)
+
+You can print the whole store to the console using this helper function:
+
+```typescript
+import { logStore } from 'matchstick-as/assembly/store'
+
+logStore()
+```
+
+As of version 0.6.0, `logStore` no longer prints derived fields, instead users can use the new `logEntity` function. Of course `logEntity` can be used to print any entity, not just ones that have derived fields. `logEntity` takes the entity type, entity id and a `showRelated` flag to indicate if users want to print the related derived entities.
+
+```
+import { logEntity } from 'matchstick-as/assembly/store'
+
+
+logEntity("Gravatar", 23, true)
+```
+
+### Expected failure
+
+Users can have expected test failures, using the shouldFail flag on the test() functions:
+
+```typescript
+test(
+  'Should throw an error',
+  () => {
+    throw new Error()
+  },
+  true,
+)
+```
+
+If the test is marked with shouldFail = true but DOES NOT fail, that will show up as an error in the logs and the test block will fail. Also, if it's marked with shouldFail = false (the default state), the test executor will crash.
+
+### Logging
+
+Having custom logs in the unit tests is exactly the same as logging in the mappings. The difference is that the log object needs to be imported from matchstick-as rather than graph-ts. Here's a simple example with all non-critical log types:
+
+```typescript
+import { test } from "matchstick-as/assembly/index";
+import { log } from "matchstick-as/assembly/log";
+
+test("Success", () => {
+    log.success("Success!". []);
+});
+test("Error", () => {
+    log.error("Error :( ", []);
+});
+test("Debug", () => {
+    log.debug("Debugging...", []);
+});
+test("Info", () => {
+    log.info("Info!", []);
+});
+test("Warning", () => {
+    log.warning("Warning!", []);
+});
+```
+
+Users can also simulate a critical failure, like so:
+
+```typescript
+test('Blow everything up', () => {
+  log.critical('Boom!')
+})
+```
+
+Logging critical errors will stop the execution of the tests and blow everything up. After all - we want to make sure you're code doesn't have critical logs in deployment, and you should notice right away if that were to happen.
+
+### Testing derived fields
+
+Testing derived fields is a feature which allows users to set a field on a certain entity and have another entity be updated automatically if it derives one of its fields from the first entity.
+
+Before version `0.6.0` it was possible to get the derived entities by accessing them as entity fields/properties, like so:
+
+```typescript
+let entity = ExampleEntity.load('id')
+let derivedEntity = entity.derived_entity
+```
+
+As of version `0.6.0`, this is done by using the `loadRelated` function of graph-node, the derived entities can be accessed the same way as in the handlers.
+
+```typescript
+test('Derived fields example test', () => {
+  let mainAccount = GraphAccount.load('12')!
+
+  assert.assertNull(mainAccount.get('nameSignalTransactions'))
+  assert.assertNull(mainAccount.get('operatorOf'))
+
+  let operatedAccount = GraphAccount.load('1')!
+  operatedAccount.operators = [mainAccount.id]
+  operatedAccount.save()
+
+  mockNameSignalTransaction('1234', mainAccount.id)
+  mockNameSignalTransaction('2', mainAccount.id)
+
+  mainAccount = GraphAccount.load('12')!
+
+  assert.assertNull(mainAccount.get('nameSignalTransactions'))
+  assert.assertNull(mainAccount.get('operatorOf'))
+
+  const nameSignalTransactions = mainAccount.nameSignalTransactions.load()
+  const operatorsOfMainAccount = mainAccount.operatorOf.load()
+
+  assert.i32Equals(2, nameSignalTransactions.length)
+  assert.i32Equals(1, operatorsOfMainAccount.length)
+
+  assert.stringEquals('1', operatorsOfMainAccount[0].id)
+
+  mockNameSignalTransaction('2345', mainAccount.id)
+
+  let nst = NameSignalTransaction.load('1234')!
+  nst.signer = '11'
+  nst.save()
+
+  store.remove('NameSignalTransaction', '2')
+
+  mainAccount = GraphAccount.load('12')!
+  assert.i32Equals(1, mainAccount.nameSignalTransactions.load().length)
+})
+```
+
+### Testing `loadInBlock`
+
+As of version `0.6.0`, users can test `loadInBlock` by using the `mockInBlockStore`, it allows mocking entities in the block cache.
+
+```typescript
+import { afterAll, beforeAll, describe, mockInBlockStore, test } from 'matchstick-as'
+import { Gravatar } from '../../generated/schema'
+
+describe('loadInBlock', () => {
+  beforeAll(() => {
+    mockInBlockStore('Gravatar', 'gravatarId0', gravatar)
+  })
+
+  afterAll(() => {
+    clearInBlockStore()
+  })
+
+  test('Can use entity.loadInBlock() to retrieve entity from cache store in the current block', () => {
+    let retrievedGravatar = Gravatar.loadInBlock('gravatarId0')
+    assert.stringEquals('gravatarId0', retrievedGravatar!.get('id')!.toString())
+  })
+
+  test("Returns null when calling entity.loadInBlock() if an entity doesn't exist in the current block", () => {
+    let retrievedGravatar = Gravatar.loadInBlock('IDoNotExist')
+    assert.assertNull(retrievedGravatar)
+  })
+})
+```
+
+### Testing dynamic data sources
+
+Testing dynamic data sources can be be done by mocking the return value of the `context()`, `address()` and `network()` functions of the dataSource namespace. These functions currently return the following: `context()` - returns an empty entity (DataSourceContext), `address()` - returns `0x0000000000000000000000000000000000000000`, `network()` - returns `mainnet`. The `create(...)` and `createWithContext(...)` functions are mocked to do nothing so they don't need to be called in the tests at all. Changes to the return values can be done through the functions of the `dataSourceMock` namespace in `matchstick-as` (version 0.3.0+).
+
+Example below:
+
+First we have the following event handler (which has been intentionally repurposed to showcase datasource mocking):
+
+```typescript
+export function handleApproveTokenDestinations(event: ApproveTokenDestinations): void {
+  let tokenLockWallet = TokenLockWallet.load(dataSource.address().toHexString())!
+  if (dataSource.network() == 'rinkeby') {
+    tokenLockWallet.tokenDestinationsApproved = true
+  }
+  let context = dataSource.context()
+  if (context.get('contextVal')!.toI32() > 0) {
+    tokenLockWallet.setBigInt('tokensReleased', BigInt.fromI32(context.get('contextVal')!.toI32()))
+  }
+  tokenLockWallet.save()
+}
+```
+
+And then we have the test using one of the methods in the dataSourceMock namespace to set a new return value for all of the dataSource functions:
+
+```typescript
+import { assert, test, newMockEvent, dataSourceMock } from 'matchstick-as/assembly/index'
+import { BigInt, DataSourceContext, Value } from '@graphprotocol/graph-ts'
+
+import { handleApproveTokenDestinations } from '../../src/token-lock-wallet'
+import { ApproveTokenDestinations } from '../../generated/templates/GraphTokenLockWallet/GraphTokenLockWallet'
+import { TokenLockWallet } from '../../generated/schema'
+
+test('Data source simple mocking example', () => {
+  let addressString = '0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'
+  let address = Address.fromString(addressString)
+
+  let wallet = new TokenLockWallet(address.toHexString())
+  wallet.save()
+  let context = new DataSourceContext()
+  context.set('contextVal', Value.fromI32(325))
+  dataSourceMock.setReturnValues(addressString, 'rinkeby', context)
+  let event = changetype<ApproveTokenDestinations>(newMockEvent())
+
+  assert.assertTrue(!wallet.tokenDestinationsApproved)
+
+  handleApproveTokenDestinations(event)
+
+  wallet = TokenLockWallet.load(address.toHexString())!
+  assert.assertTrue(wallet.tokenDestinationsApproved)
+  assert.bigIntEquals(wallet.tokensReleased, BigInt.fromI32(325))
+
+  dataSourceMock.resetValues()
+})
+```
+
+Notice that dataSourceMock.resetValues() is called at the end. That's because the values are remembered when they are changed and need to be reset if you want to go back to the default values.
+
+### Testing dynamic data source creation
+
+As of version `0.6.0`, it is possible to test if a new data source has been created from a template. This feature supports both ethereum/contract and file/ipfs templates. There are four functions for this:
+
+- `assert.dataSourceCount(templateName, expectedCount)` can be used to assert the expected count of data sources from the specified template
+- `assert.dataSourceExists(templateName, address/ipfsHash)` asserts that a data source with the specified identifier (could be a contract address or IPFS file hash) from a specified template was created
+- `logDataSources(templateName)` prints all data sources from the specified template to the console for debugging purposes
+- `readFile(path)` reads a JSON file that represents an IPFS file and returns the content as Bytes
+
+#### Testing `ethereum/contract` templates
+
+```typescript
+test('ethereum/contract dataSource creation example', () => {
+  // Assert there are no dataSources created from GraphTokenLockWallet template
+  assert.dataSourceCount('GraphTokenLockWallet', 0)
+
+  // Create a new GraphTokenLockWallet datasource with address 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
+  GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
+
+  // Assert the dataSource has been created
+  assert.dataSourceCount('GraphTokenLockWallet', 1)
+
+  // Add a second dataSource with context
+  let context = new DataSourceContext()
+  context.set('contextVal', Value.fromI32(325))
+
+  GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
+
+  // Assert there are now 2 dataSources
+  assert.dataSourceCount('GraphTokenLockWallet', 2)
+
+  // Assert that a dataSource with address "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B" was created
+  // Keep in mind that `Address` type is transformed to lower case when decoded, so you have to pass the address as all lower case when asserting if it exists
+  assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
+
+  logDataSources('GraphTokenLockWallet')
+})
+```
+
+##### Example `logDataSource` output
+
+```bash
+🛠  {
+  "0xa16081f360e3847006db660bae1c6d1b2e17ec2a": {
+    "kind": "ethereum/contract",
+    "name": "GraphTokenLockWallet",
+    "address": "0xa16081f360e3847006db660bae1c6d1b2e17ec2a",
+    "context": null
+  },
+  "0xa16081f360e3847006db660bae1c6d1b2e17ec2b": {
+    "kind": "ethereum/contract",
+    "name": "GraphTokenLockWallet",
+    "address": "0xa16081f360e3847006db660bae1c6d1b2e17ec2b",
+    "context": {
+      "contextVal": {
+        "type": "Int",
+        "data": 325
+      }
+    }
+  }
+}
+```
+
+#### Testing `file/ipfs` templates
+
+Similarly to contract dynamic data sources, users can test test file datas sources and their handlers
+
+##### Example `subgraph.yaml`
+
+```yaml
+...
+templates:
+ - kind: file/ipfs
+    name: GraphTokenLockMetadata
+    network: mainnet
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/token-lock-wallet.ts
+      handler: handleMetadata
+      entities:
+        - TokenLockMetadata
+      abis:
+        - name: GraphTokenLockWallet
+          file: ./abis/GraphTokenLockWallet.json
+```
+
+##### Example `schema.graphql`
+
+```graphql
+"""
+Token Lock Wallets which hold locked GRT
+"""
+type TokenLockMetadata @entity {
+  "The address of the token lock wallet"
+  id: ID!
+  "Start time of the release schedule"
+  startTime: BigInt!
+  "End time of the release schedule"
+  endTime: BigInt!
+  "Number of periods between start time and end time"
+  periods: BigInt!
+  "Time when the releases start"
+  releaseStartTime: BigInt!
+}
+```
+
+##### Example `metadata.json`
+
+```json
+{
+  "startTime": 1,
+  "endTime": 1,
+  "periods": 1,
+  "releaseStartTime": 1
+}
+```
+
+##### Example handler
+
+```typescript
+export function handleMetadata(content: Bytes): void {
+  // dataSource.stringParams() returns the File DataSource CID
+  // stringParam() will be mocked in the handler test
+  // for more info https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
+  let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+
+  if (value) {
+    const startTime = value.get('startTime')
+    const endTime = value.get('endTime')
+    const periods = value.get('periods')
+    const releaseStartTime = value.get('releaseStartTime')
+
+    if (startTime && endTime && periods && releaseStartTime) {
+      tokenMetadata.startTime = startTime.toBigInt()
+      tokenMetadata.endTime = endTime.toBigInt()
+      tokenMetadata.periods = periods.toBigInt()
+      tokenMetadata.releaseStartTime = releaseStartTime.toBigInt()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+##### Example test
+
+```typescript
+import { assert, test, dataSourceMock, readFile } from 'matchstick-as'
+import { Address, BigInt, Bytes, DataSourceContext, ipfs, json, store, Value } from '@graphprotocol/graph-ts'
+
+import { handleMetadata } from '../../src/token-lock-wallet'
+import { TokenLockMetadata } from '../../generated/schema'
+import { GraphTokenLockMetadata } from '../../generated/templates'
+
+test('file/ipfs dataSource creation example', () => {
+  // Generate the dataSource CID from the ipfsHash + ipfs path file
+  // For example QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
+  const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+  const CID = `${ipfshash}/example.json`
+
+  // Create a new dataSource using the generated CID
+  GraphTokenLockMetadata.create(CID)
+
+  // Assert the dataSource has been created
+  assert.dataSourceCount('GraphTokenLockMetadata', 1)
+  assert.dataSourceExists('GraphTokenLockMetadata', CID)
+  logDataSources('GraphTokenLockMetadata')
+
+  // Now we have to mock the dataSource metadata and specifically dataSource.stringParam()
+  // dataSource.stringParams actually uses the value of dataSource.address(), so we will mock the address using dataSourceMock from  matchstick-as
+  // First we will reset the values and then use dataSourceMock.setAddress() to set the CID
+  dataSourceMock.resetValues()
+  dataSourceMock.setAddress(CID)
+
+  // Now we need to generate the Bytes to pass to the dataSource handler
+  // For this case we introduced a new function readFile, that reads a local json and returns the content as Bytes
+  const content = readFile(`path/to/metadata.json`)
+  handleMetadata(content)
+
+  // Now we will test if a TokenLockMetadata was created
+  const metadata = TokenLockMetadata.load(CID)
+
+  assert.bigIntEquals(metadata!.endTime, BigInt.fromI32(1))
+  assert.bigIntEquals(metadata!.periods, BigInt.fromI32(1))
+  assert.bigIntEquals(metadata!.releaseStartTime, BigInt.fromI32(1))
+  assert.bigIntEquals(metadata!.startTime, BigInt.fromI32(1))
+})
+```
+
+## Test Coverage
+
+Using **Matchstick**, subgraph developers are able to run a script that will calculate the test coverage of the written unit tests.
+
+The test coverage tool takes the compiled test `wasm` binaries and converts them to `wat` files, which can then be easily inspected to see whether or not the handlers defined in `subgraph.yaml` have been called. Since code coverage (and testing as whole) is in very early stages in AssemblyScript and WebAssembly, **Matchstick** cannot check for branch coverage. Instead we rely on the assertion that if a given handler has been called, the event/function for it have been properly mocked.
+
+### Prerequisites
+
+To run the test coverage functionality provided in **Matchstick**, there are a few things you need to prepare beforehand:
+
+#### Export your handlers
+
+In order for **Matchstick** to check which handlers are being run, those handlers need to be exported from the **test file**. So for instance in our example, in our gravity.test.ts file we have the following handler being imported:
+
+```typescript
+import { handleNewGravatar } from '../../src/gravity'
+```
+
+In order for that function to be visible (for it to be included in the `wat` file **by name**) we need to also export it, like this:
+
+```typescript
+export { handleNewGravatar }
+```
+
+### Usage
+
+Once that's all set up, to run the test coverage tool, simply run:
+
+```sh
+graph test -- -c
+```
+
+You could also add a custom `coverage` command to your `package.json` file, like so:
+
+```typescript
+ "scripts": {
+    /.../
+    "coverage": "graph test -- -c"
+  },
+```
+
+That will execute the coverage tool and you should see something like this in the terminal:
+
+```sh
+$ graph test -c
+Skipping download/install step because binary already exists at /Users/petko/work/demo-subgraph/node_modules/binary-install-raw/bin/0.4.0
+
+___  ___      _       _         _   _      _
+|  \/  |     | |     | |       | | (_)    | |
+| .  . | __ _| |_ ___| |__  ___| |_ _  ___| | __
+| |\/| |/ _` | __/ __| '_ \/ __| __| |/ __| |/ /
+| |  | | (_| | || (__| | | \__ \ |_| | (__|   <
+\_|  |_/\__,_|\__\___|_| |_|___/\__|_|\___|_|\_\
+
+Compiling...
+
+Running in coverage report mode.
+ ️
+Reading generated test modules... 🔎️
+
+Generating coverage report 📝
+
+Handlers for source 'Gravity':
+Handler 'handleNewGravatar' is tested.
+Handler 'handleUpdatedGravatar' is not tested.
+Handler 'handleCreateGravatar' is tested.
+Test coverage: 66.7% (2/3 handlers).
+
+Handlers for source 'GraphTokenLockWallet':
+Handler 'handleTokensReleased' is not tested.
+Handler 'handleTokensWithdrawn' is not tested.
+Handler 'handleTokensRevoked' is not tested.
+Handler 'handleManagerUpdated' is not tested.
+Handler 'handleApproveTokenDestinations' is not tested.
+Handler 'handleRevokeTokenDestinations' is not tested.
+Test coverage: 0.0% (0/6 handlers).
+
+Global test coverage: 22.2% (2/9 handlers).
+```
+
+### Test run time duration in the log output
+
+The log output includes the test run duration. Here's an example:
+
+`[Thu, 31 Mar 2022 13:54:54 +0300] Program executed in: 42.270ms.`
+
+## Common compiler errors
+
+> Critical: Could not create WasmInstance from valid module with context: unknown import: wasi_snapshot_preview1::fd_write has not been defined
+
+This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
+
+> ERROR TS2554: Expected ? arguments, but got ?.
+> 
+> return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
+> 
+> in ~lib/matchstick-as/assembly/defaults.ts(18,12)
+> 
+> ERROR TS2554: Expected ? arguments, but got ?.
+> 
+> return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
+> 
+> in ~lib/matchstick-as/assembly/defaults.ts(24,12)
+
+The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
+
+## Additional Resources
+
+For any additional support, check out this [demo subgraph repo using Matchstick](https://github.com/LimeChain/demo-subgraph#readme_).
+
+## Feedback
+
+If you have any questions, feedback, feature requests or just want to reach out, the best place would be The Graph Discord where we have a dedicated channel for Matchstick, called 🔥| unit-testing.

From 8ecb132408d593adcc956f7d377076bc2afecaed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:56 -0500
Subject: [PATCH 0365/1325] New translations graphql-api.mdx (Vietnamese)

---
 website/pages/vi/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/vi/querying/graphql-api.mdx b/website/pages/vi/querying/graphql-api.mdx
index 8e1257c0b74b..65d0a40a7bd4 100644
--- a/website/pages/vi/querying/graphql-api.mdx
+++ b/website/pages/vi/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Các truy vấn
+## What is GraphQL?
 
-Trong lược đồ subgraph của bạn, bạn xác định các loại được gọi là `Entities`. Với mỗi loại `Entity`, một trường `entity` và `entities` sẽ được tạo ở loại `Query` cấp cao nhất. Lưu ý là `query` không cần phải được bao gồm ở đầu truy vấn `graphql` khi sử dụng The Graph.
+[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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Truy vấn cho một thực thể `Token` được xác định trong lược đ
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### Ví dụ
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ As of Graph Node [`v0.30.0`](https://github.com/graphprotocol/graph-node/release
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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ụ
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext 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 |
-| &#x7c; | `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                                               |
+| &#x7c;      | `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
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Lược đồ
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From 1cea3d22f75bbdf75ed132ade244689a9eabe48c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:57 -0500
Subject: [PATCH 0366/1325] New translations graphql-api.mdx (Marathi)

---
 website/pages/mr/querying/graphql-api.mdx | 69 ++++++++++++++---------
 1 file changed, 41 insertions(+), 28 deletions(-)

diff --git a/website/pages/mr/querying/graphql-api.mdx b/website/pages/mr/querying/graphql-api.mdx
index 1179e40706f2..7fefa001aca4 100644
--- a/website/pages/mr/querying/graphql-api.mdx
+++ b/website/pages/mr/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: GraphQL API
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+Learn about the GraphQL Query API used in The Graph.
 
-## Queries
+## What is GraphQL?
 
-तुमच्या सबग्राफ स्कीमामध्ये तुम्ही `एंटिटीज` नावाचे प्रकार परिभाषित करता. प्रत्येक `संस्था` प्रकारासाठी, उच्च-स्तरीय `क्वेरी` प्रकारावर एक `संस्था` आणि `संस्था` फील्ड व्युत्पन्न केले जाईल. लक्षात ठेवा की ग्राफ वापरताना `क्वेरी` `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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
 
 ### Examples
 
@@ -21,7 +29,7 @@ Query for a single `Token` entity defined in your schema:
 }
 ```
 
-> **Note:** When querying for a single entity, the `id` field is required, and it must be a string.
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
 
 Query all `Token` entities:
 
@@ -36,7 +44,10 @@ Query all `Token` entities:
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+When querying a collection, you may:
+
+- 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.
 
 #### उदाहरण
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 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.
 
-In the following example, we sort the tokens by the name of their owner:
+The following example shows tokens sorted by the name of their owner:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ In the following example, we sort the tokens by the name of their owner:
 
 ### Pagination
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-Further, the `skip` parameter can be used to skip entities and paginate. e.g. `first:100` shows the first 100 entities and `first:100, skip:100` shows the next 100 entities.
+When querying a collection, it's best to:
 
-Queries should avoid using very large `skip` values since they generally perform poorly. For retrieving a large number of items, it is much better to page through entities based on an attribute as shown in the last example.
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
 
@@ -106,7 +118,7 @@ Query 10 `Token` entities, offset by 10 places from the beginning of the collect
 
 #### Example using `first` and `id_ge`
 
-If a client needs to retrieve a large number of entities, it is much more performant to base queries on an attribute and filter by that attribute. For example, a client would retrieve a large number of tokens using this query:
+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:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
 
 ### Filtering
 
-You can use the `where` parameter in your queries to filter for different properties. You can filter on mulltiple values within the `where` parameter.
+- 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`
 
@@ -155,7 +168,7 @@ You can use suffixes like `_gt`, `_lte` for value comparison:
 
 #### Example for block filtering
 
-You can also filter entities by the `_change_block(number_gte: Int)` - this filters entities which were updated in or after the specified block.
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ This can be useful if you are looking to fetch only entities whose child-level e
 
 ##### `AND` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -208,7 +221,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ In the following example, we are filtering for challenges with `outcome` `succee
 
 ##### `OR` Operator
 
-In the following example, we are filtering for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> 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.
 
 #### उदाहरण
 
@@ -322,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol | Operator | वर्णन |
-| --- | --- | --- |
-| `&` | `आणि` | For combining multiple search terms into a filter for entities that include all of the provided terms |
-| &#x7c; | `किंवा` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms |
-| `<->` | `द्वारे अनुसरण करा` | Specify the distance between two words. |
-| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) |
+| Symbol      | Operator            | वर्णन                                                                                                                                |
+| ----------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `&`     | `आणि`               | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
+| &#x7c;      | `किंवा`             | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms |
+| `<->` | `द्वारे अनुसरण करा` | Specify the distance between two words.                                                                                              |
+| `:*`        | `Prefix`            | Use the prefix search term to find words whose prefix match (2 characters required.)                                                 |
 
 #### Examples
 
@@ -376,11 +389,11 @@ Graph Node implements [specification-based](https://spec.graphql.org/October2021
 
 ## Schema
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+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 Langauge (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.
+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.
+> Note: Our API does not expose mutations because developers are expected to issue transactions directly against the underlying blockchain from their applications.
 
 ### Entities
 

From f261421b78fe4eb433d355107b0463024f867252 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:58 -0500
Subject: [PATCH 0367/1325] New translations graphql-api.mdx (Hindi)

---
 website/pages/hi/querying/graphql-api.mdx | 71 ++++++++++++++---------
 1 file changed, 42 insertions(+), 29 deletions(-)

diff --git a/website/pages/hi/querying/graphql-api.mdx b/website/pages/hi/querying/graphql-api.mdx
index f4fbbeaac0e1..cc4946bed045 100644
--- a/website/pages/hi/querying/graphql-api.mdx
+++ b/website/pages/hi/querying/graphql-api.mdx
@@ -2,11 +2,19 @@
 title: ग्राफक्यूएल एपीआई
 ---
 
-This guide explains the GraphQL Query API that is used for The Graph Protocol.
+The Graph में उपयोग किए जाने वाले GraphQL Query API के बारे में जानें।
 
-## Queries
+## GraphQL क्या है?
 
-अपने सबग्राफ स्कीमा में आप `Entities` नामक प्रकारों को परिभाषित करते हैं। प्रत्येक `एंटिटी` प्रकार के लिए, एक `एंटिटी` और `एंटियां` फ़ील्ड शीर्ष-स्तरीय `क्वेरी` प्रकार पर जेनरेट की जाएंगी। ध्यान दें कि ग्राफ़ का उपयोग करते समय `क्वेरी` को `graphql` क्वेरी के शीर्ष पर शामिल करने की आवश्यकता नहीं है।
+[GraphQL](https://graphql.org/learn/) APIs  के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है।
+
+GraphQL की बड़ी भूमिका को समझने के लिए, [developing](/network/developing/) और [creating a subgraph](/developing/creating-a-subgraph/) की समीक्षा करें।
+
+## GraphQL के साथ क्वेरीज़
+
+अपने subgraph schema में आप `Entities` नामक प्रकार को परिभाषित करते हैं। प्रत्येक `Entity` प्रकार के लिए, शीर्ष-स्तरीय `Query` प्रकार पर `entity` और `entities` फ़ील्ड उत्पन्न की जाएंगी।
+
+> नोट: The Graph का उपयोग करते समय `query` को `graphql` क्वेरी के शीर्ष पर शामिल करने की आवश्यकता नहीं है।
 
 ### उदाहरण
 
@@ -21,7 +29,7 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 }
 ```
 
-> **ध्यान दें:** किसी एक इकाई के लिए क्वेरी करते समय, `id` फ़ील्ड की आवश्यकता होती है, और यह एक स्ट्रिंग होना चाहिए।
+> नोट: एकल entity के लिए क्वेरी करते समय, `id` फ़ील्ड आवश्यक है, और इसे एक स्ट्रिंग के रूप में लिखा जाना चाहिए।
 
 सभी `टोकन` संस्थाओं को क्वेरी करें:
 
@@ -36,7 +44,10 @@ This guide explains the GraphQL Query API that is used for The Graph Protocol.
 
 ### Sorting
 
-When querying a collection, the `orderBy` parameter may be used to sort by a specific attribute. Additionally, the `orderDirection` can be used to specify the sort direction, `asc` for ascending or `desc` for descending.
+जब आप एक संग्रह के लिए क्वेरी कर रहे हों, तो आप:
+
+- `orderBy` पैरामीटर का उपयोग एक विशेष विशेषता के आधार पर क्रमबद्ध करने के लिए करें।
+- `orderDirection` का उपयोग क्रम के दिशा को निर्दिष्ट करने के लिए करें, `asc` के लिए आरोही या `desc` के लिए अवरोही।
 
 #### उदाहरण
 
@@ -53,7 +64,7 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 ग्राफ़ नोड के अनुसार [`v0.30.0`](https://github.com/graphprotocol/graph-node/releases/tag/v0.30.0) संस्थाओं को क्रमबद्ध किया जा सकता है नेस्टेड संस्थाओं के आधार पर।
 
-निम्नलिखित उदाहरण में, हम टोकन को उनके स्वामी के नाम से क्रमित करते हैं:
+निम्नलिखित उदाहरण में टोकन उनके मालिक के नाम के अनुसार क्रमबद्ध किए गए हैं:
 
 ```graphql
 {
@@ -70,11 +81,12 @@ When querying a collection, the `orderBy` parameter may be used to sort by a spe
 
 ### पृष्ठ पर अंक लगाना
 
-When querying a collection, the `first` parameter can be used to paginate from the beginning of the collection. It is worth noting that the default sort order is by ID in ascending alphanumeric order, not by creation time.
-
-इसके अलावा, `छोड़ें` पैरामीटर का उपयोग इकाइयों को छोड़ने और पेजिनेट करने के लिए किया जा सकता है। उदा. `first:100` पहले 100 इकाइयां दिखाता है और `first:100, skip:100` अगली 100 इकाइयां दिखाता है।
+जब एक संग्रह के लिए क्वेरी की जाती है, तो यह सबसे अच्छा होता है:
 
-प्रश्नों को बहुत बड़े उपयोग से बचना चाहिए `छोड़ें` मान क्योंकि वे आम तौर पर खराब प्रदर्शन करते हैं। बड़ी संख्या में आइटम प्राप्त करने के लिए, पिछले उदाहरण में दिखाए गए विशेषता के आधार पर संस्थाओं के माध्यम से पृष्ठ बनाना बेहतर है।
+- `first` पैरामीटर का उपयोग करें ताकि संग्रह के शुरू से पेजिनेट किया जा सके।
+  - डिफ़ॉल्ट क्रम `ID` के अनुसार बढ़ते अल्फ़ान्यूमेरिक क्रम में होता है, **नहीं** कि निर्माण समय के अनुसार।
+- `skip` पैरामीटर का उपयोग करके एंटिटीज़ को छोड़ें और पृष्ठांकन करें। उदाहरण के लिए, `first:100` पहले 100 एंटिटीज़ दिखाता है और `first:100, skip:100` अगली 100 एंटिटीज़ दिखाता है।
+- `skip` मानों का उपयोग करने से बचें क्योंकि ये सामान्यतः खराब प्रदर्शन करते हैं। एक बड़े संख्या में आइटम को पुनः प्राप्त करने के लिए, एंटिटीज़ के आधार पर एक गुण के माध्यम से पृष्ठांकन करना सबसे अच्छा है, जैसा कि ऊपर के पिछले उदाहरण में दिखाया गया है।
 
 #### उदाहरण का उपयोग करना `पहले`
 
@@ -93,7 +105,7 @@ When querying a collection, the `first` parameter can be used to paginate from t
 
 #### उदाहरण का उपयोग करना `पहले` और `छोड़ें`
 
-क्वेरी 10 `टोकन` इकाइयां, संग्रह की शुरुआत से 10 स्थानों से ऑफसेट:
+क्वेरी 10 ` टोकन ` इकाइयां, संग्रह की शुरुआत से 10 स्थानों से ऑफसेट:
 
 ```graphql
 {
@@ -106,7 +118,7 @@ When querying a collection, the `first` parameter can be used to paginate from t
 
 #### उदाहरण का उपयोग करना `पहले` और ` id_ge`
 
-यदि किसी ग्राहक को बड़ी संख्या में संस्थाओं को पुनः प्राप्त करने की आवश्यकता होती है, तो यह एक विशेषता पर आधार क्वेरी और उस विशेषता द्वारा फ़िल्टर करने के लिए बहुत अधिक प्रदर्शनकारी होता है। उदाहरण के लिए, क्लाइंट इस क्वेरी का उपयोग करके बड़ी संख्या में टोकन प्राप्त करेगा:
+यदि एक क्लाइंट को बड़ी संख्या में एंटिटीज़ पुनर्प्राप्त करने की आवश्यकता है, तो एट्रिब्यूट पर आधारित क्वेरी बनाना और उस एट्रिब्यूट द्वारा फ़िल्टर करना अधिक प्रभावशाली है। उदाहरण के लिए, एक क्लाइंट इस क्वेरी का उपयोग करके बड़ी संख्या में टोकन पुनर्प्राप्त कर सकता है:
 
 ```graphql
 query manyTokens($lastID: String) {
@@ -117,11 +129,12 @@ query manyTokens($lastID: String) {
 }
 ```
 
-The first time, it would send the query with `lastID = ""`, and for subsequent requests would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+पहली बार, यह `lastID = ""` के साथ क्वेरी भेजेगा, और अगले अनुरोधों के लिए यह `lastID` को पिछले अनुरोध में अंतिम एंटिटी के `id` एट्रिब्यूट पर सेट करेगा। यह दृष्टिकोण बढ़ते `skip` मानों का उपयोग करने की तुलना में काफी बेहतर प्रदर्शन करेगा।
 
 ### छनन
 
-आप अपनी क्वेरी में `कहाँ` पैरामीटर का उपयोग विभिन्न गुणों के लिए फ़िल्टर करने के लिए कर सकते हैं। आप `जहां` पैरामीटर के भीतर एकाधिक मानों पर फ़िल्टर कर सकते हैं।
+- आप अपनी क्वेरियों में विभिन्न गुणों के लिए फ़िल्टर करने के लिए `where` पैरामीटर का उपयोग कर सकते हैं।
+- आप `where` पैरामीटर के भीतर कई मानों पर फ़िल्टर कर सकते हैं।
 
 #### उदाहरण का उपयोग करना `कहाँ`
 
@@ -155,7 +168,7 @@ The first time, it would send the query with `lastID = ""`, and for subsequent r
 
 #### ब्लॉक फ़िल्टरिंग के लिए उदाहरण
 
-आप `_change_block(number_gte: Int)` द्वारा संस्थाओं को भी फ़िल्टर कर सकते हैं - यह उन संस्थाओं को फ़िल्टर करता है जिन्हें निर्दिष्ट ब्लॉक में या उसके बाद अपडेट किया गया था।
+आप `_change_block(number_gte: Int)` के साथ उन एंटिटीज़ को भी फ़िल्टर कर सकते हैं जो किसी निर्दिष्ट ब्लॉक में या उसके बाद अपडेट की गई थीं।
 
 This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
 
@@ -193,7 +206,7 @@ This can be useful if you are looking to fetch only entities which have changed,
 
 ##### `AND` Operator
 
-निम्नलिखित उदाहरण में, हम `परिणाम` `सफल` और `number` `100` से अधिक या उसके बराबर वाली चुनौतियों के लिए फ़िल्टर कर रहे हैं।
+निम्नलिखित उदाहरण में उन चुनौतियों को फ़िल्टर किया गया है जिनका `outcome` `succeeded` है और `number` `100` के बराबर या उससे अधिक है।
 
 ```graphql
 {
@@ -208,7 +221,7 @@ This can be useful if you are looking to fetch only entities which have changed,
 ```
 
 > **सिंटैक्टिक शुगर:** आप `और` ऑपरेटर को कॉमा द्वारा अलग किए गए सब-एक्सप्रेशन को पास करके उपरोक्त क्वेरी को सरल बना सकते हैं।
->
+> 
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -223,7 +236,7 @@ This can be useful if you are looking to fetch only entities which have changed,
 
 ##### `OR` Operator
 
-निम्नलिखित उदाहरण में, हम `परिणाम` `सफल` या `number` `100` से अधिक या उसके बराबर वाली चुनौतियों के लिए फ़िल्टर कर रहे हैं।
+निम्नलिखित उदाहरण `outcome` `succeeded` या `number` जो `100` के बराबर या उससे अधिक है, के लिए चुनौतियों को फ़िल्टर करता है।
 
 ```graphql
 {
@@ -278,9 +291,9 @@ _change_block(number_gte: Int)
 
 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.
 
-The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to not be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+ऐसी क्वेरी का परिणाम समय के साथ नहीं बदलेगा, यानी, किसी निश्चित अतीत के ब्लॉक पर क्वेरी करने से वही परिणाम मिलेगा चाहे इसे कब भी निष्पादित किया जाए, इसके अलावा यदि आप किसी ब्लॉक पर क्वेरी करते हैं जो श्रृंखला के सिर के बहुत करीब है, तो परिणाम बदल सकता है यदि वह ब्लॉक मुख्य श्रृंखला पर **नहीं** है और श्रृंखला फिर से संगठित हो जाती है। एक बार जब एक ब्लॉक को अंतिम माना जा सकता है, तो क्वेरी का परिणाम नहीं बदलेगा।
 
-Note that the current implementation is still subject to certain limitations that might violate these gurantees. The implementation can not always tell that a given block hash is not on the main chain at all, or that the result of a query by block hash for a block that can not be considered final yet might 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.
+> नोट: वर्तमान कार्यान्वयन अभी भी कुछ सीमाओं के अधीन है जो इन गारंटी का उल्लंघन कर सकती हैं। कार्यान्वयन हमेशा यह नहीं बता सकता कि एक निर्दिष्ट ब्लॉक हैश मुख्य श्रृंखला पर 'नहीं' है, या यदि किसी ब्लॉक हैश द्वारा क्वेरी परिणाम एक ब्लॉक के लिए है जो अभी अंतिम नहीं माना गया है, तो यह क्वेरी के साथ समांतर चल रहे ब्लॉक पुनर्गठन से प्रभावित हो सकता है। ये उन क्वेरी के परिणामों को प्रभावित नहीं करते हैं जो ब्लॉक हैश द्वारा अंतिम और मुख्य श्रृंखला पर ज्ञात होते हैं। [यह समस्या](https://github.com/graphprotocol/graph-node/issues/1405) विस्तार से बताती है कि ये सीमाएँ क्या हैं।
 
 #### उदाहरण
 
@@ -322,12 +335,12 @@ Fulltext search query fields provide an expressive text search API that can be a
 
 पूर्ण पाठ खोज ऑपरेटर:
 
-| प्रतीक | ऑपरेटर | विवरण |
-| --- | --- | --- |
-| `&` | `And` | सभी प्रदान किए गए शब्दों को शामिल करने वाली संस्थाओं के लिए एक से अधिक खोज शब्दों को फ़िल्टर में संयोजित करने के लिए |
-| &#x7c; | `Or` | या ऑपरेटर द्वारा अलग किए गए एकाधिक खोज शब्दों वाली क्वेरी सभी संस्थाओं को प्रदान की गई शर्तों में से किसी से मेल के साथ वापस कर देगी |
-| `<->` | `Follow by` | दो शब्दों के बीच की दूरी निर्दिष्ट करें। |
-| `:*` | `Prefix` | उन शब्दों को खोजने के लिए उपसर्ग खोज शब्द का उपयोग करें जिनके उपसर्ग मेल खाते हैं (2 वर्ण आवश्यक हैं।) |
+| प्रतीक      | ऑपरेटर      | विवरण                                                                                                                                |
+| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `&`     | `And`       | सभी प्रदान किए गए शब्दों को शामिल करने वाली संस्थाओं के लिए एक से अधिक खोज शब्दों को फ़िल्टर में संयोजित करने के लिए                 |
+| &#x7c;      | `Or`        | या ऑपरेटर द्वारा अलग किए गए एकाधिक खोज शब्दों वाली क्वेरी सभी संस्थाओं को प्रदान की गई शर्तों में से किसी से मेल के साथ वापस कर देगी |
+| `<->` | `Follow by` | दो शब्दों के बीच की दूरी निर्दिष्ट करें।                                                                                             |
+| `:*`        | `Prefix`    | उन शब्दों को खोजने के लिए उपसर्ग खोज शब्द का उपयोग करें जिनके उपसर्ग मेल खाते हैं (2 वर्ण आवश्यक हैं।)                               |
 
 #### उदाहरण
 
@@ -376,11 +389,11 @@ Combine fulltext operators to make more complex filters. With a pretext search o
 
 ## योजना
 
-The schema of your data source--that is, the entity types, values, and relationships that are available to query--are defined through the [GraphQL Interface Definition Langauge (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System).
+आपके डेटा स्रोत की स्कीमा - यानी, इकाई प्रकार, मान और संबंध जो क्वेरी के लिए उपलब्ध हैं - को [GraphQL इंटरफ़ेस डेफिनिशन लैंग्वेज (IDL)](https://facebook.github.io/graphql/draft/#sec-Type-System) के माध्यम से परिभाषित किया गया है।
 
-ग्राफक्यूएल स्कीमा आम तौर पर `क्वेरी`, `सदस्यता` और `म्यूटेशन` के रूट प्रकारों को परिभाषित करते हैं। ग्राफ़ केवल `क्वेरी` का समर्थन करता है। आपके सबग्राफ के लिए रूट `क्वेरी` प्रकार स्वचालित रूप से आपके सबग्राफ मेनिफ़ेस्ट में शामिल ग्राफ़क्यूएल स्कीमा से उत्पन्न होता है।
+ग्राफक्यूएल स्कीमा आम तौर पर `क्वेरी`, `सदस्यता` और `म्यूटेशन` के रूट प्रकारों को परिभाषित करते हैं। ग्राफ़ केवल `क्वेरी` का समर्थन करता है। आपके सबग्राफ के लिए रूट `क्वेरी` प्रकार स्वचालित रूप से आपके [Subgraph manifest](/developing/creating-a-subgraph/#components-of-a-subgraph). में शामिल ग्राफ़क्यूएल स्कीमा से उत्पन्न होता है।
 
-> **ध्यान दें:** हमारा एपीआई म्यूटेशन को उजागर नहीं करता है क्योंकि डेवलपर्स से उम्मीद की जाती है कि वे अपने एप्लिकेशन से अंतर्निहित ब्लॉकचेन के खिलाफ सीधे लेनदेन जारी करेंगे।
+> ध्यान दें: हमारा एपीआई म्यूटेशन को उजागर नहीं करता है क्योंकि डेवलपर्स से उम्मीद की जाती है कि वे अपने एप्लिकेशन से अंतर्निहित ब्लॉकचेन के खिलाफ सीधे लेन-देन(transaction) जारी करेंगे।
 
 ### Entities
 

From 0383e169de58f839d3f748544e6968133525eb7a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:37:59 -0500
Subject: [PATCH 0368/1325] New translations graphql-api.mdx (Swahili)

---
 website/pages/sw/querying/graphql-api.mdx | 432 ++++++++++++++++++++++
 1 file changed, 432 insertions(+)
 create mode 100644 website/pages/sw/querying/graphql-api.mdx

diff --git a/website/pages/sw/querying/graphql-api.mdx b/website/pages/sw/querying/graphql-api.mdx
new file mode 100644
index 000000000000..d8671e53a77c
--- /dev/null
+++ b/website/pages/sw/querying/graphql-api.mdx
@@ -0,0 +1,432 @@
+---
+title: GraphQL API
+---
+
+Learn about the GraphQL Query API used in The Graph.
+
+## 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](/network/developing/) and [creating a subgraph](/developing/creating-a-subgraph/).
+
+## 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.
+
+> Note: `query` does not need to be included at the top of the `graphql` query when using The Graph.
+
+### Examples
+
+Query for a single `Token` entity defined in your schema:
+
+```graphql
+{
+  token(id: "1") {
+    id
+    owner
+  }
+}
+```
+
+> Note: When querying for a single entity, the `id` field is required, and it must be writen as a string.
+
+Query all `Token` entities:
+
+```graphql
+{
+  tokens {
+    id
+    owner
+  }
+}
+```
+
+### Sorting
+
+When querying a collection, you may:
+
+- 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.
+
+#### Example
+
+```graphql
+{
+  tokens(orderBy: price, orderDirection: asc) {
+    id
+    owner
+  }
+}
+```
+
+#### 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.
+
+The following example shows tokens sorted by the name of their owner:
+
+```graphql
+{
+  tokens(orderBy: owner__name, orderDirection: asc) {
+    id
+    owner {
+      name
+    }
+  }
+}
+```
+
+> Currently, you can sort by one-level deep `String` or `ID` types on `@entity` and `@derivedFrom` fields. Unfortunately, [sorting by interfaces on one level-deep entities](https://github.com/graphprotocol/graph-node/pull/4058), sorting by fields which are arrays and nested entities is not yet supported.
+
+### Pagination
+
+When querying a collection, it's best to:
+
+- Use the `first` parameter to paginate from the beginning of the collection.
+  - The default sort order is by `ID` in ascending alphanumeric order, **not** by creation time.
+- 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`
+
+Query the first 10 tokens:
+
+```graphql
+{
+  tokens(first: 10) {
+    id
+    owner
+  }
+}
+```
+
+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.
+
+#### Example using `first` and `skip`
+
+Query 10 `Token` entities, offset by 10 places from the beginning of the collection:
+
+```graphql
+{
+  tokens(first: 10, skip: 10) {
+    id
+    owner
+  }
+}
+```
+
+#### 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:
+
+```graphql
+query manyTokens($lastID: String) {
+  tokens(first: 1000, where: { id_gt: $lastID }) {
+    id
+    owner
+  }
+}
+```
+
+The first time, it would send the query with `lastID = ""`, and for subsequent requests it would set `lastID` to the `id` attribute of the last entity in the previous request. This approach will perform significantly better than using increasing `skip` values.
+
+### Filtering
+
+- 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`
+
+Query challenges with `failed` outcome:
+
+```graphql
+{
+  challenges(where: { outcome: "failed" }) {
+    challenger
+    outcome
+    application {
+      id
+    }
+  }
+}
+```
+
+You can use suffixes like `_gt`, `_lte` for value comparison:
+
+#### Example for range filtering
+
+```graphql
+{
+  applications(where: { deposit_gt: "10000000000" }) {
+    id
+    whitelisted
+    deposit
+  }
+}
+```
+
+#### Example for block filtering
+
+You can also filter entities that were updated in or after a specified block with `_change_block(number_gte: Int)`.
+
+This can be useful if you are looking to fetch only entities which have changed, for example since the last time you polled. Or alternatively it can be useful to investigate or debug how entities are changing in your subgraph (if combined with a block filter, you can isolate only entities that changed in a specific block).
+
+```graphql
+{
+  applications(where: { _change_block: { number_gte: 100 } }) {
+    id
+    whitelisted
+    deposit
+  }
+}
+```
+
+#### Example for nested entity filtering
+
+Filtering on the basis of nested entities is possible in the fields with the `_` suffix.
+
+This can be useful if you are looking to fetch only entities whose child-level entities meet the provided conditions.
+
+```graphql
+{
+  challenges(where: { application_: { id: 1 } }) {
+    challenger
+    outcome
+    application {
+      id
+    }
+  }
+}
+```
+
+#### 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
+
+The following example filters for challenges with `outcome` `succeeded` and `number` greater than or equal to `100`.
+
+```graphql
+{
+  challenges(where: { and: [{ number_gte: 100 }, { outcome: "succeeded" }] }) {
+    challenger
+    outcome
+    application {
+      id
+    }
+  }
+}
+```
+
+> **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
+> 
+> ```graphql
+> {
+>   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
+>     challenger
+>     outcome
+>     application {
+>       id
+>     }
+>   }
+> }
+> ```
+
+##### `OR` Operator
+
+The following example filters for challenges with `outcome` `succeeded` or `number` greater than or equal to `100`.
+
+```graphql
+{
+  challenges(where: { or: [{ number_gte: 100 }, { outcome: "succeeded" }] }) {
+    challenger
+    outcome
+    application {
+      id
+    }
+  }
+}
+```
+
+> **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.
+
+#### All Filters
+
+Full list of parameter suffixes:
+
+```
+_
+_not
+_gt
+_lt
+_gte
+_lte
+_in
+_not_in
+_contains
+_contains_nocase
+_not_contains
+_not_contains_nocase
+_starts_with
+_starts_with_nocase
+_ends_with
+_ends_with_nocase
+_not_starts_with
+_not_starts_with_nocase
+_not_ends_with
+_not_ends_with_nocase
+```
+
+> Please note that some suffixes are only supported for specific types. For example, `Boolean` only supports `_not`, `_in`, and `_not_in`, but `_` is available only for object and interface types.
+
+In addition, the following global filters are available as part of `where` argument:
+
+```gr
+_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.
+
+The result of such a query will not change over time, i.e., querying at a certain past block will return the same result no matter when it is executed, with the exception that if you query at a block very close to the head of the chain, the result might change if that block turns out to **not** be on the main chain and the chain gets reorganized. Once a block can be considered final, the result of the query will not change.
+
+> 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
+
+```graphql
+{
+  challenges(block: { number: 8000000 }) {
+    challenger
+    outcome
+    application {
+      id
+    }
+  }
+}
+```
+
+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" }) {
+    challenger
+    outcome
+    application {
+      id
+    }
+  }
+}
+```
+
+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
+
+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.
+
+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.
+
+Fulltext search operators:
+
+| Symbol      | Operator    | Description                                                                                                                          |
+| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
+| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
+| &#x7c;      | `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
+
+Using the `or` operator, this query will filter to blog entities with variations of either "anarchism" or "crumpet" in their fulltext fields.
+
+```graphql
+{
+  blogSearch(text: "anarchism | crumpets") {
+    id
+    title
+    body
+    author
+  }
+}
+```
+
+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"
+
+```graphql
+{
+  blogSearch(text: "decentralized <-> philosophy") {
+    id
+    title
+    body
+    author
+  }
+}
+```
+
+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".
+
+```graphql
+{
+  blogSearch(text: "lou:* <-> music") {
+    id
+    title
+    body
+    author
+  }
+}
+```
+
+### Validation
+
+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 Langauge (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:
+
+```graphQL
+{
+  _meta(block: { number: 123987 }) {
+    block {
+      number
+      hash
+      timestamp
+    }
+    deployment
+    hasIndexingErrors
+  }
+}
+```
+
+If a block is provided, the metadata is as of that block, if not the latest indexed block is used. If provided, the block must be after the subgraph's start block, and less than or equal to the most recently indexed block.
+
+`deployment` is a unique ID, corresponding to the IPFS CID of the `subgraph.yaml` file.
+
+`block` provides information about the latest block (taking into account any block constraints passed to `_meta`):
+
+- hash: the hash of the block
+- number: the block number
+- timestamp: the timestamp of the block, if available (this is currently only available for subgraphs indexing EVM networks)
+
+`hasIndexingErrors` is a boolean identifying whether the subgraph encountered indexing errors at some past block

From efb348d2c3efc8b7a0f3bb094657b6a1f521b67c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:01 -0500
Subject: [PATCH 0369/1325] New translations querying-best-practices.mdx
 (Hindi)

---
 .../hi/querying/querying-best-practices.mdx   | 95 +++++++++----------
 1 file changed, 45 insertions(+), 50 deletions(-)

diff --git a/website/pages/hi/querying/querying-best-practices.mdx b/website/pages/hi/querying/querying-best-practices.mdx
index d78720b40001..8480616c578f 100644
--- a/website/pages/hi/querying/querying-best-practices.mdx
+++ b/website/pages/hi/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: सर्वोत्तम प्रथाओं को क्वेरी करना
 ---
 
-ग्राफ़ ब्लॉकचेन से डेटा क्वेरी करने के लिए विकेंद्रीकृत तरीका प्रदान करता है।
+The Graph ब्लॉकचेन से डेटा क्वेरी करने का एक विकेन्द्रीकृत तरीका प्रदान करता है। इसका डेटा एक GraphQL API के माध्यम से एक्सपोज़ किया जाता है, जिससे इसे GraphQL भाषा के साथ क्वेरी करना आसान हो जाता है।
 
-ग्राफ़ नेटवर्क के डेटा को ग्राफ़िकल एपीआई के माध्यम से उजागर किया जाता है, जिससे ग्राफ़िकल भाषा के साथ डेटा को क्वेरी करना आसान हो जाता है।
-
-यह पृष्ठ आवश्यक ग्राफ़िकल भाषा नियमों और ग्राफ़कॉल प्रश्नों के सर्वोत्तम अभ्यासों के माध्यम से आपका मार्गदर्शन करेगा।
+GraphQL भाषा के आवश्यक नियमों और सर्वोत्तम प्रथाओं को सीखें ताकि आप अपने subgraph को अनुकूलित कर सकें।
 
 ---
 
 ## ग्राफ़कॉल एपीआई को क्वेरी करना
 
-### एक ग्राफक्यूएल क्वेरी की शारीरिक रचना
+### GraphQL Query की संरचना
 
 REST API के विपरीत, एक रेखांकन API एक स्कीमा पर बनाया गया है जो परिभाषित करता है कि कौन से प्रश्न किए जा सकते हैं।
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-जबकि सिंटैक्टिक डू और डॉनट्स की सूची लंबी है, ग्राफक्यूएल प्रश्नों को लिखते समय ध्यान में रखने के लिए आवश्यक नियम यहां दिए गए हैं:
+## GraphQL क्वेरी लिखने के नियम
 
 - प्रत्येक `क्वेरीनाम` का उपयोग प्रति ऑपरेशन केवल एक बार किया जाना चाहिए।
 - प्रत्येक `फ़ील्ड` का चयन में केवल एक बार उपयोग किया जाना चाहिए (हम `आईडी` को `टोकन` के अंतर्गत दो बार क्वेरी नहीं कर सकते हैं)
@@ -61,24 +59,24 @@ query [operationName]([variableName]: [variableType]) {
 - चरों की दी गई सूची में, उनमें से प्रत्येक अद्वितीय होना चाहिए।
 - सभी परिभाषित चर का उपयोग किया जाना चाहिए।
 
-उपरोक्त नियमों का पालन करने में विफल रहने पर ग्राफ़ एपीआई की त्रुटि समाप्त हो जाएगी।
+> ध्यान दें: इन नियमों का पालन न करने पर The Graph API से त्रुटि होगी।
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+नियमों की पूरी सूची और कोड उदाहरणों के लिए, [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/) देखें।
 
 ### एक ग्राफ़क्यूएल एपीआई के लिए एक प्रश्न भेजना
 
-GraphQL is a language and set of conventions that transport over HTTP.
+GraphQL एक भाषा और प्रथाओं का सेट है जो HTTP के माध्यम से संचालित होता है।
 
-It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
+इसका मतलब है कि आप एक GraphQL API को मानक `fetch` (स्थानीय रूप से या `@whatwg-node/fetch` या `isomorphic-fetch` के माध्यम से) का उपयोग करके क्वेरी कर सकते हैं।
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+हालांकि, जैसा कि [“Querying from an Application”](/querying/querying-from-an-application) में उल्लेख किया गया है, यह अनुशंसा की जाती है कि आप `graph-client` का उपयोग करें, जो निम्नलिखित अद्वितीय विशेषताओं का समर्थन करता है:
 
 - क्रॉस-चेन सबग्राफ हैंडलिंग: एक ही क्वेरी में कई सबग्राफ से पूछताछ
 - [स्वचालित ब्लॉक ट्रैकिंग](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [स्वचालित पृष्ठांकन](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - पूरी तरह से टाइप किया गया परिणाम
 
-Here's how to query The Graph with `graph-client`:
+यहाँ बताया गया है कि `graph-client` के साथ The Graph को कैसे क्वेरी किया जाए:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
-
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
+अधिक GraphQL क्लाइंट विकल्पों को [“Querying from an Application”](/querying/querying-from-an-application) में कवर किया गया है।
 
 ---
 
@@ -112,7 +108,7 @@ Now that we covered the basic rules of GraphQL queries syntax, let's now look at
 
 ### हमेशा स्टैटिक क्वेश्चन लिखें
 
-A common (bad) practice is to dynamically build query strings as follows:
+एक सामान्य (खराब) प्रथा है कि क्वेरी स्ट्रिंग्स को निम्नलिखित तरीके से गतिशील रूप से बनाया जाए:
 
 ```tsx
 const id = params.id
@@ -126,14 +122,14 @@ query GetToken {
 `
 ```
 
-While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
+जबकि उपरोक्त स्निप्पेट एक मान्य GraphQL क्वेरी उत्पन्न करता है, **इसमें कई कमियाँ हैं**:
 
 - यह संपूर्ण क्वेरी को **समझने में कठिन** बनाता है
 - डेवलपर **स्ट्रिंग इंटरपोलेशन को सुरक्षित रूप से साफ़ करने के लिए ज़िम्मेदार हैं**
 - अनुरोध पैरामीटर ** सर्वर-साइड पर संभावित कैशिंग को रोकें** के हिस्से के रूप में चर के मान नहीं भेज रहे हैं
 - यह **टूल्स को क्वेरी का स्थिर रूप से विश्लेषण करने से रोकता है** (उदा: लिंटर, या टाइप जेनरेशन टूल्स)
 
-For this reason, it is recommended to always write queries as static strings:
+इसी कारण, यह अनुशंसा की जाती है कि हमेशा क्वेरीज़ को स्थिर स्ट्रिंग्स के रूप में लिखा जाए।
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -155,18 +151,18 @@ const result = await execute(query, {
 })
 ```
 
-Doing so brings **many advantages**:
+इससे **कई लाभ** मिलते हैं:
 
 - **पढ़ने और बनाए रखने में आसान** क्वेरीज़
 - ग्राफ़क्यूएल **सर्वर वेरिएबल सैनिटाइज़ेशन को हैंडल करता है**
 - सर्वर-स्तर पर **वैरिएबल को कैश किया जा सकता है**
 - **क्वेरी का सांख्यिकीय रूप से विश्लेषण टूल द्वारा किया जा सकता है** (निम्न अनुभागों में इस पर अधिक)
 
-**Note: How to include fields conditionally in static queries**
+### स्टेटिक क्वेरीज़ में फ़ील्ड्स को शर्तानुसार कैसे शामिल करें
 
-We might want to include the `owner` field only on a particular condition.
+हो सकता है कि हम `स्वामी` फ़ील्ड को केवल किसी विशेष स्थिति में शामिल करना चाहें।
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+इसके लिए, हम `@include(if:...)` निर्देश का लाभ इस प्रकार उठा सकते हैं:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -189,17 +185,16 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> नोट: विपरीत निर्देश है `@skip(if: ...)`।
 
-### Ask for what you want
+### आप जो चाहते हैं वह मांगें
 
 GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- सुनिश्चित करें कि क्वेरीज़ केवल उतने ही एंटिटीज़ लाएँ जितनी आपको वास्तव में आवश्यकता है। डिफ़ॉल्ट रूप से, क्वेरीज़ एक संग्रह में 100 एंटिटीज़ लाएँगी, जो आमतौर पर उपयोग में लाई जाने वाली मात्रा से अधिक होती है, जैसे कि उपयोगकर्ता को प्रदर्शित करने के लिए। यह न केवल एक क्वेरी में शीर्ष-स्तरीय संग्रहों पर लागू होता है, बल्कि एंटिटीज़ के नेस्टेड संग्रहों पर भी अधिक लागू होता है।
 
 For example, in the following query:
 
@@ -220,7 +215,7 @@ The response could contain 100 transactions for each of the 100 tokens.
 
 If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
-### Use a single query to request multiple records
+### एक ही क्वेरी का उपयोग करके कई रिकॉर्ड्स का अनुरोध करें
 
 By default, subgraphs have a singular entity for one record. For multiple records, use the plural entities and filter: `where: {id_in:[X,Y,Z]}` or `where: {volume_gt:100000}`
 
@@ -252,7 +247,7 @@ query ManyRecords {
 }
 ```
 
-### Combine multiple queries in a single request
+### एकल अनुरोध में कई क्वेरियों को संयोजित करें।
 
 Your application might require querying multiple types of data as follows:
 
@@ -335,8 +330,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- अधिक व्यापक प्रश्नों के लिए पढ़ना कठिन है
-- प्रश्नों के आधार पर टाइपस्क्रिप्ट प्रकार उत्पन्न करने वाले टूल का उपयोग करते समय (_उस पर अधिक पिछले खंड में_), `newDelegate` और `oldDelegate` के परिणामस्वरूप दो अलग-अलग इनलाइन होंगे इंटरफेस।
+- बड़ी क्वेरीज़ पढ़ने में कठिन होती हैं।
+- जब ऐसे उपकरणों का उपयोग किया जाता है जो क्वेरी के आधार पर TypeScript प्रकार उत्पन्न करते हैं (_अंतिम अनुभाग में इसके बारे में अधिक_), तो ``newDelegate`\` और ``oldDelegate`\` दो अलग-अलग इनलाइन इंटरफेस का परिणाम देंगे।
 
 A refactored version of the query would be the following:
 
@@ -362,13 +357,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### ग्राफकॉल फ्रैगमेंट क्या करें और क्या न करें
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -380,7 +375,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -409,16 +404,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- जब किसी क्वेरी में एक ही प्रकार के फ़ील्ड दोहराए जाते हैं, तो उन्हें एक फ़्रैगमेंट में समूहित करें
-- जब समान लेकिन समान फ़ील्ड दोहराए जाते हैं, तो एकाधिक टुकड़े बनाएं, उदा:
+- जब एक क्वेरी में समान प्रकार के फ़ील्ड्स को दोहराया जाए, तो उन्हें `Fragment` में समूहित करें।
+- जब समान लेकिन भिन्न फ़ील्ड्स को दोहराया जाता है, तो कई फ़्रैगमेंट्स बनाएं, उदाहरण के लिए:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -441,7 +436,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## आवश्यक उपकरण
+## The Essential Tools
 
 ### ग्राफक्यूएल वेब-आधारित खोजकर्ता
 
@@ -471,11 +466,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- वाक्य - विन्यास पर प्रकाश डालना
-- स्वत: पूर्ण सुझाव
-- स्कीमा के खिलाफ सत्यापन
-- snippets
-- अंशों और इनपुट प्रकारों के लिए परिभाषा पर जाएं
+- सिंटैक्स हाइलाइटिंग
+- ऑटो-कंप्लीट सुझाव
+- स्कीमा के खिलाफ मान्यता
+- निबंध
+- फ्रैगमेंट्स और इनपुट टाइप्स के लिए परिभाषा पर जाएं।
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -483,9 +478,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- वाक्य - विन्यास पर प्रकाश डालना
-- स्वत: पूर्ण सुझाव
-- स्कीमा के खिलाफ सत्यापन
-- snippets
+- सिंटैक्स हाइलाइटिंग
+- ऑटो-कंप्लीट सुझाव
+- स्कीमा के खिलाफ मान्यता
+- निबंध
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 17a632e894f687ac6e4ab3d2286f18192ea23ecc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:02 -0500
Subject: [PATCH 0370/1325] New translations api.mdx (Vietnamese)

---
 website/pages/vi/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/vi/developing/graph-ts/api.mdx b/website/pages/vi/developing/graph-ts/api.mdx
index 5cf44ec93b76..cff2389b0279 100644
--- a/website/pages/vi/developing/graph-ts/api.mdx
+++ b/website/pages/vi/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: AssemblyScript API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-This page documents what built-in APIs can be used when writing subgraph mappings. Two kinds of APIs are available out of the box:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## Tham chiếu API
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Phiên bản | Ghi chú phát hành |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| Phiên bản | Ghi chú phát hành                                                                                                                                                                                                                             |
+| :-------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|   0.0.9   | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|   0.0.8   | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|   0.0.7   | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|   0.0.6   | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|   0.0.5   | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|   0.0.4   | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|   0.0.3   | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|   0.0.2   | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### Các loại cài sẵn
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used. Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### Loading entities from the store
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### Looking up entities created withing a block
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ Any other contract that is part of the subgraph can be imported from the generat
 
 #### Xử lý các lệnh gọi được hoàn nguyên
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-Note that a Graph node connected to a Geth or Infura client may not detect all reverts, if you rely on this we recommend using a Graph node connected to a Parity client.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### Mã hóa / Giải mã ABI
 

From 3688bebc1d0286f47530a0f970c12964fb0cd676 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:03 -0500
Subject: [PATCH 0371/1325] New translations api.mdx (Marathi)

---
 website/pages/mr/developing/graph-ts/api.mdx | 51 ++++++++++++--------
 1 file changed, 30 insertions(+), 21 deletions(-)

diff --git a/website/pages/mr/developing/graph-ts/api.mdx b/website/pages/mr/developing/graph-ts/api.mdx
index 56a87f6b95a3..36c6c0e9db2d 100644
--- a/website/pages/mr/developing/graph-ts/api.mdx
+++ b/website/pages/mr/developing/graph-ts/api.mdx
@@ -2,14 +2,16 @@
 title: असेंबलीस्क्रिप्ट API
 ---
 
-> Note: if you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, you're using an older version of AssemblyScript, we recommend taking a look at the [`Migration Guide`](/release-notes/assemblyscript-migration-guide)
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
 
-सबग्राफ मॅपिंग लिहिताना कोणते अंगभूत API वापरले जाऊ शकतात हे हे पृष्ठ दस्तऐवजीकरण करते. बॉक्सच्या बाहेर दोन प्रकारचे API उपलब्ध आहेत:
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
 
-- the [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`) and
-- code generated from subgraph files by `graph codegen`.
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
 
-It is also possible to add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript). Since this is the language mappings are written in, the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki) is a good source for language and standard library features.
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
 
 ## API संदर्भ
 
@@ -27,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| आवृत्ती | रिलीझ नोट्स |
-| :-: | --- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
-| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object |
+| आवृत्ती | रिलीझ नोट्स                                                                                                                                                                                                                                   |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
 
 ### अंगभूत प्रकार
 
@@ -252,7 +254,9 @@ export function handleTransfer(event: TransferEvent): void {
 
 When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
 
-इतर घटकांशी टक्कर टाळण्यासाठी प्रत्येक घटकाकडे एक अद्वितीय आयडी असणे आवश्यक आहे. इव्हेंट पॅरामीटर्समध्ये वापरला जाऊ शकणारा एक अद्वितीय अभिज्ञापक समाविष्ट करणे सामान्य आहे. टीप: आयडी म्हणून ट्रान्झॅक्शन हॅश वापरणे हे गृहित धरते की समान व्यवहारातील इतर कोणत्याही इव्हेंटमध्ये या हॅशसह आयडी म्हणून अस्तित्व निर्माण होत नाही.
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
 
 #### स्टोअरमधून घटक लोड करत आहे
 
@@ -268,15 +272,18 @@ if (transfer == null) {
 // Use the Transfer entity as before
 ```
 
-As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may thus be necessary to check for the `null` case before using the value.
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
 
-> **Note:** Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
 
 #### ब्लॉकसह तयार केलेल्या संस्था शोधत आहे
 
 As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
 
-The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a Transaction from some on-chain event, and a later handler wants to access this transaction if it exists. In the case where the transaction does not exist, the subgraph will have to go to the database just to find out that the entity does not exist; if the subgraph author already knows that the entity must have been created in the same block, using loadInBlock avoids this database roundtrip. For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
 let id = event.transaction.hash // or however the ID is constructed
@@ -503,7 +510,9 @@ As long as the `ERC20Contract` on Ethereum has a public read-only function calle
 
 #### रिव्हर्ट केलेले कॉल हाताळणे
 
-If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`. For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
 let gravity = Gravity.bind(event.address)
@@ -515,7 +524,7 @@ if (callResult.reverted) {
 }
 ```
 
-लक्षात ठेवा की गेथ किंवा इन्फुरा क्लायंटशी कनेक्ट केलेला ग्राफ नोड सर्व रिव्हर्ट्स शोधू शकत नाही, जर तुम्ही यावर अवलंबून असाल तर आम्ही पॅरिटी क्लायंटशी कनेक्ट केलेला ग्राफ नोड वापरण्याची शिफारस करतो.
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
 
 #### एन्कोडिंग/डिकोडिंग ABI
 

From 04ca2c32430f29d31e9a8e5007948ab711f57b06 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:04 -0500
Subject: [PATCH 0372/1325] New translations api.mdx (Swahili)

---
 website/pages/sw/developing/graph-ts/api.mdx | 890 +++++++++++++++++++
 1 file changed, 890 insertions(+)
 create mode 100644 website/pages/sw/developing/graph-ts/api.mdx

diff --git a/website/pages/sw/developing/graph-ts/api.mdx b/website/pages/sw/developing/graph-ts/api.mdx
new file mode 100644
index 000000000000..8fc1f4b48b61
--- /dev/null
+++ b/website/pages/sw/developing/graph-ts/api.mdx
@@ -0,0 +1,890 @@
+---
+title: AssemblyScript API
+---
+
+> Note: If you created a subgraph prior to `graph-cli`/`graph-ts` version `0.22.0`, then you're using an older version of AssemblyScript. It is recommended to review the [`Migration Guide`](/release-notes/assemblyscript-migration-guide).
+
+Learn what built-in APIs can be used when writing subgraph mappings. There are two kinds of APIs available out of the box:
+
+- The [Graph TypeScript library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) (`graph-ts`)
+- Code generated from subgraph files by `graph codegen`
+
+You can also add other libraries as dependencies, as long as they are compatible with [AssemblyScript](https://github.com/AssemblyScript/assemblyscript).
+
+Since language mappings are written in AssemblyScript, it is useful to review the language and standard library features from the [AssemblyScript wiki](https://github.com/AssemblyScript/assemblyscript/wiki).
+
+## API Reference
+
+The `@graphprotocol/graph-ts` library provides the following APIs:
+
+- An `ethereum` API for working with Ethereum smart contracts, events, blocks, transactions, and Ethereum values.
+- A `store` API to load and save entities from and to the Graph Node store.
+- A `log` API to log messages to the Graph Node output and Graph Explorer.
+- An `ipfs` API to load files from IPFS.
+- A `json` API to parse JSON data.
+- A `crypto` API to use cryptographic functions.
+- Low-level primitives to translate between different type systems such as Ethereum, JSON, GraphQL and AssemblyScript.
+
+### Versions
+
+The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
+
+| Version | Release notes                                                                                                                                                                                                                                 |
+| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
+|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
+|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
+|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
+|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
+|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+
+### Built-in Types
+
+Documentation on the base types built into AssemblyScript can be found in the [AssemblyScript wiki](https://www.assemblyscript.org/types.html).
+
+The following additional types are provided by `@graphprotocol/graph-ts`.
+
+#### ByteArray
+
+```typescript
+import { ByteArray } from '@graphprotocol/graph-ts'
+```
+
+`ByteArray` represents an array of `u8`.
+
+_Construction_
+
+- `fromI32(x: i32): ByteArray` - Decomposes `x` into bytes.
+- `fromHexString(hex: string): ByteArray` - Input length must be even. Prefixing with `0x` is optional.
+
+_Type conversions_
+
+- `toHexString(): string` - Converts to a hex string prefixed with `0x`.
+- `toString(): string` - Interprets the bytes as a UTF-8 string.
+- `toBase58(): string` - Encodes the bytes into a base58 string.
+- `toU32(): u32` - Interprets the bytes as a little-endian `u32`. Throws in case of overflow.
+- `toI32(): i32` - Interprets the byte array as a little-endian `i32`. Throws in case of overflow.
+
+_Operators_
+
+- `equals(y: ByteArray): bool` – can be written as `x == y`.
+- `concat(other: ByteArray) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by `other`
+- `concatI32(other: i32) : ByteArray` - return a new `ByteArray` consisting of `this` directly followed by the byte representation of `other`
+
+#### BigDecimal
+
+```typescript
+import { BigDecimal } from '@graphprotocol/graph-ts'
+```
+
+`BigDecimal` is used to represent arbitrary precision decimals.
+
+> Note: [Internally](https://github.com/graphprotocol/graph-node/blob/master/graph/src/data/store/scalar/bigdecimal.rs) `BigDecimal` is stored in [IEEE-754 decimal128 floating-point format](https://en.wikipedia.org/wiki/Decimal128_floating-point_format), which supports 34 decimal digits of significand. This makes `BigDecimal` unsuitable for representing fixed-point types that can span wider than 34 digits, such as a Solidity [`ufixed256x18`](https://docs.soliditylang.org/en/latest/types.html#fixed-point-numbers) or equivalent.
+
+_Construction_
+
+- `constructor(bigInt: BigInt)` – creates a `BigDecimal` from an `BigInt`.
+- `static fromString(s: string): BigDecimal` – parses from a decimal string.
+
+_Type conversions_
+
+- `toString(): string` – prints to a decimal string.
+
+_Math_
+
+- `plus(y: BigDecimal): BigDecimal` – can be written as `x + y`.
+- `minus(y: BigDecimal): BigDecimal` – can be written as `x - y`.
+- `times(y: BigDecimal): BigDecimal` – can be written as `x * y`.
+- `div(y: BigDecimal): BigDecimal` – can be written as `x / y`.
+- `equals(y: BigDecimal): bool` – can be written as `x == y`.
+- `notEqual(y: BigDecimal): bool` – can be written as `x != y`.
+- `lt(y: BigDecimal): bool` – can be written as `x < y`.
+- `le(y: BigDecimal): bool` – can be written as `x <= y`.
+- `gt(y: BigDecimal): bool` – can be written as `x > y`.
+- `ge(y: BigDecimal): bool` – can be written as `x >= y`.
+- `neg(): BigDecimal` - can be written as `-x`.
+
+#### BigInt
+
+```typescript
+import { BigInt } from '@graphprotocol/graph-ts'
+```
+
+`BigInt` is used to represent big integers. This includes Ethereum values of type `uint32` to `uint256` and `int64` to `int256`. Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.
+
+The `BigInt` class has the following API:
+
+_Construction_
+
+- `BigInt.fromI32(x: i32): BigInt` – creates a `BigInt` from an `i32`.
+
+- `BigInt.fromString(s: string): BigInt`– Parses a `BigInt` from a string.
+
+- `BigInt.fromUnsignedBytes(x: Bytes): BigInt` – Interprets `bytes` as an unsigned, little-endian integer. If your input is big-endian, call `.reverse()` first.
+
+- `BigInt.fromSignedBytes(x: Bytes): BigInt` – Interprets `bytes` as a signed, little-endian integer. If your input is big-endian, call `.reverse()` first.
+
+  _Type conversions_
+
+- `x.toHex(): string` – turns `BigInt` into a string of hexadecimal characters.
+
+- `x.toString(): string` – turns `BigInt` into a decimal number string.
+
+- `x.toI32(): i32` – returns the `BigInt` as an `i32`; fails if the value does not fit into `i32`. It's a good idea to first check `x.isI32()`.
+
+- `x.toBigDecimal(): BigDecimal` - converts into a decimal with no fractional part.
+
+_Math_
+
+- `x.plus(y: BigInt): BigInt` – can be written as `x + y`.
+- `x.minus(y: BigInt): BigInt` – can be written as `x - y`.
+- `x.times(y: BigInt): BigInt` – can be written as `x * y`.
+- `x.div(y: BigInt): BigInt` – can be written as `x / y`.
+- `x.mod(y: BigInt): BigInt` – can be written as `x % y`.
+- `x.equals(y: BigInt): bool` – can be written as `x == y`.
+- `x.notEqual(y: BigInt): bool` – can be written as `x != y`.
+- `x.lt(y: BigInt): bool` – can be written as `x < y`.
+- `x.le(y: BigInt): bool` – can be written as `x <= y`.
+- `x.gt(y: BigInt): bool` – can be written as `x > y`.
+- `x.ge(y: BigInt): bool` – can be written as `x >= y`.
+- `x.neg(): BigInt` – can be written as `-x`.
+- `x.divDecimal(y: BigDecimal): BigDecimal` – divides by a decimal, giving a decimal result.
+- `x.isZero(): bool` – Convenience for checking if the number is zero.
+- `x.isI32(): bool` – Check if the number fits in an `i32`.
+- `x.abs(): BigInt` – Absolute value.
+- `x.pow(exp: u8): BigInt` – Exponentiation.
+- `bitOr(x: BigInt, y: BigInt): BigInt` – can be written as `x | y`.
+- `bitAnd(x: BigInt, y: BigInt): BigInt` – can be written as `x & y`.
+- `leftShift(x: BigInt, bits: u8): BigInt` – can be written as `x << y`.
+- `rightShift(x: BigInt, bits: u8): BigInt` – can be written as `x >> y`.
+
+#### TypedMap
+
+```typescript
+import { TypedMap } from '@graphprotocol/graph-ts'
+```
+
+`TypedMap` can be used to store key-value pairs. See [this example](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
+
+The `TypedMap` class has the following API:
+
+- `new TypedMap<K, V>()` – creates an empty map with keys of type `K` and values of type `V`
+- `map.set(key: K, value: V): void` – sets the value of `key` to `value`
+- `map.getEntry(key: K): TypedMapEntry<K, V> | null` – returns the key-value pair for a `key` or `null` if the `key` does not exist in the map
+- `map.get(key: K): V | null` – returns the value for a `key` or `null` if the `key` does not exist in the map
+- `map.isSet(key: K): bool` – returns `true` if the `key` exists in the map and `false` if it does not
+
+#### Bytes
+
+```typescript
+import { Bytes } from '@graphprotocol/graph-ts'
+```
+
+`Bytes` is used to represent arbitrary-length arrays of bytes. This includes Ethereum values of type `bytes`, `bytes32`, etc.
+
+The `Bytes` class extends AssemblyScript's [Uint8Array](https://github.com/AssemblyScript/assemblyscript/blob/3b1852bc376ae799d9ebca888e6413afac7b572f/std/assembly/typedarray.ts#L64) and this supports all the `Uint8Array` functionality, plus the following new methods:
+
+_Construction_
+
+- `fromHexString(hex: string) : Bytes` - Convert the string `hex` which must consist of an even number of hexadecimal digits to a `ByteArray`. The string `hex` can optionally start with `0x`
+- `fromI32(i: i32) : Bytes` - Convert `i` to an array of bytes
+
+_Type conversions_
+
+- `b.toHex()` – returns a hexadecimal string representing the bytes in the array
+- `b.toString()` – converts the bytes in the array to a string of unicode characters
+- `b.toBase58()` – turns an Ethereum Bytes value to base58 encoding (used for IPFS hashes)
+
+_Operators_
+
+- `b.concat(other: Bytes) : Bytes` - - return new `Bytes` consisting of `this` directly followed by `other`
+- `b.concatI32(other: i32) : ByteArray` - return new `Bytes` consisting of `this` directly follow by the byte representation of `other`
+
+#### Address
+
+```typescript
+import { Address } from '@graphprotocol/graph-ts'
+```
+
+`Address` extends `Bytes` to represent Ethereum `address` values.
+
+It adds the following method on top of the `Bytes` API:
+
+- `Address.fromString(s: string): Address` – creates an `Address` from a hexadecimal string
+- `Address.fromBytes(b: Bytes): Address` – create an `Address` from `b` which must be exactly 20 bytes long. Passing in a value with fewer or more bytes will result in an error
+
+### Store API
+
+```typescript
+import { store } from '@graphprotocol/graph-ts'
+```
+
+The `store` API allows to load, save and remove entities from and to the Graph Node store.
+
+Entities written to the store map one-to-one to the `@entity` types defined in the subgraph's GraphQL schema. To make working with these entities convenient, the `graph codegen` command provided by the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) generates entity classes, which are subclasses of the built-in `Entity` type, with property getters and setters for the fields in the schema as well as methods to load and save these entities.
+
+#### Creating entities
+
+The following is a common pattern for creating entities from Ethereum events.
+
+```typescript
+// Import the Transfer event class generated from the ERC20 ABI
+import { Transfer as TransferEvent } from '../generated/ERC20/ERC20'
+
+// Import the Transfer entity type generated from the GraphQL schema
+import { Transfer } from '../generated/schema'
+
+// Transfer event handler
+export function handleTransfer(event: TransferEvent): void {
+  // Create a Transfer entity, using the transaction hash as the entity ID
+  let id = event.transaction.hash
+  let transfer = new Transfer(id)
+
+  // Set properties on the entity, using the event parameters
+  transfer.from = event.params.from
+  transfer.to = event.params.to
+  transfer.amount = event.params.amount
+
+  // Save the entity to the store
+  transfer.save()
+}
+```
+
+When a `Transfer` event is encountered while processing the chain, it is passed to the `handleTransfer` event handler using the generated `Transfer` type (aliased to `TransferEvent` here to avoid a naming conflict with the entity type). This type allows accessing data such as the event's parent transaction and its parameters.
+
+Each entity must have a unique ID to avoid collisions with other entities. It is fairly common for event parameters to include a unique identifier that can be used.
+
+> Note: Using the transaction hash as the ID assumes that no other events in the same transaction create entities with this hash as the ID.
+
+#### Loading entities from the store
+
+If an entity already exists, it can be loaded from the store with the following:
+
+```typescript
+let id = event.transaction.hash // or however the ID is constructed
+let transfer = Transfer.load(id)
+if (transfer == null) {
+  transfer = new Transfer(id)
+}
+
+// Use the Transfer entity as before
+```
+
+As the entity may not exist in the store yet, the `load` method returns a value of type `Transfer | null`. It may be necessary to check for the `null` case before using the value.
+
+> Note: Loading entities is only necessary if the changes made in the mapping depend on the previous data of an entity. See the next section for the two ways of updating existing entities.
+
+#### Looking up entities created withing a block
+
+As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.30.0 and `@graphprotocol/graph-cli` v0.49.0 the `loadInBlock` method is available on all entity types.
+
+The store API facilitates the retrieval of entities that were created or updated in the current block. A typical situation for this is that one handler creates a transaction from some on-chain event, and a later handler wants to access this transaction if it exists.
+
+- In the case where the transaction does not exist, the subgraph will have to go to the database simply to find out that the entity does not exist. If the subgraph author already knows that the entity must have been created in the same block, using `loadInBlock` avoids this database roundtrip.
+- For some subgraphs, these missed lookups can contribute significantly to the indexing time.
+
+```typescript
+let id = event.transaction.hash // or however the ID is constructed
+let transfer = Transfer.loadInBlock(id)
+if (transfer == null) {
+  transfer = new Transfer(id)
+}
+
+// Use the Transfer entity as before
+```
+
+> Note: If there is no entity created in the given block, `loadInBlock` will return `null` even if there is an entity with the given ID in the store.
+
+#### Looking up derived entities
+
+As of `graph-node` v0.31.0, `@graphprotocol/graph-ts` v0.31.0 and `@graphprotocol/graph-cli` v0.51.0 the `loadRelated` method is available.
+
+This enables loading derived entity fields from within an event handler. For example, given the following schema:
+
+```graphql
+type Token @entity {
+  id: ID!
+  holder: Holder!
+  color: String
+}
+
+type Holder @entity {
+  id: ID!
+  tokens: [Token!]! @derivedFrom(field: "holder")
+}
+```
+
+The following code will load the `Token` entity that the `Holder` entity was derived from:
+
+```typescript
+let holder = Holder.load('test-id')
+// Load the Token entities associated with a given holder
+let tokens = holder.tokens.load()
+```
+
+#### Updating existing entities
+
+There are two ways to update an existing entity:
+
+1. Load the entity with e.g. `Transfer.load(id)`, set properties on the entity, then `.save()` it back to the store.
+2. Simply create the entity with e.g. `new Transfer(id)`, set properties on the entity, then `.save()` it to the store. If the entity already exists, the changes are merged into it.
+
+Changing properties is straight forward in most cases, thanks to the generated property setters:
+
+```typescript
+let transfer = new Transfer(id)
+transfer.from = ...
+transfer.to = ...
+transfer.amount = ...
+```
+
+It is also possible to unset properties with one of the following two instructions:
+
+```typescript
+transfer.from.unset()
+transfer.from = null
+```
+
+This only works with optional properties, i.e. properties that are declared without a `!` in GraphQL. Two examples would be `owner: Bytes` or `amount: BigInt`.
+
+Updating array properties is a little more involved, as the getting an array from an entity creates a copy of that array. This means array properties have to be set again explicitly after changing the array. The following assumes `entity` has a `numbers: [BigInt!]!` field.
+
+```typescript
+// This won't work
+entity.numbers.push(BigInt.fromI32(1))
+entity.save()
+
+// This will work
+let numbers = entity.numbers
+numbers.push(BigInt.fromI32(1))
+entity.numbers = numbers
+entity.save()
+```
+
+#### Removing entities from the store
+
+There is currently no way to remove an entity via the generated types. Instead, removing an entity requires passing the name of the entity type and the entity ID to `store.remove`:
+
+```typescript
+import { store } from '@graphprotocol/graph-ts'
+...
+let id = event.transaction.hash
+store.remove('Transfer', id)
+```
+
+### Ethereum API
+
+The Ethereum API provides access to smart contracts, public state variables, contract functions, events, transactions, blocks and the encoding/decoding Ethereum data.
+
+#### Support for Ethereum Types
+
+As with entities, `graph codegen` generates classes for all smart contracts and events used in a subgraph. For this, the contract ABIs need to be part of the data source in the subgraph manifest. Typically, the ABI files are stored in an `abis/` folder.
+
+With the generated classes, conversions between Ethereum types and the [built-in types](#built-in-types) take place behind the scenes so that subgraph authors do not have to worry about them.
+
+The following example illustrates this. Given a subgraph schema like
+
+```graphql
+type Transfer @entity {
+  id: Bytes!
+  from: Bytes!
+  to: Bytes!
+  amount: BigInt!
+}
+```
+
+and a `Transfer(address,address,uint256)` event signature on Ethereum, the `from`, `to` and `amount` values of type `address`, `address` and `uint256` are converted to `Address` and `BigInt`, allowing them to be passed on to the `Bytes!` and `BigInt!` properties of the `Transfer` entity:
+
+```typescript
+let id = event.transaction.hash
+let transfer = new Transfer(id)
+transfer.from = event.params.from
+transfer.to = event.params.to
+transfer.amount = event.params.amount
+transfer.save()
+```
+
+#### Events and Block/Transaction Data
+
+Ethereum events passed to event handlers, such as the `Transfer` event in the previous examples, not only provide access to the event parameters but also to their parent transaction and the block they are part of. The following data can be obtained from `event` instances (these classes are a part of the `ethereum` module in `graph-ts`):
+
+```typescript
+class Event {
+  address: Address
+  logIndex: BigInt
+  transactionLogIndex: BigInt
+  logType: string | null
+  block: Block
+  transaction: Transaction
+  parameters: Array<EventParam>
+  receipt: TransactionReceipt | null
+}
+
+class Block {
+  hash: Bytes
+  parentHash: Bytes
+  unclesHash: Bytes
+  author: Address
+  stateRoot: Bytes
+  transactionsRoot: Bytes
+  receiptsRoot: Bytes
+  number: BigInt
+  gasUsed: BigInt
+  gasLimit: BigInt
+  timestamp: BigInt
+  difficulty: BigInt
+  totalDifficulty: BigInt
+  size: BigInt | null
+  baseFeePerGas: BigInt | null
+}
+
+class Transaction {
+  hash: Bytes
+  index: BigInt
+  from: Address
+  to: Address | null
+  value: BigInt
+  gasLimit: BigInt
+  gasPrice: BigInt
+  input: Bytes
+  nonce: BigInt
+}
+
+class TransactionReceipt {
+  transactionHash: Bytes
+  transactionIndex: BigInt
+  blockHash: Bytes
+  blockNumber: BigInt
+  cumulativeGasUsed: BigInt
+  gasUsed: BigInt
+  contractAddress: Address
+  logs: Array<Log>
+  status: BigInt
+  root: Bytes
+  logsBloom: Bytes
+}
+
+class Log {
+  address: Address
+  topics: Array<Bytes>
+  data: Bytes
+  blockHash: Bytes
+  blockNumber: Bytes
+  transactionHash: Bytes
+  transactionIndex: BigInt
+  logIndex: BigInt
+  transactionLogIndex: BigInt
+  logType: string
+  removed: bool | null
+}
+```
+
+#### Access to Smart Contract State
+
+The code generated by `graph codegen` also includes classes for the smart contracts used in the subgraph. These can be used to access public state variables and call functions of the contract at the current block.
+
+A common pattern is to access the contract from which an event originates. This is achieved with the following code:
+
+```typescript
+// Import the generated contract class and generated Transfer event class
+import { ERC20Contract, Transfer as TransferEvent } from '../generated/ERC20Contract/ERC20Contract'
+// Import the generated entity class
+import { Transfer } from '../generated/schema'
+
+export function handleTransfer(event: TransferEvent) {
+  // Bind the contract to the address that emitted the event
+  let contract = ERC20Contract.bind(event.address)
+
+  // Access state variables and functions by calling them
+  let erc20Symbol = contract.symbol()
+}
+```
+
+`Transfer` is aliased to `TransferEvent` here to avoid a naming conflict with the entity type
+
+As long as the `ERC20Contract` on Ethereum has a public read-only function called `symbol`, it can be called with `.symbol()`. For public state variables a method with the same name is created automatically.
+
+Any other contract that is part of the subgraph can be imported from the generated code and can be bound to a valid address.
+
+#### Handling Reverted Calls
+
+If the read-only methods of your contract may revert, then you should handle that by calling the generated contract method prefixed with `try_`.
+
+- For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
+
+```typescript
+let gravity = Gravity.bind(event.address)
+let callResult = gravity.try_gravatarToOwner(gravatar)
+if (callResult.reverted) {
+  log.info('getGravatar reverted', [])
+} else {
+  let owner = callResult.value
+}
+```
+
+> Note: A Graph node connected to a Geth or Infura client may not detect all reverts. If you rely on this, we recommend using a Graph Node connected to a Parity client.
+
+#### Encoding/Decoding ABI
+
+Data can be encoded and decoded according to Ethereum's ABI encoding format using the `encode` and `decode` functions in the `ethereum` module.
+
+```typescript
+import { Address, BigInt, ethereum } from '@graphprotocol/graph-ts'
+
+let tupleArray: Array<ethereum.Value> = [
+  ethereum.Value.fromAddress(Address.fromString('0x0000000000000000000000000000000000000420')),
+  ethereum.Value.fromUnsignedBigInt(BigInt.fromI32(62)),
+]
+
+let tuple = tupleArray as ethereum.Tuple
+
+let encoded = ethereum.encode(ethereum.Value.fromTuple(tuple))!
+
+let decoded = ethereum.decode('(address,uint256)', encoded)
+```
+
+For more information:
+
+- [ABI Spec](https://docs.soliditylang.org/en/v0.7.4/abi-spec.html#types)
+- Encoding/decoding [Rust library/CLI](https://github.com/rust-ethereum/ethabi)
+- More [complex example](https://github.com/graphprotocol/graph-node/blob/08da7cb46ddc8c09f448c5ea4b210c9021ea05ad/tests/integration-tests/host-exports/src/mapping.ts#L86).
+
+#### Balance of an Address
+
+The native token balance of an address can be retrieved using the `ethereum` module. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`. The `getBalance()` retrieves the balance of the specified address as of the end of the block in which the event is triggered.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+let address = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
+let balance = ethereum.getBalance(address) // returns balance in BigInt
+```
+
+#### Check if an Address is a Contract or EOA
+
+To check whether an address is a smart contract address or an externally owned address (EOA), use the `hasCode()` function from the `ethereum` module which will return `boolean`. This feature is available from `apiVersion: 0.0.9` which is defined `subgraph.yaml`.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+let contractAddr = Address.fromString('0x2E645469f354BB4F5c8a05B3b30A929361cf77eC')
+let isContract = ethereum.hasCode(contractAddr).inner // returns true
+
+let eoa = Address.fromString('0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045')
+let isContract = ethereum.hasCode(eoa).inner // returns false
+```
+
+### Logging API
+
+```typescript
+import { log } from '@graphprotocol/graph-ts'
+```
+
+The `log` API allows subgraphs to log information to the Graph Node standard output as well as Graph Explorer. Messages can be logged using different log levels. A basic format string syntax is provided to compose log messages from argument.
+
+The `log` API includes the following functions:
+
+- `log.debug(fmt: string, args: Array<string>): void` - logs a debug message.
+- `log.info(fmt: string, args: Array<string>): void` - logs an informational message.
+- `log.warning(fmt: string, args: Array<string>): void` - logs a warning.
+- `log.error(fmt: string, args: Array<string>): void` - logs an error message.
+- `log.critical(fmt: string, args: Array<string>): void` – logs a critical message _and_ terminates the subgraph.
+
+The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
+
+```typescript
+log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.toString(), 'already a string'])
+```
+
+#### Logging one or more values
+
+##### Logging a single value
+
+In the example below, the string value "A" is passed into an array to become`['A']` before being logged:
+
+```typescript
+let myValue = 'A'
+
+export function handleSomeEvent(event: SomeEvent): void {
+  // Displays : "My value is: A"
+  log.info('My value is: {}', [myValue])
+}
+```
+
+##### Logging a single entry from an existing array
+
+In the example below, only the first value of the argument array is logged, despite the array containing three values.
+
+```typescript
+let myArray = ['A', 'B', 'C']
+
+export function handleSomeEvent(event: SomeEvent): void {
+  // Displays : "My value is: A"  (Even though three values are passed to `log.info`)
+  log.info('My value is: {}', myArray)
+}
+```
+
+#### Logging multiple entries from an existing array
+
+Each entry in the arguments array requires its own placeholder `{}` in the log message string. The below example contains three placeholders `{}` in the log message. Because of this, all three values in `myArray` are logged.
+
+```typescript
+let myArray = ['A', 'B', 'C']
+
+export function handleSomeEvent(event: SomeEvent): void {
+  // Displays : "My first value is: A, second value is: B, third value is: C"
+  log.info('My first value is: {}, second value is: {}, third value is: {}', myArray)
+}
+```
+
+##### Logging a specific entry from an existing array
+
+To display a specific value in the array, the indexed value must be provided.
+
+```typescript
+export function handleSomeEvent(event: SomeEvent): void {
+  // Displays : "My third value is C"
+  log.info('My third value is: {}', [myArray[2]])
+}
+```
+
+##### Logging event information
+
+The example below logs the block number, block hash and transaction hash from an event:
+
+```typescript
+import { log } from '@graphprotocol/graph-ts'
+
+export function handleSomeEvent(event: SomeEvent): void {
+  log.debug('Block number: {}, block hash: {}, transaction hash: {}', [
+    event.block.number.toString(), // "47596000"
+    event.block.hash.toHexString(), // "0x..."
+    event.transaction.hash.toHexString(), // "0x..."
+  ])
+}
+```
+
+### IPFS API
+
+```typescript
+import { ipfs } from '@graphprotocol/graph-ts'
+```
+
+Smart contracts occasionally anchor IPFS files on chain. This allows mappings to obtain the IPFS hashes from the contract and read the corresponding files from IPFS. The file data will be returned as `Bytes`, which usually requires further processing, e.g. with the `json` API documented later on this page.
+
+Given an IPFS hash or path, reading a file from IPFS is done as follows:
+
+```typescript
+// Put this inside an event handler in the mapping
+let hash = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D'
+let data = ipfs.cat(hash)
+
+// Paths like `QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile`
+// that include files in directories are also supported
+let path = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile'
+let data = ipfs.cat(path)
+```
+
+**Note:** `ipfs.cat` is not deterministic at the moment. If the file cannot be retrieved over the IPFS network before the request times out, it will return `null`. Due to this, it's always worth checking the result for `null`.
+
+It is also possible to process larger files in a streaming fashion with `ipfs.map`. The function expects the hash or path for an IPFS file, the name of a callback, and flags to modify its behavior:
+
+```typescript
+import { JSONValue, Value } from '@graphprotocol/graph-ts'
+
+export function processItem(value: JSONValue, userData: Value): void {
+  // See the JSONValue documentation for details on dealing
+  // with JSON values
+  let obj = value.toObject()
+  let id = obj.get('id')
+  let title = obj.get('title')
+
+  if (!id || !title) {
+    return
+  }
+
+  // Callbacks can also created entities
+  let newItem = new Item(id)
+  newItem.title = title.toString()
+  newitem.parent = userData.toString() // Set parent to "parentId"
+  newitem.save()
+}
+
+// Put this inside an event handler in the mapping
+ipfs.map('Qm...', 'processItem', Value.fromString('parentId'), ['json'])
+
+// Alternatively, use `ipfs.mapJSON`
+ipfs.mapJSON('Qm...', 'processItem', Value.fromString('parentId'))
+```
+
+The only flag currently supported is `json`, which must be passed to `ipfs.map`. With the `json` flag, the IPFS file must consist of a series of JSON values, one value per line. The call to `ipfs.map` will read each line in the file, deserialize it into a `JSONValue` and call the callback for each of them. The callback can then use entity operations to store data from the `JSONValue`. Entity changes are stored only when the handler that called `ipfs.map` finishes successfully; in the meantime, they are kept in memory, and the size of the file that `ipfs.map` can process is therefore limited.
+
+On success, `ipfs.map` returns `void`. If any invocation of the callback causes an error, the handler that invoked `ipfs.map` is aborted, and the subgraph is marked as failed.
+
+### Crypto API
+
+```typescript
+import { crypto } from '@graphprotocol/graph-ts'
+```
+
+The `crypto` API makes a cryptographic functions available for use in mappings. Right now, there is only one:
+
+- `crypto.keccak256(input: ByteArray): ByteArray`
+
+### JSON API
+
+```typescript
+import { json, JSONValueKind } from '@graphprotocol/graph-ts'
+```
+
+JSON data can be parsed using the `json` API:
+
+- `json.fromBytes(data: Bytes): JSONValue` – parses JSON data from a `Bytes` array interpreted as a valid UTF-8 sequence
+- `json.try_fromBytes(data: Bytes): Result<JSONValue, boolean>` – safe version of `json.fromBytes`, it returns an error variant if the parsing failed
+- `json.fromString(data: string): JSONValue` – parses JSON data from a valid UTF-8 `String`
+- `json.try_fromString(data: string): Result<JSONValue, boolean>` – safe version of `json.fromString`, it returns an error variant if the parsing failed
+
+The `JSONValue` class provides a way to pull values out of an arbitrary JSON document. Since JSON values can be booleans, numbers, arrays and more, `JSONValue` comes with a `kind` property to check the type of a value:
+
+```typescript
+let value = json.fromBytes(...)
+if (value.kind == JSONValueKind.BOOL) {
+  ...
+}
+```
+
+In addition, there is a method to check if the value is `null`:
+
+- `value.isNull(): boolean`
+
+When the type of a value is certain, it can be converted to a [built-in type](#built-in-types) using one of the following methods:
+
+- `value.toBool(): boolean`
+- `value.toI64(): i64`
+- `value.toF64(): f64`
+- `value.toBigInt(): BigInt`
+- `value.toString(): string`
+- `value.toArray(): Array<JSONValue>` - (and then convert `JSONValue` with one of the 5 methods above)
+
+### Type Conversions Reference
+
+| Source(s)            | Destination          | Conversion function          |
+| -------------------- | -------------------- | ---------------------------- |
+| Address              | Bytes                | none                         |
+| Address              | String               | s.toHexString()              |
+| BigDecimal           | String               | s.toString()                 |
+| BigInt               | BigDecimal           | s.toBigDecimal()             |
+| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex() |
+| BigInt               | String (unicode)     | s.toString()                 |
+| BigInt               | i32                  | s.toI32()                    |
+| Boolean              | Boolean              | none                         |
+| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
+| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)  |
+| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex() |
+| Bytes                | String (unicode)     | s.toString()                 |
+| Bytes                | String (base58)      | s.toBase58()                 |
+| Bytes                | i32                  | s.toI32()                    |
+| Bytes                | u32                  | s.toU32()                    |
+| Bytes                | JSON                 | json.fromBytes(s)            |
+| int8                 | i32                  | none                         |
+| int32                | i32                  | none                         |
+| int32                | BigInt               | BigInt.fromI32(s)            |
+| uint24               | i32                  | none                         |
+| int64 - int256       | BigInt               | none                         |
+| uint32 - uint256     | BigInt               | none                         |
+| JSON                 | boolean              | s.toBool()                   |
+| JSON                 | i64                  | s.toI64()                    |
+| JSON                 | u64                  | s.toU64()                    |
+| JSON                 | f64                  | s.toF64()                    |
+| JSON                 | BigInt               | s.toBigInt()                 |
+| JSON                 | string               | s.toString()                 |
+| JSON                 | Array                | s.toArray()                  |
+| JSON                 | Object               | s.toObject()                 |
+| String               | Address              | Address.fromString(s)        |
+| Bytes                | Address              | Address.fromBytes(s)         |
+| String               | BigInt               | BigInt.fromString(s)         |
+| String               | BigDecimal           | BigDecimal.fromString(s)     |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
+
+### Data Source Metadata
+
+You can inspect the contract address, network and context of the data source that invoked the handler through the `dataSource` namespace:
+
+- `dataSource.address(): Address`
+- `dataSource.network(): string`
+- `dataSource.context(): DataSourceContext`
+
+### Entity and DataSourceContext
+
+The base `Entity` class and the child `DataSourceContext` class have helpers to dynamically set and get fields:
+
+- `setString(key: string, value: string): void`
+- `setI32(key: string, value: i32): void`
+- `setBigInt(key: string, value: BigInt): void`
+- `setBytes(key: string, value: Bytes): void`
+- `setBoolean(key: string, value: bool): void`
+- `setBigDecimal(key, value: BigDecimal): void`
+- `getString(key: string): string`
+- `getI32(key: string): i32`
+- `getBigInt(key: string): BigInt`
+- `getBytes(key: string): Bytes`
+- `getBoolean(key: string): boolean`
+- `getBigDecimal(key: string): BigDecimal`
+
+### DataSourceContext in Manifest
+
+The `context` section within `dataSources` allows you to define key-value pairs that are accessible within your subgraph mappings. The available types are `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`.
+
+Here is a YAML example illustrating the usage of various types in the `context` section:
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ContractName
+    network: mainnet
+    context:
+      bool_example:
+        type: Bool
+        data: true
+      string_example:
+        type: String
+        data: 'hello'
+      int_example:
+        type: Int
+        data: 42
+      int8_example:
+        type: Int8
+        data: 127
+      big_decimal_example:
+        type: BigDecimal
+        data: '10.99'
+      bytes_example:
+        type: Bytes
+        data: '0x68656c6c6f'
+      list_example:
+        type: List
+        data:
+          - type: Int
+            data: 1
+          - type: Int
+            data: 2
+          - type: Int
+            data: 3
+      big_int_example:
+        type: BigInt
+        data: '1000000000000000000000000'
+```
+
+- `Bool`: Specifies a Boolean value (`true` or `false`).
+- `String`: Specifies a String value.
+- `Int`: Specifies a 32-bit integer.
+- `Int8`: Specifies an 8-bit integer.
+- `BigDecimal`: Specifies a decimal number. Must be quoted.
+- `Bytes`: Specifies a hexadecimal string.
+- `List`: Specifies a list of items. Each item needs to specify its type and data.
+- `BigInt`: Specifies a large integer value. Must be quoted due to its large size.
+
+This context is then accessible in your subgraph mapping files, enabling more dynamic and configurable subgraphs.

From 01e381d81455639ed51bf27799fc278ba4218327 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:05 -0500
Subject: [PATCH 0373/1325] New translations subgraphs.mdx (Vietnamese)

---
 website/pages/vi/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/vi/subgraphs.mdx b/website/pages/vi/subgraphs.mdx
index 27b452211477..42c1e806f822 100644
--- a/website/pages/vi/subgraphs.mdx
+++ b/website/pages/vi/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From f37924961971e96949c8acee265e4b2d1ad1b440 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:07 -0500
Subject: [PATCH 0374/1325] New translations transfer-to-the-graph.mdx
 (Vietnamese)

---
 website/pages/vi/cookbook/transfer-to-the-graph.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/vi/cookbook/transfer-to-the-graph.mdx b/website/pages/vi/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..cfd461e80d4d 100644
--- a/website/pages/vi/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/vi/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### Ví dụ
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 

From 751734881382d1f66cec294e356d1a008687bf73 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:08 -0500
Subject: [PATCH 0375/1325] New translations advanced.mdx (Vietnamese)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/vi/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/vi/developing/creating-a-subgraph/advanced.mdx b/website/pages/vi/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..e929137a7147
--- /dev/null
+++ b/website/pages/vi/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Tổng quan
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Lỗi không nghiêm trọng
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Tổng quan
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Ghép vào các Subgraph Hiện có
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- Nó thêm hoặc xóa các loại thực thể
+- Nó loại bỏ các thuộc tính khỏi các loại thực thể
+- Nó thêm các thuộc tính nullable vào các loại thực thể
+- Nó biến các thuộc tính không thể nullable thành các thuộc tính nullable
+- Nó thêm giá trị vào enums
+- Nó thêm hoặc xóa các giao diện
+- Nó thay đổi đối với loại thực thể nào mà một giao diện được triển khai
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 110b5a6ee965f444d049017dc2b33ef03453c9a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:09 -0500
Subject: [PATCH 0376/1325] New translations assemblyscript-mappings.mdx
 (Vietnamese)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/vi/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/vi/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/vi/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..8a1d491a50fd
--- /dev/null
+++ b/website/pages/vi/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Tổng quan
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Viết Ánh xạ
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Các ID được Đề xuất để tạo các Thực thể Mới
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Tạo mã
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From e8f38a3f8b878f9181743c3d634671786c2a3882 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:10 -0500
Subject: [PATCH 0377/1325] New translations install-the-cli.mdx (Vietnamese)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..92e75af5d3ad
--- /dev/null
+++ b/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Cài đặt Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Tổng quan
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Cài đặt Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Tạo một Subgraph
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+(Các) tệp ABI phải khớp với (các) hợp đồng của bạn. Có một số cách để lấy tệp ABI:
+
+- Nếu bạn đang xây dựng dự án của riêng mình, bạn có thể sẽ có quyền truy cập vào các ABI mới nhất của mình.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Phiên bản | Ghi chú phát hành                                                                                                                                                        |
+| :-------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|   1.2.0   | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|   1.1.0   | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|   1.0.0   | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|   0.0.9   | Supports `endBlock` feature                                                                                                                                              |
+|   0.0.8   | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|   0.0.7   | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|   0.0.6   | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|   0.0.5   | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|   0.0.4   | Added support for managing subgraph features.                                                                                                                            |

From 3ff33d5d610be904d6b62a9262887685738b0abf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:11 -0500
Subject: [PATCH 0378/1325] New translations ql-schema.mdx (Vietnamese)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..4367bbd4b7f1
--- /dev/null
+++ b/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Tổng quan
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Ví dụ tốt
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Ví dụ tồi
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Các trường tùy chọn và bắt buộc
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Giá trị rỗng (null) được giải quyết cho trường không phải null 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Các loại vô hướng tích hợp
+
+#### GraphQL Vô hướng được hỗ trợ
+
+The following scalars are supported in the GraphQL API:
+
+| Loại         | Miêu tả                                                                                                                                                                                                          |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Mảng byte, được biểu diễn dưới dạng chuỗi thập lục phân. Thường được sử dụng cho các mã băm và địa chỉ Ethereum.                                                                                                 |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Mối quan hệ thực thể
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### Mối quan hệ một-một
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### Mối quan hệ một-nhiều
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Tra cứu ngược
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Ví dụ
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Mối quan hệ nhiều-nhiều
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Ví dụ
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Xác định các Trường Tìm kiếm toàn Văn bản
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Các ngôn ngữ được hỗ trợ
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Từ điển    |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Thuật toán Xếp hạng
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                                     |
+| ------------- | ------------------------------------------------------------------------------- |
+| rank          | Sử dụng chất lượng đối sánh (0-1) của truy vấn toàn văn bản để sắp xếp kết quả. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                 |

From 601c14c55811c02b2855fe974b49574e6d0e99f0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:12 -0500
Subject: [PATCH 0379/1325] New translations subgraph-manifest.mdx (Vietnamese)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/vi/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/vi/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/vi/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..1843837e0506
--- /dev/null
+++ b/website/pages/vi/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Tổng quan
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+Các mục nhập quan trọng cần cập nhật cho tệp kê khai là:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Trình xử lý lệnh gọi
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Xác định một Trình xử lý lệnh gọi
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Chức năng Ánh xạ
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Trình xử lý Khối
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Bộ lọc được hỗ trợ
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Chức năng Ánh xạ
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Sự kiện Ẩn danh
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+Các trình kích hoạt cho nguồn dữ liệu trong một khối được sắp xếp theo quy trình sau:
+
+1. Trình kích hoạt sự kiện và cuộc gọi được sắp xếp đầu tiên theo chỉ mục giao dịch trong khối.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Trình kích hoạt chặn được chạy sau trình kích hoạt sự kiện và cuộc gọi, theo thứ tự chúng được xác định trong tệp kê khai.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Mẫu Nguồn Dữ liệu
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Nguồn Dữ liệu cho Hợp đồng Chính
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Mẫu Nguồn Dữ liệu cho các Hợp đồng được Tạo Tự động
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Khởi tạo một Mẫu Nguồn Dữ liệu
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> Nếu các khối trước đó chứa dữ liệu có liên quan đến nguồn dữ liệu mới, tốt nhất là lập chỉ mục dữ liệu đó bằng cách đọc trạng thái hiện tại của hợp đồng và tạo các thực thể đại diện cho trạng thái đó tại thời điểm nguồn dữ liệu mới được tạo.
+
+### Bối cảnh Nguồn Dữ liệu
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Khối Bắt đầu
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Tìm kiếm hợp đồng bằng cách nhập địa chỉ của nó vào thanh tìm kiếm.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Tải trang chi tiết giao dịch nơi bạn sẽ tìm thấy khối bắt đầu cho hợp đồng đó.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From affd065ae4d97d980faac4d78b155aecddb6926d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:13 -0500
Subject: [PATCH 0380/1325] New translations subgraphs.mdx (Marathi)

---
 website/pages/mr/subgraphs.mdx | 53 +++++++++++++++++++++++++++++++---
 1 file changed, 49 insertions(+), 4 deletions(-)

diff --git a/website/pages/mr/subgraphs.mdx b/website/pages/mr/subgraphs.mdx
index 27b452211477..1738964b82d2 100644
--- a/website/pages/mr/subgraphs.mdx
+++ b/website/pages/mr/subgraphs.mdx
@@ -24,7 +24,13 @@ The **subgraph definition** consists of the following files:
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## सबग्राफ लाइफसायकल
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
 
 ## Subgraph Development
 
@@ -34,8 +40,47 @@ To learn more about each of subgraph component, check out [creating a subgraph](
 4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
 5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
 
-## Subgraph Lifecycle
+### Build locally
 
-Here is a general overview of a subgraph’s lifecycle:
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 8d70e55ecf4cf4b04a5d6ff15ee1d9a7e06a8fa0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:14 -0500
Subject: [PATCH 0381/1325] New translations transfer-to-the-graph.mdx
 (Marathi)

---
 website/pages/mr/cookbook/transfer-to-the-graph.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/mr/cookbook/transfer-to-the-graph.mdx b/website/pages/mr/cookbook/transfer-to-the-graph.mdx
index 287cd7d81b4b..3ab0ac609022 100644
--- a/website/pages/mr/cookbook/transfer-to-the-graph.mdx
+++ b/website/pages/mr/cookbook/transfer-to-the-graph.mdx
@@ -12,9 +12,9 @@ Quickly upgrade your subgraphs from any platform to [The Graph's decentralized n
 
 ## Upgrade Your Subgraph to The Graph in 3 Easy Steps
 
-1.  [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
-2.  [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
-3.  [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
 
 ## 1. Set Up Your Studio Environment
 
@@ -48,7 +48,7 @@ graph init --product subgraph-studio
 In The Graph CLI, use the auth command seen in Subgraph Studio:
 
 ```sh
-graph auth --studio <your-auth-code>
+graph auth <your-auth-code>
 ```
 
 ## 2. Deploy Your Subgraph to Studio
@@ -58,7 +58,7 @@ If you have your source code, you can easily deploy it to Studio. If you don't h
 In The Graph CLI, run the following command:
 
 ```sh
-graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 ```
 
@@ -74,7 +74,7 @@ graph deploy --studio <slug> --ipfs-hash <your-subgraph-ipfs-hash>
 
 You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
 
-#### Example
+#### उदाहरण
 
 [CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
 

From cce3c22a90555a8b1f35a44513eabdc015e78f59 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:16 -0500
Subject: [PATCH 0382/1325] New translations advanced.mdx (Marathi)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/mr/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/mr/developing/creating-a-subgraph/advanced.mdx b/website/pages/mr/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..0908f93a2214
--- /dev/null
+++ b/website/pages/mr/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## सविश्लेषण
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## गैर-घातक त्रुटी
+
+आधीच समक्रमित केलेल्या सबग्राफ्सवर अनुक्रमणिका त्रुटी, डीफॉल्टनुसार, सबग्राफ अयशस्वी होण्यास आणि समक्रमण थांबवण्यास कारणीभूत ठरतील. सबग्राफ वैकल्पिकरित्या त्रुटींच्या उपस्थितीत समक्रमण सुरू ठेवण्यासाठी कॉन्फिगर केले जाऊ शकतात, हँडलरने केलेल्या बदलांकडे दुर्लक्ष करून, ज्यामुळे त्रुटी उद्भवली. हे सबग्राफ लेखकांना त्यांचे सबग्राफ दुरुस्त करण्यासाठी वेळ देते जेव्हा की नवीनतम ब्लॉकच्या विरूद्ध क्वेरी चालू ठेवल्या जातात, जरी त्रुटीमुळे परिणाम विसंगत असू शकतात. लक्षात घ्या की काही त्रुटी अजूनही नेहमीच घातक असतात. गैर-घातक होण्यासाठी, त्रुटी निश्चितपणे ज्ञात असणे आवश्यक आहे.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> हे ऑफ-चेन डेटाच्या निर्धारवादी अनुक्रमणिकेसाठी तसेच अनियंत्रित HTTP-स्रोत डेटाच्या संभाव्य परिचयासाठी देखील पाया घालते.
+
+### सविश्लेषण
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+मूळ एकत्रित अस्तित्व:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+नवीन, विभाजित अस्तित्व:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+जर मूळ घटक आणि परिणामी फाइल डेटा स्रोत घटक यांच्यातील संबंध 1:1 असेल तर, आयपीएफएस सीआयडी लुकअप म्हणून वापरून मूळ घटकाला परिणामी फाइल घटकाशी जोडणे हा सर्वात सोपा नमुना आहे. तुम्हाला तुमच्या नवीन फाइल-आधारित घटकांचे मॉडेलिंग करण्यात अडचण येत असल्यास Discord वर संपर्क साधा!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### फाइल्सवर प्रक्रिया करण्यासाठी नवीन हँडलर तयार करा
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+उदाहरण हँडलर:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### आवश्यकतेनुसार फाईल डेटा स्रोत तयार करा
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+उदाहरण:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### तुमचे सबग्राफ उपयोजित करत आहे
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+फाइल डेटा स्रोत हँडलर आणि संस्था इतर सबग्राफ संस्थांपासून वेगळ्या केल्या जातात, ते कार्यान्वित केल्यावर ते निर्धारवादी आहेत याची खात्री करून आणि साखळी-आधारित डेटा स्रोतांचे दूषित होणार नाही याची खात्री करतात. विशिष्ट असणे:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> बहुतेक वापर-प्रकरणांसाठी ही मर्यादा समस्याप्रधान नसावी, परंतु काहींसाठी ते जटिलता आणू शकते. सबग्राफमध्‍ये तुमच्‍या फाईल-आधारित डेटाचे मॉडेल बनवण्‍यात तुम्‍हाला समस्या येत असल्‍यास कृपया डिस्‍कॉर्ड द्वारे संपर्क साधा!
+
+याव्यतिरिक्त, फाइल डेटा स्रोतावरून डेटा स्रोत तयार करणे शक्य नाही, मग ते ऑनचेन डेटा स्रोत असो किंवा अन्य फाइल डेटा स्रोत. भविष्यात हे निर्बंध उठवले जाऊ शकतात.
+
+#### चांगला सराव
+
+तुम्ही एनएफटी मेटाडेटाला संबंधित टोकनशी लिंक करत असल्यास, टोकन एंटिटीमधील मेटाडेटा घटकाचा संदर्भ देण्यासाठी मेटाडेटाचा IPFS हॅश वापरा. आयडी म्हणून IPFS हॅश वापरून मेटाडेटा घटक जतन करा.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### ओळखलेले समस्या
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### संदर्भ
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### विद्यमान सबग्राफवर कलम करणे
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+बेस डेटा इंडेक्स करण्याऐवजी कॉपीचे ग्राफ्टिंग केल्यामुळे, सुरवातीपासून इंडेक्स करण्यापेक्षा इच्छित ब्लॉकमध्ये सबग्राफ मिळवणे खूप जलद आहे, जरी सुरुवातीच्या डेटा कॉपीला खूप मोठ्या सबग्राफसाठी बरेच तास लागू शकतात. ग्रॅफ्टेड सबग्राफ सुरू होत असताना, ग्राफ नोड आधीपासून कॉपी केलेल्या घटक प्रकारांबद्दल माहिती लॉग करेल.
+
+ग्राफ्टेड सबग्राफ GraphQL स्कीमा वापरू शकतो जो बेस सबग्राफपैकी एकाशी एकसारखा नसतो, परंतु त्याच्याशी फक्त सुसंगत असतो. ती स्वतःच्या अधिकारात वैध सबग्राफ स्कीमा असणे आवश्यक आहे, परंतु खालील प्रकारे बेस सबग्राफच्या स्कीमापासून विचलित होऊ शकते:
+
+- हे घटक प्रकार जोडते किंवा काढून टाकते
+- हे घटक प्रकारातील गुणधर्म काढून टाकते
+- हे अस्तित्व प्रकारांमध्ये रद्द करण्यायोग्य विशेषता जोडते
+- हे नॉन-नलेबल अॅट्रिब्यूट्सना न्युलेबल अॅट्रिब्यूटमध्ये बदलते
+- हे enums मध्ये मूल्ये जोडते
+- हे इंटरफेस जोडते किंवा काढून टाकते
+- कोणत्या घटकासाठी इंटरफेस लागू केला जातो ते बदलते
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 6c40d2d621d1afb7df4280c02dcbf357b737a4d9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:17 -0500
Subject: [PATCH 0383/1325] New translations assemblyscript-mappings.mdx
 (Marathi)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/mr/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/mr/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/mr/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..682aec0ae2a5
--- /dev/null
+++ b/website/pages/mr/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## सविश्लेषण
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## मॅपिंग लेखन
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### नवीन संस्था तयार करण्यासाठी शिफारस केलेले आयडी
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## कोड जनरेशन
+
+स्मार्ट कॉन्ट्रॅक्ट्स, इव्हेंट्स आणि संस्थांसोबत काम करणे सोपे आणि टाइप-सुरक्षित करण्यासाठी, ग्राफ CLI सबग्राफच्या GraphQL स्कीमा आणि डेटा स्रोतांमध्ये समाविष्ट केलेल्या कॉन्ट्रॅक्ट ABIs मधून असेंबलीस्क्रिप्ट प्रकार व्युत्पन्न करू शकतो.
+
+यासह केले जाते
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From c449e69c5f9c33e05ecab779617141bdc9bc4e00 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:18 -0500
Subject: [PATCH 0384/1325] New translations install-the-cli.mdx (Marathi)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..4489fad1955b
--- /dev/null
+++ b/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## सविश्लेषण
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## प्रारंभ करणे
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+तुमच्या स्थानिक मशीनवर, खालीलपैकी एक कमांड चालवा:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## सबग्राफ तयार करा
+
+### विद्यमान करारातून
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### सबग्राफच्या उदाहरणावरून
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| आवृत्ती | रिलीझ नोट्स                                                                                                                                                              |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 3b99f2e0746c2d28473bc0c0be3f437b283653ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:19 -0500
Subject: [PATCH 0385/1325] New translations ql-schema.mdx (Marathi)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..5d567ca32ddc
--- /dev/null
+++ b/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## सविश्लेषण
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### उत्तम उदाहरण
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### वाईट उदाहरण
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### पर्यायी आणि आवश्यक फील्ड
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+नॉन-नल फील्ड 'नावासाठी शून्य मूल्य सोडवले
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### अंगभूत स्केलर प्रकार
+
+#### ग्राफक्यूएल समर्थित स्केलर
+
+The following scalars are supported in the GraphQL API:
+
+| प्रकार       | वर्णन                                                                                                                                                                                                            |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### एनम्स
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### अस्तित्व संबंध
+
+एखाद्या घटकाचा तुमच्या स्कीमामधील एक किंवा अधिक इतर घटकांशी संबंध असू शकतो. हे नातेसंबंध तुमच्या प्रश्नांमध्ये असू शकतात. आलेखामधील संबंध दिशाहीन आहेत. नात्याच्या "शेवट" वर एकदिशात्मक संबंध परिभाषित करून द्विदिशात्मक संबंधांचे अनुकरण करणे शक्य आहे.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### वन-टू-वन संबंध
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### एक-ते-अनेक संबंध
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### उलटे लुकअप
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+एक-ते-अनेक संबंधांसाठी, संबंध नेहमी 'एका' बाजूला साठवले पाहिजेत आणि 'अनेक' बाजू नेहमी काढल्या पाहिजेत. 'अनेक' बाजूंवर संस्थांचा अ‍ॅरे संचयित करण्याऐवजी अशा प्रकारे नातेसंबंध संचयित केल्याने, अनुक्रमणिका आणि सबग्राफ क्वेरी या दोन्हीसाठी नाटकीयरित्या चांगले कार्यप्रदर्शन होईल. सर्वसाधारणपणे, घटकांचे अ‍ॅरे संग्रहित करणे जितके व्यावहारिक आहे तितके टाळले पाहिजे.
+
+#### उदाहरण
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### अनेक-ते-अनेक संबंध
+
+अनेक-ते-अनेक नातेसंबंधांसाठी, जसे की वापरकर्ते जे कोणत्याही संस्थेशी संबंधित असू शकतात, सर्वात सरळ, परंतु सामान्यतः सर्वात कार्यक्षम नसतात, संबंध मॉडेल करण्याचा मार्ग समाविष्ट असलेल्या दोन घटकांपैकी प्रत्येकामध्ये एक अॅरे आहे. नातेसंबंध सममितीय असल्यास, नातेसंबंधाची फक्त एक बाजू संग्रहित करणे आवश्यक आहे आणि दुसरी बाजू मिळवता येते.
+
+#### उदाहरण
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+अनेक-ते-अनेक संबंध संचयित करण्याच्या या अधिक विस्तृत मार्गामुळे सबग्राफसाठी कमी डेटा संग्रहित केला जाईल आणि म्हणूनच अनुक्रमणिका आणि क्वेरीसाठी नाटकीयरित्या वेगवान असलेल्या सबग्राफमध्ये.
+
+### स्कीमामध्ये टिप्पण्या जोडत आहे
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## पूर्ण मजकूर शोध फील्ड परिभाषित करणे
+
+मजकूर शोध इनपुटवर आधारित फुलटेक्स्ट शोध क्वेरी फिल्टर आणि रँक घटक. फुलटेक्स्ट क्वेरी अनुक्रमित मजकूर डेटाशी तुलना करण्यापूर्वी स्टेममध्ये क्वेरी मजकूर इनपुटवर प्रक्रिया करून समान शब्दांसाठी जुळणी परत करण्यास सक्षम आहेत.
+
+पूर्ण मजकूर क्वेरी व्याख्येमध्ये क्वेरीचे नाव, मजकूर फील्डवर प्रक्रिया करण्यासाठी वापरला जाणारा भाषा शब्दकोष, परिणाम ऑर्डर करण्यासाठी वापरले जाणारे रँकिंग अल्गोरिदम आणि शोधामध्ये समाविष्ट फील्ड समाविष्ट असतात. प्रत्येक फुलटेक्स्ट क्वेरी एकाधिक फील्डमध्ये असू शकते, परंतु सर्व समाविष्ट फील्ड एकाच घटक प्रकारातील असणे आवश्यक आहे.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## भाषा समर्थित
+
+भिन्न भाषा निवडल्याने पूर्ण मजकूर शोध API वर निश्चित, काहीवेळा सूक्ष्म असले तरी परिणाम होईल. फुलटेक्स्ट क्वेरी फील्डद्वारे कव्हर केलेले फील्ड निवडलेल्या भाषेच्या संदर्भात तपासले जातात, म्हणून विश्लेषण आणि शोध क्वेरीद्वारे तयार केलेले लेक्सेम भाषेनुसार भिन्न असतात. उदाहरणार्थ: समर्थित तुर्की शब्दकोश वापरताना "टोकन" हे "टोक" वर स्टेम केले जाते, तर अर्थातच, इंग्रजी शब्दकोश "टोकन" वर स्टेम करेल.
+
+समर्थित भाषा शब्दकोश:
+
+| Code   | शब्दकोश    |
+| ------ | ---------- |
+| सोपे   | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | पोर्तुगीज  |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### रँकिंग अल्गोरिदम
+
+परिणाम ऑर्डर करण्यासाठी समर्थित अल्गोरिदम:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | निकाल ऑर्डर करण्यासाठी फुलटेक्स्ट क्वेरीची जुळणी गुणवत्ता (0-1) वापरा.  |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From 2cc6c9130aa9d37a1b1dcfd5fa4dd952afbe95f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:20 -0500
Subject: [PATCH 0386/1325] New translations subgraph-manifest.mdx (Marathi)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/mr/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/mr/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/mr/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..fad2db52e58e
--- /dev/null
+++ b/website/pages/mr/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## सविश्लेषण
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+मॅनिफेस्टसाठी अद्यतनित करण्याच्या महत्त्वाच्या नोंदी आहेत:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## हँडलर्सना कॉल करा
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+कॉल हँडलर्स फक्त दोनपैकी एका प्रकरणात ट्रिगर होतील: जेव्हा निर्दिष्ट केलेल्या फंक्शनला कॉन्ट्रॅक्ट व्यतिरिक्त इतर खात्याद्वारे कॉल केले जाते किंवा जेव्हा ते सॉलिडिटीमध्ये बाह्य म्हणून चिन्हांकित केले जाते आणि त्याच कॉन्ट्रॅक्टमधील दुसर्‍या फंक्शनचा भाग म्हणून कॉल केले जाते.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### कॉल हँडलरची व्याख्या
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### मॅपिंग कार्य
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## ब्लॉक हँडलर
+
+कॉन्ट्रॅक्ट इव्हेंट्स किंवा फंक्शन कॉल्सची सदस्यता घेण्याव्यतिरिक्त, सबग्राफला त्याचा डेटा अद्यतनित करायचा असेल कारण साखळीमध्ये नवीन ब्लॉक्स जोडले जातात. हे साध्य करण्यासाठी सबग्राफ प्रत्येक ब्लॉकनंतर किंवा पूर्व-परिभाषित फिल्टरशी जुळणार्‍या ब्लॉक्सनंतर फंक्शन चालवू शकतो.
+
+### समर्थित फिल्टर
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+ब्लॉक हँडलरसाठी फिल्टरची अनुपस्थिती हे सुनिश्चित करेल की हँडलरला प्रत्येक ब्लॉक म्हटले जाईल. डेटा स्त्रोतामध्ये प्रत्येक फिल्टर प्रकारासाठी फक्त एक ब्लॉक हँडलर असू शकतो.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### मॅपिंग कार्य
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## अनामिक घटना
+
+तुम्हाला सॉलिडिटीमध्ये निनावी इव्हेंटवर प्रक्रिया करायची असल्यास, ते इव्हेंटचा विषय 0 प्रदान करून प्राप्त केले जाऊ शकते, उदाहरणार्थ:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. समान व्यवहारामधील इव्हेंट आणि कॉल ट्रिगर्स एक नियम वापरून ऑर्डर केले जातात: प्रथम इव्हेंट ट्रिगर नंतर कॉल ट्रिगर, प्रत्येक प्रकार मॅनिफेस्टमध्ये परिभाषित केलेल्या क्रमाचा आदर करतो.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## डेटा स्रोत टेम्पलेट्स
+
+EVM-सुसंगत स्मार्ट कॉन्ट्रॅक्ट्समधील एक सामान्य नमुना म्हणजे नोंदणी किंवा फॅक्टरी कॉन्ट्रॅक्टचा वापर, जिथे एक करार तयार करतो, व्यवस्थापित करतो किंवा इतर करारांची अनियंत्रित संख्या संदर्भित करतो ज्या प्रत्येकाची स्वतःची स्थिती आणि घटना असतात.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### मुख्य करारासाठी डेटा स्रोत
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### डेटा स्रोत टेम्पलेट इन्स्टंट करणे
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> पूर्वीच्या ब्लॉक्समध्ये नवीन डेटा स्रोताशी संबंधित डेटा असल्यास, कराराची वर्तमान स्थिती वाचून आणि नवीन डेटा स्रोत तयार करताना त्या स्थितीचे प्रतिनिधित्व करणारी संस्था तयार करून तो डेटा अनुक्रमित करणे सर्वोत्तम आहे.
+
+### डेटा स्रोत संदर्भ
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## ब्लॉक सुरू करा
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From a432dc0013a49de53b0496c3db2e3d365429d9ae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:21 -0500
Subject: [PATCH 0387/1325] New translations subgraphs.mdx (Hindi)

---
 website/pages/hi/subgraphs.mdx | 89 +++++++++++++++++++++++++---------
 1 file changed, 67 insertions(+), 22 deletions(-)

diff --git a/website/pages/hi/subgraphs.mdx b/website/pages/hi/subgraphs.mdx
index 27b452211477..4599a8cc79d9 100644
--- a/website/pages/hi/subgraphs.mdx
+++ b/website/pages/hi/subgraphs.mdx
@@ -1,41 +1,86 @@
 ---
-title: Subgraphs
+title: सबग्राफ
 ---
 
-## What is a Subgraph?
+## Subgraph क्या है?
 
-A subgraph is a custom, open API that extracts data from a blockchain, processes it, and stores it so it can be easily queried via GraphQL.
+एक subgraph एक कस्टम, ओपन API है जो एक ब्लॉकचेन से डेटा निकालता है, उसे प्रोसेस करता है, और उसे इस तरह से स्टोर करता है कि उसे GraphQL के माध्यम से आसानी से क्वेरी किया जा सके।
 
-### Subgraph Capabilities
+### Subgraph क्षमताएँ
 
-- **Access Data:** Subgraphs enable the querying and indexing of blockchain data for web3.
-- **Build:** Developers can build, deploy, and publish subgraphs to The Graph Network. To get started, check out the subgraph developer [Quick Start](quick-start/).
-- **Index & Query:** Once a subgraph is indexed, anyone can query it. Explore and query all subgraphs published to the network in [Graph Explorer](https://thegraph.com/explorer).
+- डेटा एक्सेस करें: Subgraphs web3 के लिए ब्लॉकचेन डेटा के क्वेरी और इंडेक्सिंग को सक्षम बनाते हैं।
+- बनाएँ: डेवलपर्स The Graph Network पर subgraphs बना सकते हैं, डिप्लॉय कर सकते हैं और प्रकाशित कर सकते हैं। शुरुआत करने के लिए, subgraph डेवलपर Quick Start(quick-start/) देखें।
+- इंडेक्स और क्वेरी: एक बार जब एक subgraph को इंडेक्स किया जाता है, तो कोई भी इसे क्वेरी कर सकता है।GraphExplorer(https://thegraph.com/explorer) में नेटवर्क पर प्रकाशित सभी subgraphs का अन्वेषण और क्वेरी करें।
 
-## Inside a Subgraph
+## एक Subgraph के अंदर
 
-The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+subgraph मैनिफेस्ट, subgraph.yaml, उन स्मार्ट कॉन्ट्रैक्ट्स और नेटवर्क को परिभाषित करता है जिन्हें आपका subgraph इंडेक्स करेगा, इन कॉन्ट्रैक्ट्स से ध्यान देने योग्य इवेंट्स, और इवेंट डेटा को उन संस्थाओं के साथ मैप करने का तरीका जिन्हें Graph Node स्टोर करता है और जिन्हें क्वेरी करने की अनुमति देता है।
 
-The **subgraph definition** consists of the following files:
+**subgraph definition** में निम्नलिखित फ़ाइलें शामिल हैं:
 
-- `subgraph.yaml`: Contains the subgraph manifest
+- subgraph.yaml: में subgraph मैनिफेस्ट शामिल है
 
-- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+- schema.graphql: एक GraphQL स्कीमा जो आपके लिए डेटा को परिभाषित करता है और इसे GraphQL के माध्यम से क्वेरी करने का तरीका बताता है.
 
 - `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
 
-To learn more about each of subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+प्रत्येक उपग्राफ घटक के बारे में अधिक जानने के लिए, देखें creating a subgraph(/developing/creating-a-subgraph/).
 
-## Subgraph Development
+## सबग्राफ जीवनचक्र
 
-1. [Create a subgraph](/developing/creating-a-subgraph/)
-2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/)
-3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio)
-4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
-5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
+यहाँ एक Subgraph के जीवनचक्र का सामान्य अवलोकन है।
 
-## Subgraph Lifecycle
+![Subgraph जीवनचक्र ](/img/subgraph-lifecycle.png)
 
-Here is a general overview of a subgraph’s lifecycle:
+## सबग्राफ विकास
 
-![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+1. [एक subgraph बनाएँ](/developing/creating-a-subgraph/)
+2. [डिप्लॉय a subgraph](/deploying/deploying-a-subgraph-to-studio/)
+3. [एक 'subgraph' का परीक्षण करें](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio)
+4. [एक subgraph प्रकाशित करें](/publishing/publishing-a-subgraph/)
+5. [subgraph पर संकेत](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
+
+### Build locally
+
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
+
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 55ead524fa6968d8cfdd03fcc1ecd1ffa5c76e2a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:23 -0500
Subject: [PATCH 0388/1325] New translations advanced.mdx (Hindi)

---
 .../creating-a-subgraph/advanced.mdx          | 556 ++++++++++++++++++
 1 file changed, 556 insertions(+)
 create mode 100644 website/pages/hi/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/hi/developing/creating-a-subgraph/advanced.mdx b/website/pages/hi/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..17ea3311f5a9
--- /dev/null
+++ b/website/pages/hi/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,556 @@
+---
+title: Advance Subgraph Features
+---
+
+## अवलोकन
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries और Aggregations
+
+Timeseries और aggregations आपके subgraph को दैनिक औसत मूल्य, घंटेवारी कुल स्थानांतरण आदि जैसे आंकड़े ट्रैक करने में सक्षम बनाते हैं।
+
+यह विशेषता दो नए प्रकार की 'subgraph' इकाई पेश करती है। 'Timeseries' इकाइयाँ डेटा बिंदुओं को समय की छाप के साथ रिकॉर्ड करती हैं। 'Aggregation' इकाइयाँ 'Timeseries' डेटा बिंदुओं पर पूर्व-घोषित गणनाएँ करती हैं, जो प्रति घंटे या प्रति दिन होती हैं, फिर परिणामों को GraphQL के माध्यम से आसान पहुँच के लिए संग्रहीत करती हैं।
+
+### उदाहरण स्कीमा
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### टाइमसीरीज और एग्रीगेशन्स को परिभाषित करना
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### उपलब्ध Aggregation अंतराल
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### उपलब्ध Aggregation फ़ंक्शन
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### उदाहरण Aggregations queries
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+नोट:
+
+Timeseries और Aggregations का उपयोग करने के लिए, एक subgraph का spec version ≥1.1.0 होना चाहिए। ध्यान दें कि यह सुविधा महत्वपूर्ण परिवर्तनों का सामना कर सकती है जो पीछे की संगतता को प्रभावित कर सकती है।
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## गैर-घातक त्रुटियाँ
+
+पहले से सिंक किए गए सबग्राफ पर इंडेक्सिंग त्रुटियां, डिफ़ॉल्ट रूप से, सबग्राफ को विफल कर देंगी और सिंक करना बंद कर देंगी। सबग्राफ को वैकल्पिक रूप से त्रुटियों की उपस्थिति में समन्वयन जारी रखने के लिए कॉन्फ़िगर किया जा सकता है, हैंडलर द्वारा किए गए परिवर्तनों को अनदेखा करके त्रुटि उत्पन्न हुई। यह सबग्राफ लेखकों को अपने सबग्राफ को ठीक करने का समय देता है, जबकि नवीनतम ब्लॉक के विरुद्ध प्रश्नों को जारी रखा जाता है, हालांकि त्रुटि के कारण बग के कारण परिणाम असंगत हो सकते हैं। ध्यान दें कि कुछ त्रुटियाँ अभी भी हमेशा घातक होती हैं। गैर-घातक होने के लिए, त्रुटि नियतात्मक होने के लिए जानी जानी चाहिए।
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+गैर-घातक त्रुटियों को सक्षम करने के लिए सबग्राफ मेनिफ़ेस्ट पर निम्न फ़ीचर फ़्लैग सेट करने की आवश्यकता होती है:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave फ़ाइल डेटा स्रोत
+
+फाइल डेटा स्रोत एक नई subgraph कार्यक्षमता है जो indexing के दौरान ऑफ-चेन डेटा तक एक मजबूत, विस्तारित तरीके से पहुँच प्रदान करती है। फाइल डेटा स्रोत IPFS और Arweave से फ़ाइलें फ़ेच करने का समर्थन करते हैं।
+
+> यह ऑफ-चेन डेटा के नियतात्मक अनुक्रमण के साथ-साथ स्वैच्छिक HTTP-स्रोत डेटा के संभावित परिचय के लिए आधार भी देता है।
+
+### अवलोकन
+
+"लाइन" में हैंडलर कार्यान्वयन के दौरान फ़ाइलों को लाने के बजाय, यह टेम्पलेट्स को पेश करता है जिन्हें एक दिए गए फ़ाइल पहचानकर्ता के लिए नए डेटा स्रोतों के रूप में उत्पन्न किया जा सकता है। ये नए डेटा स्रोत फ़ाइलों को लाते हैं, यदि वे असफल होते हैं तो पुनः प्रयास करते हैं, और जब फ़ाइल मिलती है तो एक समर्पित हैंडलर चलाते हैं।
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### अपग्रेड गाइड
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### एक नया इकाई प्रकार जोड़ें जो फ़ाइलें मिलने पर अपडेट किया जाएगा
+
+फ़ाइल डेटा स्रोत श्रृंखला-आधारित संस्थाओं तक पहुँच या अद्यतन नहीं कर सकते हैं, लेकिन फ़ाइल विशिष्ट संस्थाओं को अद्यतन करना चाहिए।
+
+इसका मतलब हो सकता है कि फ़ील्ड को मौजूदा इकाइयों से अलग-अलग इकाइयों में विभाजित करना, एक साथ जुड़े हुए।
+
+मूल संयुक्त इकाई:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+नई, विभाजित इकाई:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+यदि पैरेंट इकाई और परिणामी फ़ाइल डेटा स्रोत इकाई के बीच संबंध 1:1 है, तो सबसे सरल पैटर्न मूल इकाई को लुकअप के रूप में IPFS CID का उपयोग करके परिणामी फ़ाइल इकाई से लिंक करना है। यदि आपको अपनी नई फ़ाइल-आधारित संस्थाओं को मॉडलिंग करने में कठिनाई हो रही है, तो डिस्कॉर्ड पर संपर्क करें!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+यह वह डेटा स्रोत है जो ब्याज की फ़ाइल की पहचान होने पर उत्पन्न होगा।
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### फ़ाइलों को संसाधित करने के लिए एक नया हैंडलर बनाएँ
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+उदाहरण हैंडलर:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### आवश्यक होने पर फ़ाइल डेटा स्रोत स्पॉन करें
+
+अब आप चेन-आधारित हैंडलर के निष्पादन के दौरान फ़ाइल डेटा स्रोत बना सकते हैं:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+उदाहरण:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+यह एक नया file data source बनाएगा, जो Graph Node के configured किए गए IPFS या Arweave endpoint का सर्वेक्षण करेगा, यदि यह नहीं मिलता है तो पुनः प्रयास करेगा। जब file मिल जाती है, तो file data source handler execute किया जाएगा।
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+बधाई हो, आप फ़ाइल डेटा स्रोतों का उपयोग कर रहे हैं!
+
+#### अपने उप-अनुच्छेदों को तैनात करना
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### परिसीमन
+
+फ़ाइल डेटा स्रोत हैंडलर और संस्थाएँ अन्य सबग्राफ संस्थाओं से अलग हैं, यह सुनिश्चित करते हुए कि वे निष्पादित होने पर नियतात्मक हैं, और श्रृंखला-आधारित डेटा स्रोतों का कोई संदूषण सुनिश्चित नहीं करते हैं। विस्तार से:
+
+- फ़ाइल डेटा स्रोतों द्वारा बनाई गई इकाइयाँ अपरिवर्तनीय हैं, और इन्हें अद्यतन नहीं किया जा सकता है
+- फ़ाइल डेटा स्रोत हैंडलर अन्य फ़ाइल डेटा स्रोतों से संस्थाओं तक नहीं पहुँच सकते
+- फ़ाइल डेटा स्रोतों से जुड़ी संस्थाओं को चेन-आधारित हैंडलर द्वारा एक्सेस नहीं किया जा सकता है
+
+> हालांकि यह बाधा अधिकांश उपयोग-मामलों के लिए समस्याग्रस्त नहीं होनी चाहिए, यह कुछ के लिए जटिलता का परिचय दे सकती है। यदि आपको अपने फ़ाइल-आधारित डेटा को सबग्राफ में मॉडलिंग करने में समस्या आ रही है, तो कृपया डिस्कॉर्ड के माध्यम से संपर्क करें!
+
+इसके अतिरिक्त, फ़ाइल डेटा स्रोत से डेटा स्रोत बनाना संभव नहीं है, चाहे वह ऑनचेन डेटा स्रोत हो या अन्य फ़ाइल डेटा स्रोत। भविष्य में यह प्रतिबंध हटाया जा सकता है।
+
+#### सर्वोत्तम प्रथाएं
+
+यदि आप NFT मेटाडेटा को संबंधित टोकन से लिंक कर रहे हैं, तो टोकन इकाई से मेटाडेटा इकाई को संदर्भित करने के लिए मेटाडेटा के IPFS हैश का उपयोग करें। एक आईडी के रूप में IPFS हैश का उपयोग करके मेटाडेटा इकाई को सहेजें।
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> हम ऊपर दिए गए सुझाव को बेहतर बनाने के लिए काम कर रहे हैं, इसलिए क्वेरी केवल "नवीनतम" संस्करण लौटाती हैं
+
+#### ज्ञात समस्याएँ
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### उदाहरण
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### संदर्भ
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## सूचीकृत तर्क फ़िल्टर / विषय फ़िल्टर
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+विषय फ़िल्टर, जिन्हें इंडेक्स किए गए तर्क फ़िल्टर भी कहा जाता है, एक शक्तिशाली विशेषता है जो उपयोगकर्ताओं को उनके इंडेक्स किए गए तर्कों के मानों के आधार पर ब्लॉकचेन घटनाओं को सटीक रूप से फ़िल्टर करने की अनुमति देती है।
+
+- ये फ़िल्टर ब्लॉकचेन पर घटनाओं की विशाल धारा से रुचि की विशिष्ट घटनाओं को अलग करने में मदद करते हैं, जिससे सबग्राफ़ केवल प्रासंगिक डेटा पर ध्यान केंद्रित करके अधिक कुशलता से कार्य कर सके।
+
+- यह व्यक्तिगत subgraphs बनाने के लिए उपयोगी है जो विशेष पते और विभिन्न स्मार्ट कॉन्ट्रैक्ट्स के साथ उनके इंटरैक्शन को ट्रैक करते हैं ब्लॉकचेन पर।
+
+### शीर्षक फ़िल्टर कैसे काम करते हैं
+
+जब एक स्मार्ट कॉन्ट्रैक्ट एक इवेंट को उत्पन्न करता है, तो कोई भी तर्क जो 'indexed' के रूप में चिह्नित किया गया है, एक 'subgraph' की मैनिफेस्ट में फ़िल्टर के रूप में उपयोग किया जा सकता है। यह 'subgraph' को इन 'indexed' तर्कों से मेल खाने वाले इवेंट्स के लिए चयनात्मक रूप से सुनने की अनुमति देता है।
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // ईवेंट की घोषणा जिसमें पते के लिए इंडेक्स्ड पैरामीटर हैं
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // टोकन ट्रांसफर करने की क्रिया को सिमुलेट करने के लिए फ़ंक्शन
+    function transfer(address to, uint256 value) public {
+        // from, to, और value के साथ Transfer ईवेंट को उत्सर्जित करना
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+इस उदाहरण में:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### सबस्पष्ट में कॉन्फ़िगरेशन
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+इस सेटअप में:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- प्रत्येक विषय में एक या अधिक मान हो सकते हैं, और एक घटना केवल तभी प्रोसेस की जाती है जब वह प्रत्येक निर्दिष्ट विषय में से किसी एक मान से मेल खाती है।
+
+#### फ़िल्टर लॉजिक
+
+- एकल विषय के भीतर: लॉजिक एक OR स्थिति के रूप में कार्य करता है। यदि यह किसी दिए गए विषय में सूचीबद्ध मूल्यों में से किसी एक के साथ मेल खाता है, तो इवेंट को प्रोसेस किया जाएगा।
+- विभिन्न विषयों के बीच: लॉजिक एक AND स्थिति के रूप में कार्य करता है। एक घटना को संबंधित हैंडलर को ट्रिगर करने के लिए विभिन्न विषयों में सभी निर्दिष्ट शर्तों को संतोषजनक रूप से पूरा करना चाहिए।
+
+#### उदाहरण 1: 'पता A' से 'पता B' के लिए प्रत्यक्ष स्थानांतरण का ट्रैकिंग
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+इस कॉन्फ़िगरेशन में:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### उदाहरण 2: दो या अधिक 'पते' के बीच किसी भी दिशा में लेन-देन को ट्रैक करना
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # प्रेषक पता
+    topic2: ['0xAddressB', '0xAddressC'] # प्राप्तकर्ता पता
+```
+
+इस कॉन्फ़िगरेशन में:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- Subgraph उन कई पतों के बीच होने वाले लेनदेन को दोनों दिशाओं में सूचीबद्ध करेगा, जिससे सभी पतों के बीच इंटरैक्शन की व्यापक निगरानी संभव हो सकेगी।
+
+## घोषित eth_call
+
+> नोट: यह एक प्रयोगात्मक फीचर है जो अभी तक स्थिर Graph Node रिलीज़ में उपलब्ध नहीं है। आप इसे केवल Subgraph Studio या अपने स्वयं-होस्टेड नोड में ही उपयोग कर सकते हैं।
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+यह फ़ीचर निम्नलिखित कार्य करता है:
+
+- इथेरियम ब्लॉकचेन से डेटा प्राप्त करने के प्रदर्शन में महत्वपूर्ण सुधार करता है, जिससे कई कॉल के लिए कुल समय कम होता है और सबग्राफ की समग्र दक्षता का अनुकूलन होता है।
+- यह तेजी से डेटा फ़ेचिंग की अनुमति देता है, जिससे तेजी से क्वेरी प्रतिक्रियाएँ और बेहतर उपयोगकर्ता अनुभव मिलता है।
+- कई Ethereum कॉल्स से डेटा को एकत्रित करने की आवश्यकता वाली अनुप्रयोगों के लिए प्रतीक्षा समय को कम करता है, जिससे डेटा पुनर्प्राप्ति प्रक्रिया अधिक प्रभावी हो जाती है।
+
+### मुख्य अवधारणाएँ
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- समानांतर निष्पादन: एक कॉल समाप्त होने की प्रतीक्षा करने के बजाय, कई कॉल एक साथ आरंभ किए जा सकते हैं।
+- समय दक्षता: सभी कॉल के लिए कुल समय व्यक्तिगत कॉल के समय के योग (अनुक्रमिक) से बदलकर सबसे लंबे कॉल के द्वारा लिए गए समय (समानांतर) में बदल जाता है।
+
+#### Scenario without Declarative `eth_calls`
+
+आपके पास एक subgraph है जिसे एक उपयोगकर्ता के लेनदेन, बैलेंस और टोकन होल्डिंग्स के बारे में डेटा प्राप्त करने के लिए तीन Ethereum कॉल करने की आवश्यकता है।
+
+परंपरागत रूप से, ये कॉल क्रमिक रूप से की जा सकती हैं:
+
+1. कॉल 1 (लेनदेन): 3 सेकंड लेता है
+2. कॉल 2 (शेष): 2 सेकंड लेता है
+3. कॉल 3 (टोकन होल्डिंग्स): लेता है 4 सेकंड
+
+कुल समय लिया गया = 3 + 2 + 4 = 9 सेकंड
+
+#### Scenario with Declarative `eth_calls`
+
+इस फीचर के साथ, आप इन कॉल्स को समानांतर में निष्पादित करने के लिए घोषित कर सकते हैं:
+
+1. कॉल 1 (लेनदेन): 3 सेकंड लेता है
+2. कॉल 2 (शेष): 2 सेकंड लेता है
+3. कॉल 3 (टोकन होल्डिंग्स): लेता है 4 सेकंड
+
+चूंकि ये कॉल समानांतर में निष्पादित होते हैं, कुल समय लिया गया सबसे लंबे कॉल के समय के बराबर होता है।
+
+कुल समय = max (3, 2, 4) = 4 सेकंड
+
+#### कैसे कार्य करता है
+
+1. In the subgraph manifest, आप Ethereum कॉल्स को इस तरह घोषित करते हैं कि ये समानांतर में निष्पादित किए जा सकें।
+2. पैरलेल निष्पादन इंजन: The Graph Node का निष्पादन इंजन इन घोषणाओं को पहचानता है और कॉल को समानांतर में चलाता है।
+3. परिणाम संग्रहण: जब सभी कॉल समाप्त हो जाते हैं, तो परिणामों को एकत्रित किया जाता है और आगे की प्रक्रिया के लिए उपयोग किया जाता है।
+
+#### उदाहरण कॉन्फ़िगरेशन Subgraph मैनिफेस्ट में
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+उदाहरण उपरोक्त के लिए विवरण:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+
+```
+
+### मौजूदा सबग्राफ पर ग्राफ्टिंग
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+क्योंकि आधार डेटा को अनुक्रमित करने के बजाय प्रतियों को ग्राफ्ट करना, स्क्रैच से अनुक्रमणित करने की तुलना में सबग्राफ को वांछित ब्लॉक में प्राप्त करना बहुत तेज है, हालांकि बहुत बड़े सबग्राफ के लिए प्रारंभिक डेटा कॉपी में अभी भी कई घंटे लग सकते हैं। जबकि ग्राफ्टेड सबग्राफ को इनिशियलाइज़ किया जा रहा है, ग्राफ़ नोड उन एंटिटी प्रकारों के बारे में जानकारी लॉग करेगा जो पहले ही कॉपी किए जा चुके हैं।
+
+ग्राफ्टेड सबग्राफ एक ग्राफक्यूएल स्कीमा का उपयोग कर सकता है जो बेस सबग्राफ के समान नहीं है, लेकिन इसके साथ केवल संगत है। यह अपने आप में एक मान्य सबग्राफ स्कीमा होना चाहिए, लेकिन निम्नलिखित तरीकों से बेस सबग्राफ के स्कीमा से विचलित हो सकता है:
+
+- यह इकाई प्रकार जोड़ता या हटाता है
+- यह इकाई प्रकारों से विशेषताएँ निकालता है
+- यह प्रभावहीन गुणों को इकाई प्रकारों में जोड़ता है|
+- यह प्रभाव वाले गुणों को प्रभावहीन गुणों में बदल देता है|
+- यह इनम्स में महत्व देता है|
+- यह इंटरफेस जोड़ता या हटाता है|
+- यह कि, किन इकाई प्रकारों के लिए इंटरफ़ेस लागू होगा, इसे बदल देता है|
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From e1e34e3c33151064e9e84ed5dd90e1aeba1552ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:24 -0500
Subject: [PATCH 0389/1325] New translations assemblyscript-mappings.mdx
 (Hindi)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/hi/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/hi/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/hi/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..38441c623127
--- /dev/null
+++ b/website/pages/hi/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## अवलोकन
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## मैपिंग लिखना
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### नई संस्थाओं को बनाने के लिए अनुशंसित आईडी
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### एक समान आईडी वाले एंटिटीज़ का प्रबंधन
+
+जब एक नई इकाई बनाते और सहेजते हैं, यदि एक ही ID वाली इकाई पहले से मौजूद है, तो मर्ज प्रक्रिया के दौरान नई इकाई के गुणों को हमेशा प्राथमिकता दी जाती है। इसका मतलब है कि मौजूदा इकाई को नई इकाई के मानों के साथ अपडेट किया जाएगा।
+
+यदि एक नया एन्टिटी जिसमें समान ID है, के लिए किसी फील्ड के लिए जानबूझकर एक null मान सेट किया जाता है, तो मौजूदा एन्टिटी को null मान के साथ अपडेट किया जाएगा।
+
+यदि समान ID वाली नई entity में किसी field के लिए कोई मान set नहीं किया गया है, तो field का result भी null हो जाएगा।
+
+## कोड जनरेशन
+
+स्मार्ट कॉन्ट्रैक्ट्स, इवेंट्स और एंटिटीज के साथ काम करना आसान और टाइप-सेफ बनाने के लिए, ग्राफ सीएलआई सबग्राफ के ग्राफक्यूएल स्कीमा और डेटा स्रोतों में शामिल कॉन्ट्रैक्ट एबीआई से असेंबलीस्क्रिप्ट प्रकार उत्पन्न कर सकता है।
+
+इसके साथ किया जाता है
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From 7b7822395a197488d3979284a28917e1397d51ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:25 -0500
Subject: [PATCH 0390/1325] New translations install-the-cli.mdx (Hindi)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..d9660acfb4b2
--- /dev/null
+++ b/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: . ग्राफ़ सीएलआई इनस्टॉल करें
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## अवलोकन
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## शुरू करना
+
+### . ग्राफ़ सीएलआई इनस्टॉल करें
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+अपनी स्थानीय मशीन पर, निम्न आदेशों में से कोई एक चलाएँ:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## एक सबग्राफ बनाएं
+
+### एक मौजूदा कॉन्ट्रैक्ट से
+
+यह कमांड एक subgraph बनाता है जो एक मौजूदा कॉन्ट्रैक्ट के सभी इवेंट्स को इंडेक्स करता है:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- कमांड Etherscan से कॉन्ट्रैक्ट ABI को पुनः प्राप्त करने की कोशिश करता है।
+
+  - The Graph CLI एक सार्वजनिक RPC एंडपॉइंट पर निर्भर करता है। जबकि कुछ असफलताएँ अपेक्षित हैं, पुनः प्रयास आमतौर पर इस समस्या को हल कर देते हैं। यदि असफलताएँ बनी रहती हैं, तो एक स्थानीय ABI का उपयोग करने पर विचार करें।
+
+- यदि कोई वैकल्पिक तर्क गायब है, तो यह आपको एक इंटरैक्टिव फॉर्म के माध्यम से मार्गदर्शन करता है।
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### एक उदाहरण सबग्राफ से
+
+निम्नलिखित कमांड एक उदाहरण subgraph से एक नया प्रोजेक्ट प्रारंभ करता है:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### विशिष्टताएँ
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### एबीआई प्राप्त करना
+
+एबीआई फाइल(फाइलों) को आपके अनुबंध(ओं) से मेल खाना चाहिए। ABI फ़ाइलें प्राप्त करने के कुछ तरीके हैं:
+
+- यदि आप अपना खुद का प्रोजेक्ट बना रहे हैं, तो आपके पास अपने सबसे मौजूदा एबीआई तक पहुंच होने की संभावना है।
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## स्पेकवर्जन रिलीज़
+
+| संस्करण | रिलीज नोट्स                                                                                                                                                              |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है।                                                                                          |
+|  0.0.4  | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है।                                                                                          |

From 8336c0aa86d2b2cc01fbc0003baa85ee63ad33a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:26 -0500
Subject: [PATCH 0391/1325] New translations ql-schema.mdx (Hindi)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..a554978d786b
--- /dev/null
+++ b/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## अवलोकन
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### संपत्ति परिभाषित करना
+
+इससे पहले कि आप एन्टिटीज को परिभाषित करें, यह महत्वपूर्ण है कि आप एक कदम पीछे हटें और सोचें कि आपका डेटा कैसे संरचित और लिंक किया गया है।
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- यह उपयोगी हो सकता है कि संस्थाओं की कल्पना 'डेटा' समाहित करने वाले वस्तुओं के रूप में की जाए, न कि घटनाओं या कार्यों के रूप में।
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- डिफ़ॉल्ट रूप से, संस्थाएँ परिवर्तनीय होती हैं, जिसका अर्थ है कि मैपिंग मौजूदा संस्थाओं को लोड कर सकती हैं, उन्हें संशोधित कर सकती हैं और उस संस्थान के एक नए संस्करण को संग्रहीत कर सकती हैं।
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - अगर किसी एंटिटी को बनाने वाले उसी ब्लॉक में परिवर्तन होते हैं, तो मैपिंग्स अम्यूटेबल एंटिटीज़ में परिवर्तन कर सकती हैं। अम्यूटेबल एंटिटीज़ को लिखने और क्वेरी करने में बहुत तेज़ होती हैं, इसलिए इन्हें संभव होने पर उपयोग करना चाहिए।
+
+#### अच्छा उदाहरण
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### खराब उदाहरण
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### वैकल्पिक और आवश्यक फ़ील्ड
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+गैर-शून्य फ़ील्ड 'नाम' के लिए हल किया गया शून्य मान
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### बिल्ट-इन स्केलर प्रकार
+
+#### ग्राफक्यूएल समर्थित स्केलर्स
+
+नीचे दिए गए स्केलर्स GraphQL API में समर्थित हैं:
+
+| प्रकार       | विवरण                                                                                                                                                                                                            |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | बाइट सरणी, एक हेक्साडेसिमल स्ट्रिंग के रूप में दर्शाया गया है। आमतौर पर एथेरियम हैश और पतों के लिए उपयोग किया जाता है।                                                                                           |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+आप स्कीमा के भीतर एनम भी बना सकते हैं। Enums में निम्न सिंटैक्स होता है:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### निकाय संबंध
+
+एक इकाई का आपकी स्कीमा में एक या अधिक अन्य संस्थाओं से संबंध हो सकता है। आपके प्रश्नों में इन संबंधों का पता लगाया जा सकता है। ग्राफ़ में रिश्ते यूनिडायरेक्शनल हैं। रिश्ते के किसी भी "अंत" पर एक यूनिडायरेक्शनल रिश्ते को परिभाषित करके द्विपक्षीय संबंधों को अनुकरण करना संभव है।
+
+संस्थाओं पर संबंधों को किसी अन्य क्षेत्र की तरह ही परिभाषित किया जाता है सिवाय इसके कि निर्दिष्ट प्रकार किसी अन्य इकाई का है।
+
+#### एक-से-एक संबंध
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### एक से कई रिश्ते
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### रिवर्स लुकअप
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+एक-से-अनेक संबंधों के लिए, संबंध को हमेशा 'एक' पक्ष में संग्रहीत किया जाना चाहिए, और 'अनेक' पक्ष हमेशा निकाला जाना चाहिए। संबंधों को इस तरह से संग्रहीत करने के बजाय, 'अनेक' पक्ष पर संस्थाओं की एक सरणी संग्रहीत करने के परिणामस्वरूप, सबग्राफ को अनुक्रमित करने और क्वेरी करने दोनों के लिए नाटकीय रूप से बेहतर प्रदर्शन होगा। सामान्य तौर पर, संस्थाओं की सरणियों को संग्रहीत करने से जितना संभव हो उतना बचा जाना चाहिए।
+
+#### उदाहरण
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### अनेक-से-अनेक संबंध
+
+मैनी-टू-मैनी संबंधों के लिए, जैसे कि प्रत्येक उपयोगकर्ता किसी भी संख्या में संगठनों से संबंधित हो सकता है, सबसे सरल, लेकिन आम तौर पर सबसे अधिक प्रदर्शनकारी नहीं, संबंध को मॉडल करने का तरीका शामिल दो संस्थाओं में से प्रत्येक में एक सरणी के रूप में है। यदि संबंध सममित है, तो संबंध के केवल एक पक्ष को संग्रहित करने की आवश्यकता है और दूसरे पक्ष को व्युत्पन्न किया जा सकता है।
+
+#### उदाहरण
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+इस दृष्टिकोण के लिए आवश्यक है कि प्रश्नों को पुनः प्राप्त करने के लिए एक अतिरिक्त स्तर में उतरना पड़े, उदाहरण के लिए, उपयोगकर्ताओं के लिए संगठन:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+मैनी-टू-मैनी संबंधों को संग्रहीत करने के इस अधिक विस्तृत तरीके के परिणामस्वरूप सबग्राफ के लिए कम डेटा संग्रहीत होगा, और इसलिए एक सबग्राफ के लिए जो अक्सर इंडेक्स और क्वेरी के लिए नाटकीय रूप से तेज़ होता है।
+
+### स्कीमा में टिप्पणियां जोड़ना
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## फुलटेक्स्ट सर्च फील्ड्स को परिभाषित करना
+
+पूर्ण पाठ खोज क्वेरी फ़िल्टर करती है और पाठ खोज इनपुट के आधार पर संस्थाओं को रैंक करती है। अनुक्रमित टेक्स्ट डेटा से तुलना करने से पहले क्वेरी टेक्स्ट इनपुट को तने में संसाधित करके पूर्ण टेक्स्ट क्वेरी समान शब्दों के लिए मैच वापस करने में सक्षम हैं।
+
+एक पूर्ण पाठ क्वेरी परिभाषा में क्वेरी का नाम, पाठ फ़ील्ड को संसाधित करने के लिए उपयोग किया जाने वाला भाषा शब्दकोश, परिणामों को क्रमबद्ध करने के लिए उपयोग किया जाने वाला रैंकिंग एल्गोरिदम और खोज में शामिल फ़ील्ड शामिल हैं। प्रत्येक पूर्ण-पाठ क्वेरी में कई फ़ील्ड शामिल हो सकते हैं, लेकिन सभी शामिल फ़ील्ड एक इकाई प्रकार से होने चाहिए।
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## भाषाओं का समर्थन किया
+
+एक अलग भाषा का चयन एक निश्चित, हालांकि कभी-कभी सूक्ष्म, पूर्ण पाठ खोज एपीआई पर प्रभाव डालेगा। पूर्ण-पाठ क्वेरी फ़ील्ड द्वारा कवर किए गए फ़ील्ड को चुनी हुई भाषा के संदर्भ में जांचा जाता है, इसलिए विश्लेषण और खोज क्वेरी द्वारा उत्पन्न शब्दांश भाषा से भाषा में भिन्न होते हैं। उदाहरण के लिए: समर्थित तुर्की शब्दकोश "टोकन" का उपयोग करते समय "टोकन" के लिए स्टेम किया जाता है, जबकि निश्चित रूप से, अंग्रेजी शब्दकोश इसे "टोकन" के लिए स्टेम करेगा।
+
+समर्थित भाषा शब्दकोश:
+
+| Code   | शब्दकोष    |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | पुर्तगाली  |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### रैंकिंग एल्गोरिदम
+
+परिणाम ऑर्डर करने के लिए समर्थित एल्गोरिदम:
+
+| Algorithm     | Description                                                                               |
+| ------------- | ----------------------------------------------------------------------------------------- |
+| rank          | परिणामों को व्यवस्थित करने के लिए पूर्ण पाठ क्वेरी की मिलान गुणवत्ता (0-1) का उपयोग करें। |
+| proximityRank | Similar to rank but also includes the proximity of the matches.                           |

From f9166d46f841f7df5e143766d433cf22d18cb749 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:27 -0500
Subject: [PATCH 0392/1325] New translations subgraph-manifest.mdx (Hindi)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..7a554404dd2c
--- /dev/null
+++ b/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## अवलोकन
+
+subgraph मैनिफेस्ट, subgraph.yaml, उन स्मार्ट कॉन्ट्रैक्ट्स और नेटवर्क को परिभाषित करता है जिन्हें आपका subgraph इंडेक्स करेगा, इन कॉन्ट्रैक्ट्स से ध्यान देने योग्य इवेंट्स, और इवेंट डेटा को उन संस्थाओं के साथ मैप करने का तरीका जिन्हें Graph Node स्टोर करता है और जिन्हें क्वेरी करने की अनुमति देता है।
+
+**subgraph definition** में निम्नलिखित फ़ाइलें शामिल हैं:
+
+- subgraph.yaml: में subgraph मैनिफेस्ट शामिल है
+
+- schema.graphql: एक GraphQL स्कीमा जो आपके लिए डेटा को परिभाषित करता है और इसे GraphQL के माध्यम से क्वेरी करने का तरीका बताता है.
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph क्षमताएँ
+
+एक सिंगल subgraph कर सकता है:
+
+- कई स्मार्ट कॉन्ट्रैक्ट्स से डेटा को इंडेक्स करें (लेकिन कई नेटवर्क नहीं)।
+
+- IPFS फ़ाइलों से डेटा को डेटा स्रोत फ़ाइलें  का उपयोग करके अनुक्रमित करें।
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+मेनिफेस्ट के लिए अद्यतन करने के लिए महत्वपूर्ण प्रविष्टियां हैं:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## आयोजन Handlers
+
+Event handlers एक subgraph में स्मार्ट कॉन्ट्रैक्ट्स द्वारा ब्लॉकचेन पर उत्पन्न होने वाले विशिष्ट घटनाओं पर प्रतिक्रिया करते हैं और subgraph के मैनिफेस्ट में परिभाषित हैंडलर्स को ट्रिगर करते हैं। इससे subgraphs को परिभाषित लॉजिक के अनुसार घटना डेटा को प्रोसेस और स्टोर करने की अनुमति मिलती है।
+
+### इवेंट हैंडलर को परिभाषित करना
+
+एक event handler को डेटा स्रोत के भीतर subgraph के YAML configuration में घोषित किया जाता है। यह निर्दिष्ट करता है कि कौन से events पर ध्यान देना है और उन events का पता चलने पर कार्यान्वित करने के लिए संबंधित function क्या है।
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## कॉल हैंडलर्स
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+कॉल हैंडलर केवल दो मामलों में से एक में ट्रिगर होंगे: जब निर्दिष्ट फ़ंक्शन को अनुबंध के अलावा किसी अन्य खाते द्वारा कॉल किया जाता है या जब इसे सॉलिडिटी में बाहरी के रूप में चिह्नित किया जाता है और उसी अनुबंध में किसी अन्य फ़ंक्शन के भाग के रूप में कॉल किया जाता है।
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### कॉल हैंडलर को परिभाषित करना
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### मानचित्रण समारोह
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## ब्लॉक हैंडलर
+
+Contract events या function calls की सदस्यता लेने के अलावा, एक subgraph अपने data को update करना चाह सकता है क्योंकि chain में नए blocks जोड़े जाते हैं। इसे प्राप्त करने के लिए एक subgraph every block के बाद या pre-defined filter से match होन वाले block के बाद एक function चला सकता है।
+
+### समर्थित फ़िल्टर
+
+#### कॉल फ़िल्टर
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+ब्लॉक हैंडलर के लिए फ़िल्टर की अनुपस्थिति सुनिश्चित करेगी कि हैंडलर को प्रत्येक ब्लॉक कहा जाता है। डेटा स्रोत में प्रत्येक फ़िल्टर प्रकार के लिए केवल एक ब्लॉक हैंडलर हो सकता है।
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### मतदान फ़िल्टर
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once फ़िल्टर
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+'once' फ़िल्टर के साथ परिभाषित हैंडलर केवल एक बार सभी अन्य हैंडलर्स चलने से पहले कॉल किया जाएगा। यह कॉन्फ़िगरेशन 'subgraph' को प्रारंभिक हैंडलर के रूप में उपयोग करने की अनुमति देता है, जिससे 'indexing' के शुरू होने पर विशिष्ट कार्य किए जा सकते हैं।
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### मानचित्रण समारोह
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## अनाम घटनाएँ
+
+यदि आपको अनाम घटनाओं को सॉलिडिटी में संसाधित करने की आवश्यकता है, तो इसे घटना के विषय 0 प्रदान करके प्राप्त किया जा सकता है, जैसा कि उदाहरण में है:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## इवेंट हैंडलर में लेनदेन रसीदें
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## ट्रिगरिंग हैंडलर्स का क्रम
+
+निम्नलिखित प्रक्रिया का उपयोग करके एक ब्लॉक के भीतर डेटा स्रोत के लिए ट्रिगर्स का आदेश दिया गया है:
+
+1. ईवेंट और कॉल ट्रिगर्स को पहले ब्लॉक के भीतर ट्रांजैक्शन इंडेक्स द्वारा ऑर्डर किया जाता है।
+2. एक ही लेन-देन के भीतर ईवेंट और कॉल ट्रिगर्स को एक कन्वेंशन का उपयोग करके ऑर्डर किया जाता है: ईवेंट पहले ट्रिगर करता है फिर ट्रिगर्स को कॉल करता है, प्रत्येक प्रकार के ऑर्डर का सम्मान करते हुए उन्हें मेनिफेस्ट में परिभाषित किया जाता है।
+3. ब्लॉक ट्रिगर इवेंट और कॉल ट्रिगर के बाद चलाए जाते हैं, जिस क्रम में उन्हें मेनिफेस्ट में परिभाषित किया गया है।
+
+ये आदेश नियम परिवर्तन के अधीन हैं।
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## डेटा स्रोत टेम्पलेट्स
+
+ईवीएम-संगत स्मार्ट अनुबंधों में एक सामान्य पैटर्न रजिस्ट्री या फ़ैक्टरी अनुबंधों का उपयोग होता है, जहां एक अनुबंध अन्य अनुबंधों की मनमानी संख्या का निर्माण, प्रबंधन या संदर्भ करता है, जिनमें से प्रत्येक का अपना राज्य और ईवेंट होता है।
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### मुख्य अनुबंध के लिए डेटा स्रोत
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### गतिशील रूप से बनाए गए अनुबंधों के लिए डेटा स्रोत टेम्प्लेट
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### डेटा स्रोत टेम्प्लेट को इंस्टेंट करना
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> यदि पिछले ब्लॉक में नए डेटा स्रोत के लिए प्रासंगिक डेटा है, तो उस डेटा को अनुबंध की वर्तमान स्थिति को पढ़कर और नए डेटा स्रोत के निर्माण के समय उस स्थिति का प्रतिनिधित्व करने वाली संस्थाओं का निर्माण करना सबसे अच्छा है।
+
+### डेटा स्रोत प्रसंग
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. खोज बार में उसका पता दर्ज करके अनुबंध की खोज करें।
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. लेन-देन विवरण पृष्ठ लोड करें जहां आपको उस अनुबंध के लिए प्रारंभ ब्लॉक मिलेगा।
+
+## Indexer संकेत
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. एक विशेष संख्या: ऐतिहासिक ब्लॉकों की एक कस्टम सीमा निर्धारित करता है जिन्हें बनाए रखा जाना है।
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> इस संदर्भ में "history" का अर्थ उन आंकड़ों को संग्रहीत करने से है जो 'mutable' संस्थाओं की पुरानी स्थितियों को दर्शाते हैं।
+
+दिए गए ब्लॉक के रूप में इतिहास की आवश्यकता है:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- उस ब्लॉक पर 'subgraph' को वापस लाना
+
+यदि ब्लॉक के रूप में ऐतिहासिक डेटा को प्रून किया गया है, तो उपरोक्त क्षमताएँ उपलब्ध नहीं होंगी।
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+विशिष्ट मात्रा में ऐतिहासिक डेटा बनाए रखने के लिए:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+पूरे 'entity' राज्यों का इतिहास बनाए रखने के लिए:
+
+```
+indexerHints:
+  prune: never
+```

From c525c3a4cbbc3c1c68f67dcd4c2cbfdef6794c49 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:28 -0500
Subject: [PATCH 0393/1325] New translations subgraphs.mdx (Swahili)

---
 website/pages/sw/subgraphs.mdx | 86 ++++++++++++++++++++++++++++++++++
 1 file changed, 86 insertions(+)
 create mode 100644 website/pages/sw/subgraphs.mdx

diff --git a/website/pages/sw/subgraphs.mdx b/website/pages/sw/subgraphs.mdx
new file mode 100644
index 000000000000..42c1e806f822
--- /dev/null
+++ b/website/pages/sw/subgraphs.mdx
@@ -0,0 +1,86 @@
+---
+title: Subgraphs
+---
+
+## What is a Subgraph?
+
+A subgraph is a custom, open API that extracts data from a blockchain, processes it, and stores it so it can be easily queried via GraphQL.
+
+### Subgraph Capabilities
+
+- **Access Data:** Subgraphs enable the querying and indexing of blockchain data for web3.
+- **Build:** Developers can build, deploy, and publish subgraphs to The Graph Network. To get started, check out the subgraph developer [Quick Start](quick-start/).
+- **Index & Query:** Once a subgraph is indexed, anyone can query it. Explore and query all subgraphs published to the network in [Graph Explorer](https://thegraph.com/explorer).
+
+## Inside a Subgraph
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema
+
+To learn more about each subgraph component, check out [creating a subgraph](/developing/creating-a-subgraph/).
+
+## Subgraph Lifecycle
+
+Here is a general overview of a subgraph’s lifecycle:
+
+![Subgraph Lifecycle](/img/subgraph-lifecycle.png)
+
+## Subgraph Development
+
+1. [Create a subgraph](/developing/creating-a-subgraph/)
+2. [Deploy a subgraph](/deploying/deploying-a-subgraph-to-studio/)
+3. [Test a subgraph](/deploying/subgraph-studio/#testing-your-subgraph-in-subgraph-studio)
+4. [Publish a subgraph](/publishing/publishing-a-subgraph/)
+5. [Signal on a subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph)
+
+### Build locally
+
+Great subgraphs start with a local development environment and unit tests. Developers use [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli), a command-line interface tool for building and deploying subgraphs on The Graph. They can also use [Graph TypeScript](/developing/graph-ts/) and [Matchstick](/developing/unit-testing-framework/) to create robust subgraphs.
+
+### Deploy to Subgraph Studio
+
+Once defined, a subgraph can be [deployed to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio/). In Subgraph Studio, you can do the following:
+
+- Use its staging environment to index the deployed subgraph and make it available for review.
+- Verify that your subgraph doesn't have any indexing errors and works as expected.
+
+### Publish to the Network
+
+When you're happy with your subgraph, you can [publish it](/publishing/publishing-a-subgraph/) to The Graph Network.
+
+- This is an on-chain action, which registers the subgraph and makes it discoverable by Indexers.
+- Published subgraphs have a corresponding NFT, which defines the ownership of the subgraph. You can [transfer the subgraph's ownership](/managing/transfer-a-subgraph/) by sending the NFT.
+- Published subgraphs have associated metadata, which provides other network participants with useful context and information.
+
+### Add Curation Signal for Indexing
+
+Published subgraphs are unlikely to be picked up by Indexers without curation signal. To encourage indexing you should add signal to your subgraph. Learn more about signaling and [curating](/network/curating/) on The Graph.
+
+#### What is signal?
+
+- Signal is locked GRT associated with a given subgraph. It indicates to Indexers that a given subgraph will receive query volume and it contributes to the indexing rewards available for processing it.
+- Third-party Curators may also signal on a given subgraph, if they deem the subgraph likely to drive query volume.
+
+### Querying & Application Development
+
+Subgraphs on The Graph Network receive 100,000 free queries per month, after which point developers can either [pay for queries with GRT or a credit card](/billing/).
+
+Learn more about [querying subgraphs](/querying/querying-the-graph/).
+
+### Updating Subgraphs
+
+To update your subgraph with bug fixes or new functionalities, initiate a transaction to point it to the new version. You can deploy new versions of your subgraphs to [Subgraph Studio](https://thegraph.com/studio/) for development and testing.
+
+- If you selected "auto-migrate" when you applied the signal, updating the subgraph will migrate any signal to the new version and incur a migration tax.
+- This signal migration should prompt Indexers to start indexing the new version of the subgraph, so it should soon become available for querying.
+
+### Deleting & Transferring Subgraphs
+
+If you no longer need a published subgraph, you can [delete](/managing/delete-a-subgraph/) or [transfer](/managing/transfer-a-subgraph/) it. Deleting a subgraph returns any signaled GRT to [Curators](/network/curating/).

From 931e221b7e3e35c9c361c4d68566ee4658b8ccef Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:29 -0500
Subject: [PATCH 0394/1325] New translations transfer-to-the-graph.mdx
 (Swahili)

---
 .../sw/cookbook/transfer-to-the-graph.mdx     | 104 ++++++++++++++++++
 1 file changed, 104 insertions(+)
 create mode 100644 website/pages/sw/cookbook/transfer-to-the-graph.mdx

diff --git a/website/pages/sw/cookbook/transfer-to-the-graph.mdx b/website/pages/sw/cookbook/transfer-to-the-graph.mdx
new file mode 100644
index 000000000000..6a5d2c2793f3
--- /dev/null
+++ b/website/pages/sw/cookbook/transfer-to-the-graph.mdx
@@ -0,0 +1,104 @@
+---
+title: Tranfer to The Graph
+---
+
+Quickly upgrade your subgraphs from any platform to [The Graph's decentralized network](https://thegraph.com/networks/).
+
+## Benefits of Switching to The Graph
+
+- Use the same subgraph that your apps already use with zero-downtime migration.
+- Increase reliability from a global network supported by 100+ Indexers.
+- Receive lightning-fast support for subgraphs 24/7, with an on-call engineering team.
+
+## Upgrade Your Subgraph to The Graph in 3 Easy Steps
+
+1. [Set Up Your Studio Environment](/cookbook/transfer-to-the-graph/#1-set-up-your-studio-environment)
+2. [Deploy Your Subgraph to Studio](/cookbook/transfer-to-the-graph/#2-deploy-your-subgraph-to-studio)
+3. [Publish to The Graph Network](/cookbook/transfer-to-the-graph/#publish-your-subgraph-to-the-graphs-decentralized-network)
+
+## 1. Set Up Your Studio Environment
+
+### Create a Subgraph in Subgraph Studio
+
+- Go to [Subgraph Studio](https://thegraph.com/studio/) and connect your wallet.
+- Click "Create a Subgraph". It is recommended to name the subgraph in Title Case: "Subgraph Name Chain Name".
+
+> Note: After publishing, the subgraph name will be editable but requires on-chain action each time, so name it properly.
+
+### Install the Graph CLI⁠
+
+You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm` or `pnpm`) installed to use the Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run the following command:
+
+Using [npm](https://www.npmjs.com/):
+
+```sh
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+Use the following command to create a subgraph in Studio using the CLI:
+
+```sh
+graph init --product subgraph-studio
+```
+
+### Authenticate Your Subgraph
+
+In The Graph CLI, use the auth command seen in Subgraph Studio:
+
+```sh
+graph auth <your-auth-code>
+```
+
+## 2. Deploy Your Subgraph to Studio
+
+If you have your source code, you can easily deploy it to Studio. If you don't have it, here's a quick way to deploy your subgraph.
+
+In The Graph CLI, run the following command:
+
+```sh
+graph deploy <slug> --ipfs-hash <your-subgraph-ipfs-hash>
+
+```
+
+> **Note:** Every subgraph has an IPFS hash (Deployment ID), which looks like this: "Qmasdfad...". To deploy simply use this **IPFS hash**. You’ll be prompted to enter a version (e.g., v0.0.1).
+
+## 3. Publish Your Subgraph to The Graph Network
+
+![publish button](/img/publish-sub-transfer.png)
+
+### Query Your Subgraph
+
+> To attract about 3 indexers to query your subgraph, it’s recommended to curate at least 3,000 GRT. To learn more about curating, check out [Curating](/network/curating/) on The Graph.
+
+You can start [querying](/querying/querying-the-graph/) any subgraph by sending a GraphQL query into the subgraph’s query URL endpoint, which is located at the top of its Explorer page in Subgraph Studio.
+
+#### Example
+
+[CryptoPunks Ethereum subgraph](https://thegraph.com/explorer/subgraphs/HdVdERFUe8h61vm2fDyycHgxjsde5PbB832NHgJfZNqK) by Messari:
+
+![Query URL](/img/cryptopunks-screenshot-transfer.png)
+
+The query URL for this subgraph is:
+
+```sh
+https://gateway-arbitrum.network.thegraph.com/api/`**your-own-api-key**`/subgraphs/id/HdVdERFUe8h61vm2fDyycgxjsde5PbB832NHgJfZNqK
+```
+
+Now, you simply need to fill in **your own API Key** to start sending GraphQL queries to this endpoint.
+
+### Getting your own API Key
+
+You can create API Keys in Subgraph Studio under the “API Keys” menu at the top of the page:
+
+![API keys](/img/Api-keys-screenshot.png)
+
+### Monitor Subgraph Status
+
+Once you upgrade, you can access and manage your subgraphs in [Subgraph Studio](https://thegraph.com/studio/) and explore all subgraphs in [The Graph Explorer](https://thegraph.com/networks/).
+
+### Additional Resources
+
+- To quickly create and publish a new subgraph, check out the [Quick Start](/quick-start/).
+- To explore all the ways you can optimize and customize your subgraph for a better performance, read more about [creating a subgraph here](/developing/creating-a-subgraph/).

From dbb6ab211f37b920390bba94873a78824b8fd824 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:30 -0500
Subject: [PATCH 0395/1325] New translations advanced.mdx (Swahili)

---
 .../creating-a-subgraph/advanced.mdx          | 555 ++++++++++++++++++
 1 file changed, 555 insertions(+)
 create mode 100644 website/pages/sw/developing/creating-a-subgraph/advanced.mdx

diff --git a/website/pages/sw/developing/creating-a-subgraph/advanced.mdx b/website/pages/sw/developing/creating-a-subgraph/advanced.mdx
new file mode 100644
index 000000000000..3a08ddab7066
--- /dev/null
+++ b/website/pages/sw/developing/creating-a-subgraph/advanced.mdx
@@ -0,0 +1,555 @@
+---
+title: Advance Subgraph Features
+---
+
+## Overview
+
+Add and implement advanced subgraph features to enhanced your subgraph's built.
+
+Starting from `specVersion` `0.0.4`, subgraph features must be explicitly declared in the `features` section at the top level of the manifest file, using their `camelCase` name, as listed in the table below:
+
+| Feature                                              | Name             |
+| ---------------------------------------------------- | ---------------- |
+| [Non-fatal errors](#non-fatal-errors)                | `nonFatalErrors` |
+| [Full-text Search](#defining-fulltext-search-fields) | `fullTextSearch` |
+| [Grafting](#grafting-onto-existing-subgraphs)        | `grafting`       |
+
+For instance, if a subgraph uses the **Full-Text Search** and the **Non-fatal Errors** features, the `features` field in the manifest should be:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+  - fullTextSearch
+  - nonFatalErrors
+dataSources: ...
+```
+
+> Note that using a feature without declaring it will incur a **validation error** during subgraph deployment, but no errors will occur if a feature is declared but not used.
+
+## Timeseries and Aggregations
+
+Timeseries and aggregations enable your subgraph to track statistics like daily average price, hourly total transfers, etc.
+
+This feature introduces two new types of subgraph entity. Timeseries entities record data points with timestamps. Aggregation entities perform pre-declared calculations on the Timeseries data points on an hourly or daily basis, then store the results for easy access via GraphQL.
+
+### Example Schema
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+### Defining Timeseries and Aggregations
+
+Timeseries entities are defined with `@entity(timeseries: true)` in schema.graphql. Every timeseries entity must have a unique ID of the int8 type, a timestamp of the Timestamp type, and include data that will be used for calculation by aggregation entities. These Timeseries entities can be saved in regular trigger handlers, and act as the “raw data” for the Aggregation entities.
+
+Aggregation entities are defined with `@aggregation` in schema.graphql. Every aggregation entity defines the source from which it will gather data (which must be a Timeseries entity), sets the intervals (e.g., hour, day), and specifies the aggregation function it will use (e.g., sum, count, min, max, first, last). Aggregation entities are automatically calculated on the basis of the specified source at the end of the required interval.
+
+#### Available Aggregation Intervals
+
+- `hour`: sets the timeseries period every hour, on the hour.
+- `day`: sets the timeseries period every day, starting and ending at 00:00.
+
+#### Available Aggregation Functions
+
+- `sum`: Total of all values.
+- `count`: Number of values.
+- `min`: Minimum value.
+- `max`: Maximum value.
+- `first`: First value in the period.
+- `last`: Last value in the period.
+
+#### Example Aggregations Query
+
+```graphql
+{
+  stats(interval: "hour", where: { timestamp_gt: 1704085200 }) {
+    id
+    timestamp
+    sum
+  }
+}
+```
+
+Note:
+
+To use Timeseries and Aggregations, a subgraph must have a spec version ≥1.1.0. Note that this feature might undergo significant changes that could affect backward compatibility.
+
+[Read more](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) about Timeseries and Aggregations.
+
+## Non-fatal errors
+
+Indexing errors on already synced subgraphs will, by default, cause the subgraph to fail and stop syncing. Subgraphs can alternatively be configured to continue syncing in the presence of errors, by ignoring the changes made by the handler which provoked the error. This gives subgraph authors time to correct their subgraphs while queries continue to be served against the latest block, though the results might be inconsistent due to the bug that caused the error. Note that some errors are still always fatal. To be non-fatal, the error must be known to be deterministic.
+
+> **Note:** The Graph Network does not yet support non-fatal errors, and developers should not deploy subgraphs using that functionality to the network via the Studio.
+
+Enabling non-fatal errors requires setting the following feature flag on the subgraph manifest:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+features:
+    - nonFatalErrors
+    ...
+```
+
+The query must also opt-in to querying data with potential inconsistencies through the `subgraphError` argument. It is also recommended to query `_meta` to check if the subgraph has skipped over errors, as in the example:
+
+```graphql
+foos(first: 100, subgraphError: allow) {
+  id
+}
+
+_meta {
+  hasIndexingErrors
+}
+```
+
+If the subgraph encounters an error, that query will return both the data and a graphql error with the message `"indexing_error"`, as in this example response:
+
+```graphql
+"data": {
+    "foos": [
+        {
+          "id": "0xdead"
+        }
+    ],
+    "_meta": {
+        "hasIndexingErrors": true
+    }
+},
+"errors": [
+    {
+        "message": "indexing_error"
+    }
+]
+```
+
+## IPFS/Arweave File Data Sources
+
+File data sources are a new subgraph functionality for accessing off-chain data during indexing in a robust, extendable way. File data sources support fetching files from IPFS and from Arweave.
+
+> This also lays the groundwork for deterministic indexing of off-chain data, as well as the potential introduction of arbitrary HTTP-sourced data.
+
+### Overview
+
+Rather than fetching files "in line" during handler execution, this introduces templates which can be spawned as new data sources for a given file identifier. These new data sources fetch the files, retrying if they are unsuccessful, running a dedicated handler when the file is found.
+
+This is similar to the [existing data source templates](/developing/creating-a-subgraph/#data-source-templates), which are used to dynamically create new chain-based data sources.
+
+> This replaces the existing `ipfs.cat` API
+
+### Upgrade guide
+
+#### Update `graph-ts` and `graph-cli`
+
+File data sources requires graph-ts >=0.29.0 and graph-cli >=0.33.1
+
+#### Add a new entity type which will be updated when files are found
+
+File data sources cannot access or update chain-based entities, but must update file specific entities.
+
+This may mean splitting out fields from existing entities into separate entities, linked together.
+
+Original combined entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  externalURL: String!
+  ipfsURI: String!
+  image: String!
+  name: String!
+  description: String!
+  type: String!
+  updatedAtTimestamp: BigInt
+  owner: User!
+}
+```
+
+New, split entity:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenID: BigInt!
+  tokenURI: String!
+  ipfsURI: TokenMetadata
+  updatedAtTimestamp: BigInt
+  owner: String!
+}
+
+type TokenMetadata @entity {
+  id: ID!
+  image: String!
+  externalURL: String!
+  name: String!
+  description: String!
+}
+```
+
+If the relationship is 1:1 between the parent entity and the resulting file data source entity, the simplest pattern is to link the parent entity to a resulting file entity by using the IPFS CID as the lookup. Get in touch on Discord if you are having difficulty modelling your new file-based entities!
+
+> You can use [nested filters](/querying/graphql-api/#example-for-nested-entity-filtering) to filter parent entities on the basis of these nested entities.
+
+#### Add a new templated data source with `kind: file/ipfs` or `kind: file/arweave`
+
+This is the data source which will be spawned when a file of interest is identified.
+
+```yaml
+templates:
+  - name: TokenMetadata
+    kind: file/ipfs
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      file: ./src/mapping.ts
+      handler: handleMetadata
+      entities:
+        - TokenMetadata
+      abis:
+        - name: Token
+          file: ./abis/Token.json
+```
+
+> Currently `abis` are required, though it is not possible to call contracts from within file data sources
+
+The file data source must specifically mention all the entity types which it will interact with under `entities`. See [limitations](#limitations) for more details.
+
+#### Create a new handler to process files
+
+This handler should accept one `Bytes` parameter, which will be the contents of the file, when it is found, which can then be processed. This will often be a JSON file, which can be processed with `graph-ts` helpers ([documentation](/developing/graph-ts/api/#json-api)).
+
+The CID of the file as a readable string can be accessed via the `dataSource` as follows:
+
+```typescript
+const cid = dataSource.stringParam()
+```
+
+Example handler:
+
+```typescript
+import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
+import { TokenMetadata } from '../generated/schema'
+
+export function handleMetadata(content: Bytes): void {
+  let tokenMetadata = new TokenMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
+  if (value) {
+    const image = value.get('image')
+    const name = value.get('name')
+    const description = value.get('description')
+    const externalURL = value.get('external_url')
+
+    if (name && image && description && externalURL) {
+      tokenMetadata.name = name.toString()
+      tokenMetadata.image = image.toString()
+      tokenMetadata.externalURL = externalURL.toString()
+      tokenMetadata.description = description.toString()
+    }
+
+    tokenMetadata.save()
+  }
+}
+```
+
+#### Spawn file data sources when required
+
+You can now create file data sources during execution of chain-based handlers:
+
+- Import the template from the auto-generated `templates`
+- call `TemplateName.create(cid: string)` from within a mapping, where the cid is a valid content identifier for IPFS or Arweave
+
+For IPFS, Graph Node supports [v0 and v1 content identifiers](https://docs.ipfs.tech/concepts/content-addressing/), and content identifers with directories (e.g. `bafyreighykzv2we26wfrbzkcdw37sbrby4upq7ae3aqobbq7i4er3tnxci/metadata.json`).
+
+For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave based on their [transaction ID](https://docs.arweave.org/developers/arweave-node-server/http-api#transactions) from an Arweave gateway ([example file](https://bdxujjl5ev5eerd5ouhhs6o4kjrs4g6hqstzlci5pf6vhxezkgaa.arweave.net/CO9EpX0lekJEfXUOeXncUmMuG8eEp5WJHXl9U9yZUYA)). Arweave supports transactions uploaded via Irys (previously Bundlr), and Graph Node can also fetch files based on [Irys manifests](https://docs.irys.xyz/overview/gateways#indexing).
+
+Example:
+
+```typescript
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
+
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
+//This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
+
+export function handleTransfer(event: TransferEvent): void {
+  let token = Token.load(event.params.tokenId.toString())
+  if (!token) {
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
+
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
+    //This creates a path to the metadata for a single Crypto coven NFT. It concats the directory with "/" + filename + ".json"
+
+    token.ipfsURI = tokenIpfsHash
+
+    TokenMetadataTemplate.create(tokenIpfsHash)
+  }
+
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
+}
+```
+
+This will create a new file data source, which will poll Graph Node's configured IPFS or Arweave endpoint, retrying if it is not found. When the file is found, the file data source handler will be executed.
+
+This example is using the CID as the lookup between the parent `Token` entity and the resulting `TokenMetadata` entity.
+
+> Previously, this is the point at which a subgraph developer would have called `ipfs.cat(CID)` to fetch the file
+
+Congratulations, you are using file data sources!
+
+#### Deploying your subgraphs
+
+You can now `build` and `deploy` your subgraph to any Graph Node >=v0.30.0-rc.0.
+
+#### Limitations
+
+File data source handlers and entities are isolated from other subgraph entities, ensuring that they are deterministic when executed, and ensuring no contamination of chain-based data sources. To be specific:
+
+- Entities created by File Data Sources are immutable, and cannot be updated
+- File Data Source handlers cannot access entities from other file data sources
+- Entities associated with File Data Sources cannot be accessed by chain-based handlers
+
+> While this constraint should not be problematic for most use-cases, it may introduce complexity for some. Please get in touch via Discord if you are having issues modelling your file-based data in a subgraph!
+
+Additionally, it is not possible to create data sources from a file data source, be it an onchain data source or another file data source. This restriction may be lifted in the future.
+
+#### Best practices
+
+If you are linking NFT metadata to corresponding tokens, use the metadata's IPFS hash to reference a Metadata entity from the Token entity. Save the Metadata entity using the IPFS hash as an ID.
+
+You can use [DataSource context](/developing/graph-ts/api/#entity-and-datasourcecontext) when creating File Data Sources to pass extra information which will be available to the File Data Source handler.
+
+If you have entities which are refreshed multiple times, create unique file-based entities using the IPFS hash & the entity ID, and reference them using a derived field in the chain-based entity.
+
+> We are working to improve the above recommendation, so queries only return the "most recent" version
+
+#### Known issues
+
+File data sources currently require ABIs, even though ABIs are not used ([issue](https://github.com/graphprotocol/graph-cli/issues/961)). Workaround is to add any ABI.
+
+Handlers for File Data Sources cannot be in files which import `eth_call` contract bindings, failing with "unknown import: `ethereum::ethereum.call` has not been defined" ([issue](https://github.com/graphprotocol/graph-node/issues/4309)). Workaround is to create file data source handlers in a dedicated file.
+
+#### Examples
+
+[Crypto Coven Subgraph migration](https://github.com/azf20/cryptocoven-api/tree/file-data-sources-refactor)
+
+#### References
+
+[GIP File Data Sources](https://forum.thegraph.com/t/gip-file-data-sources/2721)
+
+## Indexed Argument Filters / Topic Filters
+
+> **Requires**: [SpecVersion](#specversion-releases) >= `1.2.0`
+
+Topic filters, also known as indexed argument filters, are a powerful feature in subgraphs that allow users to precisely filter blockchain events based on the values of their indexed arguments.
+
+- These filters help isolate specific events of interest from the vast stream of events on the blockchain, allowing subgraphs to operate more efficiently by focusing only on relevant data.
+
+- This is useful for creating personal subgraphs that track specific addresses and their interactions with various smart contracts on the blockchain.
+
+### How Topic Filters Work
+
+When a smart contract emits an event, any arguments that are marked as indexed can be used as filters in a subgraph's manifest. This allows the subgraph to listen selectively for events that match these indexed arguments.
+
+- The event's first indexed argument corresponds to `topic1`, the second to `topic2`, and so on, up to `topic3`, since the Ethereum Virtual Machine (EVM) allows up to three indexed arguments per event.
+
+```solidity
+// SPDX-License-Identifier: MIT
+pragma solidity ^0.8.0;
+
+contract Token {
+    // Event declaration with indexed parameters for addresses
+    event Transfer(address indexed from, address indexed to, uint256 value);
+
+    // Function to simulate transferring tokens
+    function transfer(address to, uint256 value) public {
+        // Emitting the Transfer event with from, to, and value
+        emit Transfer(msg.sender, to, value);
+    }
+}
+```
+
+In this example:
+
+- The `Transfer` event is used to log transactions of tokens between addresses.
+- The `from` and `to` parameters are indexed, allowing event listeners to filter and monitor transfers involving specific addresses.
+- The `transfer` function is a simple representation of a token transfer action, emitting the Transfer event whenever it is called.
+
+#### Configuration in Subgraphs
+
+Topic filters are defined directly within the event handler configuration in the subgraph manifest. Here is how they are configured:
+
+```yaml
+eventHandlers:
+  - event: SomeEvent(indexed uint256, indexed address, indexed uint256)
+    handler: handleSomeEvent
+    topic1: ['0xValue1', '0xValue2']
+    topic2: ['0xAddress1', '0xAddress2']
+    topic3: ['0xValue3']
+```
+
+In this setup:
+
+- `topic1` corresponds to the first indexed argument of the event, `topic2` to the second, and `topic3` to the third.
+- Each topic can have one or more values, and an event is only processed if it matches one of the values in each specified topic.
+
+#### Filter Logic
+
+- Within a Single Topic: The logic functions as an OR condition. The event will be processed if it matches any one of the listed values in a given topic.
+- Between Different Topics: The logic functions as an AND condition. An event must satisfy all specified conditions across different topics to trigger the associated handler.
+
+#### Example 1: Tracking Direct Transfers from Address A to Address B
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleDirectedTransfer
+    topic1: ['0xAddressA'] # Sender Address
+    topic2: ['0xAddressB'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` is the receiver.
+- The subgraph will only index transactions that occur directly from `0xAddressA` to `0xAddressB`.
+
+#### Example 2: Tracking Transactions in Either Direction Between Two or More Addresses
+
+```yaml
+eventHandlers:
+  - event: Transfer(indexed address,indexed address,uint256)
+    handler: handleTransferToOrFrom
+    topic1: ['0xAddressA', '0xAddressB', '0xAddressC'] # Sender Address
+    topic2: ['0xAddressB', '0xAddressC'] # Receiver Address
+```
+
+In this configuration:
+
+- `topic1` is configured to filter `Transfer` events where `0xAddressA`, `0xAddressB`, `0xAddressC` is the sender.
+- `topic2` is configured to filter `Transfer` events where `0xAddressB` and `0xAddressC` is the receiver.
+- The subgraph will index transactions that occur in either direction between multiple addresses allowing for comprehensive monitoring of interactions involving all addresses.
+
+## Declared eth_call
+
+> Note: This is an experimental feature that is not currently available in a stable Graph Node release yet. You can only use it in Subgraph Studio or your self-hosted node.
+
+Declarative `eth_calls` are a valuable subgraph feature that allows `eth_calls` to be executed ahead of time, enabling `graph-node` to execute them in parallel.
+
+This feature does the following:
+
+- Significantly improves the performance of fetching data from the Ethereum blockchain by reducing the total time for multiple calls and optimizing the subgraph's overall efficiency.
+- Allows faster data fetching, resulting in quicker query responses and a better user experience.
+- Reduces wait times for applications that need to aggregate data from multiple Ethereum calls, making the data retrieval process more efficient.
+
+### Key Concepts
+
+- Declarative `eth_calls`: Ethereum calls that are defined to be executed in parallel rather than sequentially.
+- Parallel Execution: Instead of waiting for one call to finish before starting the next, multiple calls can be initiated simultaneously.
+- Time Efficiency: The total time taken for all the calls changes from the sum of the individual call times (sequential) to the time taken by the longest call (parallel).
+
+#### Scenario without Declarative `eth_calls`
+
+Imagine you have a subgraph that needs to make three Ethereum calls to fetch data about a user's transactions, balance, and token holdings.
+
+Traditionally, these calls might be made sequentially:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Total time taken = 3 + 2 + 4 = 9 seconds
+
+#### Scenario with Declarative `eth_calls`
+
+With this feature, you can declare these calls to be executed in parallel:
+
+1. Call 1 (Transactions): Takes 3 seconds
+2. Call 2 (Balance): Takes 2 seconds
+3. Call 3 (Token Holdings): Takes 4 seconds
+
+Since these calls are executed in parallel, the total time taken is equal to the time taken by the longest call.
+
+Total time taken = max (3, 2, 4) = 4 seconds
+
+#### How it Works
+
+1. Declarative Definition: In the subgraph manifest, you declare the Ethereum calls in a way that indicates they can be executed in parallel.
+2. Parallel Execution Engine: The Graph Node's execution engine recognizes these declarations and runs the calls simultaneously.
+3. Result Aggregation: Once all calls are complete, the results are aggregated and used by the subgraph for further processing.
+
+#### Example Configuration in Subgraph Manifest
+
+Declared `eth_calls` can access the `event.address` of the underlying event as well as all the `event.params`.
+
+`Subgraph.yaml` using `event.address`:
+
+```yaml
+eventHandlers:
+event: Swap(indexed address,indexed address,int256,int256,uint160,uint128,int24)
+handler: handleSwap
+calls:
+  global0X128: Pool[event.address].feeGrowthGlobal0X128()
+  global1X128: Pool[event.address].feeGrowthGlobal1X128()
+```
+
+Details for the example above:
+
+- `global0X128` is the declared `eth_call`.
+- The text (`global0X128`) is the label for this `eth_call` which is used when logging errors.
+- The text (`Pool[event.address].feeGrowthGlobal0X128()`) is the actual `eth_call` that will be executed, which is in the form of `Contract[address].function(arguments)`
+- The `address` and `arguments` can be replaced with variables that will be available when the handler is executed.
+
+`Subgraph.yaml` using `event.params`
+
+```yaml
+calls:
+  - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
+```
+
+### Grafting onto Existing Subgraphs
+
+> **Note:** it is not recommended to use grafting when initially upgrading to The Graph Network. Learn more [here](/cookbook/grafting/#important-note-on-grafting-when-upgrading-to-the-network).
+
+When a subgraph is first deployed, it starts indexing events at the genesis block of the corresponding chain (or at the `startBlock` defined with each data source) In some circumstances; it is beneficial to reuse the data from an existing subgraph and start indexing at a much later block. This mode of indexing is called _Grafting_. Grafting is, for example, useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed.
+
+A subgraph is grafted onto a base subgraph when the subgraph manifest in `subgraph.yaml` contains a `graft` block at the top-level:
+
+```yaml
+description: ...
+graft:
+  base: Qm... # Subgraph ID of base subgraph
+  block: 7345624 # Block number
+```
+
+When a subgraph whose manifest contains a `graft` block is deployed, Graph Node will copy the data of the `base` subgraph up to and including the given `block` and then continue indexing the new subgraph from that block on. The base subgraph must exist on the target Graph Node instance and must have indexed up to at least the given block. Because of this restriction, grafting should only be used during development or during an emergency to speed up producing an equivalent non-grafted subgraph.
+
+Because grafting copies rather than indexes base data, it is much quicker to get the subgraph to the desired block than indexing from scratch, though the initial data copy can still take several hours for very large subgraphs. While the grafted subgraph is being initialized, the Graph Node will log information about the entity types that have already been copied.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+> **[Feature Management](#experimental-features):** `grafting` must be declared under `features` in the subgraph manifest.

From 64057a369dc08defc7f117d617debcfbceefcdbd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:31 -0500
Subject: [PATCH 0396/1325] New translations assemblyscript-mappings.mdx
 (Swahili)

---
 .../assemblyscript-mappings.mdx               | 113 ++++++++++++++++++
 1 file changed, 113 insertions(+)
 create mode 100644 website/pages/sw/developing/creating-a-subgraph/assemblyscript-mappings.mdx

diff --git a/website/pages/sw/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/sw/developing/creating-a-subgraph/assemblyscript-mappings.mdx
new file mode 100644
index 000000000000..2ac894695fe1
--- /dev/null
+++ b/website/pages/sw/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -0,0 +1,113 @@
+---
+title: Writing AssemblyScript Mappings
+---
+
+## Overview
+
+The mappings take data from a particular source and transform it into entities that are defined within your schema. Mappings are written in a subset of [TypeScript](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html) called [AssemblyScript](https://github.com/AssemblyScript/assemblyscript/wiki) which can be compiled to WASM ([WebAssembly](https://webassembly.org/)). AssemblyScript is stricter than normal TypeScript, yet provides a familiar syntax.
+
+## Writing Mappings
+
+For each event handler that is defined in `subgraph.yaml` under `mapping.eventHandlers`, create an exported function of the same name. Each handler must accept a single parameter called `event` with a type corresponding to the name of the event which is being handled.
+
+In the example subgraph, `src/mapping.ts` contains handlers for the `NewGravatar` and `UpdatedGravatar` events:
+
+```javascript
+import { NewGravatar, UpdatedGravatar } from '../generated/Gravity/Gravity'
+import { Gravatar } from '../generated/schema'
+
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id)
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let id = event.params.id
+  let gravatar = Gravatar.load(id)
+  if (gravatar == null) {
+    gravatar = new Gravatar(id)
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+The first handler takes a `NewGravatar` event and creates a new `Gravatar` entity with `new Gravatar(event.params.id.toHex())`, populating the entity fields using the corresponding event parameters. This entity instance is represented by the variable `gravatar`, with an id value of `event.params.id.toHex()`.
+
+The second handler tries to load the existing `Gravatar` from the Graph Node store. If it does not exist yet, it is created on-demand. The entity is then updated to match the new event parameters before it is saved back to the store using `gravatar.save()`.
+
+### Recommended IDs for Creating New Entities
+
+It is highly recommended to use `Bytes` as the type for `id` fields, and only use `String` for attributes that truly contain human-readable text, like the name of a token. Below are some recommended `id` values to consider when creating new entities.
+
+- `transfer.id = event.transaction.hash`
+
+- `let id = event.transaction.hash.concatI32(event.logIndex.toI32())`
+
+- For entities that store aggregated data, for e.g, daily trade volumes, the `id` usually contains the day number. Here, using a `Bytes` as the `id` is beneficial. Determining the `id` would look like
+
+```typescript
+let dayID = event.block.timestamp.toI32() / 86400
+let id = Bytes.fromI32(dayID)
+```
+
+- Convert constant addresses to `Bytes`.
+
+`const id = Bytes.fromHexString('0xdead...beef')`
+
+There is a [Graph Typescript Library](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) which contains utilities for interacting with the Graph Node store and conveniences for handling smart contract data and entities. It can be imported into `mapping.ts` from `@graphprotocol/graph-ts`.
+
+### Handling of entities with identical IDs
+
+When creating and saving a new entity, if an entity with the same ID already exists, the properties of the new entity are always preferred during the merge process. This means that the existing entity will be updated with the values from the new entity.
+
+If a null value is intentionally set for a field in the new entity with the same ID, the existing entity will be updated with the null value.
+
+If no value is set for a field in the new entity with the same ID, the field will result in null as well.
+
+## Code Generation
+
+In order to make it easy and type-safe to work with smart contracts, events and entities, the Graph CLI can generate AssemblyScript types from the subgraph's GraphQL schema and the contract ABIs included in the data sources.
+
+This is done with
+
+```sh
+graph codegen [--output-dir <OUTPUT_DIR>] [<MANIFEST>]
+```
+
+but in most cases, subgraphs are already preconfigured via `package.json` to allow you to simply run one of the following to achieve the same:
+
+```sh
+# Yarn
+yarn codegen
+
+# NPM
+npm run codegen
+```
+
+This will generate an AssemblyScript class for every smart contract in the ABI files mentioned in `subgraph.yaml`, allowing you to bind these contracts to specific addresses in the mappings and call read-only contract methods against the block being processed. It will also generate a class for every contract event to provide easy access to event parameters, as well as the block and transaction the event originated from. All of these types are written to `<OUTPUT_DIR>/<DATA_SOURCE_NAME>/<ABI_NAME>.ts`. In the example subgraph, this would be `generated/Gravity/Gravity.ts`, allowing mappings to import these types with.
+
+```javascript
+import {
+  // The contract class:
+  Gravity,
+  // The events classes:
+  NewGravatar,
+  UpdatedGravatar,
+} from '../generated/Gravity/Gravity'
+```
+
+In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
+
+```javascript
+import { Gravatar } from '../generated/schema'
+```
+
+> **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
+
+Code generation does not check your mapping code in `src/mapping.ts`. If you want to check that before trying to deploy your subgraph to Graph Explorer, you can run `yarn build` and fix any syntax errors that the TypeScript compiler might find.

From c45ef860a9408a08e147ffcd35d2212a63f7ca89 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:32 -0500
Subject: [PATCH 0397/1325] New translations install-the-cli.mdx (Swahili)

---
 .../creating-a-subgraph/install-the-cli.mdx   | 119 ++++++++++++++++++
 1 file changed, 119 insertions(+)
 create mode 100644 website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx

diff --git a/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx
new file mode 100644
index 000000000000..5897ae02b134
--- /dev/null
+++ b/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx
@@ -0,0 +1,119 @@
+---
+title: Install the Graph CLI
+---
+
+> In order to use your subgraph on The Graph's decentralized network, you will need to [create an API key](/deploying/subgraph-studio-faqs/#2-how-do-i-create-an-api-key) in [Subgraph Studio](https://thegraph.com/studio/apikeys/). It is recommended that you add signal to your subgraph with at least 3,000 GRT to attract 2-3 Indexers. To learn more about signaling, check out [curating](/network/curating/).
+
+## Overview
+
+The [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a command-line interface that facilitates developers' commands for The Graph. It processes a [subgraph manifest](/creating-a-subgraph/subgraph-manifest/) and compiles the [mappings](/creating-a-subgraph/assemblyscript-mappings/) to create the files you will need to deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) and the network.
+
+## Getting Started
+
+### Install the Graph CLI
+
+The Graph CLI is written in TypeScript, and you must have `node` and either `npm` or `yarn` installed to use it. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+On your local machine, run one of the following commands:
+
+#### Using [npm](https://www.npmjs.com/)
+
+```bash
+npm install -g @graphprotocol/graph-cli@latest
+```
+
+#### Using [yarn](https://yarnpkg.com/)
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+The `graph init` command can be used to set up a new subgraph project, either from an existing contract or from an example subgraph. If you already have a smart contract deployed to your preferred network, you can bootstrap a new subgraph from that contract to get started.
+
+## Create a Subgraph
+
+### From an Existing Contract
+
+The following command creates a subgraph that indexes all events of an existing contract:
+
+```sh
+graph init \
+  --product subgraph-studio
+  --from-contract <CONTRACT_ADDRESS> \
+  [--network <ETHEREUM_NETWORK>] \
+  [--abi <FILE>] \
+  <SUBGRAPH_SLUG> [<DIRECTORY>]
+```
+
+- The command tries to retrieve the contract ABI from Etherscan.
+
+  - The Graph CLI relies on a public RPC endpoint. While occasional failures are expected, retries typically resolve this issue. If failures persist, consider using a local ABI.
+
+- If any of the optional arguments are missing, it guides you through an interactive form.
+
+- The `<SUBGRAPH_SLUG>` is the ID of your subgraph in [Subgraph Studio](https://thegraph.com/studio/). It can be found on your subgraph details page.
+
+### From an Example Subgraph
+
+The following command initializes a new project from an example subgraph:
+
+```sh
+graph init <SUBGRAPH_SLUG> --from-example=example-subgraph
+```
+
+- The [example subgraph](https://github.com/graphprotocol/example-subgraph) is based on the Gravity contract by Dani Grant, which manages user avatars and emits `NewGravatar` or `UpdateGravatar` events whenever avatars are created or updated.
+
+- The subgraph handles these events by writing `Gravatar` entities to the Graph Node store and ensuring these are updated according to the events.
+
+### Add New `dataSources` to an Existing Subgraph
+
+`dataSources` are key components of subgraphs. They define the sources of data that the subgraph indexes and processes. A `dataSource` specifies which smart contract to listen to, which events to process, and how to handle them.
+
+Recent versions of the Graph CLI supports adding new `dataSources` to an existing subgraph through the `graph add` command:
+
+```sh
+graph add <address> [<subgraph-manifest default: "./subgraph.yaml">]
+
+Options:
+
+      --abi <path>              Path to the contract ABI (default: download from Etherscan)
+      --contract-name           Name of the contract (default: Contract)
+      --merge-entities          Whether to merge entities with the same name (default: false)
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+#### Specifics
+
+The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is specified with the `--abi` option) and creates a new `dataSource`, similar to how the `graph init` command creates a `dataSource` `--from-contract`, updating the schema and mappings accordingly. This allows you to index implementation contracts from their proxy contracts.
+
+- The `--merge-entities` option identifies how the developer would like to handle `entity` and `event` name conflicts:
+
+  - If `true`: the new `dataSource` should use existing `eventHandlers` & `entities`.
+
+  - If `false`: a new `entity` & `event` handler should be created with `${dataSourceName}{EventName}`.
+
+- The contract `address` will be written to the `networks.json` for the relevant network.
+
+> Note: When using the interactive CLI, after successfully running `graph init`, you'll be prompted to add a new `dataSource`.
+
+### Getting The ABIs
+
+The ABI file(s) must match your contract(s). There are a few ways to obtain ABI files:
+
+- If you are building your own project, you will likely have access to your most current ABIs.
+- If you are building a subgraph for a public project, you can download that project to your computer and get the ABI by using [`npx hardhat compile`](https://hardhat.org/hardhat-runner/docs/guides/compile-contracts#compiling-your-contracts) or using `solc` to compile.
+- You can also find the ABI on [Etherscan](https://etherscan.io/), but this isn't always reliable, as the ABI that is uploaded there may be out of date. Make sure you have the right ABI, otherwise running your subgraph will fail.
+
+## SpecVersion Releases
+
+| Version | Release notes                                                                                                                                                            |
+| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
+|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
+|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
+|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
+|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
+|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
+|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
+|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |

From 227c7d6831f1f73b6688e5e80b39731a82402503 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:33 -0500
Subject: [PATCH 0398/1325] New translations ql-schema.mdx (Swahili)

---
 .../creating-a-subgraph/ql-schema.mdx         | 312 ++++++++++++++++++
 1 file changed, 312 insertions(+)
 create mode 100644 website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx

diff --git a/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx
new file mode 100644
index 000000000000..3df39853f82b
--- /dev/null
+++ b/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx
@@ -0,0 +1,312 @@
+---
+title: The Graph QL Schema
+---
+
+## Overview
+
+The schema for your subgraph is in the file `schema.graphql`. GraphQL schemas are defined using the GraphQL interface definition language.
+
+> Note: If you've never written a GraphQL schema, it is recommended that you check out this primer on the GraphQL type system. Reference documentation for GraphQL schemas can be found in the [GraphQL API](/querying/graphql-api/) section.
+
+### Defining Entities
+
+Before defining entities, it is important to take a step back and think about how your data is structured and linked.
+
+- All queries will be made against the data model defined in the subgraph schema. As a result, the design of the subgraph schema should be informed by the queries that your application will need to perform.
+- It may be useful to imagine entities as "objects containing data", rather than as events or functions.
+- You define entity types in `schema.graphql`, and Graph Node will generate top-level fields for querying single instances and collections of that entity type.
+- Each type that should be an entity is required to be annotated with an `@entity` directive.
+- By default, entities are mutable, meaning that mappings can load existing entities, modify them and store a new version of that entity.
+  - Mutability comes at a price, so for entity types that will never be modified, such as those containing data extracted verbatim from the chain, it is recommended to mark them as immutable with `@entity(immutable: true)`.
+  - If changes happen in the same block in which the entity was created, then mappings can make changes to immutable entities. Immutable entities are much faster to write and to query so they should be used whenever possible.
+
+#### Good Example
+
+The following `Gravatar` entity is structured around a Gravatar object and is a good example of how an entity could be defined.
+
+```graphql
+type Gravatar @entity(immutable: true) {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+  accepted: Boolean
+}
+```
+
+#### Bad Example
+
+The following example `GravatarAccepted` and `GravatarDeclined` entities are based around events. It is not recommended to map events or function calls to entities 1:1.
+
+```graphql
+type GravatarAccepted @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+
+type GravatarDeclined @entity {
+  id: Bytes!
+  owner: Bytes
+  displayName: String
+  imageUrl: String
+}
+```
+
+#### Optional and Required Fields
+
+Entity fields can be defined as required or optional. Required fields are indicated by the `!` in the schema. If the field is a scalar field, you get an error when you try to store the entity. If the field references another entity then you get this error:
+
+```
+Null value resolved for non-null field 'name'
+```
+
+Each entity must have an `id` field, which must be of type `Bytes!` or `String!`. It is generally recommended to use `Bytes!`, unless the `id` contains human-readable text, since entities with `Bytes!` id's will be faster to write and query as those with a `String!` `id`. The `id` field serves as the primary key, and needs to be unique among all entities of the same type. For historical reasons, the type `ID!` is also accepted and is a synonym for `String!`.
+
+For some entity types the `id` for `Bytes!` is constructed from the id's of two other entities; that is possible using `concat`, e.g., `let id = left.id.concat(right.id) ` to form the id from the id's of `left` and `right`. Similarly, to construct an id from the id of an existing entity and a counter `count`, `let id = left.id.concatI32(count)` can be used. The concatenation is guaranteed to produce unique id's as long as the length of `left` is the same for all such entities, for example, because `left.id` is an `Address`.
+
+### Built-In Scalar Types
+
+#### GraphQL Supported Scalars
+
+The following scalars are supported in the GraphQL API:
+
+| Type         | Description                                                                                                                                                                                                      |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
+| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
+| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
+| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
+| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
+| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+
+### Enums
+
+You can also create enums within a schema. Enums have the following syntax:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+Once the enum is defined in the schema, you can use the string representation of the enum value to set an enum field on an entity. For example, you can set the `tokenStatus` to `SecondOwner` by first defining your entity and subsequently setting the field with `entity.tokenStatus = "SecondOwner"`. The example below demonstrates what the Token entity would look like with an enum field:
+
+More detail on writing enums can be found in the [GraphQL documentation](https://graphql.org/learn/schema/).
+
+### Entity Relationships
+
+An entity may have a relationship to one or more other entities in your schema. These relationships may be traversed in your queries. Relationships in The Graph are unidirectional. It is possible to simulate bidirectional relationships by defining a unidirectional relationship on either "end" of the relationship.
+
+Relationships are defined on entities just like any other field except that the type specified is that of another entity.
+
+#### One-To-One Relationships
+
+Define a `Transaction` entity type with an optional one-to-one relationship with a `TransactionReceipt` entity type:
+
+```graphql
+type Transaction @entity(immutable: true) {
+  id: Bytes!
+  transactionReceipt: TransactionReceipt
+}
+
+type TransactionReceipt @entity(immutable: true) {
+  id: Bytes!
+  transaction: Transaction
+}
+```
+
+#### One-To-Many Relationships
+
+Define a `TokenBalance` entity type with a required one-to-many relationship with a Token entity type:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+### Reverse Lookups
+
+Reverse lookups can be defined on an entity through the `@derivedFrom` field. This creates a virtual field on the entity that may be queried but cannot be set manually through the mappings API. Rather, it is derived from the relationship defined on the other entity. For such relationships, it rarely makes sense to store both sides of the relationship, and both indexing and query performance will be better when only one side is stored and the other is derived.
+
+For one-to-many relationships, the relationship should always be stored on the 'one' side, and the 'many' side should always be derived. Storing the relationship this way, rather than storing an array of entities on the 'many' side, will result in dramatically better performance for both indexing and querying the subgraph. In general, storing arrays of entities should be avoided as much as is practical.
+
+#### Example
+
+We can make the balances for a token accessible from the token by deriving a `tokenBalances` field:
+
+```graphql
+type Token @entity(immutable: true) {
+  id: Bytes!
+  tokenBalances: [TokenBalance!]! @derivedFrom(field: "token")
+}
+
+type TokenBalance @entity {
+  id: Bytes!
+  amount: Int!
+  token: Token!
+}
+```
+
+#### Many-To-Many Relationships
+
+For many-to-many relationships, such as users that each may belong to any number of organizations, the most straightforward, but generally not the most performant, way to model the relationship is as an array in each of the two entities involved. If the relationship is symmetric, only one side of the relationship needs to be stored and the other side can be derived.
+
+#### Example
+
+Define a reverse lookup from a `User` entity type to an `Organization` entity type. In the example below, this is achieved by looking up the `members` attribute from within the `Organization` entity. In queries, the `organizations` field on `User` will be resolved by finding all `Organization` entities that include the user's ID.
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [User!]!
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [Organization!]! @derivedFrom(field: "members")
+}
+```
+
+A more performant way to store this relationship is through a mapping table that has one entry for each `User` / `Organization` pair with a schema like
+
+```graphql
+type Organization @entity {
+  id: Bytes!
+  name: String!
+  members: [UserOrganization!]! @derivedFrom(field: "organization")
+}
+
+type User @entity {
+  id: Bytes!
+  name: String!
+  organizations: [UserOrganization!] @derivedFrom(field: "user")
+}
+
+type UserOrganization @entity {
+  id: Bytes! # Set to `user.id.concat(organization.id)`
+  user: User!
+  organization: Organization!
+}
+```
+
+This approach requires that queries descend into one additional level to retrieve, for example, the organizations for users:
+
+```graphql
+query usersWithOrganizations {
+  users {
+    organizations {
+      # this is a UserOrganization entity
+      organization {
+        name
+      }
+    }
+  }
+}
+```
+
+This more elaborate way of storing many-to-many relationships will result in less data stored for the subgraph, and therefore to a subgraph that is often dramatically faster to index and to query.
+
+### Adding comments to the schema
+
+As per GraphQL spec, comments can be added above schema entity attributes using the hash symbol `#`. This is illustrated in the example below:
+
+```graphql
+type MyFirstEntity @entity {
+  # unique identifier and primary key of the entity
+  id: Bytes!
+  address: Bytes!
+}
+```
+
+## Defining Fulltext Search Fields
+
+Fulltext search queries filter and rank entities based on a text search input. Fulltext queries are able to return matches for similar words by processing the query text input into stems before comparing them to the indexed text data.
+
+A fulltext query definition includes the query name, the language dictionary used to process the text fields, the ranking algorithm used to order the results, and the fields included in the search. Each fulltext query may span multiple fields, but all included fields must be from a single entity type.
+
+To add a fulltext query, include a `_Schema_` type with a fulltext directive in the GraphQL schema.
+
+```graphql
+type _Schema_
+  @fulltext(
+    name: "bandSearch"
+    language: en
+    algorithm: rank
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
+  )
+
+type Band @entity {
+  id: Bytes!
+  name: String!
+  description: String!
+  bio: String
+  wallet: Address
+  labels: [Label!]!
+  discography: [Album!]!
+  members: [Musician!]!
+}
+```
+
+The example `bandSearch` field can be used in queries to filter `Band` entities based on the text documents in the `name`, `description`, and `bio` fields. Jump to [GraphQL API - Queries](/querying/graphql-api#queries) for a description of the fulltext search API and more example usage.
+
+```graphql
+query {
+  bandSearch(text: "breaks & electro & detroit") {
+    id
+    name
+    description
+    wallet
+  }
+}
+```
+
+> **[Feature Management](#experimental-features):** From `specVersion` `0.0.4` and onwards, `fullTextSearch` must be declared under the `features` section in the subgraph manifest.
+
+## Languages supported
+
+Choosing a different language will have a definitive, though sometimes subtle, effect on the fulltext search API. Fields covered by a fulltext query field are examined in the context of the chosen language, so the lexemes produced by analysis and search queries vary from language to language. For example: when using the supported Turkish dictionary "token" is stemmed to "toke" while, of course, the English dictionary will stem it to "token".
+
+Supported language dictionaries:
+
+| Code   | Dictionary |
+| ------ | ---------- |
+| simple | General    |
+| da     | Danish     |
+| nl     | Dutch      |
+| en     | English    |
+| fi     | Finnish    |
+| fr     | French     |
+| de     | German     |
+| hu     | Hungarian  |
+| it     | Italian    |
+| no     | Norwegian  |
+| pt     | Portuguese |
+| ro     | Romanian   |
+| ru     | Russian    |
+| es     | Spanish    |
+| sv     | Swedish    |
+| tr     | Turkish    |
+
+### Ranking Algorithms
+
+Supported algorithms for ordering results:
+
+| Algorithm     | Description                                                             |
+| ------------- | ----------------------------------------------------------------------- |
+| rank          | Use the match quality (0-1) of the fulltext query to order the results. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.         |

From 87aad92f22a8e0110d1f9248bfb3825bac30fa97 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:34 -0500
Subject: [PATCH 0399/1325] New translations subgraph-manifest.mdx (Swahili)

---
 .../creating-a-subgraph/subgraph-manifest.mdx | 534 ++++++++++++++++++
 1 file changed, 534 insertions(+)
 create mode 100644 website/pages/sw/developing/creating-a-subgraph/subgraph-manifest.mdx

diff --git a/website/pages/sw/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/sw/developing/creating-a-subgraph/subgraph-manifest.mdx
new file mode 100644
index 000000000000..f282f3946e75
--- /dev/null
+++ b/website/pages/sw/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -0,0 +1,534 @@
+---
+title: Subgraph Manifest
+---
+
+## Overview
+
+The subgraph manifest, `subgraph.yaml`, defines the smart contracts & network your subgraph will index, the events from these contracts to pay attention to, and how to map event data to entities that Graph Node stores and allows to query.
+
+The **subgraph definition** consists of the following files:
+
+- `subgraph.yaml`: Contains the subgraph manifest
+
+- `schema.graphql`: A GraphQL schema defining the data stored for your subgraph and how to query it via GraphQL
+
+- `mapping.ts`: [AssemblyScript Mappings](https://github.com/AssemblyScript/assemblyscript) code that translates event data into entities defined in your schema (e.g. `mapping.ts` in this guide)
+
+### Subgraph Capabilities
+
+A single subgraph can:
+
+- Index data from multiple smart contracts (but not multiple networks).
+
+- Index data from IPFS files using File Data Sources.
+
+- Add an entry for each contract that requires indexing to the `dataSources` array.
+
+The full specification for subgraph manifests can be found [here](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md).
+
+For the example subgraph listed above, `subgraph.yaml` is:
+
+```yaml
+specVersion: 0.0.4
+description: Gravatar for Ethereum
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      abi: Gravity
+      startBlock: 6175244
+      endBlock: 7175245
+    context:
+      foo:
+        type: Bool
+        data: true
+      bar:
+        type: String
+        data: 'bar'
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: NewGravatar(uint256,address,string,string)
+          handler: handleNewGravatar
+        - event: UpdatedGravatar(uint256,address,string,string)
+          handler: handleUpdatedGravatar
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCall
+          filter:
+            kind: call
+      file: ./src/mapping.ts
+```
+
+## Subgraph Entries
+
+> Important Note: Be sure you populate your subgraph manifest with all handlers and [entities](/developing/creating-a-subgraph/ql-schema/).
+
+The important entries to update for the manifest are:
+
+- `specVersion`: a semver version that identifies the supported manifest structure and functionality for the subgraph. The latest version is `1.2.0`. See [specVersion releases](#specversion-releases) section to see more details on features & releases.
+
+- `description`: a human-readable description of what the subgraph is. This description is displayed in Graph Explorer when the subgraph is deployed to Subgraph Studio.
+
+- `repository`: the URL of the repository where the subgraph manifest can be found. This is also displayed in Graph Explorer.
+
+- `features`: a list of all used [feature](#experimental-features) names.
+
+- `indexerHints.prune`: Defines the retention of historical block data for a subgraph. See [prune](#prune) in [indexerHints](#indexer-hints) section.
+
+- `dataSources.source`: the address of the smart contract the subgraph sources, and the ABI of the smart contract to use. The address is optional; omitting it allows to index matching events from all contracts.
+
+- `dataSources.source.startBlock`: the optional number of the block that the data source starts indexing from. In most cases, we suggest using the block in which the contract was created.
+
+- `dataSources.source.endBlock`: The optional number of the block that the data source stops indexing at, including that block. Minimum spec version required: `0.0.9`.
+
+- `dataSources.context`: key-value pairs that can be used within subgraph mappings. Supports various data types like `Bool`, `String`, `Int`, `Int8`, `BigDecimal`, `Bytes`, `List`, and `BigInt`. Each variable needs to specify its `type` and `data`. These context variables are then accessible in the mapping files, offering more configurable options for subgraph development.
+
+- `dataSources.mapping.entities`: the entities that the data source writes to the store. The schema for each entity is defined in the schema.graphql file.
+
+- `dataSources.mapping.abis`: one or more named ABI files for the source contract as well as any other smart contracts that you interact with from within the mappings.
+
+- `dataSources.mapping.eventHandlers`: lists the smart contract events this subgraph reacts to and the handlers in the mapping—./src/mapping.ts in the example—that transform these events into entities in the store.
+
+- `dataSources.mapping.callHandlers`: lists the smart contract functions this subgraph reacts to and handlers in the mapping that transform the inputs and outputs to function calls into entities in the store.
+
+- `dataSources.mapping.blockHandlers`: lists the blocks this subgraph reacts to and handlers in the mapping to run when a block is appended to the chain. Without a filter, the block handler will be run every block. An optional call-filter can be provided by adding a `filter` field with `kind: call` to the handler. This will only run the handler if the block contains at least one call to the data source contract.
+
+A single subgraph can index data from multiple smart contracts. Add an entry for each contract from which data needs to be indexed to the `dataSources` array.
+
+## Event Handlers
+
+Event handlers in a subgraph react to specific events emitted by smart contracts on the blockchain and trigger handlers defined in the subgraph's manifest. This enables subgraphs to process and store event data according to defined logic.
+
+### Defining an Event Handler
+
+An event handler is declared within a data source in the subgraph's YAML configuration. It specifies which events to listen for and the corresponding function to execute when those events are detected.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      eventHandlers:
+        - event: Approval(address,address,uint256)
+          handler: handleApproval
+        - event: Transfer(address,address,uint256)
+          handler: handleTransfer
+          topic1: ['0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045', '0xc8dA6BF26964aF9D7eEd9e03E53415D37aA96325'] # Optional topic filter which filters only events with the specified topic.
+```
+
+## Call Handlers
+
+While events provide an effective way to collect relevant changes to the state of a contract, many contracts avoid generating logs to optimize gas costs. In these cases, a subgraph can subscribe to calls made to the data source contract. This is achieved by defining call handlers referencing the function signature and the mapping handler that will process calls to this function. To process these calls, the mapping handler will receive an `ethereum.Call` as an argument with the typed inputs to and outputs from the call. Calls made at any depth in a transaction's call chain will trigger the mapping, allowing activity with the data source contract through proxy contracts to be captured.
+
+Call handlers will only trigger in one of two cases: when the function specified is called by an account other than the contract itself or when it is marked as external in Solidity and called as part of another function in the same contract.
+
+> **Note:** Call handlers currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more call handlers, it will not start syncing. Subgraph developers should instead use event handlers. These are far more performant than call handlers, and are supported on every evm network.
+
+### Defining a Call Handler
+
+To define a call handler in your manifest, simply add a `callHandlers` array under the data source you would like to subscribe to.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      callHandlers:
+        - function: createGravatar(string,string)
+          handler: handleCreateGravatar
+```
+
+The `function` is the normalized function signature to filter calls by. The `handler` property is the name of the function in your mapping you would like to execute when the target function is called in the data source contract.
+
+### Mapping Function
+
+Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
+
+```typescript
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
+
+export function handleCreateGravatar(call: CreateGravatarCall): void {
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
+}
+```
+
+The `handleCreateGravatar` function takes a new `CreateGravatarCall` which is a subclass of `ethereum.Call`, provided by `@graphprotocol/graph-ts`, that includes the typed inputs and outputs of the call. The `CreateGravatarCall` type is generated for you when you run `graph codegen`.
+
+## Block Handlers
+
+In addition to subscribing to contract events or function calls, a subgraph may want to update its data as new blocks are appended to the chain. To achieve this a subgraph can run a function after every block or after blocks that match a pre-defined filter.
+
+### Supported Filters
+
+#### Call Filter
+
+```yaml
+filter:
+  kind: call
+```
+
+_The defined handler will be called once for every block which contains a call to the contract (data source) the handler is defined under._
+
+> **Note:** The `call` filter currently depend on the Parity tracing API. Certain networks, such as BNB chain and Arbitrum, does not support this API. If a subgraph indexing one of these networks contain one or more block handlers with a `call` filter, it will not start syncing.
+
+The absence of a filter for a block handler will ensure that the handler is called every block. A data source can only contain one block handler for each filter type.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: dev
+    source:
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Gravatar
+        - Transaction
+      abis:
+        - name: Gravity
+          file: ./abis/Gravity.json
+      blockHandlers:
+        - handler: handleBlock
+        - handler: handleBlockWithCallToContract
+          filter:
+            kind: call
+```
+
+#### Polling Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Polling filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleBlock
+    filter:
+      kind: polling
+      every: 10
+```
+
+The defined handler will be called once for every `n` blocks, where `n` is the value provided in the `every` field. This configuration allows the subgraph to perform specific operations at regular block intervals.
+
+#### Once Filter
+
+> **Requires `specVersion` >= 0.0.8**
+>
+> **Note:** Once filters are only available on dataSources of `kind: ethereum`.
+
+```yaml
+blockHandlers:
+  - handler: handleOnce
+    filter:
+      kind: once
+```
+
+The defined handler with the once filter will be called only once before all other handlers run. This configuration allows the subgraph to use the handler as an initialization handler, performing specific tasks at the start of indexing.
+
+```ts
+export function handleOnce(block: ethereum.Block): void {
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
+}
+```
+
+### Mapping Function
+
+The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
+
+```typescript
+import { ethereum } from '@graphprotocol/graph-ts'
+
+export function handleBlock(block: ethereum.Block): void {
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
+}
+```
+
+## Anonymous Events
+
+If you need to process anonymous events in Solidity, that can be achieved by providing the topic 0 of the event, as in the example:
+
+```yaml
+eventHandlers:
+  - event: LogNote(bytes4,address,bytes32,bytes32,uint256,bytes)
+    topic0: '0x644843f351d3fba4abcd60109eaff9f54bac8fb8ccf0bab941009c21df21cf31'
+    handler: handleGive
+```
+
+An event will only be triggered when both the signature and topic 0 match. By default, `topic0` is equal to the hash of the event signature.
+
+## Transaction Receipts in Event Handlers
+
+Starting from `specVersion` `0.0.5` and `apiVersion` `0.0.7`, event handlers can have access to the receipt for the transaction which emitted them.
+
+To do so, event handlers must be declared in the subgraph manifest with the new `receipt: true` key, which is optional and defaults to false.
+
+```yaml
+eventHandlers:
+  - event: NewGravatar(uint256,address,string,string)
+    handler: handleNewGravatar
+    receipt: true
+```
+
+Inside the handler function, the receipt can be accessed in the `Event.receipt` field. When the `receipt` key is set to `false` or omitted in the manifest, a `null` value will be returned instead.
+
+## Order of Triggering Handlers
+
+The triggers for a data source within a block are ordered using the following process:
+
+1. Event and call triggers are first ordered by transaction index within the block.
+2. Event and call triggers within the same transaction are ordered using a convention: event triggers first then call triggers, each type respecting the order they are defined in the manifest.
+3. Block triggers are run after event and call triggers, in the order they are defined in the manifest.
+
+These ordering rules are subject to change.
+
+> **Note:** When new [dynamic data source](#data-source-templates-for-dynamically-created-contracts) are created, the handlers defined for dynamic data sources will only start processing after all existing data source handlers are processed, and will repeat in the same sequence whenever triggered.
+
+## Data Source Templates
+
+A common pattern in EVM-compatible smart contracts is the use of registry or factory contracts, where one contract creates, manages, or references an arbitrary number of other contracts that each have their own state and events.
+
+The addresses of these sub-contracts may or may not be known upfront and many of these contracts may be created and/or added over time. This is why, in such cases, defining a single data source or a fixed number of data sources is impossible and a more dynamic approach is needed: _data source templates_.
+
+### Data Source for the Main Contract
+
+First, you define a regular data source for the main contract. The snippet below shows a simplified example data source for the [Uniswap](https://uniswap.org) exchange factory contract. Note the `NewExchange(address,address)` event handler. This is emitted when a new exchange contract is created on-chain by the factory contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: Factory
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - Directory
+      abis:
+        - name: Factory
+          file: ./abis/factory.json
+      eventHandlers:
+        - event: NewExchange(address,address)
+          handler: handleNewExchange
+```
+
+### Data Source Templates for Dynamically Created Contracts
+
+Then, you add _data source templates_ to the manifest. These are identical to regular data sources, except that they lack a pre-defined contract address under `source`. Typically, you would define one template for each type of sub-contract managed or referenced by the parent contract.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: Factory
+    # ... other source fields for the main contract ...
+templates:
+  - name: Exchange
+    kind: ethereum/contract
+    network: mainnet
+    source:
+      abi: Exchange
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/exchange.ts
+      entities:
+        - Exchange
+      abis:
+        - name: Exchange
+          file: ./abis/exchange.json
+      eventHandlers:
+        - event: TokenPurchase(address,uint256,uint256)
+          handler: handleTokenPurchase
+        - event: EthPurchase(address,uint256,uint256)
+          handler: handleEthPurchase
+        - event: AddLiquidity(address,uint256,uint256)
+          handler: handleAddLiquidity
+        - event: RemoveLiquidity(address,uint256,uint256)
+          handler: handleRemoveLiquidity
+```
+
+### Instantiating a Data Source Template
+
+In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  // Start indexing the exchange; `event.params.exchange` is the
+  // address of the new exchange contract
+  Exchange.create(event.params.exchange)
+}
+```
+
+> **Note:** A new data source will only process the calls and events for the block in which it was created and all following blocks, but will not process historical data, i.e., data that is contained in prior blocks.
+>
+> If prior blocks contain data relevant to the new data source, it is best to index that data by reading the current state of the contract and creating entities representing that state at the time the new data source is created.
+
+### Data Source Context
+
+Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
+
+```typescript
+import { Exchange } from '../generated/templates'
+
+export function handleNewExchange(event: NewExchange): void {
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
+}
+```
+
+Inside a mapping of the `Exchange` template, the context can then be accessed:
+
+```typescript
+import { dataSource } from '@graphprotocol/graph-ts'
+
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
+```
+
+There are setters and getters like `setString` and `getString` for all value types.
+
+## Start Blocks
+
+The `startBlock` is an optional setting that allows you to define from which block in the chain the data source will start indexing. Setting the start block allows the data source to skip potentially millions of blocks that are irrelevant. Typically, a subgraph developer will set `startBlock` to the block in which the smart contract of the data source was created.
+
+```yaml
+dataSources:
+  - kind: ethereum/contract
+    name: ExampleSource
+    network: mainnet
+    source:
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
+      abi: ExampleContract
+      startBlock: 6627917
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      file: ./src/mappings/factory.ts
+      entities:
+        - User
+      abis:
+        - name: ExampleContract
+          file: ./abis/ExampleContract.json
+      eventHandlers:
+        - event: NewEvent(address,address)
+          handler: handleNewEvent
+```
+
+> **Note:** The contract creation block can be quickly looked up on Etherscan:
+>
+> 1. Search for the contract by entering its address in the search bar.
+> 2. Click on the creation transaction hash in the `Contract Creator` section.
+> 3. Load the transaction details page where you'll find the start block for that contract.
+
+## Indexer Hints
+
+The `indexerHints` setting in a subgraph's manifest provides directives for indexers on processing and managing a subgraph. It influences operational decisions across data handling, indexing strategies, and optimizations. Presently, it features the `prune` option for managing historical data retention or pruning.
+
+> This feature is available from `specVersion: 1.0.0`
+
+### Prune
+
+`indexerHints.prune`: Defines the retention of historical block data for a subgraph. Options include:
+
+1. `"never"`: No pruning of historical data; retains the entire history.
+2. `"auto"`: Retains the minimum necessary history as set by the indexer, optimizing query performance.
+3. A specific number: Sets a custom limit on the number of historical blocks to retain.
+
+```
+ indexerHints:
+  prune: auto
+```
+
+> The term "history" in this context of subgraphs is about storing data that reflects the old states of mutable entities.
+
+History as of a given block is required for:
+
+- [Time travel queries](/querying/graphql-api/#time-travel-queries), which enable querying the past states of these entities at specific blocks throughout the subgraph's history
+- Using the subgraph as a [graft base](/developing/creating-a-subgraph/#grafting-onto-existing-subgraphs) in another subgraph, at that block
+- Rewinding the subgraph back to that block
+
+If historical data as of the block has been pruned, the above capabilities will not be available.
+
+> Using `"auto"` is generally recommended as it maximizes query performance and is sufficient for most users who do not require access to extensive historical data.
+
+For subgraphs leveraging [time travel queries](/querying/graphql-api/#time-travel-queries), it's advisable to either set a specific number of blocks for historical data retention or use `prune: never` to keep all historical entity states. Below are examples of how to configure both options in your subgraph's settings:
+
+To retain a specific amount of historical data:
+
+```
+ indexerHints:
+  prune: 1000 # Replace 1000 with the desired number of blocks to retain
+```
+
+To preserve the complete history of entity states:
+
+```
+indexerHints:
+  prune: never
+```

From 361a61e39c9da5874b550260bc509c36f9125451 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:35 -0500
Subject: [PATCH 0400/1325] New translations introduction.mdx (Hindi)

---
 website/pages/hi/sps/introduction.mdx | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/hi/sps/introduction.mdx b/website/pages/hi/sps/introduction.mdx
index 3e50521589af..d2e1f0179d40 100644
--- a/website/pages/hi/sps/introduction.mdx
+++ b/website/pages/hi/sps/introduction.mdx
@@ -1,19 +1,19 @@
 ---
-title: Introduction to Substreams-powered Subgraphs
+title: Substreams-संचालित Subgraphs का परिचय
 ---
 
-By using a Substreams package (`.spkg`) as a data source, your subgraph gains access to a stream of pre-indexed blockchain data. This enables more efficient and scalable data handling, especially with large or complex blockchain networks.
+Substreams पैकेज (.spkg) का उपयोग करके, आपका subgraph पूर्व-सूचीबद्ध ब्लॉकचेन डेटा के एक स्ट्रीम तक पहुंच प्राप्त करता है। यह विशेष रूप से बड़े या जटिल ब्लॉकचेन नेटवर्क के साथ डेटा हैंडलिंग को अधिक कुशल और स्केलेबल बनाता है।
 
-There are two methods of enabling this technology:
+इस तकनीक को सक्षम करने के दो तरीके हैं:
 
-Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph.
+Using Substreams triggers(./triggers): किसी भी Substreams मॉड्यूल से उपभोग करें, Protobuf मॉडल को एक subgraph हैंडलर के माध्यम से आयात करके और सभी लॉजिक को एक subgraph में स्थानांतरित करें। यह विधि subgraph संस्थाओं को सीधे subgraph में बनाती है।
 
-Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities.
+Entity Changes (https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out) का उपयोग करके: Substreams में अधिक लॉजिक लिखने से, आप सीधे graph-node में मॉड्यूल का आउटपुट प्राप्त कर सकते हैं। graph-node में, आप Substreams डेटा का उपयोग करके अपने उपग्रह संस्थाएं बना सकते हैं।
 
-It is really a matter of where you put your logic, in the subgraph or the Substreams. Keep in mind that having more of your logic in Substreams benefits from a parallelized model, whereas triggers will be linearly consumed in graph-node.
+यह वास्तव में इस पर निर्भर करता है कि आप अपनी लॉजिक को कहाँ रखते हैं, subgraph या Substreams में। ध्यान रखें कि यदि आपकी लॉजिक अधिकतर Substreams में है, तो इससे एक पैरेललाइज़्ड मॉडल का लाभ मिलता है, जबकि ट्रिगर्स graph-node में लाइनर रूप से उपभोग किए जाएंगे।
 
-Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
+नीचे दिए गए लिंक पर जाएं How-To गाइड्स के लिए जो आपको कोड-जनरेशन टूलिंग का उपयोग करके अपना पहला एंड-टू-एंड प्रोजेक्ट तेजी से बनाने में मदद करेंगे:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 93fe8e99b18e330f2c24f37981004b4f12054e3b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:36 -0500
Subject: [PATCH 0401/1325] New translations cosmos.mdx (French)

---
 website/pages/fr/cookbook/cosmos.mdx | 48 ++++++++++++++--------------
 1 file changed, 24 insertions(+), 24 deletions(-)

diff --git a/website/pages/fr/cookbook/cosmos.mdx b/website/pages/fr/cookbook/cosmos.mdx
index 9d332f717043..d21938a729dd 100644
--- a/website/pages/fr/cookbook/cosmos.mdx
+++ b/website/pages/fr/cookbook/cosmos.mdx
@@ -48,30 +48,30 @@ La définition d'un subgraph comporte trois éléments clés :
 Le manifeste du subgraph (`subgraph.yaml`) identifie les sources de données du subgraph, les déclencheurs d'intérêt et les fonctions (`handlers`) qui doivent être exécutées en réponse à ces déclencheurs. Vous trouverez ci-dessous un exemple de manifeste de subgraph pour un subgraph Cosmos :
 
 ```yaml
-version spec: 0.0.5
-description: Exemple de subgraph Cosmos
+version spec : 0.0.5
+description : Exemple de subgraph Cosmos
 schéma:
-  fichier: ./schema.graphql # lien vers le fichier de schéma
+   fichier : ./schema.graphql # lien vers le fichier de schéma
 les sources de données:
-  - genre: cosmos
-    nom: CosmosHub
-    réseau: cosmoshub-4 # Cela changera pour chaque blockchain basée sur le cosmos. Dans ce cas, l’exemple utilise le mainnet Cosmos Hub.
-    source:
-      startBlock: 0 # Requis pour Cosmos, définissez-le sur 0 pour démarrer l'indexation à partir de la genèse de la chaîne
-    cartographie:
-      Version api: 0.0.7
-      langage: wasm/assemblyscript
-      gestionnaires de blocs:
-        - handler: handleNewBlock # le nom de la fonction dans le fichier de mappage
-      Gestionnaires d'événements:
-        - event: récompenses # le type d'événement qui sera géré
-          handler: handleReward # le nom de la fonction dans le fichier de mappage
-      Gestionnaires de transactions:
-        - handler: handleTransaction # le nom de la fonction dans le fichier de mappage
-      Gestionnaires de messages:
-        - message: /cosmos.staking.v1beta1.MsgDelegate # le type d'un message
-          handler: handleMsgDelegate # le nom de la fonction dans le fichier de mappage
-      fichier: ./src/mapping.ts # lien vers le fichier avec les mappages Assemblyscript
+   - genre : cosmos
+     nom : CosmosHub
+     réseau : cosmoshub-4 # Cela changera pour chaque blockchain basée sur le cosmos. Dans ce cas, l’exemple utilise le mainnet Cosmos Hub.
+     source:
+       startBlock : 0 # Requis pour Cosmos, définissez-le sur 0 pour démarrer l'indexation à partir de la genèse de la chaîne
+     cartographie :
+       Version api : 0.0.7
+       langage : wasm/assemblyscript
+       gestionnaires de blocs :
+         - handler: handleNewBlock # le nom de la fonction dans le fichier de mappage
+       Gestionnaires d'événements :
+         - event : récompenses # le type d'événement qui sera géré
+           handler: handleReward # le nom de la fonction dans le fichier de mappage
+       Gestionnaires de transactions :
+         - handler: handleTransaction # le nom de la fonction dans le fichier de mappage
+       Gestionnaires de messages :
+         - message : /cosmos.staking.v1beta1.MsgDelegate # le type d'un message
+           handler : handleMsgDelegate # le nom de la fonction dans le fichier de mappage
+       fichier : ./src/mapping.ts # lien vers le fichier avec les mappages Assemblyscript
 ```
 
 - Les subgraphs cosmos introduisent un nouveau `type` de source de données (`cosmos`).
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Les gestionnaires pour le traitement des événements sont écrits en [AssemblyScript](https://www.assemblyscript.org/).
 
-L'indexation Cosmos introduit des types de données spécifiques à Cosmos dans l'[API AssemblyScript](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ Une fois votre subgraph créé, vous pouvez le déployer en utilisant la command
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 017525f0039f5fc3f4fef3d05f3394517727b3cf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:37 -0500
Subject: [PATCH 0402/1325] New translations arweave.mdx (French)

---
 website/pages/fr/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/fr/cookbook/arweave.mdx b/website/pages/fr/cookbook/arweave.mdx
index d4ba304400b1..b65102acbee9 100644
--- a/website/pages/fr/cookbook/arweave.mdx
+++ b/website/pages/fr/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ La définition du schéma décrit la structure de la base de données de subgrap
 
 Les gestionnaires pour le traitement des événements sont écrits en [AssemblyScript](https://www.assemblyscript.org/).
 
-L'indexation Arweave introduit des types de données spécifiques à Arweave dans l'[API AssemblyScript](/developing/graph-ts/api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ L'écriture des mappages d'un subgraph Arweave est très similaire à l'écritur
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Interroger un subgraph d'Arweave

From 37e01504aadd3230ad4103d8d3d2188a2070537f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:39 -0500
Subject: [PATCH 0403/1325] New translations cosmos.mdx (Hindi)

---
 website/pages/hi/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/cookbook/cosmos.mdx b/website/pages/hi/cookbook/cosmos.mdx
index 334b290e5a11..b64bc7c1cd7b 100644
--- a/website/pages/hi/cookbook/cosmos.mdx
+++ b/website/pages/hi/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ $ graph build
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From d61415c928716b44c769759103c5a4cfb34c5b69 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:40 -0500
Subject: [PATCH 0404/1325] New translations arweave.mdx (Hindi)

---
 website/pages/hi/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/hi/cookbook/arweave.mdx b/website/pages/hi/cookbook/arweave.mdx
index abe929009a8d..21103e5aac2e 100644
--- a/website/pages/hi/cookbook/arweave.mdx
+++ b/website/pages/hi/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ dataSources:
 
 इवेंट्स को प्रोसेस करने के लिए हैंडलर्स [असेंबली स्क्रिप्ट](https://www.assemblyscript.org/) में लिखे गए हैं|
 
-आरवीव इंडेक्सिंग आरवीव-विशेष डाटा टाइप्स को [AssemblyScript API](/developing/graph-ts/api/) में लाती है|
+Arweave इंडेक्सिंग '[AssemblyScript API](/developing/graph-ts/api/)' में Arweave-विशिष्ट डेटा प्रकारों को पेश करती है।
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ class Transaction {
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## आरवीव सब-ग्राफ क्वेरी करना

From a9dd5390d83586a3f69feaabbbfff1be57843688 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:42 -0500
Subject: [PATCH 0405/1325] New translations explorer.mdx (Russian)

---
 website/pages/ru/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/ru/network/explorer.mdx b/website/pages/ru/network/explorer.mdx
index d88d1f8c4535..c85daa791ead 100644
--- a/website/pages/ru/network/explorer.mdx
+++ b/website/pages/ru/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Субграфы
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Изображение проводника 1](/img/Subgraphs-Explorer-Landing.png)
 
-Если Вы кликнете по субграфу, Вы сможете тестировать запросы в песочнице и использовать информацию о сети для принятия обоснованных решений. Вы также сможете отправить сигнал GRT на свой субграф или субграфы других участников, чтобы проинформировать индексаторов о его значимости и высоком качестве. Это очень важно, поскольку отправка сигнала на субграф стимулирует его индексацию, а это означает, что он появится в сети для последующего обслуживания запросов.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Изображение проводника 2](/img/Subgraph-Details.png)
 
-На отдельной странице каждого субграфа отображается несколько деталей. Это:
+On each subgraph’s dedicated page, you can do the following:
 
 - Сигнал/снятие сигнала на субграфах
 - Просмотр дополнительных сведений, таких как диаграммы, текущий идентификатор развертывания и другие метаданные
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## Участники
 
-На этой вкладке Вы получите возможность увидеть всех участников, принимающих участие в сетевой деятельности, таких как индексаторы, делегаторы и кураторы. Далее мы подробно рассмотрим, что каждая вкладка означает.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Индексаторы
 
 ![Изображение проводника 4](/img/Indexer-Pane.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.
 
-- Сокращение комиссии за запрос — процент скидки от платы за запрос, которую индексатор сохраняет при разделении с Делегаторами
-- Эффективное сокращение вознаграждения — сокращение вознаграждения за индексацию, применяемое к пулу делегирования. Если он отрицательный, это означает, что индексатор отдает часть своего вознаграждения. Если он положительный, это означает, что индексатор сохраняет часть своих вознаграждений
-- Оставшееся время восстановления — время, оставшееся до того, как Индексатор сможет изменить вышеуказанные параметры делегирования. Периоды восстановления устанавливаются Индексаторами при обновлении параметров делегирования
-- Собственность — это внесенная ставка индексатора, которая может быть уменьшена за злонамеренное или неправильное поведение
-- Делегирование — доля Делегаторов, которая может быть выделена Индексатором, но не может быть сокращена
-- Выделение — доля, которую Индексаторы активно распределяют между индексируемыми субграфами
-- Доступная емкость делегирования — объем делегированной доли, которую Индексаторы всё ещё могут получить, прежде чем они будут перераспределены
+**Специфические особенности**
+
+- 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.
 
-Индексаторы могут зарабатывать как комиссии за запросы, так и вознаграждения за индексацию. Фактически это происходит, когда участники сети делегируют GRT Индексатору. Это позволяет Индексаторам получать комиссионные и вознаграждения в зависимости от параметров самого Индексатора. Параметры индексации устанавливаются нажатием на правую сторону таблицы или переходом в профиль Индексатора и нажатием кнопки «Делегировать».
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Чтобы узнать больше о том, как стать индексатором, ознакомьтесь с [официальной документацией](/network/indexing) или [Руководством для Индексаторов The Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ### 2. Кураторы
 
-Кураторы анализируют субграфы, чтобы определить, какие из них имеют наивысшее качество. Найдя потенциально привлекательный субграф, Куратор может курировать его, отправляя сигнал на его кривую связывания. Таким образом, Кураторы сообщают Индексаторам, какие субграфы имеют высокое качество и должны быть проиндексированы.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Кураторы могут быть членами сообщества, потребителями данных или даже разработчиками субграфов, которые отправляют сигналы на свои собственные субграфы, депонируя токены GRT на кривую связывания. Депонируя GRT, Кураторы создают акции кураторства субграфа. В результате Кураторы имеют право получать часть комиссий за запросы, которые генерирует субграф, на который они отправили сигнал. Кривая связывания стимулирует Кураторов курировать источники данных наивысшего качества. Таблица Куратора в этом разделе позволит Вам увидеть:
+In the The Curator table listed below you can see:
 
 - Дату начала курирования
 - Количество GRT, которое было внесено
@@ -68,34 +92,36 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ![Изображение проводника 6](/img/Curation-Overview.png)
 
-Если Вы хотите получить больше информации о роли Куратора, Вы можете сделать это, перейдя по следующим ссылкам: [ Академия The Graph](https://thegraph.academy/curators/) или [ Официальная документация.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Делегаторы
 
-Делегаторы играют ключевую роль в обеспечении безопасности и децентрализации сети The Graph. Они участвуют в сети, делегируя (то есть "ставя") токены GRT одному или нескольким индексаторам. Без Делегаторов у Индексаторов меньше вероятности заработать значительные награды и комиссии. Поэтому Индексаторы стремятся привлечь Делегаторов, предлагая им часть наград за индексацию и комиссий за запросы, которые они зарабатывают.
+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.
 
-Делегаторы, в свою очередь, выбирают Индексаторов на основе ряда различных переменных, таких как прошлые результаты, ставки вознаграждения за индексирование и снижение стоимости оплаты за запросы. Репутация в сообществе также может сыграть важную роль в этом! Рекомендуется подключаться к выбранным индексаторам через [The Graph’s Discord](https://discord.gg/graphprotocol) или [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![Изображение проводника 7](/img/Delegation-Overview.png)
 
-Таблица «Делегаторы» позволит Вам увидеть активных Делегаторов сообщества, а также такие показатели, как:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Количество Индексаторов, к которым делегирует Делегатор
 - Первоначальная делегация Делегатора
 - Накопленные ими вознаграждения, которые они не вывели из протокола
 - Реализованные вознаграждения, которые они сняли с протокола
 - Общее количество GRT, которое у них имеется в настоящее время в протоколе
-- Дата их последней делегации
+- The date they last delegated
 
-Если Вы хотите узнать больше о том, как стать Делегатором, не ищите информацию дальше! Все, что Вам нужно сделать, это перейти к [официальной документации](/network/delegating) или в [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Сеть
 
-В разделе "Сеть" Вы увидите глобальные ключевые показатели эффективности, а также сможете переключиться на основу каждой эпохи и проанализировать метрики сети более детально. Эти данные дадут Вам представление о том, как сеть работает на протяжении определённого времени.
+In this section, you can see global KPIs and view 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.
 
 ### Обзор
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - Текущая общая доля сети
 - Доля распределяется между Индексаторами и их Делегаторами
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Параметры протокола, такие как вознаграждение за курирование, уровень инфляции и т. д
 - Награды и сборы текущей эпохи
 
-Несколько ключевых деталей, о которых стоит упомянуть:
+A few key details to note:
 
-- **Комиссии за запросы представляют собой сборы, генерируемые потребителями**, и их могут заявить (или не заявить) Индексаторы по истечении периода как минимум 7 эпох (см. ниже) после того, как их распределения по отношению к субграфам были закрыты и данные, которые они предоставили, были проверены потребителями.
-- **Вознаграждения за индексацию представляют собой количество вознаграждений, которые Индексаторы заявили за выпуск сети в течение эпохи.** Хотя объем выпуска протокола фиксирован, вознаграждения создаются только после того, как Индексаторы закрывают свои распределения по отношению к субграфам, которые они индексировали. Таким образом, количество вознаграждений в эпоху меняется (т. е. в течение некоторых эпох Индексаторы могли коллективно закрыть распределения, которые были открыты в течение многих дней).
+- **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).
 
 ![Изображение проводника 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ The overview section has all the current network metrics as well as some cumulat
   - Активная эпоха - это та, в которой Индексаторы в настоящее время выделяют ставки и собирают комиссионные за запросы
   - Эпохи урегулирования — это эпохи, в которых используются государственные каналы. Это означает, что Индексаторы могут столкнуться с сокращением своих GRT, если потребители откроют против них споры.
   - Эпохи распределения - это эпохи, в которых состояния каналов для эпох регулируются, и Индексаторы могут требовать скидки на комиссию за запросы.
-  - Завершенные эпохи — это эпохи, в которых Индексаторы не имеют скидок на комиссию за запросы, и поэтому они являются завершенными.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Изображение проводника 9](/img/Epoch-Stats.png)
 
 ## Ваш профиль пользователя
 
-Теперь, когда мы поговорили о статистике сети, давайте перейдем к Вашему личному профилю. Ваш личный профиль - это место, где Вы можете видеть свою сетевую активность, независимо от того, как Вы участвуете в сети. Ваш криптовалютный кошелек будет действовать как Ваш профиль пользователя, и с помощью пользовательской панели Вы сможете увидеть:
+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:
 
 ### Обзор профиля
 
-Здесь Вы можете увидеть любые текущие действия, которые Вы предприняли. Здесь Вы также можете найти информацию о своём профиле, описание и веб-сайт (если Вы его добавили).
+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).
 
 ![Изображение проводника 10](/img/Profile-Overview.png)
 
 ### Вкладка "Субграфы"
 
-Если Вы перейдете на вкладку "Субграфы", Вы увидите свои опубликованные субграфы. Здесь не будут отображаться субграфы, развернутые с помощью CLI в целях тестирования – субграфы появятся только после их публикации в децентрализованной сети.
+In the Subgraphs tab, you’ll see 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.
 
 ![Изображение проводника 11](/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.
 
 Этот раздел также будет содержать подробную информацию о Ваших чистых вознаграждениях Индексатора и чистой комиссии за запросы. Вы увидите следующие показатели:
 
@@ -158,7 +189,9 @@ The overview section has all the current network metrics as well as some cumulat
 
 ### Вкладка "Делегирование"
 
-Делегаторы важны для сети the Graph. Делегатор должен использовать свои знания, чтобы выбрать Индексатора, который обеспечит высокий доход от вознаграждений. Здесь Вы можете найти детали своих активных и прежних делегаций, а также метрики Индексаторов, которым Вы делегировали.
+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.
 
 В первой половине страницы Вы можете увидеть диаграмму делегирования, а также диаграмму только вознаграждений. Слева Вы можете увидеть ключевые показатели эффективности, которые отражают Ваши текущие показатели делегирования.
 

From 160214a1fb8f3b99140083a698a32c5b9fceced3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:43 -0500
Subject: [PATCH 0406/1325] New translations tokenomics.mdx (Romanian)

---
 website/pages/ro/tokenomics.mdx | 44 ++++++++++++++-------------------
 1 file changed, 18 insertions(+), 26 deletions(-)

diff --git a/website/pages/ro/tokenomics.mdx b/website/pages/ro/tokenomics.mdx
index 6fa9686eec71..e2e4c904000d 100644
--- a/website/pages/ro/tokenomics.mdx
+++ b/website/pages/ro/tokenomics.mdx
@@ -1,21 +1,21 @@
 ---
 title: Tokenomics of The Graph Network
-description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token works.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Overview
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Specifics
 
-It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
 ## The Roles of Network Participants
 
@@ -29,15 +29,15 @@ There are four primary network participants:
 
 4.  Indexers - Backbone of blockchain data
 
-Fishermen and Arbitrators are also integral to the network’s success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
@@ -45,9 +45,9 @@ If you're reading this, you're capable of becoming a Delegator right now by head
 
 ## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
@@ -75,25 +75,17 @@ Indexers are the backbone of The Graph. They operate independent hardware and so
 
 Indexers can earn GRT rewards in two ways:
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-2.  Indexing rewards: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs) verifying that they have indexed data accurately.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
 Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-In order to run an indexing node, Indexers must stake 100,000 GRT or more with the network. Indexers are incentivized to stake GRT in proportion to the amount of queries they serve.
-
-Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial stake), they will not be able to use the additional GRT from Delegators until they increase their stake in the network.
-
-The amount of rewards an Indexer receives can vary based on the initial stake, accepted delegation, quality of service, and many more factors. The following chart is publicly available data from an active Indexer on The Graph's decentralized network.
-
-### The Indexer stake & reward of allnodes-com.eth
-
-![Indexing stake and rewards](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-This data is from February 2021 to September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Please note, this will improve when the [Arbitrum migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) is complete, making gas costs a significantly lower burden for participating on the network.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
 ## Token Supply: Burning & Issuance
 

From 830c5f07a56c97557168046387a722950326b26a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:44 -0500
Subject: [PATCH 0407/1325] New translations tokenomics.mdx (French)

---
 website/pages/fr/tokenomics.mdx | 92 +++++++++++++++------------------
 1 file changed, 42 insertions(+), 50 deletions(-)

diff --git a/website/pages/fr/tokenomics.mdx b/website/pages/fr/tokenomics.mdx
index a504e03334ae..c7bafa41af3b 100644
--- a/website/pages/fr/tokenomics.mdx
+++ b/website/pages/fr/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Les tokenomiques du réseau The Graph
-description: Le réseau The Graph est encouragé par une puissante tokénomique. Voici comment fonctionne GRT, le jeton natif de l'utilitaire de travail du réseau The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Aperçu
 
-- Adresse du jeton GRT sur Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph est un protocole décentralisé qui facilite l'accès aux données de la blockchain.
+## Spécificités⁠
 
-Il s'agit d'un modèle similaire à celui du B2B2C, sauf qu'il est alimenté par un réseau décentralisé de participants. Les participants au réseau travaillent ensemble pour fournir des données aux utilisateurs finaux en échange de récompenses GRT. GRT est le jeton de travail utilitaire qui coordonne les fournisseurs de données et les consommateurs. Le GRT sert d'utilitaire pour coordonner les fournisseurs et les consommateurs de données au sein du réseau et incite les participants au protocole à organiser les données de manière efficace.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexe les données de la blockchain de la même manière que Google indexe le web. En fait, vous utilisez peut-être déjà The Graph sans vous en rendre compte. Si vous avez consulté le front-end d'une dapp qui obtient ses données à partir d'un subgraph, vous avez interrogé des données à partir d'un subgraph !
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph joue un rôle crucial en rendant les données blockchain plus accessibles et en permettant un marché pour leur échange.
+- Adresse du jeton GRT sur Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Les rôles des participants au réseau
+## The Roles of Network Participants
 
-Les participants au réseau sont au nombre de quatre :
+There are four primary network participants:
 
 1.  Délégateurs - Déléguer les GRT aux indexeurs & sécuriser le réseau
 
@@ -29,82 +29,74 @@ Les participants au réseau sont au nombre de quatre :
 
 4.  Indexeurs - épine dorsale des données de la blockchain
 
-Les pêcheurs et les arbitres font également partie intégrante du succès du réseau à travers d’autres contributions, soutenant le travail des autres principaux participants. Pour plus d'informations sur les rôles réseau, [lisez cet article](https://thegraph.com/blog/the-graph-grt-token-activitys/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Diagramme des tokenomics](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Délégués (gagnez passivement des GRT)
+## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Si vous lisez ceci, vous pouvez devenir délégant dès maintenant en vous rendant sur la [page des participants au réseau](https://thegraph.com/explorer/participants/indexers), et déléguer GRT à un indexeur de votre choix.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Conservateurs (gagnez du GRT)
+## Curators (Earn GRT)
 
-Les curateurs identifient les subgraphs de haute qualité et les "curent" (c'est-à-dire qu'ils signalent le GRT sur eux) pour gagner des parts de curation, qui garantissent un pourcentage de tous les frais de requête futurs générés par le subgraph. Bien que tout participant indépendant au réseau puisse être un curateur, les développeurs de subgraphs sont généralement parmi les premiers curateurs de leurs propres subgraphs, car ils veulent s'assurer que leur subgraph est indexé.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Les conservateurs paient une taxe de conservation de 1 % lorsqu'ils organisent un nouveau subgraph. Cette taxe de conservation est brûlée, ce qui diminue l'offre de GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Développeurs
+## Developers
 
-Les développeurs créent et interrogent des subgraphs pour récupérer les données de la blockchain. Étant donné que les subgraphs sont open source, les développeurs peuvent interroger les subgraphs existants pour charger des données blockchain dans leurs dapps. Les développeurs paient pour les requêtes qu'ils effectuent en GRT, qui est distribué aux participants du réseau.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Création d'un subgraph
 
-Les développeurs peuvent [créer un subgraph](/developing/creating-a-subgraph/) pour indexer des données sur la blockchain. Les subgraphs sont des instructions pour les indexeurs concernant les données qui doivent être servies aux consommateurs.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Une fois que les développeurs ont construit et testé leur subgraph, ils peuvent [publier leur subgraph](/publishing/publishing-a-subgraph/) sur le réseau décentralisé du graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Interroger un subgraph existant
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Les subgraphes sont [interrogés à l'aide de GraphQL](/querying/querying-the-graph/), et les frais de requête sont payés en GRT dans [Subgraph Studio](https://thegraph.com/studio/). Les frais de requête sont distribués aux participants du réseau en fonction de leurs contributions au protocole.
-
-1% des frais de recherche payés au réseau sont brûlés.
-
-## Indexeurs (gagnez du GRT)
-
-Les indexeurs sont l’épine dorsale de The Graph. Ils exploitent du matériel et des logiciels indépendants qui alimentent le réseau décentralisé de The Graph. Les indexeurs fournissent des données aux consommateurs sur la base des instructions des subgraphs.
-
-Les indexeurs peuvent obtenir des récompenses en GRT de deux manières :
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Frais de requête : GRT payés par les développeurs ou les utilisateurs pour les requêtes de données de subgraphs. Les frais de requête sont directement distribués aux indexeurs selon la fonction de remise exponentielle (voir GIP [ici](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Récompenses d'indexation : l'émission annuelle de 3 % est distribuée aux indexeurs en fonction du nombre de subgraphs qu'ils indexent. Ces récompenses incitent les indexeurs à indexer les subgraphs, parfois avant le début des frais de requête, pour accumuler et soumettre des preuves d'indexation (POI) vérifiant qu'ils ont indexé les données avec précision.
+## Indexers (Earn GRT)
 
-Chaque subgraph se voit attribuer une partie de l’émission totale de jetons de réseau, en fonction de la quantité de signal de curation du subgraph. Ce montant est ensuite récompensé aux indexeurs en fonction de leur participation allouée sur le subgraph.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Pour faire fonctionner un nœud d'indexation, les indexeurs doivent miser au moins 100 000 GRT sur le réseau. Les indexeurs sont incités à miser des GRT proportionnellement au nombre de requêtes qu'ils traitent.
+Indexers can earn GRT rewards in two ways:
 
-Les indexeurs peuvent augmenter leurs allocations de GRT sur les subgraphes en acceptant la délégation de GRT des délégateurs, et ils peuvent accepter jusqu'à 16 fois leur mise initiale. Si un indexeur devient "sur-délégué" (c'est-à-dire plus de 16 fois sa mise initiale), il ne pourra pas utiliser le GRT supplémentaire des délégateurs tant qu'il n'aura pas augmenté sa mise dans le réseau.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-Le montant des récompenses qu'un indexeur reçoit peut varier en fonction de la mise initiale, de la délégation acceptée, de la qualité du service et bien d'autres facteurs. Le graphique suivant présente les données publiquement disponibles provenant d'un indexeur actif sur le réseau décentralisé de The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### La mise & récompense de l'indexeur allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Indexation des enjeux et des récompenses](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Ces données couvrent la période allant de février 2021 à septembre 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Veuillez noter que cette situation s'améliorera lorsque la migration [Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) sera terminée, ce qui réduira considérablement la charge liée aux coûts du gaz pour les participants au réseau.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Approvisionnement en jetons: Destruction & Émission
+## Token Supply: Burning & Issuance
 
-L'offre initiale de jetons est de 10 milliards de GRT, avec un objectif de 3 % de nouvelles émissions par an pour récompenser les indexeurs pour l'attribution de participations sur les subgraphs. Cela signifie que l'offre totale de jetons GRT augmentera de 3 % chaque année à mesure que de nouveaux jetons seront émis aux indexeurs pour leur contribution au réseau.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graph est conçu avec plusieurs mécanismes de gravure pour compenser l'émission de nouveaux jetons. Environ 1 % de l'approvisionnement en GRT est brûlé chaque année à travers diverses activités sur le réseau, et ce nombre augmente à mesure que l'activité du réseau continue de croître. Ces activités de gravure comprennent une taxe de délégation de 0,5 % chaque fois qu'un délégant délègue GRT à un indexeur, une taxe de conservation de 1 % lorsque les conservateurs signalent sur un subgraph et 1 % des frais de requête pour les données blockchain.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Total de GRT détruits](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-En plus de ces activités de brûlage régulières, le jeton GRT dispose également d'un mécanisme de réduction (slashing) pour pénaliser les comportements malveillants ou irresponsables des indexeurs. Lorsqu'un indexeur est sanctionné, 50 % de ses récompenses d'indexation pour l'époque sont brûlées (l'autre moitié allant au pêcheur), et sa participation personnelle est réduite de 2,5 %, la moitié de ce montant étant brûlée. Cela permet de s'assurer que les indexeurs sont fortement incités à agir dans l'intérêt du réseau et à contribuer à sa sécurité et à sa stabilité.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Améliorer le protocole
+## Improving the Protocol
 
-Le réseau The Graph est en constante évolution et des améliorations sont constamment apportées à la conception économique du protocole pour offrir la meilleure expérience à tous les participants du réseau. Le Conseil du graph supervise les changements de protocole et les membres de la communauté sont encouragés à participer. Impliquez-vous dans les améliorations du protocole dans [The Graph Forum](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 3170236501cba051bd8f96949cddb4348af53a8a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:45 -0500
Subject: [PATCH 0408/1325] New translations tokenomics.mdx (Spanish)

---
 website/pages/es/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/es/tokenomics.mdx b/website/pages/es/tokenomics.mdx
index 97a07883e8bf..d2b3cdd86026 100644
--- a/website/pages/es/tokenomics.mdx
+++ b/website/pages/es/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Tokenomics de The Graph Network
-description: The Graph Network está incentivado por un poderoso tokenomics. Así es como funciona GRT, el token de utilidad de trabajo nativo de The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Descripción
 
-- Dirección del token GRT en Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph es un protocolo descentralizado que permite un acceso sencillo a los datos de la blockchain.
+## Specifics
 
-Es similar a un modelo B2B2C, pero está impulsado por una red descentralizada de participantes. Los participantes de la red trabajan juntos para proporcionar datos a los usuarios finales a cambio de recompensas en GRT. GRT es el token de utilidad que coordina a los proveedores y consumidores de datos. GRT actúa como una utilidad para coordinar a los proveedores y consumidores de datos dentro de la red, e incentiva a los participantes del protocolo a organizar los datos de manera efectiva.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexa los datos de la blockchain de forma similar a como Google indexa la web. De hecho, es posible que ya estés utilizando The Graph sin darte cuenta. Si has visto la interfaz de una aplicación que obtiene sus datos de un subgrafo, ¡has consultado datos de un subgrafo!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph desempeña un papel crucial a la hora de hacer más accesibles los datos de la blockchain y proporcionar un mercado para su intercambio.
+- Dirección del token GRT en Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Los roles de los participantes de la red
+## The Roles of Network Participants
 
-Hay cuatro participantes principales en la red:
+There are four primary network participants:
 
 1.  Delegadores - Delegan GRT a los Indexadores y aseguran la red
 
@@ -29,82 +29,74 @@ Hay cuatro participantes principales en la red:
 
 4.  Indexadores: Son la columna vertebral de los datos de la blockchain
 
-Fishermen (o pescadores) y Arbitrators también contribuyen al éxito de la red con otros aportes, apoyando el trabajo de los demás roles principales de los participantes. Para más información sobre las funciones de la red, lee [este artículo](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Diagrama del tokenomics](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegadores (ganan GRT de manera pasiva)
+## Delegators (Passively earn GRT)
 
-Los Delegadores delegan GRT en los Indexadores, aumentando su stake en los subgrafos de la red. A cambio, los Delegadores obtienen un porcentaje de todas las tarifas de consulta y recompensas de indexación del Indexador. Cada Indexador fija el porcentaje que se recompensará a los Delegadores de forma independiente, lo que crea una competencia entre los Indexadores para atraer a los Delegadores. La mayoría de los Indexadores ofrecen entre un 9 y un 12% anual.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Por ejemplo, si un Delegador delegara 15.000 GRT a un Indexador que ofreciera el 10%, el Delegador recibiría ~1500 GRT anuales en recompensas.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Existe un impuesto de delegación del 0,5% que se quema cada vez que un Delegador delega GRT en la red. Si un Delegador decide retirar su GRT delegado, debe esperar al periodo de desbloqueo de 28 épocas. Cada época es de 6.646 bloques, lo que significa que 28 épocas terminan siendo aproximadamente 26 días.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Si estás leyendo esto, eres capaz de convertirte en Delegador ahora mismo dirigiéndote a la [página de participantes de la red](https://thegraph.com/explorer/participants/indexers) y delegando GRT en un Indexador de tu elección.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Curadores (ganan GRT)
+## Curators (Earn GRT)
 
-Los Curadores identifican subgrafos de alta calidad y los "curan" (es decir, señalan GRT en ellos) para ganar cuotas de curación, que garantizan un porcentaje de todas las futuras tarifas de consulta generadas por el subgrafo. Aunque cualquier participante independiente de la red puede ser Curador, los desarrolladores de subgrafos suelen estar entre los primeros Curadores de sus propios subgrafos porque quieren asegurarse de que su subgrafo está indexado.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Los Curadores pagan un impuesto de curación del 1% cuando curan un nuevo subgrafo. Este impuesto se quema, lo que reduce la oferta de GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Desarolladores
+## Developers
 
-Los Desarrolladores construyen y consultan subgrafos para recuperar datos de la blockchain. Dado que los subgrafos son de código abierto, los Desarrolladores pueden consultar subgrafos existentes para cargar datos de la blockchain en sus dapps. Los Desarrolladores pagan por las consultas que realizan en GRT, que se distribuye entre los participantes de la red.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Creación de un subgrafo
 
-Los desarrolladores pueden [crear un subgrafo](/developing/creating-a-subgraph/) para indexar datos en la blockchain. Los subgrafos son instrucciones para los Indexadores sobre qué datos deben servirse a los consumidores.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Una vez que los desarrolladores han construido y probado su subgrafo, pueden [publicarlo](/publishing/publishing-a-subgraph/) en la red descentralizada de The Graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Consulta de un subgrafo existente
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Los subgrafos se [consultan utilizando GraphQL](/querying/querying-the-graph/), y las tarifas de consulta se pagan con GRT en [Subgraph Studio](https://thegraph.com/studio/). Las tarifas de consulta se distribuyen entre los participantes de la red en función de sus contribuciones al protocolo.
-
-Se quema el 1% de las tarifas de consulta pagadas a la red.
-
-## Indexadores (Ganan GRT)
-
-Los indexadores son la columna vertebral de The Graph. Funcionan con hardware y software independientes que alimentan la red descentralizada de The Graph. Los Indexadores sirven datos a los consumidores siguiendo instrucciones de los subgrafos.
-
-Los Indexadores pueden obtener recompensas de GRT de dos maneras:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Recompensas de indexación: la emisión anual del 3% se distribuye a los Indexadores en función del número de subgrafos que indexan. Estas recompensas incentivan a los Indexadores a indexar subgrafos, ocasionalmente antes de que comiencen las tarifas de consulta, para acumular y enviar Pruebas de Indexación (POIs) que verifiquen que han indexado datos con precisión.
+## Indexers (Earn GRT)
 
-A cada subgrafo se le asigna una parte de la emisión total de tokens de la red, en función de la cantidad de la señal de curación del subgrafo. Esa cantidad se recompensa a los Indexadores en función de su participación en el subgrafo.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Para poner en marcha un nodo de indexación, los Indexadores deben realizar stake de 100.000 GRT o más en la red. A los Indexadores se les incentiva a realizar stake de GRT en proporción a la cantidad de consultas que atienden.
+Indexers can earn GRT rewards in two ways:
 
-Los Indexadores pueden aumentar sus allocations de GRT en subgrafos aceptando la delegación de GRT de los Delegadores, y pueden aceptar hasta 16 veces su stake inicial. Si un Indexador se "sobredelega" (es decir, más de 16 veces su stake inicial), no podrá utilizar el GRT adicional de los Delegadores hasta que aumente su stake en la red.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-La cantidad de recompensas que recibe un Indexador puede variar en función del stake inicial, la delegación aceptada, la calidad del servicio y muchos más factores. El siguiente gráfico muestra datos públicos de un Indexador activo en la red descentralizada de The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### El stake y las recompensas del Indexador allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Stake y recompensas de indexación](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Estos datos son de febrero de 2021 a septiembre de 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Ten en cuenta que esta situación mejorará cuando finalice la [migración a Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551), con lo que el coste del gas será mucho menor para los participantes en la red.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Suministro de tokens: Quema y emisión
+## Token Supply: Burning & Issuance
 
-El suministro inicial de tokens es de 10.000 millones de GRT, con un objetivo de 3% de nuevas emisiones anuales para recompensar a los Indexadores por asignar stake en subgrafos. Esto significa que la oferta total de tokens GRT aumentará un 3% cada año a medida que se emitan nuevos tokens a los Indexadores por su contribución a la red.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graph está diseñado con múltiples mecanismos de quema para compensar la emisión de nuevos tokens. Aproximadamente el 1% de la oferta de GRT se quema anualmente a través de diversas actividades en la red, y este número ha ido aumentando a medida que la actividad de la red sigue creciendo. Estas actividades de quema incluyen un impuesto de delegación del 0,5% cada vez que un Delegador delega GRT a un Indexador, un impuesto de curación del 1% cuando los Curadores señalan en un subgrafo, y un 1% de las tarifas de consulta de datos de blockchain.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Total GRT quemado](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-Además de estas actividades de quema periódicas, el token GRT también cuenta con un mecanismo de slashing para penalizar el comportamiento malicioso o irresponsable de los Indexadores. Si un Indexador recibe slashing, se quema el 50% de sus recompensas de indexación de la época (mientras que la otra mitad va a parar al Fisherman), y su self-stake se reduce en un 2,5%, quemándose la mitad de esta cantidad. Esto ayuda a garantizar que los Indexadores tengan un fuerte incentivo para actuar en el mejor interés de la red y contribuir a su seguridad y estabilidad.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Mejorando el protocolo
+## Improving the Protocol
 
-The Graph Network está en constante evolución y se introducen mejoras en el diseño económico del protocolo para ofrecer la mejor experiencia a todos los participantes en la red. The Graph Council supervisa los cambios en el protocolo y se anima a los miembros de la comunidad a participar. Participe en las mejoras del protocolo en el [Graph Forum](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From eee4f1caecb3c4757cf3fb5c2709734bd7f25384 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:46 -0500
Subject: [PATCH 0409/1325] New translations tokenomics.mdx (Arabic)

---
 website/pages/ar/tokenomics.mdx | 90 +++++++++++++++------------------
 1 file changed, 41 insertions(+), 49 deletions(-)

diff --git a/website/pages/ar/tokenomics.mdx b/website/pages/ar/tokenomics.mdx
index ef7aee0871ec..049df2b7f086 100644
--- a/website/pages/ar/tokenomics.mdx
+++ b/website/pages/ar/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: اقتصاد التوكن (Tokenomics) لشبكة الغراف
-description: تعتمد شبكة The Graphعلى نظام إقتصادي قوي للتشجيع على المشاركة. إليك كيف يعمل GRT ، التوكن الأساسي للعمل في The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## نظره عامة
 
-- عنوان توكن GRT على Arbitrum One: [ 0x9623063377AD1B27544C965cCd7342f7EA7e88C7 ](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Specifics
 
-إنه مشابه لنموذج B2B2C ، إلا أنه مدعوم بشبكة لا مركزية من المشاركين. يعمل المشاركون في الشبكة معًا لتوفير البيانات للمستخدمين النهائيين مقابل مكافآت GRT. GRT هو أداة العمل الذي ينسق بين موفري البيانات والمستهلكين. تعمل GRT كأداة مساعدة للتنسيق بين موفري البيانات والمستهلكين داخل الشبكة وتحفيز المشاركين في البروتوكول على تنظيم البيانات بشكل فعال.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-يقوم الغراف بفهرسة بيانات blockchain بنفس طريقة فهرسة Google للويب. في الواقع ، ربما كنت تستخدم الغراف بالفعل دون أن تدرك ذلك. إذا كنت قد شاهدت الواجهة الأمامية لـ dapp الذي يحصل على بياناته من subgraph! ، فقد استعلمت عن البيانات من ال subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- عنوان توكن GRT على Arbitrum One: [ 0x9623063377AD1B27544C965cCd7342f7EA7e88C7 ](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## أدوار المشاركين على الشبكة
+## The Roles of Network Participants
 
-هناك أربعة أدوار أساسية في الشبكة:
+There are four primary network participants:
 
 1.  المفوضين (Delegators) - يقومو بتفويض GRT للمفهرسين & تأمين الشبكة
 
@@ -29,82 +29,74 @@ The Graph plays a crucial role in making blockchain data more accessible and ena
 
 4.  المفهرسون (Indexers) - العمود الفقري لبيانات blockchain
 
-الصيادون والمحكمون (Fishermen و Arbitrators) يلعبون أيضاً دورا حاسما في نجاح الشبكة من خلال مساهماتهم الأخرى، ويدعمون عمل الأدوار الأساسية للمشاركين الآخرين. لمزيد من المعلومات حول أدوار الشبكة، يُرجى [قراءة هذه المقالة](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![رسم بياني لاقتصاد التوكن (Tokenomics diagram)](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## المفوِّضين (يربحون GRT بشكل سلبي)
+## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-هناك ضريبة تفويض بنسبة 0.5٪ يتم حرقها عندما يقوم المفوض بتفويض GRT على الشبكة. إذا قرر أحد المفوضين سحب GRT المفوضة ، فيجب عليه الانتظار لفترة فك الارتباط والتي تستغرق 28 حقبة. كل حقبة تتكون من 6646 كتلة ، مما يعني أن 28 حقبة تستغرق حوالي 26 يومًا.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-إذا كنت تقرأ هذا ، فيمكنك أن تصبح مفوضًا الآن من خلال التوجه إلى [ صفحة المشاركين في الشبكة ](https://thegraph.com/explorer/participants/indexers) ، و تفويض GRT إلى مفهرس من اختيارك.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## المنسِّقون (كسب GRT)
+## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## المطورين
+## Developers
 
-يقوم المطورون ببناء الsubgraphs والاستعلام عنها لاسترداد بيانات blockchain. نظرًا لأن الsubgraph مفتوحة المصدر ، يمكن للمطورين الاستعلام عن الsubgraph الموجودة لتحميل بيانات blockchain في dapps الخاصة بهم. يدفع المطورون ثمن الاستعلامات التي يقومون بها ب GRT ، والتي يتم توزيعها على المشاركين في الشبكة.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### إنشاء subgraph
 
-يمكن للمطورين [ إنشاء subgraph ](/developing/creating-a-subgraph/) لفهرسة البيانات على blockchain. الsubgraph هي تعليمات للمفهرسين حول البيانات التي يجب تقديمها للمستهلكين.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-بمجرد أن يقوم المطورون ببناء الsubgraph واختباره ، يمكنهم [ نشر الsubgraph ](/publishing/publishing-a-subgraph/) على الشبكة اللامركزية لـ The Graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### الاستعلام عن subgraph موجود
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-يتم [ الاستعلام عن الSubgraph باستخدام GraphQL ](/querying/querying-the-graph/) ، ويتم دفع رسوم الاستعلام باستخدام GRT في [ Subgraph Studio ](https://thegraph.com/studio/). يتم توزيع رسوم الاستعلام على المشاركين في الشبكة بناءً على مساهماتهم في البروتوكول.
-
-يتم حرق 1٪ من رسوم الاستعلام المدفوعة للشبكة.
-
-## المفهرسون (كسب GRT)
-
-المفهرسين هم العمود الفقري لThe Graph. يعملون على أجهزة وبرامج مستقلة تشغل الشبكة اللامركزية لـ The Graph. يقدم المفهرسين البيانات للمستهلكين بناءً على تعليمات من الsubgraphs.
-
-يمكن للمفهرسين ربح مكافآت GRT بطريقتين:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  مكافآت الفهرسة: يتم توزيع 3% من الإصدار السنوي على المفهرسين بناءً على عدد الsubgraphs التي يقومون بفهرستها. هذه المكافآت تشجع المفهرسين على فهرسة الsubgraphs ، أحيانًا قبل البدء بفرض الرسوم على الاستعلامات ،يقوم المفهرسون بتجميع وتقديم أدلة فهرسة (POIs) للتحقق من دقة فهرسة البيانات التي قاموا بفهرستها.
+## Indexers (Earn GRT)
 
-كل subgraph يخصص له جزء من إجمالي إصدار التوكن للشبكة بناءً على مقدار إشارة تنسيق الsubgraph. هذا المقدار يتم منحه للمفهرسين وفقا لحصصهم المخصصة على الـ subgraph.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-من أجل تشغيل عقدة الفهرسة ، يجب أن يشارك المفهرسون برهن 100،000 GRT أو أكثر مع الشبكة. يتم تشجيع المفهرسين برهن GRT تتناسب مع عدد الاستعلامات التي يقدمونها.
+Indexers can earn GRT rewards in two ways:
 
-يمكن للمفهرسين زيادة تخصيصاتهم من GRT على الsubgraph عن طريق قبول تفويض GRT من المفوضين ، ويمكنهم قبول ما يصل إلى 16 ضعف من رهانهم أو"حصتهم" الأولي. إذا أصبح المفهرس "مفوضا بشكل زائد" (أي أكثر من 16 ضعف من حصته الأولية) ، فلن يتمكن من استخدام GRT الإضافي من المفوضين حتى يزيد المفهرس حصته في الشبكة.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-يمكن أن يختلف مقدار المكافآت التي يتلقاها المفهرس بناءً على الحصة الأولية والتفويض المقبول وجودة الخدمة والعديد من العوامل الأخرى. الرسم البياني التالي هي بيانات عامة لمفهرس نشط في شبكة TheGraph اللامركزية.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### The Indexer stake & reward of allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![حصص الفهرسة والمكافآت](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-هذه البيانات من فبراير 2021 إلى سبتمبر 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> يرجى ملاحظة أن هذا سيتحسن عند اكتمال عملية الترحيل إلى [Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551)، مما يجعل تكاليف الغاز أقل بشكل كبير ويجعلها أقل عبئا للمشاركة في الشبكة.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## معروض التوكن: الحرق & الإصدار
+## Token Supply: Burning & Issuance
 
-يبلغ المعروض الأولي للتوكن 10 مليار GRT ، مع هدف إصدار جديد بنسبة 3٪ سنويًا لمكافأة المفهرسين الذين يخصصون حصصهم على الsubgraphs. هذا يعني أن إجمالي المعروض من توكن GRT سيزيد بنسبة 3٪ كل عام حيث يتم إصدار توكن جديد للمفهرسين تكريما لمساهمتهم في الشبكة.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
 The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![مجموع عملة القراف المحروقة](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-بالإضافة إلى أنشطة الحرق الدورية المذكورة، يتوفر في توكن GRT آلية القطع لمعاقبة المفهرسين المسؤولين عن سلوك ضار أو غير مسؤول. وفي حالة إعطائهم عقوبة القطع، يتم حرق 50% من مكافآتهم الخاصة بالفهرسة في فترة زمنية محددة (بينما يذهب النصف الآخر للصياد"fisherman")، ويتم خفض حصتهم الشخصية بنسبة 2.5%، ويتم حرق نصف هذا المبلغ. ويساعد ذلك على ضمان أن المفهرسين لديهم حافز قوي للعمل بما يخدم مصالح الشبكة والمساهمة في أمنها واستقرارها.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## تحسين البروتوكول
+## Improving the Protocol
 
-تتطور شبكة Graph باستمرار ويتم إجراء تحسينات على التصميم الاقتصادي للبروتوكول باستمرار لتوفير أفضل تجربة لجميع المشاركين في الشبكة. يشرف مجلس The Graph على تغييرات البروتوكول ويتم تشجيع أعضاء المجتمع على المشاركة. شارك في تحسينات البروتوكول في [ منتدى The Graph ](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From d42ac0510cd4c9d0020a1e47d0354b60a0855077 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:47 -0500
Subject: [PATCH 0410/1325] New translations tokenomics.mdx (Czech)

---
 website/pages/cs/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/cs/tokenomics.mdx b/website/pages/cs/tokenomics.mdx
index f884f2e3257a..01a258d0fdcd 100644
--- a/website/pages/cs/tokenomics.mdx
+++ b/website/pages/cs/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Tokenomics sítě grafů
-description: Síť grafů je motivována výkonnou tokenomikou. Zde se dozvíte, jak funguje GRT, nativní token pracovní užitečnost grafu.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Přehled
 
-- Adresa tokenu GRT na Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-Graf je decentralizovaný protokol, který umožňuje snadný přístup k datům blockchainu.
+## Specifics
 
-Je to podobný model jako B2B2C, jen je poháněn decentralizovanou sítí účastníků. Účastníci sítě spolupracují na poskytování dat koncovým uživatelům výměnou za odměny GRT. GRT je token pracovní utility, který koordinuje poskytovatele a spotřebitele dat. GRT slouží jako utilita pro koordinaci poskytovatelů a spotřebitelů dat v rámci sítě a motivuje účastníky protokolu k efektivní organizaci dat.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-Pomocí Graf mohou uživatelé snadno přistupovat k datům z blockchainu a platit pouze za konkrétní informace, které potřebují. Graf dnes využívá mnoho [populárních dapps](https://thegraph.com/explorer) v ekosystému web3.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-Graf indexuje data blockchainu podobně jako Google indexuje web. Možná už Graf používáte, aniž byste si to uvědomovali. Pokud jste si prohlíželi front end dapp, která získává svá data z podgrafu, dotazovali jste se na data z podgrafu!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-Graf hraje klíčovou roli při zpřístupňování blockchainových dat a umožnění trhu pro jejich výměnu.
+- Adresa tokenu GRT na Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Role účastníků sítě
+## The Roles of Network Participants
 
-V síti jsou čtyři hlavní účastníci:
+There are four primary network participants:
 
 1.  Delegáti - delegování GRT na indexátory & zabezpečení sítě
 
@@ -29,82 +29,74 @@ V síti jsou čtyři hlavní účastníci:
 
 4.  Indexery - páteř blockchainových dat
 
-Fishermen a Arbitrátoři jsou také nedílnou součástí úspěchu sítě díky svým dalším příspěvkům, které podporují práci ostatních primárních rolí účastníků. Pro více informací o rolích v síti si přečtěte tento článek.
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Tokenomický diagram](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegáti (pasivně vydělávají GRT)
+## Delegators (Passively earn GRT)
 
-Delegáti delegují indexátorům GRT, čímž zvyšují podíl indexátorů na podgraf v síti. Delegáti na oplátku získávají od indexátorů procenta ze všech poplatků za dotazy a odměn za indexování. Každý indexátor si nezávisle na sobě stanoví podíl, který bude delegátům odměněn, čímž vzniká mezi indexátory soutěž o získání delegátů. Většina indexátorů nabízí 9-12% ročně.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Pokud by například delegát delegoval 15 tisíc GRT na indexátora nabízejícího 10%, obdržel by delegát ročně odměnu ~1500 GRT.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Existuje 0.5% daň z delegování, která se spálí vždy, když delegát deleguje GRT v síti. Pokud se delegát rozhodne stáhnout své delegované GRT, musí počkat na 28-epoch lhůtu pro zrušení vazby. Každá epocha je 6 646 bloků, což znamená, že 28 epoch je přibližně 26 dní.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Pokud čtete tento článek, můžete se právě teď stát delegátem tak, že přejdete na stránku [účastníci sítě](https://thegraph.com/explorer/participants/indexers) a delegujete GRT na vybraného indexátora.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Kurátoři (Získat GRT)
+## Curators (Earn GRT)
 
-Kurátoři identifikují vysoce kvalitní podgrafy a "curate" je (tj. signalizují na nich GRT), aby získali kurátorské podíly, které zaručují procento ze všech budoucích poplatků za dotazy generované tímto podgraf. Ačkoli kurátorem může být každý nezávislý účastník sítě, obvykle jsou vývojáři podgrafů mezi prvními kurátory svých vlastních podgrafů, protože chtějí zajistit, aby byl jejich podgraf indexován.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Kurátoři platí 1% kurátorskou daň, když vytvoří nový podgraf. Tato kurátorská daň se spálí, čímž se sníží nabídka GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Vývojáři
+## Developers
 
-Vývojáři vytvářejí podgrafy a dotazují se na ně, aby získali data blockchainu. Vzhledem k tomu, že podgrafy jsou open source, mohou vývojáři dotazovat existující podgrafy a načítat data blockchainu do svých dapps. Vývojáři platí za dotazy, které provádějí v GRT a které jsou distribuovány účastníkům sítě.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Vytvoření podgrafu
 
-Vývojáři mohou [vytvořit subgraf](/developing/creating-a-subgraph/) pro indexování dat v blockchainu. Podgrafy jsou pokyny pro indexátory, která data mají být doručena spotřebitelům.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Jakmile vývojáři vytvoří a otestují svůj podgraf, mohou [zveřejnit svůj podgraf](/publishing/publishing-a-subgraph/) v decentralizované síti Graf.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Dotazování na existující podgraf
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Podgrafy jsou [vyhledávány pomocí GraphQL](/querying/querying-the-graph/) a poplatky za dotazy jsou hrazeny pomocí GRT v [Subgraph Studio](https://thegraph.com/studio/). Poplatky za dotazy se rozdělují mezi účastníky sítě na základě jejich příspěvků do protokolu.
-
-1 % poplatků za dotazy zaplacených síti se spálí.
-
-## Indexéry (Získat GRT)
-
-Základem Graf jsou indexátoři. Provozují nezávislý hardware a software, který pohání decentralizovanou síť Graf. Indexery servírují data spotřebitelům na základě pokynů z dílčích grafů.
-
-Indexátoři mohou získat odměny GRT dvěma způsoby:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Poplatky za dotazy: GRT, které platí vývojáři nebo uživatelé za dotazy na data podgrafu. Poplatky za dotazy jsou rozdělovány přímo indexátorům podle exponenciální funkce rabat (viz GIP [zde](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Odměny za indexování: 3% roční odměna se rozděluje indexátorům podle počtu indexovaných podgrafů. Tyto odměny motivují indexátory k indexování podgrafů, občas před zahájením poplatků za dotazování, k akumulaci a předkládání důkazů o indexaci (POI), které ověřují, že indexovali data přesně.
+## Indexers (Earn GRT)
 
-Každému podgrafu je přidělena část z celkové emise síťových tokenů, a to na základě množství kurátorského signálu podgrafu. Tato částka je pak odměněna indexátorům na základě jejich přiděleného podílu na podgrafu.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Aby bylo možné spustit indexovací uzel, musí indexátory vsadit do sítě 100,000 GRT nebo více. Indexátoři jsou motivováni k tomu, aby sázeli GRT úměrně množství dotazů, které obsluhují.
+Indexers can earn GRT rewards in two ways:
 
-Indexátoři mohou zvýšit své alokace GRT na podgrafy přijetím delegování GRT od delegátů a mohou přijmout až 16násobek svého původního podílu. Pokud se indexátor stane "nadměrně delegovaným" (tj. více než 16násobek svého původního podílu), nebude moci využít dodatečné GRT od delegátů, dokud nezvýší svůj podíl v síti.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-Výše odměny, kterou indexátor obdrží, se může lišit v závislosti na počátečním vkladu, přijatém delegování, kvalitě služeb a mnoha dalších faktorech. V následujícím grafu jsou veřejně dostupné údaje aktivního indexera v decentralizované síti Graf.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### Indexer podíl & odměna allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Indexování podílu a odměn](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Tyto údaje se týkají období od února 2021 do září 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Upozorňujeme, že tato situace se zlepší, až bude dokončena [Arbitrum migrace](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551), takže náklady na plyn budou pro účastníky sítě výrazně nižší.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Dodávka žetonů: Burning & Vydání
+## Token Supply: Burning & Issuance
 
-Počáteční nabídka tokenů je 10 miliard GRT, přičemž cílem je vydávat 3 % nových tokenů ročně jako odměnu indexátorům za přidělování podílů na subgrafech. To znamená, že celková nabídka tokenů GRT se bude každý rok zvyšovat o 3 %, protože nové tokeny budou vydávány Indexerům za jejich příspěvek do sítě.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-Graf je navržen s několika mechanismy spalování, které kompenzují vydávání nových tokenů. Přibližně 1 % zásoby GRT je ročně spáleno prostřednictvím různých aktivit v síti a toto číslo se zvyšuje s tím, jak aktivita sítě stále roste. Mezi tyto spalovací činnosti patří 0.5% daň z delegování, kdykoli delegátor deleguje GRT na indexátora, 1% daň z kurátorství, když kurátoři signalizují na subgrafu, a 1% poplatek za dotaz na data v blockchainu.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Celková spálená GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-Kromě těchto pravidelně se vyskytujících činností vypalování má token GRT také mechanismus slashing, který má trestat zlomyslné nebo nezodpovědné chování indexátorů. Pokud je indexátor slashován, spálí se 50 % jeho odměny za indexaci v dané epoše (zatímco druhá polovina připadne rybáři) a jeho vlastní podíl se sníží o 2.5 %, přičemž polovina této částky se spálí. To pomáhá zajistit, aby indexátoři měli silnou motivaci jednat v nejlepším zájmu sítě a přispívat k její bezpečnosti a stabilitě.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Zlepšení protokolu
+## Improving the Protocol
 
-Síť Graf se neustále vyvíjí a ekonomický návrh protokolu se neustále vylepšuje, aby poskytoval co nejlepší služby všem účastníkům sítě. Na změny protokolu dohlíží Rada Graf a členové komunity jsou vyzýváni k účasti. Zapojte se do zlepšování protokolu v [Fórum Graf](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From b25d8bc4929b57907b3711f09ab5f388b8eed03c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:49 -0500
Subject: [PATCH 0411/1325] New translations tokenomics.mdx (German)

---
 website/pages/de/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/de/tokenomics.mdx b/website/pages/de/tokenomics.mdx
index 2359a03db100..135ec1c56fb8 100644
--- a/website/pages/de/tokenomics.mdx
+++ b/website/pages/de/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Tokenomics des The Graph Netzwerks
-description: The Graph Network wird durch leistungsstarke Tokenomics unterstützt. Hier ist, wie GRT, The Graph's eigener Work Utility Token funktioniert.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Overview
 
-- GRT-Token-Adresse auf Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph ist ein dezentrales Protokoll, das einen einfachen Zugang zu Blockchain-Daten ermöglicht.
+## Besonderheiten
 
-Es ähnelt einem B2B2C-Modell, nur dass es von einem dezentralen Netzwerk von Teilnehmern betrieben wird. Die Netzwerkteilnehmer arbeiten zusammen, um den Endnutzern Daten im Austausch für GRT-Belohnungen zur Verfügung zu stellen. GRT ist der Arbeits-Utility-Token, der Datenanbieter und -nutzer koordiniert. GRT dient als Dienstprogramm zur Koordinierung von Datenanbietern und -nachfragern innerhalb des Netzwerks und schafft Anreize für die Protokollteilnehmer, Daten effektiv zu organisieren.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-Durch die Verwendung von The Graph können Nutzer einfach auf Daten aus der Blockchain zugreifen und zahlen nur für die spezifischen Informationen, die sie benötigen. The Graph wird heute von vielen [populären Dapps](https://thegraph.com/explorer) im web3-Ökosystem verwendet.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexiert Blockchain-Daten ähnlich wie Google das Web. Es kann sogar sein, dass Sie The Graph bereits nutzen, ohne es zu merken. Wenn Sie sich das Frontend einer Dapp angesehen haben, die ihre Daten aus einem Subgraph bezieht, haben Sie Daten aus einem Subgraph abgefragt!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph spielt eine entscheidende Rolle, wenn es darum geht, Blockchain-Daten besser zugänglich zu machen und einen Marktplatz für deren Austausch zu schaffen.
+- GRT-Token-Adresse auf Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Die Rollen der Teilnehmer des Netzwerks
+## The Roles of Network Participants
 
-Es gibt vier primäre Netzwerkteilnehmer:
+There are four primary network participants:
 
 1.  Delegatoren - Delegieren Sie GRT an Indexer & sichern Sie das Netzwerk
 
@@ -29,82 +29,74 @@ Es gibt vier primäre Netzwerkteilnehmer:
 
 4.  Indexer - Das Rückgrat der Blockchain-Daten
 
-Fischer und Schiedsrichter tragen auch durch andere Beiträge zum Erfolg des Netzwerks bei und unterstützen die Arbeit der anderen Hauptakteure. Weitere Informationen über die Rollen im Netzwerk finden Sie in diesem Artikel[Lesen Sie diesen Artikel](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Diagramm zur Tokenomik](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegatoren (verdienen passiv GRT)
+## Delegators (Passively earn GRT)
 
-Indexer werden von Delegatoren mit GRT betraut, die den Anteil des Indexers an den Subgraphen im Netzwerk erhöhen. Im Gegenzug verdienen die Delegatoren einen Prozentsatz aller Abfragegebühren und Indexierungsbelohnungen von den Indexern. Jeder Indexer legt den Anteil, den er an die Delegatoren vergütet, selbständig fest, wodurch ein Wettbewerb zwischen den Indexern entsteht, um Delegatoren anzuziehen. Die meisten Indexierer bieten zwischen 9-12% jährlich.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Wenn zum Beispiel ein Delegator 15.000 BRT an einen Indexer delegiert, der 10 % anbietet, würde der Delegator jährlich ~1500 GRT an Belohnungen erhalten.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Es gibt eine Delegationssteuer von 0,5 %, die jedes Mal erhoben wird, wenn ein Delegator GRT an das Netzwerk delegiert. Wenn ein Delegator beschließt, sein delegiertes GRT zurückzuziehen, muss er die 28-Epochen-Frist abwarten, in der die Bindung aufgehoben wird. Jede Epoche besteht aus 6.646 Blöcken, was bedeutet, dass 28 Epochen ungefähr 26 Tagen entsprechen.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Wenn Sie dies lesen, können Sie sofort Delegator werden, indem Sie auf die [Netzwerkteilnehmerseite](https://thegraph.com/explorer/participants/indexers) gehen und GRT an einen Indexer Ihrer Wahl delegieren.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Kuratoren (verdienen GRT)
+## Curators (Earn GRT)
 
-Kuratoren identifizieren qualitativ hochwertige Untergraphen und "kuratieren" sie (d.h. signalisieren GRT auf ihnen), um Kurationsanteile zu verdienen, die einen Prozentsatz aller zukünftigen Abfragegebühren garantieren, die durch den Untergraphen generiert werden. Obwohl jeder unabhängige Netzwerkteilnehmer ein Kurator sein kann, gehören die Entwickler von Subgraphen in der Regel zu den ersten Kuratoren für ihre eigenen Subgraphen, da sie sicherstellen wollen, dass ihr Subgraph indiziert wird.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Kuratoren zahlen eine Kurationssteuer von 1%, wenn sie einen neuen Untergraphen kuratieren. Diese Kuratierungssteuer wird verbrannt, wodurch das Angebot an GRT sinkt.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Entwickler
+## Developers
 
-Entwickler erstellen Subgraphen und fragen sie ab, um Blockchain-Daten abzurufen. Da Subgraphen quelloffen sind, können Entwickler bestehende Subgraphen abfragen, um Blockchain-Daten in ihre Dapps zu laden. Entwickler zahlen für Abfragen, die sie in GRT machen, das an die Netzwerkteilnehmer verteilt wird.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Erstellung eines Untergraphen
 
-Entwickler können [einen Subgraph](/developing/creating-a-subgraph/) erstellen, um Daten auf der Blockchain zu indizieren. Subgraphen sind Anweisungen für Indexer darüber, welche Daten an Verbraucher geliefert werden sollen.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Sobald Entwickler ihren Subgraphen erstellt und getestet haben, können sie [ihren Subgraphen](/publishing/publishing-a-subgraph/) im dezentralen Netzwerk von The Graph veröffentlichen.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Abfrage eines vorhandenen Untergraphen
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Subgraphen werden [mit GraphQL](/querying/querying-the-graph/) abgefragt, und die Abfragegebühren werden mit GRT in [Subgraph Studio](https://thegraph.com/studio/) bezahlt. Die Abfragegebühren werden an die Netzwerkteilnehmer auf der Grundlage ihrer Beiträge zum Protokoll verteilt.
-
-1 % der an das Netzwerk gezahlten Abfragegebühren werden verbrannt.
-
-## Indexierer (verdienen GRT)
-
-Indexer sind das Rückgrat von The Graph. Sie betreiben unabhängige Hardware und Software, die das dezentrale Netzwerk von The Graph antreiben. Indexer liefern Daten an Verbraucher auf der Grundlage von Anweisungen von Untergraphen.
-
-Indexierer können auf zwei Arten GRT-Belohnungen verdienen:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Abfragegebühren: GRT, die von Entwicklern oder Nutzern für Abfragen von Subgraphen-Daten gezahlt werden. Die Abfragegebühren werden gemäß der exponentiellen Rabattfunktion (siehe GIP [hier](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)) direkt an die Indexierer verteilt.
+1% of the query fees paid to the network are burned.
 
-2.  Indexierungsprämien: Die jährliche Ausgabe von 3 % wird an die Indexierer auf der Grundlage der Anzahl der von ihnen indexierten Untergraphen verteilt. Diese Belohnungen sind ein Anreiz für Indexer, Untergraphen zu indexieren, gelegentlich bevor die Abfragegebühren beginnen, um Proofs of Indexing (POIs) zu sammeln und einzureichen, die bestätigen, dass sie Daten korrekt indexiert haben.
+## Indexers (Earn GRT)
 
-Jedem Untergraphen wird ein Teil der gesamten Netzwerk-Token-Ausgabe zugeteilt, basierend auf der Höhe des Kurationssignals des Untergraphen. Dieser Betrag wird dann an die Indexer auf der Grundlage ihres zugewiesenen Anteils an dem Subgraphen vergütet.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Um einen Indexierungs-Knoten zu betreiben, müssen Indexer 100.000 GRT oder mehr in das Netzwerk einbringen. Für Indexer besteht ein Anreiz, GRT im Verhältnis zur Anzahl der von ihnen bearbeiteten Abfragen einzusetzen.
+Indexers can earn GRT rewards in two ways:
 
-Indexer können ihre GRT-Zuteilungen auf Untergraphen erhöhen, indem sie GRT-Delegierung von Delegatoren akzeptieren, und sie können bis zum 16-fachen ihres ursprünglichen Einsatzes akzeptieren. Wenn ein Indexer "überdelegiert" wird (d.h. mehr als das 16-fache seines ursprünglichen Einsatzes), kann er die zusätzlichen GRT von Delegatoren nicht nutzen, bis er seinen Einsatz im Netzwerk erhöht.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-Die Höhe der Belohnungen, die ein Indexer erhält, kann je nach anfänglichem Einsatz, akzeptierter Delegation, Qualität des Dienstes und vielen weiteren Faktoren variieren. Das folgende Diagramm ist ein öffentlich zugängliches Diagramm eines aktiven Indexers im dezentralen Netzwerk von The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### Der Indexer Einsatz & Belohnung von allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Indexierung von Einsatz und Belohnungen](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Diese Daten beziehen sich auf den Zeitraum von Februar 2021 bis September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Bitte beachten Sie, dass sich diese Situation verbessern wird, wenn die [Arbitrum-Migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) abgeschlossen ist, so dass die Gaskosten für die Teilnehmer des Netzes eine deutlich geringere Belastung darstellen.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Token-Versorgung: Burning & Ausgabe
+## Token Supply: Burning & Issuance
 
-Das anfängliche Token-Angebot beträgt 10 Milliarden GRT, mit einem Ziel von 3 % Neuemissionen pro Jahr, um Indexer für die Zuweisung von Anteilen an Subgraphen zu belohnen. Das bedeutet, dass das Gesamtangebot an GRT-Token jedes Jahr um 3 % steigen wird, da neue Token an Indexer für ihren Beitrag zum Netzwerk ausgegeben werden.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graph ist mit mehreren Brennmechanismen ausgestattet, um die Ausgabe neuer Token auszugleichen. Ungefähr 1 % des GRT-Angebots wird jährlich durch verschiedene Aktivitäten im Netzwerk verbrannt, und diese Zahl steigt, da die Netzwerkaktivität weiter zunimmt. Zu diesen Burning-Aktivitäten gehören eine Delegationssteuer von 0,5 %, wenn ein Delegator GRT an einen Indexer delegiert, eine Kurationssteuer von 1 %, wenn Kuratoren ein Signal auf einem Untergraphen geben, und 1 % der Abfragegebühren für Blockchain-Daten.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Verbrannte GRT insgesamt](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-Zusätzlich zu diesen regelmäßig stattfindenden Burning-Aktivitäten verfügt der GRT-Token auch über einen Slashing-Mechanismus, um böswilliges oder unverantwortliches Verhalten von Indexern zu bestrafen. Wenn ein Indexer geslashed wird, werden 50% seiner Indexierungsbelohnungen für die Epoche verbrannt (während die andere Hälfte an den Fischer geht), und sein Eigenanteil wird um 2,5% gekürzt, wobei die Hälfte dieses Betrags verbrannt wird. Dies trägt dazu bei, dass Indexer einen starken Anreiz haben, im besten Interesse des Netzwerks zu handeln und zu dessen Sicherheit und Stabilität beizutragen.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Verbesserung des Protokolls
+## Improving the Protocol
 
-Das The Graph Network entwickelt sich ständig weiter, und es werden laufend Verbesserungen an der wirtschaftlichen Gestaltung des Protokolls vorgenommen, um allen Netzwerkteilnehmern die bestmögliche Erfahrung zu bieten. DerThe Graph-Rat überwacht die Protokolländerungen, und die Mitglieder der Community sind aufgerufen, sich daran zu beteiligen. Beteiligen Sie sich an der Verbesserung des Protokolls im [Das Graph Forum](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 77cd3d2ff685734e45d5a24787753256de96da25 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:50 -0500
Subject: [PATCH 0412/1325] New translations tokenomics.mdx (Italian)

---
 website/pages/it/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/it/tokenomics.mdx b/website/pages/it/tokenomics.mdx
index 04e1f3f753b1..cab957ee77ac 100644
--- a/website/pages/it/tokenomics.mdx
+++ b/website/pages/it/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Tokenomics di The Graph Network
-description: The Graph Network è incentivato da una forte tokenomics. Ecco come funziona GRT, il token di utilità nativo di The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Panoramica
 
-- Indirizzo del token GRT su Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph è un protocollo decentralizzato che consente di accedere facilmente ai dati della blockchain.
+## Specifics
 
-È simile a un modello B2B2C, ma è alimentato da una rete decentralizzata di partecipanti. I partecipanti alla rete collaborano per fornire dati agli utenti finali in cambio di ricompense GRT. GRT è il token di utilità che coordina i fornitori e i consumatori di dati. Il GRT funge da utilità per coordinare i fornitori e i consumatori di dati all'interno della rete e incentiva i partecipanti al protocollo a organizzare i dati in modo efficace.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-Utilizzando The Graph, gli utenti possono accedere facilmente ai dati della blockchain, pagando solo per le informazioni specifiche di cui hanno bisogno. The Graph è utilizzato da molte [dapp popolari](https://thegraph.com/explorer) nell'ecosistema web3.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indicizza i dati della blockchain in modo simile a come Google indicizza il web. In effetti, potreste già utilizzare The Graph senza rendervene conto. Se avete visualizzato il front-end di una dapp che ottiene i suoi dati da un subgraph, avete interrogato i dati di un subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph svolge un ruolo cruciale nel rendere più accessibili i dati della blockchain e nel creare un mercato per il loro scambio.
+- Indirizzo del token GRT su Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## I ruoli dei partecipanti alla rete
+## The Roles of Network Participants
 
-I partecipanti alla rete sono quattro:
+There are four primary network participants:
 
 1.  Delegator - Delegare il GRT agli Indexer e proteggere la rete
 
@@ -29,82 +29,74 @@ I partecipanti alla rete sono quattro:
 
 4.  Indexer - Struttura portante dei dati della blockchain
 
-I Fisherman e glii Arbitrator sono parte integrante del successo della rete anche attraverso altri contributi, che supportano il lavoro degli altri ruoli principali dei partecipanti. Per maggiori informazioni sui ruoli della rete, [leggere questo articolo](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Diagramma della Tokenomics](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegator (guadagnano GRT passivamente)
+## Delegators (Passively earn GRT)
 
-Agli Indexer sono delegati GRT dai Delegator che aumentano lo stake dell'Indexer nei subgraph della rete. In cambio, i Delegator guadagnano una percentuale su tutte le tariffe di query e sui premi di indicizzazione dell'Indexer. Ogni Indexer stabilisce in modo indipendente la percentuale che verrà ricompensata ai Delegator, creando una concorrenza tra gli Indexer per attirare i Delegator. La maggior parte degli Indexer offre tra il 9 e il 12% annuo.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Ad esempio, se un Delegator dovesse delegare 15k GRT a un Indexer che offre il 10%, il Delegator riceverebbe annualmente ~1500 GRT in ricompense.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Esiste una tassa di delega dello 0,5% che viene bruciata ogni volta che un Delegator delega GRT sulla rete. Se un Delegator sceglie di ritirare il proprio GRT delegato, deve attendere il periodo di unbonding di 28 epoche. Ogni epoca corrisponde a 6.646 blocchi, il che significa che 28 epoche corrispondono a circa 26 giorni.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Se state leggendo queste righe, potete diventare Delegator fin da ora andando alla pagina [participanti alla rete](https://thegraph.com/explorer/participants/indexers) e delegando GRT a un Indexer di vostra scelta.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Curator (guadagnano GRT)
+## Curators (Earn GRT)
 
-I Curator identificano i subgraph di alta qualità e li "curano" (cioè segnalano il GRT su di essi) per guadagnare quote di curation, che garantiscono una percentuale di tutte le future tariffe di query generate dal subgraph. Anche se qualsiasi partecipante indipendente alla rete può essere un Curator, di solito gli sviluppatori di subgraph sono tra i primi Curator dei loro subgraph, perché vogliono assicurarsi che il loro subgraph sia indicizzato.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-I Curator pagano una tassa di curation dell'1% quando curano un nuovo subgraph. Questa tassa di curation viene bruciata, diminuendo l'offerta di GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Sviluppatori
+## Developers
 
-Gli sviluppatori costruiscono e eseguono i subgraph per recuperare i dati della blockchain. Poiché i subgraph sono open source, gli sviluppatori possono eseguire query di subgraph esistenti per caricare i dati della blockchain nelle loro dapp. Gli sviluppatori pagano per le query effettuate in GRT, che viene distribuito ai partecipanti alla rete.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Creare un subgraph
 
-Gli sviluppatori possono [creare un subgraph](/developing/creating-a-subgraph/) per indicizzare i dati sulla blockchain. I subgraph sono istruzioni per gli Indexer su quali dati devono essere serviti ai consumatori.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Una volta che gli sviluppatori hanno costruito e testato il loro subgraph, possono [pubblicare il loro subgraph](/publishing/publishing-a-subgraph/) sulla rete decentralizzata di The Graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Eseguire query di un subgraph esistente
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-I subgraph [vengono interrogati utilizzando GraphQL](/querying/querying-the-graph/), e le tariffe di query vengono pagate con GRT nel [Subgraph Studio](https://thegraph.com/studio/). Le tariffe di query sono distribuite ai partecipanti alla rete in base ai loro contributi al protocollo.
-
-1% delle tariffe di query pagate alla rete viene bruciato.
-
-## Indexer (Guadagnano GRT)
-
-Gli Indexer sono la spina dorsale di The Graph. Gestiscono hardware e software indipendenti che alimentano la rete decentralizzata di The Graph. Gli Indexer servono i dati ai consumatori in base alle istruzioni dei subgraph.
-
-Gli Indexer possono guadagnare premi GRT in due modi:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Tariffe di query: GRT pagato dagli sviluppatori o dagli utenti per le query sui dati del subgraph. Le tariffe di query sono distribuite direttamente agli Indexer secondo la funzione di sconto esponenziale (vedi GIP [qui](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Ricompense per l'indicizzazione: l'emissione annuale del 3% viene distribuita agli Indexer in base al numero di subgraph che stanno indicizzando. Queste ricompense incentivano gli Indexer a indicizzare i subgraph, occasionalmente prima dell'inizio delle tariffe di query, per accumulare e inviare Proofs of Indexing (POI) che verificano l'accuratezza dell'indicizzazione dei dati.
+## Indexers (Earn GRT)
 
-A ogni subgraph viene assegnata una parte dell'emissione totale di token della rete, in base all'importo del segnale di curation del subgraph. Tale importo viene poi ricompensato agli Indexer in base alla quota di partecipazione assegnata al subgraph.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Per gestire un nodo di indicizzazione, gli Indexer devono investire nella rete almeno 100.000 GRT. Gli Indexer sono incentivati a fare lo stake in GRT in proporzione alla quantità di query che servono.
+Indexers can earn GRT rewards in two ways:
 
-Gli Indexer possono aumentare le loro allocazione di GRT sui subgraph accettando la delega di GRT da parte dei Delegator, e possono accettare fino a 16 volte la loro partecipazione iniziale. Se un Indexer diventa "sovra-delegato" (cioè, più di 16 volte la sua partecipazione iniziale), non sarà in grado di utilizzare il GRT aggiuntivo dei Delegator fino a quando non aumenterà la sua partecipazione alla rete.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-La quantità delle ricompense che un Indexer riceve può variare in base allo stake iniziale, al delega accettata, alla qualità del servizio e a molti altri fattori. Il grafico seguente è costituito dai dati pubblicamente disponibili di un Indexer attivo sulla rete decentralizzata di The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### L'Indexer stake e ricompensa di allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Stake e ricompense di indicizzazione](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-I dati si riferiscono al periodo febbraio 2021-settembre 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Si noti che questa situazione migliorerà quando la [migrazione di Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) sarà completata, rendendo i costi del gas un onere significativamente inferiore per la partecipazione alla rete.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Fornitura di token: Bruciatura e Emissione
+## Token Supply: Burning & Issuance
 
-L'offerta iniziale di token è di 10 miliardi di GRT, con un obiettivo del 3% di nuove emissioni all'anno per ricompensare gli Indexer per per l'allocation dello stake nel subgraph. Ciò significa che l'offerta totale di token GRT aumenterà del 3% ogni anno, quando vengono emessi nuovi token agli Indexer per il loro contributo alla rete.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graph è progettato con meccanismi multipli di combustione per compensare l'emissione di nuovi token. Circa 1% della fornitura di GRT viene bruciato ogni anno attraverso varie attività sulla rete, e questo numero è aumentato con la continua crescita dell'attività della rete. Queste attività di combustione includono una tassa di delega di 0,5% ogni volta che un Delegator delega GRT a un Indexer, una tassa di curation di 1% quando i Curator segnalano un subgraph e 1% delle tariffe di query per i dati della blockchain.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Totale GRT bruciati](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-Oltre a queste attività di combustione che si svolgono regolarmente, il token GRT prevede anche un meccanismo di taglio per penalizzare i comportamenti dannosi o irresponsabili degli Indexer. Se un Indexer subisce un taglio, il 50% delle sue ricompense di indicizzazione per l'epoca viene bruciato (mentre l'altra metà va al fisherman), e la sua self-stake viene ridotta del 2,5%, con la metà di questo importo che viene bruciata. Ciò contribuisce a garantire che gli Indexer siano fortemente incentivati ad agire nell'interesse della rete e a contribuire alla sua sicurezza e stabilità.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Miglioramento del protocollo
+## Improving the Protocol
 
-La Rete di The Graph è in continua evoluzione e i miglioramenti al design economico del protocollo vengono costantemente apportati per fornire la migliore esperienza a tutti i partecipanti alla rete. Il Graph Council supervisiona le modifiche al protocollo e i membri della comunità sono incoraggiati a partecipare. Partecipate ai miglioramenti del protocollo nel [The Graph Forum](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 08786a20b7e955436fa7193194ef571d4d43eb9a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:51 -0500
Subject: [PATCH 0413/1325] New translations tokenomics.mdx (Japanese)

---
 website/pages/ja/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/ja/tokenomics.mdx b/website/pages/ja/tokenomics.mdx
index 9633dd7d13e1..58a6e5871ca8 100644
--- a/website/pages/ja/tokenomics.mdx
+++ b/website/pages/ja/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: グラフネットワークのトークノミクス
-description: The Graph Networkは、強力なトークノミクスでインセンティブを与えています。ここでは、The GraphのネイティブワークユーティリティトークンであるGRTの仕組みについて説明します。
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## 概要
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-グラフは、ブロックチェーン データへの簡単なアクセスを可能にする分散型プロトコルです。
+## Specifics
 
-B2B2C モデルに似ていますが、参加者の分散型ネットワークによって強化されています。ネットワーク参加者は協力して、GRT 報酬と引き換えにエンド ユーザーにデータを提供します。 GRT は、データのプロバイダーとコンシューマーを調整するワーク ユーティリティ トークンです。 GRT は、ネットワーク内のデータ プロバイダーとコンシューマーを調整するためのユーティリティとして機能し、プロトコル参加者がデータを効果的に整理するように動機付けます。
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-The Graphを利用することで、ユーザーはブロックチェーンのデータに簡単にアクセスでき、必要な特定の情報に対してのみ料金を支払うことができます。The Graphは、今日のweb3エコシステムにおける多くの[人気dapps](https://thegraph.com/explorer)によって使用されています。
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graphは、Googleがウェブをインデックスするのと同様に、ブロックチェーンデータをインデックスします。実際、あなたは気づかないうちにすでにThe Graphを利用しているかもしれません。サブグラフからデータを取得するダップのフロントエンドを見たことがあるなら、サブグラフからデータを照会したことになります。
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-グラフは、ブロックチェーンのデータをより身近なものにし、その交換のためのマーケットプレイスを実現するという重要な役割を担っています。
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## ネットワーク参加者の役割
+## The Roles of Network Participants
 
-主なネットワーク参加者は4つの種類があります：
+There are four primary network participants:
 
 1.  デリゲーター - GRTをインデクサーに委任する & ネットワークを確保する
 
@@ -29,82 +29,74 @@ The Graphは、Googleがウェブをインデックスするのと同様に、
 
 4.  インデクサー - ブロックチェーンデータのバックボーン
 
-フィッシャーマンとアービトレーターは、他の貢献を通じてネットワークの成功に不可欠な存在であり、他の主要参加者の役割の仕事をサポートします。ネットワークの役割の詳細については、[この記事をお読みください](https://thegraph.com/blog/the-graph-grt-token-economics/)。
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![トークノミクス図](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## 委任者 (受動的に GRT を獲得)
+## Delegators (Passively earn GRT)
 
-インデクサーは、ネットワーク上のサブグラフでインデクサーのステークを増やす委任者によって GRT を委任されます。その見返りとして、委任者はすべてのクエリ料金とインデクサーからのインデックス作成報酬の一定の割合を獲得します。各インデクサーは、委任者に報いるカットを個別に設定し、委任者を引き付けるためにインデクサー間の競争を生み出します。ほとんどのインデクサーは、年間 9 ～ 12% のオファーを提供しています
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-例えば、デリゲーターが10％の報酬を提供するインデクサーに15000GRTを委任した場合、委任者は年間1500GRTの報酬を受け取ることになります。
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-0.5%のデリゲーター税は、デリゲーターがネットワーク上でGRTを委任するたびにバーンされます。デリゲーターが委任されたGRTを撤回する場合、デリゲーターは28エポックのアンボンド期間を待つ必要があります。各エポックは6,646ブロックであり、28エポックは約26日間になります。
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-これを読んでいる方は、[ネットワーク参加者ページ](https://thegraph.com/explorer/participants/indexers)にアクセスして、GRTを自分の選んだインデクサーに委任することで、今すぐデリゲーターになることができるのです。
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## キュレーター (GRT を獲得)
+## Curators (Earn GRT)
 
-キュレーターは、高品質のサブグラフを特定し、それを「キュレーション」（GRTシグナルを送ること）することで、そのサブグラフから将来発生する全てのクエリ料の一定割合を保証するキュレーションシェアを獲得します。独立したネットワーク参加者であれば誰でもキュレーターになることができますが、通常、サブグラフの開発者は、自分のサブグラフがインデックスされることを保証したいため、自分のサブグラフの最初のキュレーターの一人になります。
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-キュレーターは、新しいサブグラフをキュレーションするときに1%のキュレーション税を支払います。このキュレーション税はバーンされ、GRTの供給量を減少させます。
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## 開発者
+## Developers
 
-ディベロッパーは、ブロックチェーンのデータを取得するためにサブグラフを構築し、クエリを実行します。サブグラフはオープンソースであるため、ディベロッパーは既存のサブグラフに問い合わせを行い、ブロックチェーンのデータを自分のDappsにロードすることができます。ディベロッパーは、クエリを実行する際に、ネットワーク参加者に配布されるGRTで支払いを行う
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### サブグラフの作成
 
-ディベロッパーは[サブグラフ](/developing/creating-a-subgraph/)を作成し、ブロックチェーン上のデータをインデックス化することができます。サブグラフは、どのデータをコンシューマーに提供すべきかについて、インデクサーに指示するものです。
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-サブグラフの構築とテストが完了したら、開発者は[The Graphの分散型ネットワークでサブグラフを公開することができます](/publishing/publishing-a-subgraph/)。
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### 既存のサブグラフのクエリ
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-サブグラフは[GraphQL](/querying/querying-the-graph/)でクエリされ、クエリ料は[Subgraph Studio](https://thegraph.com/studio/)でGRTで支払われます。クエリ料は、プロトコルへの貢献度に応じてネットワーク参加者に分配されます。
-
-ネットワークに支払われるクエリーフィーの1％がバーンされます。
-
-## インデクサー (GRT を獲得)
-
-インデクサーは、The Graphのバックボーンです。彼らは、The Graphの分散型ネットワークを支える独立したハードウェアとソフトウェアを操作しています。インデクサーは、サブグラフからの指示に基づいてコンシューマーにデータを提供します。
-
-インデクサーは、2つの方法でGRT報酬を獲得することができます：
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  クエリ料金：開発者やユーザーがサブグラフデータのクエリに支払うGRTのことです。クエリ料金は、指数的リベート関数に従って直接インデクサーに分配されます（GIPは[こちら](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)を参照）。
+1% of the query fees paid to the network are burned.
 
-2.  インデックス作成報酬：年間3％の発行額は、インデックスを作成しているサブグラフの数に応じて、インデクサーに分配されます。この報酬は、インデクサーのインセンティブとなり、時にはクエリ料が機能する前にサブグラフのインデックスを作成し、データを正確にインデックスしたことを証明するPOI（Proofs of Indexing）を蓄積して提出します。
+## Indexers (Earn GRT)
 
-各サブグラフは、そのサブグラフのキュレーションシグナルの量に基づき、ネットワークトークン発行総額の一部が割り当てられます。そして、その量は、サブグラフに割り当てられたステークに基づき、インデクサーに報酬として支払われます。
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-インデックスノードを運営するために、インデクサーはネットワークに100,000GRT以上の出資をする必要があります。インデクサーは、提供するクエリの量に比例して、GRTをステークするインセンティブを得ます。
+Indexers can earn GRT rewards in two ways:
 
-インデクサーは、デリゲーターからのGRTの委任を受け入れることで、サブグラフ上のGRT割り当てを増やすことができ、最大で初期ステークスの16倍を受け入れることができます。もし、インデクサーが「過剰委任」（つまり、初期出資額の16倍以上）になった場合、ネットワークへの出資額を増やすまで、デリゲーターからの追加GRTを使用することができなくなります。
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-インデクサーが受け取る報酬の量は、最初のステーク、受け入れられた委任、サービスの質、その他多くの要因に基づいて変化する可能性があります。以下のグラフは、The Graphの分散型ネットワーク上でアクティブなインデクサーから公開されたデータです。
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### インデクサーステーク&allnodes-com.ethの報酬
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![インデキシングステークと報酬](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-本データは、2021年2月から2022年9月までのものです。
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> なお、[Arbitrumの移行](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551)が完了すると改善され、ガス代はネットワークに参加するための負担が大幅に軽減されることになります。
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## トークン供給: 燃焼& 発行
+## Token Supply: Burning & Issuance
 
-最初のトークン供給量は100億GRTで、サブグラフにステークを割り当てるIndexerに報いるため、毎年3%の新規発行を目標としています。つまり、GRTトークンの総供給量は、ネットワークへの貢献に対してインデクサーに新しいトークンが発行されることにより、毎年3％ずつ増加することになります。
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-グラフは、新しいトークン発行を相殺するために、複数のバーンメカニズムで設計されています。GRTの供給量の約1%が、ネットワーク上の様々な活動を通じて毎年バーンされ、この数はネットワークの活動が成長し続けるにつれて増加しています。これらのバーン活動には、デリゲーターがGRTをインデクサーに委任するたびに0.5%のデリゲーション税、キュレーターがサブグラフにシグナルを送るときに1%のキュレーション税、ブロックチェーンデータのクエリー料金の1%が含まれます。
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![バーンGRTの合計](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-このような定期的に発生するバーニング活動に加え、GRTトークンには、インデクサーの悪意ある行動や無責任な行動にペナルティを与えるスラッシングの仕組みも用意されています。インデクサーがスラッシングされた場合、そのエポックのインデックス報酬の50％が焼却され（残りの半分は漁師に渡る）、自己ステークは2.5％スラッシングされ、その半分がバーンされます。これにより、インデクサーはネットワークの最善の利益のために行動し、そのセキュリティと安定性に貢献するという強いインセンティブを確保することができます。
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## プロトコルの改善
+## Improving the Protocol
 
-グラフネットワークは常に進化しており、プロトコルの経済的な設計の改善は、すべてのネットワーク参加者に最高の体験を提供するために常に行われています。グラフ評議会はプロトコルの変更を監督し、コミュニティメンバーも参加することが推奨されています。[グラフフォーラム](https://forum.thegraph.com/)で、プロトコルの改良に参加してください。
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From decd68f91e2d638505ed88f96a59b7c947e4c261 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:52 -0500
Subject: [PATCH 0414/1325] New translations tokenomics.mdx (Korean)

---
 website/pages/ko/tokenomics.mdx | 44 ++++++++++++++-------------------
 1 file changed, 18 insertions(+), 26 deletions(-)

diff --git a/website/pages/ko/tokenomics.mdx b/website/pages/ko/tokenomics.mdx
index 6fa9686eec71..e2e4c904000d 100644
--- a/website/pages/ko/tokenomics.mdx
+++ b/website/pages/ko/tokenomics.mdx
@@ -1,21 +1,21 @@
 ---
 title: Tokenomics of The Graph Network
-description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token works.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Overview
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Specifics
 
-It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
 ## The Roles of Network Participants
 
@@ -29,15 +29,15 @@ There are four primary network participants:
 
 4.  Indexers - Backbone of blockchain data
 
-Fishermen and Arbitrators are also integral to the network’s success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
@@ -45,9 +45,9 @@ If you're reading this, you're capable of becoming a Delegator right now by head
 
 ## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
@@ -75,25 +75,17 @@ Indexers are the backbone of The Graph. They operate independent hardware and so
 
 Indexers can earn GRT rewards in two ways:
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-2.  Indexing rewards: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs) verifying that they have indexed data accurately.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
 Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-In order to run an indexing node, Indexers must stake 100,000 GRT or more with the network. Indexers are incentivized to stake GRT in proportion to the amount of queries they serve.
-
-Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial stake), they will not be able to use the additional GRT from Delegators until they increase their stake in the network.
-
-The amount of rewards an Indexer receives can vary based on the initial stake, accepted delegation, quality of service, and many more factors. The following chart is publicly available data from an active Indexer on The Graph's decentralized network.
-
-### The Indexer stake & reward of allnodes-com.eth
-
-![Indexing stake and rewards](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-This data is from February 2021 to September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Please note, this will improve when the [Arbitrum migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) is complete, making gas costs a significantly lower burden for participating on the network.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
 ## Token Supply: Burning & Issuance
 

From 1ca968217205323a4aa32bf2de9318023b91c51c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:53 -0500
Subject: [PATCH 0415/1325] New translations tokenomics.mdx (Dutch)

---
 website/pages/nl/tokenomics.mdx | 44 ++++++++++++++-------------------
 1 file changed, 18 insertions(+), 26 deletions(-)

diff --git a/website/pages/nl/tokenomics.mdx b/website/pages/nl/tokenomics.mdx
index 6fa9686eec71..e2e4c904000d 100644
--- a/website/pages/nl/tokenomics.mdx
+++ b/website/pages/nl/tokenomics.mdx
@@ -1,21 +1,21 @@
 ---
 title: Tokenomics of The Graph Network
-description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token works.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Overview
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Specifics
 
-It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
 ## The Roles of Network Participants
 
@@ -29,15 +29,15 @@ There are four primary network participants:
 
 4.  Indexers - Backbone of blockchain data
 
-Fishermen and Arbitrators are also integral to the network’s success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
@@ -45,9 +45,9 @@ If you're reading this, you're capable of becoming a Delegator right now by head
 
 ## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
@@ -75,25 +75,17 @@ Indexers are the backbone of The Graph. They operate independent hardware and so
 
 Indexers can earn GRT rewards in two ways:
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-2.  Indexing rewards: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs) verifying that they have indexed data accurately.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
 Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-In order to run an indexing node, Indexers must stake 100,000 GRT or more with the network. Indexers are incentivized to stake GRT in proportion to the amount of queries they serve.
-
-Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial stake), they will not be able to use the additional GRT from Delegators until they increase their stake in the network.
-
-The amount of rewards an Indexer receives can vary based on the initial stake, accepted delegation, quality of service, and many more factors. The following chart is publicly available data from an active Indexer on The Graph's decentralized network.
-
-### The Indexer stake & reward of allnodes-com.eth
-
-![Indexing stake and rewards](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-This data is from February 2021 to September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Please note, this will improve when the [Arbitrum migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) is complete, making gas costs a significantly lower burden for participating on the network.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
 ## Token Supply: Burning & Issuance
 

From 6166430ccb9ff8269a44a2137e4a1c5e26463d21 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:54 -0500
Subject: [PATCH 0416/1325] New translations tokenomics.mdx (Polish)

---
 website/pages/pl/tokenomics.mdx | 44 ++++++++++++++-------------------
 1 file changed, 18 insertions(+), 26 deletions(-)

diff --git a/website/pages/pl/tokenomics.mdx b/website/pages/pl/tokenomics.mdx
index 6fa9686eec71..e2e4c904000d 100644
--- a/website/pages/pl/tokenomics.mdx
+++ b/website/pages/pl/tokenomics.mdx
@@ -1,21 +1,21 @@
 ---
 title: Tokenomics of The Graph Network
-description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token works.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Overview
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Specifics
 
-It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
 ## The Roles of Network Participants
 
@@ -29,15 +29,15 @@ There are four primary network participants:
 
 4.  Indexers - Backbone of blockchain data
 
-Fishermen and Arbitrators are also integral to the network’s success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
@@ -45,9 +45,9 @@ If you're reading this, you're capable of becoming a Delegator right now by head
 
 ## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
@@ -75,25 +75,17 @@ Indexers are the backbone of The Graph. They operate independent hardware and so
 
 Indexers can earn GRT rewards in two ways:
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-2.  Indexing rewards: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs) verifying that they have indexed data accurately.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
 Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-In order to run an indexing node, Indexers must stake 100,000 GRT or more with the network. Indexers are incentivized to stake GRT in proportion to the amount of queries they serve.
-
-Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial stake), they will not be able to use the additional GRT from Delegators until they increase their stake in the network.
-
-The amount of rewards an Indexer receives can vary based on the initial stake, accepted delegation, quality of service, and many more factors. The following chart is publicly available data from an active Indexer on The Graph's decentralized network.
-
-### The Indexer stake & reward of allnodes-com.eth
-
-![Indexing stake and rewards](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-This data is from February 2021 to September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Please note, this will improve when the [Arbitrum migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) is complete, making gas costs a significantly lower burden for participating on the network.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
 ## Token Supply: Burning & Issuance
 

From 325d2d0cad041fd1d0043317d14de897ac7bf40b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:55 -0500
Subject: [PATCH 0417/1325] New translations tokenomics.mdx (Portuguese)

---
 website/pages/pt/tokenomics.mdx | 96 +++++++++++++++------------------
 1 file changed, 44 insertions(+), 52 deletions(-)

diff --git a/website/pages/pt/tokenomics.mdx b/website/pages/pt/tokenomics.mdx
index f75afc1bd1cc..9b7888bda8b9 100644
--- a/website/pages/pt/tokenomics.mdx
+++ b/website/pages/pt/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Tokenomia da Graph Network
-description: A Graph Network é incentivada por uma tokenomia (economia de token) poderosa. Aqui está como funciona o GRT, o token nativo de utilidades de trabalho no The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- Endereço do Token GRT na Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Visão geral
 
-- Endereço do Token GRT no Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-O The Graph é um protocolo descentralizado que permite o acesso fácil a dados de blockchain.
+## Especificações
 
-É parecido com um modelo B2B2C, mas movido por uma rede descentralizada de participantes, que trabalham juntos para fornecer dados a utilizadores finais em troca de recompensas em GRT. O GRT é o token de utilidade que coordena provedores e consumidores de dados. O GRT serve como utilidade para a coordenação de provedores e consumidores de dados dentro da rede, e incentiva os participantes do protocolo a organizarem dados com eficácia.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-Ao usar o The Graph, os utilizadores podem acessar dados da blockchain com facilidade e pagar apenas pelas informações de que precisam. O The Graph é usado por vários [dApps populares](https://thegraph.com/explorer) no ecossistema web3 hoje.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-O The Graph indexa dados de blockchain de forma parecida com a indexação da web pelo Google. De fato, pode já estar a usar o The Graph sem perceber. Se viu o frontend de um dApp que ganha os seus dados de um subgraph, já fez um query para dados de um subgraph!
+- Endereço do Token GRT na Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-O The Graph tem um papel muito importante em aumentar a acessibilidade de dados de blockchain e ativar um mercado para a sua troca.
+- Endereço do Token GRT no Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Os Papeis dos Participantes na Rede
+## The Roles of Network Participants
 
-Há quatro participantes primários na rede:
+There are four primary network participants:
 
 1.  Delegantes — Delegam GRT aos Indexers & protegem a rede
 
@@ -29,82 +29,74 @@ Há quatro participantes primários na rede:
 
 4.  Indexadores — Rede de transporte de dados em blockchain
 
-Pescadores e Árbitros também são integrais ao êxito da rede através de outras contribuições, com o seu apoio ao trabalho dos outros papéis participantes primários. Para saber mais sobre papéis na rede, [leia este artigo](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Diagrama de tokenomia](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegantes (Ganham GRT passivamente)
+## Delegators (Passively earn GRT)
 
-Os Delegantes delegam GRT a Indexadores, aumentando o stake do Indexador em subgraphs na rede. Em troca, ganham uma porcentagem de todas as taxas de query e recompensas de indexação do Indexador. Cada Indexador determina a porção que será recompensada aos Delegantes de forma independente, criando competição entre Indexadores para atrair Delegantes. Muitos Indexadores oferecem entre 9 e 12% ao ano.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Por exemplo, se um Delegante delegasse 15.000 GRT a um Indexador que oferecesse 10%, o Delegante receberia cerca de 1.500 GRT em recompensas por ano.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Há uma taxa de 0.% de delegação, queimada quando um Delegante delega GRT na rede. Se um Delegante escolher sacar o GRT que delegou, o Delegante deve esperar o período de desligamento de 28 epochs. Cada epoch dura 6.646 blocos, o que significa que 28 blocos duram, em média, 26 dias.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Quem ler isto pode tornar-se um Delegante agora mesmo na [página de participantes da rede](https://thegraph.com/explorer/participants/indexers), e começar a delegar GRT a um Indexador da sua escolha.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Curadores (Ganham GRT)
+## Curators (Earn GRT)
 
-Os Curadores identificam subgraphs de alta qualidade e os "curam" (por ex., sinalizam GRT neles) para ganhar ações de curadoria, que garantem uma porção de todas as taxas de query futuras geradas pelo subgraph. Enquanto qualquer participante independente da rede pode ser um Curador, os programadores de subgraphs tendem a ser os primeiros Curadores dos seus próprios subgraphs, pois querem garantir que o seu subgraph seja indexado.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-Desde 11 de abril de 2024, os programadores de subgraphs podem curar o seu subgraph com, no mínimo, 3.000 GRT. Porém, este número pode ser impactado pela atividade na rede e participação na comunidade.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Os Curadores pagam uma taxa de curadoria de 1% ao curar um subgraph novo. Esta taxa de curadoria é queimada, de modo a reduzir a reserva de GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Programadores
+## Developers
 
-Os programadores constroem e fazem queries em subgraphs para retirar dados da blockchain. Como os subgraphs têm o código aberto, os programadores podem carregar dados da blockchain em seus dApps com queries nos subgraphs existentes. Os programadores pagam por queries feitos em GRT, que é distribuído aos participantes da rede.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Como criar um Subgraph
 
-Para indexar dados na blockchain, os programadores podem [criar um subgraph](/developing/creating-a-subgraph/) — um conjunto de instruções para Indexadores sobre quais dados devem ser servidos aos consumidores.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Quando os programadores tiverem construído e testado o seu subgraph, eles podem [editar o seu subgraph](/publishing/publishing-a-subgraph/) na rede descentralizada do The Graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Como fazer queries um Subgraph existente
 
-Quando um subgraph é [editado](/publishing/publishing-a-subgraph/) na rede descentralizada do The Graph, qualquer um pode criar uma chave API, depositar GRT no seu saldo de cobrança, e consultar o subgraph em um query.
-
-Os Subgraphs recebem [queries pelo GraphQL](/querying/querying-the-graph/), e as taxas de query são pagas em GRT no [Subgraph Studio](https://thegraph.com/studio/). As taxas de query são distribuídas a participantes da rede com base nas suas contribuições ao protocolo.
-
-1% das taxas de query pagas à rede é queimado.
-
-## Indexadores (Ganham GRT)
-
-Os Indexadores são o núcleo do The Graph; operam o equipamento e o software independentes que movem a rede descentralizada do The Graph. Eles servem dados a consumidores baseado em instruções de subgraphs.
+Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Os Indexadores podem ganhar recompensas em GRT de duas maneiras:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Taxas de query: GRT pago, por programadores ou utilizadores, para queries de dados de subgraph. Taxas de query são distribuídas diretamente a Indexadores conforme a função de rebate exponencial (veja o GIP [aqui](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Recompensas de indexação: a emissão anual de 3% é distribuída aos Indexadores com base no número de subgraphs que indexam. Estas recompensas os incentivam a indexar subgraphs, às vezes antes das taxas de query começarem, de modo a acumular e enviar Provas de Indexação (POIs) que verificam que indexaram dados corretamente.
+## Indexers (Earn GRT)
 
-Cada subgraph recebe uma porção da emissão total do token na rede, com base na quantia do sinal de curadoria do subgraph. Essa quantia é então recompensada aos Indexadores com base no seu stake alocado no subgraph.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Para executar um node de indexação, os Indexadores devem fazer um stake de 100.000 GRT ou mais com a rede. Os mesmos são incentivados a fazer um stake de GRT, proporcional à quantidade de queries que servem.
+Indexers can earn GRT rewards in two ways:
 
-Os Indexadores podem aumentar suas alocações de GRT nos subgraphs, ao aceitar delegações de GRT de Delegantes; tamném podem aceitar até 16 vezes a quantia do seu stake inicial. Se um Indexador se tornar "excessivamente delegado" (por ex., com seu stake inicial multiplicado mais de 16 vezes), ele não poderá usar o GRT adicional dos Delegantes até aumentar o seu próprio stake na rede.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-O montante de recompensas que um Indexador recebe pode variar com base no stake inicial, delegação aceita, qualidade do serviço, e vários outros fatores. O seguinte gráfico mostra dados públicos de um Indexador ativo na rede descentralizada do The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### O stake & recompensa de um Indexador do allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Stake e recompensas de indexação](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Os dados são de fevereiro de 2021 até setembro de 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Perceba que isto melhorará quando a [migração ao Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) for completa, de modo a reduzir drasticamente os custos de gas por participar na rede.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Reserva de Tokens: Queima & Emissão
+## Token Supply: Burning & Issuance
 
-A reserva inicial de tokens é de 10 bilhões de GRT, com um alvo de emissão de 3% novos ao ano para recompensar os Indexadores por alocar stake em subgraphs. Portanto, a reserva total de tokens GRT aumentará por 3% a cada ano à medida que tokens novos são emitidos para Indexadores, pela sua contribuição à rede.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-O The Graph é projetado com vários mecanismos de queima para compensar pela emissão de novos tokens. Aproximadamente 1% da reserva de GRT é queimado todo ano, através de várias atividades na rede, e este número só aumenta conforme a atividade na rede cresce. Estas atividades de queima incluem: uma taxa de delegação de 0.5% sempre que um Delegante delega GRT a um Indexador; uma taxa de curadoria de 1% quando Curadores sinalizam em um subgraph; e 1% de taxas de query por dados de blockchain.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Total de GRT queimado](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-Além destas atividades recorrentes de queima, o token GRT também tem um mecanismo de corte para penalizar comportamentos maliciosos ou irresponsáveis pelos Indexadores. Se um Indexador for cortado, é queimado 50% das suas recompensas de indexação no epoch (e a outra metade vai ao pescador); e o seu auto-stake é cortado em 2.5%, com metade desta quantidade queimada. Isto ajuda a garantir que os Indexadores tenham um forte incentivo a agir nos melhores interesses da rede e contribuir à sua segurança e estabilidade.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Como Aprimorar o Protocolo
+## Improving the Protocol
 
-A Graph Network está sempre a evoluir, e o projeto económico do protocolo está sempre a melhorar, de modo a entregar a melhor experiência para todos os participantes da rede. O Graph Council (Conselho do Graph) supervisa as mudanças no protocolo e os membros da comunidade estão convidados para participar. Ajude a melhorar o protocolo no [Fórum do The Graph](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From c48a402ba11ccd2882deb4e36de63316bf45a7d7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:56 -0500
Subject: [PATCH 0418/1325] New translations tokenomics.mdx (Russian)

---
 website/pages/ru/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/ru/tokenomics.mdx b/website/pages/ru/tokenomics.mdx
index d863f7c30612..c5c854d49ffe 100644
--- a/website/pages/ru/tokenomics.mdx
+++ b/website/pages/ru/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Токеномика сети The Graph
-description: Сеть The Graph стимулируется мощной токеномикой. Вот как работает GRT, нативный токен The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Обзор
 
-- Адрес токена GRT в сети Arbitrum One [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph - это децентрализованный протокол, который обеспечивает легкий доступ к данным блокчейна.
+## Специфические особенности
 
-Это похоже на модель B2B2C, за исключением того, что она основана на децентрализованной сети участников. Участники сети работают сообща, предоставляя данные конечным пользователям в обмен на вознаграждение в GRT. GRT - это токен рабочей утилиты, который координирует поставщиков данных и потребителей. Токен GRT служит средством координации поставщиков и потребителей данных в сети и стимулирует участников протокола к эффективной организации данных.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph индексирует данные блокчейна так же, как Google индексирует данные в интернете. Что интересно, Вы даже, возможно, уже пользовались The Graph, просто Вы этого не знаете. Если Вы взглянете на Front End dapp и увидите там subgraph, знайте - Вы получаете данные благодаря The Graph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph играет решающую роль в том, чтобы сделать данные блокчейна более доступными и создать площадку для их обмена.
+- Адрес токена GRT в сети Arbitrum One [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Роли участников сети
+## The Roles of Network Participants
 
-Есть четыре основных участника сети:
+There are four primary network participants:
 
 1.  Делегаторы - Делегируют токены GRT Индексерам & защищают сеть
 
@@ -29,82 +29,74 @@ The Graph играет решающую роль в том, чтобы сдел
 
 4.  Индексаторы - Магистральный канал передачи данных блокчейна
 
-Рыбаки и Арбитры также являются неотъемлемой частью успеха сети благодаря другим вкладам, поддерживающим работу других основных ролей участников. Подробнее о сетевых ролях читайте в [этой статье](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Диаграмма токеномики](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Делегаторы (Возможность пассивного дохода в GRT)
+## Delegators (Passively earn GRT)
 
-Делегаторы делегируют Индексаторам GRT, увеличивая стейк Индексатора в субграфах в сети. Взамен Делегаторы получают процент от всех сборов за запросы и вознаграждения за индексирование от Индексатора. Каждый Индексатор самостоятельно устанавливает размер вознаграждения для Делегаторов, что создает конкуренцию между Индексаторами за привлечение Делегаторов. Большинство Индексаторов предлагают от 9 до 12% годовых.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Например, если бы Делегатор делегировал 15 тыс. GRT Индексатору, предлагающему 10%, Делегатор получал бы вознаграждение в размере ~ 1500 GRT в год.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Существует комиссия на делегирование в размере 0,5%, которая взимается всякий раз, когда Делегатор делегирует GRT в сети. Если Делегатор решает отозвать свои делегированные GRT, он должен подождать 28-эпох, которые занимают период отмены делегирования. Каждая эпоха состоит из 6646 блоков, что означает, что 28 эпох в конечном итоге составляют приблизительно 26 дней.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Если Вы читаете это, Вы можете стать Делегатором прямо сейчас, перейдя на [страницу участников сети](https://thegraph.com/explorer/participants/indexers) и делегировав GRT Индексатору по Вашему выбору.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Кураторы (Заработок GRT)
+## Curators (Earn GRT)
 
-Кураторы определяют высококачественные субграфы и "курируют" их (т. е. сигнализируют о них GRT), чтобы получать комиссии кураторства, которые гарантируют процент от всех будущих сборов за запросы, сгенерированные субграфом. В то время как Куратором может быть любой независимый участник сети, обычно разработчики субграфов являются одними из первых Кураторов своих собственных субграфов, потому что они хотят убедиться, что их субграф проиндексирован.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Кураторы платят комиссию за кураторство в размере 1%, когда они курируют новый субграф. Эта комиссия сжигается, уменьшая предложение GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Разработчики
+## Developers
 
-Разработчики создают и запрашивают субграфы для получения данных блокчейна. Поскольку субграфы имеют открытый исходный код, разработчики могут делать запросы к существующим субграфам, чтобы загрузить данные блокчейна в свои dapps. Разработчики платят за запросы, которые они выполняют, в GRT, распределяемых среди участников сети.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Создание субграфа
 
-Разработчики могут [создать субграф](/developing/creating-a-subgraph/) для индексации данных в блокчейне. Субграфы - это инструкции для индексаторов о том, какие данные должны предоставляться потребителям.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-После того как разработчики создали и протестировали свой субграф, они могут [ опубликовать его](/publishing/publishing-a-subgraph/) в децентрализованной сети The Graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Запрос к существующему субграфу
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Субграфы [запрашиваются с помощью GraphQL](/querying/querying-the-graph/), а плата за запрос производится с помощью GRT в [Subgraph Studio](https://thegraph.com/studio/). Плата за запрос распределяется между участниками сети на основе их вклада в протокол.
-
-1% от платы за запрос, выплаченной в сети, сжигается.
-
-## Индексаторы (Заработок GRT)
-
-Индексаторы являются основой сети The Graph. Они управляют независимым аппаратным и программным обеспечением, питающим децентрализованную сеть The Graph. Индексаторы предоставляют данные потребителям на основе инструкций из субграфов.
-
-Индексаторы могут зарабатывать GRT двумя путями:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Плата за запросы: GRT, выплачиваемая разработчиками или пользователями за запросы данных субграфа. Плата за запрос напрямую распределяется между индексаторами в соответствии с экспоненциальной функцией скидки (см. GIP [здесь](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Вознаграждения за индексирование: ежегодная эмиссия в размере 3% распределяется между Индексаторами в зависимости от количества индексируемых ими субграфов. Эти вознаграждения стимулируют Индексаторов индексировать субграфы, иногда до начала сборов за запросы, чтобы накопить и отправить доказательства индексирования (POI), подтверждающие, что они точно проиндексировали данные.
+## Indexers (Earn GRT)
 
-Каждому субграфу выделяется часть общей эмиссии сетевых токенов, основанная на количестве сигналов курирования субграфа. Затем эта сумма присуждается индексаторам на основе их выделенного стейка на субграфе.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Чтобы запустить индексаторскую ноду, Индексаторы должны застейкать в сети 100 000 GRT или более. Индексаторы заинтересованы в том, чтобы делать ставки GRT пропорционально количеству запросов, которые они обслуживают.
+Indexers can earn GRT rewards in two ways:
 
-Индексаторы могут увеличить свои аллокации GRT на субграфах, приняв делегации GRT от Делегаторов, при этом они могут принять в 16 раз больше своей первоначальной ставки. Если Индексатор становится "чрезмерно делегированным" (т.е. более чем в 16 раз превышает свою первоначальную сумму стейка), он не сможет использовать дополнительные токены GRT от Делегаторов, пока не увеличит свою долю в сети.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-Размер вознаграждений, которые получает Индексатор, может варьироваться в зависимости от первоначального стейка, полученного делегирования, качества обслуживания и многих других факторов. На следующей диаграмме представлены общедоступные данные активного Индексатора в децентрализованной сети The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### Стейк Индексатора & вознаграждение allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Индексация ставок и вознаграждения](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Эти данные относятся к периоду с февраля 2021 по сентябрь 2022 года.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Пожалуйста, обратите внимание на то, что после завершения миграции [Arbitrum'а](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) произойдут улучшения, которые приведут к значительному снижению затрат на газ для участия в сети.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Запас токенов: Сжигание & Эмиссия
+## Token Supply: Burning & Issuance
 
-Первоначальное предложение токенов составляет 10 миллиардов GRT, с целью ежегодного выпуска 3% новых токенов для вознаграждения Индексаторов за распределение стейка на субграфах. Это означает, что общий объем токенов GRT будет увеличиваться на 3% каждый год по мере того, как Индексаторам будут выдаваться новые токены за их вклад в сеть.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graph разработан с использованием нескольких механизмов сжигания токенов, чтобы компенсировать выпуск новых токенов. Примерно 1% от общего объема GRT ежегодно сжигается в результате различных действий в сети, и это число увеличивается по мере того, как сетевая активность продолжает расти. Эти текущие действия включают комиссию на делегирование в размере 0,5% всякий раз, когда Делегатор делегирует GRT Индексатору, комиссию на кураторство в размере 1%, когда Кураторы сигнализируют о субграфе, и плату за запрос данных блокчейна в размере 1%.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Количество сожженных GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-В дополнение к этим регулярно происходящим действиям по сжиганию токенов, токен GRT также имеет механизм слэшинга для наказания за злонамеренное или безответственное поведение Индексаторов. Если Индексатор заслэшен, 50% его вознаграждения за индексацию за эпоху сжигается (в то время как другая половина достается Рыбаку), а его собственная сумма стейка уменьшается на 2,5%, причем половина этой суммы сгорает. Это помогает гарантировать, что у Индексаторов есть сильный стимул действовать в наилучших интересах сети и вносить свой вклад в ее безопасность и стабильность.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Улучшение протокола
+## Improving the Protocol
 
-Сеть The Graph постоянно развивается, и постоянно вносятся улучшения в экономический дизайн протокола, чтобы обеспечить наилучший опыт для всех участников сети. The Graph Council следит за изменениями протокола, и членам сообщества рекомендуется в этом участвовать. Участвуйте в улучшении протокола на [форуме The Graph](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 56373d6bfee6818582c5edfa4525be4f17f3eac5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:57 -0500
Subject: [PATCH 0419/1325] New translations tokenomics.mdx (Swedish)

---
 website/pages/sv/tokenomics.mdx | 92 +++++++++++++++------------------
 1 file changed, 42 insertions(+), 50 deletions(-)

diff --git a/website/pages/sv/tokenomics.mdx b/website/pages/sv/tokenomics.mdx
index e7b62371e367..b85a99fa6693 100644
--- a/website/pages/sv/tokenomics.mdx
+++ b/website/pages/sv/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Tokenomics för The Graf Nätverk
-description: The Graf Nätverk drivs av kraftfull tokenomics. Här är hur GRT, The Grafs nativa arbetsnyttighets-token, fungerar.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Översikt
 
-- GRT Tokenadress på Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graf är en decentraliserad protokoll som möjliggör enkel åtkomst till blockkedjedata.
+## Specifics
 
-Det liknar en B2B2C-modell, förutom att den drivs av ett decentraliserat nätverk av deltagare. Nätverksdeltagare samarbetar för att tillhandahålla data till slutanvändare i utbyte mot GRT-belöningar. GRT är arbetsnyttighetstoken som samordnar dataleverantörer och konsumenter. GRT fungerar som en nytta för att samordna dataleverantörer och konsumenter inom nätverket och stimulerar protokolldeltagare att organisera data effektivt.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexerar blockkedjedata på ett liknande sätt som Google indexerar webben. Faktum är att du kanske redan använder The Graph utan att inse det. Om du har sett framsidan av en dapp som får sina data från en subgraf, har du frågat data från en subgraf!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph spelar en avgörande roll för att göra blockkedjedata mer tillgängligt och möjliggöra en marknad för dess utbyte.
+- GRT Tokenadress på Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Nätverksdeltagarnas Roller
+## The Roles of Network Participants
 
-Det finns fyra primära nätverksdeltagare:
+There are four primary network participants:
 
 1.  Delegater - Delegera GRT till Indexers & säkra nätverket
 
@@ -29,82 +29,74 @@ Det finns fyra primära nätverksdeltagare:
 
 4.  Indexers - Grundvalen för blockkedjedata
 
-Fiskare och Skiljedomare är också integrerade för nätverkets framgång genom andra bidrag, och de stöder arbetet för de andra primära deltagarrollerna. För mer information om nätverksroller, [läs den här artikeln](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegater (Passivt tjäna GRT)
+## Delegators (Passively earn GRT)
 
-Indexers delegeras GRT av Delegater som ökar Indexers insats i subgrafter på nätverket. Som ett resultat tjänar Delegater en procentandel av alla frågeavgifter och indexbelöningar från Indexer. Varje Indexer ställer in den andel som kommer att belönas till Delegater oberoende, vilket skapar konkurrens mellan Indexers för att locka Delegater. De flesta Indexers erbjuder mellan 9-12% årligen.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-Till exempel, om en Delegat skulle delegera 15k GRT till en Indexer som erbjuder 10%, skulle Delegaten få ~1500 GRT i belöningar årligen.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Det finns en delegatskatt på 0,5% som bränns när en Delegat delegerar GRT på nätverket. Om en Delegat väljer att dra tillbaka sitt delegerade GRT måste Delegaten vänta på en 28-epoch obundenhetsperiod. Varje epoch är 6,646 block, vilket innebär att 28 epocher slutar vara ungefär 26 dagar.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Om du läser detta kan du bli en Delegat just nu genom att gå till [nätverksdeltagar-sidan](https://thegraph.com/explorer/participants/indexers) och delegera GRT till en Indexer av ditt val.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Kuratorer (Tjäna GRT)
+## Curators (Earn GRT)
 
-Kuratorer identifierar högkvalitativa subgrafter och "kuraterar" dem (dvs. signalerar GRT på dem) för att tjäna andelar av kurering, vilket garanterar en procentandel av alla framtida frågeavgifter som genereras av subgrafen. Även om vilken oberoende nätverksdeltagare som helst kan vara en Kurator är det vanligtvis subgrafsutvecklare som först blir Kuratorer för sina egna subgrafter eftersom de vill se till att deras subgraf indexerades.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Kuratorer betalar en kuratorskatt på 1% när de kurar en ny subgraf. Denna kuratorskatt bränns och minskar tillgången på GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Utvecklare
+## Developers
 
-Utvecklare bygger och frågar subgrafter för att hämta blockkedjedata. Eftersom subgrafter är öppen källkod kan utvecklare fråga befintliga subgrafter för att ladda blockkedjedata i sina dappar. Utvecklare betalar för de frågor de gör med GRT, som distribueras till nätverksdeltagare.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Skapa en subgraf
 
-Utvecklare kan [skapa en subgraf](/developing/creating-a-subgraph/) för att indexera data på blockkedjan. Subgrafer är instruktioner för Indexers om vilka data som ska serveras till konsumenter.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-När utvecklare har byggt och testat sin subgraf kan de [publicera sin subgraf](/publishing/publishing-a-subgraph/) på The Graphs decentraliserade nätverk.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Fråga en befintlig subgraf
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Subgrafter [frågas med GraphQL](/querying/querying-the-graph/) och frågeavgifterna betalas med GRT i [Subgraf Studio](https://thegraph.com/studio/). Frågeavgifterna distribueras till nätverksdeltagare baserat på deras bidrag till protokollet.
-
-1% av frågeavgifterna som betalas till nätverket bränns.
-
-## Indexers (Tjäna GRT)
-
-Indexers är grundvalen för The Graf. De driver oberoende maskinvara och programvara som driver The Graphs decentraliserade nätverk. Indexers serverar data till konsumenter baserat på instruktioner från subgrafter.
-
-Indexers kan tjäna GRT-belöningar på två sätt:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Frågeavgifter: GRT som betalas av utvecklare eller användare för frågor om subgrafsdata. Frågeavgifter distribueras direkt till Indexers enligt den exponentiella rabattfunktionen (se GIP [här](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  Indexeringsbelöningar: den årliga utfärdandet på 3% distribueras till Indexers baserat på antalet subgrafter de indexerar. Dessa belöningar stimulerar Indexers att indexera subgrafter, ibland innan frågeavgifterna börjar, för att ackumulera och skicka in indexbevis (POIs) som verifierar att de har indexerat data korrekt.
+## Indexers (Earn GRT)
 
-Varje subgraf tilldelas en del av den totala nätverkets tokenutfärdandet, baserat på subgrafens kureringssignal. Den mängden belönas sedan till Indexers baserat på deras tilldelade insats på subgrafen.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-För att köra en indexeringsnod måste Indexers satsa 100 000 GRT eller mer med nätverket. Indexers stimuleras att satsa GRT i proportion till antalet frågor de utför.
+Indexers can earn GRT rewards in two ways:
 
-Indexers kan öka sina GRT-tilldelningar på subgrafter genom att acceptera GRT-delegering från Delegater, och de kan acceptera upp till 16 gånger sin ursprungliga insats. Om en Indexer blir "överdelegerad" (dvs. mer än 16 gånger sin ursprungliga insats) kommer de inte att kunna använda det extra GRT från Delegater tills de ökar sin insats i nätverket.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-Mängden belöningar som en Indexer får kan variera beroende på ursprunglig insats, accepterad delegering, kvalitet på tjänst och många andra faktorer. Följande diagram är offentlig tillgänglig data från en aktiv Indexer på The Graphs decentraliserade nätverk.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### Indexerns insats & belöning för allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Indexeringsinsats och belöning](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Denna data är från februari 2021 till september 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Observera att detta kommer att förbättras när [Arbitrum-migrationen](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) är klar och gör gasavgifter till en betydligt lägre börda för deltagande i nätverket.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Tokensupply: Bränning och Utfärdande
+## Token Supply: Burning & Issuance
 
-Den ursprungliga tokensupplyn är 10 miljarder GRT, med en målsättning om 3% ny utfärdande årligen för att belöna Indexers för att tilldela insats på subgrafter. Detta innebär att den totala tokensupplyn för GRT kommer att öka med 3% varje år när nya token utfärdas till Indexers för deras bidrag till nätverket.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graf är utformad med flera brännmekanismer för att motverka ny tokensutfärdande. Ungefär 1% av GRT-tillgången bränns årligen genom olika aktiviteter på nätverket, och detta nummer har ökat när nätverksaktiviteten fortsätter att växa. Dessa brännaktiviteter inkluderar en 0,5% delegatsskatt när en Delegat delegerar GRT till en Indexer, en 1% kuratorskatt när Kuratorer signalerar på en subgraf, och 1% av frågeavgifterna för blockkedjedata.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Totalt brända GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-Utöver dessa regelbundet förekommande brännaktiviteter har GRT-tokens också en mekanism för att straffa skadligt eller ansvarslöst beteende av Indexers. Om en Indexer straffas bränns 50% av deras indexeringsbelöningar för epoken (medan den andra halvan går till fiskaren), och deras självinsats straffas med 2,5%, varav hälften bränns. Detta hjälper till att säkerställa att Indexers har ett starkt incitament att agera i nätverkets bästa intresse och bidra till dess säkerhet och stabilitet.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Förbättring av Protokollet
+## Improving the Protocol
 
-The Graph Nätverk utvecklas ständigt och förbättringar av protokollets ekonomiska design görs kontinuerligt för att ge den bästa upplevelsen för alla nätverksdeltagare. The Graph-rådet övervakar protokolländringar och samhällsmedlemmar uppmanas att delta. Delta i förbättringar av protokollet i [The Graph Forum](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From abbf60a4b4b5cbc2312bb685b3e486f6567e01fa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:38:59 -0500
Subject: [PATCH 0420/1325] New translations tokenomics.mdx (Turkish)

---
 website/pages/tr/tokenomics.mdx | 58 ++++++++++++++-------------------
 1 file changed, 25 insertions(+), 33 deletions(-)

diff --git a/website/pages/tr/tokenomics.mdx b/website/pages/tr/tokenomics.mdx
index 1e5fbb1e0f39..1ac77ce1c85d 100644
--- a/website/pages/tr/tokenomics.mdx
+++ b/website/pages/tr/tokenomics.mdx
@@ -1,23 +1,23 @@
 ---
 title: Tokenomics of The Graph Network
-description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token works.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Genel Bakış
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Ayrıntılar
 
-It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## Ağ Katılımcılarının Rolleri
+## The Roles of Network Participants
 
 There are four primary network participants:
 
@@ -29,29 +29,29 @@ There are four primary network participants:
 
 4.  Indexers - Backbone of blockchain data
 
-Fishermen and Arbitrators are also integral to the network’s success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## Delegeler (Pasif olarak GRT kazanırlar)
+## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
 If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## Küratörler (GRT Kazanırlar)
+## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## Geliştiriciler
+## Developers
 
 Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
@@ -69,33 +69,25 @@ Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the qu
 
 1% of the query fees paid to the network are burned.
 
-## İndeksleyiciler (GRT Kazanırlar)
+## Indexers (Earn GRT)
 
 Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
 Indexers can earn GRT rewards in two ways:
 
-1.  Sorgu ücretleri: Subgraph veri sorguları için geliştiriciler veya kullanıcılar tarafından ödenen GRT'dir. Sorgu ücretleri, üstel indirim fonksiyonuna göre doğrudan İndeksleyicilere dağıtılır ([buradan](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162) GIP'e ulaşın).
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-2.  Indexing rewards: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs) verifying that they have indexed data accurately.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
 Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-In order to run an indexing node, Indexers must stake 100,000 GRT or more with the network. Indexers are incentivized to stake GRT in proportion to the amount of queries they serve.
-
-Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial stake), they will not be able to use the additional GRT from Delegators until they increase their stake in the network.
-
-The amount of rewards an Indexer receives can vary based on the initial stake, accepted delegation, quality of service, and many more factors. The following chart is publicly available data from an active Indexer on The Graph's decentralized network.
-
-### allnodes-com.eth'nin İndeksleyici stake ve ödülü
-
-![Indexing stake and rewards](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-This data is from February 2021 to September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Please note, this will improve when the [Arbitrum migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) is complete, making gas costs a significantly lower burden for participating on the network.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## Token Arzı: Yakma & İhraç
+## Token Supply: Burning & Issuance
 
 The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
@@ -105,6 +97,6 @@ The Graph is designed with multiple burning mechanisms to offset new token issua
 
 In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## Protokolün Geliştirilmesi
+## Improving the Protocol
 
 The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 6abcde7d200e242d076936b33fcf5779bb8852d9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:00 -0500
Subject: [PATCH 0421/1325] New translations tokenomics.mdx (Ukrainian)

---
 website/pages/uk/tokenomics.mdx | 80 +++++++++++++++------------------
 1 file changed, 36 insertions(+), 44 deletions(-)

diff --git a/website/pages/uk/tokenomics.mdx b/website/pages/uk/tokenomics.mdx
index 0720187917e8..cc8be5788483 100644
--- a/website/pages/uk/tokenomics.mdx
+++ b/website/pages/uk/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Токеноміка мережі The Graph
-description: Мережа The Graph стимулюється потужною токеномікою. Ось як працює GRT, нативний токен мережі The Graph.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Overview
 
-- Адреса GRT токена в мережі Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-Graph - це децентралізований протокол, який забезпечує легкий доступ до даних блокчейну.
+## Specifics
 
-Це схоже на модель B2B2C, за винятком того, що вона працює на основі децентралізованої мережі користувачів. Користувачі мережі працюють разом, щоб надавати дані кінцевим користувачам в обмін на винагороду в токенах GRT. GRT - це робочий ютіліті токен, який координує постачальників і споживачів даних. GRT дає можливість для координації постачальників і споживачів даних у мережі та стимулює учасників протоколу до ефективної організації даних.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph індексує дані блокчейну подібно до того, як Google індексує дані в інтернеті. Мало того, ви вже могли використовувати The Graph, навіть не розуміючи цього. Якщо ви розглядали інтерфейс децентралізованого застосунку, який отримує дані з підграфа, то ви автоматично зробили запит на дані з підграфа!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph відіграє вирішальну роль у забезпеченні більшої доступності блокчейн-даних та створенні торгової платформи для їх обміну.
+- Адреса GRT токена в мережі Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
 ## The Roles of Network Participants
 
-Наразі є чотири основних учасники мережі:
+There are four primary network participants:
 
 1.  Делегати - делегують токен GRT індексаторам & забезпечують захист мережі
 
@@ -29,82 +29,74 @@ The Graph відіграє вирішальну роль у забезпечен
 
 4.  Індексатори - кістяк блокчейн-даних
 
-Fishermen та Arbitrators також є невіднятною частиною успіху мережі, оскільки вони приносять користь іншими діями, допомагаючи роботі головних ролей в мережі. Щоб дізнатися більше про ролі користувачів мережі, [читайте цю статтю](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![Діаграма токеноміки](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Індексатори отримують токени GRT від делегатів, що збільшує стейк індексатора в підграфах в мережі. Натомість делегати отримують відсоток від усіх комісій за запити та винагороди за індексацію, власне, від індексатора. Кожен індексатор самостійно встановлює відсоток, який буде виплачуватися делегатам, створюючи конкуренцію між індексаторами, які хочуть залучити більшу кількість делегатів. Більшість індексаторів пропонують 9-12% річних.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-До прикладу, якщо делегат делегує 15 тис. GRT індексатору, який пропонує 10% річних, то цей делегат отримає ~ 1500 токенів GRT у винагороду щорічно.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-Існує збір на делегування у розмірі 0.5%, який спалюється щоразу, коли делегат делегує GRT в мережі. Якщо делегат виявить бажання вивести делеговані ним GRT, він повинен дочекатися певного періоду розблокування, який триває 28 епох. Кожна епоха становить 6,646 блока, це означає, що 28 епох дорівнює приблизно 26 днів.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-Якщо ви читаєте цю статтю, ви можете стати делегатом прямо зараз, перейшовши на [сторінку користувачів мережі](https://thegraph.com/explorer/participants/indexers) та делегувавши GRT обраному вами індексатору.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
 ## Curators (Earn GRT)
 
-Куратори визначають високоякісні підграфи та "курують" їх (тобто сигналізують про них за допомогою GRT), щоб отримати кураторські частки, які гарантують відсоток від усіх майбутніх комісій за запити, що генеруються підграфом. Попри те, що будь-який користувач мережі може бути куратором, зазвичай розробники підграфів є одними з перших кураторів власних підграфів, оскільки вони хочуть забезпечити індексацію свого підграфа.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-Куратори сплачують збір у розмірі 1%, коли вони починають курувати новий підграф. Цей % спалюється, зменшуючи загальну кількість токенів GRT.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
 ## Developers
 
-Розробники створюють і перевіряють підграфи для отримання даних блокчейну. Оскільки підграфи мають відкритий вихідний код, розробники можуть використовувати наявні підграфи для завантаження даних блокчейну у свої децентралізовані додатки. Розробники платять за запити, які вони роблять у GRT. Ця плата розподіляється між користувачами мережі.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### Creating a subgraph
 
-Розробники можуть [створити підграф](/developing/creating-a-subgraph/) з метою індексації даних у блокчейні. Підграфи - це інструкції для індексаторів щодо того, які дані слід надавати споживачам.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-Як тільки розробники створили та перевірили свій підграф, вони можуть [опублікувати його](/publishing/publishing-a-subgraph/) в децентралізованій мережі The Graph.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### Querying an existing subgraph
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-Запити до підграфів роблять за допомогою [GraphQL](/querying/querying-the-graph/), а оплата комісій здійснюється за допомогою GRT в [Subgraph Studio](https://thegraph.com/studio/). Ці комісії розподіляються між користувачами мережі на основі їх внесків у роботу протоколу.
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1% комісій за запити спалюється.
+1% of the query fees paid to the network are burned.
 
 ## Indexers (Earn GRT)
 
-Індексатори є серцевиною The Graph. Вони працюють на незалежному апаратному та програмному забезпеченні, що живить децентралізовану мережу The Graph. Індексатори надають дані споживачам на основі інструкцій від підграфів.
-
-Індексатори можуть заробляти GRT двома способами:
-
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
-
-2.  Винагороди за індексування: 3% щорічної емісії токенів розподіляється серед індексаторів на основі кількості підграфів, які вони індексують в той момент. Ці винагороди стимулюють індексаторів індексувати підграфи, іноді навіть до того, як почне стягуватися комісія за запити, нараховувати та подавати підтвердження індексування (POI), які підтверджують, що вони точно проіндексували дані.
-
-Кожному підграфу відведена частина від загального обсягу емісії токенів мережі, виходячи з розміру сигналу курації підграфа. Потім ця сума розподіляється як нагорода індексаторам відповідно до їхнього стейка на підграфі.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-Для того, щоб запустити ноду індексації, індексатори повинні застейкати в мережі мінімум 100 000 GRT. Індексатори зацікавлені стейкати GRT пропорційно до кількості запитів, які вони обслуговують.
+Indexers can earn GRT rewards in two ways:
 
-Індексатори можуть збільшувати кількість GRT, що розподіляється на них та на їх підграфи, приймаючи делегації GRT від делегатів, вони можуть приймати до того часу, поки цифра не стане у 16 разів більше від їх початкового стейку. Якщо індексатор отримує "переделегування" (тобто більше ніж у 16 разів перевищить свою початкову частку), він не зможе використовувати цей додатковий GRT від делегатів, поки не збільшить свій стейк в мережі.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-Розмір винагороди, яку отримує індексатор, може варіюватися залежно від початкового стейка, прийнятого делегування токенів, якості послуг та багатьох інших факторів. Наступна діаграма - це загальнодоступні дані від активного індексатора в децентралізованій мережі The Graph.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### The Indexer stake & reward of allnodes-com.eth
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![Індексація стейка та винагороди](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-Ці дані представлені за період з лютого 2021 року по вересень 2022 року.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Зверніть увагу, що ситуація стане значно кращою після [міграції на Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551), що зробить витрати на газ значно меншими та полегшить вашу участь в мережі.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
 ## Token Supply: Burning & Issuance
 
-Початкова пропозиція токенів становить 10 мільярдів GRT, мета - 3% емісії нових токенів щорічно, для винагороди індексаторів за розподіл свого стейка на підграфах. Це означає, що загальна кількість токенів GRT буде збільшуватися на 3% щороку, оскільки нові токени будуть видаватися індексаторам за їх внесок в мережу.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-The Graph розроблений з урахуванням декількох механізмів спалювання, щоб компенсувати випуск нових токенів. Приблизно 1% загальної кількості GRT спалюється щорічно через різні види діяльності в мережі, і ця цифра поступово збільшується, оскільки активність мережі продовжує стрімко зростати. Ці активності зі спалюванням токенів включають 0,5% збір на делегування, коли делегат делегує GRT індексатору, 1% на кураторство, коли куратори починають курувати новий підграф, і 1% за запити до даних блокчейну.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![Загальна кількість спалених GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-На додаток до цих регулярних спалювань, токен GRT також має механізм слешингу, що використовується для покарання зловмисної або безвідповідальної поведінки індексаторів. Якщо індексатора було обмежено, 50% від його винагороди за індексацію за конкретну епоху спалюється (друга половина переходить до Fisherman), а його селф-стейк зменшується на 2.5%, причому половина цієї суми згорає. Це допомагає гарантувати, що індексатори мають сильний стимул діяти в інтересах мережі та сприяти її безпеці й стабільності.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
 ## Improving the Protocol
 
-Мережа The Graph постійно розвивається, також постійно поліпшується економічний дизайн протоколу, щоб забезпечити найкращий досвід для всіх користувачів в мережі. The Graph Council контролює зміни протоколу, а члени спільноти заохочуються до участі в мережі. Ви можете долучитися до вдосконалення протоколу перейшовши на [форум The Graph](https://forum.thegraph.com/).
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 3fc629ca11c326253764a3b0e1ae4e1f7a7b427b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:01 -0500
Subject: [PATCH 0422/1325] New translations
 substreams-powered-subgraphs-faq.mdx (Turkish)

---
 .../tr/developing/substreams-powered-subgraphs-faq.mdx    | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/tr/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/tr/developing/substreams-powered-subgraphs-faq.mdx
index 031f92327f90..008fc7ecef4a 100644
--- a/website/pages/tr/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/tr/developing/substreams-powered-subgraphs-faq.mdx
@@ -4,7 +4,7 @@ title: Substreams destekli subgraphlar SSS
 
 ## Substreams nedir?
 
-Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere.
+[StreamingFast](https://www.streamingfast.io/) tarafından geliştirilen Substreams, zengin blokzinciri veri akışlarını işleyebilen son derece güçlü bir işlem motorudur. Substreams, blokzinciri verilerini son kullanıcı uygulamaları tarafından hızlı ve sorunsuz bir şekilde işlenmek üzere rafine etmenizi ve şekillendirmenizi sağlar. Daha spesifik olmak gerekirse, Substreams, farklı blokzincirleriyle uyumlu, paralelleştirilmiş ve akış öncelikli bir motor olup bir blokzinciri veri dönüşüm katmanı olarak işlev görür. [Firehose](https://firehose.streamingfast.io/) tarafından desteklenen Substreams, geliştiricilerin Rust modülleri yazmasına, topluluk modüllerini kullanarak geliştirme yapmasına, son derece yüksek performanslı endeksleme sağlamasına ve verilerini herhangi bir yere yönlendirmesine ([sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink)) olanak tanır.
 
 Substreams hakkında daha fazla bilgi için [SubstreamsDökümantasyonuna](/substreams) gidin.
 
@@ -22,7 +22,7 @@ Buna karşılık, Substreams destekli subgraphlar, Substreams paketini referans
 
 ## Substreams destekli subgraphlar kullanmanın avantajları nelerdir?
 
-Substreams-powered subgraphs combine all the benefits of Substreams with the queryability of subgraphs. They bring greater composability and high-performance indexing to The Graph. They also enable new data use cases; for example, once you've built your Substreams-powered Subgraph, you can reuse your [Substreams modules](https://substreams.streamingfast.io/documentation/develop/manifest-modules) to output to different [sinks](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) such as PostgreSQL, MongoDB, and Kafka.
+Substreams destekli subgraph'ler, Substreams'in tüm avantajlarını subgraph'lerin sorgulanabilirliğiyle birleştirir. Bu yaklaşım, The Graph'e daha fazla birleştirilebilirlik ve yüksek performanslı endeksleme sağlar. Ayrıca, yeni veri kullanım senaryolarını mümkün kılar. Örneğin, Substreams destekli subgraph'inizi oluşturduktan sonra, [Substreams modüllerinizi](https://substreams.streamingfast.io/documentation/develop/manifest-modules) PostgreSQL, MongoDB ve Kafka gibi farklı [veri hedeflerine](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) çıktı almak için yeniden kullanabilirsiniz.
 
 ## Substreams'in faydaları nelerdir?
 
@@ -66,13 +66,13 @@ Firehose kullanmanın birçok faydası vardır, bunlar şunlardır:
 
 [Substreams destekli subgrahplar belgeleri](/cookbook/substreams-powered-subgraphs/), onları Graph üzerinde dağıtmak için nasıl paketleyeceğinizi gösterecektir.
 
-The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code.
+[En son sürüm Substreams Codegen aracı](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6), hiç kod yazmadan bir Substreams projesi başlatmanıza olanak tanır.
 
 ## Rust modüllerinin Substreams içindeki rolü nedir?
 
 Rust modülleri, Subgraphs'teki AssemblyScript eşleştiricilerinin karşılığıdır. WASM'ye benzer şekilde derlenirler, ancak programlama modelleri paralel yürütme için olanak sağlar. Rust modülleri, ham blok zinciri verilerine uygulamak istediğiniz dönüşümleri ve birleştirmeleri tanımlar.
 
-See [modules documentation](https://substreams.streamingfast.io/documentation/develop/manifest-modules) for details.
+Detaylar için [modüller dokümantasyonuna](https://substreams.streamingfast.io/documentation/develop/manifest-modules) bakın.
 
 ## Substreams'i birleştirilebilir yapan nedir?
 

From da5a07b704c2575db958071cb6828fead1ee2b06 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:02 -0500
Subject: [PATCH 0423/1325] New translations common-issues.mdx (Turkish)

---
 website/pages/tr/developing/graph-ts/common-issues.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/tr/developing/graph-ts/common-issues.mdx b/website/pages/tr/developing/graph-ts/common-issues.mdx
index 892ab40dce7f..c0debe317d00 100644
--- a/website/pages/tr/developing/graph-ts/common-issues.mdx
+++ b/website/pages/tr/developing/graph-ts/common-issues.mdx
@@ -2,7 +2,7 @@
 title: Genel AssemblyScript Sorunları
 ---
 
-There are certain [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) issues that are common to run into during subgraph development. They range in debug difficulty, however, being aware of them may help. The following is a non-exhaustive list of these issues:
+Subgraph geliştirme sırasında karşılaşılması muhtemel bazı [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) sorunları bulunmaktadır. Bu sorunlar, hata ayıklama zorluğuna göre değişiklik gösterse de bunların farkında olmak faydalı olabilir. Aşağıda, bu sorunların kapsamlı olmayan bir listesi verilmiştir:
 
-- `Private` class variables are not enforced in [AssembyScript](https://www.assemblyscript.org/status.html#language-features). There is no way to protect class variables from being directly changed from the class object.
-- Scope is not inherited into [closure functions](https://www.assemblyscript.org/status.html#on-closures), i.e. variables declared outside of closure functions cannot be used. Explanation in [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s).
+- [AssemblyScript'te](https://www.assemblyscript.org/status.html#language-features) `private` sınıf değişkenleri zorunlu tutulmaz. Sınıf nesnesi üzerinden sınıf değişkenlerinin doğrudan değiştirilmesini engellemenin bir yolu yoktur.
+- Kapsam [Closure fonksiyonlarına] aktarılmaz (https://www.assemblyscript.org/status.html#on-closures) kalıtılmaz, yani closure fonksiyonlarının dışında tanımlanan değişkenler bu fonksiyonlar içinde kullanılamaz. Daha fazla açıklama için [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s) videosuna bakabilirsiniz.

From 0095415effb68ca4326e964960551729488d01f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:03 -0500
Subject: [PATCH 0424/1325] New translations supported-networks.json (Turkish)

---
 website/pages/tr/developing/supported-networks.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/tr/developing/supported-networks.json b/website/pages/tr/developing/supported-networks.json
index 6e5afdc4c92f..12a54cd5f729 100644
--- a/website/pages/tr/developing/supported-networks.json
+++ b/website/pages/tr/developing/supported-networks.json
@@ -2,8 +2,8 @@
   "network": "Ağ",
   "cliName": "CLI Adı",
   "chainId": "Zincir Kimliği",
-  "hostedService": "Barındırılan Hizmet",
+  "hostedService": "Barındırılan hizmet",
   "subgraphStudio": "Subgraph Stüdyosu",
   "decentralizedNetwork": "Merkeziyetsiz Ağ",
-  "integrationType": "Integration Type"
+  "integrationType": "Entegrasyon Türü"
 }

From 5102fb9b43c4141d3edda14510afdce75890c5a8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:04 -0500
Subject: [PATCH 0425/1325] New translations triggers.mdx (Hindi)

---
 website/pages/hi/sps/triggers.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/hi/sps/triggers.mdx b/website/pages/hi/sps/triggers.mdx
index ed19635d4768..2d5a8db77b60 100644
--- a/website/pages/hi/sps/triggers.mdx
+++ b/website/pages/hi/sps/triggers.mdx
@@ -1,12 +1,12 @@
 ---
-title: Substreams Triggers
+title: सबस्ट्रीम्स ट्रिगर्स
 ---
 
-Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework.
+कस्टम ट्रिगर्स आपको अपने subgraph मैपिंग फ़ाइल और इकाइयों (टेबल और फ़ील्ड के समान) में डेटा सीधे भेजने की अनुमति देते हैं, जो GraphQL परत का पूरा उपयोग करने में सक्षम बनाते हैं। अपने Substreams मॉड्यूल द्वारा उत्पन्न Protobuf परिभाषाओं को आयात करके, आप अपने subgraph के हैंडलर के भीतर इस डेटा को प्राप्त और प्रोसेस कर सकते हैं, जो subgraph ढांचे के भीतर कुशल और सुव्यवस्थित डेटा प्रबंधन सुनिश्चित करता है।
 
-> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container.
+> नोट: यदि आपने पहले से ऐसा नहीं किया है, तो अपने पहले प्रोजेक्ट को Development Container में स्कैफोल्ड करने के लिए यहाँ (./introduction) पाए जाने वाले How-To Guides में से एक पर जाएं।
 
-The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created.
+निम्नलिखित कोड यह दर्शाता है कि कैसे एक handleTransactions फ़ंक्शन को एक subgraph हैंडलर में परिभाषित किया जा सकता है। यह फ़ंक्शन कच्चे Substreams बाइट्स को एक पैरामीटर के रूप में प्राप्त करता है और उन्हें एक Transactions ऑब्जेक्ट में डिकोड करता है। प्रत्येक लेनदेन के लिए, एक नई subgraph एंटिटी बनाई जाती है।
 
 ```tsx
 export function handleTransactions(bytes: Uint8Array): void {
@@ -28,10 +28,10 @@ export function handleTransactions(bytes: Uint8Array): void {
 }
 ```
 
-Here's what you’re seeing in the `mappings.ts` file:
+यहां वह है जो आप mappings.ts फ़ाइल में देख रहे हैं:
 
-1. The bytes containing Substreams data are decoded into the generated `Transactions` object, this object is used like any other AssemblyScript object
-2. Looping over the transactions
-3. Create a new subgraph entity for every transaction
+1. Substreams डेटा को जनरेट किए गए Transactions ऑब्जेक्ट में डिकोड किया जाता है, यह ऑब्जेक्ट किसी अन्य AssemblyScript ऑब्जेक्ट की तरह उपयोग किया जाता है।
+2. लेनदेन पर लूप करना
+3. प्रत्येक लेनदेन के लिए एक नया subgraph entity बनाएं
 
-To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example).
+ड्रैगर-आधारित एक उपग्राफ के विस्तृत उदाहरण के लिए, यहां क्लिक करें(./triggers-example).

From f4610dc23e9cd242b9a57c97cf0e5c6c5ac22fb7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:05 -0500
Subject: [PATCH 0426/1325] New translations multiple-networks.mdx (Hindi)

---
 .../pages/hi/deploying/multiple-networks.mdx  | 77 ++++++++++---------
 1 file changed, 39 insertions(+), 38 deletions(-)

diff --git a/website/pages/hi/deploying/multiple-networks.mdx b/website/pages/hi/deploying/multiple-networks.mdx
index dc2b8e533430..4f0308b2e45b 100644
--- a/website/pages/hi/deploying/multiple-networks.mdx
+++ b/website/pages/hi/deploying/multiple-networks.mdx
@@ -1,30 +1,31 @@
 ---
-title: Deploying a Subgraph to Multiple Networks
+title: मल्टीपल नेटवर्क्स पर एक Subgraph डिप्लॉय करना
 ---
 
-This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
+यह पृष्ठ कई नेटवर्क पर एक subgraph को डिप्लॉय करने के तरीके को समझाता है। एक subgraph को डिप्लॉय करने के लिए, आपको पहले Graph CLI(https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) स्थापित करना होगा। यदि आपने पहले से एक subgraph नहीं बनाया है, तो Creating a subgraph (/developing/creating-a-subgraph). देखें।
 
-## Deploying the subgraph to multiple networks
+## सबग्राफ को कई नेटवर्क पर तैनात करना
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+कुछ मामलों में, आप एक ही सबग्राफ को इसके सभी कोड को डुप्लिकेट किए बिना कई नेटवर्क पर तैनात करना चाहेंगे। इसके साथ आने वाली मुख्य चुनौती यह है कि इन नेटवर्कों पर अनुबंध के पते अलग-अलग हैं।
 
-### Using `graph-cli`
+### graph-cli का उपयोग करते हुए
 
-Both `graph build` (since `v0.29.0`) and `graph deploy` (since `v0.32.0`) accept two new options:
+दोनों graph build (v0.29.0 से) और graph deploy (v0.32.0 से) दो नए विकल्प स्वीकार करते हैं:
 
 ```sh
-Options:
+विकल्प:
 
       ...
-      --network <name>          Network configuration to use from the networks config file
-      --network-file <path>     Networks config file path (default: "./networks.json")
+      --network <name>          नेटवर्क कॉन्फ़िगरेशन का उपयोग करें जो नेटवर्क कॉन्फ़िग फ़ाइल से हो
+      --network-file <path>     नेटवर्क्स कॉन्फ़िग फ़ाइल का पथ (डिफ़ॉल्ट: "./networks.json")
+
 ```
 
-You can use the `--network` option to specify a network configuration from a `json` standard file (defaults to `networks.json`) to easily update your subgraph during development.
+आप --network विकल्प का उपयोग करके एक नेटवर्क कॉन्फ़िगरेशन को एक json मानक फ़ाइल (डिफ़ॉल्ट रूप से networks.json) से निर्दिष्ट कर सकते हैं ताकि विकास के दौरान आसानी से अपने subgraph को अपडेट किया जा सके
 
-> Note: The `init` command will now auto-generate a `networks.json` based on the provided information. You will then be able to update existing or add additional networks.
+> ध्यान दें: init कमांड अब दी गई जानकारी के आधार पर एक networks.json को स्वचालित रूप से उत्पन्न करेगा। इसके बाद आप मौजूदा नेटवर्क को अपडेट कर सकेंगे या अतिरिक्त नेटवर्क जोड़ सकेंगे।
 
-If you don't have a `networks.json` file, you'll need to manually create one with the following structure:
+अगर आपके पास networks.json फ़ाइल नहीं है, तो आपको इसे मैन्युअल रूप से निम्नलिखित संरचना के साथ बनाना होगा:
 
 ```json
 {
@@ -52,9 +53,9 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 }
 ```
 
-> Note: You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
+> ध्यान दें: आपको किसी भी 'templates' (यदि आपके पास कोई है) को config फ़ाइल में निर्दिष्ट करने की आवश्यकता नहीं है, केवल 'dataSources' को। यदि 'subgraph.yaml' फ़ाइल में कोई 'templates' घोषित किए गए हैं, तो उनका नेटवर्क स्वचालित रूप से उस नेटवर्क में अपडेट हो जाएगा जो 'network' विकल्प के साथ निर्दिष्ट किया गया है।
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `sepolia` networks, and this is your `subgraph.yaml`:
+मान लीजिए कि आप अपने subgraph को mainnet और sepolia नेटवर्क पर डिप्लॉय करना चाहते हैं, और यह आपका subgraph.yaml है:
 
 ```yaml
 # ...
@@ -69,7 +70,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+आपकी नेटवर्क कॉन्फ़िग फ़ाइल इस तरह दिखनी चाहिए:
 
 ```json
 {
@@ -86,7 +87,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+अब हम निम्न में से कोई एक कमांड चला सकते हैं:
 
 ```sh
 # Using default networks.json file
@@ -96,7 +97,7 @@ yarn build --network sepolia
 yarn build --network sepolia --network-file path/to/config
 ```
 
-The `build` command will update your `subgraph.yaml` with the `sepolia` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+build कमांड आपके subgraph.yaml को sepolia कॉन्फ़िगरेशन के साथ अपडेट करेगा और फिर से subgraph को पुनः-कंपाइल करेगा। आपका subgraph.yaml फ़ाइल अब इस प्रकार दिखना चाहिए:
 
 ```yaml
 # ...
@@ -111,9 +112,9 @@ dataSources:
       kind: ethereum/events
 ```
 
-Now you are ready to `yarn deploy`.
+अब आप yarn deploy के लिए तैयार हैं।
 
-> Note: As mentioned earlier, since `graph-cli 0.32.0` you can directly run `yarn deploy` with the `--network` option:
+> नोट: जैसा कि पहले बताया गया है, graph-cli 0.32.0 से, आप सीधे yarn deploy को --network विकल्प के साथ चला सकते हैं:
 
 ```sh
 # Using default networks.json file
@@ -123,9 +124,9 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Subgraph.yaml टेम्पलेट का उपयोग करना
 
-One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
+एक तरीका है 'graph-cli' के पुराने संस्करणों का उपयोग करके अनुबंध पते जैसी विशेषताओं को पैरामीटरित करना, जो कि एक टेम्पलेटिंग सिस्टम जैसे Mustache (https://mustache.github.io/) या Handlebars (https://handlebarsjs.com/) के साथ इसके कुछ हिस्सों को जनरेट करना है।
 
 To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Sepolia using different contract addresses. You could then define two config files providing the addresses for each network:
 
@@ -136,7 +137,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+और
 
 ```json
 {
@@ -145,7 +146,7 @@ and
 }
 ```
 
-Along with that, you would substitute the network name and addresses in the manifest with variable placeholders `{{network}}` and `{{address}}` and rename the manifest to e.g. `subgraph.template.yaml`:
+साथ ही, आप नेटवर्क नाम और पते को मैनिफेस्ट में वेरिएबल प्लेसहोल्डर्स {{network}} और {{address}} से बदल देंगे और मैनिफेस्ट का नाम बदलकर उदाहरण के लिए subgraph.template.yaml रख देंगे:
 
 ```yaml
 # ...
@@ -162,10 +163,10 @@ dataSources:
       kind: ethereum/events
 ```
 
-In order to generate a manifest to either network, you could add two additional commands to `package.json` along with a dependency on `mustache`:
+एक मैनिफेस्ट बनाने के लिए, आप package.json में दो अतिरिक्त कमांड जोड़ सकते हैं, साथ ही mustache पर एक निर्भरता भी डाल सकते हैं:
 
 ```json
-{
+
   ...
   "scripts": {
     ...
@@ -182,20 +183,20 @@ In order to generate a manifest to either network, you could add two additional
 To deploy this subgraph for mainnet or Sepolia you would now simply run one of the two following commands:
 
 ```sh
-# Mainnet:
-yarn prepare:mainnet && yarn deploy
+मेननेट:
+yarn prepare && yarn deploy
 
-# Sepolia:
-yarn prepare:sepolia && yarn deploy
+सेपोलिया:
+yarn prepare && yarn deploy
 ```
 
-A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
+एक कामकाजी उदाहरण इसे यहां पाया जा सकता है here (https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
 
-**Note:** This approach can also be applied to more complex situations, where it is necessary to substitute more than contract addresses and network names or where generating mappings or ABIs from templates as well.
+यह दृष्टिकोण अधिक जटिल परिस्थितियों में भी लागू किया जा सकता है, जहां अनुबंध पते और नेटवर्क नामों के अलावा अधिक को प्रतिस्थापित करने की आवश्यकता होती है या जहां टेम्पलेट से मैपिंग या ABIs उत्पन्न करने की आवश्यकता होती है।
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+यह आपको chainHeadBlock देगा जिसे आप अपने subgraph पर latestBlock के साथ तुलना कर सकते हैं यह जाँचने के लिए कि क्या यह पीछे चल रहा है। synced यह बताता है कि क्या subgraph कभी श्रृंखला के साथ मेल खा गया है। health वर्तमान में दो मान ले सकता है: healthy अगर कोई त्रुटियाँ नहीं हुई हैं, या failed अगर कोई त्रुटि हुई है जिसने subgraph की प्रगति को रोक दिया है। इस स्थिति में, आप इस त्रुटि के विवरण के लिए fatalError फ़ील्ड की जांच कर सकते हैं।
 
-## Subgraph Studio subgraph archive policy
+## सबग्राफ स्टूडियो सबग्राफ संग्रह नीति
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,13 +206,13 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+इस नीति से प्रभावित प्रत्येक सबग्राफ के पास विचाराधीन संस्करण को वापस लाने का विकल्प है।
 
-## Checking subgraph health
+## सबग्राफ स्वास्थ्य की जाँच करना
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+यदि एक सबग्राफ सफलतापूर्वक सिंक हो जाता है, तो यह एक अच्छा संकेत है कि यह हमेशा के लिए अच्छी तरह से चलता रहेगा। हालांकि, नेटवर्क पर नए ट्रिगर्स के कारण आपका सबग्राफ एक अनुपयोगी त्रुटि स्थिति में आ सकता है या यह प्रदर्शन समस्याओं या नोड ऑपरेटरों के साथ समस्याओं के कारण पीछे पड़ना शुरू हो सकता है।
 
-Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+Graph Node एक GraphQL endpoint को उजागर करता है जिसे आप अपने subgraph की स्थिति की जांच करने के लिए क्वेरी कर सकते हैं। होस्टेड सेवा पर, यह https://api.thegraph.com/index-node/graphql पर उपलब्ध है। एक स्थानीय नोड पर, यह डिफ़ॉल्ट रूप से पोर्ट 8030/graphql पर उपलब्ध है। इस endpoint के लिए पूरा स्कीमा यहां (https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql) पाया जा सकता है। यहां एक उदाहरण क्वेरी है जो एक subgraph के वर्तमान संस्करण की स्थिति की जांच करती है:
 
 ```graphql
 {
@@ -238,4 +239,4 @@ Graph Node exposes a GraphQL endpoint which you can query to check the status of
 }
 ```
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+यह आपको chainHeadBlock देगा जिसे आप अपने subgraph पर latestBlock के साथ तुलना कर सकते हैं यह जाँचने के लिए कि क्या यह पीछे चल रहा है। synced यह बताता है कि क्या subgraph कभी श्रृंखला के साथ मेल खा गया है। health वर्तमान में दो मान ले सकता है: healthy अगर कोई त्रुटियाँ नहीं हुई हैं, या failed अगर कोई त्रुटि हुई है जिसने subgraph की प्रगति को रोक दिया है। इस स्थिति में, आप इस त्रुटि के विवरण के लिए fatalError फ़ील्ड की जांच कर सकते हैं।

From a223d360ca4cef78b373172934c13410d53f94ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:06 -0500
Subject: [PATCH 0427/1325] New translations deploy-using-subgraph-studio.mdx
 (Hindi)

---
 .../deploy-using-subgraph-studio.mdx          | 132 +++++++++---------
 1 file changed, 65 insertions(+), 67 deletions(-)

diff --git a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx b/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..ae89fa2d38fd 100644
--- a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
@@ -1,139 +1,137 @@
 ---
-title: Deploy Using Subgraph Studio
+title: Subgraph Studio का उपयोग करके डिप्लॉय करें
 ---
 
-Learn how to deploy your subgraph to Subgraph Studio.
+अपने subgraph को Subgraph Studio में डिप्लॉय करना सीखें।
 
-> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
+> नोट: जब आप एक subgraph को डिप्लॉय करते हैं, तो आप इसे Subgraph Studio पर पुश करते हैं, जहाँ आप इसे टेस्ट कर सकेंगे। यह याद रखना महत्वपूर्ण है कि डिप्लॉय करना प्रकाशित करने के समान नहीं है। जब आप एक subgraph को प्रकाशित करते हैं, तो आप इसे ऑन-चेन प्रकाशित कर रहे हैं।
 
-## Subgraph Studio Overview
+## Subgraph Studio का अवलोकन
 
-In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
+In <a href="https://thegraph.com/studio/">Subgraph Studio</a>,आप निम्नलिखित कर सकते हैं:
 
-- View a list of subgraphs you've created
-- Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
-- Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
-- Test your subgraph in the playground environment
-- Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
-- Manage your billing
+- आपने बनाए गए subgraphs की सूची देखें
+- एक विशेष subgraph की स्थिति को प्रबंधित करें, विवरण देखें और दृश्य रूप में प्रदर्शित करें
+- विशिष्ट सबग्राफ के लिए अपनी एपीआई keys बनाएं और प्रबंधित करें
+- अपने API कुंजी को विशेष डोमेन तक सीमित करें और केवल कुछ Indexers को उनके साथ क्वेरी करने की अनुमति दें
+- अपना subgraph बनाएं
+- अपने subgraph को The Graph CLI का उपयोग करके डिप्लॉय करें
+- अपने 'subgraph' को 'playground' वातावरण में टेस्ट करें
+- अपने स्टेजिंग में 'subgraph' को विकास क्वेरी URL का उपयोग करके एकीकृत करें 
+- अपने subgraph को The Graph Network पर प्रकाशित करें
+- अपने बिलिंग को प्रबंधित करें
 
-## Install The Graph CLI
+## The Graph CLI स्थापित करें
 
-Before deploying, you must install The Graph CLI.
+Deploy करने से पहले, आपको The Graph CLI इंस्टॉल करना होगा।
 
-You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+आपको 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 संस्करण की जांच करें।
 
-**Install with yarn:**
+### इंस्टॉल करें 'yarn' के साथ
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### इंस्टॉल करें 'npm' के साथ
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
+## शुरू हो जाओ
 
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+1. खोलें [Subgraph Studio](https://thegraph.com/studio/).
+2. अपने वॉलेट से साइन इन करें।
+   - आप इसे MetaMask, Coinbase Wallet, WalletConnect, या Safe के माध्यम से कर सकते हैं।
+3. साइन इन करने के बाद, आपका यूनिक डिप्लॉय की आपकी subgraph विवरण पृष्ठ पर प्रदर्शित होगा।
+   - Deploy key आपको अपने subgraphs को प्रकाशित करने या अपने API keys और billing को प्रबंधित करने की अनुमति देता है। यह अद्वितीय है लेकिन यदि आपको लगता है कि यह समझौता किया गया है, तो इसे पुनः उत्पन्न किया जा सकता है।
 
-1. Open [Subgraph Studio](https://thegraph.com/studio/).
-2. Connect your wallet to sign in.
-   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
-3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
-   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
-
-> Important: You need an API key to query subgraphs
+> महत्वपूर्ण: आपको subgraphs को क्वेरी करने के लिए एक API कुंजी की आवश्यकता है
 
 ### How to Create a Subgraph in Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> अतिरिक्त लिखित विवरण के लिए, Quick Start(/quick-start/) की समीक्षा करें।
 
-### Subgraph Compatibility with The Graph Network
+### ग्राफ नेटवर्क के साथ सबग्राफ अनुकूलता
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
-- Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- एक supported network(/developing/supported-networks) को अनुक्रमित करें
+- निम्नलिखित सुविधाओं में से किसी का उपयोग नहीं करना चाहिए:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - गैर-घातक त्रुटियाँ
+  - ग्राफ्टिंग
 
-## Initialize Your Subgraph
+## अपने Subgraph को प्रारंभ करें
 
-Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
+एक बार जब आपका subgraph Subgraph Studio में बना दिया गया है, तो आप इस कमांड का उपयोग करके CLI के माध्यम से इसके कोड को प्रारंभ कर सकते हैं:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
-You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+आप <SUBGRAPH_SLUG> मान को अपने subgraph विवरण पृष्ठ पर Subgraph Studio में पा सकते हैं, नीचे दी गई छवि देखें:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
-After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+`graph init` चलाने के बाद, आपसे संपर्क पता, नेटवर्क, और एक ABI इनपुट करने के लिए कहा जाएगा जिसे आप क्वेरी करना चाहते हैं। यह आपके स्थानीय मशीन पर एक नया फोल्डर उत्पन्न करेगा जिसमें आपके Subgraph पर काम करना शुरू करने के लिए कुछ मूल कोड होगा। आप फिर अपने Subgraph को अंतिम रूप दे सकते हैं ताकि यह सुनिश्चित किया जा सके कि यह अपेक्षित रूप से काम करता है।
 
-## Graph Auth
+## ग्राफ प्रमाणीकरण
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+अपने subgraph को Subgraph Studio पर डिप्लॉय करने से पहले, आपको CLI के भीतर अपने खाते में लॉग इन करना होगा। ऐसा करने के लिए, आपको अपना deploy key चाहिए होगा, जिसे आप अपने subgraph विवरण पृष्ठ के तहत पा सकते हैं।
 
-Then, use the following command to authenticate from the CLI:
+फिर, CLI से प्रमाणित करने के लिए निम्नलिखित आदेश का उपयोग करें:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
-## Deploying a Subgraph
+## Subgraph डिप्लॉय करना
 
-Once you are ready, you can deploy your subgraph to Subgraph Studio.
+जब आप तैयार हों, तो आप अपना subgraph को Subgraph Studio पर डिप्लॉय कर सकते हैं।
 
-> Deploying a subgraph with the CLI pushes it to the Studio, where you can test it and and update the metadata. This action won't publish your subgraph to the decentralized network.
+> CLI का उपयोग करके subgraph को डिप्लॉय करना उसे Studio में पुश करता है, जहां आप इसे टेस्ट कर सकते हैं और मेटाडेटा को अपडेट कर सकते हैं। यह क्रिया आपके subgraph को विकेंद्रीकृत नेटवर्क पर प्रकाशित नहीं करेगी।
 
-Use the following CLI command to deploy your subgraph:
+निम्नलिखित CLI कमांड का उपयोग करके अपना subgraph डिप्लॉय करें:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
-After running this command, the CLI will ask for a version label.
+यह कमांड चलाने के बाद, CLI एक वर्शन लेबल मांगेगा।
 
-- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
-- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
+- यह दृढ़ता से अनुशंसा की जाती है कि वर्शनिंग के लिए semver(https://semver.org/) का उपयोग किया जाए जैसे 0.0.1। फिर भी, आप किसी भी स्ट्रिंग को वर्शन के रूप में चुनने के लिए स्वतंत्र हैं जैसे v1, version1, या asdf।
+- जो लेबल आप बनाएंगे, वे Graph Explorer में दिखाई देंगे और Curators द्वारा उपयोग किए जा सकते हैं ताकि वे यह निर्णय ले सकें कि वे किसी विशेष संस्करण पर संकेत देना चाहते हैं या नहीं, इसलिए उन्हें सोच-समझकर चुनें।
 
-## Testing Your Subgraph
+## अपने Subgraph का परीक्षण करें
 
-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.
+डिप्लॉय करने के बाद, आप अपने subgraph का परीक्षण कर सकते हैं (या तो Subgraph Studio में या अपने ऐप में, डिप्लॉयमेंट क्वेरी URL के साथ), एक और संस्करण डिप्लॉय करें, मेटाडेटा को अपडेट करें, और जब आप तैयार हों, तो Graph Explorer(https://thegraph.com/explorer) पर प्रकाशित करें।
 
-Use Subgraph Studio to check the logs on the dashboard and look for any errors with your subgraph.
+Subgraph Studio का उपयोग करके डैशबोर्ड पर लॉग्स की जांच करें और अपने subgraph के साथ किसी भी त्रुटियों की तलाश करें।
 
-## Publish Your Subgraph
+## अपने Subgraph को प्रकाशित करें
 
-In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/).
+अपने subgraph को सफलतापूर्वक प्रकाशित करने के लिए, publishing a subgraph(/publishing/publishing-a-subgraph/). की समीक्षा करें।
 
-## Versioning Your Subgraph with the CLI
+## अपने Subgraph को CLI के साथ संस्करण बनाना
 
-If you want to update your subgraph, you can do the following:
+यदि आप अपने subgraph को अपडेट करना चाहते हैं, तो आप निम्नलिखित कर सकते हैं:
 
-- You can deploy a new version to Studio using the CLI (it will only be private at this point).
-- Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
-- This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
+- आप स्टूडियो में CLI का उपयोग करके एक नया संस्करण डिप्लॉय कर सकते हैं (इस समय यह केवल निजी होगा)।
+- एक बार जब आप इससे संतुष्ट हो जाएं, तो आप अपने नए डिप्लॉयमेंट को Graph Explorer(https://thegraph.com/explorer). पर प्रकाशित कर सकते हैं।
+- यह क्रिया आपके नए संस्करण का निर्माण करेगी जिसे Curators सिग्नल करना शुरू कर सकते हैं और Indexers अनुक्रमित कर सकते हैं।
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+आप अपने subgraph के मेटाडेटा को बिना नई संस्करण प्रकाशित किए भी अपडेट कर सकते हैं। आप Studio में अपने subgraph विवरण (प्रोफ़ाइल चित्र, नाम, विवरण, आदि के अंतर्गत) को [Graph Explorer](https://thegraph.com/explorer). में Update Details नामक विकल्प को चेक करके अपडेट कर सकते हैं। यदि यह चेक किया गया है, तो एक ऑन-चेन लेनदेन उत्पन्न होगा जो Explorer में subgraph विवरण को अपडेट करेगा, बिना नई तैनाती के साथ नया संस्करण प्रकाशित किए।
 
-> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
+> Note: नेटवर्क पर नए संस्करण को प्रकाशित करने से संबंधित लागतें हैं। लेनदेन शुल्क के अलावा, आपको ऑटो-माइग्रेटिंग सिग्नल पर क्यूरेशन टैक्स का एक भाग भी फंड करना होगा। यदि क्यूरेटरों ने इस पर सिग्नल नहीं किया है, तो आप अपने सबग्राफ का नया संस्करण प्रकाशित नहीं कर सकते। अधिक जानकारी के लिए, कृपया और पढ़ें यहाँ(/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## सबग्राफ संस्करणों का स्वचालित संग्रह
 
-Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
+जब भी आप Subgraph Studio में एक नया subgraph संस्करण डिप्लॉय करते हैं, तो पिछले संस्करण को आर्काइव कर दिया जाएगा। आर्काइव किए गए संस्करणों को इंडेक्स/सिंक नहीं किया जाएगा और इसलिए उन्हें क्वेरी नहीं किया जा सकता। आप Subgraph Studio में अपने subgraph के आर्काइव किए गए संस्करण को अनआर्काइव कर सकते हैं।
 
-> Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.
+> नोट: स्टूडियो में डिप्लॉय किए गए गैर-प्रकाशित subgraphs के पिछले संस्करणों को स्वचालित रूप से आर्काइव किया जाएगा।
 
 ![Subgraph Studio - Unarchive](/img/Unarchive.png)

From bb519fbebba057f2c85123d4938e81c5163d9913 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:07 -0500
Subject: [PATCH 0428/1325] New translations starting-your-subgraph.mdx
 (Romanian)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/ro/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/ro/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ro/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/ro/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 30ed63523889899785e99cadfd93d0f464e539fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:09 -0500
Subject: [PATCH 0429/1325] New translations starting-your-subgraph.mdx
 (French)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/fr/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/fr/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/fr/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..423512bd80bc
--- /dev/null
+++ b/website/pages/fr/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Aperçu
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 80f293c4857237643f7207ed0aeb3eb2a76db7da Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:10 -0500
Subject: [PATCH 0430/1325] New translations starting-your-subgraph.mdx
 (Spanish)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/es/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/es/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/es/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..316da18524ef
--- /dev/null
+++ b/website/pages/es/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Descripción
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 13b62af09a2ed516843091924af2c8d0affe8810 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:11 -0500
Subject: [PATCH 0431/1325] New translations starting-your-subgraph.mdx
 (Arabic)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/ar/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/ar/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ar/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..f48efba92d85
--- /dev/null
+++ b/website/pages/ar/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## نظره عامة
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From e2ac785f19f2dfaa2cae6b0b7d115cb216d4c4d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:12 -0500
Subject: [PATCH 0432/1325] New translations starting-your-subgraph.mdx (Czech)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/cs/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/cs/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/cs/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..68fba6498608
--- /dev/null
+++ b/website/pages/cs/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Přehled
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 79c2472777ea27910c5ed48fbe87199b18d876f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:13 -0500
Subject: [PATCH 0433/1325] New translations starting-your-subgraph.mdx
 (German)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/de/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/de/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/de/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/de/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 438fafdf9cc7b703eefca89b86bb1bbde86de583 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:14 -0500
Subject: [PATCH 0434/1325] New translations starting-your-subgraph.mdx
 (Italian)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/it/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/it/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/it/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..8a73865b5656
--- /dev/null
+++ b/website/pages/it/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Panoramica
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 1d5d0377f58b8bbac85924a970532f7016fe531e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:15 -0500
Subject: [PATCH 0435/1325] New translations starting-your-subgraph.mdx
 (Japanese)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/ja/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/ja/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ja/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..15e1d6048cbf
--- /dev/null
+++ b/website/pages/ja/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## 概要
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 23b1c903daa31a6315471fb8dadd2c05e0a7e63c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:16 -0500
Subject: [PATCH 0436/1325] New translations starting-your-subgraph.mdx
 (Korean)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/ko/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/ko/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ko/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/ko/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 0d247c3e72681d68eb03cf41e0c4d0b3b6dd3be9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:17 -0500
Subject: [PATCH 0437/1325] New translations starting-your-subgraph.mdx (Dutch)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/nl/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/nl/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/nl/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/nl/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 978fd609d7f4316b1326aea4f02e2a7a729ba0d4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:18 -0500
Subject: [PATCH 0438/1325] New translations starting-your-subgraph.mdx
 (Polish)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/pl/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/pl/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/pl/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/pl/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 4917124eccd5367ace96951422fe84db49b837f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:19 -0500
Subject: [PATCH 0439/1325] New translations starting-your-subgraph.mdx
 (Portuguese)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/pt/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/pt/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/pt/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5d89cfb2fb27
--- /dev/null
+++ b/website/pages/pt/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Visão geral
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 4e580fb59cb8321949aed492ab8608ba58e78f20 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:20 -0500
Subject: [PATCH 0440/1325] New translations starting-your-subgraph.mdx
 (Russian)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/ru/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/ru/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ru/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..39005caf1eeb
--- /dev/null
+++ b/website/pages/ru/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Обзор
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From d06c6c8b1793710ffe900380203ca189f326dd86 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:21 -0500
Subject: [PATCH 0441/1325] New translations starting-your-subgraph.mdx
 (Swedish)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/sv/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/sv/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/sv/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..8e28ff3558ab
--- /dev/null
+++ b/website/pages/sv/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Översikt
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From fbfd36c63315f5312865ee7e03c80fa4e5a53153 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:22 -0500
Subject: [PATCH 0442/1325] New translations starting-your-subgraph.mdx
 (Turkish)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/tr/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/tr/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/tr/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..9423e8078f24
--- /dev/null
+++ b/website/pages/tr/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Genel Bakış
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From d62229e0d0ddb4c4b1155c227f5d30385119dc55 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:23 -0500
Subject: [PATCH 0443/1325] New translations starting-your-subgraph.mdx
 (Ukrainian)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/uk/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/uk/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/uk/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/uk/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From df461874f53703e6baa0ea74f549d3c64ea81d4e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:24 -0500
Subject: [PATCH 0444/1325] New translations starting-your-subgraph.mdx
 (Chinese Simplified)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/zh/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/zh/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/zh/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..f99d56a6aa44
--- /dev/null
+++ b/website/pages/zh/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## 概述
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 90e1b41e0033b96b0ebc15a4b214c7878a411ebf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:25 -0500
Subject: [PATCH 0445/1325] New translations starting-your-subgraph.mdx (Urdu
 (Pakistan))

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/ur/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/ur/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/ur/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..7f864e823000
--- /dev/null
+++ b/website/pages/ur/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## جائزہ
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 2a24ae0a10f5c581eab502123517ed930ee0e28c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:26 -0500
Subject: [PATCH 0446/1325] New translations starting-your-subgraph.mdx
 (Vietnamese)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/vi/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/vi/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/vi/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..4354f4d9b0fd
--- /dev/null
+++ b/website/pages/vi/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Tổng quan
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From c057c9854cecefb121c254b8c8f9cf9d4dcb4955 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:27 -0500
Subject: [PATCH 0447/1325] New translations starting-your-subgraph.mdx
 (Marathi)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/mr/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/mr/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/mr/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..3920ea48feaf
--- /dev/null
+++ b/website/pages/mr/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## सविश्लेषण
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 4eb8c9cc595b4463a407fc7816c1c33c98d70d01 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:28 -0500
Subject: [PATCH 0448/1325] New translations starting-your-subgraph.mdx (Hindi)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/hi/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/hi/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/hi/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..999393096533
--- /dev/null
+++ b/website/pages/hi/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## अवलोकन
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From b875b3f3e66f9865daa6eec377a7a3452754adfc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:30 -0500
Subject: [PATCH 0449/1325] New translations starting-your-subgraph.mdx
 (Swahili)

---
 .../starting-your-subgraph.mdx                | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/sw/developing/creating-a-subgraph/starting-your-subgraph.mdx

diff --git a/website/pages/sw/developing/creating-a-subgraph/starting-your-subgraph.mdx b/website/pages/sw/developing/creating-a-subgraph/starting-your-subgraph.mdx
new file mode 100644
index 000000000000..5127f01632aa
--- /dev/null
+++ b/website/pages/sw/developing/creating-a-subgraph/starting-your-subgraph.mdx
@@ -0,0 +1,21 @@
+---
+title: Starting Your Subgraph
+---
+
+## Overview
+
+The Graph is home to thousands of subgraphs already available for query, so check [The Graph Explorer](https://thegraph.com/explorer) and find one that already matches your needs.
+
+When you create a [subgraph](/subgraphs/), you create a custom open API that extracts data from a blockchain, processes it, stores it, and makes it easy to query via GraphQL.
+
+Subgraph development ranges from simple scaffold subgraphs to advanced, specifically tailored subgraphs.
+
+### Start Building
+
+Start the process and build a subgraph that matches your needs:
+
+1. [Install the CLI](/developing/creating-a-subgraph/install-the-cli/) - Set up your infrastructure
+2. [Subgraph Manifest](/developing/creating-a-subgraph/subgraph-manifest/) - Understand a subgraph's key component
+3. [The Graph Ql Schema](/developing/creating-a-subgraph/ql-schema/) - Write your schema
+4. [Writing AssemblyScript Mappings](/developing/creating-a-subgraph/assemblyscript-mappings/) - Write your mappings
+5. [Advanced Features](/developing/creating-a-subgraph/advanced/) - Customize your subgraph with advanced features

From 4f0b22d79087da01c5867e9a2cdd07ffb1321f7c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:31 -0500
Subject: [PATCH 0450/1325] New translations tokenomics.mdx (Chinese
 Simplified)

---
 website/pages/zh/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/zh/tokenomics.mdx b/website/pages/zh/tokenomics.mdx
index dfb848f1ceee..d3ef5296a6b9 100644
--- a/website/pages/zh/tokenomics.mdx
+++ b/website/pages/zh/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: Graph网络的代币经济学
-description: Graph网络受到强大的代币经济学的激励。以下是GRT——Graph的原生工具代币的工作原理。
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## 概述
 
-- Arbitrum One上的GRT代币地址: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-Graph是一种去中心化协议，可以轻松访问区块链数据。
+## Specifics
 
-它类似于B2B2C模式，只是由去中心化的参与者网络提供支持。网络参与者共同向最终用户提供数据，以换取GRT奖励。GRT是协调数据提供者和消费者的工作工具代币。GRT作为协调网络内数据提供商和消费者的工具，并激励协议参与者有效组织数据。
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-Graph索引区块链数据的方式与Google索引web的方式类似。事实上，您可能已经在使用Graph而没有意识到它。如果您查看了从子图获取数据的dapp的前端，那么您已经从子图查询数据！
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-该Graph在使区块链数据更容易访问并为其交换提供市场方面发挥着至关重要的作用。
+- Arbitrum One上的GRT代币地址: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## 网络参与者的角色
+## The Roles of Network Participants
 
-有四个主要网络参与者：
+There are four primary network participants:
 
 1.  授权人-将GRT授权给索引人并确保网络安全
 
@@ -29,82 +29,74 @@ Graph索引区块链数据的方式与Google索引web的方式类似。事实上
 
 4.  索引人-区块链数据的主干
 
-渔民和仲裁员也通过其他贡献，支持其他主要参与者角色的工作，对网络的成功不可或缺。有关网络角色的更多信息，请[阅读本文](https://thegraph.com/blog/the-graph-grt-token-economics/)。
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![代币图表](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## 授权者（被动获得GRT）
+## Delegators (Passively earn GRT)
 
-索引人由授权者授权GRT，以增加索引人在网络子图中的份额。作为回报，授权者从索引人获得所有查询费用和索引奖励的一部分。每一个索引人都会单独设置奖励给授权者的回扣，从而在索引人之间产生竞争以吸引授权人。大多数指数成份股的年利率在9-12%之间。
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-例如，如果委托人将1.5万GRT委托给提供10%的索引人，则委托人每年将获得约1500 GRT的奖励。
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-每当授权者在网络上授权GRT时，将缴纳0.5%的授权税。如果授权人选择撤回其授权GRT，则授权人必须等待28个月的解锁期。每个时期为6646个区块，这意味着28个时期结束时约为26天。
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-如果你正在阅读这篇文章，你现在就可以成为一名授权者，方法是转到[网络参与者页面](https://thegraph.com/explorer/participants/indexers)，并将GRT授权给你选择的索引人。
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## 策展人（赚取GRT）
+## Curators (Earn GRT)
 
-策展人识别高质量的子图，并对其进行“策展”（即向其发出GRT信号），以获得策展份额，这保证了子图产生的所有未来查询费用的一定比例。尽管任何独立的网络参与者都可以是策展人，但通常子图开发人员是他们自己子图的首批策展人之一，因为他们希望确保自己的子图被索引。
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-策展人在策划新的子图时要缴纳1%的策展税。这种策展税被销毁了，减少了GRT的供应。
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## 开发人员
+## Developers
 
-开发人员构建和查询子图以检索区块链数据。由于子图是开源的，开发人员可以查询现有子图以将区块链数据加载到其dapp中。开发人员为他们在GRT中进行的查询付费，GRT分配给网络参与者。
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### 创建子图
 
-开发人员可以[创建一个子图](/developing/creating-a-subgraph/)来索引区块链上的数据。子图是索引人应向消费者提供哪些数据的说明。
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-一旦开发人员构建并测试了他们的子图，他们就可以在Graph的去中心化网络上[发布子图](/publishing/publishing-a-subgraph/)。
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### 查询现存子图
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-子图[使用GraphQL查询](/querying/querying-the-graph/)，查询费用由[子图工作室](https://thegraph.com/studio/)中的GRT支付。查询费用根据网络参与者对协议的贡献分配给他们。
-
-支付给网络的查询费用的1%被销毁。
-
-## 索引人（赚取GRT）
-
-索引人是Graph的支柱。他们运营独立的硬件和软件，为Graph的去中心化网络提供动力。索引人根据子图的指令向消费者提供数据。
-
-索引人可以通过两种方式获得GRT奖励：
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  索引奖励：每年3%的发行量根据索引子图的数量分配给索引者。这些奖励激励索引者对子图进行索引，有时在查询费用开始之前，累积并提交索引证明（POI），以验证他们是否已准确索引数据。
+## Indexers (Earn GRT)
 
-基于子图的策展信号的量，向每个子图分配总网络代币发行的一部分。然后，根据其在子图上分配的份额，将该金额奖励给索引人。
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-为了运行索引节点，索引人必须在网络中质押100000 GRT或更多。索引人被激励根据其服务的查询量按比例持有GRT。
+Indexers can earn GRT rewards in two ways:
 
-索引人可以通过接受委托人的GRT委托来增加其在子图上的GRT分配，并且他们可以接受最多16倍的初始份额。如果索引人变得“过度授权”（即超过其初始股权16倍），他们将无法使用授权人的额外GRT，直到他们增加其在网络中的份额。
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-索引人获得的奖励金额可能会因初始持股、接受的授权、服务质量以及其他因素而有所不同。下图是Graph去中心化网络上活动索引人的公开可用数据。
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### 名为Allnodes-com.eth的索引人质押奖励
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![索引质押和奖励](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-该数据是2021年2月至2022年9月。
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> 请注意，当[Arbitrum](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551)迁移完成后，这将有所改善，gas成本的减少将大大降低参与网络的负担。
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## 代币供应：销毁和发行
+## Token Supply: Burning & Issuance
 
-初始代币供应量为100亿GRT，目标是每年发行3%的新代币，以奖励在子图上分配份额的索引人。这意味着，GRT代币的总供应量将每年增加3%，因为新的代币将发行给索引人，以供其对网络的贡献。
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-Graph设计有多个消耗机制，以抵消新的代币发行。每年约有1%的GRT供应通过网络上的各种活动花费，随着网络活动的持续增长，这一数字一直在增加。这些花费活动包括每当委托人将GRT委托给索引人时，0.5%的委托税；当策展人在子图上发出信号时，1%的策展税，以及1%的区块链数据查询费。
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![总销毁GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-除了这些经常发生的花费活动外，GRT代币还具有一个砍削机制，以惩罚索引人的恶意或不负责任的行为。如果索引人被削减，他们在该时期索引回报的50%将被销毁（而另一半归fisherman所有），他们的自股将被削减2.5%，其中一半将被花费。这有助于确保索引人有强烈的动机以网络的最大利益为出发点，并为网络的安全和稳定做出贡献。
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## 改进协议
+## Improving the Protocol
 
-Graph网络不断发展，协议的经济设计不断改进，为所有网络参与者提供最佳体验。Graph委员会负责监督协议变更，并鼓励社区成员参与。参与[Graph论坛](https://forum.thegraph.com/)中的协议改进。
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 1e7c9bfb05f8ce781409aba4d91f3ed255274ded Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:32 -0500
Subject: [PATCH 0451/1325] New translations tokenomics.mdx (Urdu (Pakistan))

---
 website/pages/ur/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/ur/tokenomics.mdx b/website/pages/ur/tokenomics.mdx
index 746823f815ea..320a53a47746 100644
--- a/website/pages/ur/tokenomics.mdx
+++ b/website/pages/ur/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: گراف نیٹ ورک کے ٹوکنومکس
-description: گراف نیٹ ورک کو طاقتور ٹوکنومکس کے ذریعے ترغیب دی جاتی ہے۔ یہاں GRT، دی گراف کی مقامی ورک یوٹیلیٹی ٹوکن کام کرنے کا طریقہ ہے.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## جائزہ
 
-- آربٹرم ون پر GRT ٹوکن ایڈریس: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-گراف ایک ڈیسینٹرالائزڈ پروٹوکول ہے جو بلاکچین ڈیٹا تک آسان رسائی کے قابل بناتا ہے.
+## Specifics
 
-یہ ایک B2B2C ماڈل سے ملتا جلتا ہے، سوائے اس کے کہ یہ شرکا کے ڈیسینٹرالائزڈ نیٹ ورک سے چلتا ہے۔ نیٹ ورک کے شرکاء GRT انعامات کے بدلے اختتامی صارفین کو ڈیٹا فراہم کرنے کے لیے مل کر کام کرتے ہیں۔ GRT ورک یوٹیلیٹی ٹوکن ہے جو ڈیٹا فراہم کرنے والوں اور صارفین کو مربوط کرتا ہے۔ GRT نیٹ ورک کے اندر ڈیٹا فراہم کرنے والوں اور صارفین کو مربوط کرنے کے لیے ایک افادیت کے طور پر کام کرتا ہے اور پروٹوکول کے شرکاء کو ڈیٹا کو مؤثر طریقے سے ترتیب دینے کی ترغیب دیتا ہے.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-گراف کا استعمال کرتے ہوئے، صارفین آسانی سے بلاکچین سے ڈیٹا تک رسائی حاصل کر سکتے ہیں، صرف اپنی ضرورت کی مخصوص معلومات کے لیے ادائیگی کر سکتے ہیں۔ گراف آج ویب 3 ایکو سسٹم میں بہت سے [مقبول ڈیپز](https://thegraph.com/explorer) کے ذریعہ استعمال کیا جاتا ہے.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-گراف اسی طرح بلاکچین ڈیٹا کو انڈیکس کرتا ہے جس طرح گوگل ویب کو انڈیکس کرتا ہے۔ درحقیقت، ہو سکتا ہے کہ آپ پہلے ہی گراف کو سمجھے بغیر استعمال کر رہے ہوں۔ اگر آپ نے ڈیپ کے سامنے والے حصے کو دیکھا ہے جو اس کا ڈیٹا سب گراف سے حاصل کرتا ہے، تو آپ نے سب گراف سے ڈیٹا دریافت کیا!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-گراف بلاکچین ڈیٹا کو مزید قابل رسائی بنانے اور اس کے تبادلے کے لیے مارکیٹ پلیس کو فعال کرنے میں ایک اہم کردار ادا کرتا ہے.
+- آربٹرم ون پر GRT ٹوکن ایڈریس: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## نیٹ ورک کے شرکاء کے کردار
+## The Roles of Network Participants
 
-نیٹ ورک کے چار بنیادی شرکاء ہیں:
+There are four primary network participants:
 
 1.  ڈیلیگیٹرز - انڈیکسرز کو GRT ڈیلیگیٹ کریں اور نیٹ ورک کو محفوظ کریں
 
@@ -29,82 +29,74 @@ description: گراف نیٹ ورک کو طاقتور ٹوکنومکس کے ذر
 
 4.  انڈیکسرز - بلاکچین ڈیٹا کی ریڑھ کی ہڈی
 
-فیشرمین اور ثالث بھی دیگر شراکتوں کے ذریعے نیٹ ورک کی کامیابی کے لیے لازم و ملزوم ہیں۔ نیٹ ورک کے کردار کے بارے میں مزید معلومات کے لیے، [یہ مضمون پڑھیں](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![ٹوکنومکس ڈایاگرام](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## ڈیلیگیٹرز (غیر فعال طور پر GRT کمائیں)
+## Delegators (Passively earn GRT)
 
-انڈیکسرز کو ڈیلیگیٹرز کے ذریعے GRT سونپا جاتا ہے جس سے نیٹ ورک پر سب گرافس میں انڈیکسر کا حصہ بڑھتا ہے۔ اس کے بدلے میں، ڈیلیگیٹرز انڈیکسر سے تمام کیوری کی فیسوں اور انڈیکسنگ کے انعامات کا ایک فیصد حاصل کرتے ہیں۔ ہر انڈیکسرز کٹ سیٹ کرتا ہے جو ڈیلیگیٹرز کو آزادانہ طور پر دیا جائے گا، جس سے انڈیکسرز کے درمیان ڈیلیگیٹرز کو راغب کرنے کے لیے مقابلہ پیدا ہوتا ہے۔ زیادہ تر انڈیکسرز سالانہ 9-12% کے درمیان پیش کرتے ہیں.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-مثال کے طور پر، اگر ایک ڈیلیگیٹر 15k GRT ایک انڈیکسر کو 10% کی پیشکش کرتا ہے، تو ڈیلیگیٹر کو سالانہ 1500 GRT انعامات ملیں گے.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-0.5% ڈیلیگیشن ٹیکس ہے جو کہ جب بھی کوئی ڈیلیگیٹر نیٹ ورک پر GRT ڈیلیگیٹ کرتا ہے تو اسے جلا دیا جاتا ہے۔ اگر کوئی ڈیلیگیٹر اپنی ڈیلیگیٹ شدہ GRT کو واپس لینے کا انتخاب کرتا ہے، تو ڈیلیگیٹر کو 28-ایپوچ ان بانڈنگ مدت کا انتظار کرنا چاہیے۔ ہر ایپوچ 6,646 بلاکس کا ہوتا ہے، جس کا مطلب ہے کہ 28 ایپوچ تقریباً 26 دن پر ختم ہوتے ہیں.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-اگر آپ اسے پڑھ رہے ہیں، تو آپ ابھی [نیٹ ورک کے شرکاء کے صفحہ](https://thegraph.com/explorer/participants/indexers) پر جا کر ڈیلیگیٹرز بننے کے اہل ہیں، اور اپنی پسند کے انڈیکسر کو GRT ڈیلیگیٹ کرنا.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## کیوریٹرز (GRT کمائیں)
+## Curators (Earn GRT)
 
-کیوریٹرز اعلیٰ معیار کے سب گراف کی شناخت کرتے ہیں، اور کیوریشن شیئرز حاصل کرنے کے لیے ان کو "کیوریٹ" کرتے ہیں (یعنی ان پر GRT کا اشارہ دیتے ہیں)، جو سب گراف کے ذریعے پیدا ہونے والی مستقبل کی تمام کیوری کی فیسوں کے فیصد کی ضمانت دیتے ہیں۔ اگرچہ کوئی بھی آزاد نیٹ ورک حصہ دار کیوریٹر ہو سکتا ہے، عام طور پر سب گراف ڈویلپرز اپنے سب گراف کے لیے پہلے کیوریٹرز میں شامل ہوتے ہیں کیونکہ وہ اس بات کو یقینی بنانا چاہتے ہیں کہ ان کا سب گراف انڈیکس ہو.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-کیوریٹرز جب نیا سب گراف کیوریٹ کرتے ہیں تو 1% کیوریشن ٹیکس ادا کرتے ہیں۔ اس کیوریشن ٹیکس کو جلا دیا جاتا ہے، جس سے GRT کی سپلائی کم ہوتی ہے.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## ڈویلپرز
+## Developers
 
-ڈیولپر بلاکچین ڈیٹا کو بازیافت کرنے کے لیے سب گراف بناتے اور کیوری کرتے ہیں۔ چونکہ سب گراف اوپن سورس ہیں، اس لیے ڈویلپرز اپنے ڈی ایپ میں بلاکچین ڈیٹا لوڈ کرنے کے لیے موجودہ سب گرافس سے کیوری کر سکتے ہیں۔ ڈویلپرز GRT میں کیے گئے کیوریز کے لیے ادائیگی کرتے ہیں، جو نیٹ ورک کے شرکاء میں تقسیم کیے جاتے ہیں.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### سب گراف بنائیں
 
-ڈیولپرز بلاکچین پر ڈیٹا کو انڈیکس کرنے کے لیے [سب گراف بنا سکتے ہیں](/developing/creating-a-subgraph/)۔ سب گراف انڈیکسرز کے لیے ہدایات ہیں جن کے بارے میں صارفین کو ڈیٹا فراہم کیا جانا چاہیے.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-ایک بار جب ڈویلپرز نے اپنا سب گراف بنایا اور جانچ لیا، تو وہ گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر [اپنا سب گراف شائع](/publishing/publishing-a-subgraph/) کر سکتے ہیں.
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### موجودہ سب گراف کو کیوری کریں
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-سب گراف [GraphQL کا استعمال کرتے ہوئے کیوری کیے جاتے ہیں](/querying/querying-the-graph/)، اور کیوری کی فیس GRT کے ساتھ [سب گراف اسٹوڈیو](https://thegraph.com/studio میں ادا کی جاتی ہے۔ /)۔ پروٹوکول میں ان کے تعاون کی بنیاد پر نیٹ ورک کے شرکاء میں کیوری کی فیس تقسیم کی جاتی ہے.
-
-نیٹ ورک کو ادا کی جانے والی کیوری کی فیس کا 1% جل گیا ہے.
-
-## انڈیکسرز (GRT کمائیں)
-
-انڈیکسرز دی گراف کی ریڑھ کی ہڈی ہیں۔ وہ گراف کے ڈیسینٹرالائزڈ نیٹ ورک کو طاقت دینے والے آزاد ہارڈ ویئر اور سافٹ ویئر چلاتے ہیں۔ انڈیکسرز سب گراف کی ہدایات کی بنیاد پر صارفین کو ڈیٹا فراہم کرتے ہیں.
-
-انڈیکسرز دو طریقوں سے GRT انعامات حاصل کر سکتے ہیں:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  کیوری فیس: ڈیلپرز یا صارفین کے ذریعے سب گراف ڈیٹا کے کیوریز کے لیے GRT ادا کیا جاتا ہے۔ کیوری فیس براہ راست انڈیکسرز میں ایکسپونینشل ریبیٹ فنکشن کے مطابق تقسیم کی جاتی ہیں (جی آئی پی [یہاں](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162) دیکھیں).
+1% of the query fees paid to the network are burned.
 
-2.  انڈیکسنگ کے انعامات: 3% سالانہ اجراء انڈیکسرز میں تقسیم کیا جاتا ہے اس بنیاد پر کہ وہ انڈیکس کر رہے ہیں۔ یہ انعامات انڈیکسرز کو انڈیکس سب گراف کی ترغیب دیتے ہیں، کبھی کبھار کیوری کی فیس شروع ہونے سے پہلے، انڈیکسنگ کے ثبوت (POIs) جمع کرنے اور جمع کروانے کے لیے اس بات کی تصدیق کرتے ہیں کہ انھوں نے ڈیٹا کو درست طریقے سے ترتیب دیا ہے.
+## Indexers (Earn GRT)
 
-ہر سب گراف کو کل نیٹ ورک ٹوکن جاری کرنے کا ایک حصہ الاٹ کیا جاتا ہے، سب گراف کے کیوریشن سگنل کی مقدار کی بنیاد پر۔ اس کے بعد اس رقم کو انڈیکسرز کو سب گراف پر ان کے مختص حصص کی بنیاد پر انعام دیا جاتا ہے.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-انڈیکسنگ نوڈ کو چلانے کے لیے، انڈیکسرز کو نیٹ ورک کے ساتھ 100,000 GRT یا اس سے زیادہ حصہ لینا چاہیے۔ انڈیکسرز کو ان کی پیش کردہ کیوریز کی مقدار کے تناسب سے GRT کو داؤ پر لگانے کی ترغیب دی جاتی ہے.
+Indexers can earn GRT rewards in two ways:
 
-انڈیکسرز ڈیلیگیٹرز سے GRT ڈیلیگیشن کو قبول کر کے سب گراف پر اپنی GRT مختص میں اضافہ کر سکتے ہیں، اور وہ اپنے ابتدائی حصص کے 16 گنا تک قبول کر سکتے ہیں۔ اگر ایک انڈیکسر "اوور ڈیلیگیٹڈ" ہو جاتا ہے (یعنی ان کے ابتدائی حصص سے 16 گنا زیادہ)، تو وہ ڈیلیگیٹرز سے اضافی GRT استعمال نہیں کر سکیں گے جب تک کہ وہ نیٹ ورک میں اپنا حصہ نہیں بڑھا لیتے.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-انڈیکسر کو ملنے والے انعامات کی رقم ابتدائی داؤ، قبول شدہ وفد، خدمت کے معیار، اور بہت سے دیگر عوامل کی بنیاد پر مختلف ہو سکتی ہے۔ درج ذیل چارٹ گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر ایک فعال انڈیکسر سے عوامی طور پر دستیاب ڈیٹا ہے.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### انڈیکسر اسٹیک اور allnodes-com.eth کا انعام
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![انڈیکسنگ سٹیک اور انعامات](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-یہ ڈیٹا فروری 2021 سے ستمبر 2022 تک کا ہے.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> براہ کرم نوٹ کریں، جب [آربٹرم مائیگریشن](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) مکمل ہو جائے گا تو اس میں بہتری آئے گی، جس سے نیٹ ورک پر حصہ لینے کے لیے گیس کی لاگت کافی کم ہو جائے گی.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## ٹوکن کی فراہمی: جلنا اور جاری کرنے
+## Token Supply: Burning & Issuance
 
-ابتدائی ٹوکن سپلائی 10 بلین GRT ہے، جس کا ہدف ہر سال 3% نئے اجراء کا ہے تاکہ انڈیکسرز کو سب گراف پر حصص مختص کرنے پر انعام دیا جا سکے۔ اس کا مطلب ہے کہ GRT ٹوکن کی کل سپلائی میں ہر سال 3% اضافہ ہو گا کیونکہ انڈیکسرز کو نیٹ ورک میں ان کے تعاون کے لیے نئے ٹوکن جاری کیے جاتے ہیں.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-گراف کو نئے ٹوکن کے اجراء کو پورا کرنے کے لیے متعدد برننگ میکانزم کے ساتھ ڈیزائن کیا گیا ہے۔ تقریباً 1% GRT سپلائی نیٹ ورک پر مختلف سرگرمیوں کے ذریعے سالانہ جل جاتی ہے، اور یہ تعداد بڑھ رہی ہے کیونکہ نیٹ ورک کی سرگرمیوں میں مسلسل اضافہ ہوتا جا رہا ہے۔ ان جلنے والی سرگرمیوں میں 0.5% ڈیلیگیشن ٹیکس شامل ہوتا ہے جب بھی کوئی ڈیلیگیٹر کسی انڈیکسر کو GRT ڈیلیگیٹس کرتا ہے، 1% کیوریشن ٹیکس جب کیوریٹرز سب گراف پر اشارہ کرتے ہیں، اور بلاک چین ڈیٹا کے لیے 1% کیوری کی فیس.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![کل جلے ہوئی GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-باقاعدگی سے ہونے والی ان جلنے والی سرگرمیوں کے علاوہ، GRT ٹوکن میں انڈیکسرز کی طرف سے بدنیتی پر مبنی یا غیر ذمہ دارانہ رویے کو سزا دینے کے لیے ایک سلیشنگ میکانزم بھی موجود ہے۔ اگر کسی انڈیکسر کو کم کیا جاتا ہے، تو ایپوچ کے لیے ان کے انڈیکسنگ کے انعامات کا 50% جلا دیا جاتا ہے (جبکہ بقیہ نصف فیشرمین کے پاس جاتا ہے)، اور ان کی سیلف سٹیک کو 2.5% تک کم کر دیا جاتا ہے، اس رقم کا آدھا حصہ جل جاتا ہے۔ اس سے اس بات کو یقینی بنانے میں مدد ملتی ہے کہ انڈیکسرز کو نیٹ ورک کے بہترین مفاد میں کام کرنے اور اس کی سلامتی اور استحکام میں حصہ ڈالنے کے لیے ایک مضبوط ترغیب حاصل ہے.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## پروٹوکول کو بہتر بنانا
+## Improving the Protocol
 
-گراف نیٹ ورک ہمیشہ تیار ہو رہا ہے اور پروٹوکول کے معاشی ڈیزائن میں مسلسل بہتری لائی جا رہی ہے تاکہ نیٹ ورک کے تمام شرکاء کو بہترین تجربہ فراہم کیا جا سکے۔ گراف کونسل پروٹوکول کی تبدیلیوں کی نگرانی کرتی ہے اور کمیونٹی ممبران کی شرکت کے لیے حوصلہ افزائی کی جاتی ہے۔ [گراف فورم](https://forum.thegraph.com/) میں پروٹوکول کی بہتری کے ساتھ شامل ہوں.
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From a3cdfae8b4d4fd8ff846cbd77b414fd68e2a4723 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:33 -0500
Subject: [PATCH 0452/1325] New translations tokenomics.mdx (Vietnamese)

---
 website/pages/vi/tokenomics.mdx | 44 ++++++++++++++-------------------
 1 file changed, 18 insertions(+), 26 deletions(-)

diff --git a/website/pages/vi/tokenomics.mdx b/website/pages/vi/tokenomics.mdx
index 6fa9686eec71..7b23de66edfc 100644
--- a/website/pages/vi/tokenomics.mdx
+++ b/website/pages/vi/tokenomics.mdx
@@ -1,21 +1,21 @@
 ---
 title: Tokenomics of The Graph Network
-description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token works.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## Tổng quan
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-The Graph is a decentralized protocol that enables easy access to blockchain data.
+## Specifics
 
-It's similar to a B2B2C model, except it is powered by a decentralized network of participants. Network participants work together to provide data to end users in exchange for GRT rewards. GRT is the work utility token that coordinates data providers and consumers. GRT serves as a utility for coordinating data providers and consumers within the network and incentivizes protocol participants to organize data effectively.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-The Graph indexes blockchain data similarly to how Google indexes the web. In fact, you may already be using The Graph without realizing it. If you've viewed the front end of a dapp that gets its data from a subgraph, you queried data from a subgraph!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-The Graph plays a crucial role in making blockchain data more accessible and enabling a marketplace for its exchange.
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
 ## The Roles of Network Participants
 
@@ -29,15 +29,15 @@ There are four primary network participants:
 
 4.  Indexers - Backbone of blockchain data
 
-Fishermen and Arbitrators are also integral to the network’s success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
 ![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Indexers are delegated GRT by Delegators increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1500 GRT in rewards annually.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
 There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
@@ -45,9 +45,9 @@ If you're reading this, you're capable of becoming a Delegator right now by head
 
 ## Curators (Earn GRT)
 
-Curators identify high-quality subgraphs, and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
 Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
@@ -75,25 +75,17 @@ Indexers are the backbone of The Graph. They operate independent hardware and so
 
 Indexers can earn GRT rewards in two ways:
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-2.  Indexing rewards: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs) verifying that they have indexed data accurately.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
 Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-In order to run an indexing node, Indexers must stake 100,000 GRT or more with the network. Indexers are incentivized to stake GRT in proportion to the amount of queries they serve.
-
-Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial stake), they will not be able to use the additional GRT from Delegators until they increase their stake in the network.
-
-The amount of rewards an Indexer receives can vary based on the initial stake, accepted delegation, quality of service, and many more factors. The following chart is publicly available data from an active Indexer on The Graph's decentralized network.
-
-### The Indexer stake & reward of allnodes-com.eth
-
-![Indexing stake and rewards](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-This data is from February 2021 to September 2022.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> Please note, this will improve when the [Arbitrum migration](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) is complete, making gas costs a significantly lower burden for participating on the network.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
 ## Token Supply: Burning & Issuance
 

From d81a60e1b1f70b93e953c362646dfb8e4c15cf98 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:34 -0500
Subject: [PATCH 0453/1325] New translations tokenomics.mdx (Marathi)

---
 website/pages/mr/tokenomics.mdx | 94 +++++++++++++++------------------
 1 file changed, 43 insertions(+), 51 deletions(-)

diff --git a/website/pages/mr/tokenomics.mdx b/website/pages/mr/tokenomics.mdx
index 08698f8c5f7a..d31fa89a55a7 100644
--- a/website/pages/mr/tokenomics.mdx
+++ b/website/pages/mr/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: ग्राफ नेटवर्कचे टोकनॉमिक्स
-description: ग्राफ नेटवर्क शक्तिशाली टोकनॉमिक्सद्वारे प्रोत्साहन दिले जाते. GET, The Graph चे नेटिव्ह वर्क युटिलिटी टोकन कसे कार्य करते ते येथे आहे.
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## सविश्लेषण
 
-- आर्बिट्रम वन वर GRT टोकन पत्ता: [0x9623063377AD1B27544C965cCd738](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-आलेख हा विकेंद्रित प्रोटोकॉल आहे जो ब्लॉकचेन डेटामध्ये सहज प्रवेश करण्यास सक्षम करतो.
+## Specifics
 
-हे B2B2C मॉडेलसारखेच आहे, शिवाय ते सहभागींच्या विकेंद्रित नेटवर्कद्वारे समर्थित आहे. नेटवर्क सहभागी GRT रिवॉर्डच्या बदल्यात अंतिम वापरकर्त्यांना डेटा प्रदान करण्यासाठी एकत्र काम करतात. GRT हे कार्य उपयुक्तता टोकन आहे जे डेटा प्रदाते आणि ग्राहकांना समन्वयित करते. GRT नेटवर्कमधील डेटा प्रदाते आणि ग्राहकांमध्ये समन्वय साधण्यासाठी उपयुक्तता म्हणून काम करते आणि प्रोटोकॉल सहभागींना डेटा प्रभावीपणे व्यवस्थित करण्यासाठी प्रोत्साहन देते.
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-By using The Graph, users can easily access data from the blockchain, paying only for the specific information they need. The Graph is used by many [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem today.
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-Google वेब कसे अनुक्रमित करते त्याचप्रमाणे आलेख ब्लॉकचेन डेटा अनुक्रमित करतो. खरं तर, तुम्ही कदाचित आधीच The Graph वापरत असाल ते लक्षात न घेता. तुम्ही सबग्राफ वरून डेटा मिळवणाऱ्या dapp चे पुढचे टोक पाहिले असल्यास, तुम्ही सबग्राफ वरून डेटा विचारला आहे!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-ब्लॉकचेन डेटा अधिक सुलभ बनवण्यात आणि त्याच्या एक्सचेंजसाठी मार्केटप्लेस सक्षम करण्यात आलेख महत्त्वपूर्ण भूमिका बजावते.
+- आर्बिट्रम वन वर GRT टोकन पत्ता: [0x9623063377AD1B27544C965cCd738](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## नेटवर्क सहभागींची भूमिका
+## The Roles of Network Participants
 
-चार प्राथमिक नेटवर्क सहभागी आहेत:
+There are four primary network participants:
 
 1.  प्रतिनिधी - GRT इंडेक्सर्सना सोपवा & नेटवर्क सुरक्षित करा
 
@@ -29,82 +29,74 @@ Google वेब कसे अनुक्रमित करते त्या
 
 4.  इंडेक्सर्स - ब्लॉकचेन डेटाचा कणा
 
-मच्छीमार आणि मध्यस्थ हे देखील इतर योगदानांद्वारे नेटवर्कच्या यशासाठी अविभाज्य आहेत, इतर प्राथमिक सहभागी भूमिकांच्या कार्यास समर्थन देतात. नेटवर्क भूमिकांबद्दल अधिक माहितीसाठी, [हा लेख वाचा](https://thegraph.com/blog/the-graph-grt-token-economics/).
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![टोकनॉमिक्स आकृती](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
-## प्रतिनिधी (निष्क्रियपणे GRT कमवा)
+## Delegators (Passively earn GRT)
 
-इंडेक्सर्सना नेटवर्कवरील सबग्राफमध्ये इंडेक्सरचा स्टेक वाढवून प्रतिनिधींद्वारे GRT दिला जातो. त्या बदल्यात, प्रतिनिधी सर्व क्वेरी फी आणि इंडेक्सरकडून अनुक्रमित बक्षिसे मिळवतात. प्रत्येक इंडेक्सर स्वतंत्रपणे प्रतिनिधींना बक्षीस देणारा कट सेट करतो, ज्यामुळे प्रतिनिधींना आकर्षित करण्यासाठी इंडेक्सर्समध्ये स्पर्धा निर्माण होते. बहुतेक इंडेक्सर्स वार्षिक 9-12% च्या दरम्यान ऑफर करतात.
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-उदाहरणार्थ, जर प्रतिनिधीने 10% ऑफर करणार्‍या इंडेक्सरला 15k GRT सोपवायचे असेल, तर प्रतिनिधीला वार्षिक ~1500 GRT बक्षिसे मिळतील.
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-0.5% डेलिगेशन कर आहे जो जेव्हा जेव्हा प्रतिनिधी नेटवर्कवर GRT नियुक्त करतो तेव्हा बर्न केला जातो. जर एखाद्या प्रतिनिधीने त्यांचे प्रतिनिधी GRT मागे घेणे निवडले तर, प्रतिनिधीने 28-युग अनबॉन्डिंग कालावधीची प्रतीक्षा करणे आवश्यक आहे. प्रत्येक युग 6,646 ब्लॉक्सचा असतो, म्हणजे 28 युगे अंदाजे 26 दिवसांचे असतात.
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-तुम्ही हे वाचत असल्यास, तुम्ही सध्या [नेटवर्क सहभागी पृष्ठावर](https://thegraph.com/explorer/participants/indexers) जाऊन प्रतिनिधी बनण्यास सक्षम आहात आणि तुमच्या आवडीच्या इंडेक्सरला GRT सोपवणे.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## क्युरेटर (GRT मिळवा)
+## Curators (Earn GRT)
 
-क्युरेटर्स उच्च-गुणवत्तेचे सबग्राफ ओळखतात आणि क्युरेशन शेअर्स मिळविण्यासाठी त्यांना "क्युरेट" करतात (म्हणजे त्यांच्यावर GRT सिग्नल करतात), जे सबग्राफद्वारे व्युत्पन्न केलेल्या भविष्यातील सर्व क्वेरी फीच्या टक्केवारीची हमी देतात. कोणताही स्वतंत्र नेटवर्क सहभागी क्युरेटर असू शकतो, सामान्यत: सबग्राफ डेव्हलपर त्यांच्या स्वत: च्या सबग्राफसाठी प्रथम क्युरेटर्समध्ये असतात कारण त्यांना त्यांचा सबग्राफ इंडेक्स केलेला असल्याची खात्री करायची असते.
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-क्युरेटर जेव्हा नवीन सबग्राफ क्युरेट करतात तेव्हा 1% क्युरेशन कर भरतात. हा क्युरेशन कर बर्न केला जातो, जीआरटीचा पुरवठा कमी होतो.
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## विकसक
+## Developers
 
-विकासक ब्लॉकचेन डेटा पुनर्प्राप्त करण्यासाठी सबग्राफ तयार करतात आणि क्वेरी करतात. सबग्राफ हे ओपन सोर्स असल्याने, डेव्हलपर त्यांच्या डॅप्समध्ये ब्लॉकचेन डेटा लोड करण्यासाठी विद्यमान सबग्राफची चौकशी करू शकतात. विकासक GRT मध्ये केलेल्या प्रश्नांसाठी पैसे देतात, जे नेटवर्क सहभागींना वितरित केले जाते.
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### सबग्राफ तयार करणे
 
-ब्लॉकचेनवरील डेटा अनुक्रमित करण्यासाठी विकसक [सबग्राफ तयार करू शकतात](/developing/creating-a-subgraph/). सबग्राफ हे इंडेक्सर्ससाठी निर्देश आहेत जे ग्राहकांना कोणता डेटा दिला जावा.
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-एकदा विकासकांनी त्यांचा सबग्राफ तयार केला आणि तपासला की, ते ग्राफच्या विकेंद्रित नेटवर्कवर [त्यांचा सबग्राफ प्रकाशित करू शकतात](/publishing/publishing-a-subgraph/).
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### विद्यमान सबग्राफची चौकशी करत आहे
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-सबग्राफ [GraphQL वापरून विचारले जातात](/querying/querying-the-graph/), आणि क्वेरी शुल्कासाठी GRT सह [सबग्राफ स्टुडिओ](https://thegraph.com/studio मध्ये पैसे दिले जातात /). प्रोटोकॉलमधील त्यांच्या योगदानाच्या आधारावर नेटवर्क सहभागींना क्वेरी फी वितरित केली जाते.
-
-नेटवर्कला भरलेल्या क्वेरी फीपैकी 1% बर्न केली जाते.
-
-## इंडेक्सर्स (GRT मिळवा)
-
-इंडेक्सर्स हा ग्राफचा कणा आहे. ते ग्राफच्या विकेंद्रित नेटवर्कला शक्ती देणारे स्वतंत्र हार्डवेअर आणि सॉफ्टवेअर चालवतात. इंडेक्सर्स सबग्राफच्या सूचनांवर आधारित ग्राहकांना डेटा देतात.
-
-इंडेक्सर्स दोन प्रकारे GRT रिवॉर्ड मिळवू शकतात:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  इंडेक्सिंग रिवॉर्ड्स: 3% वार्षिक जारी इंडेक्सर्सना ते अनुक्रमित करत असलेल्या सबग्राफच्या संख्येवर आधारित वितरीत केले जातात. हे रिवॉर्ड्स इंडेक्सर्सना अनुक्रमणिका सबग्राफसाठी प्रोत्साहन देतात, कधीकधी क्वेरी फी सुरू होण्यापूर्वी, त्यांनी डेटा अचूकपणे अनुक्रमित केला आहे याची पडताळणी करून प्रूफ ऑफ इंडेक्सिंग (POI) जमा करणे आणि सबमिट करणे.
+## Indexers (Earn GRT)
 
-प्रत्येक सबग्राफला सबग्राफच्या क्युरेशन सिग्नलच्या रकमेवर आधारित, एकूण नेटवर्क टोकन जारी करण्याचा एक भाग दिला जातो. त्यानंतर ती रक्कम इंडेक्सर्सना त्यांच्या सबग्राफवर वाटप केलेल्या स्टेकच्या आधारे पुरस्कृत केली जाते.
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-इंडेक्सिंग नोड चालवण्‍यासाठी, इंडेक्सर्सनी नेटवर्कसह 100,000 GRT किंवा अधिक स्‍टेक करणे आवश्‍यक आहे. इंडेक्सर्सना त्यांनी दिलेल्या प्रश्नांच्या प्रमाणात GRT ला भाग पाडण्यासाठी प्रोत्साहन दिले जाते.
+Indexers can earn GRT rewards in two ways:
 
-इंडेक्सर्स प्रतिनिधींकडून GRT प्रतिनिधीत्व स्वीकारून सबग्राफवर त्यांचे GRT वाटप वाढवू शकतात आणि ते त्यांच्या सुरुवातीच्या 16 पट पर्यंत स्वीकारू शकतात. जर एखादा इंडेक्सर "ओव्हर-डेलिगेटेड" झाला (म्हणजेच, त्यांच्या सुरुवातीच्या स्टेकच्या 16 पट पेक्षा जास्त), तर ते नेटवर्कमधील त्यांचा स्टेक वाढवत नाहीत तोपर्यंत ते डेलिगेटर्सकडून अतिरिक्त GRT वापरू शकणार नाहीत.
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
 
-इंडेक्सरला मिळणाऱ्या बक्षिसेची रक्कम प्रारंभिक स्टेक, स्वीकृत प्रतिनिधी, सेवेची गुणवत्ता आणि इतर अनेक घटकांवर आधारित बदलू शकते. ग्राफच्या विकेंद्रीकृत नेटवर्कवरील सक्रिय इंडेक्सरकडून खालील तक्ता सार्वजनिकरित्या उपलब्ध डेटा आहे.
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
 
-### इंडेक्सर स्टेक & allnodes-com.eth चे बक्षीस
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![इंडेक्सिंग स्टेक आणि रिवॉर्ड्स](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-हा डेटा फेब्रुवारी 2021 ते सप्टेंबर 2022 पर्यंतचा आहे.
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> कृपया लक्षात ठेवा, जेव्हा [आर्बिट्रम माइग्रेशन](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) पूर्ण झाले आहे, ज्यामुळे नेटवर्कवर सहभागी होण्यासाठी गॅसची किंमत लक्षणीयरीत्या कमी होते.
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## टोकन पुरवठा: बर्निंग & जारी करणे
+## Token Supply: Burning & Issuance
 
-प्रारंभिक टोकन पुरवठा 10 अब्ज GRT आहे, ज्यामध्ये सबग्राफवर स्टेक वाटप केल्याबद्दल इंडेक्सर्सना बक्षीस देण्यासाठी वार्षिक 3% नवीन जारी करण्याचे लक्ष्य आहे. याचा अर्थ असा की GRT टोकनचा एकूण पुरवठा दरवर्षी 3% ने वाढेल कारण इंडेक्सर्सना त्यांच्या नेटवर्कमधील योगदानासाठी नवीन टोकन जारी केले जातात.
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-नवीन टोकन जारी करणे ऑफसेट करण्यासाठी आलेख अनेक बर्निंग यंत्रणेसह डिझाइन केले आहे. नेटवर्कवरील विविध क्रियाकलापांद्वारे अंदाजे 1% GRT पुरवठा दरवर्षी बर्न केला जातो आणि नेटवर्क क्रियाकलाप वाढत असताना ही संख्या वाढत आहे. या बर्निंग अ‍ॅक्टिव्हिटींमध्ये जेव्हा एखादा प्रतिनिधी इंडेक्सरला GRT सोपवतो तेव्हा 0.5% डेलिगेशन कर, सबग्राफवर क्युरेटर सिग्नल करतात तेव्हा 1% क्युरेशन टॅक्स आणि ब्लॉकचेन डेटासाठी 1% क्वेरी शुल्क यांचा समावेश होतो.
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![एकूण बर्न GRT](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-या नियमितपणे होणार्‍या बर्निंग अ‍ॅक्टिव्हिटींव्यतिरिक्त, GRT टोकनमध्ये इंडेक्सर्सच्या दुर्भावनापूर्ण किंवा बेजबाबदार वर्तनास दंड करण्यासाठी एक स्लॅशिंग यंत्रणा देखील आहे. जर एखादा इंडेक्सर कमी केला गेला, तर त्या युगासाठी त्यांच्या अनुक्रमणिकेतील 50% बक्षिसे जाळून टाकली जातात (तर अर्धा भाग मच्छिमाराकडे जातो), आणि त्यांचा स्व-स्टेक 2.5% ने कमी केला जातो, यापैकी अर्धी रक्कम जाळली जाते. हे सुनिश्चित करण्यात मदत करते की इंडेक्सर्सना नेटवर्कच्या सर्वोत्कृष्ट हितासाठी कार्य करण्यासाठी आणि त्याच्या सुरक्षितता आणि स्थिरतेमध्ये योगदान देण्यासाठी मजबूत प्रोत्साहन आहे.
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## प्रोटोकॉल सुधारणे
+## Improving the Protocol
 
-ग्राफ नेटवर्क सतत विकसित होत आहे आणि सर्व नेटवर्क सहभागींना सर्वोत्तम अनुभव प्रदान करण्यासाठी प्रोटोकॉलच्या आर्थिक डिझाइनमध्ये सतत सुधारणा केल्या जात आहेत. आलेख परिषद प्रोटोकॉल बदलांचे निरीक्षण करते आणि समुदाय सदस्यांना सहभागी होण्यासाठी प्रोत्साहित केले जाते. [द ग्राफ फोरम](https://forum.thegraph.com/) मधील प्रोटोकॉल सुधारणांमध्ये सहभागी व्हा.
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 7cc54583d7d80011a0798a514c755620e574e7f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:35 -0500
Subject: [PATCH 0454/1325] New translations tokenomics.mdx (Hindi)

---
 website/pages/hi/tokenomics.mdx | 92 +++++++++++++++------------------
 1 file changed, 42 insertions(+), 50 deletions(-)

diff --git a/website/pages/hi/tokenomics.mdx b/website/pages/hi/tokenomics.mdx
index 606a0519b1bb..b643a3aeaa90 100644
--- a/website/pages/hi/tokenomics.mdx
+++ b/website/pages/hi/tokenomics.mdx
@@ -1,25 +1,25 @@
 ---
 title: ग्राफ नेटवर्क के टोकनोमिक्स
-description: ग्राफ़ नेटवर्क को शक्तिशाली टोकन अर्थशास्त्र द्वारा प्रोत्साहित किया जाता है। यहां बताया गया है कि कैसे GET, ग्राफ़ का मूल कार्य उपयोगिता टोकन काम करता है।
+description: The Graph Network को शक्तिशाली टोकनोमिक्स द्वारा प्रोत्साहित किया जाता है। यहां बताया गया है कि GRT, The Graph का मूल कार्य उपयोगिता टोकन, कैसे काम करता है।
 ---
 
-- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+## अवलोकन
 
-- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
 
-ग्राफ़ एक विकेन्द्रीकृत प्रोटोकॉल है जो ब्लॉकचैन डेटा तक आसान पहुंच को सक्षम बनाता है।
+## विशिष्टताएँ
 
-ग्राफ़ एक विकेन्द्रीकृत प्रोटोकॉल है जो ब्लॉकचैन डेटा तक आसान पहुंच को सक्षम बनाता है। यह B2B2C मॉडल के समान है, सिवाय इसके कि यह प्रतिभागियों के विकेंद्रीकृत नेटवर्क द्वारा संचालित है। जीआरटी पुरस्कारों के बदले अंतिम उपयोगकर्ताओं को डेटा प्रदान करने के लिए नेटवर्क प्रतिभागी एक साथ काम करते हैं। जीआरटी कार्य उपयोगिता टोकन है जो डेटा प्रदाताओं और उपभोक्ताओं का समन्वय करता है। GRT नेटवर्क के भीतर डेटा प्रदाताओं और उपभोक्ताओं के समन्वय के लिए एक उपयोगिता के रूप में कार्य करता है और डेटा को प्रभावी ढंग से व्यवस्थित करने के लिए प्रोटोकॉल प्रतिभागियों को प्रोत्साहित करता है।
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
 
-Graph का उपयोग करके, users आसानी से blockchain से data तक पहुँच सकते हैं, केवल उन specific information के लिए भुगतान करते हुए जो उन्हें आवश्यक होती है। आज web3 ecosystem में कई [popular dapps](https://thegraph.com/explorer) द्वारा Graph का उपयोग किया जाता है।
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
 
-Graph blockchain data को उसी तरह indexes करता है जैसे Google web को indexes करता है। In fact, हो सकता है कि आप पहले से ही Graph का उपयोग बिना इसे जाने कर रहे हों। यदि आपने एक dapp के front end को देखा है जो एक subgraph से अपना data प्राप्त करता है, तो आपने एक subgraph से data की query की है!
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
 
-Blockchain data को अधिक accessible बनाने और इसके exchange के लिए बाज़ार को सक्षम करने में Graph एक महत्वपूर्ण भूमिका निभाता है।
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
 
-## नेटवर्क प्रतिभागियों की भूमिकाएँ
+## The Roles of Network Participants
 
-चार प्राथमिक नेटवर्क प्रतिभागी हैं:
+There are four primary network participants:
 
 1.  डेलिगेटर्स - इंडेक्सर्स और amp के लिए GRT डेलिगेट करें; नेटवर्क को सुरक्षित करें
 
@@ -29,82 +29,74 @@ Blockchain data को अधिक accessible बनाने और इसक
 
 4.  इंडेक्सर्स - ब्लॉकचेन डेटा की रीढ़
 
-मछुआरे और मध्यस्थ भी अन्य प्राथमिक भागीदार भूमिकाओं के काम का समर्थन करते हुए, अन्य योगदानों के माध्यम से नेटवर्क की सफलता के अभिन्न अंग हैं। नेटवर्क भूमिकाओं के बारे में अधिक जानकारी के लिए, [यह लेख पढ़ें](https://thegraph.com/blog/the-graph-grt-token-economics/)।
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
 
-![टोकनोमिक्स आरेख](/img/updated-tokenomics-image.png)
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
 
 ## Delegators (Passively earn GRT)
 
-Network पर subgraphs में Indexers की हिस्सेदारी बढ़ाने वाले Delegators द्वारा Indexer’s को GRT प्रत्यायोजित किया जाता है। बदले में, Delegators Indexer से सभी query fees और indexing rewards का एक प्रतिशत अर्जित करते हैं। प्रत्येक Indexer cut set करता है जिसे Delegators को independent रूप से rewarded किया जाएगा, जिससे Delegators को attract करने के लिए Indexers के बीच competition पैदा होगी। Most Indexers सालाना 9-12% के बीच का offer करते हैं।
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
 
-उदाहरण के लिए, यदि एक डेलिगेटर को 10% की पेशकश करने वाले इंडेक्सर को 15k GRT प्रत्यायोजित करना होता है, तो डेलिगेटर को सालाना पुरस्कारों में ~1500 GRT प्राप्त होगा।
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
 
-एक 0.5% डेलिगेशन टैक्स है, जो तब नष्ट हो जाता है जब कोई डेलिगेटर नेटवर्क पर GRT को प्रत्यायोजित करता है। यदि एक प्रतिनिधि अपने प्रत्यायोजित जीआरटी को वापस लेने का विकल्प चुनता है, तो प्रतिनिधि को 28-युग की अनबंडिंग अवधि के लिए प्रतीक्षा करनी होगी। प्रत्येक युग 6,646 ब्लॉक है, जिसका अर्थ है कि 28 युग लगभग 26 दिनों में समाप्त होते हैं।
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
 
-यदि आप इसे पढ़ रहे हैं, तो आप [नेटवर्क सहभागी पृष्ठ](https://thegraph.com/explorer/participants/indexers) पर जाकर अभी प्रतिनिधि बनने में सक्षम हैं, और अपनी पसंद के इंडेक्सर को GRT सौंपना.
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
 
-## क्यूरेटर (जीआरटी अर्जित करें)
+## Curators (Earn GRT)
 
-क्यूरेटर उच्च-गुणवत्ता वाले सबग्राफ की पहचान करते हैं, और क्यूरेशन शेयर अर्जित करने के लिए उन्हें "क्यूरेट" करते हैं (यानी, उन पर जीआरटी का संकेत देते हैं), जो सबग्राफ द्वारा उत्पन्न सभी भविष्य की क्वेरी फीस के प्रतिशत की गारंटी देते हैं। जबकि कोई भी स्वतंत्र नेटवर्क प्रतिभागी क्यूरेटर हो सकता है, आमतौर पर सबग्राफ डेवलपर्स अपने स्वयं के सबग्राफ के लिए पहले क्यूरेटर में से होते हैं क्योंकि वे यह सुनिश्चित करना चाहते हैं कि उनका सबग्राफ अनुक्रमित हो।
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
 
-As of April 11th, 2024, subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
 
-जब क्यूरेटर एक नया सबग्राफ तैयार करते हैं तो क्यूरेटर 1% क्यूरेशन टैक्स का भुगतान करते हैं। इस क्यूरेशन टैक्स को जला दिया जाता है, जिससे जीआरटी की आपूर्ति घट जाती है।
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
 
-## डेवलपर्स
+## Developers
 
-ब्लॉकचैन डेटा को पुनः प्राप्त करने के लिए डेवलपर्स सबग्राफ बनाते हैं और क्वेरी करते हैं। चूंकि सबग्राफ ओपन सोर्स हैं, इसलिए डेवलपर्स ब्लॉकचेन डेटा को अपने डैप में लोड करने के लिए मौजूदा सबग्राफ को क्वेरी कर सकते हैं। डेवलपर्स जीआरटी में किए गए प्रश्नों के लिए भुगतान करते हैं, जो नेटवर्क प्रतिभागियों को वितरित किया जाता है।
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
 
 ### सबग्राफ बनाना
 
-ब्लॉकचैन पर डेटा इंडेक्स करने के लिए डेवलपर [सबग्राफ बना सकते हैं](/developing/creating-a-subgraph/)। सबग्राफ इंडेक्सर्स के लिए निर्देश हैं जिसके बारे में उपभोक्ताओं को डेटा परोसा जाना चाहिए।
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
 
-एक बार जब डेवलपर अपना सबग्राफ बना लेते हैं और उसका परीक्षण कर लेते हैं, तो वे ग्राफ़ के विकेंद्रीकृत नेटवर्क पर [अपना सबग्राफ़ प्रकाशित](/publishing/publishing-a-subgraph/) कर सकते हैं।
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
 
 ### किसी मौजूदा सबग्राफ को क्वेरी करना
 
 Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
 
-सबग्राफ [GraphQL का उपयोग करके पूछताछ की जाती है](/querying/querying-the-graph/), और क्वेरी शुल्क का भुगतान [सबग्राफ स्टूडियो](https://thegraph.com/studio में जीआरटी के साथ किया जाता है /)। प्रोटोकॉल में उनके योगदान के आधार पर नेटवर्क प्रतिभागियों को क्वेरी शुल्क वितरित किया जाता है।
-
-नेटवर्क को भुगतान किए गए क्वेरी शुल्क का 1% नष्ट हो जाता है।
-
-## इंडेक्सर्स (जीआरटी अर्जित करें)
-
-इंडेक्सर्स द ग्राफ की रीढ़ हैं। वे ग्राफ़ के विकेंद्रीकृत नेटवर्क को सशक्त बनाने वाले स्वतंत्र हार्डवेयर और सॉफ़्टवेयर संचालित करते हैं। इंडेक्सर्स सबग्राफ के निर्देशों के आधार पर उपभोक्ताओं को डेटा प्रदान करते हैं।
-
-अनुक्रमणकर्ता दो तरह से GRT पुरस्कार अर्जित कर सकते हैं:
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
 
-1.  Query fees: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+1% of the query fees paid to the network are burned.
 
-2.  इंडेक्सिंग रिवार्ड्स: 3% वार्षिक निर्गमन इंडेक्सर्स को उनके द्वारा इंडेक्स किए जाने वाले सबग्राफ की संख्या के आधार पर वितरित किया जाता है। ये पुरस्कार अनुक्रमणकों को उप-अनुच्छेदों को अनुक्रमणित करने के लिए प्रोत्साहित करते हैं, कभी-कभी क्वेरी शुल्क शुरू होने से पहले, यह सत्यापित करने के लिए कि उन्होंने डेटा को सटीक रूप से अनुक्रमित किया है, अनुक्रमणिका (POIs) के प्रमाण अर्जित करने और जमा करने के लिए।
+## Indexers (Earn GRT)
 
-सबग्राफ के क्यूरेशन सिग्नल की मात्रा के आधार पर, प्रत्येक सबग्राफ को कुल नेटवर्क टोकन जारी करने का एक हिस्सा आवंटित किया जाता है। उस राशि को तब सबग्राफ पर आवंटित हिस्सेदारी के आधार पर इंडेक्सर्स को पुरस्कृत किया जाता है।
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
 
-इंडेक्सिंग नोड को चलाने के लिए, इंडेक्सर्स को नेटवर्क के साथ 100,000 GRT या उससे अधिक का दांव लगाना चाहिए। इंडेक्सर्स को उनके द्वारा दी जाने वाली क्वेरी की मात्रा के अनुपात में GRT को दांव पर लगाने के लिए प्रोत्साहित किया जाता है।
+Indexers can earn GRT rewards in two ways:
 
-इंडेक्सर्स, प्रतिनिधियों से जीआरटी प्रतिनिधिमंडल को स्वीकार करके सबग्राफ पर अपने जीआरटी आवंटन बढ़ा सकते हैं, और वे अपनी प्रारंभिक हिस्सेदारी का 16 गुना तक स्वीकार कर सकते हैं। यदि कोई इंडेक्सर "अति-प्रत्यायोजित" हो जाता है (अर्थात्, उनकी प्रारंभिक हिस्सेदारी का 16 गुना से अधिक), तो वे डेलिगेटर से अतिरिक्त जीआरटी का उपयोग तब तक नहीं कर पाएंगे जब तक कि वे नेटवर्क में अपनी हिस्सेदारी नहीं बढ़ाते।
+1.  **क्वेरी शुल्क**: डेवलपर्स या उपयोगकर्ताओं द्वारा subgraph डेटा क्वेरी के लिए भुगतान किए गए GRT। क्वेरी शुल्क सीधे गुणात्मक रिबेट फंक्शन के अनुसार Indexers को वितरित किए जाते हैं (GIP [यहां](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162) देखें)।
 
-इंडेक्सर को प्राप्त होने वाले पुरस्कारों की राशि प्रारंभिक हिस्सेदारी, स्वीकृत प्रतिनिधिमंडल, सेवा की गुणवत्ता और कई अन्य कारकों के आधार पर भिन्न हो सकती है। निम्नलिखित चार्ट ग्राफ़ के विकेन्द्रीकृत नेटवर्क पर एक सक्रिय इंडेक्सर से सार्वजनिक रूप से उपलब्ध डेटा है।
+2.  **इंडेक्सिंग रिवार्ड्स**: 3% वार्षिक इश्यूअंस उन Indexers को वितरित किया जाता है, जो वे कितने subgraphs को इंडेक्स कर रहे हैं, उस पर आधारित होता है। ये रिवार्ड्स Indexers को subgraphs को इंडेक्स करने के लिए प्रेरित करते हैं, कभी-कभी query fees शुरू होने से पहले, ताकि वे Proofs of Indexing (POIs) एकत्रित और सबमिट कर सकें, यह सत्यापित करने के लिए कि उन्होंने डेटा को सही ढंग से इंडेक्स किया है।
 
-### इंडेक्सर हिस्सेदारी & allnodes-com.eth का इनाम
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
 
-![अनुक्रमण हिस्सेदारी और पुरस्कार](/img/indexing-stake-and-income.png)
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
 
-यह डेटा फरवरी 2021 से सितंबर 2022 तक का है।
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
 
-> कृपया ध्यान दें, [आर्बिट्रम माइग्रेशन](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551) पूरा होने पर इसमें सुधार होगा, जिससे नेटवर्क पर भाग लेने के लिए गैस की लागत काफी कम हो जाएगी।
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
 
-## टोकन आपूर्ति: जलन & जारी करने, निर्गमन
+## Token Supply: Burning & Issuance
 
-प्रारंभिक टोकन आपूर्ति 10 बिलियन जीआरटी है, जिसमें सबग्राफ पर हिस्सेदारी आवंटित करने के लिए इंडेक्सर्स को पुरस्कृत करने के लिए सालाना 3% नए जारी करने का लक्ष्य है। इसका मतलब यह है कि इंडेक्सर्स को नेटवर्क में उनके योगदान के लिए नए टोकन जारी किए जाने के कारण जीआरटी टोकन की कुल आपूर्ति में हर साल 3% की वृद्धि होगी।
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
 
-नए टोकन जारी करने की भरपाई के लिए ग्राफ को कई बर्निंग मैकेनिज्म के साथ डिजाइन किया गया है। नेटवर्क पर विभिन्न गतिविधियों के माध्यम से सालाना GRT आपूर्ति का लगभग 1% नष्ट हो जाता है, और यह संख्या बढ़ रही है क्योंकि नेटवर्क गतिविधि लगातार बढ़ रही है। इन ज्वलंत गतिविधियों में 0.5% डेलिगेशन टैक्स शामिल है जब भी कोई डेलिगेटर किसी इंडेक्सर को GRT सौंपता है, क्यूरेटर द्वारा सबग्राफ पर संकेत देने पर 1% क्यूरेशन टैक्स, और ब्लॉकचैन डेटा के लिए 1% क्वेरी शुल्क शामिल होता है।
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
 
-![कुल जला जीआरटी](/img/total-burned-grt.jpeg)
+![Total burned GRT](/img/total-burned-grt.jpeg)
 
-इन नियमित रूप से होने वाली ज्वलनशील गतिविधियों के अलावा, इंडेक्सर्स द्वारा दुर्भावनापूर्ण या गैर-जिम्मेदाराना व्यवहार को दंडित करने के लिए जीआरटी टोकन में एक स्लेशिंग तंत्र भी है। यदि एक इंडेक्सर को घटाया जाता है, तो युग के लिए उनके इंडेक्सिंग पुरस्कारों का 50% नष्ट हो जाता है (जबकि अन्य आधा मछुआरे के पास जाता है), और उनकी स्वयं की हिस्सेदारी 2.5% कम हो जाती है, इस राशि का आधा हिस्सा जला दिया जाता है। यह सुनिश्चित करने में मदद करता है कि इंडेक्सर्स के पास नेटवर्क के सर्वोत्तम हित में कार्य करने और इसकी सुरक्षा और स्थिरता में योगदान करने के लिए एक मजबूत प्रोत्साहन है।
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
 
-## प्रोटोकॉल में सुधार
+## Improving the Protocol
 
-ग्राफ नेटवर्क लगातार विकसित हो रहा है और सभी नेटवर्क प्रतिभागियों के लिए सबसे अच्छा अनुभव प्रदान करने के लिए प्रोटोकॉल के आर्थिक डिजाइन में लगातार सुधार किए जा रहे हैं। ग्राफ काउंसिल प्रोटोकॉल परिवर्तनों की देखरेख करती है और समुदाय के सदस्यों को भाग लेने के लिए प्रोत्साहित किया जाता है। [द ग्राफ़ फ़ोरम](https://forum.thegraph.com/) में प्रोटोकॉल सुधारों में शामिल हों।
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From b80ef68981c5de581cc7d88d287bde9c6bce1e1c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:36 -0500
Subject: [PATCH 0455/1325] New translations tokenomics.mdx (Swahili)

---
 website/pages/sw/tokenomics.mdx | 102 ++++++++++++++++++++++++++++++++
 1 file changed, 102 insertions(+)
 create mode 100644 website/pages/sw/tokenomics.mdx

diff --git a/website/pages/sw/tokenomics.mdx b/website/pages/sw/tokenomics.mdx
new file mode 100644
index 000000000000..e2e4c904000d
--- /dev/null
+++ b/website/pages/sw/tokenomics.mdx
@@ -0,0 +1,102 @@
+---
+title: Tokenomics of The Graph Network
+description: The Graph Network is incentivized by powerful tokenomics. Here’s how GRT, The Graph’s native work utility token, works.
+---
+
+## Overview
+
+The Graph is a decentralized protocol that enables easy access to blockchain data. It indexes blockchain data similarly to how Google indexes the web. If you've used a dapp that retrieves data from a subgraph, you've probably interacted with The Graph. Today, thousands of [popular dapps](https://thegraph.com/explorer) in the web3 ecosystem use The Graph.
+
+## Specifics
+
+The Graph's model is akin to a B2B2C model, but it's driven by a decentralized network where participants collaborate to provide data to end users in exchange for GRT rewards. GRT is the utility token for The Graph. It coordinates and incentivizes the interaction between data providers and consumers within the network.
+
+The Graph plays a vital role in making blockchain data more accessible and supports a marketplace for its exchange. To learn more about The Graph's pay-for-what-you-need model, check out its [free and growth plans](/billing/).
+
+- GRT Token Address on Mainnet: [0xc944e90c64b2c07662a292be6244bdf05cda44a7](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)
+
+- GRT Token Address on Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+
+## The Roles of Network Participants
+
+There are four primary network participants:
+
+1.  Delegators - Delegate GRT to Indexers & secure the network
+
+2.  Curators - Find the best subgraphs for Indexers
+
+3.  Developers - Build & query subgraphs
+
+4.  Indexers - Backbone of blockchain data
+
+Fishermen and Arbitrators are also integral to the network's success through other contributions, supporting the work of the other primary participant roles. For more information about network roles, [read this article](https://thegraph.com/blog/the-graph-grt-token-economics/).
+
+![Tokenomics diagram](/img/updated-tokenomics-image.png)
+
+## Delegators (Passively earn GRT)
+
+Indexers are delegated GRT by Delegators, increasing the Indexer’s stake in subgraphs on the network. In return, Delegators earn a percentage of all query fees and indexing rewards from the Indexer. Each Indexer sets the cut that will be rewarded to Delegators independently, creating competition among Indexers to attract Delegators. Most Indexers offer between 9-12% annually.
+
+For example, if a Delegator were to delegate 15k GRT to an Indexer offering 10%, the Delegator would receive ~1,500 GRT in rewards annually.
+
+There is a 0.5% delegation tax which is burned whenever a Delegator delegates GRT on the network. If a Delegator chooses to withdraw their delegated GRT, the Delegator must wait for the 28-epoch unbonding period. Each epoch is 6,646 blocks, which means 28 epochs ends up being approximately 26 days.
+
+If you're reading this, you're capable of becoming a Delegator right now by heading to the [network participants page](https://thegraph.com/explorer/participants/indexers), and delegating GRT to an Indexer of your choice.
+
+## Curators (Earn GRT)
+
+Curators identify high-quality subgraphs and "curate" them (i.e., signal GRT on them) to earn curation shares, which guarantee a percentage of all future query fees generated by the subgraph. While any independent network participant can be a Curator, typically subgraph developers are among the first Curators for their own subgraphs because they want to ensure their subgraph is indexed.
+
+Subgraph developers are encouraged to curate their subgraph with at least 3,000 GRT. However, this number may be impacted by network activity and community participation.
+
+Curators pay a 1% curation tax when they curate a new subgraph. This curation tax is burned, decreasing the supply of GRT.
+
+## Developers
+
+Developers build and query subgraphs to retrieve blockchain data. Since subgraphs are open source, developers can query existing subgraphs to load blockchain data into their dapps. Developers pay for queries they make in GRT, which is distributed to network participants.
+
+### Creating a subgraph
+
+Developers can [create a subgraph](/developing/creating-a-subgraph/) to index data on the blockchain. Subgraphs are instructions for Indexers about which data should be served to consumers.
+
+Once developers have built and tested their subgraph, they can [publish their subgraph](/publishing/publishing-a-subgraph/) on The Graph's decentralized network.
+
+### Querying an existing subgraph
+
+Once a subgraph is [published](/publishing/publishing-a-subgraph/) to The Graph's decentralized network, anyone can create an API key, add GRT to their billing balance, and query the subgraph.
+
+Subgraphs are [queried using GraphQL](/querying/querying-the-graph/), and the query fees are paid for with GRT in [Subgraph Studio](https://thegraph.com/studio/). Query fees are distributed to network participants based on their contributions to the protocol.
+
+1% of the query fees paid to the network are burned.
+
+## Indexers (Earn GRT)
+
+Indexers are the backbone of The Graph. They operate independent hardware and software powering The Graph’s decentralized network. Indexers serve data to consumers based on instructions from subgraphs.
+
+Indexers can earn GRT rewards in two ways:
+
+1.  **Query fees**: GRT paid by developers or users for subgraph data queries. Query fees are directly distributed to Indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)).
+
+2.  **Indexing rewards**: the 3% annual issuance is distributed to Indexers based on the number of subgraphs they are indexing. These rewards incentivize Indexers to index subgraphs, occasionally before the query fees begin, to accrue and submit Proofs of Indexing (POIs), verifying that they have indexed data accurately.
+
+Each subgraph is allotted a portion of the total network token issuance, based on the amount of the subgraph’s curation signal. That amount is then rewarded to Indexers based on their allocated stake on the subgraph.
+
+In order to run an indexing node, Indexers must self-stake 100,000 GRT or more with the network. Indexers are incentivized to self-stake GRT in proportion to the amount of queries they serve.
+
+Indexers can increase their GRT allocations on subgraphs by accepting GRT delegation from Delegators, and they can accept up to 16 times their initial self-stake. If an Indexer becomes "over-delegated" (i.e., more than 16 times their initial self-stake), they will not be able to use the additional GRT from Delegators until they increase their self-stake in the network.
+
+The amount of rewards an Indexer receives can vary based on the Indexer's self-stake, accepted delegation, quality of service, and many more factors.
+
+## Token Supply: Burning & Issuance
+
+The initial token supply is 10 billion GRT, with a target of 3% new issuance annually to reward Indexers for allocating stake on subgraphs. This means that the total supply of GRT tokens will increase by 3% each year as new tokens are issued to Indexers for their contribution to the network.
+
+The Graph is designed with multiple burning mechanisms to offset new token issuance. Approximately 1% of the GRT supply is burned annually through various activities on the network, and this number has been increasing as network activity continues to grow. These burning activities include a 0.5% delegation tax whenever a Delegator delegates GRT to an Indexer, a 1% curation tax when Curators signal on a subgraph, and a 1% of query fees for blockchain data.
+
+![Total burned GRT](/img/total-burned-grt.jpeg)
+
+In addition to these regularly occurring burning activities, the GRT token also has a slashing mechanism in place to penalize malicious or irresponsible behavior by Indexers. If an Indexer is slashed, 50% of their indexing rewards for the epoch are burned (while the other half goes to the fisherman), and their self-stake is slashed by 2.5%, with half of this amount being burned. This helps to ensure that Indexers have a strong incentive to act in the best interests of the network and to contribute to its security and stability.
+
+## Improving the Protocol
+
+The Graph Network is ever-evolving and improvements to the economic design of the protocol are constantly being made to provide the best experience for all network participants. The Graph Council oversees protocol changes and community members are encouraged to participate. Get involved with protocol improvements in [The Graph Forum](https://forum.thegraph.com/).

From 35f2305cc1a212e86cf1c918db4f77c12d619c53 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:38 -0500
Subject: [PATCH 0456/1325] New translations grafting.mdx (French)

---
 website/pages/fr/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/fr/cookbook/grafting.mdx b/website/pages/fr/cookbook/grafting.mdx
index 7a7c618dc550..b255c571ec8b 100644
--- a/website/pages/fr/cookbook/grafting.mdx
+++ b/website/pages/fr/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ Pour plus d’informations, vous pouvez vérifier :
 
 - [Greffage](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-Dans ce tutoriel, nous allons aborder un cas d'utilisation de base. Nous allons remplacer un contrat existant par un contrat identique (avec une nouvelle adresse, mais le même code). Ensuite, nous grefferons le subgraph existant sur le subgraph "de base" qui suit le nouveau contrat.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Remarque importante sur le greffage lors de la mise à niveau vers le réseau
 
@@ -30,7 +30,7 @@ Dans ce tutoriel, nous allons aborder un cas d'utilisation de base. Nous allons
 
 ### Pourquoi est-ce important?
 
-La greffe est une fonctionnalité puissante qui permet de "greffer" un subgraph sur un autre, transférant ainsi les données historiques du subgraph existant vers une nouvelle version. Bien qu'il s'agisse d'un moyen efficace de préserver les données et de gagner du temps sur l'indexation, la greffe peut introduire des complexités et des problèmes potentiels lors de la migration d'un environnement hébergé vers le réseau décentralisé. Il n'est pas possible de greffer un subgraph du Graph Network vers le service hébergé ou le Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Les meilleures pratiques
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - La source de données `Lock` est l'adresse abi et le contrat que nous obtiendrons lorsque nous compilerons et déploierons le contrat
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - La section `mapping` définit les déclencheurs d'intérêt et les fonctions qui doivent être exécutées en réponse à ces déclencheurs. Dans ce cas, nous écoutons l'événement `Withdrawal` et appelons la fonction `handleWithdrawal` lorsqu'elle est émise.
 
 ## Définition de manifeste de greffage
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Ressources complémentaires
 
-Si vous souhaitez acquérir plus d'expérience en matière de greffes, voici quelques exemples de contrats populaires :
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 31061ea783682b6144731ff40e60bbaca2ac89df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:39 -0500
Subject: [PATCH 0457/1325] New translations subgraph-uncrashable.mdx (French)

---
 website/pages/fr/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/fr/cookbook/subgraph-uncrashable.mdx b/website/pages/fr/cookbook/subgraph-uncrashable.mdx
index 56b166b1056f..319851bc8579 100644
--- a/website/pages/fr/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/fr/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Générateur de code de subgraph sécurisé
 
 - Le cadre comprend également un moyen (via le fichier de configuration) de créer des fonctions de définition personnalisées, mais sûres, pour des groupes de variables d'entité. De cette façon, il est impossible pour l'utilisateur de charger/utiliser une entité de graph obsolète et il est également impossible d'oublier de sauvegarder ou définissez une variable requise par la fonction.
 
-- Les journaux d'avertissement sont enregistrés sous forme de journaux indiquant où il y a une violation de la logique de subgraph pour aider à corriger le problème afin de garantir l'exactitude des données. Ces journaux peuvent être consultés dans le service hébergé de The Graph dans la section "Journaux".
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable peut être exécuté en tant qu'indicateur facultatif à l'aide de la commande Graph CLI codegen.
 

From 64919c5b5e442d499cfe5614c9f78645df8ae354 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:40 -0500
Subject: [PATCH 0458/1325] New translations derivedfrom.mdx (French)

---
 website/pages/fr/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/fr/cookbook/derivedfrom.mdx b/website/pages/fr/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/fr/cookbook/derivedfrom.mdx
+++ b/website/pages/fr/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 88ecaab8b20fb1587c3fe3c4e622100b03312362 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:41 -0500
Subject: [PATCH 0459/1325] New translations
 immutable-entities-bytes-as-ids.mdx (French)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/fr/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/fr/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/fr/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/fr/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From edeee1f33c8a2625fc64ce74db05478a0b65c4c7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:43 -0500
Subject: [PATCH 0460/1325] New translations avoid-eth-calls.mdx (Romanian)

---
 website/pages/ro/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/ro/cookbook/avoid-eth-calls.mdx b/website/pages/ro/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/ro/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/ro/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ab5b1a2a7d1fcfbfe12162b94a8ed1c4eb8d5b8b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:44 -0500
Subject: [PATCH 0461/1325] New translations derivedfrom.mdx (Romanian)

---
 website/pages/ro/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/ro/cookbook/derivedfrom.mdx b/website/pages/ro/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/ro/cookbook/derivedfrom.mdx
+++ b/website/pages/ro/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 452e27813a45765d02a4141c2feb01d79778bb95 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:45 -0500
Subject: [PATCH 0462/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Romanian)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ro/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ro/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/ro/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/ro/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 01e6c320b29d0744e0dd78f08fcb9b0b37aea806 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:46 -0500
Subject: [PATCH 0463/1325] New translations pruning.mdx (Romanian)

---
 website/pages/ro/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ro/cookbook/pruning.mdx b/website/pages/ro/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/ro/cookbook/pruning.mdx
+++ b/website/pages/ro/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 92eb126ef477b8ba6ff657e32b85b424ae6841ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:47 -0500
Subject: [PATCH 0464/1325] New translations avoid-eth-calls.mdx (French)

---
 website/pages/fr/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/fr/cookbook/avoid-eth-calls.mdx b/website/pages/fr/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/fr/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/fr/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 318eba6352f928acb179e90accc98da206077ab0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:48 -0500
Subject: [PATCH 0465/1325] New translations pruning.mdx (French)

---
 website/pages/fr/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/fr/cookbook/pruning.mdx b/website/pages/fr/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/fr/cookbook/pruning.mdx
+++ b/website/pages/fr/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From db39203d61e681cd4ec66e3026a8cf6d595b97cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:49 -0500
Subject: [PATCH 0466/1325] New translations avoid-eth-calls.mdx (Spanish)

---
 website/pages/es/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/es/cookbook/avoid-eth-calls.mdx b/website/pages/es/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/es/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/es/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ab36615ed7a62b912768b48ccf0145e9f3a0629c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:50 -0500
Subject: [PATCH 0467/1325] New translations derivedfrom.mdx (Spanish)

---
 website/pages/es/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/es/cookbook/derivedfrom.mdx b/website/pages/es/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/es/cookbook/derivedfrom.mdx
+++ b/website/pages/es/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 4281c8c73ccb9b41b1aebfea85bc0272c28c8752 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:51 -0500
Subject: [PATCH 0468/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Spanish)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/es/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/es/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/es/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/es/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7977b59d56cc581d6854ec196721b6aa2a27ff21 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:52 -0500
Subject: [PATCH 0469/1325] New translations pruning.mdx (Spanish)

---
 website/pages/es/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/es/cookbook/pruning.mdx b/website/pages/es/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/es/cookbook/pruning.mdx
+++ b/website/pages/es/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 95a07e9148706f274b96d7efd9ae774317eab5dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:53 -0500
Subject: [PATCH 0470/1325] New translations avoid-eth-calls.mdx (Arabic)

---
 website/pages/ar/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/ar/cookbook/avoid-eth-calls.mdx b/website/pages/ar/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/ar/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/ar/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From dba878702363368a612034ef83c84dcdb9e346d2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:54 -0500
Subject: [PATCH 0471/1325] New translations derivedfrom.mdx (Arabic)

---
 website/pages/ar/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/ar/cookbook/derivedfrom.mdx b/website/pages/ar/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/ar/cookbook/derivedfrom.mdx
+++ b/website/pages/ar/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From af8416b2031cb9d29515dded124e877cf335d750 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:55 -0500
Subject: [PATCH 0472/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Arabic)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ar/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ar/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/ar/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/ar/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 75744682f87b783772477a3a101afdf57bdc6fbf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:56 -0500
Subject: [PATCH 0473/1325] New translations pruning.mdx (Arabic)

---
 website/pages/ar/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ar/cookbook/pruning.mdx b/website/pages/ar/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/ar/cookbook/pruning.mdx
+++ b/website/pages/ar/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 18684f0fe6c218048154da3654c6b93030e6694e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:57 -0500
Subject: [PATCH 0474/1325] New translations avoid-eth-calls.mdx (Czech)

---
 website/pages/cs/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/cs/cookbook/avoid-eth-calls.mdx b/website/pages/cs/cookbook/avoid-eth-calls.mdx
index 0b7af55002b4..2a469ec0844e 100644
--- a/website/pages/cs/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/cs/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Poznámka: Deklarované eth_calls lze provádět pouze v podgraf s verzí specVe
 
 ## Závěr
 
-Výkon indexování můžeme výrazně zlepšit minimalizací nebo odstraněním `eth_calls` v našich podgraf.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 894a3b7cc8630c3a0a448ef1b466725981327cd4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:59 -0500
Subject: [PATCH 0475/1325] New translations derivedfrom.mdx (Czech)

---
 website/pages/cs/cookbook/derivedfrom.mdx | 50 +++++++++++++++--------
 1 file changed, 32 insertions(+), 18 deletions(-)

diff --git a/website/pages/cs/cookbook/derivedfrom.mdx b/website/pages/cs/cookbook/derivedfrom.mdx
index e95a2cbe3069..b5662250e154 100644
--- a/website/pages/cs/cookbook/derivedfrom.mdx
+++ b/website/pages/cs/cookbook/derivedfrom.mdx
@@ -1,28 +1,28 @@
 ---
-title: Subgraph Best Practice 2 - Improve Indexing and Query Responsiveness By Using @derivedFrom
+title: Podgraf Doporučený postup 2 - Zlepšení indexování a rychlosti dotazů pomocí @derivedFrom
 ---
 
 ## TLDR
 
-Arrays in your schema can really slow down a subgraph's performance as they grow beyond thousands of entries. If possible, the `@derivedFrom` directive should be used when using arrays as it prevents large arrays from forming, simplifies handlers, and reduces the size of individual entities, improving indexing speed and query performance significantly.
+Pole ve vašem schématu mohou skutečně zpomalit výkon podgrafu, pokud jejich počet přesáhne tisíce položek. Pokud je to možné, měla by se při použití polí používat direktiva `@derivedFrom`, která zabraňuje vzniku velkých polí, zjednodušuje obslužné programy a snižuje velikost jednotlivých entit, čímž výrazně zvyšuje rychlost indexování a výkon dotazů.
 
-## How to Use the `@derivedFrom` Directive
+## Jak používat směrnici `@derivedFrom`
 
-You just need to add a `@derivedFrom` directive after your array in your schema. Like this:
+Stačí ve schématu za pole přidat směrnici `@derivedFrom`. Takto:
 
 ```graphql
 comments: [Comment!]! @derivedFrom(field: "post")
 ```
 
-`@derivedFrom` creates efficient one-to-many relationships, enabling an entity to dynamically associate with multiple related entities based on a field in the related entity. This approach removes the need for both sides of the relationship to store duplicate data, making the subgraph more efficient.
+`@derivedFrom` vytváří efektivní vztahy typu one-to-many, které umožňují dynamické přiřazení entity k více souvisejícím entitám na základě pole v související entitě. Tento přístup odstraňuje nutnost ukládat duplicitní data na obou stranách vztahu, čímž se podgraf stává efektivnějším.
 
-### Example Use Case for `@derivedFrom`
+### Příklad případu použití pro `@derivedFrom`
 
-An example of a dynamically growing array is a blogging platform where a “Post” can have many “Comments”.
+Příkladem dynamicky rostoucího pole je blogovací platforma, kde "příspěvek“ může mít mnoho "komentářů“.
 
-Let’s start with our two entities, `Post` and `Comment`
+Začněme s našimi dvěma entitami, `příspěvek` a `Komentář`
 
-Without optimization, you could implement it like this with an array:
+Bez optimalizace byste to mohli implementovat takto pomocí pole:
 
 ```graphql
 type Post @entity {
@@ -38,9 +38,9 @@ type Comment @entity {
 }
 ```
 
-Arrays like these will effectively store extra Comments data on the Post side of the relationship.
+Taková pole budou efektivně ukládat další data komentářů na straně Post vztahu.
 
-Here’s what an optimized version looks like using `@derivedFrom`:
+Zde vidíte, jak vypadá optimalizovaná verze s použitím `@derivedFrom`:
 
 ```graphql
 type Post @entity {
@@ -57,18 +57,32 @@ type Comment @entity {
 }
 ```
 
-Just by adding the `@derivedFrom` directive, this schema will only store the “Comments” on the “Comments” side of the relationship and not on the “Post” side of the relationship. Arrays are stored across individual rows, which allows them to expand significantly. This can lead to particularly large sizes if their growth is unbounded.
+Pouhým přidáním direktivy `@derivedFrom` bude toto schéma ukládat "Komentáře“ pouze na straně "Komentáře“ vztahu a nikoli na straně "Příspěvek“ vztahu. Pole se ukládají napříč jednotlivými řádky, což umožňuje jejich výrazné rozšíření. To může vést k obzvláště velkým velikostem, pokud je jejich růst neomezený.
 
-This will not only make our subgraph more efficient, but it will also unlock three features:
+Tím se nejen zefektivní náš podgraf, ale také se odemknou tři funkce:
 
-1. We can query the `Post` and see all of its comments.
+1. Můžeme se zeptat na `Post` a zobrazit všechny jeho komentáře.
 
-2. We can do a reverse lookup and query any `Comment` and see which post it comes from.
+2. Můžeme provést zpětné vyhledávání a dotazovat se na jakýkoli `Komentář` a zjistit, ze kterého příspěvku pochází.
 
-3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings.
+3. Pomocí [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) můžeme odemknout možnost přímého přístupu a manipulace s daty z virtuálních vztahů v našich mapováních podgrafů.
 
 ## Závěr
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From b1f4f932ed33dab224a00942faa03b76a882500d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:39:59 -0500
Subject: [PATCH 0476/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Czech)

---
 .../immutable-entities-bytes-as-ids.mdx       | 76 +++++++++++--------
 1 file changed, 45 insertions(+), 31 deletions(-)

diff --git a/website/pages/cs/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/cs/cookbook/immutable-entities-bytes-as-ids.mdx
index 378e73ac83b8..620906f8cf65 100644
--- a/website/pages/cs/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/cs/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -1,14 +1,14 @@
 ---
-title: Subgraph Best Practice 3 - Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs
+title: Osvědčený postup 3 - Zlepšení indexování a výkonu dotazů pomocí neměnných entit a bytů jako ID
 ---
 
 ## TLDR
 
-Using Immutable Entities and Bytes for IDs in our `schema.graphql` file [significantly improves ](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/) indexing speed and query performance.
+Použití neměnných entit a bytů pro ID v našem souboru `schema.graphql` [výrazně zlepšuje ](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/) rychlost indexování a výkonnost dotazů.
 
-## Immutable Entities
+## Nezměnitelné entity
 
-To make an entity immutable, we simply add `(immutable: true)` to an entity.
+Aby byla entita neměnná, jednoduše k ní přidáme `(immutable: true)`.
 
 ```graphql
 type Transfer @entity(immutable: true) {
@@ -19,21 +19,21 @@ type Transfer @entity(immutable: true) {
 }
 ```
 
-By making the `Transfer` entity immutable, graph-node is able to process the entity more efficiently, improving indexing speeds and query responsiveness.
+Tím, že je entita `Transfer` neměnná, je grafový uzel schopen ji zpracovávat efektivněji, což zvyšuje rychlost indexování a odezvu dotazů.
 
-Immutable Entities structures will not change in the future. An ideal entity to become an Immutable Entity would be an entity that is directly logging on-chain event data, such as a `Transfer` event being logged as a `Transfer` entity.
+Struktury neměnných entit se v budoucnu nezmění. Ideální entitou, která by se měla stát nezměnitelnou entitou, by byla entita, která přímo zaznamenává data událostí v řetězci, například událost `Převod` by byla zaznamenána jako entita `Převod`.
 
-### Under the hood
+### Pod kapotou
 
-Mutable entities have a 'block range' indicating their validity. Updating these entities requires the graph node to adjust the block range of previous versions, increasing database workload. Queries also need filtering to find only live entities. Immutable entities are faster because they are all live and since they won't change, no checks or updates are required while writing, and no filtering is required during queries.
+Mutabilní entity mají "rozsah bloku", který udává jejich platnost. Aktualizace těchto entit vyžaduje, aby uzel grafu upravil rozsah bloků předchozích verzí, což zvyšuje zatížení databáze. Dotazy je také třeba filtrovat, aby byly nalezeny pouze živé entity. Neměnné entity jsou rychlejší, protože jsou všechny živé, a protože se nebudou měnit, nejsou při zápisu nutné žádné kontroly ani aktualizace a při dotazech není nutné žádné filtrování.
 
-### When not to use Immutable Entities
+### Kdy nepoužívat nezměnitelné entity
 
-If you have a field like `status` that needs to be modified over time, then you should not make the entity immutable. Otherwise, you should use immutable entities whenever possible.
+Pokud máte pole, jako je `status`, které je třeba v průběhu času měnit, neměli byste entitu učinit neměnnou. Jinak byste měli používat neměnné entity, kdykoli je to možné.
 
-## Bytes as IDs
+## Bajty jako IDs
 
-Every entity requires an ID. In the previous example, we can see that the ID is already of the Bytes type.
+Každá entita vyžaduje ID. V předchozím příkladu vidíme, že ID je již typu Bytes.
 
 ```graphql
 type Transfer @entity(immutable: true) {
@@ -44,19 +44,19 @@ type Transfer @entity(immutable: true) {
 }
 ```
 
-While other types for IDs are possible, such as String and Int8, it is recommended to use the Bytes type for all IDs due to character strings taking twice as much space as Byte strings to store binary data, and comparisons of UTF-8 character strings must take the locale into account which is much more expensive than the bytewise comparison used to compare Byte strings.
+I když jsou možné i jiné typy ID, například String a Int8, doporučuje se pro všechna ID používat typ Bytes, protože pro uložení binárních dat zabírají znakové řetězce dvakrát více místa než řetězce Byte a při porovnávání znakových řetězců UTF-8 se musí brát v úvahu locale, což je mnohem dražší než bytewise porovnávání používané pro porovnávání řetězců Byte.
 
-### Reasons to Not Use Bytes as IDs
+### Důvody, proč nepoužívat bajty jako IDs
 
-1. If entity IDs must be human-readable such as auto-incremented numerical IDs or readable strings, Bytes for IDs should not be used.
-2. If integrating a subgraph’s data with another data model that does not use Bytes as IDs, Bytes as IDs should not be used.
-3. Indexing and querying performance improvements are not desired.
+1. Pokud musí být IDs entit čitelné pro člověka, například automaticky doplňované číselné IDs nebo čitelné řetězce, neměly by být použity bajty pro IDs.
+2. Při integraci dat podgrafu s jiným datovým modelem, který nepoužívá bajty jako IDs, by se bajty jako IDs neměly používat.
+3. Zlepšení výkonu indexování a dotazování není žádoucí.
 
-### Concatenating With Bytes as IDs
+### Konkatenace s byty jako IDs
 
-It is a common practice in many subgraphs to use string concatenation to combine two properties of an event into a single ID, such as using `event.transaction.hash.toHex() + "-" + event.logIndex.toString()`. However, as this returns a string, this significantly impedes subgraph indexing and querying performance.
+V mnoha podgrafech se běžně používá spojování řetězců ke spojení dvou vlastností události do jediného ID, například pomocí `event.transaction.hash.toHex() + "-" + event.logIndex.toString()`. Protože se však tímto způsobem vrací řetězec, značně to zhoršuje indexování podgrafů a výkonnost dotazování.
 
-Instead, we should use the `concatI32()` method to concatenate event properties. This strategy results in a `Bytes` ID that is much more performant.
+Místo toho bychom měli použít metodu `concatI32()` pro spojování vlastností událostí. Výsledkem této strategie je ID `Bytes`, které je mnohem výkonnější.
 
 ```typescript
 export function handleTransfer(event: TransferEvent): void {
@@ -73,11 +73,11 @@ export function handleTransfer(event: TransferEvent): void {
 }
 ```
 
-### Sorting With Bytes as IDs
+### Třídění s bajty jako ID
 
-Sorting using Bytes as IDs is not optimal as seen in this example query and response.
+Třídění pomocí bajtů jako IDs není optimální, jak je vidět v tomto příkladu dotazu a odpovědi.
 
-Query:
+Dotaz:
 
 ```graphql
 {
@@ -90,7 +90,7 @@ Query:
 }
 ```
 
-Query response:
+Odpověď na dotaz:
 
 ```json
 {
@@ -119,9 +119,9 @@ Query response:
 }
 ```
 
-The IDs are returned as hex.
+ID jsou vrácena v hex.
 
-To improve sorting, we should create another field on the entity that is a BigInt.
+Abychom zlepšili třídění, měli bychom v entitě vytvořit další pole, které bude BigInt.
 
 ```graphql
 type Transfer @entity {
@@ -133,9 +133,9 @@ type Transfer @entity {
 }
 ```
 
-This will allow for sorting to be optimized sequentially.
+To umožní postupnou optimalizaci třídění.
 
-Query:
+Dotaz:
 
 ```graphql
 {
@@ -146,7 +146,7 @@ Query:
 }
 ```
 
-Query Response:
+Odpověď na dotaz:
 
 ```json
 {
@@ -171,6 +171,20 @@ Query Response:
 
 ## Závěr
 
-Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
+Bylo prokázáno, že použití neměnných entit i bytů jako ID výrazně zvyšuje efektivitu podgrafů. Testy konkrétně ukázaly až 28% nárůst výkonu dotazů a až 48% zrychlení indexace.
 
-Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+Více informací o používání nezměnitelných entit a bytů jako ID najdete v tomto příspěvku na blogu Davida Lutterkorta, softwarového inženýra ve společnosti Edge & Node: [Dvě jednoduchá vylepšení výkonu podgrafu](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 830a3adecb566a824699da5adb1581dc5f6b197d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:00 -0500
Subject: [PATCH 0477/1325] New translations pruning.mdx (Czech)

---
 website/pages/cs/cookbook/pruning.mdx | 40 ++++++++++++++++++---------
 1 file changed, 27 insertions(+), 13 deletions(-)

diff --git a/website/pages/cs/cookbook/pruning.mdx b/website/pages/cs/cookbook/pruning.mdx
index 7533d0070737..32ffb4e5450a 100644
--- a/website/pages/cs/cookbook/pruning.mdx
+++ b/website/pages/cs/cookbook/pruning.mdx
@@ -1,22 +1,22 @@
 ---
-title: Subgraph Best Practice 1 - Improve Query Speed with Subgraph Pruning
+title: Doporučený postup 1 - Zlepšení rychlosti dotazu pomocí ořezávání podgrafů
 ---
 
 ## TLDR
 
-[Pruning](/developing/creating-a-subgraph/#prune) removes archival entities from the subgraph’s database up to a given block, and removing unused entities from a subgraph’s database will improve a subgraph’s query performance, often dramatically. Using `indexerHints` is an easy way to prune a subgraph.
+[Pruning](/developing/creating-a-subgraph/#prune) odstraní archivní entity z databáze podgrafu až do daného bloku a odstranění nepoužívaných entit z databáze podgrafu zlepší výkonnost dotazu podgrafu, často výrazně. Použití `indexerHints` je snadný způsob, jak podgraf ořezat.
 
-## How to Prune a Subgraph With `indexerHints`
+## Jak prořezat podgraf pomocí `indexerHints`
 
-Add a section called `indexerHints` in the manifest.
+Přidejte do manifestu sekci `indexerHints`.
 
-`indexerHints` has three `prune` options:
+`indexerHints` má tři možnosti `prune`:
 
-- `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0.
-- `prune: <Number of blocks to retain>`: Sets a custom limit on the number of historical blocks to retain.
-- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired.
+- `prune: auto`: Udržuje minimální potřebnou historii nastavenou indexátorem, čímž optimalizuje výkon dotazu. Toto je obecně doporučené nastavení a je výchozí pro všechny podgrafy vytvořené pomocí `graph-cli` >= 0.66.0.
+- `prune: <Number of blocks to retain>`: Nastaví vlastní omezení počtu historických bloků, které se mají zachovat.
+- `prune: never`: Je výchozí, pokud není k dispozici sekce `indexerHints`. `prune: never` by mělo být vybráno, pokud jsou požadovány [Dotazy na cestování časem](/querying/graphql-api/#time-travel-queries).
 
-We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`:
+Aktualizací souboru `subgraph.yaml` můžeme do podgrafů přidat `indexerHints`:
 
 ```yaml
 specVersion: 1.0.0
@@ -30,12 +30,26 @@ dataSources:
     network: mainnet
 ```
 
-## Important Considerations
+## Důležité úvahy
 
-- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: <Number of blocks to retain>` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data.
+- Pokud jsou kromě ořezávání požadovány i [dotazy na cestování v čase](/querying/graphql-api/#time-travel-queries), musí být ořezávání provedeno přesně, aby byla zachována funkčnost dotazů na cestování v čase. Z tohoto důvodu se obecně nedoporučuje používat `indexerHints: prune: auto` s Time Travel Queries. Místo toho proveďte ořezávání pomocí `indexerHints: prune: <Number of blocks to retain>` pro přesné ořezání na výšku bloku, která zachovává historická data požadovaná dotazy Time Travel, nebo použijte `prune: never` pro zachování všech dat.
 
-- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: <Number of blocks to retain>` that will accurately retain a set number of blocks (e.g., enough for six months).
+- Není možné [roubovat](/cookbook/grafting/) na výšku bloku, který byl prořezán. Pokud se roubování provádí běžně a je požadováno prořezání, doporučuje se použít `indexerHints: prune: <Number of blocks to retain> ` který přesně zachová stanovený počet bloků (např. dostatečný počet na šest měsíců).
 
 ## Závěr
 
-Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+Ořezávání pomocí `indexerHints` je osvědčeným postupem pro vývoj podgrafů, který nabízí významné zlepšení výkonu dotazů.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 1f19e1efd76c62d4e3f5b3d1b996fd87fcc9e94f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:01 -0500
Subject: [PATCH 0478/1325] New translations avoid-eth-calls.mdx (German)

---
 website/pages/de/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/de/cookbook/avoid-eth-calls.mdx b/website/pages/de/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/de/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/de/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From fdcf18f2bdd95fff1b6b63055533c702843c95a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:03 -0500
Subject: [PATCH 0479/1325] New translations derivedfrom.mdx (German)

---
 website/pages/de/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/de/cookbook/derivedfrom.mdx b/website/pages/de/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/de/cookbook/derivedfrom.mdx
+++ b/website/pages/de/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8866f1ffe93649a906848c2c59c0c6eb415bfacd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:03 -0500
Subject: [PATCH 0480/1325] New translations
 immutable-entities-bytes-as-ids.mdx (German)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/de/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/de/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/de/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/de/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 9bb8494095c105d76ffd1d626a7df7425b142b6e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:04 -0500
Subject: [PATCH 0481/1325] New translations pruning.mdx (German)

---
 website/pages/de/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/de/cookbook/pruning.mdx b/website/pages/de/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/de/cookbook/pruning.mdx
+++ b/website/pages/de/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7df50624a1c0f12341a219a98834379cbaf1995d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:06 -0500
Subject: [PATCH 0482/1325] New translations avoid-eth-calls.mdx (Italian)

---
 website/pages/it/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/it/cookbook/avoid-eth-calls.mdx b/website/pages/it/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/it/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/it/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ee392cd7382ee8c9f30245568d4e4108e445f078 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:07 -0500
Subject: [PATCH 0483/1325] New translations derivedfrom.mdx (Italian)

---
 website/pages/it/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/it/cookbook/derivedfrom.mdx b/website/pages/it/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/it/cookbook/derivedfrom.mdx
+++ b/website/pages/it/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From bdff59281d84e51d481df650c4804c39d9c1421f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:08 -0500
Subject: [PATCH 0484/1325] New translations enums.mdx (French)

---
 website/pages/fr/cookbook/enums.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/fr/cookbook/enums.mdx b/website/pages/fr/cookbook/enums.mdx
index a10970c1539f..ac68bdc05ade 100644
--- a/website/pages/fr/cookbook/enums.mdx
+++ b/website/pages/fr/cookbook/enums.mdx
@@ -50,7 +50,7 @@ type Token @entity {
 
 In this schema, `TokenStatus` is a simple string with no specific, allowed values.
 
-#### Why is this a problem?
+#### Pourquoi est-ce un problème ?
 
 - There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
 - It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Ressources additionnelles
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 9948031c6b3008c55dfaff7c731eafc45f2b3151 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:10 -0500
Subject: [PATCH 0485/1325] New translations enums.mdx (Hindi)

---
 website/pages/hi/cookbook/enums.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/hi/cookbook/enums.mdx b/website/pages/hi/cookbook/enums.mdx
index a10970c1539f..6ce7f9e84551 100644
--- a/website/pages/hi/cookbook/enums.mdx
+++ b/website/pages/hi/cookbook/enums.mdx
@@ -50,7 +50,7 @@ type Token @entity {
 
 In this schema, `TokenStatus` is a simple string with no specific, allowed values.
 
-#### Why is this a problem?
+#### यह एक समस्या क्यों है?
 
 - There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
 - It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## अतिरिक्त संसाधन
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From fea75263d0d8b3b96f2e8e0ebb513dded450f7f9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:11 -0500
Subject: [PATCH 0486/1325] New translations grafting-hotfix.mdx (Romanian)

---
 website/pages/ro/cookbook/grafting-hotfix.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ro/cookbook/grafting-hotfix.mdx b/website/pages/ro/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..040e3a8209d5 100644
--- a/website/pages/ro/cookbook/grafting-hotfix.mdx
+++ b/website/pages/ro/cookbook/grafting-hotfix.mdx
@@ -1,5 +1,5 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 4c45dd5dd29032c1b8f6d995d2c39b563f8cedcd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:12 -0500
Subject: [PATCH 0487/1325] New translations grafting-hotfix.mdx (French)

---
 website/pages/fr/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/fr/cookbook/grafting-hotfix.mdx b/website/pages/fr/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..fd32ece68e7e 100644
--- a/website/pages/fr/cookbook/grafting-hotfix.mdx
+++ b/website/pages/fr/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Aperçu
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Ressources additionnelles
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a56d6adb52021d8ab05c2423744061daa117f88d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:13 -0500
Subject: [PATCH 0488/1325] New translations grafting-hotfix.mdx (Spanish)

---
 website/pages/es/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/es/cookbook/grafting-hotfix.mdx b/website/pages/es/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..61da49e08f7b 100644
--- a/website/pages/es/cookbook/grafting-hotfix.mdx
+++ b/website/pages/es/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Descripción
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Recursos Adicionales
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From e5bab6dccf43b6e27bb7dcac86127442cd5e115f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:14 -0500
Subject: [PATCH 0489/1325] New translations grafting-hotfix.mdx (Arabic)

---
 website/pages/ar/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/ar/cookbook/grafting-hotfix.mdx b/website/pages/ar/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..b7699bf2bc85 100644
--- a/website/pages/ar/cookbook/grafting-hotfix.mdx
+++ b/website/pages/ar/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### نظره عامة
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## مصادر إضافية
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ed2deaed36ad2a596437466b355ff1d7cdb99758 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:16 -0500
Subject: [PATCH 0490/1325] New translations grafting-hotfix.mdx (Czech)

---
 website/pages/cs/cookbook/grafting-hotfix.mdx | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/cs/cookbook/grafting-hotfix.mdx b/website/pages/cs/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..e93c527fa90c 100644
--- a/website/pages/cs/cookbook/grafting-hotfix.mdx
+++ b/website/pages/cs/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Přehled
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -154,7 +154,7 @@ While grafting is a powerful tool for deploying hotfixes quickly, there are spec
 - **Data Integrity**: Incorrect block numbers can lead to data loss or duplication.
 - **Testing**: Always test grafting in a development environment before deploying to production.
 
-## Conclusion
+## Závěr
 
 Grafting is an effective strategy for deploying hotfixes in subgraph development, enabling you to:
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Další zdroje
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ee6ea4b9c2ad194262efa67b2b55408607e49690 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:17 -0500
Subject: [PATCH 0491/1325] New translations grafting-hotfix.mdx (German)

---
 website/pages/de/cookbook/grafting-hotfix.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/de/cookbook/grafting-hotfix.mdx b/website/pages/de/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..040e3a8209d5 100644
--- a/website/pages/de/cookbook/grafting-hotfix.mdx
+++ b/website/pages/de/cookbook/grafting-hotfix.mdx
@@ -1,5 +1,5 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 97f4964211d982b4820593197be07e89b722ceb6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:18 -0500
Subject: [PATCH 0492/1325] New translations timeseries.mdx (Romanian)

---
 website/pages/ro/cookbook/timeseries.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ro/cookbook/timeseries.mdx b/website/pages/ro/cookbook/timeseries.mdx
index 88ee70005a6e..2ce0ce266ccf 100644
--- a/website/pages/ro/cookbook/timeseries.mdx
+++ b/website/pages/ro/cookbook/timeseries.mdx
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ebb7bc49a1bd55cd854a2c5bef68f74add08c8b9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:19 -0500
Subject: [PATCH 0493/1325] New translations timeseries.mdx (French)

---
 website/pages/fr/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/fr/cookbook/timeseries.mdx b/website/pages/fr/cookbook/timeseries.mdx
index 88ee70005a6e..44d7eca76ee9 100644
--- a/website/pages/fr/cookbook/timeseries.mdx
+++ b/website/pages/fr/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Aperçu
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+L'exemple:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+L'exemple:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+L'exemple:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+L'exemple:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From d6b7e515dfaab6e7fd3ac30c4a1e22b978b0f9a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:20 -0500
Subject: [PATCH 0494/1325] New translations timeseries.mdx (Spanish)

---
 website/pages/es/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/es/cookbook/timeseries.mdx b/website/pages/es/cookbook/timeseries.mdx
index 88ee70005a6e..8eaed50b0ea3 100644
--- a/website/pages/es/cookbook/timeseries.mdx
+++ b/website/pages/es/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Descripción
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+Ejemplo:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+Ejemplo:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+Ejemplo:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+Ejemplo:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ec2072cc5a515db194467aae0e25847c340562d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:21 -0500
Subject: [PATCH 0495/1325] New translations timeseries.mdx (Arabic)

---
 website/pages/ar/cookbook/timeseries.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ar/cookbook/timeseries.mdx b/website/pages/ar/cookbook/timeseries.mdx
index 88ee70005a6e..a6402c800725 100644
--- a/website/pages/ar/cookbook/timeseries.mdx
+++ b/website/pages/ar/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## نظره عامة
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7a92f0b9d1e3a3b997cbe58a779321a4f31a42d1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:22 -0500
Subject: [PATCH 0496/1325] New translations timeseries.mdx (Czech)

---
 website/pages/cs/cookbook/timeseries.mdx | 26 ++++++++++++------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/website/pages/cs/cookbook/timeseries.mdx b/website/pages/cs/cookbook/timeseries.mdx
index 88ee70005a6e..48be01215291 100644
--- a/website/pages/cs/cookbook/timeseries.mdx
+++ b/website/pages/cs/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Přehled
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -27,7 +27,7 @@ Timeseries and aggregations reduce data processing overhead and accelerate queri
 - Immutable Data: All timeseries data is immutable, enabling efficient storage and retrieval.
 - Efficient Data Separation: Aggregates are stored separately from raw timeseries data, allowing queries to process significantly less data—often several orders of magnitude less.
 
-### Important Considerations
+### Důležité úvahy
 
 - Immutable Data: Timeseries data cannot be altered once written, ensuring data integrity and simplifying indexing.
 - Automatic ID and Timestamp Management: id and timestamp fields are automatically managed by graph-node, reducing potential errors.
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+Příklad:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+Příklad:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+Příklad:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+Příklad:
 
 ### Timeseries Entity
 
@@ -169,7 +169,7 @@ Supported operators and functions include basic arithmetic (+, -, \_, /), compar
 - Sorting: Results are automatically sorted by timestamp and id in descending order.
 - Current Data: An optional current argument can include the current, partially filled interval.
 
-### Conclusion
+### Závěr
 
 Implementing timeseries and aggregations in subgraphs is a best practice for projects dealing with time-based data. This approach:
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From cbc7d40747060d9d8b38f4303b62ae8b336371fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:23 -0500
Subject: [PATCH 0497/1325] New translations timeseries.mdx (German)

---
 website/pages/de/cookbook/timeseries.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/de/cookbook/timeseries.mdx b/website/pages/de/cookbook/timeseries.mdx
index 88ee70005a6e..2ce0ce266ccf 100644
--- a/website/pages/de/cookbook/timeseries.mdx
+++ b/website/pages/de/cookbook/timeseries.mdx
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8dc3dcf68c640c263f4f4d898b8d12ea2fc08b37 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:24 -0500
Subject: [PATCH 0498/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Italian)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/it/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/it/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/it/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/it/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a685a1d261adef52d3dbc3137538d1d73f57a08c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:25 -0500
Subject: [PATCH 0499/1325] New translations pruning.mdx (Italian)

---
 website/pages/it/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/it/cookbook/pruning.mdx b/website/pages/it/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/it/cookbook/pruning.mdx
+++ b/website/pages/it/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From d47382bd532f81ced30281f3ecc4550c2ccdd333 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:26 -0500
Subject: [PATCH 0500/1325] New translations avoid-eth-calls.mdx (Japanese)

---
 website/pages/ja/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/ja/cookbook/avoid-eth-calls.mdx b/website/pages/ja/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/ja/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/ja/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 6d262e477c34bafc6138b0edadb74335fa0f13c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:27 -0500
Subject: [PATCH 0501/1325] New translations derivedfrom.mdx (Japanese)

---
 website/pages/ja/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/ja/cookbook/derivedfrom.mdx b/website/pages/ja/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/ja/cookbook/derivedfrom.mdx
+++ b/website/pages/ja/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 1ad54abb3c3dcfcc2f4d04a1a7c4051178b25c4d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:28 -0500
Subject: [PATCH 0502/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Japanese)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ja/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ja/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/ja/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/ja/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a2bf2de9d55f4151540f0f7f78a19afd85b1f8aa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:29 -0500
Subject: [PATCH 0503/1325] New translations pruning.mdx (Japanese)

---
 website/pages/ja/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ja/cookbook/pruning.mdx b/website/pages/ja/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/ja/cookbook/pruning.mdx
+++ b/website/pages/ja/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From fd391b51e61b2317508df07a70a94c026c526c23 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:30 -0500
Subject: [PATCH 0504/1325] New translations avoid-eth-calls.mdx (Korean)

---
 website/pages/ko/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/ko/cookbook/avoid-eth-calls.mdx b/website/pages/ko/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/ko/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/ko/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 517cf40dac82dd6092d722f6070cce2646c3eb23 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:31 -0500
Subject: [PATCH 0505/1325] New translations derivedfrom.mdx (Korean)

---
 website/pages/ko/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/ko/cookbook/derivedfrom.mdx b/website/pages/ko/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/ko/cookbook/derivedfrom.mdx
+++ b/website/pages/ko/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From f1a15611e837b9a541323f34a3db1029fb2d7cd4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:32 -0500
Subject: [PATCH 0506/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Korean)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ko/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ko/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/ko/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/ko/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a4ac7d60e415e6c0cf25cbfc3ee409044bab925a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:33 -0500
Subject: [PATCH 0507/1325] New translations pruning.mdx (Korean)

---
 website/pages/ko/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ko/cookbook/pruning.mdx b/website/pages/ko/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/ko/cookbook/pruning.mdx
+++ b/website/pages/ko/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ebb4c23c24647f6ec1ce5c35585965f4edbf5230 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:34 -0500
Subject: [PATCH 0508/1325] New translations avoid-eth-calls.mdx (Dutch)

---
 website/pages/nl/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/nl/cookbook/avoid-eth-calls.mdx b/website/pages/nl/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/nl/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/nl/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8d3ba13319bf77a3e21b6dd52b35f72d6f60261d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:35 -0500
Subject: [PATCH 0509/1325] New translations derivedfrom.mdx (Dutch)

---
 website/pages/nl/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/nl/cookbook/derivedfrom.mdx b/website/pages/nl/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/nl/cookbook/derivedfrom.mdx
+++ b/website/pages/nl/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8f082aeffbc67ce750532b92da63d5173c841ccb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:36 -0500
Subject: [PATCH 0510/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Dutch)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/nl/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/nl/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/nl/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/nl/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 605d0185e5027542eedd2ab58f4f5153cb72e2c4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:37 -0500
Subject: [PATCH 0511/1325] New translations pruning.mdx (Dutch)

---
 website/pages/nl/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/nl/cookbook/pruning.mdx b/website/pages/nl/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/nl/cookbook/pruning.mdx
+++ b/website/pages/nl/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ec39da68873c1a47c5a6ca2d34e5797000fcc7b5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:38 -0500
Subject: [PATCH 0512/1325] New translations avoid-eth-calls.mdx (Polish)

---
 website/pages/pl/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/pl/cookbook/avoid-eth-calls.mdx b/website/pages/pl/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/pl/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/pl/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From d58c55b9dca798b074f7155335c45fd66af742b4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:39 -0500
Subject: [PATCH 0513/1325] New translations derivedfrom.mdx (Polish)

---
 website/pages/pl/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/pl/cookbook/derivedfrom.mdx b/website/pages/pl/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/pl/cookbook/derivedfrom.mdx
+++ b/website/pages/pl/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7517acc27b73f6686a239b4c7ea0dff50d458770 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:40 -0500
Subject: [PATCH 0514/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Polish)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/pl/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/pl/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/pl/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/pl/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 27e28481454ae50ce59db7fcb87abe5bf70e21ce Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:41 -0500
Subject: [PATCH 0515/1325] New translations pruning.mdx (Polish)

---
 website/pages/pl/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/pl/cookbook/pruning.mdx b/website/pages/pl/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/pl/cookbook/pruning.mdx
+++ b/website/pages/pl/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a270e0fb6434fde22927679512fe12458ed34807 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:42 -0500
Subject: [PATCH 0516/1325] New translations avoid-eth-calls.mdx (Portuguese)

---
 website/pages/pt/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/pt/cookbook/avoid-eth-calls.mdx b/website/pages/pt/cookbook/avoid-eth-calls.mdx
index c3e4c27ec660..427e3e9e669d 100644
--- a/website/pages/pt/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/pt/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Nota: `eth_calls` declaradas só podem ser feitas em subgraphs com specVersion m
 
 ## Conclusão
 
-Podemos melhorar muito o desempenho da indexação ao minimizar ou eliminar `eth_calls` nos nossos subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 3e3a4a595933e2b0dc0c28187f2a40e9e45f824e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:43 -0500
Subject: [PATCH 0517/1325] New translations derivedfrom.mdx (Portuguese)

---
 website/pages/pt/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/pt/cookbook/derivedfrom.mdx b/website/pages/pt/cookbook/derivedfrom.mdx
index a5d1f31c14bc..f6f7a4e51283 100644
--- a/website/pages/pt/cookbook/derivedfrom.mdx
+++ b/website/pages/pt/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ Isto não só aumenta a eficiência do nosso subgraph, mas também desbloqueia t
 
 ## Conclusão
 
-Adotar a diretiva `@derivedFrom` nos subgraphs lida eficientemente com arranjos que crescem dinamicamente, o que melhora a performance da indexação e o retiro de dados.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-Para aprender mais estratégias detalhadas sobre evitar arranjos grandes, leia este blog por Kevin Jones: [Melhores Práticas no Desenvolvimento de Subgraphs: Como Evitar Grandes Arranjos](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 434ffc8f4bf2fe59221f1b6b33a2ab3b561b9e50 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:44 -0500
Subject: [PATCH 0518/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Portuguese)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/pt/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/pt/cookbook/immutable-entities-bytes-as-ids.mdx
index d4a347e68243..b00bf3708ef3 100644
--- a/website/pages/pt/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/pt/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Resposta de query:
 É comprovado que usar Entidades Imutáveis e Bytes como IDs aumenta muito a eficiência de subgraphs. Especificamente, segundo testes, houve um aumento de até 28% no desempenho de queries e uma aceleração de até 48% em velocidades de indexação.
 
 Leia mais sobre o uso de Entidades Imutáveis e Bytes como IDs nesta publicação por David Lutterkort, Engenheiro de Software na Edge & Node: [Duas Melhorias Simples no Desempenho de Subgraphs](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 55194a5f426c2b40d04bf2ca51892bfd54fa09ec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:45 -0500
Subject: [PATCH 0519/1325] New translations pruning.mdx (Portuguese)

---
 website/pages/pt/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/pt/cookbook/pruning.mdx b/website/pages/pt/cookbook/pruning.mdx
index e7abf0788ae1..7eb1be85ddf9 100644
--- a/website/pages/pt/cookbook/pruning.mdx
+++ b/website/pages/pt/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusão
 
 O pruning com `indexerHints` é uma boa prática para o desenvolvimento de subgraphs que oferece melhorias significativas no desempenho de queries.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 218b1c1ace85a2d621468172836ec637313442a3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:46 -0500
Subject: [PATCH 0520/1325] New translations avoid-eth-calls.mdx (Russian)

---
 website/pages/ru/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/ru/cookbook/avoid-eth-calls.mdx b/website/pages/ru/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/ru/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/ru/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 9d3f6142d0e36dd8a0db0533851271fe41bef660 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:47 -0500
Subject: [PATCH 0521/1325] New translations derivedfrom.mdx (Russian)

---
 website/pages/ru/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/cookbook/derivedfrom.mdx b/website/pages/ru/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/ru/cookbook/derivedfrom.mdx
+++ b/website/pages/ru/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From f26a07b66117139ef86450937bf234fed6e71315 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:48 -0500
Subject: [PATCH 0522/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Russian)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ru/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ru/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/ru/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/ru/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 484b8db50d84cb3eab5611fe08dd593b722241c3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:49 -0500
Subject: [PATCH 0523/1325] New translations pruning.mdx (Russian)

---
 website/pages/ru/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ru/cookbook/pruning.mdx b/website/pages/ru/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/ru/cookbook/pruning.mdx
+++ b/website/pages/ru/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8bc0ec9b2aa103f0065a631f3a882d7e62262e29 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:50 -0500
Subject: [PATCH 0524/1325] New translations avoid-eth-calls.mdx (Swedish)

---
 website/pages/sv/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/sv/cookbook/avoid-eth-calls.mdx b/website/pages/sv/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/sv/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/sv/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From cf79b4b56336b08a12c3bf9182a3c1f95ccd56f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:51 -0500
Subject: [PATCH 0525/1325] New translations derivedfrom.mdx (Swedish)

---
 website/pages/sv/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/sv/cookbook/derivedfrom.mdx b/website/pages/sv/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/sv/cookbook/derivedfrom.mdx
+++ b/website/pages/sv/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 1ced41d85b801a870a09a422783652e27d57ba12 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:52 -0500
Subject: [PATCH 0526/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Swedish)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/sv/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/sv/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/sv/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/sv/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ad7315ae6fa34daae7c4c5b6197606b8a025e9b0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:53 -0500
Subject: [PATCH 0527/1325] New translations pruning.mdx (Swedish)

---
 website/pages/sv/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/sv/cookbook/pruning.mdx b/website/pages/sv/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/sv/cookbook/pruning.mdx
+++ b/website/pages/sv/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 12ac581de373f91d136cd1b4458ebec25d968762 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:54 -0500
Subject: [PATCH 0528/1325] New translations avoid-eth-calls.mdx (Turkish)

---
 website/pages/tr/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/tr/cookbook/avoid-eth-calls.mdx b/website/pages/tr/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/tr/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/tr/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a36b3987d625cb664a3a2b84390cb214c436f99a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:55 -0500
Subject: [PATCH 0529/1325] New translations derivedfrom.mdx (Turkish)

---
 website/pages/tr/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/tr/cookbook/derivedfrom.mdx b/website/pages/tr/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/tr/cookbook/derivedfrom.mdx
+++ b/website/pages/tr/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ff9ed9159436c9ea63f890b73aef432a6e2b7539 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:56 -0500
Subject: [PATCH 0530/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Turkish)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/tr/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/tr/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/tr/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/tr/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ea8cf3a55a9a655ef3a08cc6bcb451f5aadc1f64 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:57 -0500
Subject: [PATCH 0531/1325] New translations pruning.mdx (Turkish)

---
 website/pages/tr/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/tr/cookbook/pruning.mdx b/website/pages/tr/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/tr/cookbook/pruning.mdx
+++ b/website/pages/tr/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8ed7f557685ce8d99f2d95f5c54afdb7cf3947c0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:58 -0500
Subject: [PATCH 0532/1325] New translations grafting-hotfix.mdx (Italian)

---
 website/pages/it/cookbook/grafting-hotfix.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/it/cookbook/grafting-hotfix.mdx b/website/pages/it/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..0a0767655660 100644
--- a/website/pages/it/cookbook/grafting-hotfix.mdx
+++ b/website/pages/it/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Panoramica
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 551482dedab0f2648926babcf8253387f5eb745c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:40:59 -0500
Subject: [PATCH 0533/1325] New translations grafting-hotfix.mdx (Japanese)

---
 website/pages/ja/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/ja/cookbook/grafting-hotfix.mdx b/website/pages/ja/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..9c474ebdd73e 100644
--- a/website/pages/ja/cookbook/grafting-hotfix.mdx
+++ b/website/pages/ja/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### 概要
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## その他のリソース
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7db459497fb53424b638c5375dc0cb4052f08006 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:00 -0500
Subject: [PATCH 0534/1325] New translations grafting-hotfix.mdx (Korean)

---
 website/pages/ko/cookbook/grafting-hotfix.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ko/cookbook/grafting-hotfix.mdx b/website/pages/ko/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..040e3a8209d5 100644
--- a/website/pages/ko/cookbook/grafting-hotfix.mdx
+++ b/website/pages/ko/cookbook/grafting-hotfix.mdx
@@ -1,5 +1,5 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7b40454724cb2b6fee8353a009b81490311e40c9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:01 -0500
Subject: [PATCH 0535/1325] New translations grafting-hotfix.mdx (Dutch)

---
 website/pages/nl/cookbook/grafting-hotfix.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/nl/cookbook/grafting-hotfix.mdx b/website/pages/nl/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..040e3a8209d5 100644
--- a/website/pages/nl/cookbook/grafting-hotfix.mdx
+++ b/website/pages/nl/cookbook/grafting-hotfix.mdx
@@ -1,5 +1,5 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 84baa4b3ae5a5fe54a31aab8da25fc36e7ba9b7f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:02 -0500
Subject: [PATCH 0536/1325] New translations grafting-hotfix.mdx (Polish)

---
 website/pages/pl/cookbook/grafting-hotfix.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/pl/cookbook/grafting-hotfix.mdx b/website/pages/pl/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..040e3a8209d5 100644
--- a/website/pages/pl/cookbook/grafting-hotfix.mdx
+++ b/website/pages/pl/cookbook/grafting-hotfix.mdx
@@ -1,5 +1,5 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 2a1dbd43c52de8fdf973d9c5724afef3d71ba8cf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:03 -0500
Subject: [PATCH 0537/1325] New translations grafting-hotfix.mdx (Portuguese)

---
 website/pages/pt/cookbook/grafting-hotfix.mdx | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/pt/cookbook/grafting-hotfix.mdx b/website/pages/pt/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..ca17181cbf11 100644
--- a/website/pages/pt/cookbook/grafting-hotfix.mdx
+++ b/website/pages/pt/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Visão geral
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -154,7 +154,7 @@ While grafting is a powerful tool for deploying hotfixes quickly, there are spec
 - **Data Integrity**: Incorrect block numbers can lead to data loss or duplication.
 - **Testing**: Always test grafting in a development environment before deploying to production.
 
-## Conclusion
+## Conclusão
 
 Grafting is an effective strategy for deploying hotfixes in subgraph development, enabling you to:
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Outros Recursos
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From eae93b7dd329df22569f0771adf0c0bb4666f02f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:04 -0500
Subject: [PATCH 0538/1325] New translations grafting-hotfix.mdx (Russian)

---
 website/pages/ru/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/ru/cookbook/grafting-hotfix.mdx b/website/pages/ru/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..5d1b5f30770d 100644
--- a/website/pages/ru/cookbook/grafting-hotfix.mdx
+++ b/website/pages/ru/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Обзор
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Дополнительные источники
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From d56296b4a87dcbf4a6243a0718081db00359fe3d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:06 -0500
Subject: [PATCH 0539/1325] New translations grafting-hotfix.mdx (Swedish)

---
 website/pages/sv/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/sv/cookbook/grafting-hotfix.mdx b/website/pages/sv/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..b1e1a022076a 100644
--- a/website/pages/sv/cookbook/grafting-hotfix.mdx
+++ b/website/pages/sv/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Översikt
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Ytterligare resurser
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From c079cd2954e4ddad244474cc386cb1f8bf86a3a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:07 -0500
Subject: [PATCH 0540/1325] New translations timeseries.mdx (Italian)

---
 website/pages/it/cookbook/timeseries.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/it/cookbook/timeseries.mdx b/website/pages/it/cookbook/timeseries.mdx
index 88ee70005a6e..5c7e78871d22 100644
--- a/website/pages/it/cookbook/timeseries.mdx
+++ b/website/pages/it/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Panoramica
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 24cd78cdf37a4746bf58e344762435a185346b1d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:08 -0500
Subject: [PATCH 0541/1325] New translations timeseries.mdx (Japanese)

---
 website/pages/ja/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/ja/cookbook/timeseries.mdx b/website/pages/ja/cookbook/timeseries.mdx
index 88ee70005a6e..035975b433d3 100644
--- a/website/pages/ja/cookbook/timeseries.mdx
+++ b/website/pages/ja/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## 概要
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+例：
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+例：
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+例：
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+例：
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 232b7b28f19508b1b9c2a14cdf2dcd4133bfbcea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:08 -0500
Subject: [PATCH 0542/1325] New translations timeseries.mdx (Korean)

---
 website/pages/ko/cookbook/timeseries.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ko/cookbook/timeseries.mdx b/website/pages/ko/cookbook/timeseries.mdx
index 88ee70005a6e..2ce0ce266ccf 100644
--- a/website/pages/ko/cookbook/timeseries.mdx
+++ b/website/pages/ko/cookbook/timeseries.mdx
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 21aad7f78d289e45c89adbe2115d58bc9a76237a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:09 -0500
Subject: [PATCH 0543/1325] New translations timeseries.mdx (Dutch)

---
 website/pages/nl/cookbook/timeseries.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/nl/cookbook/timeseries.mdx b/website/pages/nl/cookbook/timeseries.mdx
index 88ee70005a6e..2ce0ce266ccf 100644
--- a/website/pages/nl/cookbook/timeseries.mdx
+++ b/website/pages/nl/cookbook/timeseries.mdx
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a720efaaa4b87d65f1f66e544458535cf3a73150 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:10 -0500
Subject: [PATCH 0544/1325] New translations timeseries.mdx (Polish)

---
 website/pages/pl/cookbook/timeseries.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/pl/cookbook/timeseries.mdx b/website/pages/pl/cookbook/timeseries.mdx
index 88ee70005a6e..2ce0ce266ccf 100644
--- a/website/pages/pl/cookbook/timeseries.mdx
+++ b/website/pages/pl/cookbook/timeseries.mdx
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a2cc06e81726a12accd876b264a2f6ac3cb6e4ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:12 -0500
Subject: [PATCH 0545/1325] New translations timeseries.mdx (Portuguese)

---
 website/pages/pt/cookbook/timeseries.mdx | 26 ++++++++++++------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/website/pages/pt/cookbook/timeseries.mdx b/website/pages/pt/cookbook/timeseries.mdx
index 88ee70005a6e..d6362da8dda1 100644
--- a/website/pages/pt/cookbook/timeseries.mdx
+++ b/website/pages/pt/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Visão geral
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -27,7 +27,7 @@ Timeseries and aggregations reduce data processing overhead and accelerate queri
 - Immutable Data: All timeseries data is immutable, enabling efficient storage and retrieval.
 - Efficient Data Separation: Aggregates are stored separately from raw timeseries data, allowing queries to process significantly less data—often several orders of magnitude less.
 
-### Important Considerations
+### Considerações Importantes
 
 - Immutable Data: Timeseries data cannot be altered once written, ensuring data integrity and simplifying indexing.
 - Automatic ID and Timestamp Management: id and timestamp fields are automatically managed by graph-node, reducing potential errors.
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+Exemplo:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+Exemplo:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+Exemplo:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+Exemplo:
 
 ### Timeseries Entity
 
@@ -169,7 +169,7 @@ Supported operators and functions include basic arithmetic (+, -, \_, /), compar
 - Sorting: Results are automatically sorted by timestamp and id in descending order.
 - Current Data: An optional current argument can include the current, partially filled interval.
 
-### Conclusion
+### Conclusão
 
 Implementing timeseries and aggregations in subgraphs is a best practice for projects dealing with time-based data. This approach:
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 918bde1b5ceb02a2c3aaf89640aff41ab51e068d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:13 -0500
Subject: [PATCH 0546/1325] New translations timeseries.mdx (Russian)

---
 website/pages/ru/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/ru/cookbook/timeseries.mdx b/website/pages/ru/cookbook/timeseries.mdx
index 88ee70005a6e..1e4fbc5cb68f 100644
--- a/website/pages/ru/cookbook/timeseries.mdx
+++ b/website/pages/ru/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Обзор
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+Пример:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+Пример:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+Пример:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+Пример:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ae07bb505b667a52f5eb32d7f505709ddce845ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:14 -0500
Subject: [PATCH 0547/1325] New translations timeseries.mdx (Swedish)

---
 website/pages/sv/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/sv/cookbook/timeseries.mdx b/website/pages/sv/cookbook/timeseries.mdx
index 88ee70005a6e..306ebfa0647a 100644
--- a/website/pages/sv/cookbook/timeseries.mdx
+++ b/website/pages/sv/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Översikt
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+Exempel:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+Exempel:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+Exempel:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+Exempel:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 4097a15663c98c388f09ee556995841fa252180c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:15 -0500
Subject: [PATCH 0548/1325] New translations cosmos.mdx (Russian)

---
 website/pages/ru/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/cookbook/cosmos.mdx b/website/pages/ru/cookbook/cosmos.mdx
index 04b2847fdb65..f47e04b61d35 100644
--- a/website/pages/ru/cookbook/cosmos.mdx
+++ b/website/pages/ru/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ dataSources:
 
 Обработчики событий написаны на языке [AssemblyScript](https://www.assemblyscript.org/).
 
-Индексация Cosmos вводит специфичные для Cosmos типы данных в [AssemblyScript API](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ $ graph build
 Посетите Subgraph Studio, чтобы создать новый субграф.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Локальная Graph Node (на основе конфигурации по умолчанию):**

From 406c8e6d2bd0bfc7e1e93863a915f8c5d0cad4f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:16 -0500
Subject: [PATCH 0549/1325] New translations arweave.mdx (Russian)

---
 website/pages/ru/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/cookbook/arweave.mdx b/website/pages/ru/cookbook/arweave.mdx
index 5650a7daed55..fa34140e6213 100644
--- a/website/pages/ru/cookbook/arweave.mdx
+++ b/website/pages/ru/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ dataSources:
 
 Обработчики событий написаны на [AssemblyScript](https://www.assemblyscript.org/).
 
-Индексация Arweave вводит типы данных, специфичные для Arweave, в [AssemblyScript API](/developing/graph-ts/api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ class Transaction {
 После создания субграфа на панели управления Subgraph Studio его можно развернуть с помощью команды CLI `graph Deploy`.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Запрос субграфа Arweave

From 2b855d0878252f77d1cafa31b2b355a36df762a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:18 -0500
Subject: [PATCH 0550/1325] New translations avoid-eth-calls.mdx (Ukrainian)

---
 website/pages/uk/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/uk/cookbook/avoid-eth-calls.mdx b/website/pages/uk/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/uk/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/uk/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 93a10f3d7da39f7c719f59e10f651b45a1afa888 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:19 -0500
Subject: [PATCH 0551/1325] New translations derivedfrom.mdx (Ukrainian)

---
 website/pages/uk/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/uk/cookbook/derivedfrom.mdx b/website/pages/uk/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/uk/cookbook/derivedfrom.mdx
+++ b/website/pages/uk/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 56318bc9b2fbcc0f6b366cc8eb54d148dc16ee73 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:20 -0500
Subject: [PATCH 0552/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Ukrainian)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/uk/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/uk/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/uk/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/uk/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From f693a75e6c2236c286d4d2cfb98aa8ff52165ff5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:21 -0500
Subject: [PATCH 0553/1325] New translations pruning.mdx (Ukrainian)

---
 website/pages/uk/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/uk/cookbook/pruning.mdx b/website/pages/uk/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/uk/cookbook/pruning.mdx
+++ b/website/pages/uk/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 3c90a4056c3a7db23e0b58c08d70eefb9e2d2e85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:22 -0500
Subject: [PATCH 0554/1325] New translations avoid-eth-calls.mdx (Chinese
 Simplified)

---
 website/pages/zh/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/zh/cookbook/avoid-eth-calls.mdx b/website/pages/zh/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/zh/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/zh/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 4f3529a0f2acbb228545b932d3116e668739002e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:23 -0500
Subject: [PATCH 0555/1325] New translations derivedfrom.mdx (Chinese
 Simplified)

---
 website/pages/zh/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/zh/cookbook/derivedfrom.mdx b/website/pages/zh/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/zh/cookbook/derivedfrom.mdx
+++ b/website/pages/zh/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ab53e21f14572158636515a5a983f41c4917eb58 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:24 -0500
Subject: [PATCH 0556/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Chinese Simplified)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/zh/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/zh/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/zh/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/zh/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 08f8223c691b917e2cb7c285d1662ed7515c22cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:25 -0500
Subject: [PATCH 0557/1325] New translations pruning.mdx (Chinese Simplified)

---
 website/pages/zh/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/zh/cookbook/pruning.mdx b/website/pages/zh/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/zh/cookbook/pruning.mdx
+++ b/website/pages/zh/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 4c935935a2fdd6ee6c764e9f151a72bf2ac90b76 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:26 -0500
Subject: [PATCH 0558/1325] New translations avoid-eth-calls.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/ur/cookbook/avoid-eth-calls.mdx b/website/pages/ur/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/ur/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/ur/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 07d15da77f5d221006f794bafbfd1a81a0f26590 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:27 -0500
Subject: [PATCH 0559/1325] New translations derivedfrom.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/ur/cookbook/derivedfrom.mdx b/website/pages/ur/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/ur/cookbook/derivedfrom.mdx
+++ b/website/pages/ur/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 1c570a8cd169e2f756f621682aecada55c42c9a8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:28 -0500
Subject: [PATCH 0560/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Urdu (Pakistan))

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ur/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/ur/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/ur/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/ur/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From af98a61b60048dfec12852655552d1807ea06b6f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:29 -0500
Subject: [PATCH 0561/1325] New translations pruning.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/ur/cookbook/pruning.mdx b/website/pages/ur/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/ur/cookbook/pruning.mdx
+++ b/website/pages/ur/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a253eed1541fee2baddd11c20a08a8f4630c322e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:30 -0500
Subject: [PATCH 0562/1325] New translations avoid-eth-calls.mdx (Vietnamese)

---
 website/pages/vi/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/vi/cookbook/avoid-eth-calls.mdx b/website/pages/vi/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/vi/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/vi/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 73ac60fa8aa0af6292887a512d66ba0c73125cd3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:31 -0500
Subject: [PATCH 0563/1325] New translations derivedfrom.mdx (Vietnamese)

---
 website/pages/vi/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/vi/cookbook/derivedfrom.mdx b/website/pages/vi/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/vi/cookbook/derivedfrom.mdx
+++ b/website/pages/vi/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7cf31b4fa1bdd94958739626bc3c0c59e2a9f642 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:32 -0500
Subject: [PATCH 0564/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Vietnamese)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/vi/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/vi/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/vi/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/vi/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 07260ea62e38f7ef63291f2a09ba226342096092 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:33 -0500
Subject: [PATCH 0565/1325] New translations pruning.mdx (Vietnamese)

---
 website/pages/vi/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/vi/cookbook/pruning.mdx b/website/pages/vi/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/vi/cookbook/pruning.mdx
+++ b/website/pages/vi/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 70637715dab5ed0b6d5e50a45ac711f5d566cb84 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:34 -0500
Subject: [PATCH 0566/1325] New translations avoid-eth-calls.mdx (Marathi)

---
 website/pages/mr/cookbook/avoid-eth-calls.mdx | 16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/website/pages/mr/cookbook/avoid-eth-calls.mdx b/website/pages/mr/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..8897ecdbfdc7 100644
--- a/website/pages/mr/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/mr/cookbook/avoid-eth-calls.mdx
@@ -99,4 +99,18 @@ Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0
 
 ## Conclusion
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 167a32cfa5cf64bd08471604f61a1127aef4d1db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:35 -0500
Subject: [PATCH 0567/1325] New translations derivedfrom.mdx (Marathi)

---
 website/pages/mr/cookbook/derivedfrom.mdx | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/website/pages/mr/cookbook/derivedfrom.mdx b/website/pages/mr/cookbook/derivedfrom.mdx
index 69dd48047744..09ba62abde3f 100644
--- a/website/pages/mr/cookbook/derivedfrom.mdx
+++ b/website/pages/mr/cookbook/derivedfrom.mdx
@@ -69,6 +69,20 @@ This will not only make our subgraph more efficient, but it will also unlock thr
 
 ## Conclusion
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 14e932462251b4435356be7f781246c6437f318e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:36 -0500
Subject: [PATCH 0568/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Marathi)

---
 .../cookbook/immutable-entities-bytes-as-ids.mdx   | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/mr/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/mr/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..541212617f9f 100644
--- a/website/pages/mr/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/mr/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -174,3 +174,17 @@ Query Response:
 Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
 
 Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a283e631001ee45da118836948c01c633008acb3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:37 -0500
Subject: [PATCH 0569/1325] New translations pruning.mdx (Marathi)

---
 website/pages/mr/cookbook/pruning.mdx | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/website/pages/mr/cookbook/pruning.mdx b/website/pages/mr/cookbook/pruning.mdx
index f22a2899f1de..d86bf50edf42 100644
--- a/website/pages/mr/cookbook/pruning.mdx
+++ b/website/pages/mr/cookbook/pruning.mdx
@@ -39,3 +39,17 @@ dataSources:
 ## Conclusion
 
 Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 84ed4480036c38e77b061ce2c9352590ed95b87b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:38 -0500
Subject: [PATCH 0570/1325] New translations avoid-eth-calls.mdx (Hindi)

---
 website/pages/hi/cookbook/avoid-eth-calls.mdx | 70 +++++++++++--------
 1 file changed, 42 insertions(+), 28 deletions(-)

diff --git a/website/pages/hi/cookbook/avoid-eth-calls.mdx b/website/pages/hi/cookbook/avoid-eth-calls.mdx
index 446b0e8ecd17..1892134f2a4c 100644
--- a/website/pages/hi/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/hi/cookbook/avoid-eth-calls.mdx
@@ -1,24 +1,24 @@
 ---
-title: Subgraph Best Practice 4 - Improve Indexing Speed by Avoiding eth_calls
+title: सबग्राफ सर्वोत्तम प्रथा 4 - eth_calls से बचकर अनुक्रमण गति में सुधार करें
 ---
 
 ## TLDR
 
-`eth_calls` are calls that can be made from a subgraph to an Ethereum node. These calls take a significant amount of time to return data, slowing down indexing. If possible, design smart contracts to emit all the data you need so you don’t need to use `eth_calls`.
+eth_calls वे कॉल हैं जो एक Subgraph से Ethereum नोड पर किए जा सकते हैं। ये कॉल डेटा लौटाने में महत्वपूर्ण समय लेते हैं, जिससे indexing धीमी हो जाती है। यदि संभव हो, तो स्मार्ट कॉन्ट्रैक्ट्स को इस तरह से डिजाइन करें कि वे सभी आवश्यक डेटा उत्पन्न करें ताकि आपको eth_calls का उपयोग न करना पड़े।
 
-## Why Avoiding `eth_calls` Is a Best Practice
+## Eth_calls से बचना एक सर्वोत्तम अभ्यास क्यों है
 
-Subgraphs are optimized to index event data emitted from smart contracts. A subgraph can also index the data coming from an `eth_call`, however, this can significantly slow down subgraph indexing as `eth_calls` require making external calls to smart contracts. The responsiveness of these calls relies not on the subgraph but on the connectivity and responsiveness of the Ethereum node being queried. By minimizing or eliminating eth_calls in our subgraphs, we can significantly improve our indexing speed.
+Subgraphs को स्मार्ट कॉन्ट्रैक्ट्स से निकले हुए इवेंट डेटा को इंडेक्स करने के लिए ऑप्टिमाइज़ किया गया है। एक subgraph ‘eth_call’ से आने वाले डेटा को भी इंडेक्स कर सकता है, लेकिन इससे subgraph इंडेक्सिंग काफी धीमी हो सकती है क्योंकि ‘eth_calls’ के लिए स्मार्ट कॉन्ट्रैक्ट्स को एक्सटर्नल कॉल्स करने की आवश्यकता होती है। इन कॉल्स की प्रतिक्रिया subgraph पर निर्भर नहीं करती, बल्कि उस Ethereum नोड की कनेक्टिविटी और प्रतिक्रिया पर निर्भर करती है, जिसे क्वेरी किया जा रहा है। हमारे subgraphs में ‘eth_calls’ को कम करके या पूरी तरह से समाप्त करके, हम अपने इंडेक्सिंग स्पीड में उल्लेखनीय सुधार कर सकते हैं।
 
-### What Does an eth_call Look Like?
+### एक eth_call कैसा दिखता है?
 
-`eth_calls` are often necessary when the data required for a subgraph is not available through emitted events. For example, consider a scenario where a subgraph needs to identify whether ERC20 tokens are part of a specific pool, but the contract only emits a basic `Transfer` event and does not emit an event that contains the data that we need:
+eth_calls अक्सर तब आवश्यक होते हैं जब subgraph के लिए आवश्यक डेटा इमिटेड इवेंट्स के माध्यम से उपलब्ध नहीं होता है। उदाहरण के लिए, एक ऐसा परिदृश्य मानें जहां एक subgraph को यह पहचानने की आवश्यकता है कि क्या ERC20 टोकन एक विशेष पूल का हिस्सा हैं, लेकिन कॉन्ट्रैक्ट केवल एक बुनियादी Transfer इवेंट इमिट करता है और वह इवेंट इमिट नहीं करता जिसमें हमें आवश्यक डेटा हो:
 
 ```yaml
-event Transfer(address indexed from, address indexed to, uint256 value);
+इवेंट Transfer(address indexed from, address indexed to, uint256 value);
 ```
 
-Suppose the tokens' pool membership is determined by a state variable named `getPoolInfo`. In this case, we would need to use an `eth_call` to query this data:
+मान लें कि टोकन्स की पूल सदस्यता एक state वेरिएबल getPoolInfo द्वारा निर्धारित होती है। इस मामले में, हमें इस डेटा को क्वेरी करने के लिए एक eth_call का उपयोग करना होगा:
 
 ```typescript
 import { Address } from '@graphprotocol/graph-ts'
@@ -28,10 +28,10 @@ import { TokenTransaction } from '../generated/schema'
 export function handleTransfer(event: Transfer): void {
   let transaction = new TokenTransaction(event.transaction.hash.toHex())
 
-  // Bind the ERC20 contract instance to the given address:
+  // दिए गए पते पर ERC20 कॉन्ट्रैक्ट इंस्टेंस को बाइंड करें:
   let instance = ERC20.bind(event.address)
 
-  // Retrieve pool information via eth_call
+  // eth_call के जरिए पूल जानकारी प्राप्त करें
   let poolInfo = instance.getPoolInfo(event.params.to)
 
   transaction.pool = poolInfo.toHexString()
@@ -43,17 +43,17 @@ export function handleTransfer(event: Transfer): void {
 }
 ```
 
-This is functional, however is not ideal as it slows down our subgraph’s indexing.
+यह कार्यात्मक है, हालांकि यह आदर्श नहीं है क्योंकि यह हमारे subgraph की indexing को धीमा कर देता है।
 
-## How to Eliminate `eth_calls`
+## Eth_calls को कैसे समाप्त करें
 
-Ideally, the smart contract should be updated to emit all necessary data within events. For instance, modifying the smart contract to include pool information in the event could eliminate the need for `eth_calls`:
+आदर्श रूप से, स्मार्ट कॉन्ट्रैक्ट को सभी आवश्यक डेटा को इवेंट्स के भीतर प्रकट करने के लिए अपडेट किया जाना चाहिए। उदाहरण के लिए, स्मार्ट कॉन्ट्रैक्ट में इवेंट में पूल जानकारी शामिल करने के लिए संशोधन करने से eth_calls की आवश्यकता को समाप्त किया जा सकता है:
 
 ```
 event TransferWithPool(address indexed from, address indexed to, uint256 value, bytes32 indexed poolInfo);
 ```
 
-With this update, the subgraph can directly index the required data without external calls:
+इस अपडेट के साथ, subgraph आवश्यक डेटा को बिना बाहरी कॉल के सीधे अनुक्रमित कर सकता है:
 
 ```typescript
 import { Address } from '@graphprotocol/graph-ts'
@@ -72,31 +72,45 @@ export function handleTransferWithPool(event: TransferWithPool): void {
 }
 ```
 
-This is much more performant as it has eliminated the need for `eth_calls`.
+यह बहुत अधिक प्रदर्शनकारी है क्योंकि इसने eth_calls की आवश्यकता को समाप्त कर दिया है।
 
-## How to Optimize `eth_calls`
+## Eth_calls को ऑप्टिमाइज़ करने का तरीका
 
-If modifying the smart contract is not possible and `eth_calls` are required, read “[Improve Subgraph Indexing Performance Easily: Reduce eth_calls](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/)” by Simon Emanuel Schmid to learn various strategies on how to optimize `eth_calls`.
+यदि स्मार्ट कॉन्ट्रैक्ट में परिवर्तन करना संभव नहीं है और eth_calls की आवश्यकता है, तो विभिन्न रणनीतियों को सीखने के लिए Improve Subgraph Indexing Performance Easily: Reduce eth_calls पढ़ें जो eth_calls को ऑप्टिमाइज़ करने के तरीके बताती है।
 
-## Reducing the Runtime Overhead of `eth_calls`
+## Eth_calls के रनटाइम ओवरहेड को कम करना
 
-For the `eth_calls` that can not be eliminated, the runtime overhead they introduce can be minimized by declaring them in the manifest. When `graph-node` processes a block it performs all declared `eth_calls` in parallel before handlers are run. Calls that are not declared are executed sequentially when handlers run. The runtime improvement comes from performing calls in parallel rather than sequentially - that helps reduce the total time spent in calls but does not eliminate it completely.
+जिन eth_calls को समाप्त नहीं किया जा सकता है, उनके द्वारा उत्पन्न रनटाइम ओवरहेड को मैनिफेस्ट में घोषित करके कम किया जा सकता है। जब graph-node एक ब्लॉक को प्रोसेस करता है, तो यह हैंडलर्स के चलने से पहले सभी घोषित eth_calls को समानांतर में प्रदर्शन करता है। जो कॉल घोषित नहीं हैं, वे हैंडलर्स के चलने के समय अनुक्रमिक रूप से निष्पादित होते हैं। रनटाइम में सुधार समानांतर में कॉल्स को करने से आता है, न कि अनुक्रमिक रूप से - यह कुल समय को कम करने में मदद करता है, लेकिन इसे पूरी तरह से समाप्त नहीं करता है।
 
-Currently, `eth_calls` can only be declared for event handlers. In the manifest, write
+वर्तमान में, eth_calls को केवल event handlers के लिए घोषित किया जा सकता है। मैनिफेस्ट में, लिखें
 
 ```yaml
-event: TransferWithPool(address indexed, address indexed, uint256, bytes32 indexed)
-handler: handleTransferWithPool
-calls:
+इवेंट: TransferWithPool(address indexed, address indexed, uint256, bytes32 indexed)
+हैंडलर: handleTransferWithPool
+कॉल्स:
   ERC20.poolInfo: ERC20[event.address].getPoolInfo(event.params.to)
 ```
 
-The portion highlighted in yellow is the call declaration. The part before the colon is simply a text label that is only used for error messages. The part after the colon has the form `Contract[address].function(params)`. Permissible values for address and params are `event.address` and `event.params.<name>`.
+पीले रंग में हाइलाइट किया गया हिस्सा कॉल डिक्लेरेशन है। कॉल के पहले वाले हिस्से में जो टेक्स्ट लेबल है, वह केवल त्रुटि संदेशों के लिए उपयोग किया जाता है। कॉल के बाद वाला हिस्सा Contract[address].function(params) के रूप में होता है। address और params के लिए मान event.address और event.params.<name> अनुमेय हैं।
 
-The handler itself accesses the result of this `eth_call` exactly as in the previous section by binding to the contract and making the call. graph-node caches the results of declared `eth_calls` in memory and the call from the handler will retrieve the result from this in memory cache instead of making an actual RPC call.
+Handler स्वयं इस eth_call के परिणाम तक ठीक उसी तरह पहुंचता है जैसे पिछले अनुभाग में, अनुबंध से बाइंडिंग करके और कॉल करके। graph-node घोषित eth_calls के परिणामों को मेमोरी में कैश करता है और हैंडलर से कॉल इस मेमोरी कैश से परिणाम प्राप्त करेगा, बजाय इसके कि एक वास्तविक RPC कॉल की जाए।
 
-Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0.
+नोट: घोषित eth_calls केवल उन subgraphs में किए जा सकते हैं जिनका specVersion >= 1.2.0 है।
 
-## Conclusion
+## निष्कर्ष
 
-We can significantly improve indexing performance by minimizing or eliminating `eth_calls` in our subgraphs.
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From e870b705fda76b06a006dbe227dd8abfeb517d4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:39 -0500
Subject: [PATCH 0571/1325] New translations derivedfrom.mdx (Hindi)

---
 website/pages/hi/cookbook/derivedfrom.mdx | 56 ++++++++++++++---------
 1 file changed, 35 insertions(+), 21 deletions(-)

diff --git a/website/pages/hi/cookbook/derivedfrom.mdx b/website/pages/hi/cookbook/derivedfrom.mdx
index 69dd48047744..3c8ffa04332a 100644
--- a/website/pages/hi/cookbook/derivedfrom.mdx
+++ b/website/pages/hi/cookbook/derivedfrom.mdx
@@ -1,28 +1,28 @@
 ---
-title: Subgraph Best Practice 2 - Improve Indexing and Query Responsiveness By Using @derivedFrom
+title: Subgraph सर्वोत्तम प्रथा 2 - @derivedFrom का उपयोग करके अनुक्रमण और क्वेरी की प्रतिक्रियाशीलता में सुधार करें।
 ---
 
-## TLDR
+## संक्षेप में
 
-Arrays in your schema can really slow down a subgraph's performance as they grow beyond thousands of entries. If possible, the `@derivedFrom` directive should be used when using arrays as it prevents large arrays from forming, simplifies handlers, and reduces the size of individual entities, improving indexing speed and query performance significantly.
+आपके स्कीमा में ऐरे हजारों प्रविष्टियों से बढ़ने पर एक सबग्राफ के प्रदर्शन को वास्तव में धीमा कर सकते हैं। यदि संभव हो, तो @derivedFrom निर्देशिका का उपयोग करना चाहिए जब आप ऐरे का उपयोग कर रहे हों, क्योंकि यह बड़े ऐरे के निर्माण को रोकता है, हैंडलरों को सरल बनाता है और व्यक्तिगत संस्थाओं के आकार को कम करता है, जिससे अनुक्रमण गति और प्रश्न प्रदर्शन में महत्वपूर्ण सुधार होता है।
 
-## How to Use the `@derivedFrom` Directive
+## @derivedFrom निर्देशिका का उपयोग कैसे करें
 
-You just need to add a `@derivedFrom` directive after your array in your schema. Like this:
+आपको बस अपने स्कीमा में अपने एरे के बाद एक @derivedFrom निर्देशिका जोड़ने की आवश्यकता है। ऐसा:
 
 ```graphql
-comments: [Comment!]! @derivedFrom(field: "post")
+टिप्पणियाँ : [Comment!]! @derivedFrom(field: “post”)
 ```
 
-`@derivedFrom` creates efficient one-to-many relationships, enabling an entity to dynamically associate with multiple related entities based on a field in the related entity. This approach removes the need for both sides of the relationship to store duplicate data, making the subgraph more efficient.
+@derivedFrom कुशल एक से कई संबंध बनाता है, जिससे एक इकाई को संबंधित इकाई में एक फ़ील्ड के आधार पर कई संबंधित इकाइयों के साथ गतिशील रूप से संबंध बनाने की अनुमति मिलती है। यह दृष्टिकोण रिश्ते के दोनों पक्षों को डुप्लिकेट डेटा संग्रहीत करने की आवश्यकता को समाप्त करता है, जिससे subgraph अधिक कुशल बन जाता है।
 
-### Example Use Case for `@derivedFrom`
+### @derivedFrom के लिए उदाहरण उपयोग मामला
 
-An example of a dynamically growing array is a blogging platform where a “Post” can have many “Comments”.
+एक गतिशील रूप से बढ़ने वाले ऐरे का एक उदाहरण एक ब्लॉगिंग प्लेटफ़ॉर्म है जहाँ एक “Post” के कई “Comments” हो सकते हैं।
 
-Let’s start with our two entities, `Post` and `Comment`
+आइए हम अपनी दो संस्थाओं, Post और Comment के साथ शुरू करते हैं।
 
-Without optimization, you could implement it like this with an array:
+बिना ऑप्टिमाइजेशन के, आप इसे एक ऐरे के साथ इस प्रकार लागू कर सकते हैं:
 
 ```graphql
 type Post @entity {
@@ -38,9 +38,9 @@ type Comment @entity {
 }
 ```
 
-Arrays like these will effectively store extra Comments data on the Post side of the relationship.
+इस तरह के ऐरे प्रभावी रूप से संबंध के पोस्ट पक्ष पर अतिरिक्त Comments डेटा को संग्रहीत करेंगे।
 
-Here’s what an optimized version looks like using `@derivedFrom`:
+यहाँ एक अनुकूलित संस्करण है जो @derivedFrom का उपयोग करता है:
 
 ```graphql
 type Post @entity {
@@ -57,18 +57,32 @@ type Comment @entity {
 }
 ```
 
-Just by adding the `@derivedFrom` directive, this schema will only store the “Comments” on the “Comments” side of the relationship and not on the “Post” side of the relationship. Arrays are stored across individual rows, which allows them to expand significantly. This can lead to particularly large sizes if their growth is unbounded.
+बस @derivedFrom निर्देश जोड़ने से, यह स्कीमा केवल संबंध के “Comments” पक्ष पर “Comments” को संग्रहीत करेगा और संबंध के “Post” पक्ष पर नहीं। ऐरे व्यक्तिगत पंक्तियों में संग्रहीत होते हैं, जिससे उन्हें काफी विस्तार करने की अनुमति मिलती है। यदि उनका विकास अनियंत्रित है, तो इससे विशेष रूप से बड़े आकार हो सकते हैं।
 
-This will not only make our subgraph more efficient, but it will also unlock three features:
+यह न केवल हमारे subgraph को अधिक प्रभावी बनाएगा, बल्कि यह तीन विशेषताओं को भी अनलॉक करेगा:
 
-1. We can query the `Post` and see all of its comments.
+1. हम Post को क्वेरी कर सकते हैं और इसके सभी कमेंट्स देख सकते हैं।
 
-2. We can do a reverse lookup and query any `Comment` and see which post it comes from.
+2. हम एक रिवर्स लुकअप कर सकते हैं और किसी भी Comment को क्वेरी कर सकते हैं और देख सकते हैं कि यह किस पोस्ट से आया है।
 
-3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings.
+3. हम [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) का उपयोग कर सकते हैं ताकि हमारे Subgraph मैपिंग में वर्चुअल संबंधों से डेटा को सीधे एक्सेस और संपादित करने की क्षमता को अनलॉक किया जा सके।
 
-## Conclusion
+## निष्कर्ष
 
-Adopting the `@derivedFrom` directive in subgraphs effectively handles dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
 
-To learn more detailed strategies to avoid large arrays, read this blog from Kevin Jones: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From c18caf352e4527b1ddc849f84a50c2009d3875f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:40 -0500
Subject: [PATCH 0572/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Hindi)

---
 .../immutable-entities-bytes-as-ids.mdx       | 76 +++++++++++--------
 1 file changed, 45 insertions(+), 31 deletions(-)

diff --git a/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx
index f38c33385604..4875006914e4 100644
--- a/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -1,14 +1,14 @@
 ---
-title: Subgraph Best Practice 3 - Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs
+title: सबग्राफ सर्वश्रेष्ठ प्रथा 3 - अपरिवर्तनीय संस्थाओं और बाइट्स को आईडी के रूप में उपयोग करके अनुक्रमण और क्वेरी प्रदर्शन में सुधार करें।
 ---
 
 ## TLDR
 
-Using Immutable Entities and Bytes for IDs in our `schema.graphql` file [significantly improves ](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/) indexing speed and query performance.
+हमारे schema.graphql फ़ाइल में अमूर्त एंटिटीज और आईडी के लिए बाइट्स का उपयोग सूचक गति और क्वेरी प्रदर्शन में [महत्वपूर्ण सुधार](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/) करता है।
 
-## Immutable Entities
+## अमूर्त एंटिटीज
 
-To make an entity immutable, we simply add `(immutable: true)` to an entity.
+एक एंटिटी को अमूर्त बनाने के लिए, हम बस एंटिटी में (immutable: true) जोड़ते हैं।
 
 ```graphql
 type Transfer @entity(immutable: true) {
@@ -19,21 +19,21 @@ type Transfer @entity(immutable: true) {
 }
 ```
 
-By making the `Transfer` entity immutable, graph-node is able to process the entity more efficiently, improving indexing speeds and query responsiveness.
+Transfer एंटिटी को अमूर्त बनाने से, graph-node एंटिटी को अधिक कुशलता से संसाधित कर सकता है, जिससे indexing गति और क्वेरी की प्रतिक्रिया में सुधार होता है।
 
-Immutable Entities structures will not change in the future. An ideal entity to become an Immutable Entity would be an entity that is directly logging on-chain event data, such as a `Transfer` event being logged as a `Transfer` entity.
+Immutable Entities संरचनाएँ भविष्य में नहीं बदलेंगी। एक आदर्श एंटिटी जो अमूर्त एंटिटी बनेगी, वह एंटिटी होगी जो सीधे ऑन-चेन इवेंट डेटा को लॉग कर रही है, जैसे कि Transfer इवेंट को Transfer एंटिटी के रूप में लॉग किया जाना।
 
-### Under the hood
+### हुड के नीचे
 
-Mutable entities have a 'block range' indicating their validity. Updating these entities requires the graph node to adjust the block range of previous versions, increasing database workload. Queries also need filtering to find only live entities. Immutable entities are faster because they are all live and since they won't change, no checks or updates are required while writing, and no filtering is required during queries.
+परिवर्तनीय एंटिटियों में एक ‘ब्लॉक रेंज’ होती है जो उनकी वैधता को इंगित करती है। इन एंटिटियों को अपडेट करने के लिए ग्राफ नोड को पिछले संस्करणों की ब्लॉक रेंज को समायोजित करना पड़ता है, जिससे डेटाबेस का कार्यभार बढ़ जाता है। क्वेरियों को भी केवल जीवित एंटिटियों को खोजने के लिए फ़िल्टर करने की आवश्यकता होती है। अमूर्त एंटिटियाँ तेज होती हैं क्योंकि ये सभी जीवित होती हैं और चूंकि ये नहीं बदलेंगी, लिखते समय किसी भी चेक या अपडेट की आवश्यकता नहीं होती, और क्वेरियों के दौरान कोई फ़िल्टरिंग की आवश्यकता नहीं होती।
 
-### When not to use Immutable Entities
+### अमूर्त एंटिटीज का उपयोग कब न करें
 
-If you have a field like `status` that needs to be modified over time, then you should not make the entity immutable. Otherwise, you should use immutable entities whenever possible.
+अगर आपके पास एक ऐसा फ़ील्ड है जैसे status जिसे समय के साथ संशोधित करने की आवश्यकता है, तो आपको एंटिटी को अमूर्त नहीं बनाना चाहिए। अन्यथा, आपको जब भी संभव हो, अमूर्त एंटिटीज का उपयोग करना चाहिए।
 
-## Bytes as IDs
+## Bytes को IDs के रूप में
 
-Every entity requires an ID. In the previous example, we can see that the ID is already of the Bytes type.
+हर एंटिटी के लिए एक ID की आवश्यकता होती है। पिछले उदाहरण में, हम देख सकते हैं कि ID पहले से ही Bytes प्रकार की है।
 
 ```graphql
 type Transfer @entity(immutable: true) {
@@ -44,19 +44,19 @@ type Transfer @entity(immutable: true) {
 }
 ```
 
-While other types for IDs are possible, such as String and Int8, it is recommended to use the Bytes type for all IDs due to character strings taking twice as much space as Byte strings to store binary data, and comparisons of UTF-8 character strings must take the locale into account which is much more expensive than the bytewise comparison used to compare Byte strings.
+हालांकि IDs के लिए अन्य प्रकार संभव हैं, जैसे String और Int8, लेकिन सभी IDs के लिए Bytes प्रकार का उपयोग करने की सिफारिश की जाती है क्योंकि चरित्र स्ट्रिंग्स को बाइनरी डेटा संग्रहीत करने के लिए बाइट स्ट्रिंग्स की तुलना में दोगुना स्थान चाहिए, और UTF-8 चरित्र स्ट्रिंग्स की तुलना करते समय स्थानीय भाषा का ध्यान रखना आवश्यक है, जो बाइट स्ट्रिंग्स की तुलना के लिए उपयोग की जाने वाली बाइटवाइज तुलना की तुलना में बहुत अधिक महंगा है।
 
-### Reasons to Not Use Bytes as IDs
+### IDs के रूप में Bytes का उपयोग न करने के कारण
 
-1. If entity IDs must be human-readable such as auto-incremented numerical IDs or readable strings, Bytes for IDs should not be used.
-2. If integrating a subgraph’s data with another data model that does not use Bytes as IDs, Bytes as IDs should not be used.
-3. Indexing and querying performance improvements are not desired.
+1. यदि एंटिटी IDs मानव-पठनीय होने चाहिए, जैसे कि ऑटो-इंक्रीमेंटेड न्यूमेरिकल IDs या पठनीय स्ट्रिंग्स, तो IDs के लिए Bytes का उपयोग नहीं किया जाना चाहिए।
+2. यदि किसी subgraph के डेटा को दूसरे डेटा मॉडल के साथ एकीकृत किया जा रहा है जो IDs के रूप में Bytes का उपयोग नहीं करता है, तो Bytes के रूप में IDs का उपयोग नहीं किया जाना चाहिए।
+3. Indexing और क्वेरीिंग प्रदर्शन में सुधार की आवश्यकता नहीं है।
 
-### Concatenating With Bytes as IDs
+### Bytes के रूप में IDs के साथ जोड़ना
 
-It is a common practice in many subgraphs to use string concatenation to combine two properties of an event into a single ID, such as using `event.transaction.hash.toHex() + "-" + event.logIndex.toString()`. However, as this returns a string, this significantly impedes subgraph indexing and querying performance.
+बहुत से subgraphs में एक ID में दो प्रॉपर्टीज को जोड़ने के लिए स्ट्रिंग संयोजन का उपयोग करना एक सामान्य प्रथा है, जैसे कि event.transaction.hash.toHex() + "-" + event.logIndex.toString() का उपयोग करना। हालांकि, चूंकि यह एक स्ट्रिंग लौटाता है, यह subgraph इंडेक्सिंग और क्वेरी प्रदर्शन में महत्वपूर्ण रूप से बाधा डालता है।
 
-Instead, we should use the `concatI32()` method to concatenate event properties. This strategy results in a `Bytes` ID that is much more performant.
+इसके बजाय, हमें event properties को जोड़ने के लिए concatI32() method का उपयोग करना चाहिए। यह रणनीति एक Bytes ID उत्पन्न करती है जो बहुत अधिक performant होती है।
 
 ```typescript
 export function handleTransfer(event: TransferEvent): void {
@@ -73,9 +73,9 @@ export function handleTransfer(event: TransferEvent): void {
 }
 ```
 
-### Sorting With Bytes as IDs
+### Bytes के रूप में IDs के साथ क्रमबद्ध करना
 
-Sorting using Bytes as IDs is not optimal as seen in this example query and response.
+Bytes को IDs के रूप में उपयोग करके क्रमबद्ध करना इस उदाहरण क्वेरी और प्रतिक्रिया में देखे गए अनुसार उपयुक्त नहीं है।
 
 Query:
 
@@ -90,7 +90,7 @@ Query:
 }
 ```
 
-Query response:
+प्रश्न प्रतिक्रिया: 
 
 ```json
 {
@@ -119,9 +119,9 @@ Query response:
 }
 ```
 
-The IDs are returned as hex.
+IDs,hex के रूप में वापस किए जाते हैं।
 
-To improve sorting, we should create another field on the entity that is a BigInt.
+क्रमबद्धता में सुधार करने के लिए, हमें इकाई पर एक और फ़ील्ड बनानी चाहिए जो एक BigInt हो।
 
 ```graphql
 type Transfer @entity {
@@ -133,9 +133,9 @@ type Transfer @entity {
 }
 ```
 
-This will allow for sorting to be optimized sequentially.
+इससे क्रमबद्धता को क्रमिक रूप से अनुकूलित करने की अनुमति मिलेगी।
 
-Query:
+Query
 
 ```graphql
 {
@@ -146,7 +146,7 @@ Query:
 }
 ```
 
-Query Response:
+प्रश्न प्रतिक्रिया: 
 
 ```json
 {
@@ -169,8 +169,22 @@ Query Response:
 }
 ```
 
-## Conclusion
+## निष्कर्ष
+
+Immutable Entities और Bytes को IDs के रूप में उपयोग करने से subgraph की दक्षता में उल्लेखनीय सुधार हुआ है। विशेष रूप से, परीक्षणों ने क्वेरी प्रदर्शन में 28% तक की वृद्धि और indexing स्पीड में 48% तक की तेजी को उजागर किया है।
+
+इस ब्लॉग पोस्ट में, Edge & Node के सॉफ़्टवेयर इंजीनियर डेविड लुटरकोर्ट द्वारा Immutable Entities और Bytes को IDs के रूप में उपयोग करने के बारे में और अधिक पढ़ें: [दो सरल Subgraph प्रदर्शन सुधार।](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 4be3e8fe2902f547fd829ca6bdecb4f6f8cda559 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:42 -0500
Subject: [PATCH 0573/1325] New translations pruning.mdx (Hindi)

---
 website/pages/hi/cookbook/pruning.mdx | 42 ++++++++++++++++++---------
 1 file changed, 28 insertions(+), 14 deletions(-)

diff --git a/website/pages/hi/cookbook/pruning.mdx b/website/pages/hi/cookbook/pruning.mdx
index f22a2899f1de..dbf07aa15e60 100644
--- a/website/pages/hi/cookbook/pruning.mdx
+++ b/website/pages/hi/cookbook/pruning.mdx
@@ -1,22 +1,22 @@
 ---
-title: Subgraph Best Practice 1 - Improve Query Speed with Subgraph Pruning
+title: सबग्राफ बेस्ट प्रैक्टिस 1 - सबग्राफ प्रूनिंग के साथ क्वेरी की गति में सुधार करें
 ---
 
 ## TLDR
 
-[Pruning](/developing/creating-a-subgraph/#prune) removes archival entities from the subgraph’s database up to a given block, and removing unused entities from a subgraph’s database will improve a subgraph’s query performance, often dramatically. Using `indexerHints` is an easy way to prune a subgraph.
+Pruning(/developing/creating-a-subgraph/#prune), subgraph के डेटाबेस से दिए गए ब्लॉक तक की archival entities को हटाता है, और unused entities को subgraph के डेटाबेस से हटाने से subgraph की query performance में सुधार होगा, अक्सर काफी हद तक। indexerHints का उपयोग करना subgraph को prune करने का एक आसान तरीका है।
 
-## How to Prune a Subgraph With `indexerHints`
+## IndexerHints के साथ subgraph को prune करने का तरीका
 
-Add a section called `indexerHints` in the manifest.
+Manifest में एक section को indexerHints के नाम से जोड़ें।
 
-`indexerHints` has three `prune` options:
+indexerHints में तीन prune विकल्प होते हैं:
 
-- `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0.
-- `prune: <Number of blocks to retain>`: Sets a custom limit on the number of historical blocks to retain.
-- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired.
+- prune: auto: आवश्यक न्यूनतम इतिहास को बनाए रखता है जैसा कि Indexer द्वारा निर्धारित किया गया है, जो क्वेरी प्रदर्शन को अनुकूलित करता है। यह सामान्यतः अनुशंसित सेटिंग है और यह सभी subgraphs के लिए डिफ़ॉल्ट है जो graph-cli >= 0.66.0 द्वारा बनाए गए हैं।
+- prune: <Number of blocks to retain>: ऐतिहासिक ब्लॉकों को बनाए रखने की संख्या पर एक कस्टम सीमा निर्धारित करता है।
+- prune: never: ऐतिहासिक डेटा का कोई छंटाई नहीं; पूरी इतिहास को बनाए रखता है और यह डिफ़ॉल्ट है यदि indexerHints अनुभाग नहीं है। prune: never को तब चुना जाना चाहिए यदि Time Travel Queries (/querying/graphql-api/#time-travel-queries)की आवश्यकता हो।
 
-We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`:
+हम अपने 'subgraph' में indexerHints जोड़ सकते हैं हमारे subgraph.yaml को अपडेट करके:
 
 ```yaml
 specVersion: 1.0.0
@@ -30,12 +30,26 @@ dataSources:
     network: mainnet
 ```
 
-## Important Considerations
+## महत्वपूर्ण विचार
 
-- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: <Number of blocks to retain>` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data.
+- यदि Time Travel Queries(/querying/graphql-api/#time-travel-queries) की आवश्यकता हो और प्रूनिंग भी की जाए, तो Time Travel Query कार्यक्षमता बनाए रखने के लिए प्रूनिंग को सही ढंग से किया जाना चाहिए। इसलिए, Time Travel Queries के साथ indexerHints: prune: auto का उपयोग करना सामान्यतः अनुशंसित नहीं है। इसके बजाय, उस ब्लॉक ऊंचाई तक सही ढंग से प्रून करने के लिए indexerHints: prune: <Number of blocks to retain> का उपयोग करें जो Time Travel Queries के लिए आवश्यक ऐतिहासिक डेटा को बनाए रखता है, या prune: never का उपयोग करें ताकि सभी डेटा बनाए रखा जा सके।
 
-- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: <Number of blocks to retain>` that will accurately retain a set number of blocks (e.g., enough for six months).
+- यह 'grafting' (/cookbook/grafting/) को उस ब्लॉक ऊँचाई पर करना संभव नहीं है जो छंटनी (pruned) की गई है। यदि 'grafting' नियमित रूप से किया जाता है और छंटनी (pruning) की आवश्यकता है, तो यह अनुशंसा की जाती है कि indexerHints: prune: <Number of blocks to retain> का उपयोग किया जाए जो सटीक रूप से एक निश्चित संख्या में ब्लॉकों (जैसे, छह महीने के लिए पर्याप्त) को बनाए रखेगा।
 
-## Conclusion
+## निष्कर्ष
 
-Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+Pruning का उपयोग indexerHints से करना एक सर्वोत्तम प्रथा है subgraph विकास के लिए, जो महत्वपूर्ण क्वेरी प्रदर्शन सुधार प्रदान करता है।
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From f01ce905e6936f2357447e875fc778c143b6a075 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:43 -0500
Subject: [PATCH 0574/1325] New translations avoid-eth-calls.mdx (Swahili)

---
 website/pages/sw/cookbook/avoid-eth-calls.mdx | 116 ++++++++++++++++++
 1 file changed, 116 insertions(+)
 create mode 100644 website/pages/sw/cookbook/avoid-eth-calls.mdx

diff --git a/website/pages/sw/cookbook/avoid-eth-calls.mdx b/website/pages/sw/cookbook/avoid-eth-calls.mdx
new file mode 100644
index 000000000000..8897ecdbfdc7
--- /dev/null
+++ b/website/pages/sw/cookbook/avoid-eth-calls.mdx
@@ -0,0 +1,116 @@
+---
+title: Subgraph Best Practice 4 - Improve Indexing Speed by Avoiding eth_calls
+---
+
+## TLDR
+
+`eth_calls` are calls that can be made from a subgraph to an Ethereum node. These calls take a significant amount of time to return data, slowing down indexing. If possible, design smart contracts to emit all the data you need so you don’t need to use `eth_calls`.
+
+## Why Avoiding `eth_calls` Is a Best Practice
+
+Subgraphs are optimized to index event data emitted from smart contracts. A subgraph can also index the data coming from an `eth_call`, however, this can significantly slow down subgraph indexing as `eth_calls` require making external calls to smart contracts. The responsiveness of these calls relies not on the subgraph but on the connectivity and responsiveness of the Ethereum node being queried. By minimizing or eliminating eth_calls in our subgraphs, we can significantly improve our indexing speed.
+
+### What Does an eth_call Look Like?
+
+`eth_calls` are often necessary when the data required for a subgraph is not available through emitted events. For example, consider a scenario where a subgraph needs to identify whether ERC20 tokens are part of a specific pool, but the contract only emits a basic `Transfer` event and does not emit an event that contains the data that we need:
+
+```yaml
+event Transfer(address indexed from, address indexed to, uint256 value);
+```
+
+Suppose the tokens' pool membership is determined by a state variable named `getPoolInfo`. In this case, we would need to use an `eth_call` to query this data:
+
+```typescript
+import { Address } from '@graphprotocol/graph-ts'
+import { ERC20, Transfer } from '../generated/ERC20/ERC20'
+import { TokenTransaction } from '../generated/schema'
+
+export function handleTransfer(event: Transfer): void {
+  let transaction = new TokenTransaction(event.transaction.hash.toHex())
+
+  // Bind the ERC20 contract instance to the given address:
+  let instance = ERC20.bind(event.address)
+
+  // Retrieve pool information via eth_call
+  let poolInfo = instance.getPoolInfo(event.params.to)
+
+  transaction.pool = poolInfo.toHexString()
+  transaction.from = event.params.from.toHexString()
+  transaction.to = event.params.to.toHexString()
+  transaction.value = event.params.value
+
+  transaction.save()
+}
+```
+
+This is functional, however is not ideal as it slows down our subgraph’s indexing.
+
+## How to Eliminate `eth_calls`
+
+Ideally, the smart contract should be updated to emit all necessary data within events. For instance, modifying the smart contract to include pool information in the event could eliminate the need for `eth_calls`:
+
+```
+event TransferWithPool(address indexed from, address indexed to, uint256 value, bytes32 indexed poolInfo);
+```
+
+With this update, the subgraph can directly index the required data without external calls:
+
+```typescript
+import { Address } from '@graphprotocol/graph-ts'
+import { ERC20, TransferWithPool } from '../generated/ERC20/ERC20'
+import { TokenTransaction } from '../generated/schema'
+
+export function handleTransferWithPool(event: TransferWithPool): void {
+  let transaction = new TokenTransaction(event.transaction.hash.toHex())
+
+  transaction.pool = event.params.poolInfo.toHexString()
+  transaction.from = event.params.from.toHexString()
+  transaction.to = event.params.to.toHexString()
+  transaction.value = event.params.value
+
+  transaction.save()
+}
+```
+
+This is much more performant as it has eliminated the need for `eth_calls`.
+
+## How to Optimize `eth_calls`
+
+If modifying the smart contract is not possible and `eth_calls` are required, read “[Improve Subgraph Indexing Performance Easily: Reduce eth_calls](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/)” by Simon Emanuel Schmid to learn various strategies on how to optimize `eth_calls`.
+
+## Reducing the Runtime Overhead of `eth_calls`
+
+For the `eth_calls` that can not be eliminated, the runtime overhead they introduce can be minimized by declaring them in the manifest. When `graph-node` processes a block it performs all declared `eth_calls` in parallel before handlers are run. Calls that are not declared are executed sequentially when handlers run. The runtime improvement comes from performing calls in parallel rather than sequentially - that helps reduce the total time spent in calls but does not eliminate it completely.
+
+Currently, `eth_calls` can only be declared for event handlers. In the manifest, write
+
+```yaml
+event: TransferWithPool(address indexed, address indexed, uint256, bytes32 indexed)
+handler: handleTransferWithPool
+calls:
+  ERC20.poolInfo: ERC20[event.address].getPoolInfo(event.params.to)
+```
+
+The portion highlighted in yellow is the call declaration. The part before the colon is simply a text label that is only used for error messages. The part after the colon has the form `Contract[address].function(params)`. Permissible values for address and params are `event.address` and `event.params.<name>`.
+
+The handler itself accesses the result of this `eth_call` exactly as in the previous section by binding to the contract and making the call. graph-node caches the results of declared `eth_calls` in memory and the call from the handler will retrieve the result from this in memory cache instead of making an actual RPC call.
+
+Note: Declared eth_calls can only be made in subgraphs with specVersion >= 1.2.0.
+
+## Conclusion
+
+You can significantly improve indexing performance by minimizing or eliminating `eth_calls` in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From b199c0c9f7387278d8680523b9b44ab31e8ef692 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:44 -0500
Subject: [PATCH 0575/1325] New translations derivedfrom.mdx (Swahili)

---
 website/pages/sw/cookbook/derivedfrom.mdx | 88 +++++++++++++++++++++++
 1 file changed, 88 insertions(+)
 create mode 100644 website/pages/sw/cookbook/derivedfrom.mdx

diff --git a/website/pages/sw/cookbook/derivedfrom.mdx b/website/pages/sw/cookbook/derivedfrom.mdx
new file mode 100644
index 000000000000..09ba62abde3f
--- /dev/null
+++ b/website/pages/sw/cookbook/derivedfrom.mdx
@@ -0,0 +1,88 @@
+---
+title: Subgraph Best Practice 2 - Improve Indexing and Query Responsiveness By Using @derivedFrom
+---
+
+## TLDR
+
+Arrays in your schema can really slow down a subgraph's performance as they grow beyond thousands of entries. If possible, the `@derivedFrom` directive should be used when using arrays as it prevents large arrays from forming, simplifies handlers, and reduces the size of individual entities, improving indexing speed and query performance significantly.
+
+## How to Use the `@derivedFrom` Directive
+
+You just need to add a `@derivedFrom` directive after your array in your schema. Like this:
+
+```graphql
+comments: [Comment!]! @derivedFrom(field: "post")
+```
+
+`@derivedFrom` creates efficient one-to-many relationships, enabling an entity to dynamically associate with multiple related entities based on a field in the related entity. This approach removes the need for both sides of the relationship to store duplicate data, making the subgraph more efficient.
+
+### Example Use Case for `@derivedFrom`
+
+An example of a dynamically growing array is a blogging platform where a “Post” can have many “Comments”.
+
+Let’s start with our two entities, `Post` and `Comment`
+
+Without optimization, you could implement it like this with an array:
+
+```graphql
+type Post @entity {
+  id: Bytes!
+  title: String!
+  content: String!
+  comments: [Comment!]!
+}
+
+type Comment @entity {
+  id: Bytes!
+  content: String!
+}
+```
+
+Arrays like these will effectively store extra Comments data on the Post side of the relationship.
+
+Here’s what an optimized version looks like using `@derivedFrom`:
+
+```graphql
+type Post @entity {
+  id: Bytes!
+  title: String!
+  content: String!
+  comments: [Comment!]! @derivedFrom(field: "post")
+}
+
+type Comment @entity {
+  id: Bytes!
+  content: String!
+  post: Post!
+}
+```
+
+Just by adding the `@derivedFrom` directive, this schema will only store the “Comments” on the “Comments” side of the relationship and not on the “Post” side of the relationship. Arrays are stored across individual rows, which allows them to expand significantly. This can lead to particularly large sizes if their growth is unbounded.
+
+This will not only make our subgraph more efficient, but it will also unlock three features:
+
+1. We can query the `Post` and see all of its comments.
+
+2. We can do a reverse lookup and query any `Comment` and see which post it comes from.
+
+3. We can use [Derived Field Loaders](/developing/graph-ts/api/#looking-up-derived-entities) to unlock the ability to directly access and manipulate data from virtual relationships in our subgraph mappings.
+
+## Conclusion
+
+Use the `@derivedFrom` directive in subgraphs to effectively manage dynamically growing arrays, enhancing indexing efficiency and data retrieval.
+
+For a more detailed explanation of strategies to avoid large arrays, check out Kevin Jones' blog: [Best Practices in Subgraph Development: Avoiding Large Arrays](https://thegraph.com/blog/improve-subgraph-performance-avoiding-large-arrays/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 3fc5979ade5e5d17bfbbc6de458b81f73765d071 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:44 -0500
Subject: [PATCH 0576/1325] New translations
 immutable-entities-bytes-as-ids.mdx (Swahili)

---
 .../immutable-entities-bytes-as-ids.mdx       | 190 ++++++++++++++++++
 1 file changed, 190 insertions(+)
 create mode 100644 website/pages/sw/cookbook/immutable-entities-bytes-as-ids.mdx

diff --git a/website/pages/sw/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/sw/cookbook/immutable-entities-bytes-as-ids.mdx
new file mode 100644
index 000000000000..541212617f9f
--- /dev/null
+++ b/website/pages/sw/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -0,0 +1,190 @@
+---
+title: Subgraph Best Practice 3 - Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs
+---
+
+## TLDR
+
+Using Immutable Entities and Bytes for IDs in our `schema.graphql` file [significantly improves ](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/) indexing speed and query performance.
+
+## Immutable Entities
+
+To make an entity immutable, we simply add `(immutable: true)` to an entity.
+
+```graphql
+type Transfer @entity(immutable: true) {
+  id: Bytes!
+  from: Bytes!
+  to: Bytes!
+  value: BigInt!
+}
+```
+
+By making the `Transfer` entity immutable, graph-node is able to process the entity more efficiently, improving indexing speeds and query responsiveness.
+
+Immutable Entities structures will not change in the future. An ideal entity to become an Immutable Entity would be an entity that is directly logging on-chain event data, such as a `Transfer` event being logged as a `Transfer` entity.
+
+### Under the hood
+
+Mutable entities have a 'block range' indicating their validity. Updating these entities requires the graph node to adjust the block range of previous versions, increasing database workload. Queries also need filtering to find only live entities. Immutable entities are faster because they are all live and since they won't change, no checks or updates are required while writing, and no filtering is required during queries.
+
+### When not to use Immutable Entities
+
+If you have a field like `status` that needs to be modified over time, then you should not make the entity immutable. Otherwise, you should use immutable entities whenever possible.
+
+## Bytes as IDs
+
+Every entity requires an ID. In the previous example, we can see that the ID is already of the Bytes type.
+
+```graphql
+type Transfer @entity(immutable: true) {
+  id: Bytes!
+  from: Bytes!
+  to: Bytes!
+  value: BigInt!
+}
+```
+
+While other types for IDs are possible, such as String and Int8, it is recommended to use the Bytes type for all IDs due to character strings taking twice as much space as Byte strings to store binary data, and comparisons of UTF-8 character strings must take the locale into account which is much more expensive than the bytewise comparison used to compare Byte strings.
+
+### Reasons to Not Use Bytes as IDs
+
+1. If entity IDs must be human-readable such as auto-incremented numerical IDs or readable strings, Bytes for IDs should not be used.
+2. If integrating a subgraph’s data with another data model that does not use Bytes as IDs, Bytes as IDs should not be used.
+3. Indexing and querying performance improvements are not desired.
+
+### Concatenating With Bytes as IDs
+
+It is a common practice in many subgraphs to use string concatenation to combine two properties of an event into a single ID, such as using `event.transaction.hash.toHex() + "-" + event.logIndex.toString()`. However, as this returns a string, this significantly impedes subgraph indexing and querying performance.
+
+Instead, we should use the `concatI32()` method to concatenate event properties. This strategy results in a `Bytes` ID that is much more performant.
+
+```typescript
+export function handleTransfer(event: TransferEvent): void {
+  let entity = new Transfer(event.transaction.hash.concatI32(event.logIndex.toI32()))
+  entity.from = event.params.from
+  entity.to = event.params.to
+  entity.value = event.params.value
+
+  entity.blockNumber = event.block.number
+  entity.blockTimestamp = event.block.timestamp
+  entity.transactionHash = event.transaction.hash
+
+  entity.save()
+}
+```
+
+### Sorting With Bytes as IDs
+
+Sorting using Bytes as IDs is not optimal as seen in this example query and response.
+
+Query:
+
+```graphql
+{
+  transfers(first: 3, orderBy: id) {
+    id
+    from
+    to
+    value
+  }
+}
+```
+
+Query response:
+
+```json
+{
+  "data": {
+    "transfers": [
+      {
+        "id": "0x00010000",
+        "from": "0xabcd...",
+        "to": "0x1234...",
+        "value": "256"
+      },
+      {
+        "id": "0x00020000",
+        "from": "0xefgh...",
+        "to": "0x5678...",
+        "value": "512"
+      },
+      {
+        "id": "0x01000000",
+        "from": "0xijkl...",
+        "to": "0x9abc...",
+        "value": "1"
+      }
+    ]
+  }
+}
+```
+
+The IDs are returned as hex.
+
+To improve sorting, we should create another field on the entity that is a BigInt.
+
+```graphql
+type Transfer @entity {
+  id: Bytes!
+  from: Bytes! # address
+  to: Bytes! # address
+  value: BigInt! # unit256
+  tokenId: BigInt! # uint256
+}
+```
+
+This will allow for sorting to be optimized sequentially.
+
+Query:
+
+```graphql
+{
+  transfers(first: 3, orderBy: tokenId) {
+    id
+    tokenId
+  }
+}
+```
+
+Query Response:
+
+```json
+{
+  "data": {
+    "transfers": [
+      {
+        "id": "0x…",
+        "tokenId": "1"
+      },
+      {
+        "id": "0x…",
+        "tokenId": "2"
+      },
+      {
+        "id": "0x…",
+        "tokenId": "3"
+      }
+    ]
+  }
+}
+```
+
+## Conclusion
+
+Using both Immutable Entities and Bytes as IDs has been shown to markedly improve subgraph efficiency. Specifically, tests have highlighted up to a 28% increase in query performance and up to a 48% acceleration in indexing speeds.
+
+Read more about using Immutable Entities and Bytes as IDs in this blog post by David Lutterkort, a Software Engineer at Edge & Node: [Two Simple Subgraph Performance Improvements](https://thegraph.com/blog/two-simple-subgraph-performance-improvements/).
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a30062d2c9d6454fbb9ef100c42d96295dd8b7b6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:45 -0500
Subject: [PATCH 0577/1325] New translations pruning.mdx (Swahili)

---
 website/pages/sw/cookbook/pruning.mdx | 55 +++++++++++++++++++++++++++
 1 file changed, 55 insertions(+)
 create mode 100644 website/pages/sw/cookbook/pruning.mdx

diff --git a/website/pages/sw/cookbook/pruning.mdx b/website/pages/sw/cookbook/pruning.mdx
new file mode 100644
index 000000000000..d86bf50edf42
--- /dev/null
+++ b/website/pages/sw/cookbook/pruning.mdx
@@ -0,0 +1,55 @@
+---
+title: Subgraph Best Practice 1 - Improve Query Speed with Subgraph Pruning
+---
+
+## TLDR
+
+[Pruning](/developing/creating-a-subgraph/#prune) removes archival entities from the subgraph’s database up to a given block, and removing unused entities from a subgraph’s database will improve a subgraph’s query performance, often dramatically. Using `indexerHints` is an easy way to prune a subgraph.
+
+## How to Prune a Subgraph With `indexerHints`
+
+Add a section called `indexerHints` in the manifest.
+
+`indexerHints` has three `prune` options:
+
+- `prune: auto`: Retains the minimum necessary history as set by the Indexer, optimizing query performance. This is the generally recommended setting and is the default for all subgraphs created by `graph-cli` >= 0.66.0.
+- `prune: <Number of blocks to retain>`: Sets a custom limit on the number of historical blocks to retain.
+- `prune: never`: No pruning of historical data; retains the entire history and is the default if there is no `indexerHints` section. `prune: never` should be selected if [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired.
+
+We can add `indexerHints` to our subgraphs by updating our `subgraph.yaml`:
+
+```yaml
+specVersion: 1.0.0
+schema:
+  file: ./schema.graphql
+indexerHints:
+  prune: auto
+dataSources:
+  - kind: ethereum/contract
+    name: Contract
+    network: mainnet
+```
+
+## Important Considerations
+
+- If [Time Travel Queries](/querying/graphql-api/#time-travel-queries) are desired as well as pruning, pruning must be performed accurately to retain Time Travel Query functionality. Due to this, it is generally not recommended to use `indexerHints: prune: auto` with Time Travel Queries. Instead, prune using `indexerHints: prune: <Number of blocks to retain>` to accurately prune to a block height that preserves the historical data required by Time Travel Queries, or use `prune: never` to maintain all data.
+
+- It is not possible to [graft](/cookbook/grafting/) at a block height that has been pruned. If grafting is routinely performed and pruning is desired, it is recommended to use `indexerHints: prune: <Number of blocks to retain>` that will accurately retain a set number of blocks (e.g., enough for six months).
+
+## Conclusion
+
+Pruning using `indexerHints` is a best practice for subgraph development, offering significant query performance improvements.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From fd71e47f416f3ee1a6fd8066328466d1792bf45c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:47 -0500
Subject: [PATCH 0578/1325] New translations grafting-hotfix.mdx (Turkish)

---
 website/pages/tr/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/tr/cookbook/grafting-hotfix.mdx b/website/pages/tr/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..187d4debd2c3 100644
--- a/website/pages/tr/cookbook/grafting-hotfix.mdx
+++ b/website/pages/tr/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Genel Bakış
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## Ek Kaynaklar
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From d174f6fa927a88db5b50f7735c8517ccea388c3a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:48 -0500
Subject: [PATCH 0579/1325] New translations grafting-hotfix.mdx (Ukrainian)

---
 website/pages/uk/cookbook/grafting-hotfix.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/uk/cookbook/grafting-hotfix.mdx b/website/pages/uk/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..040e3a8209d5 100644
--- a/website/pages/uk/cookbook/grafting-hotfix.mdx
+++ b/website/pages/uk/cookbook/grafting-hotfix.mdx
@@ -1,5 +1,5 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 29df15f41be37c94f9816e54aae589787a5069dd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:49 -0500
Subject: [PATCH 0580/1325] New translations grafting-hotfix.mdx (Chinese
 Simplified)

---
 website/pages/zh/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/zh/cookbook/grafting-hotfix.mdx b/website/pages/zh/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..1a9736aa17a2 100644
--- a/website/pages/zh/cookbook/grafting-hotfix.mdx
+++ b/website/pages/zh/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### 概述
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## 其他资源
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 321f7080a1491c9955a10beb435fc44a6ff23153 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:50 -0500
Subject: [PATCH 0581/1325] New translations grafting-hotfix.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/cookbook/grafting-hotfix.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/ur/cookbook/grafting-hotfix.mdx b/website/pages/ur/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..990a199cbfe0 100644
--- a/website/pages/ur/cookbook/grafting-hotfix.mdx
+++ b/website/pages/ur/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### جائزہ
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## اضافی وسائل
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7df010bb8ddcde1a57d713cbb257317f27b74e34 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:51 -0500
Subject: [PATCH 0582/1325] New translations grafting-hotfix.mdx (Vietnamese)

---
 website/pages/vi/cookbook/grafting-hotfix.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/vi/cookbook/grafting-hotfix.mdx b/website/pages/vi/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..4c5ab7d8929f 100644
--- a/website/pages/vi/cookbook/grafting-hotfix.mdx
+++ b/website/pages/vi/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### Tổng quan
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 857cf95e1f27363b78097bee76e9a7d92bd5bc3e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:53 -0500
Subject: [PATCH 0583/1325] New translations grafting-hotfix.mdx (Marathi)

---
 website/pages/mr/cookbook/grafting-hotfix.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/mr/cookbook/grafting-hotfix.mdx b/website/pages/mr/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..16ee51f808cd 100644
--- a/website/pages/mr/cookbook/grafting-hotfix.mdx
+++ b/website/pages/mr/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### सविश्लेषण
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 8ee8e768ed19bdecc28e2e5776162fd7352900d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:54 -0500
Subject: [PATCH 0584/1325] New translations grafting-hotfix.mdx (Hindi)

---
 website/pages/hi/cookbook/grafting-hotfix.mdx | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/hi/cookbook/grafting-hotfix.mdx b/website/pages/hi/cookbook/grafting-hotfix.mdx
index 4be0a0b07790..1c858096478b 100644
--- a/website/pages/hi/cookbook/grafting-hotfix.mdx
+++ b/website/pages/hi/cookbook/grafting-hotfix.mdx
@@ -1,12 +1,12 @@
 ---
-Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
 ---
 
 ## TLDR
 
 Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
 
-### Overview
+### अवलोकन
 
 This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
 
@@ -154,7 +154,7 @@ While grafting is a powerful tool for deploying hotfixes quickly, there are spec
 - **Data Integrity**: Incorrect block numbers can lead to data loss or duplication.
 - **Testing**: Always test grafting in a development environment before deploying to production.
 
-## Conclusion
+## निष्कर्ष
 
 Grafting is an effective strategy for deploying hotfixes in subgraph development, enabling you to:
 
@@ -164,7 +164,7 @@ Grafting is an effective strategy for deploying hotfixes in subgraph development
 
 However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
 
-## Additional Resources
+## अतिरिक्त संसाधन
 
 - **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
 - **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
@@ -173,14 +173,14 @@ By incorporating grafting into your subgraph development workflow, you can enhan
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 6b145947f8fd560f360059a5369c2e8d87b3339e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:55 -0500
Subject: [PATCH 0585/1325] New translations triggers-example.mdx (French)

---
 website/pages/fr/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/fr/sps/triggers-example.mdx b/website/pages/fr/sps/triggers-example.mdx
index d8d61566295e..2b4aaa27a8ca 100644
--- a/website/pages/fr/sps/triggers-example.mdx
+++ b/website/pages/fr/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Conditions préalables
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From e7cc3135b9e9a165956cd21670157b241b92d198 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:56 -0500
Subject: [PATCH 0586/1325] New translations triggers-example.mdx (Russian)

---
 website/pages/ru/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/ru/sps/triggers-example.mdx b/website/pages/ru/sps/triggers-example.mdx
index d8d61566295e..aa110f80d8f7 100644
--- a/website/pages/ru/sps/triggers-example.mdx
+++ b/website/pages/ru/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Предварительные требования
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 72dd6d2983d988ff8c5bdf79910766a64c5d478a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:57 -0500
Subject: [PATCH 0587/1325] New translations timeseries.mdx (Turkish)

---
 website/pages/tr/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/tr/cookbook/timeseries.mdx b/website/pages/tr/cookbook/timeseries.mdx
index 88ee70005a6e..f1135f5c4bcf 100644
--- a/website/pages/tr/cookbook/timeseries.mdx
+++ b/website/pages/tr/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Genel Bakış
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+Örnek:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+Örnek:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+Örnek:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+Örnek:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 7d634eb75c2e15c2b9605185481242a61148ba65 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:58 -0500
Subject: [PATCH 0588/1325] New translations timeseries.mdx (Ukrainian)

---
 website/pages/uk/cookbook/timeseries.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/uk/cookbook/timeseries.mdx b/website/pages/uk/cookbook/timeseries.mdx
index 88ee70005a6e..2ce0ce266ccf 100644
--- a/website/pages/uk/cookbook/timeseries.mdx
+++ b/website/pages/uk/cookbook/timeseries.mdx
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 575b2e8986441bbf1c321b1570363320b31db2ff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:41:59 -0500
Subject: [PATCH 0589/1325] New translations timeseries.mdx (Chinese
 Simplified)

---
 website/pages/zh/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/zh/cookbook/timeseries.mdx b/website/pages/zh/cookbook/timeseries.mdx
index 88ee70005a6e..b3072b4d102b 100644
--- a/website/pages/zh/cookbook/timeseries.mdx
+++ b/website/pages/zh/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## 概述
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+例子:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+例子:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+例子:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+例子:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 86d886ae8608d5c68891fed7743a87266569af5f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:00 -0500
Subject: [PATCH 0590/1325] New translations timeseries.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/ur/cookbook/timeseries.mdx b/website/pages/ur/cookbook/timeseries.mdx
index 88ee70005a6e..8d3b90fe98c2 100644
--- a/website/pages/ur/cookbook/timeseries.mdx
+++ b/website/pages/ur/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## جائزہ
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+مثال:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+مثال:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+مثال:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+مثال:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 2101f3fac7e3f6b39f9534b1fc861ab623811d19 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:01 -0500
Subject: [PATCH 0591/1325] New translations timeseries.mdx (Vietnamese)

---
 website/pages/vi/cookbook/timeseries.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/vi/cookbook/timeseries.mdx b/website/pages/vi/cookbook/timeseries.mdx
index 88ee70005a6e..9f371624ebf0 100644
--- a/website/pages/vi/cookbook/timeseries.mdx
+++ b/website/pages/vi/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## Tổng quan
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From ab46f1c2d67f49ac4a5e23c6de947a2657b63631 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:02 -0500
Subject: [PATCH 0592/1325] New translations timeseries.mdx (Marathi)

---
 website/pages/mr/cookbook/timeseries.mdx | 22 +++++++++++-----------
 1 file changed, 11 insertions(+), 11 deletions(-)

diff --git a/website/pages/mr/cookbook/timeseries.mdx b/website/pages/mr/cookbook/timeseries.mdx
index 88ee70005a6e..ab5b1b677d64 100644
--- a/website/pages/mr/cookbook/timeseries.mdx
+++ b/website/pages/mr/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## सविश्लेषण
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+उदाहरण:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+उदाहरण:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+उदाहरण:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+उदाहरण:
 
 ### Timeseries Entity
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From a76146f8b8864d1df874d96374ddd63957315bfc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:03 -0500
Subject: [PATCH 0593/1325] New translations timeseries.mdx (Hindi)

---
 website/pages/hi/cookbook/timeseries.mdx | 26 ++++++++++++------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/website/pages/hi/cookbook/timeseries.mdx b/website/pages/hi/cookbook/timeseries.mdx
index 88ee70005a6e..ab4f7619d180 100644
--- a/website/pages/hi/cookbook/timeseries.mdx
+++ b/website/pages/hi/cookbook/timeseries.mdx
@@ -6,7 +6,7 @@ title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggr
 
 Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
 
-## Overview
+## अवलोकन
 
 Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
 
@@ -27,7 +27,7 @@ Timeseries and aggregations reduce data processing overhead and accelerate queri
 - Immutable Data: All timeseries data is immutable, enabling efficient storage and retrieval.
 - Efficient Data Separation: Aggregates are stored separately from raw timeseries data, allowing queries to process significantly less data—often several orders of magnitude less.
 
-### Important Considerations
+### महत्वपूर्ण विचार
 
 - Immutable Data: Timeseries data cannot be altered once written, ensuring data integrity and simplifying indexing.
 - Automatic ID and Timestamp Management: id and timestamp fields are automatically managed by graph-node, reducing potential errors.
@@ -44,7 +44,7 @@ A timeseries entity represents raw data points collected over time. It is define
   - `id`: Must be of type `Int8!` and is auto-incremented.
   - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
 
-Example:
+उदाहरण:
 
 ```graphql
 type Data @entity(timeseries: true) {
@@ -61,7 +61,7 @@ An aggregation entity computes aggregated values from a timeseries source. It is
 - Annotation Arguments:
   - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
 
-Example:
+उदाहरण:
 
 ```graphql
 type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
@@ -77,7 +77,7 @@ In this example, Stats aggregates the price field from Data over hourly and dail
 
 Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
 
-Example:
+उदाहरण:
 
 ```graphql
 {
@@ -101,7 +101,7 @@ Example:
 
 Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
 
-Example:
+उदाहरण:
 
 ### Timeseries Entity
 
@@ -169,7 +169,7 @@ Supported operators and functions include basic arithmetic (+, -, \_, /), compar
 - Sorting: Results are automatically sorted by timestamp and id in descending order.
 - Current Data: An optional current argument can include the current, partially filled interval.
 
-### Conclusion
+### निष्कर्ष
 
 Implementing timeseries and aggregations in subgraphs is a best practice for projects dealing with time-based data. This approach:
 
@@ -181,14 +181,14 @@ By adopting this pattern, developers can build more efficient and scalable subgr
 
 ## Subgraph Best Practices 1-6
 
-1.  [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
 
-2.  [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
 
-3.  [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
 
-4.  [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
 
-5.  [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
 
-6.  [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From f3dcb34ca22e1d78f8a88770794831841672fa0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:04 -0500
Subject: [PATCH 0594/1325] New translations grafting-hotfix.mdx (Swahili)

---
 website/pages/sw/cookbook/grafting-hotfix.mdx | 186 ++++++++++++++++++
 1 file changed, 186 insertions(+)
 create mode 100644 website/pages/sw/cookbook/grafting-hotfix.mdx

diff --git a/website/pages/sw/cookbook/grafting-hotfix.mdx b/website/pages/sw/cookbook/grafting-hotfix.mdx
new file mode 100644
index 000000000000..040e3a8209d5
--- /dev/null
+++ b/website/pages/sw/cookbook/grafting-hotfix.mdx
@@ -0,0 +1,186 @@
+---
+title: Subgraph Best Practice 6 - Use Grafting for Quick Hotfix Deployment
+---
+
+## TLDR
+
+Grafting is a powerful feature in subgraph development that allows you to build and deploy new subgraphs while reusing the indexed data from existing ones.
+
+### Overview
+
+This feature enables quick deployment of hotfixes for critical issues, eliminating the need to re-index the entire subgraph from scratch. By preserving historical data, grafting minimizes downtime and ensures continuity in data services.
+
+## Benefits of Grafting for Hotfixes
+
+1. **Rapid Deployment**
+
+   - **Minimize Downtime**: When a subgraph encounters a critical error and stops indexing, grafting enables you to deploy a fix immediately without waiting for re-indexing.
+   - **Immediate Recovery**: The new subgraph continues from the last indexed block, ensuring that data services remain uninterrupted.
+
+2. **Data Preservation**
+
+   - **Reuse Historical Data**: Grafting copies the existing data from the base subgraph, so you don’t lose valuable historical records.
+   - **Consistency**: Maintains data continuity, which is crucial for applications relying on consistent historical data.
+
+3. **Efficiency**
+   - **Save Time and Resources**: Avoids the computational overhead of re-indexing large datasets.
+   - **Focus on Fixes**: Allows developers to concentrate on resolving issues rather than managing data recovery.
+
+## Best Practices When Using Grafting for Hotfixes
+
+1. **Initial Deployment Without Grafting**
+
+   - **Start Clean**: Always deploy your initial subgraph without grafting to ensure that it’s stable and functions as expected.
+   - **Test Thoroughly**: Validate the subgraph’s performance to minimize the need for future hotfixes.
+
+2. **Implementing the Hotfix with Grafting**
+
+   - **Identify the Issue**: When a critical error occurs, determine the block number of the last successfully indexed event.
+   - **Create a New Subgraph**: Develop a new subgraph that includes the hotfix.
+   - **Configure Grafting**: Use grafting to copy data up to the identified block number from the failed subgraph.
+   - **Deploy Quickly**: Publish the grafted subgraph to restore service as soon as possible.
+
+3. **Post-Hotfix Actions**
+
+   - **Monitor Performance**: Ensure the grafted subgraph is indexing correctly and the hotfix resolves the issue.
+   - **Republish Without Grafting**: Once stable, deploy a new version of the subgraph without grafting for long-term maintenance.
+     > Note: Relying on grafting indefinitely is not recommended as it can complicate future updates and maintenance.
+   - **Update References**: Redirect any services or applications to use the new, non-grafted subgraph.
+
+4. **Important Considerations**
+   - **Careful Block Selection**: Choose the graft block number carefully to prevent data loss.
+   - **Tip**: Use the block number of the last correctly processed event.
+   - **Use Deployment ID**: Ensure you reference the Deployment ID of the base subgraph, not the Subgraph ID.
+   - **Note**: The Deployment ID is the unique identifier for a specific subgraph deployment.
+   - **Feature Declaration**: Remember to declare grafting in the subgraph manifest under features.
+
+## Example: Deploying a Hotfix with Grafting
+
+Suppose you have a subgraph tracking a smart contract that has stopped indexing due to a critical error. Here’s how you can use grafting to deploy a hotfix.
+
+1. **Failed Subgraph Manifest (subgraph.yaml)**
+
+   ```yaml
+   specVersion: 1.0.0
+   schema:
+     file: ./schema.graphql
+   dataSources:
+     - kind: ethereum/contract
+       name: OldSmartContract
+       network: sepolia
+       source:
+         address: '0xOldContractAddress'
+         abi: Lock
+         startBlock: 5000000
+       mapping:
+         kind: ethereum/events
+         apiVersion: 0.0.7
+         language: wasm/assemblyscript
+         entities:
+           - Withdrawal
+         abis:
+           - name: Lock
+             file: ./abis/OldLock.json
+         eventHandlers:
+           - event: Withdrawal(uint256,uint256)
+             handler: handleOldWithdrawal
+         file: ./src/old-lock.ts
+   ```
+
+2. **New Grafted Subgraph Manifest (subgraph.yaml)**
+   ```yaml
+   specVersion: 1.0.0
+   schema:
+     file: ./schema.graphql
+   dataSources:
+     - kind: ethereum/contract
+       name: NewSmartContract
+       network: sepolia
+       source:
+         address: '0xNewContractAddress'
+         abi: Lock
+         startBlock: 6000001 # Block after the last indexed block
+       mapping:
+         kind: ethereum/events
+         apiVersion: 0.0.7
+         language: wasm/assemblyscript
+         entities:
+           - Withdrawal
+         abis:
+           - name: Lock
+             file: ./abis/Lock.json
+         eventHandlers:
+           - event: Withdrawal(uint256,uint256)
+             handler: handleWithdrawal
+         file: ./src/lock.ts
+   features:
+     - grafting
+   graft:
+     base: QmBaseDeploymentID # Deployment ID of the failed subgraph
+     block: 6000000 # Last successfully indexed block
+   ```
+
+**Explanation:**
+
+- **Data Source Update**: The new subgraph points to 0xNewContractAddress, which may be a fixed version of the smart contract.
+- **Start Block**: Set to one block after the last successfully indexed block to avoid reprocessing the error.
+- **Grafting Configuration**:
+  - **base**: Deployment ID of the failed subgraph.
+  - **block**: Block number where grafting should begin.
+
+3. **Deployment Steps**
+
+   - **Update the Code**: Implement the hotfix in your mapping scripts (e.g., handleWithdrawal).
+   - **Adjust the Manifest**: As shown above, update the `subgraph.yaml` with grafting configurations.
+   - **Deploy the Subgraph**:
+     - Authenticate with the Graph CLI.
+     - Deploy the new subgraph using `graph deploy`.
+
+4. **Post-Deployment**
+   - **Verify Indexing**: Check that the subgraph is indexing correctly from the graft point.
+   - **Monitor Data**: Ensure that new data is being captured and the hotfix is effective.
+   - **Plan for Republish**: Schedule the deployment of a non-grafted version for long-term stability.
+
+## Warnings and Cautions
+
+While grafting is a powerful tool for deploying hotfixes quickly, there are specific scenarios where it should be avoided to maintain data integrity and ensure optimal performance.
+
+- **Incompatible Schema Changes**: If your hotfix requires altering the type of existing fields or removing fields from your schema, grafting is not suitable. Grafting expects the new subgraph’s schema to be compatible with the base subgraph’s schema. Incompatible changes can lead to data inconsistencies and errors because the existing data won’t align with the new schema.
+- **Significant Mapping Logic Overhauls**: When the hotfix involves substantial modifications to your mapping logic—such as changing how events are processed or altering handler functions—grafting may not function correctly. The new logic might not be compatible with the data processed under the old logic, leading to incorrect data or failed indexing.
+- **Deployments to The Graph Network**: Grafting is not recommended for subgraphs intended for The Graph’s decentralized network (mainnet). It can complicate indexing and may not be fully supported by all Indexers, potentially causing unexpected behavior or increased costs. For mainnet deployments, it’s safer to re-index the subgraph from scratch to ensure full compatibility and reliability.
+
+### Risk Management
+
+- **Data Integrity**: Incorrect block numbers can lead to data loss or duplication.
+- **Testing**: Always test grafting in a development environment before deploying to production.
+
+## Conclusion
+
+Grafting is an effective strategy for deploying hotfixes in subgraph development, enabling you to:
+
+- **Quickly Recover** from critical errors without re-indexing.
+- **Preserve Historical Data**, maintaining continuity for applications and users.
+- **Ensure Service Availability** by minimizing downtime during critical fixes.
+
+However, it’s important to use grafting judiciously and follow best practices to mitigate risks. After stabilizing your subgraph with the hotfix, plan to deploy a non-grafted version to ensure long-term maintainability.
+
+## Additional Resources
+
+- **[Grafting Documentation](/cookbook/grafting/)**: Replace a Contract and Keep its History With Grafting
+- **[Understanding Deployment IDs](/querying/querying-by-subgraph-id-vs-deployment-id/)**: Learn the difference between Deployment ID and Subgraph ID.
+
+By incorporating grafting into your subgraph development workflow, you can enhance your ability to respond to issues swiftly, ensuring that your data services remain robust and reliable.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From 68ab43c887efdbbb184d7cfef5a2012a3ca0367d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:05 -0500
Subject: [PATCH 0595/1325] New translations timeseries.mdx (Swahili)

---
 website/pages/sw/cookbook/timeseries.mdx | 194 +++++++++++++++++++++++
 1 file changed, 194 insertions(+)
 create mode 100644 website/pages/sw/cookbook/timeseries.mdx

diff --git a/website/pages/sw/cookbook/timeseries.mdx b/website/pages/sw/cookbook/timeseries.mdx
new file mode 100644
index 000000000000..2ce0ce266ccf
--- /dev/null
+++ b/website/pages/sw/cookbook/timeseries.mdx
@@ -0,0 +1,194 @@
+---
+title: Subgraph Best Practice 5 - Simplify and Optimize with Timeseries and Aggregations
+---
+
+## TLDR
+
+Leveraging the new time-series and aggregations feature in subgraphs can significantly enhance both indexing speed and query performance.
+
+## Overview
+
+Timeseries and aggregations reduce data processing overhead and accelerate queries by offloading aggregation computations to the database and simplifying mapping code. This approach is particularly effective when handling large volumes of time-based data.
+
+## Benefits of Timeseries and Aggregations
+
+1. Improved Indexing Time
+
+- Less Data to Load: Mappings handle less data since raw data points are stored as immutable timeseries entities.
+- Database-Managed Aggregations: Aggregations are automatically computed by the database, reducing the workload on the mappings.
+
+2. Simplified Mapping Code
+
+- No Manual Calculations: Developers no longer need to write complex aggregation logic in mappings.
+- Reduced Complexity: Simplifies code maintenance and minimizes the potential for errors.
+
+3. Dramatically Faster Queries
+
+- Immutable Data: All timeseries data is immutable, enabling efficient storage and retrieval.
+- Efficient Data Separation: Aggregates are stored separately from raw timeseries data, allowing queries to process significantly less data—often several orders of magnitude less.
+
+### Important Considerations
+
+- Immutable Data: Timeseries data cannot be altered once written, ensuring data integrity and simplifying indexing.
+- Automatic ID and Timestamp Management: id and timestamp fields are automatically managed by graph-node, reducing potential errors.
+- Efficient Data Storage: By separating raw data from aggregates, storage is optimized, and queries run faster.
+
+## How to Implement Timeseries and Aggregations
+
+### Defining Timeseries Entities
+
+A timeseries entity represents raw data points collected over time. It is defined with the `@entity(timeseries: true)` annotation. Key requirements:
+
+- Immutable: Timeseries entities are always immutable.
+- Mandatory Fields:
+  - `id`: Must be of type `Int8!` and is auto-incremented.
+  - `timestamp`: Must be of type `Timestamp!` and is automatically set to the block timestamp.
+
+Example:
+
+```graphql
+type Data @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  price: BigDecimal!
+}
+```
+
+### Defining Aggregation Entities
+
+An aggregation entity computes aggregated values from a timeseries source. It is defined with the `@aggregation` annotation. Key components:
+
+- Annotation Arguments:
+  - `intervals`: Specifies time intervals (e.g., `["hour", "day"]`).
+
+Example:
+
+```graphql
+type Stats @aggregation(intervals: ["hour", "day"], source: "Data") {
+  id: Int8!
+  timestamp: Timestamp!
+  sum: BigDecimal! @aggregate(fn: "sum", arg: "price")
+}
+```
+
+In this example, Stats aggregates the price field from Data over hourly and daily intervals, computing the sum.
+
+### Querying Aggregated Data
+
+Aggregations are exposed via query fields that allow filtering and retrieval based on dimensions and time intervals.
+
+Example:
+
+```graphql
+{
+  tokenStats(
+    interval: "hour"
+    where: { token: "0x1234567890abcdef", timestamp_gte: "1704164640000000", timestamp_lt: "1704251040000000" }
+  ) {
+    id
+    timestamp
+    token {
+      id
+    }
+    totalVolume
+    priceUSD
+    count
+  }
+}
+```
+
+### Using Dimensions in Aggregations
+
+Dimensions are non-aggregated fields used to group data points. They enable aggregations based on specific criteria, such as a token in a financial application.
+
+Example:
+
+### Timeseries Entity
+
+```graphql
+type TokenData @entity(timeseries: true) {
+  id: Int8!
+  timestamp: Timestamp!
+  token: Token!
+  amount: BigDecimal!
+  priceUSD: BigDecimal!
+}
+```
+
+### Aggregation Entity with Dimension
+
+```graphql
+type TokenStats @aggregation(intervals: ["hour", "day"], source: "TokenData") {
+  id: Int8!
+  timestamp: Timestamp!
+  token: Token!
+  totalVolume: BigDecimal! @aggregate(fn: "sum", arg: "amount")
+  priceUSD: BigDecimal! @aggregate(fn: "last", arg: "priceUSD")
+  count: Int8! @aggregate(fn: "count", cumulative: true)
+}
+```
+
+- Dimension Field: token groups the data, so aggregates are computed per token.
+- Aggregates:
+  - totalVolume: Sum of amount.
+  - priceUSD: Last recorded priceUSD.
+  - count: Cumulative count of records.
+
+### Aggregation Functions and Expressions
+
+Supported aggregation functions:
+
+- sum
+- count
+- min
+- max
+- first
+- last
+
+### The arg in @aggregate can be
+
+- A field name from the timeseries entity.
+- An expression using fields and constants.
+
+### Examples of Aggregation Expressions
+
+- Sum Token Value: @aggregate(fn: "sum", arg: "priceUSD \_ amount")
+- Maximum Positive Amount: @aggregate(fn: "max", arg: "greatest(amount0, amount1, 0)")
+- Conditional Sum: @aggregate(fn: "sum", arg: "case when amount0 > amount1 then amount0 else 0 end")
+
+Supported operators and functions include basic arithmetic (+, -, \_, /), comparison operators, logical operators (and, or, not), and SQL functions like greatest, least, coalesce, etc.
+
+### Query Parameters
+
+- interval: Specifies the time interval (e.g., "hour").
+- where: Filters based on dimensions and timestamp ranges.
+- timestamp_gte / timestamp_lt: Filters for start and end times (microseconds since epoch).
+
+### Notes
+
+- Sorting: Results are automatically sorted by timestamp and id in descending order.
+- Current Data: An optional current argument can include the current, partially filled interval.
+
+### Conclusion
+
+Implementing timeseries and aggregations in subgraphs is a best practice for projects dealing with time-based data. This approach:
+
+- Enhances Performance: Speeds up indexing and querying by reducing data processing overhead.
+- Simplifies Development: Eliminates the need for manual aggregation logic in mappings.
+- Scales Efficiently: Handles large volumes of data without compromising on speed or responsiveness.
+
+By adopting this pattern, developers can build more efficient and scalable subgraphs, providing faster and more reliable data access to end-users. To learn more about implementing timeseries and aggregations, refer to the [Timeseries and Aggregations Readme](https://github.com/graphprotocol/graph-node/blob/master/docs/aggregations.md) and consider experimenting with this feature in your subgraphs.
+
+## Subgraph Best Practices 1-6
+
+1. [Improve Query Speed with Subgraph Pruning](/cookbook/pruning/)
+
+2. [Improve Indexing and Query Responsiveness by Using @derivedFrom](/cookbook/derivedfrom/)
+
+3. [Improve Indexing and Query Performance by Using Immutable Entities and Bytes as IDs](/cookbook/immutable-entities-bytes-as-ids/)
+
+4. [Improve Indexing Speed by Avoiding `eth_calls`](/cookbook/avoid-eth-calls/)
+
+5. [Simplify and Optimize with Timeseries and Aggregations](/cookbook/timeseries/)
+
+6. [Use Grafting for Quick Hotfix Deployment](/cookbook/grafting-hotfix/)

From cd65fe12908e736db17f2e4ce9773be8b0baa4f5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:18 -0500
Subject: [PATCH 0596/1325] New translations global.json (Swahili)

---
 website/pages/sw/global.json | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 website/pages/sw/global.json

diff --git a/website/pages/sw/global.json b/website/pages/sw/global.json
new file mode 100644
index 000000000000..6a3eb234bfce
--- /dev/null
+++ b/website/pages/sw/global.json
@@ -0,0 +1,14 @@
+{
+  "collapse": "Collapse",
+  "expand": "Expand",
+  "previous": "Previous",
+  "next": "Next",
+  "editPage": "Edit page",
+  "pageSections": "Page Sections",
+  "linkToThisSection": "Link to this section",
+  "technicalLevelRequired": "Technical Level Required",
+  "notFoundTitle": "Oops! This page was lost in space...",
+  "notFoundSubtitle": "Check if you’re using the right address or explore our website by clicking on the link below.",
+  "goHome": "Go Home",
+  "video": "Video"
+}

From 4c13a9995c02131055754ba39ce30f30368b9892 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:21 -0500
Subject: [PATCH 0597/1325] New translations grafting.mdx (Russian)

---
 website/pages/ru/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ru/cookbook/grafting.mdx b/website/pages/ru/cookbook/grafting.mdx
index ee58e2b51387..60ed4fa7211f 100644
--- a/website/pages/ru/cookbook/grafting.mdx
+++ b/website/pages/ru/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: Замените контракт и сохраните его истор
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-В этом руководстве мы рассмотрим базовый вариант использования. Мы заменим существующий договор на идентичный договор (с новым адресом, но тем же кодом). Затем привяжем существующий субграф к «базовому» субграфу, который отслеживает новый контракт.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Важное примечание о Grafting при обновлении до сети
 
@@ -30,7 +30,7 @@ title: Замените контракт и сохраните его истор
 
 ### Почему это важно?
 
-Grafting является мощной функцией, которая позволяет Вам «прививать» один субграф на другой, эффективно передавая исторические данные существующего субграфа на новую версию. Хотя это эффективный способ сохранения данных и экономии времени на индексации, Grafting может создавать сложности и потенциальные проблемы при миграции из хостинговой среды в децентрализованную сеть. Невозможно произвести перенос субграфа из сети The Graph Network обратно в хостинговый сервис или Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Лучшие практики
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - Источник данных `Lock` — это abi и адрес контракта, которые мы получим при компиляции и развертывании контракта
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - Раздел `mapping` определяет интересующие нас триггеры и функции, которые должны запускаться в ответ на эти триггеры. В этом случае мы уделяем внимание событию `Withdrawal` и вызываем функцию `handleWithdrawal` при его возникновении.
 
 ## Определение Манифеста Grafting
@@ -191,7 +191,7 @@ You can see that the `graft-replacement` subgraph is indexing from older `graph-
 
 ## Дополнительные ресурсы
 
-Если Вы хотите получить больше опыта в графтинге, вот несколько примеров популярных контрактов:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 44f611378b6931a1eea40ddab3e39e872b61bbba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:22 -0500
Subject: [PATCH 0598/1325] New translations subgraph-uncrashable.mdx (Russian)

---
 website/pages/ru/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ru/cookbook/subgraph-uncrashable.mdx b/website/pages/ru/cookbook/subgraph-uncrashable.mdx
index a0e5a6a967db..b6697e2ab778 100644
--- a/website/pages/ru/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/ru/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Генератор кода безопасного подграфа
 
 - Фреймворк также включает способ (через config-файл) создания пользовательских, но безопасных функций установки для групп переменных объектов. Таким образом, пользователь не сможет загрузить/использовать устаревшую graph entity, и также невозможно забыть о сохранении или установке переменной, которая требуется функцией.
 
-- Логи предупреждений записываются как записи, указывающие на нарушение логики подграфа, чтобы помочь устранить проблему и обеспечить точность данных. Эти отчеты можно просмотреть в хостинговой службе The Graph в разделе "Logs".
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable можно запустить как необязательный флаг с помощью команды Graph CLI codegen.
 

From 7c23cba972cb5ca99633779116ec7e38d87d6295 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:23 -0500
Subject: [PATCH 0599/1325] New translations benefits.mdx (Romanian)

---
 website/pages/ro/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/ro/network/benefits.mdx b/website/pages/ro/network/benefits.mdx
index be704e6e925f..b54165acd51b 100644
--- a/website/pages/ro/network/benefits.mdx
+++ b/website/pages/ro/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | Rețeaua The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| Infrastructure | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                        Rețeaua The Graph                        |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|        Infrastructure        |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | Rețeaua The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastructure | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                        Rețeaua The Graph                        |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|        Infrastructure        |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | Rețeaua The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastructure | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                        Rețeaua The Graph                        |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 4037643f4e2e553ec32031a33f46127b2e27452a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:24 -0500
Subject: [PATCH 0600/1325] New translations benefits.mdx (Spanish)

---
 website/pages/es/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/es/network/benefits.mdx b/website/pages/es/network/benefits.mdx
index f3740f62ffea..f1055e96a426 100644
--- a/website/pages/es/network/benefits.mdx
+++ b/website/pages/es/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Comparación de costos | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Costo mensual del servidor\* | $350 por mes | $0 |
-| Costos de consulta | $0+ | $0 per month |
-| Tiempo de ingeniería<sup>†</sup> | $400 por mes | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
-| Consultas por mes | Limitado a capacidades de infraestructura | 100,000 (Free Plan) |
-| Costo por consulta | $0 | $0<sup>‡</sup> |
-| Infraestructura | Centralizado | Descentralizado |
-| Redundancia geográfica | $750+ por nodo adicional | Incluido |
-| Tiempo de actividad | Varía | 99.9%+ |
-| Costos mensuales totales | <span className="highlight-row" />$750+ | $0 |
+|      Comparación de costos       |                Self Hosted                |                           The Graph Network                           |
+|:--------------------------------:|:-----------------------------------------:|:---------------------------------------------------------------------:|
+|  Costo mensual del servidor\*  |               $350 por mes                |                                  $0                                   |
+|        Costos de consulta        |                    $0+                    |                             $0 per month                              |
+| Tiempo de ingeniería<sup>†</sup> |               $400 por mes                | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
+|        Consultas por mes         | Limitado a capacidades de infraestructura |                          100,000 (Free Plan)                          |
+|        Costo por consulta        |                    $0                     |                            $0<sup>‡</sup>                             |
+|         Infraestructura          |               Centralizado                |                            Descentralizado                            |
+|      Redundancia geográfica      |         $750+ por nodo adicional          |                               Incluido                                |
+|       Tiempo de actividad        |                   Varía                   |                                99.9%+                                 |
+|     Costos mensuales totales     |  <span className="highlight-row" />$750+  |                                  $0                                   |
 
 ## Medium Volume User (~3M queries per month)
 
-| Comparación de costos | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Costo mensual del servidor\* | $350 por mes | $0 |
-| Costos de consulta | $500 por mes | $120 per month |
-| Tiempo de ingeniería<sup>†</sup> | $800 por mes | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
-| Consultas por mes | Limitado a capacidades de infraestructura | ~3,000,000 |
-| Costo por consulta | $0 | $0.00004 |
-| Infraestructura | Centralizado | Descentralizado |
-| Gastos de ingeniería | $200 por hora | Incluido |
-| Redundancia geográfica | $1,200 en costos totales por nodo adicional | Incluido |
-| Tiempo de actividad | Varía | 99.9%+ |
-| Costos mensuales totales | <span className="highlight-row" /> $1,650+ | $120 |
+|      Comparación de costos       |                 Self Hosted                 |                           The Graph Network                           |
+|:--------------------------------:|:-------------------------------------------:|:---------------------------------------------------------------------:|
+|  Costo mensual del servidor\*  |                $350 por mes                 |                                  $0                                   |
+|        Costos de consulta        |                $500 por mes                 |                            $120 per month                             |
+| Tiempo de ingeniería<sup>†</sup> |                $800 por mes                 | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
+|        Consultas por mes         |  Limitado a capacidades de infraestructura  |                              ~3,000,000                               |
+|        Costo por consulta        |                     $0                      |                               $0.00004                                |
+|         Infraestructura          |                Centralizado                 |                            Descentralizado                            |
+|       Gastos de ingeniería       |                $200 por hora                |                               Incluido                                |
+|      Redundancia geográfica      | $1,200 en costos totales por nodo adicional |                               Incluido                                |
+|       Tiempo de actividad        |                    Varía                    |                                99.9%+                                 |
+|     Costos mensuales totales     | <span className="highlight-row" /> $1,650+  |                                 $120                                  |
 
 ## High Volume User (~30M queries per month)
 
-| Comparación de costos | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Costo mensual del servidor\* | $1100 por mes, por nodo | $0 |
-| Costos de consulta | $4000 | $1,200 per month |
-| Número de nodos necesarios | 10 | No aplica |
-| Tiempo de ingeniería<sup>†</sup> | $6,000 o más por mes | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
-| Consultas por mes | Limitado a capacidades de infraestructura | ~30,000,000 |
-| Costo por consulta | $0 | $0.00004 |
-| Infraestructura | Centralizado | Descentralizado |
-| Redundancia geográfica | $1,200 en costos totales por nodo adicional | Incluido |
-| Tiempo de actividad | Varía | 99.9%+ |
-| Costos mensuales totales | <span className="highlight-row" /> $11,000+ | $1,200 |
+|      Comparación de costos       |                 Self Hosted                 |                           The Graph Network                           |
+|:--------------------------------:|:-------------------------------------------:|:---------------------------------------------------------------------:|
+|  Costo mensual del servidor\*  |           $1100 por mes, por nodo           |                                  $0                                   |
+|        Costos de consulta        |                    $4000                    |                           $1,200 per month                            |
+|    Número de nodos necesarios    |                     10                      |                               No aplica                               |
+| Tiempo de ingeniería<sup>†</sup> |            $6,000 o más por mes             | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
+|        Consultas por mes         |  Limitado a capacidades de infraestructura  |                              ~30,000,000                              |
+|        Costo por consulta        |                     $0                      |                               $0.00004                                |
+|         Infraestructura          |                Centralizado                 |                            Descentralizado                            |
+|      Redundancia geográfica      | $1,200 en costos totales por nodo adicional |                               Incluido                                |
+|       Tiempo de actividad        |                    Varía                    |                                99.9%+                                 |
+|     Costos mensuales totales     | <span className="highlight-row" /> $11,000+ |                                $1,200                                 |
 
 \*incluidos los costos de copia de seguridad: $50-$100 por mes
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 En conclusión: The Graph Network es menos costoso, más fácil de usar y produce resultados superiores en comparación con ejecutar un `graph-node` localmente.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From d08f9a572791338e428f87e7ef4bec44f9e9f607 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:25 -0500
Subject: [PATCH 0601/1325] New translations benefits.mdx (Arabic)

---
 website/pages/ar/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/ar/network/benefits.mdx b/website/pages/ar/network/benefits.mdx
index d4a42c2e21f9..510e4e20eb78 100644
--- a/website/pages/ar/network/benefits.mdx
+++ b/website/pages/ar/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| البنية الأساسية | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                        The Graph Network                        |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|       البنية الأساسية        |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| البنية الأساسية | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                        The Graph Network                        |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|       البنية الأساسية        |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| البنية الأساسية | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                        The Graph Network                        |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|       البنية الأساسية        |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From a5e6ee5b9a9a62352ec6901eb4836c363e04a67f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:27 -0500
Subject: [PATCH 0602/1325] New translations benefits.mdx (Czech)

---
 website/pages/cs/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/cs/network/benefits.mdx b/website/pages/cs/network/benefits.mdx
index 6f786e54adfe..971f4a21f7e8 100644
--- a/website/pages/cs/network/benefits.mdx
+++ b/website/pages/cs/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Srovnání nákladů | Vlastní hostitel | The Graph Network |
-| :-: | :-: | :-: |
-| Měsíční náklady na server\* | $350 měsíčně | $0 |
-| Náklady na dotazování | $0+ | $0 per month |
-| Inženýrský čas<sup>†</sup> | $400 měsíčně | Žádné, zabudované do sítě s globálně distribuovanými indexery |
-| Dotazy za měsíc | Omezeno na infra schopnosti | 100,000 (Free Plan) |
-| Náklady na jeden dotaz | $0 | $0<sup>‡</sup> |
-| Infrastruktura | Centralizovaný | Decentralizované |
-| Geografická redundancy | $750+ Usd za další uzel | Zahrnuto |
-| Provozuschopnost | Různé | 99.9%+ |
-| Celkové měsíční náklady | <span className="highlight-row" />$750+ | $0 |
+|       Srovnání nákladů        |            Vlastní hostitel             |                       The Graph Network                       |
+|:-----------------------------:|:---------------------------------------:|:-------------------------------------------------------------:|
+| Měsíční náklady na server\* |              $350 měsíčně               |                              $0                               |
+|     Náklady na dotazování     |                   $0+                   |                         $0 per month                          |
+|  Inženýrský čas<sup>†</sup>   |              $400 měsíčně               | Žádné, zabudované do sítě s globálně distribuovanými indexery |
+|        Dotazy za měsíc        |       Omezeno na infra schopnosti       |                      100,000 (Free Plan)                      |
+|    Náklady na jeden dotaz     |                   $0                    |                        $0<sup>‡</sup>                         |
+|        Infrastruktura         |             Centralizovaný              |                       Decentralizované                        |
+|    Geografická redundancy     |         $750+ Usd za další uzel         |                           Zahrnuto                            |
+|       Provozuschopnost        |                  Různé                  |                            99.9%+                             |
+|    Celkové měsíční náklady    | <span className="highlight-row" />$750+ |                              $0                               |
 
 ## Medium Volume User (~3M queries per month)
 
-| Srovnání nákladů | Vlastní hostitel | The Graph Network |
-| :-: | :-: | :-: |
-| Měsíční náklady na server\* | $350 měsíčně | $0 |
-| Náklady na dotazování | $500 měsíčně | $120 per month |
-| Inženýrský čas<sup>†</sup> | $800 měsíčně | Žádné, zabudované do sítě s globálně distribuovanými indexery |
-| Dotazy za měsíc | Omezeno na infra schopnosti | ~3,000,000 |
-| Náklady na jeden dotaz | $0 | $0.00004 |
-| Infrastruktura | Centralizovaný | Decentralizované |
-| Výdaje inženýrskou | $200 za hodinu | Zahrnuto |
-| Geografická redundancy | $1,200 celkových nákladů na další uzel | Zahrnuto |
-| Provozuschopnost | Různé | 99.9%+ |
-| Celkové měsíční náklady | <span className="highlight-row" /> $1,650+ | $120 |
+|       Srovnání nákladů        |              Vlastní hostitel              |                       The Graph Network                       |
+|:-----------------------------:|:------------------------------------------:|:-------------------------------------------------------------:|
+| Měsíční náklady na server\* |                $350 měsíčně                |                              $0                               |
+|     Náklady na dotazování     |                $500 měsíčně                |                        $120 per month                         |
+|  Inženýrský čas<sup>†</sup>   |                $800 měsíčně                | Žádné, zabudované do sítě s globálně distribuovanými indexery |
+|        Dotazy za měsíc        |        Omezeno na infra schopnosti         |                          ~3,000,000                           |
+|    Náklady na jeden dotaz     |                     $0                     |                           $0.00004                            |
+|        Infrastruktura         |               Centralizovaný               |                       Decentralizované                        |
+|      Výdaje inženýrskou       |               $200 za hodinu               |                           Zahrnuto                            |
+|    Geografická redundancy     |   $1,200 celkových nákladů na další uzel   |                           Zahrnuto                            |
+|       Provozuschopnost        |                   Různé                    |                            99.9%+                             |
+|    Celkové měsíční náklady    | <span className="highlight-row" /> $1,650+ |                             $120                              |
 
 ## High Volume User (~30M queries per month)
 
-| Srovnání nákladů | Vlastní hostitel | The Graph Network |
-| :-: | :-: | :-: |
-| Měsíční náklady na server\* | $1100 měsíčně za uzel | $0 |
-| Náklady na dotazování | $4000 | $1,200 per month |
-| Počet potřebných uzlů | 10 | Nepoužije se |
-| Inženýrský čas<sup>†</sup> | 6$, 000 nebo více měsíčně | Žádné, zabudované do sítě s globálně distribuovanými indexery |
-| Dotazy za měsíc | Omezeno na infra schopnosti | ~30,000,000 |
-| Náklady na jeden dotaz | $0 | $0.00004 |
-| Infrastruktura | Centralizovaný | Decentralizované |
-| Geografická redundancy | $1,200 celkových nákladů na další uzel | Zahrnuto |
-| Provozuschopnost | Různé | 99.9%+ |
-| Celkové měsíční náklady | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Srovnání nákladů        |              Vlastní hostitel               |                       The Graph Network                       |
+|:-----------------------------:|:-------------------------------------------:|:-------------------------------------------------------------:|
+| Měsíční náklady na server\* |            $1100 měsíčně za uzel            |                              $0                               |
+|     Náklady na dotazování     |                    $4000                    |                       $1,200 per month                        |
+|     Počet potřebných uzlů     |                     10                      |                         Nepoužije se                          |
+|  Inženýrský čas<sup>†</sup>   |          6$, 000 nebo více měsíčně          | Žádné, zabudované do sítě s globálně distribuovanými indexery |
+|        Dotazy za měsíc        |         Omezeno na infra schopnosti         |                          ~30,000,000                          |
+|    Náklady na jeden dotaz     |                     $0                      |                           $0.00004                            |
+|        Infrastruktura         |               Centralizovaný                |                       Decentralizované                        |
+|    Geografická redundancy     |   $1,200 celkových nákladů na další uzel    |                           Zahrnuto                            |
+|       Provozuschopnost        |                    Různé                    |                            99.9%+                             |
+|    Celkové měsíční náklady    | <span className="highlight-row" /> $11,000+ |                            $1,200                             |
 
 \*včetně nákladů na zálohování: $50-$100 měsíčně
 
@@ -89,4 +89,4 @@ Decentralizovaná síť Grafu poskytuje uživatelům přístup ke geografické r
 
 Podtrženo a sečteno: Síť Graf je levnější, jednodušší na používání a poskytuje lepší výsledky než lokální provozování `graph-node`.
 
-Začněte používat síť Graf ještě dnes a zjistěte, jak [upgradovat svůj podgraf do decentralizované sítě Grafu](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 6fe789f3782802105942a89a2bc67ff257ad11df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:28 -0500
Subject: [PATCH 0603/1325] New translations benefits.mdx (German)

---
 website/pages/de/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/de/network/benefits.mdx b/website/pages/de/network/benefits.mdx
index e80dd34993af..35f0df7781e1 100644
--- a/website/pages/de/network/benefits.mdx
+++ b/website/pages/de/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| Infrastruktur | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                        The Graph Network                        |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|        Infrastruktur         |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastruktur | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                        The Graph Network                        |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|        Infrastruktur         |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastruktur | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                        The Graph Network                        |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|        Infrastruktur         |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 4413d3aa6254fce4cd9800c66eeb20f5b4d4a8db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:29 -0500
Subject: [PATCH 0604/1325] New translations benefits.mdx (Italian)

---
 website/pages/it/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/it/network/benefits.mdx b/website/pages/it/network/benefits.mdx
index f0542f2b5731..304e99031863 100644
--- a/website/pages/it/network/benefits.mdx
+++ b/website/pages/it/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Confronto costi | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Costo mensile del server\* | $350 al mese | $0 |
-| Costi di query | $0+ | $0 per month |
-| Tempo di progettazione<sup>†</sup> | $400 al mese | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
-| Query al mese | Limitato alle capacità di infra | 100,000 (Free Plan) |
-| Costo per query | $0 | $0<sup>‡</sup> |
-| Infrastruttura | Centralizzato | Decentralizzato |
-| Ridondanza geografica | $750+ per nodo aggiuntivo | Incluso |
-| Tempo di attività | Variabile | 99.9%+ |
-| Costo totale mensile | <span className="highlight-row" />$750+ | $0 |
+|          Confronto costi           |               Self Hosted               |                               The Graph Network                               |
+|:----------------------------------:|:---------------------------------------:|:-----------------------------------------------------------------------------:|
+|    Costo mensile del server\*    |              $350 al mese               |                                      $0                                       |
+|           Costi di query           |                   $0+                   |                                 $0 per month                                  |
+| Tempo di progettazione<sup>†</sup> |              $400 al mese               | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
+|           Query al mese            |     Limitato alle capacità di infra     |                              100,000 (Free Plan)                              |
+|          Costo per query           |                   $0                    |                                $0<sup>‡</sup>                                 |
+|           Infrastruttura           |              Centralizzato              |                                Decentralizzato                                |
+|       Ridondanza geografica        |        $750+ per nodo aggiuntivo        |                                    Incluso                                    |
+|         Tempo di attività          |                Variabile                |                                    99.9%+                                     |
+|        Costo totale mensile        | <span className="highlight-row" />$750+ |                                      $0                                       |
 
 ## Medium Volume User (~3M queries per month)
 
-| Confronto dei costi | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Costo mensile del server\* | $350 al mese | $0 |
-| Costi di query | $500 al mese | $120 per month |
-| Tempo di progettazione<sup>†</sup> | $800 al mese | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
-| Query al mese | Limitato alle capacità dell'infrastruttura | ~3,000,000 |
-| Costo per query | $0 | $0.00004 |
-| Infrastruttura | Centralizzato | Decentralizzato |
-| Costi di ingegneria | $200 all'ora | Incluso |
-| Ridondanza geografica | $1.200 di costi totali per nodo aggiuntivo | Incluso |
-| Tempo di attività | Variabile | 99.9%+ |
-| Costo totale mensile | <span className="highlight-row" /> $1,650+ | $120 |
+|        Confronto dei costi         |                Self Hosted                 |                               The Graph Network                               |
+|:----------------------------------:|:------------------------------------------:|:-----------------------------------------------------------------------------:|
+|    Costo mensile del server\*    |                $350 al mese                |                                      $0                                       |
+|           Costi di query           |                $500 al mese                |                                $120 per month                                 |
+| Tempo di progettazione<sup>†</sup> |                $800 al mese                | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
+|           Query al mese            | Limitato alle capacità dell'infrastruttura |                                  ~3,000,000                                   |
+|          Costo per query           |                     $0                     |                                   $0.00004                                    |
+|           Infrastruttura           |               Centralizzato                |                                Decentralizzato                                |
+|        Costi di ingegneria         |                $200 all'ora                |                                    Incluso                                    |
+|       Ridondanza geografica        | $1.200 di costi totali per nodo aggiuntivo |                                    Incluso                                    |
+|         Tempo di attività          |                 Variabile                  |                                    99.9%+                                     |
+|        Costo totale mensile        | <span className="highlight-row" /> $1,650+ |                                     $120                                      |
 
 ## High Volume User (~30M queries per month)
 
-| Confronto costi | Self Hosted | The Graph Network |
-| :-: | :-: | :-: |
-| Costo mensile del server\* | $1100 al mese, per nodo | $0 |
-| Costi di query | $4000 | $1,200 per month |
-| Numero di nodi necessari | 10 | Non applicabile |
-| Tempo di progettazione<sup>†</sup> | $6.000 o più al mese | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
-| Query al mese | Limitato alle capacità di infra | ~30,000,000 |
-| Costo per query | $0 | $0.00004 |
-| Infrastruttura | Centralizzato | Decentralizzato |
-| Ridondanza geografica | $1.200 di costi totali per nodo aggiuntivo | Incluso |
-| Tempo di attività | Variabile | 99.9%+ |
-| Costo totale mensile | <span className="highlight-row" /> $11,000+ | $1,200 |
+|          Confronto costi           |                 Self Hosted                 |                               The Graph Network                               |
+|:----------------------------------:|:-------------------------------------------:|:-----------------------------------------------------------------------------:|
+|    Costo mensile del server\*    |           $1100 al mese, per nodo           |                                      $0                                       |
+|           Costi di query           |                    $4000                    |                               $1,200 per month                                |
+|      Numero di nodi necessari      |                     10                      |                                Non applicabile                                |
+| Tempo di progettazione<sup>†</sup> |            $6.000 o più al mese             | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
+|           Query al mese            |       Limitato alle capacità di infra       |                                  ~30,000,000                                  |
+|          Costo per query           |                     $0                      |                                   $0.00004                                    |
+|           Infrastruttura           |                Centralizzato                |                                Decentralizzato                                |
+|       Ridondanza geografica        | $1.200 di costi totali per nodo aggiuntivo  |                                    Incluso                                    |
+|         Tempo di attività          |                  Variabile                  |                                    99.9%+                                     |
+|        Costo totale mensile        | <span className="highlight-row" /> $11,000+ |                                    $1,200                                     |
 
 \*inclusi i costi per il backup: $50-$100 al mese
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 In conclusione: The Graph Network è meno costosa, più facile da usare e produce risultati superiori rispetto alla gestione locale di `graph-node`.
 
-Iniziate a usare The Graph Network oggi e scoprite come [aggiornare il vostro subgraph alla rete decentralizzata di The Graph](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 314193f5232fe17046448cd83ea16fa149eff376 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:30 -0500
Subject: [PATCH 0605/1325] New translations benefits.mdx (Japanese)

---
 website/pages/ja/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/ja/network/benefits.mdx b/website/pages/ja/network/benefits.mdx
index 29663f61afb4..7869ee86e955 100644
--- a/website/pages/ja/network/benefits.mdx
+++ b/website/pages/ja/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| コスト比較 | セルフホスト | グラフネットワーク |
-| :-: | :-: | :-: |
-| 月額サーバー代 | $350/月 | $0 |
-| クエリコスト | $0+ | $0 per month |
-| エンジニアリングタイム<sup>†</sup> | $400/月 | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
-| 月ごとのクエリ | インフラ機能に限定 | 100,000 (Free Plan) |
-| クエリごとのコスト | $0 | $0<sup>‡</sup> |
-| インフラストラクチャ | 集中管理型 | 分散型 |
-| 地理的な冗長性 | 追加1ノードにつき$750+ | 含まれる |
-| アップタイム | バリエーション | 99.9%+ |
-| 月額費用合計 | <span className="highlight-row" />$750+ | $0 |
+|          コスト比較          |                 セルフホスト                  |              グラフネットワーク              |
+|:-----------------------:|:---------------------------------------:|:-----------------------------------:|
+|         月額サーバー代         |                 $350/月                  |                 $0                  |
+|         クエリコスト          |                   $0+                   |            $0 per month             |
+| エンジニアリングタイム<sup>†</sup> |                 $400/月                  | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
+|         月ごとのクエリ         |                インフラ機能に限定                |         100,000 (Free Plan)         |
+|        クエリごとのコスト        |                   $0                    |           $0<sup>‡</sup>            |
+|       インフラストラクチャ        |                  集中管理型                  |                 分散型                 |
+|         地理的な冗長性         |             追加1ノードにつき$750+              |                含まれる                 |
+|         アップタイム          |                 バリエーション                 |               99.9%+                |
+|         月額費用合計          | <span className="highlight-row" />$750+ |                 $0                  |
 
 ## Medium Volume User (~3M queries per month)
 
-| コスト比較 | セルフホスト | グラフネットワーク |
-| :-: | :-: | :-: |
-| 月額サーバー代 | $350/月 | $0 |
-| クエリコスト | $500/月 | $120 per month |
-| エンジニアリングタイム<sup>†</sup> | $800/月 | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
-| 月ごとのクエリ | インフラ機能に限定 | ~3,000,000 |
-| クエリごとのコスト | $0 | $0.00004 |
-| インフラストラクチャ | 中央管理型 | 分散型 |
-| エンジニアリングコスト | $200/時 | 含まれる |
-| 地理的な冗長性 | ノード追加1台につき合計1,200ドル | 含まれる |
-| アップタイム | 変動 | 99.9%+ |
-| 月額費用合計 | <span className="highlight-row" /> $1,650+ | $120 |
+|          コスト比較          |                   セルフホスト                   |              グラフネットワーク              |
+|:-----------------------:|:------------------------------------------:|:-----------------------------------:|
+|         月額サーバー代         |                   $350/月                   |                 $0                  |
+|         クエリコスト          |                   $500/月                   |           $120 per month            |
+| エンジニアリングタイム<sup>†</sup> |                   $800/月                   | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
+|         月ごとのクエリ         |                 インフラ機能に限定                  |             ~3,000,000              |
+|        クエリごとのコスト        |                     $0                     |              $0.00004               |
+|       インフラストラクチャ        |                   中央管理型                    |                 分散型                 |
+|       エンジニアリングコスト       |                   $200/時                   |                含まれる                 |
+|         地理的な冗長性         |            ノード追加1台につき合計1,200ドル             |                含まれる                 |
+|         アップタイム          |                     変動                     |               99.9%+                |
+|         月額費用合計          | <span className="highlight-row" /> $1,650+ |                $120                 |
 
 ## High Volume User (~30M queries per month)
 
-| コスト比較 | セルフホスト | グラフネットワーク |
-| :-: | :-: | :-: |
-| 月額サーバー代 | $1100/月（ノードごと） | $0 |
-| クエリコスト | $4000 | $1,200 per month |
-| 必要ノード数 | 10 | 該当なし |
-| エンジニアリングタイム<sup>†</sup> | $6,000/月 | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
-| 月ごとのクエリ | インフラ機能に限定 | ~30,000,000 |
-| クエリごとのコスト | $0 | $0.00004 |
-| インフラストラクチャ | 集中管理型 | 分散型 |
-| 地理的な冗長性 | ノード追加1台につき合計1,200ドル | 含まれる |
-| アップタイム | 変動 | 99.9%+ |
-| 月額費用合計 | <span className="highlight-row" /> $11,000+ | $1,200 |
+|          コスト比較          |                   セルフホスト                    |              グラフネットワーク              |
+|:-----------------------:|:-------------------------------------------:|:-----------------------------------:|
+|         月額サーバー代         |               $1100/月（ノードごと）                |                 $0                  |
+|         クエリコスト          |                    $4000                    |          $1,200 per month           |
+|         必要ノード数          |                     10                      |                該当なし                 |
+| エンジニアリングタイム<sup>†</sup> |                  $6,000/月                   | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
+|         月ごとのクエリ         |                  インフラ機能に限定                  |             ~30,000,000             |
+|        クエリごとのコスト        |                     $0                      |              $0.00004               |
+|       インフラストラクチャ        |                    集中管理型                    |                 分散型                 |
+|         地理的な冗長性         |             ノード追加1台につき合計1,200ドル             |                含まれる                 |
+|         アップタイム          |                     変動                      |               99.9%+                |
+|         月額費用合計          | <span className="highlight-row" /> $11,000+ |               $1,200                |
 
 \*バックアップ費用含む：月額$50〜$100
 
@@ -89,4 +89,4 @@ Graphの分散型ネットワークは、`graph-node`をセルフホストする
 
 結論: グラフ ネットワークは、ローカルで `graph-node` を実行するよりも安価で使いやすく、優れた結果を生み出します。
 
-今すぐ The Graph Network の使用を開始し、[サブグラフを The Graph の分散ネットワークにアップグレードする](/cookbook/upgrading-a-subgraph)方法を学びましょう。
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 2895a3e610ed278429e89a9017c1edd729d8a28c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:31 -0500
Subject: [PATCH 0606/1325] New translations benefits.mdx (Korean)

---
 website/pages/ko/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/ko/network/benefits.mdx b/website/pages/ko/network/benefits.mdx
index 6be4e830e565..4fd17e17727d 100644
--- a/website/pages/ko/network/benefits.mdx
+++ b/website/pages/ko/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | The Graph 네트워크 |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| Infrastructure | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                         The Graph 네트워크                          |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|        Infrastructure        |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | The Graph 네트워크 |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastructure | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                         The Graph 네트워크                          |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|        Infrastructure        |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | The Graph 네트워크 |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastructure | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                         The Graph 네트워크                          |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 889c942ee85a6ed6ce5a6abd099cb611f278069c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:32 -0500
Subject: [PATCH 0607/1325] New translations benefits.mdx (Dutch)

---
 website/pages/nl/network/benefits.mdx | 74 +++++++++++++--------------
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/website/pages/nl/network/benefits.mdx b/website/pages/nl/network/benefits.mdx
index b41bc69c223e..85fb9bde66ce 100644
--- a/website/pages/nl/network/benefits.mdx
+++ b/website/pages/nl/network/benefits.mdx
@@ -5,7 +5,7 @@ socialImage: https://thegraph.com/docs/img/seo/benefits.jpg
 
 Het gedecentraliseerde netwerk van The Graph is ontworpen en verfijnd om een robuuste ervaring te creëren bij het indexeren en opvragen van data. Het netwerk wordt iedere dag sterker door de duizenden bijdragers wereldwijd.
 
-De voordelen van dit gedecentraliseerde protocol is dat het niet gerepliceerd kan worden door een `graph-node` lokaal te laten werken. Het Graph Netwerk is betrouwbaarder, efficiënter en goedkoper.
+De voordelen van dit gedecentraliseerde protocol is dat het niet gerepliceerd kan worden door een  `graph-node` lokaal te laten werken. Het Graph Netwerk is betrouwbaarder, efficiënter en goedkoper.
 
 Hier is een analyse:
 
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Kostenvergelijking | Zelf hosten | De Graph Netwerk |
-| :-: | :-: | :-: |
-| Maandelijkse serverkosten | $350 per maand | $0 |
-| Querykosten | $0+ | $0 per month |
-| Onderhoud tijd<sup>†</sup> | $400 per maand | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
-| Aantal queries per maand | Beperkt tot infrastructuurcapaciteiten | 100,000 (Free Plan) |
-| Kosten per query | $0 | $0<sup>‡</sup> |
-| Infrastructuur | Gecentraliseerd | Gedecentraliseerd |
-| Geografische redundantie | $750+ per extra node | Inbegrepen |
-| Uptime | Wisselend | 99,9%+ |
-| Totale maandelijkse kosten | <span className="highlight-row" />$750+ | $0 |
+|     Kostenvergelijking     |               Zelf hosten               |                                         De Graph Netwerk                                         |
+|:--------------------------:|:---------------------------------------:|:------------------------------------------------------------------------------------------------:|
+| Maandelijkse serverkosten  |             $350 per maand              |                                                $0                                                |
+|        Querykosten         |                   $0+                   |                                           $0 per month                                           |
+| Onderhoud tijd<sup>†</sup> |             $400 per maand              | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
+|  Aantal queries per maand  | Beperkt tot infrastructuurcapaciteiten  |                                       100,000 (Free Plan)                                        |
+|      Kosten per query      |                   $0                    |                                          $0<sup>‡</sup>                                          |
+|       Infrastructuur       |             Gecentraliseerd             |                                        Gedecentraliseerd                                         |
+|  Geografische redundantie  |          $750+ per extra node           |                                            Inbegrepen                                            |
+|           Uptime           |                Wisselend                |                                              99,9%+                                              |
+| Totale maandelijkse kosten | <span className="highlight-row" />$750+ |                                                $0                                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Kostenvergelijking | Zelf hosten | De Graph Netwerk |
-| :-: | :-: | :-: |
-| Maandelijkse serverkosten | $350 per maand | $0 |
-| Querykosten | $500 per maand | $120 per month |
-| Onderhoud<sup>†</sup> | $800 per maand | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
-| Aantal queries per maand | Beperkt tot infrastructuurcapaciteiten | ~3,000,000 |
-| Kosten per query | $0 | $0.00004 |
-| Infrastructuur | Gecentraliseerd | Gedecentraliseerd |
-| Technische personeelskosten | $200 per uur | Inbegrepen |
-| Geografische redundantie | $1200 totale kosten per extra node | Inbegrepen |
-| Uptime | Wisselend | 99,9%+ |
-| Totale maandelijkse kosten | <span className="highlight-row" /> $1650+ | $120 |
+|     Kostenvergelijking      |                Zelf hosten                |                                         De Graph Netwerk                                         |
+|:---------------------------:|:-----------------------------------------:|:------------------------------------------------------------------------------------------------:|
+|  Maandelijkse serverkosten  |              $350 per maand               |                                                $0                                                |
+|         Querykosten         |              $500 per maand               |                                          $120 per month                                          |
+|    Onderhoud<sup>†</sup>    |              $800 per maand               | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
+|  Aantal queries per maand   |  Beperkt tot infrastructuurcapaciteiten   |                                            ~3,000,000                                            |
+|      Kosten per query       |                    $0                     |                                             $0.00004                                             |
+|       Infrastructuur        |              Gecentraliseerd              |                                        Gedecentraliseerd                                         |
+| Technische personeelskosten |               $200 per uur                |                                            Inbegrepen                                            |
+|  Geografische redundantie   |    $1200 totale kosten per extra node     |                                            Inbegrepen                                            |
+|           Uptime            |                 Wisselend                 |                                              99,9%+                                              |
+| Totale maandelijkse kosten  | <span className="highlight-row" /> $1650+ |                                               $120                                               |
 
 ## High Volume User (~30M queries per month)
 
-| Kostenvergelijking | Zelf hosten | De Graph Netwerk |
-| :-: | :-: | :-: |
-| Maandelijkse serverkosten | $1100 per maand, per node | $0 |
-| Querykosten | $4000 | $1,200 per month |
-| Aantal benodigde nodes | 10 | Niet van toepassing |
-| Onderhoud<sup>†</sup> | $6000 of meer per maand | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
-| Aantal queries per maand | Beperkt tot infrastructuurcapaciteiten | ~30,000,000 |
-| Kosten per query | $0 | $0.00004 |
-| Infrastructuur | Gecentraliseerd | Gedecentraliseerd |
-| Geografische redundantie | $1200 in totale kosten per extra node | Inbegrepen |
-| Uptime | Wisselend | 99,9%+ |
-| Totale maandelijkse kosten | <span className="highlight-row" /> $11000+ | $1,200 |
+|     Kostenvergelijking     |                Zelf hosten                 |                                         De Graph Netwerk                                         |
+|:--------------------------:|:------------------------------------------:|:------------------------------------------------------------------------------------------------:|
+| Maandelijkse serverkosten  |         $1100 per maand, per node          |                                                $0                                                |
+|        Querykosten         |                   $4000                    |                                         $1,200 per month                                         |
+|   Aantal benodigde nodes   |                     10                     |                                       Niet van toepassing                                        |
+|   Onderhoud<sup>†</sup>    |          $6000 of meer per maand           | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
+|  Aantal queries per maand  |   Beperkt tot infrastructuurcapaciteiten   |                                           ~30,000,000                                            |
+|      Kosten per query      |                     $0                     |                                             $0.00004                                             |
+|       Infrastructuur       |              Gecentraliseerd               |                                        Gedecentraliseerd                                         |
+|  Geografische redundantie  |   $1200 in totale kosten per extra node    |                                            Inbegrepen                                            |
+|           Uptime           |                 Wisselend                  |                                              99,9%+                                              |
+| Totale maandelijkse kosten | <span className="highlight-row" /> $11000+ |                                              $1,200                                              |
 
 \*inclusief kosten voor een back-up: $50-$100 per maand
 
@@ -89,4 +89,4 @@ Het gedecentraliseerde netwerk van The Graph biedt gebruikers toegang tot geogra
 
 Samenvattend: Het Graph Network is goedkoper, gemakkelijker te gebruiken en levert superieure resultaten in vergelijking met het lokaal hosten van een `graph-node`.
 
-Begin vandaag nog met het gebruik van The Graph Network en leer hoe je je subgraph kunt [upgraden naar het gedecentraliseerde netwerk van The Graph](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 39202573ab0c2d0269f3e4151e43b2f4957365b6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:33 -0500
Subject: [PATCH 0608/1325] New translations benefits.mdx (Polish)

---
 website/pages/pl/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/pl/network/benefits.mdx b/website/pages/pl/network/benefits.mdx
index 0167c34f3a67..2ff74600cf86 100644
--- a/website/pages/pl/network/benefits.mdx
+++ b/website/pages/pl/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | Sieć The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| Infrastructure | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                         Sieć The Graph                          |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|        Infrastructure        |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | Sieć The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastructure | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                         Sieć The Graph                          |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|        Infrastructure        |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | Sieć The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Infrastructure | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                         Sieć The Graph                          |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From ab1fa743272bafe74129dec5ed9d2515307b99de Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:34 -0500
Subject: [PATCH 0609/1325] New translations benefits.mdx (Portuguese)

---
 website/pages/pt/network/benefits.mdx | 75 +++++++++++++--------------
 1 file changed, 37 insertions(+), 38 deletions(-)

diff --git a/website/pages/pt/network/benefits.mdx b/website/pages/pt/network/benefits.mdx
index a806ae77758e..081aef23ec08 100644
--- a/website/pages/pt/network/benefits.mdx
+++ b/website/pages/pt/network/benefits.mdx
@@ -27,54 +27,53 @@ Os custos de query podem variar; o custo citado é o normal até o fechamento da
 
 ## Utilizador de Baixo Volume (menos de 100 mil queries por mês)
 
-| Comparação de Custos | Auto-hospedagem | The Graph Network |
-| :-: | :-: | :-: |
-| Custo mensal de servidor\* | $350 por mês | $0 |
-| Custos de query | $0+ | $0 por mês |
-| Tempo de engenharia<sup>†</sup> | $400 por mês | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
-| Queries por mês | Limitadas pelas capabilidades da infra | 100 mil (Plano Grátis) |
-| Custo por query | $0 | $0<sup>‡</sup> |
-| Infraestrutura | Centralizada | Descentralizada |
-| Redundância geográfica | $750+ por node adicional | Incluída |
-| Uptime (disponibilidade) | Varia | 99.9%+ |
-| Custos mensais totais | <span className="highlight-row" />$750+ | $0 |
+|      Comparação de Custos       |             Auto-hospedagem             |                         The Graph Network                         |
+|:-------------------------------:|:---------------------------------------:|:-----------------------------------------------------------------:|
+|  Custo mensal de servidor\*   |              $350 por mês               |                                $0                                 |
+|         Custos de query         |                   $0+                   |                            $0 por mês                             |
+| Tempo de engenharia<sup>†</sup> |              $400 por mês               | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
+|         Queries por mês         | Limitadas pelas capabilidades da infra  |                      100 mil (Plano Grátis)                       |
+|         Custo por query         |                   $0                    |                          $0<sup>‡</sup>                           |
+|         Infraestrutura          |              Centralizada               |                          Descentralizada                          |
+|     Redundância geográfica      |        $750+ por node adicional         |                             Incluída                              |
+|    Uptime (disponibilidade)     |                  Varia                  |                              99.9%+                               |
+|      Custos mensais totais      | <span className="highlight-row" />$750+ |                                $0                                 |
 
 ## Utilizador de Volume Médio (cerca de 3 milhões de queries por mês)
 
-| Comparação de Custos | Auto-hospedagem | The Graph Network |
-| :-: | :-: | :-: |
-| Custo mensal de servidor\* | $350 por mês | $0 |
-| Custos de query | $500 por mês | $120 por mês |
-| Tempo de engenharia<sup>†</sup> | $800 por mês | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
-| Queries por mês | Limitadas pelas capabilidades da infra | ~3 milhões |
-| Custo por query | $0 | $0.00004 |
-| Infraestrutura | Centralizada | Descentralizada |
-| Custo de engenharia | $200 por hora | Incluído |
-| Redundância geográfica | $1.200 em custos totais por node adicional | Incluída |
-| Uptime (disponibilidade) | Varia | 99.9%+ |
-| Custos mensais totais | <span className="highlight-row" /> $1.650+ | $120 |
+|      Comparação de Custos       |              Auto-hospedagem               |                         The Graph Network                         |
+|:-------------------------------:|:------------------------------------------:|:-----------------------------------------------------------------:|
+|  Custo mensal de servidor\*   |                $350 por mês                |                                $0                                 |
+|         Custos de query         |                $500 por mês                |                           $120 por mês                            |
+| Tempo de engenharia<sup>†</sup> |                $800 por mês                | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
+|         Queries por mês         |   Limitadas pelas capabilidades da infra   |                            ~3 milhões                             |
+|         Custo por query         |                     $0                     |                             $0.00004                              |
+|         Infraestrutura          |                Centralizada                |                          Descentralizada                          |
+|       Custo de engenharia       |               $200 por hora                |                             Incluído                              |
+|     Redundância geográfica      | $1.200 em custos totais por node adicional |                             Incluída                              |
+|    Uptime (disponibilidade)     |                   Varia                    |                              99.9%+                               |
+|      Custos mensais totais      | <span className="highlight-row" /> $1.650+ |                               $120                                |
 
 ## Utilizador de Volume Alto (cerca de 30 milhões de queries por mês)
 
-| Comparação de Custos | Auto-hospedagem | The Graph Network |
-| :-: | :-: | :-: |
-| Custo mensal de servidor\* | $1.100 por mês, por node | $0 |
-| Custos de query | $4.000 | $1,200 por mês |
-| Número de nodes necessário | 10 | Não se aplica |
-| Tempo de engenharia<sup>†</sup> | $6.000 ou mais por mês | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
-| Queries por mês | Limitadas pelas capabilidades da infra | Cerca de 30 milhões |
-| Custo por query | $0 | $0.00004 |
-| Infraestrutura | Centralizada | Descentralizada |
-| Redundância geográfica | $1.200 em custos totais por node adicional | Incluída |
-| Uptime (disponibilidade) | Varia | 99.9%+ |
-| Custos mensais totais | <span className="highlight-row" /> $11.000+ | $1.200 |
+|      Comparação de Custos       |               Auto-hospedagem               |                         The Graph Network                         |
+|:-------------------------------:|:-------------------------------------------:|:-----------------------------------------------------------------:|
+|  Custo mensal de servidor\*   |          $1.100 por mês, por node           |                                $0                                 |
+|         Custos de query         |                   $4.000                    |                          $1,200 por mês                           |
+|   Número de nodes necessário    |                     10                      |                           Não se aplica                           |
+| Tempo de engenharia<sup>†</sup> |           $6.000 ou mais por mês            | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
+|         Queries por mês         |   Limitadas pelas capabilidades da infra    |                        Cerca de 30 milhões                        |
+|         Custo por query         |                     $0                      |                             $0.00004                              |
+|         Infraestrutura          |                Centralizada                 |                          Descentralizada                          |
+|     Redundância geográfica      | $1.200 em custos totais por node adicional  |                             Incluída                              |
+|    Uptime (disponibilidade)     |                    Varia                    |                              99.9%+                               |
+|      Custos mensais totais      | <span className="highlight-row" /> $11.000+ |                              $1.200                               |
 
 \*com custos de backup incluídos: $50-$100 por mês
 
 <sup>†</sup>Tempo de engenharia baseado numa hipótese de $200 por hora
 
-<sup>‡</sup>Reflete o custo ao consumidor de dados. Taxas de query ainda são pagas a Indexadores por queries do Plano
-Grátis.
+<sup>‡</sup>Reflete o custo ao consumidor de dados. Taxas de query ainda são pagas a Indexadores por queries do Plano Grátis.
 
 Os custos estimados são apenas para subgraphs na Mainnet do Ethereum — os custos são maiores ao auto-hospedar um `graph-node` em outras redes. Alguns utilizadores devem atualizar o seu subgraph a uma versão mais recente. Até o fechamento deste texto, devido às taxas de gas do Ethereum, uma atualização custa cerca de 50 dólares. Note que as taxas de gás no [Arbitrum](/arbitrum/arbitrum-faq) são muito menores que as da mainnet do Ethereum.
 
@@ -90,4 +89,4 @@ A rede descentralizada do The Graph permite que os utilizadores acessem redundâ
 
 Enfim: A Graph Network é mais barata e fácil de usar, e produz resultados superiores comparados à execução local de um `graph-node`.
 
-Comece a usar a Graph Network hoje, e aprenda como [atualizar o seu subgraph para a rede descentralizada do The Graph](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 4e72c776e2f48628b2c71c28cea5fa5105166ed5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:35 -0500
Subject: [PATCH 0610/1325] New translations benefits.mdx (Russian)

---
 website/pages/ru/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/ru/network/benefits.mdx b/website/pages/ru/network/benefits.mdx
index a2518eb14edb..a11455ede307 100644
--- a/website/pages/ru/network/benefits.mdx
+++ b/website/pages/ru/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Сравнение затрат | Самостоятельный хостинг | Сеть The Graph |
-| :-: | :-: | :-: |
-| Ежемесячная стоимость сервера\* | $350 в месяц | $0 |
-| Стоимость запроса | $0+ | $0 per month |
-| Время разработки<sup>†</sup> | $400 в месяц | Никто, встроен в сеть с глобально распределенными индексаторами |
-| Запросы в месяц | Ограничен возможностями инфраструктуры | 100,000 (Free Plan) |
-| Стоимость одного запроса | $0 | $0<sup>‡</sup> |
-| Инфраструктура | Централизованная | Децентрализованная |
-| Географическая избыточность | $750+ за каждую дополнительную ноду | Включено |
-| Время безотказной работы | Варьируется | 99.9%+ |
-| Общие ежемесячные расходы | <span className="highlight-row" />$750+ | $0 |
+|         Сравнение затрат          |         Самостоятельный хостинг         |                         Сеть The Graph                          |
+|:---------------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+| Ежемесячная стоимость сервера\* |              $350 в месяц               |                               $0                                |
+|         Стоимость запроса         |                   $0+                   |                          $0 per month                           |
+|   Время разработки<sup>†</sup>    |              $400 в месяц               | Никто, встроен в сеть с глобально распределенными индексаторами |
+|          Запросы в месяц          | Ограничен возможностями инфраструктуры  |                       100,000 (Free Plan)                       |
+|     Стоимость одного запроса      |                   $0                    |                         $0<sup>‡</sup>                          |
+|          Инфраструктура           |            Централизованная             |                       Децентрализованная                        |
+|    Географическая избыточность    |   $750+ за каждую дополнительную ноду   |                            Включено                             |
+|     Время безотказной работы      |               Варьируется               |                             99.9%+                              |
+|     Общие ежемесячные расходы     | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Сравнение затрат | Самостоятельный хостинг | Сеть The Graph |
-| :-: | :-: | :-: |
-| Ежемесячная стоимость сервера\* | $350 в месяц | $0 |
-| Стоимость запроса | $500 в месяц | $120 per month |
-| Время разработки<sup>†</sup> | $800 в месяц | Никто, встроен в сеть с глобально распределенными индексаторами |
-| Запросы в месяц | Ограничен возможностями инфраструктуры | ~3,000,000 |
-| Стоимость одного запроса | $0 | $0.00004 |
-| Инфраструктура | Централизованная | Децентрализованная |
-| Инженерные расходы | $200 в час | Включено |
-| Географическая избыточность | общие затраты на каждую дополнительную ноду составляют $1,200 | Включено |
-| Время безотказной работы | Варьируется | 99.9%+ |
-| Общие ежемесячные расходы | <span className="highlight-row" /> $1,650+ | $120 |
+|         Сравнение затрат          |                    Самостоятельный хостинг                    |                         Сеть The Graph                          |
+|:---------------------------------:|:-------------------------------------------------------------:|:---------------------------------------------------------------:|
+| Ежемесячная стоимость сервера\* |                         $350 в месяц                          |                               $0                                |
+|         Стоимость запроса         |                         $500 в месяц                          |                         $120 per month                          |
+|   Время разработки<sup>†</sup>    |                         $800 в месяц                          | Никто, встроен в сеть с глобально распределенными индексаторами |
+|          Запросы в месяц          |            Ограничен возможностями инфраструктуры             |                           ~3,000,000                            |
+|     Стоимость одного запроса      |                              $0                               |                            $0.00004                             |
+|          Инфраструктура           |                       Централизованная                        |                       Децентрализованная                        |
+|        Инженерные расходы         |                          $200 в час                           |                            Включено                             |
+|    Географическая избыточность    | общие затраты на каждую дополнительную ноду составляют $1,200 |                            Включено                             |
+|     Время безотказной работы      |                          Варьируется                          |                             99.9%+                              |
+|     Общие ежемесячные расходы     |          <span className="highlight-row" /> $1,650+           |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Сравнение затрат | Самостоятельный хостинг | Сеть The Graph |
-| :-: | :-: | :-: |
-| Ежемесячная стоимость сервера\* | $1100 в месяц за ноду | $0 |
-| Стоимость запроса | $4000 | $1,200 per month |
-| Необходимое количество нод | 10 | Не подходит |
-| Время разработки<sup>†</sup> | $6,000 или больше в месяц | Никто, встроен в сеть с глобально распределенными индексаторами |
-| Запросы в месяц | Ограничен возможностями инфраструктуры | ~30,000,000 |
-| Стоимость одного запроса | $0 | $0.00004 |
-| Инфраструктура | Централизованная | Децентрализованная |
-| Географическая избыточность | общие затраты на каждую дополнительную ноду составляют $1,200 | Включено |
-| Время безотказной работы | Варьируется | 99.9%+ |
-| Общие ежемесячные расходы | <span className="highlight-row" /> $11,000+ | $1,200 |
+|         Сравнение затрат          |                    Самостоятельный хостинг                    |                         Сеть The Graph                          |
+|:---------------------------------:|:-------------------------------------------------------------:|:---------------------------------------------------------------:|
+| Ежемесячная стоимость сервера\* |                     $1100 в месяц за ноду                     |                               $0                                |
+|         Стоимость запроса         |                             $4000                             |                        $1,200 per month                         |
+|    Необходимое количество нод     |                              10                               |                           Не подходит                           |
+|   Время разработки<sup>†</sup>    |                   $6,000 или больше в месяц                   | Никто, встроен в сеть с глобально распределенными индексаторами |
+|          Запросы в месяц          |            Ограничен возможностями инфраструктуры             |                           ~30,000,000                           |
+|     Стоимость одного запроса      |                              $0                               |                            $0.00004                             |
+|          Инфраструктура           |                       Централизованная                        |                       Децентрализованная                        |
+|    Географическая избыточность    | общие затраты на каждую дополнительную ноду составляют $1,200 |                            Включено                             |
+|     Время безотказной работы      |                          Варьируется                          |                             99.9%+                              |
+|     Общие ежемесячные расходы     |          <span className="highlight-row" /> $11,000+          |                             $1,200                              |
 
 \* включая расходы на резервное копирование: $50-$100 в месяц
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Итог: Сеть Graph дешевле, проще в использовании и дает превосходные результаты по сравнению с запуском `graph-node` локально.
 
-Начните использовать The Graph Network сегодня и узнайте, как [обновить свой субграф до децентрализованной сети The Graph](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From d6891fb206113c8fba0ac7c9812af06ee8bb334a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:36 -0500
Subject: [PATCH 0611/1325] New translations benefits.mdx (Swedish)

---
 website/pages/sv/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/sv/network/benefits.mdx b/website/pages/sv/network/benefits.mdx
index 262dada1844c..3b8ace79fa89 100644
--- a/website/pages/sv/network/benefits.mdx
+++ b/website/pages/sv/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Kostnadsjämförelse | Egen Värd | The Graph Nätverk |
-| :-: | :-: | :-: |
-| Månatlig kostnad för server\* | $350 per månad | $0 |
-| Kostnad för frågor | $0+ | $0 per month |
-| Konstruktionstid<sup>†</sup> | $400 per månad | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
-| Frågor per månad | Begränsad till infra kapacitet | 100,000 (Free Plan) |
-| Kostnad per fråga | $0 | $0<sup>‡</sup> |
-| Infrastruktur | Centraliserad | Decentraliserad |
-| Geografisk redundans | $750+ per extra nod | Inkluderat |
-| Drifttid | Varierande | 99.9%+ |
-| Total Månadskostnad | <span className="highlight-row" />$750+ | $0 |
+|       Kostnadsjämförelse        |                Egen Värd                |                       The Graph Nätverk                       |
+|:-------------------------------:|:---------------------------------------:|:-------------------------------------------------------------:|
+| Månatlig kostnad för server\* |             $350 per månad              |                              $0                               |
+|       Kostnad för frågor        |                   $0+                   |                         $0 per month                          |
+|  Konstruktionstid<sup>†</sup>   |             $400 per månad              | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
+|        Frågor per månad         |     Begränsad till infra kapacitet      |                      100,000 (Free Plan)                      |
+|        Kostnad per fråga        |                   $0                    |                        $0<sup>‡</sup>                         |
+|          Infrastruktur          |              Centraliserad              |                        Decentraliserad                        |
+|      Geografisk redundans       |           $750+ per extra nod           |                          Inkluderat                           |
+|            Drifttid             |               Varierande                |                            99.9%+                             |
+|       Total Månadskostnad       | <span className="highlight-row" />$750+ |                              $0                               |
 
 ## Medium Volume User (~3M queries per month)
 
-| Kostnadsjämförelse | Egen Värd | The Graph Nätverk |
-| :-: | :-: | :-: |
-| Månadskostnad för server\* | $350 per månad | $0 |
-| Kostnad för frågor | $500 per månad | $120 per month |
-| Ingenjörstid<sup>†</sup> | $800 per månad | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
-| Frågor per månad | Begränsad till infra kapacitet | ~3,000,000 |
-| Kostnad per fråga | $0 | $0.00004 |
-| Infrastruktur | Centraliserad | Decentraliserad |
-| Kostnader för ingenjörsarbete | $200 per timme | Inkluderat |
-| Geografisk redundans | $1,200 i totala kostnader per extra nod | Inkluderat |
-| Drifttid | Varierar | 99.9%+ |
-| Total Månadskostnad | <span className="highlight-row" /> $1,650+ | $120 |
+|      Kostnadsjämförelse       |                 Egen Värd                  |                       The Graph Nätverk                       |
+|:-----------------------------:|:------------------------------------------:|:-------------------------------------------------------------:|
+| Månadskostnad för server\*  |               $350 per månad               |                              $0                               |
+|      Kostnad för frågor       |               $500 per månad               |                        $120 per month                         |
+|   Ingenjörstid<sup>†</sup>    |               $800 per månad               | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
+|       Frågor per månad        |       Begränsad till infra kapacitet       |                          ~3,000,000                           |
+|       Kostnad per fråga       |                     $0                     |                           $0.00004                            |
+|         Infrastruktur         |               Centraliserad                |                        Decentraliserad                        |
+| Kostnader för ingenjörsarbete |               $200 per timme               |                          Inkluderat                           |
+|     Geografisk redundans      |  $1,200 i totala kostnader per extra nod   |                          Inkluderat                           |
+|           Drifttid            |                  Varierar                  |                            99.9%+                             |
+|      Total Månadskostnad      | <span className="highlight-row" /> $1,650+ |                             $120                              |
 
 ## High Volume User (~30M queries per month)
 
-| Kostnadsjämförelse | Egen Värd | The Graph Nätverk |
-| :-: | :-: | :-: |
-| Månadskostnad för server\* | $1100 per månad, per nod | $0 |
-| Kostnad för frågor | $4000 | $1,200 per month |
-| Antal noder som behövs | 10 | Ej tillämpligt |
-| Ingenjörstid<sup>†</sup> | $6,000 eller mer per månad | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
-| Frågor per månad | Begränsad till infra kapacitet | ~30,000,000 |
-| Kostnad per fråga | $0 | $0.00004 |
-| Infrastruktur | Centraliserad | Decentraliserad |
-| Geografisk redundans | $1,200 i totala kostnader per extra nod | Inkluderat |
-| Drifttid | Varierar | 99.9%+ |
-| Total Månadskostnad | <span className="highlight-row" /> $11,000+ | $1,200 |
+|      Kostnadsjämförelse      |                  Egen Värd                  |                       The Graph Nätverk                       |
+|:----------------------------:|:-------------------------------------------:|:-------------------------------------------------------------:|
+| Månadskostnad för server\* |          $1100 per månad, per nod           |                              $0                               |
+|      Kostnad för frågor      |                    $4000                    |                       $1,200 per month                        |
+|    Antal noder som behövs    |                     10                      |                        Ej tillämpligt                         |
+|   Ingenjörstid<sup>†</sup>   |         $6,000 eller mer per månad          | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
+|       Frågor per månad       |       Begränsad till infra kapacitet        |                          ~30,000,000                          |
+|      Kostnad per fråga       |                     $0                      |                           $0.00004                            |
+|        Infrastruktur         |                Centraliserad                |                        Decentraliserad                        |
+|     Geografisk redundans     |   $1,200 i totala kostnader per extra nod   |                          Inkluderat                           |
+|           Drifttid           |                  Varierar                   |                            99.9%+                             |
+|     Total Månadskostnad      | <span className="highlight-row" /> $11,000+ |                            $1,200                             |
 
 \*inklusive kostnader för backup: $50-$100 per månad
 
@@ -89,4 +89,4 @@ The Graphs decentraliserade nätverk ger användare tillgång till geografisk re
 
 Sammanfattningsvis är The Graph Nätverk mindre kostsamt, enklare att använda och ger överlägsna resultat jämfört med att köra en `graph-node` lokalt.
 
-Börja använda The Graph Network idag och lär dig hur du [uppgraderar din subgraf till The Graphs decentraliserade nätverk](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From b9f7ca74b2045ee58f14a1b34a670570a503d185 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:38 -0500
Subject: [PATCH 0612/1325] New translations benefits.mdx (Turkish)

---
 website/pages/tr/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/tr/network/benefits.mdx b/website/pages/tr/network/benefits.mdx
index 779c806b5d23..282c68f00f68 100644
--- a/website/pages/tr/network/benefits.mdx
+++ b/website/pages/tr/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | Graph Ağı |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| Altyapı | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                            Graph Ağı                            |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|           Altyapı            |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | Graph Ağı |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Altyapı | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                            Graph Ağı                            |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|           Altyapı            |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | Graph Ağı |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Altyapı | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                            Graph Ağı                            |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|           Altyapı            |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ Graph'ın merkeziyetsiz ağı, kullanıcılara bir `graph node`'unu kendi kendin
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Graph Ağını bugün kullanmaya başlayın ve [subgraph'ınızı Graph'in merkeziyetsiz ağına nasıl yükselteceğinizi](/cookbook/upgrading-a-subgraph) öğrenin.
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 2f7bb8f6e427bb7b74ee47e9d8a2429dd412c27b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:39 -0500
Subject: [PATCH 0613/1325] New translations benefits.mdx (Ukrainian)

---
 website/pages/uk/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/uk/network/benefits.mdx b/website/pages/uk/network/benefits.mdx
index 2ddce9526ffe..b37047538c52 100644
--- a/website/pages/uk/network/benefits.mdx
+++ b/website/pages/uk/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Порівняння вартості послуг | Самостійний хостинг | Graph мережа |
-| :-: | :-: | :-: |
-| Щомісячна плата за сервер\* | $350 на місяць | $0 |
-| Вартість запитів | $0+ | $0 per month |
-| Час технічного обслуговування<sup>†</sup> | $400 на місяць | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
-| Кількість запитів за місяць | Обмежується інфраструктурними можливостями | 100,000 (Free Plan) |
-| Вартість одного запиту | $0 | $0<sup>‡</sup> |
-| Інфраструктура | Централізована | Децентралізована |
-| Географічне резервування | $750+ за кожну додаткову ноду | Включено |
-| Час безвідмовної роботи | Варіюється | 99.9%+ |
-| Загальна сума щомісячних витрат | <span className="highlight-row" />$750+ | $0 |
+|        Порівняння вартості послуг         |            Самостійний хостинг             |                           Graph мережа                            |
+|:-----------------------------------------:|:------------------------------------------:|:-----------------------------------------------------------------:|
+|       Щомісячна плата за сервер\*       |               $350 на місяць               |                                $0                                 |
+|             Вартість запитів              |                    $0+                     |                           $0 per month                            |
+| Час технічного обслуговування<sup>†</sup> |               $400 на місяць               | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
+|        Кількість запитів за місяць        | Обмежується інфраструктурними можливостями |                        100,000 (Free Plan)                        |
+|          Вартість одного запиту           |                     $0                     |                          $0<sup>‡</sup>                           |
+|              Інфраструктура               |               Централізована               |                         Децентралізована                          |
+|         Географічне резервування          |       $750+ за кожну додаткову ноду        |                             Включено                              |
+|          Час безвідмовної роботи          |                 Варіюється                 |                              99.9%+                               |
+|      Загальна сума щомісячних витрат      |  <span className="highlight-row" />$750+   |                                $0                                 |
 
 ## Medium Volume User (~3M queries per month)
 
-| Порівняння вартості послуг | Самостійний хостинг | Graph мережа |
-| :-: | :-: | :-: |
-| Щомісячна плата за сервер\* | $350 на місяць | $0 |
-| Вартість запитів | $500 на місяць | $120 per month |
-| Час технічного обслуговування<sup>†</sup> | $800 на місяць | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
-| Кількість запитів за місяць | Обмежується інфраструктурними можливостями | ~3,000,000 |
-| Вартість одного запиту | $0 | $0.00004 |
-| Інфраструктура | Централізована | Децентралізована |
-| Інженерно-технічні витрати | $200 на годину | Включено |
-| Географічне резервування | $1,200 загальних витрат на кожну додаткову ноду | Включено |
-| Час безвідмовної роботи | Варіюється | 99.9%+ |
-| Загальна сума щомісячних витрат | <span className="highlight-row" /> $1,650+ | $120 |
+|        Порівняння вартості послуг         |               Самостійний хостинг               |                           Graph мережа                            |
+|:-----------------------------------------:|:-----------------------------------------------:|:-----------------------------------------------------------------:|
+|       Щомісячна плата за сервер\*       |                 $350 на місяць                  |                                $0                                 |
+|             Вартість запитів              |                 $500 на місяць                  |                          $120 per month                           |
+| Час технічного обслуговування<sup>†</sup> |                 $800 на місяць                  | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
+|        Кількість запитів за місяць        |   Обмежується інфраструктурними можливостями    |                            ~3,000,000                             |
+|          Вартість одного запиту           |                       $0                        |                             $0.00004                              |
+|              Інфраструктура               |                 Централізована                  |                         Децентралізована                          |
+|        Інженерно-технічні витрати         |                 $200 на годину                  |                             Включено                              |
+|         Географічне резервування          | $1,200 загальних витрат на кожну додаткову ноду |                             Включено                              |
+|          Час безвідмовної роботи          |                   Варіюється                    |                              99.9%+                               |
+|      Загальна сума щомісячних витрат      |   <span className="highlight-row" /> $1,650+    |                               $120                                |
 
 ## High Volume User (~30M queries per month)
 
-| Порівняння вартості послуг | Самостійний хостинг | Graph мережа |
-| :-: | :-: | :-: |
-| Щомісячна плата за сервер\* | $1100 на місяць, за одну ноду | $0 |
-| Вартість запитів | $4000 | $1,200 per month |
-| Кількість необхідних нод | 10 | Не стосується |
-| Час технічного обслуговування<sup>†</sup> | $6,000 і більше на місяць | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
-| Кількість запитів за місяць | Обмежується інфраструктурними можливостями | ~30,000,000 |
-| Вартість одного запиту | $0 | $0.00004 |
-| Інфраструктура | Централізована | Децентралізована |
-| Географічне резервування | $1,200 загальних витрат на кожну додаткову ноду | Включено |
-| Час безвідмовної роботи | Варіюється | 99.9%+ |
-| Загальна сума щомісячних витрат | <span className="highlight-row" /> $11,000+ | $1,200 |
+|        Порівняння вартості послуг         |               Самостійний хостинг               |                           Graph мережа                            |
+|:-----------------------------------------:|:-----------------------------------------------:|:-----------------------------------------------------------------:|
+|       Щомісячна плата за сервер\*       |          $1100 на місяць, за одну ноду          |                                $0                                 |
+|             Вартість запитів              |                      $4000                      |                         $1,200 per month                          |
+|         Кількість необхідних нод          |                       10                        |                           Не стосується                           |
+| Час технічного обслуговування<sup>†</sup> |            $6,000 і більше на місяць            | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
+|        Кількість запитів за місяць        |   Обмежується інфраструктурними можливостями    |                            ~30,000,000                            |
+|          Вартість одного запиту           |                       $0                        |                             $0.00004                              |
+|              Інфраструктура               |                 Централізована                  |                         Децентралізована                          |
+|         Географічне резервування          | $1,200 загальних витрат на кожну додаткову ноду |                             Включено                              |
+|          Час безвідмовної роботи          |                   Варіюється                    |                              99.9%+                               |
+|      Загальна сума щомісячних витрат      |   <span className="highlight-row" /> $11,000+   |                              $1,200                               |
 
 \*включаючи витрати на резервне копіювання: $50-$100 на місяць
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 710a65d596d85ea11db1780d285441df94add838 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:40 -0500
Subject: [PATCH 0614/1325] New translations benefits.mdx (Chinese Simplified)

---
 website/pages/zh/network/benefits.mdx | 74 +++++++++++++--------------
 1 file changed, 37 insertions(+), 37 deletions(-)

diff --git a/website/pages/zh/network/benefits.mdx b/website/pages/zh/network/benefits.mdx
index 4af9c67518ce..56e7fbfdbde5 100644
--- a/website/pages/zh/network/benefits.mdx
+++ b/website/pages/zh/network/benefits.mdx
@@ -27,49 +27,49 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       成本比较       |                 自托管                  |                 Graph网络                  |
-| :------------------: | :-------------------------------------: | :----------------------------------------: |
-|  每月服务器费用 \*   |               每月350美元               |                   0美元                    |
-|       查询成本       |                   $0+                   |                $0 per month                |
-| 工程时间<sup>†</sup> |               400美元每月               | 没有，内置在具有全球去中心化索引者的网络中 |
-|       每月查询       |           受限于基础设施能力            |            100,000 (Free Plan)             |
-|    每个查询的成本    |                  0美元                  |               $0<sup>‡</sup>               |
-|       基础设施       |                 中心化                  |                  去中心化                  |
-|       异地备援       |           每个额外节点 $750 +           |                  包括在内                  |
-|     正常工作时间     |                  变量                   |                   99.9%+                   |
-|      每月总成本      | <span className="highlight-row" />$750+ |                   0美元                    |
+|       成本比较       |                   自托管                   |        Graph网络        |
+|:----------------:|:---------------------------------------:|:---------------------:|
+|   每月服务器费用 \*   |                 每月350美元                 |          0美元          |
+|       查询成本       |                   $0+                   |     $0 per month      |
+| 工程时间<sup>†</sup> |                 400美元每月                 | 没有，内置在具有全球去中心化索引者的网络中 |
+|       每月查询       |                受限于基础设施能力                |  100,000 (Free Plan)  |
+|     每个查询的成本      |                   0美元                   |    $0<sup>‡</sup>     |
+|       基础设施       |                   中心化                   |         去中心化          |
+|       异地备援       |              每个额外节点 $750 +              |         包括在内          |
+|      正常工作时间      |                   变量                    |        99.9%+         |
+|      每月总成本       | <span className="highlight-row" />$750+ |          0美元          |
 
 ## Medium Volume User (~3M queries per month)
 
-|       成本比较       |                     自托管                      |                 Graph网络                  |
-| :------------------: | :---------------------------------------------: | :----------------------------------------: |
-|  每月服务器费用 \*   |                   每月350美元                   |                   0美元                    |
-|       查询成本       |                   每月500美元                   |               $120 per month               |
+|       成本比较       |                     自托管                     |        Graph网络        |
+|:----------------:|:-------------------------------------------:|:---------------------:|
+|   每月服务器费用 \*   |                   每月350美元                   |          0美元          |
+|       查询成本       |                   每月500美元                   |    $120 per month     |
 | 工程时间<sup>†</sup> |                   每月800美元                   | 没有，内置在具有全球去中心化索引者的网络中 |
-|       每月查询       |               受限于基础设施能力                |                 ~3,000,000                 |
-|    每个查询的成本    |                      0美元                      |                  $0.00004                  |
-|       基础设施       |                     中心化                      |                  去中心化                  |
-|       工程费用       |                  每小时200美元                  |                  包括在内                  |
-|       异地备援       |         每个额外节点的总成本为1200美元          |                  包括在内                  |
-|     正常工作时间     |                      变量                       |                   99.9%+                   |
-|      每月总成本      | <span className="highlight-row" /> 1650美元以上 |                    $120                    |
+|       每月查询       |                  受限于基础设施能力                  |      ~3,000,000       |
+|     每个查询的成本      |                     0美元                     |       $0.00004        |
+|       基础设施       |                     中心化                     |         去中心化          |
+|       工程费用       |                  每小时200美元                   |         包括在内          |
+|       异地备援       |              每个额外节点的总成本为1200美元              |         包括在内          |
+|      正常工作时间      |                     变量                      |        99.9%+         |
+|      每月总成本       | <span className="highlight-row" /> 1650美元以上 |         $120          |
 
 ## High Volume User (~30M queries per month)
 
-|       成本比较       |                    自托管                     |                 Graph网络                  |
-| :------------------: | :-------------------------------------------: | :----------------------------------------: |
-|  每月服务器费用 \*   |              1100美元每月每节点               |                   0美元                    |
-|       查询成本       |                   4000美元                    |              $1,200 per month              |
-|    需要的节点数量    |                      10                       |                   不适用                   |
-| 工程时间<sup>†</sup> |              每月6000美元或以上               | 没有，内置在具有全球去中心化索引人的网络中 |
-|       每月查询       |              受限于基础设施能力               |                ~30,000,000                 |
-|    每个查询的成本    |                     0美元                     |                  $0.00004                  |
-|       基础设施       |                    中心化                     |                  去中心化                  |
-|       异地备援       |        每个额外节点的总成本为1200美元         |                  包括在内                  |
-|     正常工作时间     |                     变量                      |                   99.9%+                   |
-|      每月总成本      | <span className="highlight-row" /> 11000+美元 |                   $1,200                   |
-
-- 包括后备费用: 每月$50-$100美元
+|       成本比较       |                     自托管                     |        Graph网络        |
+|:----------------:|:-------------------------------------------:|:---------------------:|
+|   每月服务器费用 \*   |                 1100美元每月每节点                 |          0美元          |
+|       查询成本       |                   4000美元                    |   $1,200 per month    |
+|     需要的节点数量      |                     10                      |          不适用          |
+| 工程时间<sup>†</sup> |                 每月6000美元或以上                 | 没有，内置在具有全球去中心化索引人的网络中 |
+|       每月查询       |                  受限于基础设施能力                  |      ~30,000,000      |
+|     每个查询的成本      |                     0美元                     |       $0.00004        |
+|       基础设施       |                     中心化                     |         去中心化          |
+|       异地备援       |              每个额外节点的总成本为1200美元              |         包括在内          |
+|      正常工作时间      |                     变量                      |        99.9%+         |
+|      每月总成本       | <span className="highlight-row" /> 11000+美元 |        $1,200         |
+
+* 包括后备费用: 每月$50-$100美元
 
 <sup>†</sup>按每小时200美元的假设计算的工程时间
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 一句话: 与在本地运行一个`graph-node`相比，Graph网络成本更低，更容易使用，并且产生更好的结果。
 
-今天开始使用Graph网络学习如何 [将您的子图升级到Graph的去中心化网络](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 4af9baf3fdf3b0cbe6b55609baee70b38d7bfb4b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:41 -0500
Subject: [PATCH 0615/1325] New translations benefits.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/benefits.mdx | 76 +++++++++++++--------------
 1 file changed, 38 insertions(+), 38 deletions(-)

diff --git a/website/pages/ur/network/benefits.mdx b/website/pages/ur/network/benefits.mdx
index 4bea83bb29a0..21ef629e8418 100644
--- a/website/pages/ur/network/benefits.mdx
+++ b/website/pages/ur/network/benefits.mdx
@@ -27,49 +27,49 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| اخراجات کا موازنہ | خود میزبان | The Graph Network |
-| :-: | :-: | :-: |
-| ماہانہ سرور کی قیمت/\* | $350 فی مہینہ | $0 |
-| استفسار کے اخراجات | $0+ | $0 per month |
-| انجینئرنگ کا وقت<sup>†</sup> | $400 فی مہینہ | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
-| فی مہینہ سوالات | بنیادی صلاحیتوں تک محدود | 100,000 (Free Plan) |
-| قیمت فی سوال | $0 | $0<sup>‡</sup> |
-| بنیادی ڈھانچہ | سینٹرلائزڈ | ڈیسینٹرلائزڈ |
-| جغرافیائی فالتو پن | $750+ فی اضافی نوڈ | شامل |
-| اپ ٹائم | اتار چڑھاو | 99.9%+ |
-| کل ماہانہ اخراجات | <span className="highlight-row" />$750+ | $0 |
+|      اخراجات کا موازنہ       |               خود میزبان                |                                The Graph Network                                |
+|:----------------------------:|:---------------------------------------:|:-------------------------------------------------------------------------------:|
+|    ماہانہ سرور کی قیمت/*     |              $350 فی مہینہ              |                                       $0                                        |
+|      استفسار کے اخراجات      |                   $0+                   |                                  $0 per month                                   |
+| انجینئرنگ کا وقت<sup>†</sup> |              $400 فی مہینہ              | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
+|       فی مہینہ سوالات        |        بنیادی صلاحیتوں تک محدود         |                               100,000 (Free Plan)                               |
+|         قیمت فی سوال         |                   $0                    |                                 $0<sup>‡</sup>                                  |
+|        بنیادی ڈھانچہ         |               سینٹرلائزڈ                |                                  ڈیسینٹرلائزڈ                                   |
+|      جغرافیائی فالتو پن      |           $750+ فی اضافی نوڈ            |                                      شامل                                       |
+|           اپ ٹائم            |               اتار چڑھاو                |                                     99.9%+                                      |
+|      کل ماہانہ اخراجات       | <span className="highlight-row" />$750+ |                                       $0                                        |
 
 ## Medium Volume User (~3M queries per month)
 
-| اخراجات کا موازنہ | خود میزبان | The Graph Network |
-| :-: | :-: | :-: |
-| ماہانہ سرور کی قیمت/\* | $350 فی مہینہ | $0 |
-| استفسار کے اخراجات | $500 فی مہینہ | $120 per month |
-| انجینئرنگ کا وقت<sup>†</sup> | $800 فی مہینہ | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
-| فی مہینہ سوالات | بنیادی صلاحیتوں تک محدود | ~3,000,000 |
-| قیمت فی سوال | $0 | $0.00004 |
-| بنیادی ڈھانچہ | سینٹرلائزڈ | ڈیسینٹرلائزڈ |
-| انجینئرنگ کے اخراجات | $200 فی گھنٹہ | شامل |
-| جغرافیائی فالتو پن | فی اضافی نوڈ کل اخراجات میں $1,200 | شامل |
-| اپ ٹائم | اتار چڑھاو | 99.9%+ |
-| کل ماہانہ اخراجات | <span className="highlight-row" /> $1,650+ | $120 |
+|      اخراجات کا موازنہ       |                 خود میزبان                 |                                The Graph Network                                |
+|:----------------------------:|:------------------------------------------:|:-------------------------------------------------------------------------------:|
+|    ماہانہ سرور کی قیمت/*     |               $350 فی مہینہ                |                                       $0                                        |
+|      استفسار کے اخراجات      |               $500 فی مہینہ                |                                 $120 per month                                  |
+| انجینئرنگ کا وقت<sup>†</sup> |               $800 فی مہینہ                | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
+|       فی مہینہ سوالات        |          بنیادی صلاحیتوں تک محدود          |                                   ~3,000,000                                    |
+|         قیمت فی سوال         |                     $0                     |                                    $0.00004                                     |
+|        بنیادی ڈھانچہ         |                 سینٹرلائزڈ                 |                                  ڈیسینٹرلائزڈ                                   |
+|     انجینئرنگ کے اخراجات     |               $200 فی گھنٹہ                |                                      شامل                                       |
+|      جغرافیائی فالتو پن      |     فی اضافی نوڈ کل اخراجات میں $1,200     |                                      شامل                                       |
+|           اپ ٹائم            |                 اتار چڑھاو                 |                                     99.9%+                                      |
+|      کل ماہانہ اخراجات       | <span className="highlight-row" /> $1,650+ |                                      $120                                       |
 
 ## High Volume User (~30M queries per month)
 
-| اخراجات کا موازنہ | سیلف ہوسٹڈ | The Graph Network |
-| :-: | :-: | :-: |
-| ماہانہ سرور کی قیمت/\* | $1100 فی مہینہ، فی نوڈ | $0 |
-| استفسار کے اخراجات | $4000 | $1,200 per month |
-| نوڈس کی تعداد درکار ہے | 10 | قابل اطلاق نہیں |
-| انجینئرنگ کا وقت<sup>†</sup> | $6,000 یا اس سے زیادہ فی مہینہ | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
-| فی مہینہ سوالات | بنیادی صلاحیتوں تک محدود | ~30,000,000 |
-| قیمت فی سوال | $0 | $0.00004 |
-| بنیادی ڈھانچہ | سینٹرلائزڈ | ڈیسینٹرلائزڈ |
-| جغرافیائی فالتو پن | فی اضافی نوڈ کل اخراجات میں $1,200 | شامل |
-| اپ ٹائم | اتار چڑھاو | 99.9%+ |
-| کل ماہانہ اخراجات | <span className="highlight-row" /> $11,000+ | $1,200 |
-
-/\*بیک اپ کے اخراجات سمیت: $50-$100 فی مہینہ
+|      اخراجات کا موازنہ       |                 سیلف ہوسٹڈ                  |                                The Graph Network                                |
+|:----------------------------:|:-------------------------------------------:|:-------------------------------------------------------------------------------:|
+|    ماہانہ سرور کی قیمت/*     |           $1100 فی مہینہ، فی نوڈ            |                                       $0                                        |
+|      استفسار کے اخراجات      |                    $4000                    |                                $1,200 per month                                 |
+|    نوڈس کی تعداد درکار ہے    |                     10                      |                                 قابل اطلاق نہیں                                 |
+| انجینئرنگ کا وقت<sup>†</sup> |       $6,000 یا اس سے زیادہ فی مہینہ        | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
+|       فی مہینہ سوالات        |          بنیادی صلاحیتوں تک محدود           |                                   ~30,000,000                                   |
+|         قیمت فی سوال         |                     $0                      |                                    $0.00004                                     |
+|        بنیادی ڈھانچہ         |                 سینٹرلائزڈ                  |                                  ڈیسینٹرلائزڈ                                   |
+|      جغرافیائی فالتو پن      |     فی اضافی نوڈ کل اخراجات میں $1,200      |                                      شامل                                       |
+|           اپ ٹائم            |                 اتار چڑھاو                  |                                     99.9%+                                      |
+|      کل ماہانہ اخراجات       | <span className="highlight-row" /> $11,000+ |                                     $1,200                                      |
+
+/*بیک اپ کے اخراجات سمیت: $50-$100 فی مہینہ
 
 <sup>†</sup>$200 فی گھنٹہ کے مفروضے کی بنیاد پر انجینئرنگ کا وقت
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 نیچے کی سطر: گراف نیٹ ورک کم مہنگا ہے، استعمال میں آسان ہے، اور مقامی طور پر `graph-node` کو چلانے کے مقابلے میں بہتر نتائج پیدا کرتا ہے.
 
-آج ہی گراف نیٹ ورک کا استعمال کرنا شروع کر دیں، اور سیکھیں کہ کیسے [اپنے سب گراف کو گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر اپ گریڈ کریں](/cookbook/upgrading-a-subgraph)۔
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 316aea11d5af64b510436812d22e1348cb4cbd8c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:42 -0500
Subject: [PATCH 0616/1325] New translations benefits.mdx (Vietnamese)

---
 website/pages/vi/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/vi/network/benefits.mdx b/website/pages/vi/network/benefits.mdx
index 048ef59484eb..a5857ff2ed86 100644
--- a/website/pages/vi/network/benefits.mdx
+++ b/website/pages/vi/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| Cost Comparison | Self Hosted | Mạng The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $0+ | $0 per month |
-| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
-| Cost per query | $0 | $0<sup>‡</sup> |
-| Cơ sở hạ tầng | Centralized | Decentralized |
-| Geographic redundancy | $750+ per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
+|       Cost Comparison        |               Self Hosted               |                         Mạng The Graph                          |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|        Cơ sở hạ tầng         |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
 
 ## Medium Volume User (~3M queries per month)
 
-| Cost Comparison | Self Hosted | Mạng The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $350 per month | $0 |
-| Query costs | $500 per month | $120 per month |
-| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~3,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Cơ sở hạ tầng | Centralized | Decentralized |
-| Engineering expense | $200 per hour | Included |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
+|       Cost Comparison        |                Self Hosted                 |                         Mạng The Graph                          |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|        Cơ sở hạ tầng         |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
 
 ## High Volume User (~30M queries per month)
 
-| Cost Comparison | Self Hosted | Mạng The Graph |
-| :-: | :-: | :-: |
-| Monthly server cost\* | $1100 per month, per node | $0 |
-| Query costs | $4000 | $1,200 per month |
-| Number of nodes needed | 10 | Not applicable |
-| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
-| Queries per month | Limited to infra capabilities | ~30,000,000 |
-| Cost per query | $0 | $0.00004 |
-| Cơ sở hạ tầng | Centralized | Decentralized |
-| Geographic redundancy | $1,200 in total costs per additional node | Included |
-| Uptime | Varies | 99.9%+ |
-| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
+|       Cost Comparison        |                 Self Hosted                 |                         Mạng The Graph                          |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|        Cơ sở hạ tầng         |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
 
 \*including costs for backup: $50-$100 per month
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 2f08ace3ee51dd26b012730385f1b5023de235bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:43 -0500
Subject: [PATCH 0617/1325] New translations benefits.mdx (Marathi)

---
 website/pages/mr/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/mr/network/benefits.mdx b/website/pages/mr/network/benefits.mdx
index b8b01f42b679..95d7187a2039 100644
--- a/website/pages/mr/network/benefits.mdx
+++ b/website/pages/mr/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| खर्चाची तुलना | स्वत: होस्ट केलेले | आलेख नेटवर्क |
-| :-: | :-: | :-: |
-| मासिक सर्व्हर खर्च\* | दरमहा $350 | $0 |
-| क्वेरी खर्च | $0+ | $0 per month |
-| अभियांत्रिकी वेळ<sup>†</sup> | दरमहा $400 | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
-| प्रति महिना प्रश्न | इन्फ्रा क्षमतांपुरती मर्यादित | 100,000 (Free Plan) |
-| प्रति क्वेरी खर्च | $0 | $0<sup>‡</sup> |
-| पायाभूत सुविधा | केंद्रीकृत | विकेंद्रित |
-| भौगोलिक रिडंडंसी | प्रति अतिरिक्त नोड $750+ | समाविष्ट |
-| अपटाइम | बदलते | 99.9%+ |
-| एकूण मासिक खर्च | <span className="highlight-row" />$750+ | $0 |
+|        खर्चाची तुलना         |           स्वत: होस्ट केलेले            |                               आलेख नेटवर्क                               |
+|:----------------------------:|:---------------------------------------:|:------------------------------------------------------------------------:|
+|    मासिक सर्व्हर खर्च\*    |               दरमहा $350                |                                    $0                                    |
+|         क्वेरी खर्च          |                   $0+                   |                               $0 per month                               |
+| अभियांत्रिकी वेळ<sup>†</sup> |               दरमहा $400                | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
+|      प्रति महिना प्रश्न      |      इन्फ्रा क्षमतांपुरती मर्यादित      |                           100,000 (Free Plan)                            |
+|      प्रति क्वेरी खर्च       |                   $0                    |                              $0<sup>‡</sup>                              |
+|        पायाभूत सुविधा        |               केंद्रीकृत                |                                विकेंद्रित                                |
+|       भौगोलिक रिडंडंसी       |        प्रति अतिरिक्त नोड $750+         |                                 समाविष्ट                                 |
+|            अपटाइम            |                  बदलते                  |                                  99.9%+                                  |
+|       एकूण मासिक खर्च        | <span className="highlight-row" />$750+ |                                    $0                                    |
 
 ## Medium Volume User (~3M queries per month)
 
-| खर्चाची तुलना | स्वत: होस्ट केलेले | आलेख नेटवर्क |
-| :-: | :-: | :-: |
-| मासिक सर्व्हर खर्च\* | दरमहा $350 | $0 |
-| क्वेरी खर्च | दरमहा $500 | $120 per month |
-| अभियांत्रिकी वेळ<sup>†</sup> | दरमहा $800 | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
-| प्रति महिना प्रश्न | इन्फ्रा क्षमतांपुरती मर्यादित | ~3,000,000 |
-| प्रति क्वेरी खर्च | $0 | $0.00004 |
-| पायाभूत सुविधा | केंद्रीकृत | विकेंद्रित |
-| अभियांत्रिकी खर्च | $200 प्रति तास | समाविष्ट |
-| भौगोलिक रिडंडंसी | प्रति अतिरिक्त नोड एकूण खर्चात $1,200 | समाविष्ट |
-| अपटाइम | बदलते | 99.9%+ |
-| एकूण मासिक खर्च | <span className="highlight-row" /> $1,650+ | $120 |
+|        खर्चाची तुलना         |             स्वत: होस्ट केलेले             |                               आलेख नेटवर्क                               |
+|:----------------------------:|:------------------------------------------:|:------------------------------------------------------------------------:|
+|    मासिक सर्व्हर खर्च\*    |                 दरमहा $350                 |                                    $0                                    |
+|         क्वेरी खर्च          |                 दरमहा $500                 |                              $120 per month                              |
+| अभियांत्रिकी वेळ<sup>†</sup> |                 दरमहा $800                 | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
+|      प्रति महिना प्रश्न      |       इन्फ्रा क्षमतांपुरती मर्यादित        |                                ~3,000,000                                |
+|      प्रति क्वेरी खर्च       |                     $0                     |                                 $0.00004                                 |
+|        पायाभूत सुविधा        |                 केंद्रीकृत                 |                                विकेंद्रित                                |
+|      अभियांत्रिकी खर्च       |               $200 प्रति तास               |                                 समाविष्ट                                 |
+|       भौगोलिक रिडंडंसी       |   प्रति अतिरिक्त नोड एकूण खर्चात $1,200    |                                 समाविष्ट                                 |
+|            अपटाइम            |                   बदलते                    |                                  99.9%+                                  |
+|       एकूण मासिक खर्च        | <span className="highlight-row" /> $1,650+ |                                   $120                                   |
 
 ## High Volume User (~30M queries per month)
 
-| खर्चाची तुलना | स्वत: होस्ट केलेले | आलेख नेटवर्क |
-| :-: | :-: | :-: |
-| मासिक सर्व्हर खर्च\* | प्रति नोड, प्रति महिना $1100 | $0 |
-| क्वेरी खर्च | $4000 | $1,200 per month |
-| आवश्यक नोड्सची संख्या | 10 | लागू नाही |
-| अभियांत्रिकी वेळ<sup>†</sup> | दरमहा $6,000 किंवा अधिक | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
-| प्रति महिना प्रश्न | इन्फ्रा क्षमतांपुरती मर्यादित | ~30,000,000 |
-| प्रति क्वेरी खर्च | $0 | $0.00004 |
-| पायाभूत सुविधा | केंद्रीकृत | विकेंद्रित |
-| भौगोलिक रिडंडंसी | प्रति अतिरिक्त नोड एकूण खर्चात $1,200 | समाविष्ट |
-| अपटाइम | बदलते | 99.9%+ |
-| एकूण मासिक खर्च | <span className="highlight-row" /> $11,000+ | $1,200 |
+|        खर्चाची तुलना         |             स्वत: होस्ट केलेले              |                               आलेख नेटवर्क                               |
+|:----------------------------:|:-------------------------------------------:|:------------------------------------------------------------------------:|
+|    मासिक सर्व्हर खर्च\*    |        प्रति नोड, प्रति महिना $1100         |                                    $0                                    |
+|         क्वेरी खर्च          |                    $4000                    |                             $1,200 per month                             |
+|    आवश्यक नोड्सची संख्या     |                     10                      |                                लागू नाही                                 |
+| अभियांत्रिकी वेळ<sup>†</sup> |           दरमहा $6,000 किंवा अधिक           | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
+|      प्रति महिना प्रश्न      |        इन्फ्रा क्षमतांपुरती मर्यादित        |                               ~30,000,000                                |
+|      प्रति क्वेरी खर्च       |                     $0                      |                                 $0.00004                                 |
+|        पायाभूत सुविधा        |                 केंद्रीकृत                  |                                विकेंद्रित                                |
+|       भौगोलिक रिडंडंसी       |    प्रति अतिरिक्त नोड एकूण खर्चात $1,200    |                                 समाविष्ट                                 |
+|            अपटाइम            |                    बदलते                    |                                  99.9%+                                  |
+|       एकूण मासिक खर्च        | <span className="highlight-row" /> $11,000+ |                                  $1,200                                  |
 
 \*बॅकअपच्या खर्चासह: $50-$100 प्रति महिना
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 तळ ओळ: ग्राफ नेटवर्क कमी खर्चिक आहे, वापरण्यास सोपे आहे आणि स्थानिक पातळीवर `ग्राफ-नोड` चालवण्याच्या तुलनेत उत्कृष्ट परिणाम देते.
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 125bfd94f165b8f5b4dde5d7c9ac26e2ea2c222e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:44 -0500
Subject: [PATCH 0618/1325] New translations benefits.mdx (Hindi)

---
 website/pages/hi/network/benefits.mdx | 72 +++++++++++++--------------
 1 file changed, 36 insertions(+), 36 deletions(-)

diff --git a/website/pages/hi/network/benefits.mdx b/website/pages/hi/network/benefits.mdx
index 910f3e18dff7..fb724441c964 100644
--- a/website/pages/hi/network/benefits.mdx
+++ b/website/pages/hi/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-| लागत तुलना | स्वयं होस्ट किया गया | The Graph Network |
-| :-: | :-: | :-: |
-| मासिक सर्वर लागत\* | $350 प्रति माह | $0 |
-| पूछताछ लागत | $0+ | $0 per month |
-| इंजीनियरिंग का समय<sup>†</sup> | $ 400 प्रति माह | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
-| प्रति माह प्रश्न | इन्फ्रा क्षमताओं तक सीमित | 100,000 (Free Plan) |
-| लागत प्रति क्वेरी | $0 | $0<sup>‡</sup> |
-| आधारभूत संरचना | केंद्रीकृत | विकेन्द्रीकृत |
-| भौगोलिक अतिरेक | $750+ प्रति अतिरिक्त नोड | शामिल |
-| अपटाइम | भिन्न | 99.9%+ |
-| कुल मासिक लागत | <span className="highlight-row" />$750+ | $0 |
+|           लागत तुलना           |          स्वयं होस्ट किया गया           |                           The Graph Network                            |
+|:------------------------------:|:---------------------------------------:|:----------------------------------------------------------------------:|
+|      मासिक सर्वर लागत\*      |             $350 प्रति माह              |                                   $0                                   |
+|          पूछताछ लागत           |                   $0+                   |                              $0 per month                              |
+| इंजीनियरिंग का समय<sup>†</sup> |             $ 400 प्रति माह             | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
+|        प्रति माह प्रश्न        |        इन्फ्रा क्षमताओं तक सीमित        |                          100,000 (Free Plan)                           |
+|       लागत प्रति क्वेरी        |                   $0                    |                             $0<sup>‡</sup>                             |
+|         आधारभूत संरचना         |               केंद्रीकृत                |                             विकेन्द्रीकृत                              |
+|         भौगोलिक अतिरेक         |        $750+ प्रति अतिरिक्त नोड         |                                 शामिल                                  |
+|             अपटाइम             |                  भिन्न                  |                                 99.9%+                                 |
+|         कुल मासिक लागत         | <span className="highlight-row" />$750+ |                                   $0                                   |
 
 ## Medium Volume User (~3M queries per month)
 
-| लागत तुलना | स्वयं होस्ट किया गया | The Graph Network |
-| :-: | :-: | :-: |
-| मासिक सर्वर लागत\* | $350 प्रति माह | $0 |
-| पूछताछ लागत | $ 500 प्रति माह | $120 per month |
-| इंजीनियरिंग का समय<sup>†</sup> | $800 प्रति माह | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
-| प्रति माह प्रश्न | इन्फ्रा क्षमताओं तक सीमित | ~3,000,000 |
-| लागत प्रति क्वेरी | $0 | $0.00004 |
-| आधारभूत संरचना | केंद्रीकृत | विकेन्द्रीकृत |
-| इंजीनियरिंग खर्च | $ 200 प्रति घंटा | शामिल |
-| भौगोलिक अतिरेक | प्रति अतिरिक्त नोड कुल लागत में $1,200 | शामिल |
-| अपटाइम | भिन्न | 99.9%+ |
-| कुल मासिक लागत | <span className="highlight-row" /> $1,650+ | $120 |
+|           लागत तुलना           |            स्वयं होस्ट किया गया            |                           The Graph Network                            |
+|:------------------------------:|:------------------------------------------:|:----------------------------------------------------------------------:|
+|      मासिक सर्वर लागत\*      |               $350 प्रति माह               |                                   $0                                   |
+|          पूछताछ लागत           |              $ 500 प्रति माह               |                             $120 per month                             |
+| इंजीनियरिंग का समय<sup>†</sup> |               $800 प्रति माह               | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
+|        प्रति माह प्रश्न        |         इन्फ्रा क्षमताओं तक सीमित          |                               ~3,000,000                               |
+|       लागत प्रति क्वेरी        |                     $0                     |                                $0.00004                                |
+|         आधारभूत संरचना         |                 केंद्रीकृत                 |                             विकेन्द्रीकृत                              |
+|        इंजीनियरिंग खर्च        |              $ 200 प्रति घंटा              |                                 शामिल                                  |
+|         भौगोलिक अतिरेक         |   प्रति अतिरिक्त नोड कुल लागत में $1,200   |                                 शामिल                                  |
+|             अपटाइम             |                   भिन्न                    |                                 99.9%+                                 |
+|         कुल मासिक लागत         | <span className="highlight-row" /> $1,650+ |                                  $120                                  |
 
 ## High Volume User (~30M queries per month)
 
-| लागत तुलना | स्वयं होस्ट किया गया | The Graph Network |
-| :-: | :-: | :-: |
-| मासिक सर्वर लागत\* | $1100 प्रति माह, प्रति नोड | $0 |
-| पूछताछ लागत | $4000 | $1,200 per month |
-| आवश्यक नोड्स की संख्या | 10 | Not applicable |
-| इंजीनियरिंग का समय<sup>†</sup> | $6,000 or more per month | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
-| प्रति माह प्रश्न | इन्फ्रा क्षमताओं तक सीमित | ~30,000,000 |
-| लागत प्रति क्वेरी | $0 | $0.00004 |
-| आधारभूत संरचना | केंद्रीकृत | विकेन्द्रीकृत |
-| भौगोलिक अतिरेक | प्रति अतिरिक्त नोड कुल लागत में $1,200 | शामिल |
-| अपटाइम | भिन्न | 99.9%+ |
-| कुल मासिक लागत | <span className="highlight-row" /> $11,000+ | $1,200 |
+|           लागत तुलना           |            स्वयं होस्ट किया गया             |                           The Graph Network                            |
+|:------------------------------:|:-------------------------------------------:|:----------------------------------------------------------------------:|
+|      मासिक सर्वर लागत\*      |         $1100 प्रति माह, प्रति नोड          |                                   $0                                   |
+|          पूछताछ लागत           |                    $4000                    |                            $1,200 per month                            |
+|     आवश्यक नोड्स की संख्या     |                     10                      |                             Not applicable                             |
+| इंजीनियरिंग का समय<sup>†</sup> |          $6,000 or more per month           | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
+|        प्रति माह प्रश्न        |          इन्फ्रा क्षमताओं तक सीमित          |                              ~30,000,000                               |
+|       लागत प्रति क्वेरी        |                     $0                      |                                $0.00004                                |
+|         आधारभूत संरचना         |                 केंद्रीकृत                  |                             विकेन्द्रीकृत                              |
+|         भौगोलिक अतिरेक         |   प्रति अतिरिक्त नोड कुल लागत में $1,200    |                                 शामिल                                  |
+|             अपटाइम             |                    भिन्न                    |                                 99.9%+                                 |
+|         कुल मासिक लागत         | <span className="highlight-row" /> $11,000+ |                                 $1,200                                 |
 
 \*बैकअप की लागत सहित: $50-$100 प्रति माह
 
@@ -89,4 +89,4 @@ The Graph’s decentralized network gives users access to geographic redundancy
 
 निचला रेखा: ग्राफ़ नेटवर्क कम खर्चीला है, उपयोग में आसान है, और `ग्राफ़-नोड` को स्थानीय रूप से चलाने की तुलना में बेहतर परिणाम देता है।
 
-Start using The Graph Network today, and learn how to [upgrade your subgraph to The Graph's decentralized network](/cookbook/upgrading-a-subgraph).
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From d819b87013304154a00c2fe20b6c92c602697c21 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:45 -0500
Subject: [PATCH 0619/1325] New translations benefits.mdx (Swahili)

---
 website/pages/sw/network/benefits.mdx | 92 +++++++++++++++++++++++++++
 1 file changed, 92 insertions(+)
 create mode 100644 website/pages/sw/network/benefits.mdx

diff --git a/website/pages/sw/network/benefits.mdx b/website/pages/sw/network/benefits.mdx
new file mode 100644
index 000000000000..9000c85bc383
--- /dev/null
+++ b/website/pages/sw/network/benefits.mdx
@@ -0,0 +1,92 @@
+---
+title: The Graph Network vs. Self Hosting
+socialImage: https://thegraph.com/docs/img/seo/benefits.jpg
+---
+
+The Graph’s decentralized network has been engineered and refined to create a robust indexing and querying experience—and it’s getting better every day thanks to thousands of contributors around the world.
+
+The benefits of this decentralized protocol cannot be replicated by running a `graph-node` locally. The Graph Network is more reliable, more efficient, and less expensive.
+
+Here is an analysis:
+
+## Why You Should Use The Graph Network
+
+- Significantly lower monthly costs
+- $0 infrastructure setup costs
+- Superior uptime
+- Access to hundreds of independent Indexers around the world
+- 24/7 technical support by global community
+
+## The Benefits Explained
+
+### Lower & more Flexible Cost Structure
+
+No contracts. No monthly fees. Only pay for the queries you use—with an average cost-per-query of $40 per million queries (~$0.00004 per query). Queries are priced in USD and paid in GRT or credit card.
+
+Query costs may vary; the quoted cost is the average at time of publication (March 2024).
+
+## Low Volume User (less than 100,000 queries per month)
+
+|       Cost Comparison        |               Self Hosted               |                        The Graph Network                        |
+|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |             $350 per month              |                               $0                                |
+|         Query costs          |                   $0+                   |                          $0 per month                           |
+| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
+|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
+|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
+|        Infrastructure        |               Centralized               |                          Decentralized                          |
+|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
+|            Uptime            |                 Varies                  |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+
+## Medium Volume User (~3M queries per month)
+
+|       Cost Comparison        |                Self Hosted                 |                        The Graph Network                        |
+|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |               $350 per month               |                               $0                                |
+|         Query costs          |               $500 per month               |                         $120 per month                          |
+| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
+|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
+|        Cost per query        |                     $0                     |                            $0.00004                             |
+|        Infrastructure        |                Centralized                 |                          Decentralized                          |
+|     Engineering expense      |               $200 per hour                |                            Included                             |
+|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                   |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+
+## High Volume User (~30M queries per month)
+
+|       Cost Comparison        |                 Self Hosted                 |                        The Graph Network                        |
+|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
+|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
+|         Query costs          |                    $4000                    |                        $1,200 per month                         |
+|    Number of nodes needed    |                     10                      |                         Not applicable                          |
+| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
+|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
+|        Cost per query        |                     $0                      |                            $0.00004                             |
+|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
+|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
+|            Uptime            |                   Varies                    |                             99.9%+                              |
+|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+
+\*including costs for backup: $50-$100 per month
+
+<sup>†</sup>Engineering time based on $200 per hour assumption
+
+<sup>‡</sup>Reflects cost for data consumer. Query fees are still paid to Indexers for Free Plan queries.
+
+Estimated costs are only for Ethereum Mainnet subgraphs — costs are even higher when self hosting a `graph-node` on other networks. Some users may need to update their subgraph to a new version. Due to Ethereum gas fees, an update costs ~$50 at time of writing. Note that gas fees on [Arbitrum](/arbitrum/arbitrum-faq) are substantially lower than Ethereum mainnet.
+
+Curating signal on a subgraph is an optional one-time, net-zero cost (e.g., $1k in signal can be curated on a subgraph, and later withdrawn—with potential to earn returns in the process).
+
+## No Setup Costs & Greater Operational Efficiency
+
+Zero setup fees. Get started immediately with no setup or overhead costs. No hardware requirements. No outages due to centralized infrastructure, and more time to concentrate on your core product . No need for backup servers, troubleshooting, or expensive engineering resources.
+
+## Reliability & Resiliency
+
+The Graph’s decentralized network gives users access to geographic redundancy that does not exist when self-hosting a `graph-node`. Queries are served reliably thanks to 99.9%+ uptime, achieved by hundreds of independent Indexers securing the network globally.
+
+Bottom line: The Graph Network is less expensive, easier to use, and produces superior results compared to running a `graph-node` locally.
+
+Start using The Graph Network today, and learn how to [publish your subgraph to The Graph's decentralized network](/quick-start).

From 41da66d990e910ad2501fe0677ff74bb1de64190 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:47 -0500
Subject: [PATCH 0620/1325] New translations enums.mdx (Russian)

---
 website/pages/ru/cookbook/enums.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/cookbook/enums.mdx b/website/pages/ru/cookbook/enums.mdx
index a10970c1539f..d2e724ae5f8e 100644
--- a/website/pages/ru/cookbook/enums.mdx
+++ b/website/pages/ru/cookbook/enums.mdx
@@ -50,7 +50,7 @@ type Token @entity {
 
 In this schema, `TokenStatus` is a simple string with no specific, allowed values.
 
-#### Why is this a problem?
+#### Почему это является проблемой?
 
 - There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
 - It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Дополнительные источники
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 187a3dc29e5269be7b730ac8f313aee86c42d515 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:49 -0500
Subject: [PATCH 0621/1325] New translations docsearch.json (German)

---
 website/pages/de/docsearch.json | 42 ++++++++++++++++-----------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/website/pages/de/docsearch.json b/website/pages/de/docsearch.json
index 9f300c69acb0..366e6903069d 100644
--- a/website/pages/de/docsearch.json
+++ b/website/pages/de/docsearch.json
@@ -7,36 +7,36 @@
     "searchBox": {
       "resetButtonTitle": "Die Abfrage löschen",
       "resetButtonAriaLabel": "Die Abfrage löschen",
-      "cancelButtonText": "Cancel",
+      "cancelButtonText": "Abbrechen",
       "cancelButtonAriaLabel": "Anuluj"
     },
     "startScreen": {
-      "recentSearchesTitle": "Recent",
-      "noRecentSearchesText": "No recent searches",
-      "saveRecentSearchButtonTitle": "Save this search",
-      "removeRecentSearchButtonTitle": "Remove this search from history",
-      "favoriteSearchesTitle": "Favorite",
-      "removeFavoriteSearchButtonTitle": "Remove this search from favorites"
+      "recentSearchesTitle": "Aktuelle",
+      "noRecentSearchesText": "Keine aktuellen Suchanfragen",
+      "saveRecentSearchButtonTitle": "Diese Suche speichern",
+      "removeRecentSearchButtonTitle": "Diese Suche aus dem Verlauf entfernen",
+      "favoriteSearchesTitle": "Favorit",
+      "removeFavoriteSearchButtonTitle": "Die Suche aus Favoriten entfernen"
     },
     "errorScreen": {
-      "titleText": "Unable to fetch results",
-      "helpText": "You might want to check your network connection."
+      "titleText": "Ergebnis kann nicht abgerufen werden",
+      "helpText": "Sie sollten Ihre Netzwerkverbindung überprüfen."
     },
     "footer": {
-      "selectText": "to select",
-      "selectKeyAriaLabel": "Enter key",
-      "navigateText": "to navigate",
-      "navigateUpKeyAriaLabel": "Arrow up",
-      "navigateDownKeyAriaLabel": "Arrow down",
-      "closeText": "to close",
-      "closeKeyAriaLabel": "Escape key",
-      "searchByText": "Search by"
+      "selectText": "zur Auswahl",
+      "selectKeyAriaLabel": "Enter-Taste",
+      "navigateText": "zum Navigieren",
+      "navigateUpKeyAriaLabel": "Pfeil nach oben",
+      "navigateDownKeyAriaLabel": "Pfeil nach unten",
+      "closeText": "schließen",
+      "closeKeyAriaLabel": "Escape-Taste",
+      "searchByText": "Suche nach"
     },
     "noResultsScreen": {
-      "noResultsText": "No results for",
-      "suggestedQueryText": "Try searching for",
-      "reportMissingResultsText": "Believe this query should return results?",
-      "reportMissingResultsLinkText": "Let us know."
+      "noResultsText": "Kein Ergebnis für",
+      "suggestedQueryText": "Suchen Sie nach",
+      "reportMissingResultsText": "Glauben Sie, dass diese Abfrage Ergebnisse liefern sollte?",
+      "reportMissingResultsLinkText": "Informieren Sie uns."
     }
   }
 }

From c29c45978dfc983586c8c94d5a32543a858ce5a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:53 -0500
Subject: [PATCH 0622/1325] New translations docsearch.json (Russian)

---
 website/pages/ru/docsearch.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/docsearch.json b/website/pages/ru/docsearch.json
index e5b98f21e9c2..b81207b26a07 100644
--- a/website/pages/ru/docsearch.json
+++ b/website/pages/ru/docsearch.json
@@ -11,8 +11,8 @@
       "cancelButtonAriaLabel": "Отмена"
     },
     "startScreen": {
-      "recentSearchesTitle": "Недавние",
-      "noRecentSearchesText": "Нет недавних запросов",
+      "recentSearchesTitle": "Актуальный",
+      "noRecentSearchesText": "Нет актуальных запросов",
       "saveRecentSearchButtonTitle": "Сохранить результаты поиска",
       "removeRecentSearchButtonTitle": "Удалить этот запрос из истории запросов",
       "favoriteSearchesTitle": "Избранное",

From 0b27faebbbf8c5caf19c045817e2ea2d9c660e48 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:42:58 -0500
Subject: [PATCH 0623/1325] New translations docsearch.json (Swahili)

---
 website/pages/sw/docsearch.json | 42 +++++++++++++++++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 website/pages/sw/docsearch.json

diff --git a/website/pages/sw/docsearch.json b/website/pages/sw/docsearch.json
new file mode 100644
index 000000000000..8cfff967936d
--- /dev/null
+++ b/website/pages/sw/docsearch.json
@@ -0,0 +1,42 @@
+{
+  "button": {
+    "buttonText": "Search",
+    "buttonAriaLabel": "Search"
+  },
+  "modal": {
+    "searchBox": {
+      "resetButtonTitle": "Clear the query",
+      "resetButtonAriaLabel": "Clear the query",
+      "cancelButtonText": "Cancel",
+      "cancelButtonAriaLabel": "Cancel"
+    },
+    "startScreen": {
+      "recentSearchesTitle": "Recent",
+      "noRecentSearchesText": "No recent searches",
+      "saveRecentSearchButtonTitle": "Save this search",
+      "removeRecentSearchButtonTitle": "Remove this search from history",
+      "favoriteSearchesTitle": "Favorite",
+      "removeFavoriteSearchButtonTitle": "Remove this search from favorites"
+    },
+    "errorScreen": {
+      "titleText": "Unable to fetch results",
+      "helpText": "You might want to check your network connection."
+    },
+    "footer": {
+      "selectText": "to select",
+      "selectKeyAriaLabel": "Enter key",
+      "navigateText": "to navigate",
+      "navigateUpKeyAriaLabel": "Arrow up",
+      "navigateDownKeyAriaLabel": "Arrow down",
+      "closeText": "to close",
+      "closeKeyAriaLabel": "Escape key",
+      "searchByText": "Search by"
+    },
+    "noResultsScreen": {
+      "noResultsText": "No results for",
+      "suggestedQueryText": "Try searching for",
+      "reportMissingResultsText": "Believe this query should return results?",
+      "reportMissingResultsLinkText": "Let us know."
+    }
+  }
+}

From 7cb947a90a9c5d7bfc7e97ff550d019a350b1582 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:00 -0500
Subject: [PATCH 0624/1325] New translations cosmos.mdx (Romanian)

---
 website/pages/ro/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ro/cookbook/cosmos.mdx b/website/pages/ro/cookbook/cosmos.mdx
index a8c359b3098c..cd23a3742f86 100644
--- a/website/pages/ro/cookbook/cosmos.mdx
+++ b/website/pages/ro/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From f144cbb7f2df23632cbaf080417157dc898ce2f1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:01 -0500
Subject: [PATCH 0625/1325] New translations cosmos.mdx (Spanish)

---
 website/pages/es/cookbook/cosmos.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/es/cookbook/cosmos.mdx b/website/pages/es/cookbook/cosmos.mdx
index 5d931ce535aa..67d7021cf6d0 100644
--- a/website/pages/es/cookbook/cosmos.mdx
+++ b/website/pages/es/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Los controladores para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/).
 
-La indexación de Cosmos introduce tipos de datos específicos de Cosmos en la [AssemblyScript API](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -170,7 +170,7 @@ Cada tipo de handler viene con su propia estructura de datos que se pasa como ar
 - Los handlers de transacciones reciben el tipo `TransactionData`.
 - Los handlers de mensajes reciben el tipo `MessageData`.
 
-Como parte de `MessageData`, el message handler recibe un contexto de transacción, que contiene la información más importante sobre una transacción que abarca un mensaje. El contexto de transacción también está disponible en el tipo `EventData`, pero solo cuando el evento correspondiente está asociado con una transacción. Además, todos los controladores reciben una referencia a un bloque (`HeaderOnlyBlock`).
+Como parte de `MessageData`, el message handler recibe un contexto de transacción, que contiene la información más importante sobre una transacción que abarca un mensaje. El contexto de transacción también está disponible en el tipo ` EventData `, pero solo cuando el evento correspondiente está asociado con una transacción. Además, todos los controladores reciben una referencia a un bloque (` HeaderOnlyBlock `).
 
 Puedes encontrar una lista completa de los tipos para la integración Cosmos aquí [here](https://github.com/graphprotocol/graph-ts/blob/4c064a8118dff43b110de22c7756e5d47fcbc8df/chain/cosmos.ts).
 
@@ -203,7 +203,7 @@ Una vez que se haya creado su subgrafo, puede implementar su subgrafo usando el
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 1eed3ad7336f320d507ea61be906e572c3e41734 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:02 -0500
Subject: [PATCH 0626/1325] New translations cosmos.mdx (Arabic)

---
 website/pages/ar/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ar/cookbook/cosmos.mdx b/website/pages/ar/cookbook/cosmos.mdx
index 49a2e8c52602..15fbf0537bca 100644
--- a/website/pages/ar/cookbook/cosmos.mdx
+++ b/website/pages/ar/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ $ graph build
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 8ab6062b6ebd003880c4c118ee1ec67562db047a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:04 -0500
Subject: [PATCH 0627/1325] New translations cosmos.mdx (Czech)

---
 website/pages/cs/cookbook/cosmos.mdx | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/website/pages/cs/cookbook/cosmos.mdx b/website/pages/cs/cookbook/cosmos.mdx
index 5e67e4c3ff92..b604b8dabda0 100644
--- a/website/pages/cs/cookbook/cosmos.mdx
+++ b/website/pages/cs/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Definice schématu popisuje strukturu výsledné databáze podgrafů a vztahy me
 
 Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/).
 
-Indexování Cosmos zavádí datové typy specifické pro Cosmos do [AssemblyScript API](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ Po vytvoření podgrafu můžete podgraf nasadit pomocí příkazu `graph deploy
 Navštivte Studio podgrafů a vytvořte nový podgraf.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Místní uzel grafu (na základě výchozí config):**
@@ -226,32 +226,32 @@ Koncový bod GraphQL pro podgrafy Cosmos je určen definicí schématu se stáva
 
 #### Co je Cosmos Hub?
 
-The [Cosmos Hub blockchain](https://hub.cosmos.network/) is the first blockchain in the [Cosmos](https://cosmos.network/) ecosystem. You can visit the [official documentation](https://docs.cosmos.network/) for more information.
+[Cosmos Hub blockchain](https://hub.cosmos.network/) je první blockchain v ekosystému [Cosmos](https://cosmos.network/). Další informace naleznete v [oficiální dokumentaci](https://docs.cosmos.network/).
 
 #### Sítě
 
-Cosmos Hub mainnet is `cosmoshub-4`. Cosmos Hub current testnet is `theta-testnet-001`. <br/>Other Cosmos Hub networks, i.e. `cosmoshub-3`, are halted, therefore no data is provided for them.
+Hlavní síť Cosmos Hub je `cosmoshub-4`. Současná testovací síť Cosmos Hub je `theta-testnet-001`. <br/>Ostatní sítě Cosmos Hub, jako je `cosmoshub-3`, jsou zastavené, a proto pro ně nejsou poskytována žádná data.
 
 ### Osmosis
 
-> Osmosis support in Graph Node and on Subgraph Studio is in beta: please contact the graph team with any questions about building Osmosis subgraphs!
+> Podpora Osmosis v uzel grafua v Podgraph Studio je ve fázi beta: s případnými dotazy ohledně vytváření podgrafů Osmosis se obraťte na grafový tým!
 
 #### Co je osmosis?
 
-[Osmosis](https://osmosis.zone/) is a decentralized, cross-chain automated market maker (AMM) protocol built on top of the Cosmos SDK. It allows users to create custom liquidity pools and trade IBC-enabled tokens. You can visit the [official documentation](https://docs.osmosis.zone/) for more information.
+[Osmosis](https://osmosis.zone/) je decentralizovaný, cross-chain automatizovaný tvůrce trhu (AMM) protokol postavený na Cosmos SDK. Umožňuje uživatelům vytvářet vlastní fondy likvidity a obchodovat s tokeny povolenými IBC. Pro více informací můžete navštívit [oficiální dokumentaci](https://docs.osmosis.zone/).
 
 #### Sítě
 
-Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`.
+Osmosis mainnet je `osmosis-1`. Aktuální testnet Osmosis je `osmo-test-4`.
 
 ## Příklady podgrafů
 
-Here are some example subgraphs for reference:
+Zde je několik příkladů podgrafů:
 
-[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
+[Příklad blokového filtrování](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
 
-[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
+[Příklad odměn validátoru](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
 
-[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
+[Příklad delegování validátoru](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
 
-[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)
+[Příklad výměny tokenů Osmosis](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

From a6e35768dabebdfc6f2695298592a019616a4303 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:05 -0500
Subject: [PATCH 0628/1325] New translations cosmos.mdx (German)

---
 website/pages/de/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/de/cookbook/cosmos.mdx b/website/pages/de/cookbook/cosmos.mdx
index 6401744e7940..c37bc95e625e 100644
--- a/website/pages/de/cookbook/cosmos.mdx
+++ b/website/pages/de/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Die Handler für die Ereignisverarbeitung sind in [AssemblyScript](https://www.assemblyscript.org/) geschrieben.
 
-Die Cosmos-Indizierung führt Cosmos-spezifische Datentypen in die [AssemblyScript-API](/developing/graph-ts/api/) ein.
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From f81aed7f3c78547442ec76558b00a4bdf0304c85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:06 -0500
Subject: [PATCH 0629/1325] New translations cosmos.mdx (Italian)

---
 website/pages/it/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/it/cookbook/cosmos.mdx b/website/pages/it/cookbook/cosmos.mdx
index a8c359b3098c..cd23a3742f86 100644
--- a/website/pages/it/cookbook/cosmos.mdx
+++ b/website/pages/it/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 39336fda6c454277b11b8f95623bcd969319c9f6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:08 -0500
Subject: [PATCH 0630/1325] New translations cosmos.mdx (Japanese)

---
 website/pages/ja/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ja/cookbook/cosmos.mdx b/website/pages/ja/cookbook/cosmos.mdx
index dba17418bfc5..4ff9a970011d 100644
--- a/website/pages/ja/cookbook/cosmos.mdx
+++ b/website/pages/ja/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 イベントを処理するためのハンドラは[AssemblyScript](https://www.assemblyscript.org/)で書かれています。
 
-Cosmosインデックスでは、Cosmos特有のデータ型を[AssemblyScript API](/developing/graph-ts/api/)に導入しています。
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ $ graph build
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 81278a8cc7090d8969fe75985818327ed009518e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:09 -0500
Subject: [PATCH 0631/1325] New translations cosmos.mdx (Korean)

---
 website/pages/ko/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ko/cookbook/cosmos.mdx b/website/pages/ko/cookbook/cosmos.mdx
index a8c359b3098c..cd23a3742f86 100644
--- a/website/pages/ko/cookbook/cosmos.mdx
+++ b/website/pages/ko/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 58ef4eb1849754a07cbe4d6dee052a8a33132ad2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:10 -0500
Subject: [PATCH 0632/1325] New translations cosmos.mdx (Dutch)

---
 website/pages/nl/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/nl/cookbook/cosmos.mdx b/website/pages/nl/cookbook/cosmos.mdx
index a8c359b3098c..cd23a3742f86 100644
--- a/website/pages/nl/cookbook/cosmos.mdx
+++ b/website/pages/nl/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From ea70c18b656febb99fcd39a533c2bbf408c83d4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:11 -0500
Subject: [PATCH 0633/1325] New translations cosmos.mdx (Polish)

---
 website/pages/pl/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pl/cookbook/cosmos.mdx b/website/pages/pl/cookbook/cosmos.mdx
index a8c359b3098c..cd23a3742f86 100644
--- a/website/pages/pl/cookbook/cosmos.mdx
+++ b/website/pages/pl/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 7a0524ec005bd4630cf4b75c7b3e2ddacad07940 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:12 -0500
Subject: [PATCH 0634/1325] New translations cosmos.mdx (Portuguese)

---
 website/pages/pt/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/pt/cookbook/cosmos.mdx b/website/pages/pt/cookbook/cosmos.mdx
index 7402cf90be60..d98ffafe1a01 100644
--- a/website/pages/pt/cookbook/cosmos.mdx
+++ b/website/pages/pt/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ A definição do schema descreve a estrutura do banco de dados do subgraph resul
 
 Os handlers para o processamento de eventos são escritos em [AssemblyScript](https://www.assemblyscript.org/).
 
-A indexação do Cosmos introduz categorias de dados específicas ao Cosmos ao [API do AssemblyScript](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ Quando o seu subgraph estiver pronto, lance o seu subgraph com o comando de CLI
 Crie um novo subgraph no Subgraph Studio.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Graph Node local (baseado na configuração padrão):**

From 2508191c0752403e84ce48c7756cbd4a61faa4f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:13 -0500
Subject: [PATCH 0635/1325] New translations cosmos.mdx (Swedish)

---
 website/pages/sv/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/sv/cookbook/cosmos.mdx b/website/pages/sv/cookbook/cosmos.mdx
index 6e86c2bfbe92..f1ae3d262aa3 100644
--- a/website/pages/sv/cookbook/cosmos.mdx
+++ b/website/pages/sv/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/).
 
-Cosmos indexering introducerar Cosmos specifika datatyper till [AssemblyScript API](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ När din subgraf har skapats kan du distribuera din subgraf genom att använda `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 8b3c99e798f5641b625d9c33d20d786aac07a889 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:15 -0500
Subject: [PATCH 0636/1325] New translations cosmos.mdx (Turkish)

---
 website/pages/tr/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/tr/cookbook/cosmos.mdx b/website/pages/tr/cookbook/cosmos.mdx
index f43dce3b1a60..e1064c19faf7 100644
--- a/website/pages/tr/cookbook/cosmos.mdx
+++ b/website/pages/tr/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır.
 
-Cosmos indeksleme, Cosmos'a özgü veri türlerini [AssemblyScript API](/developing/graph-ts/api/) ile tanıştırır.
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ Subgraph'ınız oluşturulduktan sonra, `graph deploy` CLI komutunu kullanarak s
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 5efba6cc89faf108018da658ffb4b132208623ee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:16 -0500
Subject: [PATCH 0637/1325] New translations cosmos.mdx (Ukrainian)

---
 website/pages/uk/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/uk/cookbook/cosmos.mdx b/website/pages/uk/cookbook/cosmos.mdx
index 11675cb32a7a..979de8d0a4cc 100644
--- a/website/pages/uk/cookbook/cosmos.mdx
+++ b/website/pages/uk/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 Обробники для виконання подій написані на мові [AssemblyScript](https://www.assemblyscript.org/).
 
-Індексація Cosmos вводить специфічні для Cosmos типи даних до [AssemblyScript API](/developing/graph-ts/api/).
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 74180e5ebc2d44972b109e072354477dc7c4c620 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:17 -0500
Subject: [PATCH 0638/1325] New translations cosmos.mdx (Chinese Simplified)

---
 website/pages/zh/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/zh/cookbook/cosmos.mdx b/website/pages/zh/cookbook/cosmos.mdx
index d14d93133b4e..c5ea0c2b44e6 100644
--- a/website/pages/zh/cookbook/cosmos.mdx
+++ b/website/pages/zh/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。
 
-Cosmos 索引向 [AssemblyScriptAPI ](/developing/graph-ts/api/)引入了特定于 Cosmos 的数据类型。
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ $ graph build
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 6ccb036ef33865481c1a57b978e6142707f4835b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:18 -0500
Subject: [PATCH 0639/1325] New translations cosmos.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/cosmos.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ur/cookbook/cosmos.mdx b/website/pages/ur/cookbook/cosmos.mdx
index cf89dd1aa141..19ef50e2ca0d 100644
--- a/website/pages/ur/cookbook/cosmos.mdx
+++ b/website/pages/ur/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں.
 
-کوزموس انڈیکسنگ [اسمبلی اسکرپٹ API](/developing/graph-ts/api/) میں کوزموس-مخصوص ڈیٹا کی اقسام کو متعارف کراتی ہے.
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -165,7 +165,7 @@ class Any {
 
 ہر ہینڈلر کی قسم اس کے اپنے ڈیٹا ڈھانچے کے ساتھ آتی ہے جو میپنگ فنکشن کی دلیل کے طور پر پاس کی جاتی ہے.
 
-- بلاک ہینڈلرز کو `Block` قسم موصول ہوتی ہے.
+- بلاک ہینڈلرز کو ` Block ` قسم موصول ہوتی ہے.
 - ایونٹ ہینڈلرز کو `EventData` قسم موصول ہوتی ہے.
 - ٹرانزیکشن ہینڈلرز کو `TransactionData` قسم موصول ہوتی ہے.
 - میسج ہینڈلرز کو `MessageData` قسم موصول ہوتی ہے.
@@ -203,7 +203,7 @@ $ graph build
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 2a1073617eea5dc33cce15aa962cf583fc984e71 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:19 -0500
Subject: [PATCH 0640/1325] New translations cosmos.mdx (Vietnamese)

---
 website/pages/vi/cookbook/cosmos.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/vi/cookbook/cosmos.mdx b/website/pages/vi/cookbook/cosmos.mdx
index 7be4dd039524..38b983935e9a 100644
--- a/website/pages/vi/cookbook/cosmos.mdx
+++ b/website/pages/vi/cookbook/cosmos.mdx
@@ -203,7 +203,7 @@ Once your subgraph has been created, you can deploy your subgraph by using the `
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From de11c619357bd3258b70f43c042627e063aa3f35 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:20 -0500
Subject: [PATCH 0641/1325] New translations cosmos.mdx (Marathi)

---
 website/pages/mr/cookbook/cosmos.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/mr/cookbook/cosmos.mdx b/website/pages/mr/cookbook/cosmos.mdx
index 687d4f5a020c..80243dc25ebd 100644
--- a/website/pages/mr/cookbook/cosmos.mdx
+++ b/website/pages/mr/cookbook/cosmos.mdx
@@ -85,7 +85,7 @@ Schema definition describes the structure of the resulting subgraph database and
 
 इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत.
 
-कॉसमॉस अनुक्रमणिका [AssemblyScript API](/developing/graph-ts/api/) मध्ये कॉसमॉस-विशिष्ट डेटा प्रकारांचा परिचय देते.
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -203,7 +203,7 @@ $ आलेख बिल्ड
 Visit the Subgraph Studio to create a new subgraph.
 
 ```bash
-graph deploy --studio subgraph-name
+graph deploy subgraph-name
 ```
 
 **Local Graph Node (based on default configuration):**

From 47e6bdcd76e6a0226918c64dabc6d55f36d119d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:21 -0500
Subject: [PATCH 0642/1325] New translations cosmos.mdx (Swahili)

---
 website/pages/sw/cookbook/cosmos.mdx | 257 +++++++++++++++++++++++++++
 1 file changed, 257 insertions(+)
 create mode 100644 website/pages/sw/cookbook/cosmos.mdx

diff --git a/website/pages/sw/cookbook/cosmos.mdx b/website/pages/sw/cookbook/cosmos.mdx
new file mode 100644
index 000000000000..cd23a3742f86
--- /dev/null
+++ b/website/pages/sw/cookbook/cosmos.mdx
@@ -0,0 +1,257 @@
+---
+title: Building Subgraphs on Cosmos
+---
+
+This guide is an introduction on building subgraphs indexing [Cosmos](https://cosmos.network/) based blockchains.
+
+## What are Cosmos subgraphs?
+
+The Graph allows developers to process blockchain events and make the resulting data easily available via an open GraphQL API, known as a subgraph. [Graph Node](https://github.com/graphprotocol/graph-node) is now able to process Cosmos events, which means Cosmos developers can now build subgraphs to easily index on-chain events.
+
+There are four types of handlers supported in Cosmos subgraphs:
+
+- **Block handlers** run whenever a new block is appended to the chain.
+- **Event handlers** run when a specific event is emitted.
+- **Transaction handlers** run when a transaction occurs.
+- **Message handlers** run when a specific message occurs.
+
+Based on the [official Cosmos documentation](https://docs.cosmos.network/):
+
+> [Events](https://docs.cosmos.network/main/learn/advanced/events) are objects that contain information about the execution of the application. They are mainly used by service providers like block explorers and wallets to track the execution of various messages and index transactions.
+
+> [Transactions](https://docs.cosmos.network/main/learn/advanced/transactions) are objects created by end-users to trigger state changes in the application.
+
+> [Messages](https://docs.cosmos.network/main/learn/advanced/transactions#messages) are module-specific objects that trigger state transitions within the scope of the module they belong to.
+
+Even though all data can be accessed with a block handler, other handlers enable subgraph developers to process data in a much more granular way.
+
+## Building a Cosmos subgraph
+
+### Subgraph Dependencies
+
+[graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli) is a CLI tool to build and deploy subgraphs, version `>=0.30.0` is required in order to work with Cosmos subgraphs.
+
+[graph-ts](https://github.com/graphprotocol/graph-tooling/tree/main/packages/ts) is a library of subgraph-specific types, version `>=0.27.0` is required in order to work with Cosmos subgraphs.
+
+### Subgraph Main Components
+
+There are three key parts when it comes to defining a subgraph:
+
+**subgraph.yaml**: a YAML file containing the subgraph manifest, which identifies which events to track and how to process them.
+
+**schema.graphql**: a GraphQL schema that defines what data is stored for your subgraph, and how to query it via GraphQL.
+
+**AssemblyScript Mappings**: [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) code that translates from blockchain data to the entities defined in your schema.
+
+### Subgraph Manifest Definition
+
+The subgraph manifest (`subgraph.yaml`) identifies the data sources for the subgraph, the triggers of interest, and the functions (`handlers`) that should be run in response to those triggers. See below for an example subgraph manifest for a Cosmos subgraph:
+
+```yaml
+specVersion: 0.0.5
+description: Cosmos Subgraph Example
+schema:
+  file: ./schema.graphql # link to the schema file
+dataSources:
+  - kind: cosmos
+    name: CosmosHub
+    network: cosmoshub-4 # This will change for each cosmos-based blockchain. In this case, the example uses the Cosmos Hub mainnet.
+    source:
+      startBlock: 0 # Required for Cosmos, set this to 0 to start indexing from chain genesis
+    mapping:
+      apiVersion: 0.0.7
+      language: wasm/assemblyscript
+      blockHandlers:
+        - handler: handleNewBlock # the function name in the mapping file
+      eventHandlers:
+        - event: rewards # the type of the event that will be handled
+          handler: handleReward # the function name in the mapping file
+      transactionHandlers:
+        - handler: handleTransaction # the function name in the mapping file
+      messageHandlers:
+        - message: /cosmos.staking.v1beta1.MsgDelegate # the type of a message
+          handler: handleMsgDelegate # the function name in the mapping file
+      file: ./src/mapping.ts # link to the file with the Assemblyscript mappings
+```
+
+- Cosmos subgraphs introduce a new `kind` of data source (`cosmos`).
+- The `network` should correspond to a chain in the Cosmos ecosystem. In the example, the Cosmos Hub mainnet is used.
+
+### Schema Definition
+
+Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema).
+
+### AssemblyScript Mappings
+
+The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/).
+
+Cosmos indexing introduces Cosmos-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
+
+```tsx
+class Block {
+  header: Header
+  evidence: EvidenceList
+  resultBeginBlock: ResponseBeginBlock
+  resultEndBlock: ResponseEndBlock
+  transactions: Array<TxResult>
+  validatorUpdates: Array<Validator>
+}
+
+class EventData {
+  event: Event
+  block: HeaderOnlyBlock
+  tx: TransactionContext
+}
+
+class TransactionData {
+  tx: TxResult
+  block: HeaderOnlyBlock
+}
+
+class MessageData {
+  message: Any
+  block: HeaderOnlyBlock
+  tx: TransactionContext
+}
+
+class TransactionContext {
+  hash: Bytes
+  index: u32
+  code: u32
+  gasWanted: i64
+  gasUsed: i64
+}
+
+class HeaderOnlyBlock {
+  header: Header
+}
+
+class Header {
+  version: Consensus
+  chainId: string
+  height: u64
+  time: Timestamp
+  lastBlockId: BlockID
+  lastCommitHash: Bytes
+  dataHash: Bytes
+  validatorsHash: Bytes
+  nextValidatorsHash: Bytes
+  consensusHash: Bytes
+  appHash: Bytes
+  lastResultsHash: Bytes
+  evidenceHash: Bytes
+  proposerAddress: Bytes
+  hash: Bytes
+}
+
+class TxResult {
+  height: u64
+  index: u32
+  tx: Tx
+  result: ResponseDeliverTx
+  hash: Bytes
+}
+
+class Event {
+  eventType: string
+  attributes: Array<EventAttribute>
+}
+
+class Any {
+  typeUrl: string
+  value: Bytes
+}
+```
+
+Each handler type comes with its own data structure that is passed as an argument to a mapping function.
+
+- Block handlers receive the `Block` type.
+- Event handlers receive the `EventData` type.
+- Transaction handlers receive the `TransactionData` type.
+- Message handlers receive the `MessageData` type.
+
+As a part of `MessageData` the message handler receives a transaction context, which contains the most important information about a transaction that encompasses a message. The transaction context is also available in the `EventData` type, but only when the corresponding event is associated with a transaction. Additionally, all handlers receive a reference to a block (`HeaderOnlyBlock`).
+
+You can find the full list of types for the Cosmos integration [here](https://github.com/graphprotocol/graph-ts/blob/4c064a8118dff43b110de22c7756e5d47fcbc8df/chain/cosmos.ts).
+
+### Message decoding
+
+It's important to note that Cosmos messages are chain-specific and they are passed to a subgraph in the form of a serialized [Protocol Buffers](https://protobuf.dev/) payload. As a result, the message data needs to be decoded in a mapping function before it can be processed.
+
+An example of how to decode message data in a subgraph can be found [here](https://github.com/graphprotocol/graph-tooling/blob/main/examples/cosmos-validator-delegations/src/decoding.ts).
+
+## Creating and building a Cosmos subgraph
+
+The first step before starting to write the subgraph mappings is to generate the type bindings based on the entities that have been defined in the subgraph schema file (`schema.graphql`). This will allow the mapping functions to create new objects of those types and save them to the store. This is done by using the `codegen` CLI command:
+
+```bash
+$ graph codegen
+```
+
+Once the mappings are ready, the subgraph needs to be built. This step will highlight any errors the manifest or the mappings might have. A subgraph needs to build successfully in order to be deployed to the Graph Node. It can be done using the `build` CLI command:
+
+```bash
+$ graph build
+```
+
+## Deploying a Cosmos subgraph
+
+Once your subgraph has been created, you can deploy your subgraph by using the `graph deploy` CLI command:
+
+**Subgraph Studio**
+
+Visit the Subgraph Studio to create a new subgraph.
+
+```bash
+graph deploy subgraph-name
+```
+
+**Local Graph Node (based on default configuration):**
+
+```bash
+graph create subgraph-name --node http://localhost:8020
+```
+
+```bash
+graph deploy subgraph-name --node http://localhost:8020/ --ipfs http://localhost:5001
+```
+
+## Querying a Cosmos subgraph
+
+The GraphQL endpoint for Cosmos subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information.
+
+## Supported Cosmos Blockchains
+
+### Cosmos Hub
+
+#### What is Cosmos Hub?
+
+The [Cosmos Hub blockchain](https://hub.cosmos.network/) is the first blockchain in the [Cosmos](https://cosmos.network/) ecosystem. You can visit the [official documentation](https://docs.cosmos.network/) for more information.
+
+#### Networks
+
+Cosmos Hub mainnet is `cosmoshub-4`. Cosmos Hub current testnet is `theta-testnet-001`. <br/>Other Cosmos Hub networks, i.e. `cosmoshub-3`, are halted, therefore no data is provided for them.
+
+### Osmosis
+
+> Osmosis support in Graph Node and on Subgraph Studio is in beta: please contact the graph team with any questions about building Osmosis subgraphs!
+
+#### What is Osmosis?
+
+[Osmosis](https://osmosis.zone/) is a decentralized, cross-chain automated market maker (AMM) protocol built on top of the Cosmos SDK. It allows users to create custom liquidity pools and trade IBC-enabled tokens. You can visit the [official documentation](https://docs.osmosis.zone/) for more information.
+
+#### Networks
+
+Osmosis mainnet is `osmosis-1`. Osmosis current testnet is `osmo-test-4`.
+
+## Example Subgraphs
+
+Here are some example subgraphs for reference:
+
+[Block Filtering Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-block-filtering)
+
+[Validator Rewards Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-rewards)
+
+[Validator Delegations Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-validator-delegations)
+
+[Osmosis Token Swaps Example](https://github.com/graphprotocol/graph-tooling/tree/main/examples/cosmos-osmosis-token-swaps)

From 3c702f54d9546addf2cbbb2e4cc1860ae920b640 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:22 -0500
Subject: [PATCH 0643/1325] New translations supported-networks.mdx (Romanian)

---
 website/pages/ro/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ro/developing/supported-networks.mdx b/website/pages/ro/developing/supported-networks.mdx
index 1e0352c60615..b36c202d793d 100644
--- a/website/pages/ro/developing/supported-networks.mdx
+++ b/website/pages/ro/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From fb362f88f71ed5cbd0329d96ca51bd1fce070c8c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:23 -0500
Subject: [PATCH 0644/1325] New translations supported-networks.mdx (French)

---
 .../pages/fr/developing/supported-networks.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/fr/developing/supported-networks.mdx b/website/pages/fr/developing/supported-networks.mdx
index b45431b63a2f..95f3b3c65b06 100644
--- a/website/pages/fr/developing/supported-networks.mdx
+++ b/website/pages/fr/developing/supported-networks.mdx
@@ -5,20 +5,20 @@ title: Réseaux supportés
 import { getStaticPropsForSupportedNetworks } from '@/src/buildGetStaticProps'
 import { SupportedNetworksTable } from '@/src/supportedNetworks'
 
-export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
+export const getStaticProps = getStaticPropsForSupportedNetworks(__nomDuFichier)
 
 <SupportedNetworksTable networks={props.networks} />
 
-\* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).  
-\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
+\* Support réseau de base fourni par l' [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).  
+\*\* Intégration avec Graph Node : `evm`, `near`, `cosmos`, `osmosis` et `ar` sont nativement pris en charge dans Graph Node. Les blockchains compatibles avec Firehose et Substreams peuvent tirer parti de l'intégration généralisée des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs) (ceci inclut les réseaux `evm` et `near` ). &#8288;<sup>†</sup> Prend en charge le déploiement des [subgraphs alimentés par Substreams](/cookbook/substreams-powered-subgraphs).
 
-- Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
-- If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
+- Subgraph Studio repose sur la stabilité et la fiabilité des technologies sous-jacentes, comme les endpoints JSON-RPC, Firehose et Substreams.
+- Les subgraphs indexant Gnosis Chain peuvent désormais être déployés avec l'identifiant de réseau `gnosis`.
+- Si un subgraph a été publié via la CLI et repris par un Indexer, il pourrait techniquement être interrogé même sans support, et des efforts sont en cours pour simplifier davantage l'intégration de nouveaux réseaux.
 - Pour une liste complète des fonctionnalités prises en charge par le réseau décentralisé, voir [cette page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 
-## Running Graph Node locally
+## Exécution de Graph Node en local
 
-If your preferred network isn't supported on The Graph's decentralized network, you can run your own [Graph Node](https://github.com/graphprotocol/graph-node) to index any EVM-compatible network. Make sure that the [version](https://github.com/graphprotocol/graph-node/releases) you are using supports the network and you have the needed configuration.
+Si votre réseau préféré n'est pas pris en charge sur le réseau décentralisé de The Graph, vous pouvez exécuter votre propre [Graph Node](https://github.com/graphprotocol/graph-node) pour indexer n'importe quel réseau compatible EVM. Assurez-vous que la [version](https://github.com/graphprotocol/graph-node/releases) que vous utilisez prend en charge le réseau et que vous avez la configuration nécessaire.
 
-Graph Node can also index other protocols, via a Firehose integration. Firehose integrations have been created for NEAR, Arweave and Cosmos-based networks. Additionally, Graph Node can support Substreams-powered subgraphs for any network with Substreams support.
+Graph Node peut également indexer d'autres protocoles via une intégration Firehose. Des intégrations Firehose ont été créées pour NEAR, Arweave et les réseaux basés sur Cosmos. De plus, Graph Node peut prendre en charge les subgraphs alimentés par Substreams pour tout réseau prenant en charge Substreams.

From 1c28441e4e7a5780fc8382070748397f77a562e6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:24 -0500
Subject: [PATCH 0645/1325] New translations supported-networks.mdx (Spanish)

---
 website/pages/es/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/es/developing/supported-networks.mdx b/website/pages/es/developing/supported-networks.mdx
index dc663b17b3f1..86c379d637f5 100644
--- a/website/pages/es/developing/supported-networks.mdx
+++ b/website/pages/es/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From ace843f7677aa22b7ea084d94fb563a0659ca999 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:25 -0500
Subject: [PATCH 0646/1325] New translations supported-networks.mdx (Arabic)

---
 website/pages/ar/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ar/developing/supported-networks.mdx b/website/pages/ar/developing/supported-networks.mdx
index 96e737b0d743..c2e7677ae4fb 100644
--- a/website/pages/ar/developing/supported-networks.mdx
+++ b/website/pages/ar/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From c777e2764e5baece72f6f23398587d9d54fef1c6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:26 -0500
Subject: [PATCH 0647/1325] New translations supported-networks.mdx (Czech)

---
 website/pages/cs/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/cs/developing/supported-networks.mdx b/website/pages/cs/developing/supported-networks.mdx
index b9addda0b59e..cc2b778d6cad 100644
--- a/website/pages/cs/developing/supported-networks.mdx
+++ b/website/pages/cs/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - Úplný seznam funkcí podporovaných v decentralizované síti najdete na [této stránce](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 0b18ff353ac1ee9511bd009a24f3e7a351a60164 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:28 -0500
Subject: [PATCH 0648/1325] New translations supported-networks.mdx (German)

---
 website/pages/de/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/de/developing/supported-networks.mdx b/website/pages/de/developing/supported-networks.mdx
index 7c2d8d858261..797202065e99 100644
--- a/website/pages/de/developing/supported-networks.mdx
+++ b/website/pages/de/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 752b27e2407f28d5750cb944a1831fb18f71a8a8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:29 -0500
Subject: [PATCH 0649/1325] New translations supported-networks.mdx (Italian)

---
 website/pages/it/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/it/developing/supported-networks.mdx b/website/pages/it/developing/supported-networks.mdx
index 7c2d8d858261..797202065e99 100644
--- a/website/pages/it/developing/supported-networks.mdx
+++ b/website/pages/it/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From e1edffdb6444fb13a3a17cf04cb20e559bef37e4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:30 -0500
Subject: [PATCH 0650/1325] New translations supported-networks.mdx (Japanese)

---
 website/pages/ja/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ja/developing/supported-networks.mdx b/website/pages/ja/developing/supported-networks.mdx
index d0d2749a2fb5..75feee5305b5 100644
--- a/website/pages/ja/developing/supported-networks.mdx
+++ b/website/pages/ja/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - 分散型ネットワークでサポートされている機能の完全なリストについては、[このページ](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md)を参照してください。
 

From 37426a7c160d493cbfbaa259d5c024408a968d45 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:31 -0500
Subject: [PATCH 0651/1325] New translations supported-networks.mdx (Korean)

---
 website/pages/ko/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ko/developing/supported-networks.mdx b/website/pages/ko/developing/supported-networks.mdx
index 7c2d8d858261..797202065e99 100644
--- a/website/pages/ko/developing/supported-networks.mdx
+++ b/website/pages/ko/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 8ad405a428f6533d3d7c6266a6d00a630dd0af93 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:32 -0500
Subject: [PATCH 0652/1325] New translations supported-networks.mdx (Dutch)

---
 website/pages/nl/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/nl/developing/supported-networks.mdx b/website/pages/nl/developing/supported-networks.mdx
index bed07fc2da1c..bd39f933133c 100644
--- a/website/pages/nl/developing/supported-networks.mdx
+++ b/website/pages/nl/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 6db7204207a677a27a3e51c892b161c141bb49ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:33 -0500
Subject: [PATCH 0653/1325] New translations supported-networks.mdx (Polish)

---
 website/pages/pl/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pl/developing/supported-networks.mdx b/website/pages/pl/developing/supported-networks.mdx
index 6a85c1a2997b..6a9a3d7332fe 100644
--- a/website/pages/pl/developing/supported-networks.mdx
+++ b/website/pages/pl/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 256398a8a8260e39a37908b14e710fbfa00f77ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:34 -0500
Subject: [PATCH 0654/1325] New translations supported-networks.mdx
 (Portuguese)

---
 website/pages/pt/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pt/developing/supported-networks.mdx b/website/pages/pt/developing/supported-networks.mdx
index 2e750d53de96..7a1a1d46a772 100644
--- a/website/pages/pt/developing/supported-networks.mdx
+++ b/website/pages/pt/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integração com o Graph Node: `evm`, `near`, `cosmos`, `osmosis` e `ar` têm apoio nativo a handlers e tipos no Graph Node. Chains compatíveis com Firehose e Substreams podem utilizar a integração generalizada de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs) (isto inclui as redes `evm` e `near`). &#8288;<sup>†</sup> apoia o lançamento de [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs).
 
 - O Subgraph Studio depende da estabilidade e da confiança das tecnologias subjacentes, por exemplo, JSON-RPC, Firehose e endpoints dos Substreams.
-- Subgraphs que indexam a Gnosis Chain podem agora ser lançados com o identificador de rede `gnosis`. O `xdai` ainda é apoiado para subgraphs já existentes no serviço hospedado.
+- Subgraphs que indexam a Gnosis Chain agora podem ser lançados com a identificadora de rede `gnosis`.
 - Se um subgraph foi publicado via a CLI e visto por um Indexador, ele pode tecnicamente ser consultado mesmo sem apoio, e esforços estão a ser feitos para simplificar ainda mais a integração de novas redes.
 - Para uma lista completa de recursos apoiados na rede descentralizada, veja [esta página](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 8b6c5011e34c32987b4aaef0987f18e3aa3072ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:35 -0500
Subject: [PATCH 0655/1325] New translations supported-networks.mdx (Russian)

---
 .../pages/ru/developing/supported-networks.mdx   | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/ru/developing/supported-networks.mdx b/website/pages/ru/developing/supported-networks.mdx
index beda4b4094c2..4efe3873f80f 100644
--- a/website/pages/ru/developing/supported-networks.mdx
+++ b/website/pages/ru/developing/supported-networks.mdx
@@ -9,16 +9,16 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 
 <SupportedNetworksTable networks={props.networks} />
 
-\* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).  
-\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
+\* Базовая поддержка сети обеспечивается [индексатором обновления](https://thegraph.com/blog/upgrade-indexer/).  
+\*\* Интеграция с Graph Node: `evm`, `near`, `cosmos`, `osmosis` и `ar` имеют собственный обработчик и поддержку типов в Graph Node. Чейны, совместимые с Firehose и Substreams, могут использовать обобщенную интеграцию [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs) (включая сети `evm` и `near`). &#8288;<sup>†</sup> Поддерживает развертывание [субграфов на основе Substreams](/cookbook/substreams-powered-subgraphs).
 
-- Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
-- If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
+- Subgraph Studio полагается на стабильность и надежность базовых технологий, например, таких, как JSON-RPC, Firehose и конечных точек Substreams.
+- Субграфы, индексирующие Gnosis Chain, теперь могут быть развернуты с помощью сетевого идентификатора `gnosis`.
+- Если субграф был опубликован через CLI и выбран индексатором, технически его можно было бы запросить даже без поддержки, и в настоящее время предпринимаются усилия для упрощения интеграции новых сетей.
 - Полный список функций, поддерживаемых в децентрализованной сети, можно найти на [этой странице](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 
-## Running Graph Node locally
+## Локальный запуск Graph Node
 
-If your preferred network isn't supported on The Graph's decentralized network, you can run your own [Graph Node](https://github.com/graphprotocol/graph-node) to index any EVM-compatible network. Make sure that the [version](https://github.com/graphprotocol/graph-node/releases) you are using supports the network and you have the needed configuration.
+Если предпочитаемая Вами сеть не поддерживается в децентрализованной сети The Graph, Вы можете запустить свой собственный [Graph Node](https://github.com/graphprotocol/graph-node) для индексирования любой сети, совместимой с EVM. Убедитесь, что используемая Вами [версия](https://github.com/graphprotocol/graph-node/releases) поддерживает сеть, и у Вас есть необходимая конфигурация.
 
-Graph Node can also index other protocols, via a Firehose integration. Firehose integrations have been created for NEAR, Arweave and Cosmos-based networks. Additionally, Graph Node can support Substreams-powered subgraphs for any network with Substreams support.
+Graph Node также может индексировать другие протоколы через интеграцию с Firehose. Интеграции Firehose созданы для сетей на базе NEAR, Arweave и Cosmos. Кроме того, Graph Node может поддерживать субграфы на основе Substreams для любой сети с поддержкой Substreams.

From ae6fef788745b10246fe0f7593e9b8d3207a217c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:36 -0500
Subject: [PATCH 0656/1325] New translations supported-networks.mdx (Swedish)

---
 website/pages/sv/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/sv/developing/supported-networks.mdx b/website/pages/sv/developing/supported-networks.mdx
index 47341ff9f563..c8bf3ab7a332 100644
--- a/website/pages/sv/developing/supported-networks.mdx
+++ b/website/pages/sv/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - För en fullständig lista över vilka funktioner som stöds på det decentraliserade nätverket, se [den här sidan](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From f967953368a2ddce0842d4153eb6107415878dd6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:37 -0500
Subject: [PATCH 0657/1325] New translations supported-networks.mdx (Ukrainian)

---
 website/pages/uk/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/uk/developing/supported-networks.mdx b/website/pages/uk/developing/supported-networks.mdx
index b1654dee17b2..6a1805deefee 100644
--- a/website/pages/uk/developing/supported-networks.mdx
+++ b/website/pages/uk/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 88cbcc6e1d854976b6b7f78525edbf749cf5209c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:39 -0500
Subject: [PATCH 0658/1325] New translations supported-networks.mdx (Chinese
 Simplified)

---
 website/pages/zh/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/developing/supported-networks.mdx b/website/pages/zh/developing/supported-networks.mdx
index 1d19cb36097b..487d607586af 100644
--- a/website/pages/zh/developing/supported-networks.mdx
+++ b/website/pages/zh/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - 有关去中心化网络支持哪些功能的完整列表，请参阅[本页](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md)。
 

From 75fb93d1f9942ca4d74ea33928098e34e683a318 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:40 -0500
Subject: [PATCH 0659/1325] New translations supported-networks.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ur/developing/supported-networks.mdx b/website/pages/ur/developing/supported-networks.mdx
index cb315e14f536..bfa66b78c21b 100644
--- a/website/pages/ur/developing/supported-networks.mdx
+++ b/website/pages/ur/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From e467c2861f8a8ec7dd4a068b31f41f6b1b89457e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:41 -0500
Subject: [PATCH 0660/1325] New translations supported-networks.mdx
 (Vietnamese)

---
 website/pages/vi/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/vi/developing/supported-networks.mdx b/website/pages/vi/developing/supported-networks.mdx
index 2782a2c04b10..2a9585d3213f 100644
--- a/website/pages/vi/developing/supported-networks.mdx
+++ b/website/pages/vi/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 51a62a209eb9bc0d49bea5e4121f9ad5ac5ed474 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:42 -0500
Subject: [PATCH 0661/1325] New translations supported-networks.mdx (Marathi)

---
 website/pages/mr/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/mr/developing/supported-networks.mdx b/website/pages/mr/developing/supported-networks.mdx
index 7c2d8d858261..797202065e99 100644
--- a/website/pages/mr/developing/supported-networks.mdx
+++ b/website/pages/mr/developing/supported-networks.mdx
@@ -13,7 +13,7 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
 - Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From 8911be574091e1b01fc116d85f77701395448c58 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:43 -0500
Subject: [PATCH 0662/1325] New translations supported-networks.mdx (Hindi)

---
 website/pages/hi/developing/supported-networks.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/hi/developing/supported-networks.mdx b/website/pages/hi/developing/supported-networks.mdx
index 7c2d8d858261..1f54bddd05cd 100644
--- a/website/pages/hi/developing/supported-networks.mdx
+++ b/website/pages/hi/developing/supported-networks.mdx
@@ -1,5 +1,5 @@
 ---
-title: Supported Networks
+title: समर्थित नेटवर्क
 ---
 
 import { getStaticPropsForSupportedNetworks } from '@/src/buildGetStaticProps'
@@ -12,8 +12,8 @@ export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 \* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).  
 \*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
 
-- Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
-- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier. `xdai` is still supported for existing hosted service subgraphs.
+- सबग्राफ स्टूडियो निर्भर करता है अंतर्निहित प्रौद्योगिकियों की स्थिरता और विश्वसनीयता पर, जैसे JSON-RPC, फायरहोस और सबस्ट्रीम्स एंडपॉइंट्स।
+- Gnosis Chain पर सबग्राफ इंडेक्सिंग को अब `gnosis` नेटवर्क पहचानकर्ता (network identifier) के साथ डिप्लॉय किया जा सकता है।
 - If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
 - For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 

From ef390d21f5287b8a64ad21eee3d9c2266d82c807 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:44 -0500
Subject: [PATCH 0663/1325] New translations supported-networks.mdx (Swahili)

---
 .../sw/developing/supported-networks.mdx      | 24 +++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 website/pages/sw/developing/supported-networks.mdx

diff --git a/website/pages/sw/developing/supported-networks.mdx b/website/pages/sw/developing/supported-networks.mdx
new file mode 100644
index 000000000000..797202065e99
--- /dev/null
+++ b/website/pages/sw/developing/supported-networks.mdx
@@ -0,0 +1,24 @@
+---
+title: Supported Networks
+---
+
+import { getStaticPropsForSupportedNetworks } from '@/src/buildGetStaticProps'
+import { SupportedNetworksTable } from '@/src/supportedNetworks'
+
+export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
+
+<SupportedNetworksTable networks={props.networks} />
+
+\* Baseline network support provided by the [upgrade Indexer](https://thegraph.com/blog/upgrade-indexer/).  
+\*\* Integration with Graph Node: `evm`, `near`, `cosmos`, `osmosis` and `ar` have native handler and type support in Graph Node. Chains which are Firehose- and Substreams-compatible can leverage the generalised [Substreams-powered subgraph](/cookbook/substreams-powered-subgraphs) integration (this includes `evm` and `near` networks). &#8288;<sup>†</sup> Supports deployment of [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs).
+
+- Subgraph Studio relies on the stability and reliability of the underlying technologies, for example JSON-RPC, Firehose and Substreams endpoints.
+- Subgraphs indexing Gnosis Chain can now be deployed with the `gnosis` network identifier.
+- If a subgraph was published via the CLI and picked up by an Indexer, it could technically be queried even without support, and efforts are underway to further streamline integration of new networks.
+- For a full list of which features are supported on the decentralized network, see [this page](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
+
+## Running Graph Node locally
+
+If your preferred network isn't supported on The Graph's decentralized network, you can run your own [Graph Node](https://github.com/graphprotocol/graph-node) to index any EVM-compatible network. Make sure that the [version](https://github.com/graphprotocol/graph-node/releases) you are using supports the network and you have the needed configuration.
+
+Graph Node can also index other protocols, via a Firehose integration. Firehose integrations have been created for NEAR, Arweave and Cosmos-based networks. Additionally, Graph Node can support Substreams-powered subgraphs for any network with Substreams support.

From 4169bdf66c2f40a6a3b728e7d5bd1d36e0250008 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:45 -0500
Subject: [PATCH 0664/1325] New translations managing-api-keys.mdx (Romanian)

---
 .../pages/ro/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/ro/querying/managing-api-keys.mdx b/website/pages/ro/querying/managing-api-keys.mdx
index 155710dd6849..f7aff33ea926 100644
--- a/website/pages/ro/querying/managing-api-keys.mdx
+++ b/website/pages/ro/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Overview
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From 7482235bfb4e613ba7be986188e5f543286ad02b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:46 -0500
Subject: [PATCH 0665/1325] New translations managing-api-keys.mdx (French)

---
 .../pages/fr/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/fr/querying/managing-api-keys.mdx b/website/pages/fr/querying/managing-api-keys.mdx
index 44255bdfcfa7..d44a65306dc1 100644
--- a/website/pages/fr/querying/managing-api-keys.mdx
+++ b/website/pages/fr/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Gérer vos clés API
 ---
 
-Que vous soyez un développeur dapp ou un développeur de subgraphs, vous devrez gérer vos clés API. Ceci est important pour que vous puissiez interroger les subgraphs, car les clés API garantissent que les connexions entre les services d'application sont valides et autorisées. Cela inclut l'authentification de l'utilisateur final et de l'appareil utilisant l'application.
+## Aperçu
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. La section **Vue d'ensemble** vous permettra de :
+1. Under the **Overview** section, you can:
    - Modifiez le nom de votre clé
    - Régénérer les clés API
    - Affichez l'utilisation actuelle de la clé API avec les statistiques :
      - Nombre de requêtes
      - Montant de GRT dépensé
-2. Sous **Sécurité**, vous pourrez activer les paramètres de sécurité en fonction du niveau de contrôle que vous souhaitez avoir sur vos clés API. Dans cette rubrique, vous pouvez :
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Visualisez et gérez les noms de domaine autorisés à utiliser votre clé API
    - Attribuez des subgraphs qui peuvent être interrogés avec votre clé API

From b21f1cb5b019cc4ac9764c04a68867132a0ec65e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:47 -0500
Subject: [PATCH 0666/1325] New translations managing-api-keys.mdx (Spanish)

---
 .../pages/es/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/es/querying/managing-api-keys.mdx b/website/pages/es/querying/managing-api-keys.mdx
index cdb6f9b3fb17..cdbad6cb7c81 100644
--- a/website/pages/es/querying/managing-api-keys.mdx
+++ b/website/pages/es/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Administración de tus claves API
 ---
 
-Independientemente de si eres un developer de aplicaciones descentralizadas (apps) o un developer de subgrafos, necesitarás administrar tus claves de API. Esto es importante para que puedas consultar los subgrafos porque las claves API aseguran que las conexiones entre los servicios de la aplicación sean válidas y están autorizadas. Esto incluye la autenticación del usuario final y del dispositivo que utiliza la aplicación.
+## Descripción
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. La sección ** Visión General ** te permitirá:
+1. Under the **Overview** section, you can:
    - Editar el nombre de tu clave
    - Regenerar las claves API
    - Ver el uso actual de la clave API con estadísticas:
      - Número de consultas
      - Cantidad de GRT gastado
-2. En **Seguridad**, podrás optar por la configuración de seguridad en función del nivel de control que quieras tener sobre tus claves API. En esta sección, puedes:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Ver y administrar los nombres de dominio autorizados a utilizar tu clave API
    - Asignar subgrafos que puedan ser consultados con tu clave API

From e9a24cef6f55ef51ca8ebaf294d85d9a33954ead Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:48 -0500
Subject: [PATCH 0667/1325] New translations managing-api-keys.mdx (Arabic)

---
 .../pages/ar/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/ar/querying/managing-api-keys.mdx b/website/pages/ar/querying/managing-api-keys.mdx
index 7e94abf2a4a8..f23017bf015e 100644
--- a/website/pages/ar/querying/managing-api-keys.mdx
+++ b/website/pages/ar/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## نظره عامة
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - تعديل اسم المفتاح الخاص بك
    - إعادة إنشاء مفاتيح API
    - عرض الاستخدام الحالي لمفتاح API مع الإحصائيات:
      - عدد الاستعلامات
      - كمية GRT التي تم صرفها
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - عرض وإدارة أسماء النطاقات المصرح لها باستخدام مفتاح API الخاص بك
    - تعيين الـ subgraphs التي يمكن الاستعلام عنها باستخدام مفتاح API الخاص بك

From 8aac492e8583c641b737204900192e855954d1fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:49 -0500
Subject: [PATCH 0668/1325] New translations managing-api-keys.mdx (Czech)

---
 .../pages/cs/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/cs/querying/managing-api-keys.mdx b/website/pages/cs/querying/managing-api-keys.mdx
index 1a9626028815..0f5721e5cbcb 100644
--- a/website/pages/cs/querying/managing-api-keys.mdx
+++ b/website/pages/cs/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Správa klíčů API
 ---
 
-Bez ohledu na to, zda jste vývojář dapp nebo podgraf, budete muset spravovat klíče API. To je důležité pro to, abyste se mohli dotazovat na podgrafy, protože klíče API zajišťují, že spojení mezi službami aplikace jsou platná a autorizovaná. To zahrnuje ověřování koncového uživatele a zařízení, které aplikaci používá.
+## Přehled
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. Sekce **Přehled** vám umožní:
+1. Under the **Overview** section, you can:
    - Úprava názvu klíče
    - Regenerace klíčů API
    - Zobrazení aktuálního využití klíče API se statsi:
      - Počet dotazů
      - Výše vynaložených GRT
-2. V části **Zabezpečení** budete moci zvolit nastavení zabezpečení podle úrovně kontroly, kterou chcete mít nad klíči API. V této části můžete:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Zobrazení a správa názvů domén oprávněných používat váš klíč API
    - Přiřazení podgrafů, na které se lze dotazovat pomocí klíče API

From d89c33c97f67d21ebdd8d90bd5e72921fcc8f0cf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:51 -0500
Subject: [PATCH 0669/1325] New translations managing-api-keys.mdx (German)

---
 .../pages/de/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/de/querying/managing-api-keys.mdx b/website/pages/de/querying/managing-api-keys.mdx
index 155710dd6849..f7aff33ea926 100644
--- a/website/pages/de/querying/managing-api-keys.mdx
+++ b/website/pages/de/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Overview
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From 5b25f816a3d5bbf6fd1c591f19991df3afc2879c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:52 -0500
Subject: [PATCH 0670/1325] New translations managing-api-keys.mdx (Italian)

---
 .../pages/it/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/it/querying/managing-api-keys.mdx b/website/pages/it/querying/managing-api-keys.mdx
index 97ee3cc4df32..ea42572de442 100644
--- a/website/pages/it/querying/managing-api-keys.mdx
+++ b/website/pages/it/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Gestione delle chiavi API
 ---
 
-Indipendentemente dal fatto che siate sviluppatori di dapp o di subgraph, dovrete gestire le vostre chiavi API. Questo è importante per poter effetuare query dei subgraph, perché le chiavi API assicurano che le connessioni tra i servizi applicativi siano valide e autorizzate. Ciò include l'autenticazione dell'utente finale e del dispositivo che utilizza l'applicazione.
+## Panoramica
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. La sezione **Overview** vi permetterà di:
+1. Under the **Overview** section, you can:
    - Modificare il nome della chiave
    - Rigenerare le chiavi API
    - Visualizza l'utilizzo attuale della chiave API con le statistiche:
      - Numero di query
      - Importo di GRT speso
-2. Sotto **Security**, potrete scegliere le impostazioni di sicurezza a seconda del livello di controllo che desiderate avere sulle vostre chiavi API. In questa sezione è possibile:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Visualizzare e gestire i nomi di dominio autorizzati a utilizzare la chiave API
    - Assegnare i subgraph che possono essere interrogati con la chiave API

From 6217ce68ab0268bded29e1cb27de9b605d9affc9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:53 -0500
Subject: [PATCH 0671/1325] New translations managing-api-keys.mdx (Japanese)

---
 .../pages/ja/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/ja/querying/managing-api-keys.mdx b/website/pages/ja/querying/managing-api-keys.mdx
index 23c9fa043daf..fc7402c28349 100644
--- a/website/pages/ja/querying/managing-api-keys.mdx
+++ b/website/pages/ja/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: API キーの管理
 ---
 
-Dapp 開発者、サブグラフ開発者に関わらず、API キーを管理する必要があります。API キーは、アプリケーションサービス間の接続が有効で認証されていることを確認するため、サブグラフを照会できるようにするために重要です。これには、アプリケーションを使用するエンドユーザとデバイスの認証が含まれます。
+## 概要
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. **Overview**セクションでは、以下のことができます:
+1. Under the **Overview** section, you can:
    - キー名の編集
    - API キーの再生成
    - API キーの現在の使用状況を統計で表示:
      - クエリの数
      - 使用した GRT の量
-2. **Security**では、APIキーの管理レベルに応じて、セキュリティ設定を選択することができます。このセクションでは、次のことが可能です：
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - API キーの使用を許可されたドメイン名の表示と管理
    - API キーでクエリ可能なサブグラフの割り当て

From 11888047dd1a12f1944f4c093b4e89bf3c0f0461 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:54 -0500
Subject: [PATCH 0672/1325] New translations managing-api-keys.mdx (Korean)

---
 .../pages/ko/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/ko/querying/managing-api-keys.mdx b/website/pages/ko/querying/managing-api-keys.mdx
index 155710dd6849..f7aff33ea926 100644
--- a/website/pages/ko/querying/managing-api-keys.mdx
+++ b/website/pages/ko/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Overview
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From b2180b6adabc7bab11d10c3d22da100404cba44e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:55 -0500
Subject: [PATCH 0673/1325] New translations managing-api-keys.mdx (Dutch)

---
 .../pages/nl/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/nl/querying/managing-api-keys.mdx b/website/pages/nl/querying/managing-api-keys.mdx
index 155710dd6849..f7aff33ea926 100644
--- a/website/pages/nl/querying/managing-api-keys.mdx
+++ b/website/pages/nl/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Overview
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From 6f3f8a0f639c599b773ac158e35b7fcdb1a36242 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:56 -0500
Subject: [PATCH 0674/1325] New translations managing-api-keys.mdx (Polish)

---
 .../pages/pl/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/pl/querying/managing-api-keys.mdx b/website/pages/pl/querying/managing-api-keys.mdx
index 155710dd6849..f7aff33ea926 100644
--- a/website/pages/pl/querying/managing-api-keys.mdx
+++ b/website/pages/pl/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Overview
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From 8e29ac75bac9376882c1594d104c143ab188824c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:57 -0500
Subject: [PATCH 0675/1325] New translations managing-api-keys.mdx (Portuguese)

---
 .../pages/pt/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/pt/querying/managing-api-keys.mdx b/website/pages/pt/querying/managing-api-keys.mdx
index 98392067367c..0592d611312d 100644
--- a/website/pages/pt/querying/managing-api-keys.mdx
+++ b/website/pages/pt/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Como gerir as suas chaves de API
 ---
 
-Independente de ser um programador de dApp ou de subgraph, é importante gerir as suas chaves de API. Isto é importante para poder fazer queries em subgraphs, porque chaves de API garantem a validade e autorização das conexões entre serviços de aplicativos. Isto inclui a autenticação do usuário final e do dispositivo que usa o aplicativo.
+## Visão geral
 
-A tabela "API keys" lista chaves API existentes, o que lhe dará a habilidade de gestar ou apagá-las. Para cada chave, é possível ver o seu estado, o custo para o período atual, o limite de gastos para o período atual, assim como número total de queries. É possível abrir o menu de "três pontos" para mudar uma chave API:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Renomear chave API
 - Regenerar chave API
 - Apagar chave API
 - Gestar limite de gastos: este é um limite opcional de gastos mensais para uma chave API, em USD. Este limite é por período de cobrança (mês do calendário).
 
+### API Key Details
+
 É possível clicar numa chave API individual para exibir a sua página de Detalhes:
 
-1. A seção **Overview** lhe permitirá:
+1. Under the **Overview** section, you can:
    - Alterar o nome da sua chave
    - Regenerar chaves de API
    - Ver o uso atual da chave de API com estatísticas:
      - Número de queries
      - Quantia de GRT gasta
-2. Sob **Security** (Segurança), dá para ativar as configurações de segurança por opção, a depender do nível de controle que quer ter sobre as suas chaves de API. Nesta seção, é possível:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Visualizar e gerir os nomes de domínio autorizados a usar a sua chave de API
    - Apontar subgraphs que podem ser sujeitos a queries com a sua chave de API

From 56cdc7810f45c9ac4b18fe1388623cf6c5e17663 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:58 -0500
Subject: [PATCH 0676/1325] New translations managing-api-keys.mdx (Russian)

---
 .../pages/ru/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/ru/querying/managing-api-keys.mdx b/website/pages/ru/querying/managing-api-keys.mdx
index f539e2f254f7..002aa22be689 100644
--- a/website/pages/ru/querying/managing-api-keys.mdx
+++ b/website/pages/ru/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Управление вашими ключами API
 ---
 
-Независимо от того, являетесь ли вы разработчиком dapp или разработчиком субграфов, вам нужно будет управлять своими API-ключами. Это важно для того, чтобы вы могли запрашивать субграфы, поскольку ключи API гарантируют, что соединения между службами приложений действительны и авторизованы. Это включает в себя аутентификацию конечного пользователя и устройства с помощью приложения.
+## Обзор
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. Раздел ** Overview ** позволит вам:
+1. Under the **Overview** section, you can:
    - Отредактируйте свое ключевое имя
    - Регенерировать ключи API
    - Просмотр текущего использования ключа API со статистикой:
      - Количество запросов
      - Количество потраченных GRT
-2. В разделе ** Security ** вы сможете выбрать настройки безопасности в зависимости от уровня контроля, который вы хотели бы иметь над своими ключами API. В этом разделе вы можете:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Просматривайте доменные имена, авторизованные для использования вашего API-ключа, и управляйте ими
    - Назначьте субграфы, которые могут быть запрошены с помощью вашего API-ключа

From 0305d8edbad48ee85bcd7e0f04f6f1c66eaddd5b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:43:59 -0500
Subject: [PATCH 0677/1325] New translations managing-api-keys.mdx (Swedish)

---
 .../pages/sv/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/sv/querying/managing-api-keys.mdx b/website/pages/sv/querying/managing-api-keys.mdx
index c9cfc02cedb9..3c3ad4ba152e 100644
--- a/website/pages/sv/querying/managing-api-keys.mdx
+++ b/website/pages/sv/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Hantera dina API-nycklar
 ---
 
-Oavsett om du är en dapp-utvecklare eller en subgraf-utvecklare kommer du att behöva hantera dina API-nycklar. Detta är viktigt för att kunna fråga subgrafer, eftersom API-nycklar säkerställer att anslutningar mellan applikationstjänster är giltiga och auktoriserade. Detta inkluderar autentisering av slutanvändare och enheten som använder applikationen.
+## Översikt
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. **Översikts**-sektionen kommer att ge dig möjlighet att:
+1. Under the **Overview** section, you can:
    - Redigera nyckelns namn
    - Återgenerera API-nycklar
    - Visa aktuell användning av API-nyckeln med statistik:
      - Antal förfrågningar
      - Mängd GRT spenderad
-2. Under **Säkerhet** kan du välja säkerhetsinställningar beroende på vilken nivå av kontroll du vill ha över dina API-nycklar. I den här sektionen kan du:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Visa och hantera domännamn som har auktoriserats att använda din API-nyckel
    - Koppla subgrafer som kan frågas med din API-nyckel

From 15016ff973ef84721e7fda7466cf753eee462bfc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:00 -0500
Subject: [PATCH 0678/1325] New translations managing-api-keys.mdx (Turkish)

---
 .../pages/tr/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/tr/querying/managing-api-keys.mdx b/website/pages/tr/querying/managing-api-keys.mdx
index 155710dd6849..f8ece448a813 100644
--- a/website/pages/tr/querying/managing-api-keys.mdx
+++ b/website/pages/tr/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Genel Bakış
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From 922f6f239a7c5376d021db90fd00b0411902df42 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:01 -0500
Subject: [PATCH 0679/1325] New translations managing-api-keys.mdx (Ukrainian)

---
 .../pages/uk/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/uk/querying/managing-api-keys.mdx b/website/pages/uk/querying/managing-api-keys.mdx
index 9232ea2e5529..26ab619d9279 100644
--- a/website/pages/uk/querying/managing-api-keys.mdx
+++ b/website/pages/uk/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Управління API-ключами
 ---
 
-Незалежно від того, ви розробник децентралізованих додатків, чи розробник підграфів, вам в будь-якому випадку потрібно керувати власними API-ключами. Це важливо для того, щоб мати можливість отримувати запити з підграфів, оскільки ключі API гарантують, що з'єднання між програмними сервісами є дійсними та авторизованими. Це включає автентифікацію кінцевого користувача та пристрою, за допомогою якого використовувались програми.
+## Overview
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. У розділі **Overview** ви зможете:
+1. Under the **Overview** section, you can:
    - Змінювати ім'я вашого ключа
    - Повторно створити API-ключі
    - Переглянути поточне використання API-ключа з такою статистикою:
      - Кількість запитів
      - Кількість витрачених GRT
-2. У розділі **Security** ви зможете обирати налаштування безпеки залежно від рівня контролю, який ви хочете мати над своїми ключами API. Також у цьому розділі ви можете:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - Переглядати доменні імена, яким дозволено використовувати ваш API-ключ та керувати цими іменами
    - Призначати підграфи, з яких можна отримувати запити за допомогою API-ключа

From a0691373d35cbc84fe4bc834694417f968ca75fe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:02 -0500
Subject: [PATCH 0680/1325] New translations managing-api-keys.mdx (Chinese
 Simplified)

---
 .../pages/zh/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/zh/querying/managing-api-keys.mdx b/website/pages/zh/querying/managing-api-keys.mdx
index bdad66f33fa1..381ed2a67447 100644
--- a/website/pages/zh/querying/managing-api-keys.mdx
+++ b/website/pages/zh/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: 管理您的 API 密钥
 ---
 
-无论您是 dapp 开发人员还是子图开发人员，您都需要管理您的 API 密钥。 这对您能够查询子图很重要，因为 API 密钥确保应用程序服务之间的连接有效且经过授权。 这包括验证最终用户和使用应用程序的设备。
+## 概述
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. **Overview**部分将允许您：
+1. Under the **Overview** section, you can:
    - 编辑您的密钥名称
    - 重新生成 API 密钥
    - 使用统计信息查看 API 密钥的当前使用情况：
      - 查询数
      - 花费的 GRT 金额
-2. 在**Security**下，您可以根据自己对 API 密钥的控制级别选择启用安全设置。 在本节中，您可以：
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - 查看和管理授权使用您的 API 密钥的域名
    - 分配可以使用您的 API 密钥查询的子图

From d2a317068964930fc9c16cc59a45129032367cf4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:03 -0500
Subject: [PATCH 0681/1325] New translations managing-api-keys.mdx (Urdu
 (Pakistan))

---
 .../pages/ur/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/ur/querying/managing-api-keys.mdx b/website/pages/ur/querying/managing-api-keys.mdx
index e75beeb61c1e..505edb314906 100644
--- a/website/pages/ur/querying/managing-api-keys.mdx
+++ b/website/pages/ur/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: اپنی API کلیدوں کا انتظام کرنا
 ---
 
-اس سے قطع نظر کہ آپ ڈی ایپ ڈویلپر ہیں یا سب گراف ڈویلپر، آپ کو اپنی API کلیدوں کا نظم کرنے کی ضرورت ہوگی۔ آپ کے لیے سب گراف سے کیوری کرنے کے قابل ہونا ضروری ہے کیونکہ API کلید اس بات کو یقینی بناتی ہیں کہ ایپلیکیشن سروسز کے درمیان رابطے درست اور مجاز ہیں۔ اس میں ایپلیکیشن استعمال کرنے والے آخری صارف اور ڈیوائس کی تصدیق کرنا شامل ہے.
+## جائزہ
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. **Overview** کا سیکشن آپ کو اجازت دے گا کہ:
+1. Under the **Overview** section, you can:
    - اپنی کلید کے نام کو ترمیم دیں
    - API کلیدوں کو دوبارہ سے بنائیں
    - اعدادوشمار کے ساتھ API کلید کا موجودہ استعمال دیکھیں:
      - کیوریز کی تعداد
      - GRT کو تعداد جو خرچ ہوئ ہے
-2. **سیکیورٹی** کے تحت، آپ اپنی API کلیدوں پر کنٹرول کی سطح کے لحاظ سے سیکیورٹی کی ترتیبات میں آپٹ ان کرنے کے قابل ہوں گے۔ اس سیکشن میں، آپ کر سکتے ہیں:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - اپنی API کلید استعمال کرنے کے لیے مجاز ڈومین ناموں کو دیکھیں اور ان کا نظم کریں
    - سب گراف تفویض کریں جن سے آپ کی API کلید سے کیوری کیا جا سکتا ہے

From 79ba572d717584deab5eee8c213b40e9a7b741a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:04 -0500
Subject: [PATCH 0682/1325] New translations managing-api-keys.mdx (Vietnamese)

---
 .../pages/vi/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/vi/querying/managing-api-keys.mdx b/website/pages/vi/querying/managing-api-keys.mdx
index 155710dd6849..7798f96071eb 100644
--- a/website/pages/vi/querying/managing-api-keys.mdx
+++ b/website/pages/vi/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-Regardless of whether you’re a dapp developer or a subgraph developer, you’ll need to manage your API keys. This is important for you to be able to query subgraphs because API keys make sure the connections between application services are valid and authorized. This includes authenticating the end user and the device using the application.
+## Tổng quan
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. Under **Security**, you’ll be able to opt into security settings depending on the level of control you’d like to have over your API keys. In this section, you can:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From 909e37cf560f1795ed47e9e5ab30a80973ea238a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:05 -0500
Subject: [PATCH 0683/1325] New translations managing-api-keys.mdx (Marathi)

---
 .../pages/mr/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/mr/querying/managing-api-keys.mdx b/website/pages/mr/querying/managing-api-keys.mdx
index 0048861e4fbc..945a4add2851 100644
--- a/website/pages/mr/querying/managing-api-keys.mdx
+++ b/website/pages/mr/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: Managing your API keys
 ---
 
-तुम्ही dapp डेव्हलपर किंवा सबग्राफ डेव्हलपर असलात तरीही, तुम्हाला तुमच्या API की व्यवस्थापित कराव्या लागतील. तुमच्यासाठी सबग्राफ्स क्वेरी करण्यास सक्षम असणे महत्त्वाचे आहे कारण API की अनुप्रयोग सेवांमधील कनेक्शन वैध आणि अधिकृत असल्याची खात्री करतात. यात अंतिम वापरकर्ता आणि अनुप्रयोग वापरून डिव्हाइस प्रमाणीकृत करणे समाविष्ट आहे.
+## सविश्लेषण
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. The **Overview** section will allow you to:
+1. Under the **Overview** section, you can:
    - Edit your key name
    - Regenerate API keys
    - View the current usage of the API key with stats:
      - Number of queries
      - Amount of GRT spent
-2. **सुरक्षा** अंतर्गत, तुम्‍हाला तुमच्‍या API की वर असल्‍याच्‍या नियंत्रणच्‍या स्‍तरावर अवलंबून सुरक्षा सेटिंग्‍ज निवडण्‍यात सक्षम असाल. या विभागात, तुम्ही हे करू शकता:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - View and manage the domain names authorized to use your API key
    - Assign subgraphs that can be queried with your API key

From c69fc546c4b90219f2d2158bf418bc9adb01b904 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:06 -0500
Subject: [PATCH 0684/1325] New translations managing-api-keys.mdx (Hindi)

---
 .../pages/hi/querying/managing-api-keys.mdx    | 18 ++++++++++++++----
 1 file changed, 14 insertions(+), 4 deletions(-)

diff --git a/website/pages/hi/querying/managing-api-keys.mdx b/website/pages/hi/querying/managing-api-keys.mdx
index c43033b37605..4f36f067d89d 100644
--- a/website/pages/hi/querying/managing-api-keys.mdx
+++ b/website/pages/hi/querying/managing-api-keys.mdx
@@ -2,23 +2,33 @@
 title: अपनी एपीआई कुंजियों का प्रबंधन
 ---
 
-चाहे आप डैप डेवलपर हों या सबग्राफ डेवलपर, आपको अपनी एपीआई कुंजियों को प्रबंधित करने की आवश्यकता होगी। आपके लिए सबग्राफ को क्वेरी करने में सक्षम होना महत्वपूर्ण है क्योंकि एपीआई कुंजियाँ सुनिश्चित करती हैं कि एप्लिकेशन सेवाओं के बीच कनेक्शन वैध और अधिकृत हैं। इसमें एप्लिकेशन का उपयोग करने वाले अंतिम उपयोगकर्ता और डिवाइस को प्रमाणित करना शामिल है।
+## अवलोकन
 
-The "API keys" table lists out existing API keys, which will give you the ability to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, as well as total query numbers. You can click the "three dots" menu to edit a given API key:
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
 
 - Rename API key
 - Regenerate API key
 - Delete API key
 - Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
 
+### API Key Details
+
 You can click on an individual API key to view the Details page:
 
-1. **अवलोकन** अनुभाग आपको इसकी अनुमति देगा:
+1. Under the **Overview** section, you can:
    - अपना कुंजी नाम संपादित करें
    - एपीआई कुंजियों को पुन: उत्पन्न करें
    - आंकड़ों के साथ एपीआई कुंजी का वर्तमान उपयोग देखें:
      - प्रश्नों की संख्या
      - जीआरटी की राशि खर्च की गई
-2. **सुरक्षा** के अंतर्गत, आप अपनी API कुंजियों पर नियंत्रण के स्तर के आधार पर सुरक्षा सेटिंग में शामिल होने में सक्षम होंगे। इस खंड में, आप कर सकते हैं:
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
    - अपनी API कुंजी का उपयोग करने के लिए प्राधिकृत डोमेन नाम देखें और प्रबंधित करें
    - सबग्राफ असाइन करें जिन्हें आपकी एपीआई कुंजी से पूछा जा सकता है

From ad2d95818ddc18c5dccdda154ad8feb41bc5a911 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:08 -0500
Subject: [PATCH 0685/1325] New translations managing-api-keys.mdx (Swahili)

---
 .../pages/sw/querying/managing-api-keys.mdx   | 34 +++++++++++++++++++
 1 file changed, 34 insertions(+)
 create mode 100644 website/pages/sw/querying/managing-api-keys.mdx

diff --git a/website/pages/sw/querying/managing-api-keys.mdx b/website/pages/sw/querying/managing-api-keys.mdx
new file mode 100644
index 000000000000..f7aff33ea926
--- /dev/null
+++ b/website/pages/sw/querying/managing-api-keys.mdx
@@ -0,0 +1,34 @@
+---
+title: Managing your API keys
+---
+
+## Overview
+
+API keys are needed to query subgraphs. They ensure that the connections between application services are valid and authorized, including authenticating the end user and the device using the application.
+
+### Create and Manage API Keys
+
+Go to [Subgraph Studio](https://thegraph.com/studio/) and click the **API Keys** tab to create and manage your API keys for specific subgraphs.
+
+The "API keys" table lists existing API keys and allows you to manage or delete them. For each key, you can see its status, the cost for the current period, the spending limit for the current period, and the total number of queries.
+
+You can click the "three dots" menu to the right of a given API key to:
+
+- Rename API key
+- Regenerate API key
+- Delete API key
+- Manage spending limit: this is an optional monthly spending limit for a given API key, in USD. This limit is per billing period (calendar month).
+
+### API Key Details
+
+You can click on an individual API key to view the Details page:
+
+1. Under the **Overview** section, you can:
+   - Edit your key name
+   - Regenerate API keys
+   - View the current usage of the API key with stats:
+     - Number of queries
+     - Amount of GRT spent
+2. Under the **Security** section, you can opt into security settings depending on the level of control you’d like to have. Specifically, you can:
+   - View and manage the domain names authorized to use your API key
+   - Assign subgraphs that can be queried with your API key

From ab8c42c8cf8a588969ca898cb22b32b8bd51885c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:09 -0500
Subject: [PATCH 0686/1325] New translations arweave.mdx (Romanian)

---
 website/pages/ro/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ro/cookbook/arweave.mdx b/website/pages/ro/cookbook/arweave.mdx
index b079da30a013..4c35f4ee8e2e 100644
--- a/website/pages/ro/cookbook/arweave.mdx
+++ b/website/pages/ro/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From 59eefe10176d0d7e9d1e561e0960f23940e03c57 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:10 -0500
Subject: [PATCH 0687/1325] New translations arweave.mdx (Spanish)

---
 website/pages/es/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/es/cookbook/arweave.mdx b/website/pages/es/cookbook/arweave.mdx
index 5c09b46e3e9a..7c07a486f887 100644
--- a/website/pages/es/cookbook/arweave.mdx
+++ b/website/pages/es/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ La definición de esquema describe la estructura de la base de datos de subgrafo
 
 Los handlers para procesar eventos están escritos en [AssemblyScript](https://www.assemblyscript.org/).
 
-La indexación de Arweave introduce tipos de datos específicos de Arweave en la [API de AssemblyScript](/developing/graph-ts/api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ Escribir los mappings de un subgrafo de Arweave es muy similar a escribir los ma
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Consultando un subgrafo de Arweave

From aa5fe0c960a674eec0fa9939b0df39bc619f1b6e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:11 -0500
Subject: [PATCH 0688/1325] New translations arweave.mdx (Arabic)

---
 website/pages/ar/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ar/cookbook/arweave.mdx b/website/pages/ar/cookbook/arweave.mdx
index e2b25f673dfc..06fe4729bf4b 100644
--- a/website/pages/ar/cookbook/arweave.mdx
+++ b/website/pages/ar/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From 53487ab43aad65973fb3654a5c5c71af720ca943 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:14 -0500
Subject: [PATCH 0689/1325] New translations arweave.mdx (Czech)

---
 website/pages/cs/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/cs/cookbook/arweave.mdx b/website/pages/cs/cookbook/arweave.mdx
index adb99aaf5251..40c88f99ccca 100644
--- a/website/pages/cs/cookbook/arweave.mdx
+++ b/website/pages/cs/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ Definice schématu popisuje strukturu výsledné databáze podgrafu a vztahy mez
 
 Obslužné programy pro zpracování událostí jsou napsány v jazyce [AssemblyScript](https://www.assemblyscript.org/).
 
-Indexování Arweave zavádí do [AssemblyScript API](/developing/graph-ts/api/) datové typy specifické pro Arweave.
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ Zápis mapování podgrafu Arweave je velmi podobný psaní mapování podgrafu
 Jakmile je podgraf vytvořen na ovládacím panelu Podgraf Studio, můžete jej nasadit pomocí příkazu `graph deploy` CLI.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Dotazování podgrafu Arweave

From 02bddb4f5f6eb519fc2a0015bffe4d0764286c4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:15 -0500
Subject: [PATCH 0690/1325] New translations arweave.mdx (German)

---
 website/pages/de/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/de/cookbook/arweave.mdx b/website/pages/de/cookbook/arweave.mdx
index ec3eca650e4f..6e68ee97cf34 100644
--- a/website/pages/de/cookbook/arweave.mdx
+++ b/website/pages/de/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From b3eb7c32b28e2dcab462b85c03363f1a86c2f9d7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:16 -0500
Subject: [PATCH 0691/1325] New translations arweave.mdx (Italian)

---
 website/pages/it/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/it/cookbook/arweave.mdx b/website/pages/it/cookbook/arweave.mdx
index b079da30a013..4c35f4ee8e2e 100644
--- a/website/pages/it/cookbook/arweave.mdx
+++ b/website/pages/it/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From b3b4d0a639455337f1b657fa2bd4965268f773c0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:17 -0500
Subject: [PATCH 0692/1325] New translations arweave.mdx (Japanese)

---
 website/pages/ja/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ja/cookbook/arweave.mdx b/website/pages/ja/cookbook/arweave.mdx
index eae8f58fd762..5df10d06992e 100644
--- a/website/pages/ja/cookbook/arweave.mdx
+++ b/website/pages/ja/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ Arweaveデータソースは 2 種類のハンドラーをサポートしてい
 
 イベントを処理するハンドラは、[AssemblyScript](https://www.assemblyscript.org/) で記述されています。
 
-Arweaveのインデックス作成は、[AssemblyScript API](/developing/graph-ts/api/)にArweave固有のデータ型を導入しています。
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ Arweave サブグラフのマッピングの記述は、Ethereum サブグラフ
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Arweaveサブグラフのクエリ

From 6ebf15500cc88fa8892ef94a5b1a13e07701bc11 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:19 -0500
Subject: [PATCH 0693/1325] New translations arweave.mdx (Korean)

---
 website/pages/ko/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ko/cookbook/arweave.mdx b/website/pages/ko/cookbook/arweave.mdx
index b079da30a013..4c35f4ee8e2e 100644
--- a/website/pages/ko/cookbook/arweave.mdx
+++ b/website/pages/ko/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From aae6e493761aef776d645d4a19024f86ac7200bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:20 -0500
Subject: [PATCH 0694/1325] New translations arweave.mdx (Dutch)

---
 website/pages/nl/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/nl/cookbook/arweave.mdx b/website/pages/nl/cookbook/arweave.mdx
index 959ef3a2c01a..056671f1b774 100644
--- a/website/pages/nl/cookbook/arweave.mdx
+++ b/website/pages/nl/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From e240af14da54748b7a87d7955fa0a1290782d6a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:21 -0500
Subject: [PATCH 0695/1325] New translations arweave.mdx (Polish)

---
 website/pages/pl/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pl/cookbook/arweave.mdx b/website/pages/pl/cookbook/arweave.mdx
index b079da30a013..4c35f4ee8e2e 100644
--- a/website/pages/pl/cookbook/arweave.mdx
+++ b/website/pages/pl/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From 9d721c4d0f0e4fa882e3f7f0c92a216d66b33752 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:22 -0500
Subject: [PATCH 0696/1325] New translations arweave.mdx (Portuguese)

---
 website/pages/pt/cookbook/arweave.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/pt/cookbook/arweave.mdx b/website/pages/pt/cookbook/arweave.mdx
index 5ef8ac4d7ae1..beac71cf7ea5 100644
--- a/website/pages/pt/cookbook/arweave.mdx
+++ b/website/pages/pt/cookbook/arweave.mdx
@@ -86,7 +86,7 @@ dataSources:
 - A rede deve corresponder a uma rede no Graph Node que a hospeda. No Subgraph Studio, a mainnet do Arweave é `arweave-mainnet`
 - Fontes de dados no Arweave introduzem um campo `source.owner` opcional, a chave pública de uma carteira no Arweave
 
-Fontes de dados no Arweave apoiam duas categorias de _handlers_:
+Fontes de dados no Arweave apoiam duas categorias de *handlers*:
 
 - `blockHandlers` - Executar em cada bloco novo no Arweave. Nenhum `source.owner` é exigido.
 - `transactionHandlers` — Executar em todas as transações onde o `source.owner` da fonte de dados é o dono. Atualmente, um dono é exigido para o `transactionHandlers`; caso utilizadores queiram processar todas as transações, eles devem providenciar "" como o `source.owner`
@@ -97,15 +97,15 @@ Fontes de dados no Arweave apoiam duas categorias de _handlers_:
 
 > Nota: Transações no [Irys (antigo Bundlr)](https://bundlr.network/) não são apoiadas presentemente.
 
-## Definição de _Schema_
+## Definição de *Schema*
 
 A definição de Schema descreve a estrutura do banco de dados resultado do subgraph, e os relacionamentos entre entidades. Isto é agnóstico da fonte de dados original. Há mais detalhes na definição de schema de subgraph [aqui](/developing/creating-a-subgraph/#the-graphql-schema).
 
 ## Mapeamentos de AssemblyScript
 
-Os _handlers_ para eventos de processamento são escritos em [AssemblyScript](https://www.assemblyscript.org/).
+Os *handlers* para eventos de processamento são escritos em [AssemblyScript](https://www.assemblyscript.org/).
 
-O _indexing_ do Arweave introduz categorias de dados específicas ao Arweave ao [API do AssemblyScript](/developing/graph-ts/api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -146,7 +146,7 @@ class Transaction {
 }
 ```
 
-_Handlers_ de bloco recebem um `Block`, enquanto transações recebem uma `Transaction`.
+*Handlers* de bloco recebem um `Block`, enquanto transações recebem uma `Transaction`.
 
 Escrever os mapeamentos de um Subgraph no Arweave é muito similar à escrita dos mapeamentos de um Subgraph no Ethereum. Para mais informações, clique [aqui](/developing/creating-a-subgraph/#writing-mappings).
 
@@ -155,7 +155,7 @@ Escrever os mapeamentos de um Subgraph no Arweave é muito similar à escrita do
 Após criar o seu Subgraph no painel de controlo do Subraph Studio, você pode lançá-lo com o código de linha de comando `graph deploy`.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Consultando um Subgraph no Arweave

From 725f001c2d973570ddb576084b4af37992c4a914 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:23 -0500
Subject: [PATCH 0697/1325] New translations arweave.mdx (Swedish)

---
 website/pages/sv/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/sv/cookbook/arweave.mdx b/website/pages/sv/cookbook/arweave.mdx
index bdb9b1ff1810..b354355d683f 100644
--- a/website/pages/sv/cookbook/arweave.mdx
+++ b/website/pages/sv/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ Schema definition beskriver strukturen för den resulterande subgraf databasen o
 
 Hanterarna för bearbetning av händelser är skrivna i [AssemblyScript](https://www.assemblyscript.org/).
 
-Arweave indexering introducerar Arweave-specifika datatyper till [AssemblyScript API](/developing/graph-ts/api/).
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ Att skriva mappningar av en Arweave subgrafer är mycket lik att skriva mappning
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Fråga efter en Arweave-subgraf

From ed374f2f27c35537a10de9dedcc639f45f31f859 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:24 -0500
Subject: [PATCH 0698/1325] New translations arweave.mdx (Turkish)

---
 website/pages/tr/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/tr/cookbook/arweave.mdx b/website/pages/tr/cookbook/arweave.mdx
index f20ac16d23b7..01e455b7aaf6 100644
--- a/website/pages/tr/cookbook/arweave.mdx
+++ b/website/pages/tr/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ Arweave veri kaynakları iki tür işleyiciyi destekler:
 
 Olayları işlemek için işleyiciler [AssemblyScript](https://www.assemblyscript.org/) içinde yazılmıştır.
 
-Arweave indeksleme, [AssemblyScript API](/developing/graph-ts/api/)'sine Arweave'ye özgü veri tipleri ekler.
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ Bir Arweave Subgraph'ının eşleştirmelerini yazmak, bir Ethereum Subgraph'ın
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Arweave Subgraph'ını Sorgulama

From eefc107b08867b58b86ce696cac2912d75e791a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:25 -0500
Subject: [PATCH 0699/1325] New translations arweave.mdx (Ukrainian)

---
 website/pages/uk/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/uk/cookbook/arweave.mdx b/website/pages/uk/cookbook/arweave.mdx
index c7159f6e7bb2..532af9be1825 100644
--- a/website/pages/uk/cookbook/arweave.mdx
+++ b/website/pages/uk/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From 42a6cd77f5fb235602f546623815385587c11ca7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:26 -0500
Subject: [PATCH 0700/1325] New translations arweave.mdx (Chinese Simplified)

---
 website/pages/zh/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/zh/cookbook/arweave.mdx b/website/pages/zh/cookbook/arweave.mdx
index 33b585f3c22e..a3ecd2f1c70b 100644
--- a/website/pages/zh/cookbook/arweave.mdx
+++ b/website/pages/zh/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ Arweave 数据源支持两种类型的处理程序:
 
 处理事件的处理程序是用 [AssemblyScript](https://www.assemblyscript.org/) 编写的。
 
-Arweave 索引向 [AssemblyScriptAPI](/developing/graph-ts/api/) 引入了特定于 Arweave 的数据类型。
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ class Transaction {
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## 查询 Arweave 子图

From a0df39fdea2093c1dfd6ad263aec20370c667a00 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:27 -0500
Subject: [PATCH 0701/1325] New translations arweave.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/ur/cookbook/arweave.mdx b/website/pages/ur/cookbook/arweave.mdx
index c9fcac74102e..e39ad7d049d2 100644
--- a/website/pages/ur/cookbook/arweave.mdx
+++ b/website/pages/ur/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ dataSources:
 
 پروسیسنگ ایونٹس کے ہینڈلرز [اسمبلی اسکرپٹ](https://www.assemblyscript.org/) میں لکھے گئے ہیں.
 
-آرویو انڈیکسنگ آرویو سے متعلق مخصوص ڈیٹا کی اقسام کو [اسمبلی اسکرپٹ API](/developing/graph-ts/api/) سے متعارف کراتی ہے.
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ class Transaction {
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## آرویو سب گراف سے کیوری کرنا

From 9e4ce0df3d4d4c4d41a2851b43e06253c771eed7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:29 -0500
Subject: [PATCH 0702/1325] New translations arweave.mdx (Vietnamese)

---
 website/pages/vi/cookbook/arweave.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/vi/cookbook/arweave.mdx b/website/pages/vi/cookbook/arweave.mdx
index b01b9d7665d0..4d925799ee1e 100644
--- a/website/pages/vi/cookbook/arweave.mdx
+++ b/website/pages/vi/cookbook/arweave.mdx
@@ -155,7 +155,7 @@ Writing the mappings of an Arweave Subgraph is very similar to writing the mappi
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## Querying an Arweave Subgraph

From 8be392ad1f5d26e826404b967df2e9c69975a9cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:30 -0500
Subject: [PATCH 0703/1325] New translations arweave.mdx (Marathi)

---
 website/pages/mr/cookbook/arweave.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/mr/cookbook/arweave.mdx b/website/pages/mr/cookbook/arweave.mdx
index 3ffdd306aa6e..a4aebc61808d 100644
--- a/website/pages/mr/cookbook/arweave.mdx
+++ b/website/pages/mr/cookbook/arweave.mdx
@@ -105,7 +105,7 @@ Arweave डेटा स्रोत दोन प्रकारच्या 
 
 इव्हेंटवर प्रक्रिया करण्यासाठी हँडलर [AssemblyScript](https://www.assemblyscript.org/) मध्ये लिहिलेले आहेत.
 
-Arweave अनुक्रमणिका [AssemblyScript API](/developing/graph-ts/api/) मध्ये Arweave-विशिष्ट डेटा प्रकारांचा परिचय देते.
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
 ```tsx
 class Block {
@@ -155,7 +155,7 @@ Arweave Subgraph चे मॅपिंग लिहिणे हे Ethereum Su
 Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
 
 ```bash
-graph deploy --studio --access-token <your-access-token>
+graph deploy --access-token <your-access-token>
 ```
 
 ## प्रश्न करत आहे Arweave सबग्राफ

From 10fd86825c70538f8dafa62f84665ff8607786f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:31 -0500
Subject: [PATCH 0704/1325] New translations arweave.mdx (Swahili)

---
 website/pages/sw/cookbook/arweave.mdx | 239 ++++++++++++++++++++++++++
 1 file changed, 239 insertions(+)
 create mode 100644 website/pages/sw/cookbook/arweave.mdx

diff --git a/website/pages/sw/cookbook/arweave.mdx b/website/pages/sw/cookbook/arweave.mdx
new file mode 100644
index 000000000000..4c35f4ee8e2e
--- /dev/null
+++ b/website/pages/sw/cookbook/arweave.mdx
@@ -0,0 +1,239 @@
+---
+title: Building Subgraphs on Arweave
+---
+
+> Arweave support in Graph Node and on Subgraph Studio is in beta: please reach us on [Discord](https://discord.gg/graphprotocol) with any questions about building Arweave subgraphs!
+
+In this guide, you will learn how to build and deploy Subgraphs to index the Arweave blockchain.
+
+## What is Arweave?
+
+The Arweave protocol allows developers to store data permanently and that is the main difference between Arweave and IPFS, where IPFS lacks the feature; permanence, and files stored on Arweave can't be changed or deleted.
+
+Arweave already has built numerous libraries for integrating the protocol in a number of different programming languages. For more information you can check:
+
+- [Arwiki](https://arwiki.wiki/#/en/main)
+- [Arweave Resources](https://www.arweave.org/build)
+
+## What are Arweave Subgraphs?
+
+The Graph allows you to build custom open APIs called "Subgraphs". Subgraphs are used to tell indexers (server operators) which data to index on a blockchain and save on their servers in order for you to be able to query it at any time using [GraphQL](https://graphql.org/).
+
+[Graph Node](https://github.com/graphprotocol/graph-node) is now able to index data on Arweave protocol. The current integration is only indexing Arweave as a blockchain (blocks and transactions), it is not indexing the stored files yet.
+
+## Building an Arweave Subgraph
+
+To be able to build and deploy Arweave Subgraphs, you need two packages:
+
+1. `@graphprotocol/graph-cli` above version 0.30.2 - This is a command-line tool for building and deploying subgraphs. [Click here](https://www.npmjs.com/package/@graphprotocol/graph-cli) to download using `npm`.
+2. `@graphprotocol/graph-ts` above version 0.27.0 - This is library of subgraph-specific types. [Click here](https://www.npmjs.com/package/@graphprotocol/graph-ts) to download using `npm`.
+
+## Subgraph's components
+
+There are three components of a subgraph:
+
+### 1. Manifest - `subgraph.yaml`
+
+Defines the data sources of interest, and how they should be processed. Arweave is a new kind of data source.
+
+### 2. Schema - `schema.graphql`
+
+Here you define which data you want to be able to query after indexing your Subgraph using GraphQL. This is actually similar to a model for an API, where the model defines the structure of a request body.
+
+The requirements for Arweave subgraphs are covered by the [existing documentation](/developing/creating-a-subgraph/#the-graphql-schema).
+
+### 3. AssemblyScript Mappings - `mapping.ts`
+
+This is the logic that determines how data should be retrieved and stored when someone interacts with the data sources you are listening to. The data gets translated and is stored based off the schema you have listed.
+
+During subgraph development there are two key commands:
+
+```
+$ graph codegen # generates types from the schema file identified in the manifest
+$ graph build # generates Web Assembly from the AssemblyScript files, and prepares all the subgraph files in a /build folder
+```
+
+## Subgraph Manifest Definition
+
+The subgraph manifest `subgraph.yaml` identifies the data sources for the subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example subgraph manifest for an Arweave subgraph:
+
+```yaml
+specVersion: 0.0.5
+description: Arweave Blocks Indexing
+schema:
+  file: ./schema.graphql # link to the schema file
+dataSources:
+  - kind: arweave
+    name: arweave-blocks
+    network: arweave-mainnet # The Graph only supports Arweave Mainnet
+    source:
+      owner: 'ID-OF-AN-OWNER' # The public key of an Arweave wallet
+      startBlock: 0 # set this to 0 to start indexing from chain genesis
+    mapping:
+      apiVersion: 0.0.5
+      language: wasm/assemblyscript
+      file: ./src/blocks.ts # link to the file with the Assemblyscript mappings
+      entities:
+        - Block
+        - Transaction
+      blockHandlers:
+        - handler: handleBlock # the function name in the mapping file
+      transactionHandlers:
+        - handler: handleTx # the function name in the mapping file
+```
+
+- Arweave subgraphs introduce a new kind of data source (`arweave`)
+- The network should correspond to a network on the hosting Graph Node. In Subgraph Studio, Arweave's mainnet is `arweave-mainnet`
+- Arweave data sources introduce an optional source.owner field, which is the public key of an Arweave wallet
+
+Arweave data sources support two types of handlers:
+
+- `blockHandlers` - Run on every new Arweave block. No source.owner is required.
+- `transactionHandlers` - Run on every transaction where the data source's `source.owner` is the owner. Currently an owner is required for `transactionHandlers`, if users want to process all transactions they should provide "" as the `source.owner`
+
+> The source.owner can be the owner's address, or their Public Key.
+
+> Transactions are the building blocks of the Arweave permaweb and they are objects created by end-users.
+
+> Note: [Irys (previously Bundlr)](https://irys.xyz/) transactions are not supported yet.
+
+## Schema Definition
+
+Schema definition describes the structure of the resulting subgraph database and the relationships between entities. This is agnostic of the original data source. There are more details on the subgraph schema definition [here](/developing/creating-a-subgraph/#the-graphql-schema).
+
+## AssemblyScript Mappings
+
+The handlers for processing events are written in [AssemblyScript](https://www.assemblyscript.org/).
+
+Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
+
+```tsx
+class Block {
+  timestamp: u64
+  lastRetarget: u64
+  height: u64
+  indepHash: Bytes
+  nonce: Bytes
+  previousBlock: Bytes
+  diff: Bytes
+  hash: Bytes
+  txRoot: Bytes
+  txs: Bytes[]
+  walletList: Bytes
+  rewardAddr: Bytes
+  tags: Tag[]
+  rewardPool: Bytes
+  weaveSize: Bytes
+  blockSize: Bytes
+  cumulativeDiff: Bytes
+  hashListMerkle: Bytes
+  poa: ProofOfAccess
+}
+
+class Transaction {
+  format: u32
+  id: Bytes
+  lastTx: Bytes
+  owner: Bytes
+  tags: Tag[]
+  target: Bytes
+  quantity: Bytes
+  data: Bytes
+  dataSize: Bytes
+  dataRoot: Bytes
+  signature: Bytes
+  reward: Bytes
+}
+```
+
+Block handlers receive a `Block`, while transactions receive a `Transaction`.
+
+Writing the mappings of an Arweave Subgraph is very similar to writing the mappings of an Ethereum Subgraph. For more information, click [here](/developing/creating-a-subgraph/#writing-mappings).
+
+## Deploying an Arweave Subgraph in Subgraph Studio
+
+Once your subgraph has been created on your Subgraph Studio dashboard, you can deploy by using the `graph deploy` CLI command.
+
+```bash
+graph deploy --access-token <your-access-token>
+```
+
+## Querying an Arweave Subgraph
+
+The GraphQL endpoint for Arweave subgraphs is determined by the schema definition, with the existing API interface. Please visit the [GraphQL API documentation](/querying/graphql-api/) for more information.
+
+## Example Subgraphs
+
+Here is an example subgraph for reference:
+
+- [Example subgraph for Arweave](https://github.com/graphprotocol/graph-tooling/tree/main/examples/arweave-blocks-transactions)
+
+## FAQ
+
+### Can a subgraph index Arweave and other chains?
+
+No, a subgraph can only support data sources from one chain/network.
+
+### Can I index the stored files on Arweave?
+
+Currently, The Graph is only indexing Arweave as a blockchain (its blocks and transactions).
+
+### Can I identify Bundlr bundles in my subgraph?
+
+This is not currently supported.
+
+### How can I filter transactions to a specific account?
+
+The source.owner can be the user's public key or account address.
+
+### What is the current encryption format?
+
+Data is generally passed into the mappings as Bytes, which if stored directly is returned in the subgraph in a `hex` format (ex. block and transaction hashes). You may want to convert to a `base64` or `base64 URL`-safe format in your mappings, in order to match what is displayed in block explorers like [Arweave Explorer](https://viewblock.io/arweave/).
+
+The following `bytesToBase64(bytes: Uint8Array, urlSafe: boolean): string` helper function can be used, and will be added to `graph-ts`:
+
+```
+const base64Alphabet = [
+    "A", "B", "C", "D", "E", "F", "G", "H", "I", "J", "K", "L", "M",
+    "N", "O", "P", "Q", "R", "S", "T", "U", "V", "W", "X", "Y", "Z",
+    "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m",
+    "n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z",
+    "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "+", "/"
+];
+
+const base64UrlAlphabet = [
+    "A", "B", "C", "D", "E", "F", "G", "H", "I", "J", "K", "L", "M",
+    "N", "O", "P", "Q", "R", "S", "T", "U", "V", "W", "X", "Y", "Z",
+    "a", "b", "c", "d", "e", "f", "g", "h", "i", "j", "k", "l", "m",
+    "n", "o", "p", "q", "r", "s", "t", "u", "v", "w", "x", "y", "z",
+    "0", "1", "2", "3", "4", "5", "6", "7", "8", "9", "-", "_"
+];
+
+function bytesToBase64(bytes: Uint8Array, urlSafe: boolean): string {
+    let alphabet = urlSafe? base64UrlAlphabet : base64Alphabet;
+
+    let result = '', i: i32, l = bytes.length;
+    for (i = 2; i < l; i += 3) {
+        result += alphabet[bytes[i - 2] >> 2];
+        result += alphabet[((bytes[i - 2] & 0x03) << 4) | (bytes[i - 1] >> 4)];
+        result += alphabet[((bytes[i - 1] & 0x0F) << 2) | (bytes[i] >> 6)];
+        result += alphabet[bytes[i] & 0x3F];
+    }
+    if (i === l + 1) { // 1 octet yet to write
+        result += alphabet[bytes[i - 2] >> 2];
+        result += alphabet[(bytes[i - 2] & 0x03) << 4];
+        if (!urlSafe) {
+            result += "==";
+        }
+    }
+    if (!urlSafe && i === l) { // 2 octets yet to write
+        result += alphabet[bytes[i - 2] >> 2];
+        result += alphabet[((bytes[i - 2] & 0x03) << 4) | (bytes[i - 1] >> 4)];
+        result += alphabet[(bytes[i - 1] & 0x0F) << 2];
+        if (!urlSafe) {
+            result += "=";
+        }
+    }
+    return result;
+}
+```

From 723426b3d9ad11e9a75b15f6b1cc80e5c2fbc334 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:33 -0500
Subject: [PATCH 0705/1325] New translations subgraph-debug-forking.mdx
 (Arabic)

---
 website/pages/ar/cookbook/subgraph-debug-forking.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ar/cookbook/subgraph-debug-forking.mdx b/website/pages/ar/cookbook/subgraph-debug-forking.mdx
index 6c87d43045c5..44a8bfa28c2c 100644
--- a/website/pages/ar/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/ar/cookbook/subgraph-debug-forking.mdx
@@ -69,14 +69,14 @@ Oops, how unfortunate, when I deploy my perfect looking subgraph to [Subgraph St
 
 وأنا أجيب:
 
-1. `fork-base` هو عنوان URL "الأساسي" ،فمثلا عند إلحاق _subgraph id_ ، يكون عنوان URL الناتج (`<fork-base>/<subgraph-id>`) هو GraphQL endpoint صالح لمخزن الـ subgraph.
+1. ` fork-base ` هو عنوان URL "الأساسي" ،فمثلا عند إلحاق _subgraph id_ ، يكون عنوان URL الناتج (`<fork-base>/<subgraph-id>`) هو GraphQL endpoint صالح لمخزن الـ subgraph.
 2. الـتفريع سهل ، فلا داعي للقلق:
 
 ```bash
 $ graph deploy <subgraph-name> --debug-fork <subgraph-id> --ipfs http://localhost:5001 --node http://localhost:8020
 ```
 
-أيضًا ، لا تنس تعيين حقل `dataSources.source.startBlock` في subgraph manifest لرقم الكتلة(block) التي بها المشكلة، حتى تتمكن من تخطي فهرسة الكتل الغير ضرورية والاستفادة من التفريع!
+أيضًا ، لا تنس تعيين حقل ` dataSources.source.startBlock ` في subgraph manifest لرقم الكتلة(block) التي بها المشكلة، حتى تتمكن من تخطي فهرسة الكتل الغير ضرورية والاستفادة من التفريع!
 
 لذلك ، هذا ما أفعله:
 
@@ -90,7 +90,7 @@ $ cargo run -p graph-node --release -- \
     --fork-base https://api.thegraph.com/subgraphs/id/
 ```
 
-2. بعد فحص دقيق ، لاحظت أن هناك عدم تطابق في تمثيلات الـ `id` المستخدمة عند فهرسة `Gravatar` في المعالجين الخاصين بي. بينما `handleNewGravatar` يحول (`event.params.id.toHex()`) إلى سداسي ، `handleUpdatedGravatar` يستخدم int32 (`event.params.id.toI32()`) مما يجعل `handleUpdatedGravatar` قلقا من "Gravatar not found!". أنا أجعلهم كلاهما يحولان `id` إلى سداسي.
+2. بعد فحص دقيق ، لاحظت أن هناك عدم تطابق في تمثيلات الـ ` id ` المستخدمة عند فهرسة ` Gravatar ` في المعالجين الخاصين بي. بينما ` handleNewGravatar ` يحول (`event.params.id.toHex()`) إلى سداسي ، `handleUpdatedGravatar` يستخدم int32 (`event.params.id.toI32()`) مما يجعل ` handleUpdatedGravatar ` قلقا من "Gravatar not found!". أنا أجعلهم كلاهما يحولان ` id ` إلى سداسي.
 3. After I made the changes I deploy my subgraph to the local Graph Node, **_forking the failing subgraph_** and setting `dataSources.source.startBlock` to `6190343` in `subgraph.yaml`:
 
 ```bash

From 94771bd193f6683f41eb29e9868ad27bbe04ab38 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:34 -0500
Subject: [PATCH 0706/1325] New translations subgraph-debug-forking.mdx (Czech)

---
 .../cs/cookbook/subgraph-debug-forking.mdx    | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/cs/cookbook/subgraph-debug-forking.mdx b/website/pages/cs/cookbook/subgraph-debug-forking.mdx
index e0e3e2a69641..522c273a7e36 100644
--- a/website/pages/cs/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/cs/cookbook/subgraph-debug-forking.mdx
@@ -2,7 +2,7 @@
 title: Rychlé a snadné ladění podgrafů pomocí vidliček
 ---
 
-As with many systems processing large amounts of data, The Graph's Indexers (Graph Nodes) may take quite some time to sync-up your subgraph with the target blockchain. The discrepancy between quick changes with the purpose of debugging and long wait times needed for indexing is extremely counterproductive and we are well aware of that. This is why we are introducing **subgraph forking**, developed by [LimeChain](https://limechain.tech/), and in this article I will show you how this feature can be used to substantially speed-up subgraph debugging!
+Stejně jako u mnoha systémů zpracovávajících velké množství dat může indexerům grafu (Graph Nodes) trvat poměrně dlouho, než synchronizují váš podgraf s cílovým blockchainem. Nesoulad mezi rychlými změnami za účelem ladění a dlouhými čekacími dobami potřebnými pro indexaci je extrémně kontraproduktivní a jsme si toho dobře vědomi. To je důvod, proč představujeme **rozvětvování podgrafů**, vyvinutý společností [LimeChain](https://limechain.tech/), a v tomto článku Ukážu vám, jak lze tuto funkci použít k podstatnému zrychlení ladění podgrafů!
 
 ## Ok, co to je?
 
@@ -12,9 +12,9 @@ V kontextu ladění vám ** vidličkování podgrafů** umožňuje ladit neúsp
 
 ## Co?! Jak?
 
-When you deploy a subgraph to a remote Graph Node for indexing and it fails at block _X_, the good news is that the Graph Node will still serve GraphQL queries using its store, which is synced-up to block _X_. That's great! This means we can take advantage of this "up-to-date" store to fix the bugs arising when indexing block _X_.
+Když nasadíte podgraf do vzdáleného uzlu Graf pro indexování a ten selže v bloku _X_, dobrou zprávou je, že uzel Graf bude stále obsluhovat dotazy GraphQL pomocí svého úložiště, které je synchronizováno s blokem _X_. To je skvělé! To znamená, že můžeme využít tohoto "aktuálního" úložiště k opravě chyb vznikajících při indexování bloku _X_.
 
-In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph Node that is guaranteed to have the subgraph indexed up to block _X_ in order to provide the locally deployed subgraph being debugged at block _X_ an up-to-date view of the indexing state.
+Stručně řečeno, _rozvětvíme neúspěšný podgraf_ ze vzdáleného uzlu grafu, u kterého je zaručeno, že podgraf bude indexován až do bloku *X*, abychom lokálně nasazenému podgrafu laděnému v bloku _X_ poskytli aktuální pohled na stav indexování.
 
 ## Ukažte mi prosím nějaký kód!
 
@@ -44,12 +44,12 @@ export function handleUpdatedGravatar(event: UpdatedGravatar): void {
 }
 ```
 
-Oops, how unfortunate, when I deploy my perfect looking subgraph to [Subgraph Studio](https://thegraph.com/studio/) it fails with the _"Gravatar not found!"_ error.
+Oops, jak nešťastné, když jsem nasadil můj perfektně vypadající podgraf do [Podgraf Studio](https://thegraph.com/studio/), selhalo to s chybou _"Gravatar nenalezen!"_.
 
 Obvyklý způsob, jak se pokusit o opravu, je:
 
 1. Proveďte změnu ve zdroji mapování, která podle vás problém vyřeší (zatímco já vím, že ne).
-2. Re-deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) (or another remote Graph Node).
+2. Znovu nasaďte podgraf do [Subgraph Studio](https://thegraph.com/studio/) (nebo jiného vzdáleného uzlu Graf).
 3. Počkejte na synchronizaci.
 4. Pokud se opět rozbije, vraťte se na 1, jinak: Hurá!
 
@@ -59,7 +59,7 @@ Pomocí **vidličkování podgrafů** můžeme tento krok v podstatě eliminovat
 
 0. Spin-up a local Graph Node with the **_appropriate fork-base_** set.
 1. Proveďte změnu ve zdroji mapování, která podle vás problém vyřeší.
-2. Deploy to the local Graph Node, **_forking the failing subgraph_** and **_starting from the problematic block_**.
+2. Nasazení do místního uzlu Graf, **_forking selhávajícího podgrafu_** a **_zahájení od problematického bloku_**.
 3. Pokud se opět rozbije, vraťte se na 1, jinak: Hurá!
 
 Nyní můžete mít 2 otázky:
@@ -80,7 +80,7 @@ Nezapomeňte také nastavit pole `dataSources.source.startBlock` v manifestu pod
 
 Takže to dělám takhle:
 
-1. I spin-up a local Graph Node ([here is how to do it](https://github.com/graphprotocol/graph-node#running-a-local-graph-node)) with the `fork-base` option set to: `https://api.thegraph.com/subgraphs/id/`, since I will fork a subgraph, the buggy one I deployed earlier, from [Subgraph Studio](https://thegraph.com/studio/).
+1. Spustím místní uzel Graf ([zde je návod, jak to udělat](https://github.com/graphprotocol/graph-node#running-a-local-graph-node)) s volbou `fork-base` nastavenou na: `https://api.thegraph.com/subgraphs/id/`, protože budu forkovat podgraf, ten chybný, který jsem nasadil dříve, z [Podgraph Studio](https://thegraph.com/studio/).
 
 ```
 $ cargo run -p graph-node --release -- \
@@ -91,11 +91,11 @@ $ cargo run -p graph-node --release -- \
 ```
 
 2. Po pečlivém prozkoumání si všímám, že existuje nesoulad v reprezentacích `id`, které se používají při indexaci `Gravatar` v mých dvou obslužných funkcích. Zatímco `handleNewGravatar` ho převede na hex (`event.params.id.toHex()`), `handleUpdatedGravatar` používá int32 (`event.params.id.toI32()`), což způsobuje, že `handleUpdatedGravatar` selže s chybou "Gravatar nenalezen!". Udělám, aby obě převedly `id` na hex.
-3. After I made the changes I deploy my subgraph to the local Graph Node, **_forking the failing subgraph_** and setting `dataSources.source.startBlock` to `6190343` in `subgraph.yaml`:
+3. Po provedení změn jsem nasadil svůj podgraf do místního uzlu Graf, **_rozvětveníl selhávající podgraf_** a nastavil `dataSources.source.startBlock` na `6190343` v `subgraph.yaml`:
 
 ```bash
 $ graph deploy gravity --debug-fork QmNp169tKvomnH3cPXTfGg4ZEhAHA6kEq5oy1XDqAxqHmW --ipfs http://localhost:5001 --node http://localhost:8020
 ```
 
-4. I inspect the logs produced by the local Graph Node and, Hooray!, everything seems to be working.
-5. I deploy my now bug-free subgraph to a remote Graph Node and live happily ever after! (no potatoes tho)
+4. Zkontroluji protokoly vytvořené místním graf uzlem a hurá, zdá se, že vše funguje.
+5. Nasadím svůj nyní již bezchybný podgraf do vzdáleného uzlu Graf a žiji šťastně až do smrti! (bez brambor)

From 06da1cf9da27b804c552cd14015e0b05bba74924 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:36 -0500
Subject: [PATCH 0707/1325] New translations subgraph-debug-forking.mdx
 (Japanese)

---
 website/pages/ja/cookbook/subgraph-debug-forking.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ja/cookbook/subgraph-debug-forking.mdx b/website/pages/ja/cookbook/subgraph-debug-forking.mdx
index a18cf73d17b7..6fbb5070e2ec 100644
--- a/website/pages/ja/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/ja/cookbook/subgraph-debug-forking.mdx
@@ -6,9 +6,9 @@ As with many systems processing large amounts of data, The Graph's Indexers (Gra
 
 ## さて、それは何でしょうか？
 
-**サブグラフのフォーク**とは、*他*のサブグラフのストア(通常はリモート) からエンティティをフェッチするプロセスです。
+**サブグラフのフォーク**とは、_他_のサブグラフのストア(通常はリモート) からエンティティをフェッチするプロセスです。
 
-デバッグの文脈では、**サブグラフのフォーク**により、ブロック*X*への同期を待つことなく、ブロック*X*で失敗したサブグラフのデバッグを行うことができます。
+デバッグの文脈では、**サブグラフのフォーク**により、ブロック_X_への同期を待つことなく、ブロック_X_で失敗したサブグラフのデバッグを行うことができます。
 
 ## その方法は？
 
@@ -69,7 +69,7 @@ Oops, how unfortunate, when I deploy my perfect looking subgraph to [Subgraph St
 
 回答：
 
-1. `fork-base`は「ベース」URLで、*subgraph id*が追加されたときのURL (`<fork-base>/<subgraph-id>`) はサブグラフのストアに対する有効な GraphQL endpoint であることを示します。
+1. `fork-base`は「ベース」URLで、_subgraph id_が追加されたときのURL (`<fork-base>/<subgraph-id>`) はサブグラフのストアに対する有効な GraphQL endpoint であることを示します。
 2. フォーキングは簡単であり煩雑な手間はありません
 
 ```bash

From 9479af21b133f79cd33feacb76e44055c443db37 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:41 -0500
Subject: [PATCH 0708/1325] New translations subgraph-debug-forking.mdx
 (Chinese Simplified)

---
 website/pages/zh/cookbook/subgraph-debug-forking.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/cookbook/subgraph-debug-forking.mdx b/website/pages/zh/cookbook/subgraph-debug-forking.mdx
index 9407cd0d670a..96fdd046a87f 100644
--- a/website/pages/zh/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/zh/cookbook/subgraph-debug-forking.mdx
@@ -6,7 +6,7 @@ As with many systems processing large amounts of data, The Graph's Indexers (Gra
 
 ## 首先，让我们来看什么是子图分叉
 
-**子图分叉** 是从*另一个* 子图的存储（通常是远程存储）中缓慢获取实体的过程。
+**子图分叉** 是从_另一个_ 子图的存储（通常是远程存储）中缓慢获取实体的过程。
 
 在调试时，**subgraph forking** 允许您在固定的区块 _X_ 中调试失败的子图，而无需等待区块同步 _X_。
 

From 68071341b000314eabdd473ec164a5aea0abe762 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:44 -0500
Subject: [PATCH 0709/1325] New translations subgraph-debug-forking.mdx (Hindi)

---
 website/pages/hi/cookbook/subgraph-debug-forking.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/cookbook/subgraph-debug-forking.mdx b/website/pages/hi/cookbook/subgraph-debug-forking.mdx
index da72d452509e..89d0d58605ff 100644
--- a/website/pages/hi/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/hi/cookbook/subgraph-debug-forking.mdx
@@ -8,7 +8,7 @@ As with many systems processing large amounts of data, The Graph's Indexers (Gra
 
 **सबग्राफ फोर्किंग** आलसी ढंग से _दूसरे_ सबग्राफ के स्टोर (आमतौर पर एक परोक्ष सबग्राफ) से इकाइयां को लाने की प्रक्रिया है।
 
-डिबगिंग के संदर्भ में, **सबग्राफ फोर्किंग** आपको ब्लॉक*X* को सिंक-अप करने के लिए बिना प्रतीक्षा किए ब्लॉक _X_ पर अपने विफल सबग्राफ को डीबग करने की अनुमति देता है ।
+डिबगिंग के संदर्भ में, **सबग्राफ फोर्किंग** आपको ब्लॉक_X_ को सिंक-अप करने के लिए बिना प्रतीक्षा किए ब्लॉक _X_ पर अपने विफल सबग्राफ को डीबग करने की अनुमति देता है ।
 
 ## क्या?! कैसे?
 

From 03cae18f1c72377a53f19c8fc680edad586de584 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:45 -0500
Subject: [PATCH 0710/1325] New translations subgraph-debug-forking.mdx
 (Swahili)

---
 .../sw/cookbook/subgraph-debug-forking.mdx    | 101 ++++++++++++++++++
 1 file changed, 101 insertions(+)
 create mode 100644 website/pages/sw/cookbook/subgraph-debug-forking.mdx

diff --git a/website/pages/sw/cookbook/subgraph-debug-forking.mdx b/website/pages/sw/cookbook/subgraph-debug-forking.mdx
new file mode 100644
index 000000000000..6610f19da66d
--- /dev/null
+++ b/website/pages/sw/cookbook/subgraph-debug-forking.mdx
@@ -0,0 +1,101 @@
+---
+title: Quick and Easy Subgraph Debugging Using Forks
+---
+
+As with many systems processing large amounts of data, The Graph's Indexers (Graph Nodes) may take quite some time to sync-up your subgraph with the target blockchain. The discrepancy between quick changes with the purpose of debugging and long wait times needed for indexing is extremely counterproductive and we are well aware of that. This is why we are introducing **subgraph forking**, developed by [LimeChain](https://limechain.tech/), and in this article I will show you how this feature can be used to substantially speed-up subgraph debugging!
+
+## Ok, what is it?
+
+**Subgraph forking** is the process of lazily fetching entities from _another_ subgraph's store (usually a remote one).
+
+In the context of debugging, **subgraph forking** allows you to debug your failed subgraph at block _X_ without needing to wait to sync-up to block _X_.
+
+## What?! How?
+
+When you deploy a subgraph to a remote Graph Node for indexing and it fails at block _X_, the good news is that the Graph Node will still serve GraphQL queries using its store, which is synced-up to block _X_. That's great! This means we can take advantage of this "up-to-date" store to fix the bugs arising when indexing block _X_.
+
+In a nutshell, we are going to _fork the failing subgraph_ from a remote Graph Node that is guaranteed to have the subgraph indexed up to block _X_ in order to provide the locally deployed subgraph being debugged at block _X_ an up-to-date view of the indexing state.
+
+## Please, show me some code!
+
+To stay focused on subgraph debugging, let's keep things simple and run along with the [example-subgraph](https://github.com/graphprotocol/graph-tooling/tree/main/examples/ethereum-gravatar) indexing the Ethereum Gravity smart contract.
+
+Here are the handlers defined for indexing `Gravatar`s, with no bugs whatsoever:
+
+```tsx
+export function handleNewGravatar(event: NewGravatar): void {
+  let gravatar = new Gravatar(event.params.id.toHex().toString())
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+
+export function handleUpdatedGravatar(event: UpdatedGravatar): void {
+  let gravatar = Gravatar.load(event.params.id.toI32().toString())
+  if (gravatar == null) {
+    log.critical('Gravatar not found!', [])
+    return
+  }
+  gravatar.owner = event.params.owner
+  gravatar.displayName = event.params.displayName
+  gravatar.imageUrl = event.params.imageUrl
+  gravatar.save()
+}
+```
+
+Oops, how unfortunate, when I deploy my perfect looking subgraph to [Subgraph Studio](https://thegraph.com/studio/) it fails with the _"Gravatar not found!"_ error.
+
+The usual way to attempt a fix is:
+
+1. Make a change in the mappings source, which you believe will solve the issue (while I know it won't).
+2. Re-deploy the subgraph to [Subgraph Studio](https://thegraph.com/studio/) (or another remote Graph Node).
+3. Wait for it to sync-up.
+4. If it breaks again go back to 1, otherwise: Hooray!
+
+It is indeed pretty familiar to an ordinary debug process, but there is one step that horribly slows down the process: _3. Wait for it to sync-up._
+
+Using **subgraph forking** we can essentially eliminate this step. Here is how it looks:
+
+0. Spin-up a local Graph Node with the **_appropriate fork-base_** set.
+1. Make a change in the mappings source, which you believe will solve the issue.
+2. Deploy to the local Graph Node, **_forking the failing subgraph_** and **_starting from the problematic block_**.
+3. If it breaks again, go back to 1, otherwise: Hooray!
+
+Now, you may have 2 questions:
+
+1. fork-base what???
+2. Forking who?!
+
+And I answer:
+
+1. `fork-base` is the "base" URL, such that when the _subgraph id_ is appended the resulting URL (`<fork-base>/<subgraph-id>`) is a valid GraphQL endpoint for the subgraph's store.
+2. Forking is easy, no need to sweat:
+
+```bash
+$ graph deploy <subgraph-name> --debug-fork <subgraph-id> --ipfs http://localhost:5001 --node http://localhost:8020
+```
+
+Also, don't forget to set the `dataSources.source.startBlock` field in the subgraph manifest to the number of the problematic block, so you can skip indexing unnecessary blocks and take advantage of the fork!
+
+So, here is what I do:
+
+1. I spin-up a local Graph Node ([here is how to do it](https://github.com/graphprotocol/graph-node#running-a-local-graph-node)) with the `fork-base` option set to: `https://api.thegraph.com/subgraphs/id/`, since I will fork a subgraph, the buggy one I deployed earlier, from [Subgraph Studio](https://thegraph.com/studio/).
+
+```
+$ cargo run -p graph-node --release -- \
+    --postgres-url postgresql://USERNAME[:PASSWORD]@localhost:5432/graph-node \
+    --ethereum-rpc NETWORK_NAME:[CAPABILITIES]:URL \
+    --ipfs 127.0.0.1:5001
+    --fork-base https://api.thegraph.com/subgraphs/id/
+```
+
+2. After careful inspection I notice that there is a mismatch in the `id` representations used when indexing `Gravatar`s in my two handlers. While `handleNewGravatar` converts it to a hex (`event.params.id.toHex()`), `handleUpdatedGravatar` uses an int32 (`event.params.id.toI32()`) which causes the `handleUpdatedGravatar` to panic with "Gravatar not found!". I make them both convert the `id` to a hex.
+3. After I made the changes I deploy my subgraph to the local Graph Node, **_forking the failing subgraph_** and setting `dataSources.source.startBlock` to `6190343` in `subgraph.yaml`:
+
+```bash
+$ graph deploy gravity --debug-fork QmNp169tKvomnH3cPXTfGg4ZEhAHA6kEq5oy1XDqAxqHmW --ipfs http://localhost:5001 --node http://localhost:8020
+```
+
+4. I inspect the logs produced by the local Graph Node and, Hooray!, everything seems to be working.
+5. I deploy my now bug-free subgraph to a remote Graph Node and live happily ever after! (no potatoes tho)

From 5c7289bacfdf374006c8c370398940031a653c04 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:47 -0500
Subject: [PATCH 0711/1325] New translations subgraph-studio-faqs.mdx (French)

---
 website/pages/fr/deploying/subgraph-studio-faqs.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/fr/deploying/subgraph-studio-faqs.mdx b/website/pages/fr/deploying/subgraph-studio-faqs.mdx
index ae6da600254d..1ace101654f2 100644
--- a/website/pages/fr/deploying/subgraph-studio-faqs.mdx
+++ b/website/pages/fr/deploying/subgraph-studio-faqs.mdx
@@ -8,7 +8,7 @@ title: Subgraph Studio FAQ
 
 ## 2. Comment créer une clé API ?
 
-To create an API, navigate to Subgraph Studio and connect your wallet. You will be able to click the API keys tab at the top. There, you will be able to create an API key.
+Pour créer une API, allez dans Subgraph Studio et connectez votre portefeuille. Vous pourrez cliquer sur l'onglet des clés API en haut. Là, vous pourrez créer une clé API.
 
 ## 3. Puis-je créer plusieurs clés API ?
 
@@ -20,12 +20,12 @@ Après avoir créé une clé API, dans la section Sécurité, vous pouvez défin
 
 ## Puis-je transférer mon subgraph à un autre propriétaire ?
 
-Yes, subgraphs that have been published to Arbitrum One can be transferred to a new wallet or a Multisig. You can do so by clicking the three dots next to the 'Publish' button on the subgraph's details page and selecting 'Transfer ownership'.
+Oui, les subgraphs qui ont été publiés sur Arbitrum One peuvent être transférés vers un nouveau portefeuille ou un Multisig. Vous pouvez le faire en cliquant sur les trois points à côté du bouton 'Publish' sur la page des détails du subgraph et en sélectionnant 'Transfer ownership'.
 
 Notez que vous ne pourrez plus voir ou modifier le subgraph dans Studio une fois qu'il aura été transféré.
 
 ## Comment trouver les URL de requête pour les sugraphs si je ne suis pas le développeur du subgraph que je veux utiliser ?
 
-You can find the query URL of each subgraph in the Subgraph Details section of Graph Explorer. When you click on the “Query” button, you will be directed to a pane wherein you can view the query URL of the subgraph you’re interested in. You can then replace the `<api_key>` placeholder with the API key you wish to leverage in Subgraph Studio.
+Vous pouvez trouver l'URL de requête de chaque subgraph dans la section Subgraph Details de Graph Explorer. Lorsque vous cliquez sur le bouton "Query", vous serez dirigé vers un volet où vous pourrez voir l'URL de requête du subgraph qui vous intéresse. Vous pouvez ensuite remplacer le placeholder `<api_key>` par la clé API que vous souhaitez utiliser dans Subgraph Studio.
 
 N'oubliez pas que vous pouvez créer une clé API et interroger n'importe quel subgraph publié sur le réseau, même si vous créez vous-même un subgraph. Ces requêtes via la nouvelle clé API, sont des requêtes payantes comme n'importe quelle autre sur le réseau.

From fbca413d19acabf4476d63df2f6468fc5d92f6bc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:54 -0500
Subject: [PATCH 0712/1325] New translations subgraph-studio-faqs.mdx (Russian)

---
 website/pages/ru/deploying/subgraph-studio-faqs.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ru/deploying/subgraph-studio-faqs.mdx b/website/pages/ru/deploying/subgraph-studio-faqs.mdx
index f987b2c4a058..2ca6f958d83e 100644
--- a/website/pages/ru/deploying/subgraph-studio-faqs.mdx
+++ b/website/pages/ru/deploying/subgraph-studio-faqs.mdx
@@ -8,7 +8,7 @@ title: Часто задаваемые вопросы о Subgraph Studio
 
 ## 2. Как создать ключ API?
 
-To create an API, navigate to Subgraph Studio and connect your wallet. You will be able to click the API keys tab at the top. There, you will be able to create an API key.
+Чтобы создать API, перейдите в Subgraph Studio и подключите свой кошелек. Вы сможете щелкнуть вкладку API-ключи вверху. Там Вы сможете создать ключ API.
 
 ## 3. Могу ли я создать несколько ключей API?
 
@@ -20,12 +20,12 @@ To create an API, navigate to Subgraph Studio and connect your wallet. You will
 
 ## 5. Могу ли я передать свой субграф другому владельцу?
 
-Yes, subgraphs that have been published to Arbitrum One can be transferred to a new wallet or a Multisig. You can do so by clicking the three dots next to the 'Publish' button on the subgraph's details page and selecting 'Transfer ownership'.
+Да, субграфы, которые были опубликованы в Arbitrum One, могут быть перенесены в новый кошелек или на кошелек с мультиподписью. Вы можете сделать это, щелкнув три точки рядом с кнопкой «Опубликовать» на странице сведений о субграфе и выбрав «Передать право собственности».
 
 Обратите внимание, что Вы больше не сможете просматривать или редактировать субграф в Studio после его переноса.
 
 ## 6. Как мне найти URL-адреса запросов для субграфов, если я не являюсь разработчиком субграфа, который хочу использовать?
 
-You can find the query URL of each subgraph in the Subgraph Details section of Graph Explorer. When you click on the “Query” button, you will be directed to a pane wherein you can view the query URL of the subgraph you’re interested in. You can then replace the `<api_key>` placeholder with the API key you wish to leverage in Subgraph Studio.
+Вы можете найти URL-адрес запроса каждого субграфа в разделе «Сведения о Субграфе» в Graph Explorer. После нажатия на кнопку «Запрос» Вы будете перенаправлены на панель, где сможете увидеть URL-адрес запроса интересующего Вас субграфа. Затем Вы можете заменить заполнитель `<api_key>` ключом API, который хотите использовать в Subgraph Studio.
 
 Помните, что Вы можете создать ключ API и запрашивать любой субграф, опубликованный в сети, даже если сами создаете субграф. Эти запросы через новый ключ API являются платными, как и любые другие в сети.

From 7061576c8bd9c09869174c6a53a4825e7c1069cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:44:59 -0500
Subject: [PATCH 0713/1325] New translations subgraph-studio-faqs.mdx (Swahili)

---
 .../sw/deploying/subgraph-studio-faqs.mdx     | 31 +++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 website/pages/sw/deploying/subgraph-studio-faqs.mdx

diff --git a/website/pages/sw/deploying/subgraph-studio-faqs.mdx b/website/pages/sw/deploying/subgraph-studio-faqs.mdx
new file mode 100644
index 000000000000..8761f7a31bf6
--- /dev/null
+++ b/website/pages/sw/deploying/subgraph-studio-faqs.mdx
@@ -0,0 +1,31 @@
+---
+title: Subgraph Studio FAQs
+---
+
+## 1. What is Subgraph Studio?
+
+[Subgraph Studio](https://thegraph.com/studio/) is a dapp for creating, managing, and publishing subgraphs and API keys.
+
+## 2. How do I create an API Key?
+
+To create an API, navigate to Subgraph Studio and connect your wallet. You will be able to click the API keys tab at the top. There, you will be able to create an API key.
+
+## 3. Can I create multiple API Keys?
+
+Yes! You can create multiple API Keys to use in different projects. Check out the link [here](https://thegraph.com/studio/apikeys/).
+
+## 4. How do I restrict a domain for an API Key?
+
+After creating an API Key, in the Security section, you can define the domains that can query a specific API Key.
+
+## 5. Can I transfer my subgraph to another owner?
+
+Yes, subgraphs that have been published to Arbitrum One can be transferred to a new wallet or a Multisig. You can do so by clicking the three dots next to the 'Publish' button on the subgraph's details page and selecting 'Transfer ownership'.
+
+Note that you will no longer be able to see or edit the subgraph in Studio once it has been transferred.
+
+## 6. How do I find query URLs for subgraphs if I’m not the developer of the subgraph I want to use?
+
+You can find the query URL of each subgraph in the Subgraph Details section of Graph Explorer. When you click on the “Query” button, you will be directed to a pane wherein you can view the query URL of the subgraph you’re interested in. You can then replace the `<api_key>` placeholder with the API key you wish to leverage in Subgraph Studio.
+
+Remember that you can create an API key and query any subgraph published to the network, even if you build a subgraph yourself. These queries via the new API key, are paid queries as any other on the network.

From b69168404e04af2e2d4c61b8e08ec82c36735745 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:00 -0500
Subject: [PATCH 0714/1325] New translations curating.mdx (Romanian)

---
 website/pages/ro/network/curating.mdx | 56 +++++----------------------
 1 file changed, 9 insertions(+), 47 deletions(-)

diff --git a/website/pages/ro/network/curating.mdx b/website/pages/ro/network/curating.mdx
index fb2107c53884..a5a63f3e2751 100644
--- a/website/pages/ro/network/curating.mdx
+++ b/website/pages/ro/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risks
 
 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version.
    - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,7 +61,7 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. How do I decide which subgraphs are high quality to signal on?
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
 - Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. Can I sell my curation shares?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Price per shares](/img/price-per-share.png)
-
-As a result, price increases linearly, meaning that it will get more expensive to purchase a share over time. Here’s an example of what we mean, see the bonding curve below:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Consider we have two curators that mint shares for a subgraph:
-
-- Curator A is the first to signal on the subgraph. By adding 120,000 GRT into the curve, they are able to mint 2000 shares.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Since both curators hold half the total of curation shares, they would receive an equal amount of curator royalties.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- The remaining curator would now receive all the curator royalties for that subgraph. If they were to burn their shares to withdraw GRT, they would receive 120,000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In the case of The Graph, [Bancor’s implementation of a bonding curve formula](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) is leveraged.
-
 Still confused? Check out our Curation video guide below:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 737f099efbbc8ef131cd2e718159e8f44daf09fa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:01 -0500
Subject: [PATCH 0715/1325] New translations curating.mdx (Spanish)

---
 website/pages/es/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/es/network/curating.mdx b/website/pages/es/network/curating.mdx
index e8cdc12ea206..a11299ddd57e 100644
--- a/website/pages/es/network/curating.mdx
+++ b/website/pages/es/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Un curador puede optar por señalar una versión especifica de un subgrafo, o puede optar por que su señal migre automáticamente a la versión de producción mas reciente de ese subgrafo. Ambas son estrategias válidas y tienen sus pros y sus contras.
 
-Señalar una versión específica es especialmente útil cuando un subgrafo es utilizado por múltiples dApps. Una dApp puede necesitar actualizar regularmente el subgrafo con nuevas características. Otra dApp puede preferir utilizar una versión del subgrafo más antigua y probada. Tras la curación inicial, se incurre en un impuesto estándar del 1%.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Hacer que tu señal migre automáticamente a la más reciente compilación de producción puede ser valioso para asegurarse de seguir acumulando tarifas de consulta. Cada vez que curas, se incurre en un impuesto de curación del 1%. También pagarás un impuesto de curación del 0,5% en cada migración. Se desaconseja a los desarrolladores de Subgrafos que publiquen con frecuencia nuevas versiones - tienen que pagar un impuesto de curación del 0,5% en todas las acciones de curación auto-migradas.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Riesgos
 
 1. El mercado de consultas es inherentemente joven en The Graph y existe el riesgo de que su APY (Rentabilidad anualizada) sea más bajo de lo esperado debido a la dinámica del mercado que recién está empezando.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Un subgrafo puede fallar debido a un error. Un subgrafo fallido no acumula tarifas de consulta. Como resultado, tendrás que esperar hasta que el desarrollador corrija el error e implemente una nueva versión.
    - Si estás suscrito a la versión más reciente de un subgrafo, tus acciones se migrarán automáticamente a esa nueva versión. Esto incurrirá un impuesto de curación del 0.5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. ¿Cómo decido qué subgrafos son de alta calidad para señalar?
 
-Encontrar subgrafos de alta calidad es una tarea compleja, pero se puede abordar de muchas formas diferentes. Como Curador, quieres buscar subgrafos confiables que impulsen el volumen de consultas. Un subgrafo confiable puede ser valioso si es completo, preciso y respalda las necesidades de dicha dApp. Es posible que un subgrafo con una arquitectura deficiente deba revisarse o volver a publicarse, y también puede terminar fallando. Es fundamental que los Curadores revisen la arquitectura o el código de un subgrafo para evaluar si un subgrafo es valioso. Como resultado:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Los curadores pueden usar su conocimiento de una red para intentar predecir cómo un subgrafo puede generar un volumen de consultas mayor o menor a largo plazo
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. What’s the cost of updating a subgraph?
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. ¿Puedo vender mis acciones de curación?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Precio por acciones](/img/price-per-share.png)
-
-Como resultado, el precio aumenta linealmente, lo que significa que con el tiempo resultará más caro comprar una participación. A continuación, se muestra un ejemplo de lo que queremos decir; consulta la bonding curve a continuación:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Imagina que tenemos dos curadores que acuñan acciones para un subgrafo:
-
-- El Curador A es el primero en señalar en el subgrafo. Al agregar 120.000 GRT en la curva, puede acuñar 2000 participaciones.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Dado que ambos curadores poseen la mitad participativa de dicha curación, recibirían una cantidad igual en las recompensas por ser curador.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- El curador restante recibiría todas las recompensas en ese subgrafo. Si quemaran sus participaciones a fin de retirar sus GRT, recibirían 120.000 GRT.
-- **TLDR (en resumen):** La valoración de GRT de las acciones de curación viene determinada por la bonding curva y puede ser volátil. Existe la posibilidad de incurrir grandes pérdidas. Señalar temprano significa que pones menos GRT por cada acción. Por extensión, esto significa que se ganan más derechos de curador por GRT que los curadores posteriores por el mismo subgrafo.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-En el caso de The Graph, se aprovecha [la implementación de una fórmula por parte de Bancor para la bonding curve](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA).
-
 ¿Sigues confundido? Te invitamos a echarle un vistazo a nuestra guía en un vídeo que aborda todo sobre la curación:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 9a43868a470c5878ac963ea699e8ab8e870b217b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:02 -0500
Subject: [PATCH 0716/1325] New translations curating.mdx (Arabic)

---
 website/pages/ar/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/ar/network/curating.mdx b/website/pages/ar/network/curating.mdx
index 09b06f9e3476..970b6fbbc405 100644
--- a/website/pages/ar/network/curating.mdx
+++ b/website/pages/ar/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 يمكن للمنسق الإشارة إلى إصدار معين ل subgraph ، أو يمكنه اختيار أن يتم ترحيل migrate إشاراتهم تلقائيا إلى أحدث إصدار لهذا ال subgraph. كلاهما استراتيجيات سليمة ولها إيجابيات وسلبيات.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## المخاطر
 
 1. سوق الاستعلام يعتبر حديثا في The Graph وهناك خطر من أن يكون٪ APY الخاص بك أقل مما تتوقع بسبب ديناميكيات السوق الناشئة.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. يمكن أن يفشل ال subgraph بسبب خطأ. ال subgraph الفاشل لا يمكنه إنشاء رسوم استعلام. نتيجة لذلك ، سيتعين عليك الانتظار حتى يصلح المطور الخطأ وينشر إصدارا جديدا.
    - إذا كنت مشتركا في أحدث إصدار من subgraph ، فسيتم ترحيل migrate أسهمك تلقائيا إلى هذا الإصدار الجديد. هذا سيتحمل ضريبة تنسيق بنسبة 0.5٪.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. كيف يمكنني تقرير ما إذا كان ال subgraph عالي الجودة لكي أقوم بالإشارة إليه؟
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- يمكن للمنسقين استخدام فهمهم للشبكة لمحاولة التنبؤ كيف لل subgraph أن يولد حجم استعلام أعلى أو أقل في المستقبل
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. What’s the cost of updating a subgraph?
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. هل يمكنني بيع أسهم التنسيق الخاصة بي؟
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## منحنى الترابط 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![سعر السهم](/img/price-per-share.png)
-
-نتيجة لذلك ، يرتفع السعر بثبات ، مما يعني أنه سيكون شراء السهم أكثر تكلفة مع مرور الوقت. فيما يلي مثال لما نعنيه ، راجع منحنى الترابط أدناه:
-
-![منحنى الترابط Bonding curve](/img/bonding-curve.png)
-
-ضع في اعتبارك أن لدينا منسقان يشتركان في Subgraph واحد:
-
-- المنسق (أ) هو أول من أشار إلى ال Subgraphs. من خلال إضافة 120000 GRT إلى المنحنى ، سيكون من الممكن صك 2000 سهم.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- لأن كلا من المنسقين يحتفظان بنصف إجمالي اسهم التنسيق ، فإنهم سيحصلان على قدر متساوي من عوائد المنسقين.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- سيحصل المنسق المتبقي على جميع عوائد المنسق لهذ ال subgraphs. وإذا قام بحرق حصته للحصول علىGRT ، فإنه سيحصل على 120.000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In the case of The Graph, [Bancor’s implementation of a bonding curve formula](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) is leveraged.
-
 لازلت مشوشا؟ راجع فيديو دليل التنسيق أدناه:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From a15c5462654de7b57e43e1a03713663114ca5649 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:03 -0500
Subject: [PATCH 0717/1325] New translations curating.mdx (Czech)

---
 website/pages/cs/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/cs/network/curating.mdx b/website/pages/cs/network/curating.mdx
index 7b10db17c678..d0230e080bdf 100644
--- a/website/pages/cs/network/curating.mdx
+++ b/website/pages/cs/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Kurátor si může zvolit, zda bude signalizovat na konkrétní verzi podgrafu, nebo zda se jeho signál automaticky přenese na nejnovější produkční sestavení daného podgrafu. Obě strategie jsou platné a mají své výhody i nevýhody.
 
-Signalizace na konkrétní verzi je užitečná zejména tehdy, když jeden podgraf používá více dApps. Jedna dApp může potřebovat pravidelně aktualizovat podgraf o nové funkce. Jiná dApp může preferovat používání starší, dobře otestované verze podgrafu. Při počáteční kurátorské úpravě je účtována standardní daň ve výši 1 %.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Automatická migrace signálu na nejnovější produkční sestavení může být cenná, protože zajistí, že se poplatky za dotazy budou neustále zvyšovat. Při každém kurátorství se platí 1% kurátorský poplatek. Při každé migraci také zaplatíte 0,5% kurátorskou daň. Vývojáři podgrafu jsou odrazováni od častého publikování nových verzí - musí zaplatit 0.5% kurátorskou daň ze všech automaticky migrovaných kurátorských podílů.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Rizika
 
 1. Trh s dotazy je v Graf ze své podstaty mladý a existuje riziko, že vaše %APY může být nižší, než očekáváte, v důsledku dynamiky rodícího se trhu.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Podgraf může selhat kvůli chybě. Za neúspěšný podgraf se neúčtují poplatky za dotaz. V důsledku toho budete muset počkat, až vývojář chybu opraví a nasadí novou verzi.
    - Pokud jste přihlášeni k odběru nejnovější verze podgrafu, vaše sdílené položky se automaticky přemigrují na tuto novou verzi. Při tom bude účtována 0,5% kurátorská daň.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. Jak se rozhodnu, které podgrafy jsou kvalitní a na kterých je třeba signalizovat?
 
-Nalezení kvalitních podgrafů je složitý úkol, ale lze k němu přistupovat mnoha různými způsoby. Jako kurátor chcete hledat důvěryhodné podgrafy, které jsou zdrojem objemu dotazů. Důvěryhodný podgraf může být cenný, pokud je úplný, přesný a podporuje datové potřeby dApp. Špatně navržený podgraf může vyžadovat revizi nebo opětovné zveřejnění a může také skončit neúspěchem. Pro kurátory je zásadní, aby přezkoumali architekturu nebo kód podgrafu, aby mohli posoudit, zda je podgraf hodnotný. V důsledku toho:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Kurátoři mohou využít své znalosti sítě k tomu, aby se pokusili předpovědět, jak může jednotlivý podgraf v budoucnu generovat vyšší nebo nižší objem dotazů
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. Jaké jsou náklady na aktualizaci podgrafu?
@@ -78,50 +76,14 @@ Doporučujeme, abyste podgrafy neaktualizovali příliš často. Další podrobn
 
 ### 5. Mohu prodat své kurátorské podíly?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Křivka lepení 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Cena za akcii](/img/price-per-share.png)
-
-V důsledku toho se cena lineárně zvyšuje, což znamená, že nákup akcie bude v průběhu času dražší. Zde je příklad toho, co máme na mysli, viz níže uvedená vazební křivka:
-
-![Křivka lepení](/img/bonding-curve.png)
-
-Uvažujme, že máme dva kurátory, kteří mintují podíly pro podgraf
-
-- Kurátor A signalizuje jako první na podgrafu. Přidáním 120,000 GRT do křivky se jim podaří vydolovat 2000 akcií.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Vzhledem k tomu, že oba kurátoři mají polovinu všech kurátorských podílů, dostávali by stejnou částku kurátorských honorářů.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Zbývající kurátor by nyní obdržel všechny kurátorské honoráře za tento podgraf. Pokud by své podíly spálili a vybrali GRT, získali by 120,000 GRT.
-- **TLDR:** Ocenění kurátorských akcií GRT je určeno vazebnou křivkou a může být volatilní. Existuje potenciál pro vznik velkých ztrát. Včasná signalizace znamená, že do každé akcie vložíte méně GRT. V důsledku to znamená, že vyděláte více kurátorských poplatků za GRT než pozdější kurátoři za stejný podgraf.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-V případě Grafu se využívá [Bankorova implementace vzorce vazební křivky](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA).
-
 Stále jste zmateni? Podívejte se na našeho videoprůvodce kurátorstvím níže
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 715226bc0b8ac881aa5df6faeec4010e16eb3dba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:04 -0500
Subject: [PATCH 0718/1325] New translations curating.mdx (German)

---
 website/pages/de/network/curating.mdx | 56 +++++----------------------
 1 file changed, 9 insertions(+), 47 deletions(-)

diff --git a/website/pages/de/network/curating.mdx b/website/pages/de/network/curating.mdx
index fb2107c53884..a5a63f3e2751 100644
--- a/website/pages/de/network/curating.mdx
+++ b/website/pages/de/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risks
 
 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version.
    - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,7 +61,7 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. How do I decide which subgraphs are high quality to signal on?
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
 - Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. Can I sell my curation shares?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Price per shares](/img/price-per-share.png)
-
-As a result, price increases linearly, meaning that it will get more expensive to purchase a share over time. Here’s an example of what we mean, see the bonding curve below:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Consider we have two curators that mint shares for a subgraph:
-
-- Curator A is the first to signal on the subgraph. By adding 120,000 GRT into the curve, they are able to mint 2000 shares.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Since both curators hold half the total of curation shares, they would receive an equal amount of curator royalties.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- The remaining curator would now receive all the curator royalties for that subgraph. If they were to burn their shares to withdraw GRT, they would receive 120,000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In the case of The Graph, [Bancor’s implementation of a bonding curve formula](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) is leveraged.
-
 Still confused? Check out our Curation video guide below:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From fbb4d9e150bab17851ebf1b56bea098ef86c8bb9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:06 -0500
Subject: [PATCH 0719/1325] New translations curating.mdx (Italian)

---
 website/pages/it/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/it/network/curating.mdx b/website/pages/it/network/curating.mdx
index 20cb357b49b0..b7c0039f86b9 100644
--- a/website/pages/it/network/curating.mdx
+++ b/website/pages/it/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Un curator può scegliere di segnalare su una versione specifica del subgraph, oppure può scegliere di far migrare automaticamente il proprio segnale alla versione di produzione più recente di quel subgraph. Entrambe le strategie sono valide e hanno i loro pro e contro.
 
-La segnalazione di una versione specifica è particolarmente utile quando un subgraph è utilizzato da multipli dApp. Una dApp potrebbe aver bisogno di aggiornare regolarmente il subgraph con nuove funzionalità. Un'altra dApp potrebbe preferire l'uso di una versione più vecchia e ben testata del subgraph. Al momento della curation iniziale, viene applicata una tassa standard del 1%.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 La migrazione automatica del segnale alla più recente versione di produzione può essere utile per garantire l'accumulo di tariffe di query. Ogni volta che si effettua una curation, si paga una tassa di curation del 1%. Si pagherà anche una tassa di curation del 0,5% per ogni migrazione. Gli sviluppatori di subgraph sono scoraggiati dal pubblicare frequentemente nuove versioni: devono pagare una tassa di curation del 0,5% su tutte le quote di curation auto-migrate.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Rischi
 
 1. Il mercato delle query è intrinsecamente giovane per The Graph e c'è il rischio che la vostra %APY possa essere inferiore a quella prevista a causa delle dinamiche di mercato nascenti.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Un subgraph può fallire a causa di un bug. Un subgraph fallito non matura commissioni della query. Di conseguenza, si dovrà attendere che lo sviluppatore risolva il bug e distribuisca una nuova versione.
    - Se siete iscritti alla versione più recente di un subgraph, le vostre quote di partecipazione migreranno automaticamente a quella nuova versione. Questo comporta una tassa di curation di 0,5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. Come si fa a decidere quali subgraph sono di alta qualità da segnalare?
 
-Trovare subgraph di alta qualità è un compito complesso, ma può essere affrontato in molti modi diversi. Come Curator, si desidera cercare subgraph affidabili che generano un volume di query. Un subgraph affidabile può essere utile se è completo, accurato e supporta le esigenze di dati di una dApp. Un subgraph mal progettato potrebbe dover essere rivisto o ripubblicato e potrebbe anche finire per fallire. È fondamentale che i Curator rivedano l'architettura o il codice di un subgraph per valutarne il valore. Di conseguenza:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- I curator possono utilizzare la loro comprensione di una rete per cercare di prevedere come un singolo subgraph possa generare un volume di query più o meno elevato in futuro
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. Qual è il costo dell'aggiornamento di un subgraph?
@@ -78,50 +76,14 @@ Si suggerisce di non aggiornare i subgraph troppo frequentemente. Si veda la dom
 
 ### 5. Posso vendere le mie quote di curation?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Prezzo per quote di partecipazione](/img/price-per-share.png)
-
-Di conseguenza, il prezzo aumenta linearmente, il che significa che l'acquisto di una quota diventerà più costoso nel tempo. Ecco un esempio di ciò che intendiamo, vedi la curva di legame qui sotto:
-
-![Curva di legame](/img/bonding-curve.png)
-
-Si consideri che abbiamo due curation che coniano quote di partecipazione per un subgraph:
-
-- Il curator A è il primo a segnalare il subgraph. Aggiungendo 120,000 GRT alla curva, riesce a coniarne 2000 quote di partecipazione.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Dal momento che entrambi i curator detengono la metà del totale delle quote di curation, riceveranno una quantità uguale di royalties di curation.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Il curator rimanente riceverebbe ora tutte le royalties di curation per quel subgraph. Se dovessero bruciare le loro quote per ritirare GRT, riceverebbero 120.000 GRT.
-- **TLDR:** La valutazione del GRT delle quote di curation è determinata dalla curva di legame e può essere volatile. È possibile subire grosse perdite. Segnalare in anticipo significa investire meno GRT per ogni quota di partecipazione. Per estensione, ciò significa che si guadagnano più royalties di curation per GRT rispetto ai curator successivi per lo stesso subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-Nel caso di The Graph, [l'implementazione da parte di Bancor della formula della curva di legame](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) viene sfruttata.
-
 Ancora confusi? Date un'occhiata alla nostra video-guida sulla Curation:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 1ee3a237ad3d887963b6b3cb8272ba20502d0488 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:07 -0500
Subject: [PATCH 0720/1325] New translations curating.mdx (Japanese)

---
 website/pages/ja/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/ja/network/curating.mdx b/website/pages/ja/network/curating.mdx
index e961e914c063..1415887e0b70 100644
--- a/website/pages/ja/network/curating.mdx
+++ b/website/pages/ja/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 キュレーターは、特定のサブグラフのバージョンでシグナルを出すことも、そのサブグラフの最新のプロダクションビルドに自動的にシグナルを移行させることも可能ですます。 どちらも有効な戦略であり、それぞれに長所と短所があります。
 
-特定のバージョンでのシグナリングは、1 つのサブグラフを複数の dapps が使用する場合に特に有効です。 ある DAP は、サブグラフを定期的に新機能で更新する必要があるかもしれません。 別のアプリは、古くても、よくテストされたサブグラフのバージョンを使用することを好むかもしれません。 初回キュレーション時には、1％の標準税が発生します。
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 シグナルを最新のプロダクションビルドに自動的に移行させることは、クエリー料金の発生を確実にするために有効です。 キュレーションを行うたびに、1％のキュレーション税が発生します。 また、移行ごとに 0.5%のキュレーション税を支払うことになります。 つまり、サブグラフの開発者が、頻繁に新バージョンを公開することは推奨されません。 自動移行された全てのキュレーションシェアに対して、0.5%のキュレーション税を支払わなければならないからです。
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## リスク
 
 1. The Graph では、クエリ市場は本質的に歴史が浅く、初期の市場ダイナミクスのために、あなたの%APY が予想より低くなるリスクがあります。
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. サブグラフはバグで失敗することがあります。 失敗したサブグラフは、クエリフィーが発生しません。 結果的に、開発者がバグを修正して新しいバージョンを展開するまで待たなければならなくなります。
    - サブグラフの最新バージョンに加入している場合、シェアはその新バージョンに自動移行します。 これには 0.5％のキュレーション税がかかります。
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. シグナルを出すのに適した質の高いサブグラフはどのようにして決めるのですか？
 
-高品質のサブグラフを見つけるのは複雑な作業ですが、さまざまな方法でアプローチできます。 キュレーターとしては、クエリボリュームを牽引している信頼できるサブグラフを探したいと考えます。 信頼できるサブグラフは、それが完全で正確であり、Dap のデータニーズをサポートしていれば価値があるかもしれません。 アーキテクチャが不十分なサブグラフは、修正や再公開が必要になるかもしれませんし、失敗に終わることもあります。 キュレーターにとって、サブグラフが価値あるものかどうかを評価するために、サブグラフのアーキテクチャやコードをレビューすることは非常に重要です。 その結果として：
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- キュレーターはネットワークの理解を利用して、個々のサブグラフが将来的にどのように高いまたは低いクエリボリュームを生成するかを予測することができます。
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. サブグラフの更新にかかるコストはいくらですか?
@@ -78,50 +76,14 @@ Migrating your curation shares to a new subgraph version incurs a curation tax o
 
 ### 5. キュレーションのシェアを売却することはできますか？
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## ボンディングカーブ 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![シェアあたりの価格](/img/price-per-share.png)
-
-その結果、価格は直線的に上昇し、時間の経過とともにシェアの購入価格が高くなることを意味しています。 下のボンディングカーブを見て、その例を示します：
-
-![ボンディングカーブ](/img/bonding-curve.png)
-
-あるサブグラフのシェアを作成する 2 人のキュレーターがいるとします。
-
-- キュレーター A は、サブグラフに最初にシグナルを送ります。 120,000GRT をボンディングカーブに加えることで、2000 もシェアをミントすることができます。
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- 両方のキュレーターがキュレーションシェアの合計の半分を保有しているので、彼らは同額のキュレーターロイヤルティを受け取ることになります。
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- 残りのキュレーターは、そのサブグラフのキュレーター・ロイヤリティーをすべて受け取ることになります。 もし彼らが自分のシェアをバーンして GRT を引き出す場合、彼らは 120,000GRT を受け取ることになります。
-- **TLDR:** キュレーションシェアの GRT 評価はボンディングカーブによって決まるため、変動しやすいという傾向があります。 また、大きな損失を被る可能性があります。 早期にシグナリングするということは、1 つのシェアに対してより少ない GRT を投入することを意味します。 ひいては、同じサブグラフの後続のキュレーターよりも、GRT あたりのキュレーター・ロイヤリティーを多く得られることになります。
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-The Graph の場合は、 [Bancor が実装しているボンディングカーブ式](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) を活用しています。
-
 まだ不明点がありますか？ その他の不明点に関しては、 以下のキュレーションビデオガイドをご覧ください：
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From c98ee630926a04cddcd44885c7523dcd8042661e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:08 -0500
Subject: [PATCH 0721/1325] New translations curating.mdx (Korean)

---
 website/pages/ko/network/curating.mdx | 56 +++++----------------------
 1 file changed, 9 insertions(+), 47 deletions(-)

diff --git a/website/pages/ko/network/curating.mdx b/website/pages/ko/network/curating.mdx
index fb2107c53884..a5a63f3e2751 100644
--- a/website/pages/ko/network/curating.mdx
+++ b/website/pages/ko/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risks
 
 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version.
    - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,7 +61,7 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. How do I decide which subgraphs are high quality to signal on?
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
 - Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. Can I sell my curation shares?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Price per shares](/img/price-per-share.png)
-
-As a result, price increases linearly, meaning that it will get more expensive to purchase a share over time. Here’s an example of what we mean, see the bonding curve below:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Consider we have two curators that mint shares for a subgraph:
-
-- Curator A is the first to signal on the subgraph. By adding 120,000 GRT into the curve, they are able to mint 2000 shares.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Since both curators hold half the total of curation shares, they would receive an equal amount of curator royalties.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- The remaining curator would now receive all the curator royalties for that subgraph. If they were to burn their shares to withdraw GRT, they would receive 120,000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In the case of The Graph, [Bancor’s implementation of a bonding curve formula](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) is leveraged.
-
 Still confused? Check out our Curation video guide below:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From e24d77770c629c70ef89c8fadc180a8ef64eec56 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:09 -0500
Subject: [PATCH 0722/1325] New translations curating.mdx (Dutch)

---
 website/pages/nl/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/nl/network/curating.mdx b/website/pages/nl/network/curating.mdx
index 870fc3f4e54e..3e64881ac6eb 100644
--- a/website/pages/nl/network/curating.mdx
+++ b/website/pages/nl/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Een curator kan ervoor kiezen om een signaal af te geven voor een specifieke subgraph versie, of ze kunnen ervoor kiezen om hun signaal automatisch te laten migreren naar de nieuwste versie van de subgraph. Beide strategieën hebben voordelen en nadelen.
 
-Signaleren voor een specifieke versie is vooral handig wanneer één subgraph door meerdere dApps wordt gebruikt. Sommige dApps moeten de subgraph mogelijk regelmatig bijwerken met nieuwe functies. Andere dApps hebben mogelijk de voorkeur om een oudere, goed geteste subgraphversie te gebruiken. Bij de initiële curatie wordt een standaardbelasting van 1% in rekening gebracht.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Automatische migratie van je signalering naar de nieuwste subgraphversie kan waardevol zijn om ervoor te zorgen dat je querykosten blijft ontvangen. Elke keer dat je signaleert, wordt een curatiebelasting van 1% in rekening gebracht. Je betaalt ook een curatiebelasting van 0,5% bij elke migratie. Subgraphontwikkelaars worden ontmoedigd om vaak nieuwe versies te publiceren - ze moeten een curatiebelasting van 0,5% betalen voor alle automatisch gemigreerde curatie-aandelen.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risico's
 
 1. De querymarkt is nog jong bij het Graph Netwerk en er bestaat een risico dat je %APY lager kan zijn dan je verwacht door opkomende marktdynamiek.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Een subgraph kan stuk gaan door een bug. Een subgraph die stuk is gegenereerd geen querykosten. Als gevolg hiervan moet je wachten tot de ontwikkelaar de bug repareert en een nieuwe versie implementeert.
    - Als je bent geabonneerd op de nieuwste versie van een subgraph, worden je curatieaandelen automatisch gemigreerd naar die nieuwe versie. Er is een curatiebelasting van 0,5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### Hoe bepaal ik welke subgraphs van hoge kwaliteit zijn om op te signaleren?
 
-Het vinden van subgraphs van hoge kwaliteit is een complexe taak, maar het kan op vele verschillende manieren worden benadert. Als curator wil je op zoek gaan naar betrouwbare subgraphs die veel queries genereren. Een betrouwbare subgraph kan waardevol zijn als deze compleet, nauwkeurig is en voldoet aan de gegevensbehoeften van een dApp. Een slecht geconstrueerde subgrafiek moet mogelijk worden herzien of opnieuw worden gepubliceerd en kan ook stuk gaan. Het is essentieel voor curatoren om de architectuur of code van een subgraph te beoordelen om te bepalen of een subgraph waardevol is. Als gevolg daarvan kunnen curatoren:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Hun begrip van een netwerk gebruiken om te proberen voorspellen hoe een individuele subgraph in de toekomst mogelijk een hoger of lager queryvolume zal genereren
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### Wat zijn de kosten voor het updaten van een subgraph?
@@ -78,50 +76,14 @@ Het wordt aanbevolen om je subgraphs niet te vaak bij te werken. Zie de bovensta
 
 ### Kan ik mijn curatieaandelen verkopen?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Prijs per aandeel](/img/price-per-share.png)
-
-Hierdoor neemt de prijs lineair toe, wat betekent dat het in de loop van de tijd duurder wordt om een curatie-aandeel te kopen. Voor een voorbeeld van wat we precies bedoelen, zie de bonding curve hieronder:
-
-![Bonding Curve](/img/bonding-curve.png)
-
-Stel dat we twee curatoren hebben die curatie-aandelen voor een subgraph maken:
-
-- Curator A is de eerste die signaleert op de subgraph. Door 120.000 GRT aan de curve toe te voegen, kan hij 2000 aandelen maken.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Aangezien beide curatoren de helft van het totale aantal curatie-aandelen hebben, zullen ze een gelijke hoeveelheid curator royalties ontvangen.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- De overgebleven curator zou nu alle curator royalties voor die subgraph ontvangen. Als ze hun aandelen zouden "burnen" om GRT op te nemen, zouden ze 120.000 GRT ontvangen.
-- **Samenvattend:** De GRT-waardering van curatie-aandelen wordt bepaald door de bonding curve en kan volatiel zijn. Er is een mogelijkheid om grote verliezen te leiden. Vroeg signaleren betekent dat je minder GRT inlegt voor elk aandeel. Als gevolg hiervan verdien je meer curator royalties per GRT dan latere curatoren voor dezelfde subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In het geval van The Graph wordt gebruik gemaakt van de implementatie van een [bonding curve-formule van Bancor.](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA).
-
 Nog in de war? Bekijk onze Curatie videogids hieronder:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 53e3f1ab035b7a723384a9c976d410af15c5244f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:10 -0500
Subject: [PATCH 0723/1325] New translations curating.mdx (Polish)

---
 website/pages/pl/network/curating.mdx | 56 +++++----------------------
 1 file changed, 9 insertions(+), 47 deletions(-)

diff --git a/website/pages/pl/network/curating.mdx b/website/pages/pl/network/curating.mdx
index fb2107c53884..a5a63f3e2751 100644
--- a/website/pages/pl/network/curating.mdx
+++ b/website/pages/pl/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risks
 
 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version.
    - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,7 +61,7 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. How do I decide which subgraphs are high quality to signal on?
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
 - Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. Can I sell my curation shares?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Price per shares](/img/price-per-share.png)
-
-As a result, price increases linearly, meaning that it will get more expensive to purchase a share over time. Here’s an example of what we mean, see the bonding curve below:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Consider we have two curators that mint shares for a subgraph:
-
-- Curator A is the first to signal on the subgraph. By adding 120,000 GRT into the curve, they are able to mint 2000 shares.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Since both curators hold half the total of curation shares, they would receive an equal amount of curator royalties.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- The remaining curator would now receive all the curator royalties for that subgraph. If they were to burn their shares to withdraw GRT, they would receive 120,000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-In the case of The Graph, [Bancor’s implementation of a bonding curve formula](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) is leveraged.
-
 Still confused? Check out our Curation video guide below:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 43c5ea1f57727cf32ad4c566767f0340d1939842 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:12 -0500
Subject: [PATCH 0724/1325] New translations curating.mdx (Portuguese)

---
 website/pages/pt/network/curating.mdx | 60 +++++----------------------
 1 file changed, 11 insertions(+), 49 deletions(-)

diff --git a/website/pages/pt/network/curating.mdx b/website/pages/pt/network/curating.mdx
index 852fc054dd5d..89fc295d4c15 100644
--- a/website/pages/pt/network/curating.mdx
+++ b/website/pages/pt/network/curating.mdx
@@ -8,9 +8,7 @@ Curadores são importantes para a economia descentralizada do The Graph. Eles ut
 
 Antes que consumidores possam indexar um subgraph, ele deve ser indexado. É aqui que entra a curadoria. Para que Indexadores ganhem taxas de query substanciais em subgraphs de qualidade, eles devem saber quais subgraphs indexar. Quando Curadores sinalizam um subgraph, isto diz aos Indexadores que um subgraph está em demanda e tem qualidade suficiente para ser indexado.
 
-Os Indexadores podem confiar no sinal de um Curador porque ao sinalizar, Curadores mintam uma ação de curadoria para o subgraph, o que dá aos Curadores uma porção de taxas de query futuras que o subgraph move.
-
-Curadores dão eficiência à Graph Network, e a [sinalização](#how-to-signal) é o processo que curadores usam para dizer aos Indexadores que um subgraph é bom para indexar; onde GRT é adicionado a uma bonding curve para um subgraph. Os Indexadores podem confiar no sinal de um Curador porque ao sinalizar, Curadores mintam uma ação de curadoria para o subgraph, o que dá aos Curadores uma porção de taxas de query futuras que o subgraph move.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Sinais de curador são representados como tokens ERC20 chamados de Ações de Curadoria do Graph (GCS). Quem quiser ganhar mais taxas de query devem sinalizar o seu GRT a subgraphs que apostam que gerará um fluxo forte de taxas á rede. Curadores não podem ser cortados por mau comportamento, mas há uma taxa de depósito em Curadores para desincentivar más decisões que possam ferir a integridade da rede. Curadores também ganharão menos taxas de query se curarem um subgraph de baixa qualidade, já que haverão menos queries a processar ou menos Indexadores para processá-las.
 
@@ -18,7 +16,7 @@ O [Indexador de Atualização do Nascer do Sol](/sunrise/#what-is-the-upgrade-in
 
 Ao sinalizar, Curadores podem decidir entre sinalizar numa versão específica do subgraph ou sinalizar com a automigração. Caso sinalizem com a automigração, as ações de um curador sempre serão atualizadas à versão mais recente publicada pelo programador. Se decidirem sinalizar numa versão específica, as ações sempre permanecerão nesta versão específica.
 
-Para ajudar equipas que transitam subgraphs do serviço hospedado à Graph Network, o suporte da curadoria foi lançado. Se precisar de ajuda com curadoria para melhorar a qualidade do serviço, mande um pedido à equipa da Edge & Node em support@thegraph.zendesk.com e especifique os subgraphs com os quais você precisa de ajuda.
+Se precisar de ajuda com a curadoria para melhorar a qualidade do serviço, mande um pedido à equipa da Edge & Node em support@thegraph.zendesk.com e especifique os subgraphs com que precisa de ajuda.
 
 Os indexadores podem achar subgraphs para indexar com base em sinais de curadoria que veem no Graph Explorer (imagem abaixo).
 
@@ -30,11 +28,11 @@ Dentro da aba Curator (Curador) no Graph Explorer, os curadores poderão sinaliz
 
 Um curador pode escolher sinalizar uma versão específica de subgraph, ou pode automaticamente migrar o seu sinal à versão mais recente desse subgraph. Ambas estratégias são válidas, e vêm com as suas próprias vantagens e desvantagens.
 
-Sinalizar numa versão específica serve muito mais quando um subgraph é usado por vários dApps. Um dApp pode precisar atualizar o subgraph regularmente com novos recursos; Outro dApp pode preferir usar uma versão mais antiga, porém mais testada. Na curadoria inicial, é incorrida uma taxa de 1%.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Ter um sinal que migra automaticamente à build mais recente de um subgraph pode ser bom para garantir o acúmulo de taxas de consulta. Toda vez que cura, é incorrida uma taxa de 1% de curadoria. Também pagará uma taxa de 0.5% em toda migração. É recomendado que rogramadores de subgraphs evitem editar novas versões com frequência - eles devem pagar uma taxa de curadoria de 0.5% em todas as ações de curadoria auto-migradas.
 
-> **Nota:** O primeiro endereço a sinalizar um subgraph particular é considerado o primeiro curador e deverá realizar tarefas muito mais intensivas em gas do que o resto dos seguintes curadores — porque o primeiro curador inicializa os tokens de ação de curadoria, inicializa o bonding curve (até no Arbitrum), e também transfere tokens no proxy do Graph.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Como Sacar o Seu GRT
 
@@ -49,8 +47,8 @@ Porém, é recomendado que curadores deixem o seu GRT no lugar, não apenas para
 ## Riscos
 
 1. O mercado de consulta é jovem por natureza no The Graph, e há sempre o risco do seu rendimento anual ser menor que o esperado devido às dinâmicas nascentes do mercado.
-2. Taxa de Curadoria — quando um curador sinaliza GRT em um subgraph, ele incorre uma taxa de 1% de curadoria. Esta taxa é queimada, e o resto é depositado na reserva da bonding curve.
-3. (Só para o Ethereum) Quando os curadores queimam as suas ações para sacar GRT, o valor das ações restantes em GRT é diminuído. Saiba que, em alguns casos, os curadores podem decidir queimar todas as suas ações **de uma vez só**. Isto pode ser comum se um programador de dApp parar de versionar/melhorar e consultar seu subgraph, ou se um subgraph falhar. Portanto, os curadores restantes podem não poder sacar mais do que uma fração do seu GRT inicial. Para um papel de rede com um perfil de risco menor, veja [Delegados](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Um subgraph pode falhar devido a um erro de código. Um subgraph falho não acumula taxas de consulta. Portanto, espere até o programador consertar o erro e lançar uma nova versão.
    - Caso se inscreva à versão mais recente de um subgraph, suas ações migrarão automaticamente a esta versão nova. Isto incorrerá uma taxa de curadoria de 0.5%.
    - Se sinalizou em um subgraph específico e ele falhou, deverá queimar as suas ações de curadoria manualmente. Será então possível sinalizar na nova versão do subgraph, o que incorre uma taxa de curadoria de 1%.
@@ -63,10 +61,10 @@ Ao sinalizar em um subgraph, ganhará parte de todas as taxas de query geradas p
 
 ### 2. Como decidir quais subgraphs são de qualidade alta para sinalizar?
 
-Achar subgraphs de alta qualidade é uma tarefa complexa, mas ela pode ser abordada de várias formas diferentes. Como Curador, vale procurar subgraphs com boa reputação que movem volumes de consulta. Um subgraph confiável pode ser valioso se for completo, preciso, e apoiar as necessidades de dados de um dApp. Um subgraph mal arquitetado pode precisar de revisão ou reedição, e também tem risco de falhar. É crítico que os Curadores verifiquem a arquitetura ou código de um subgraph, para avaliar se ele é valioso. Portanto:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Os curadores podem usar o seu conhecimento de uma rede para tentar prever como um subgraph individual pode gerar um volume maior ou menor de queries no futuro
-- Os curadores também devem entender as métricas disponíveis através do Graph Explorer. Métricas como volume passado de consultas e quem é o programador do subgraph podem ajudar a determinar se um subgraph vale ou não o sinal.
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
+- Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. Qual o custo de atualizar um subgraph?
 
@@ -78,50 +76,14 @@ Não atualize os seus subgraphs com frequência excessiva. Veja a questão acima
 
 ### 5. Posso vender as minhas ações de curadoria?
 
-Ações de curadoria não podem ser "compradas" ou "vendidas", como outros tokens ERC20 que você deve conhecer. Eles só podem ser cunhados (criados) ou queimados (destruídos) dentro da bonding curve para um subgraph particular. A quantidade de GRT necessária para cunhar um novo sinal, e a quantidade de GRT que você recebe ao queimar o seu sinal existente, são determinados por aquela bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- Como um Curador no Ethereum, você precisa saber que quando queimar as suas ações de curadoria para sacar GRT, pode acabar com mais ou menos GRT do que o depositado inicialmente.
-- Como um Curador no Arbitrum, é garantido que você receberá o GRT que depositou inicialmente (menos a taxa).
+Como um Curador no Arbitrum, é garantido que você receberá o GRT que depositou inicialmente (menos a taxa).
 
 ### 6. Tenho direito a uma bolsa de curadoria?
 
 Bolsas de curadoria são determinadas individualmente. Se precisar de ajuda com a curadoria, entre em contacto em support@thegraph.zendesk.com.
 
-## Diferenças Entre Curar no Ethereum x Arbitrum
-
-O comportamento do mecanismo de curadoria difere com base no lançamento da chain do protocolo, particularmente, como o preço de uma ação de subgraph é calculado.
-
-O lançamento original da Graph Network no Ethereum usa bonding curves para determinar o preço de ações: **o preço de cada ação de subgraph aumenta com cada token investido** e **o preço de cada ação diminui com cada token vendido.** Isto significa que a curadoria coloca o seu principal em risco, já que não há garantia de poder vender as suas ações e retornar o seu investimento original.
-
-No Arbitrum, curar subgraphs fica muito mais simples. As bonding curves são "achatadas" e o seu efeito é anulado, o que significa que nenhum Curador poderá realizar ganhos à custa dos outros. Isto permite que Curadores sinalizem ou dessinalizem em subgraphs a qualquer hora, a um custo consistente e com risco muito limitado.
-
-Se tens interesse em curar no Ethereum e quer entender os detalhes de bonding curves e seus efeitos, veja [Bonding Curve 101](#bonding-curve-101). Seja diligente; garanta que curará subgraphs de confiança. Criar um subgraph é um processo livre de permissões, para que o povo possa criar subgraphs e chamá-los do nome que quiser. Para mais conselhos sobre riscos de curadoria, confira o [Guia de Curadoria da Graph Academy.](https://thegraph.academy/curators/)
-
-## Os Básicos da Bonding Curve
-
-> **Nota**: esta secção só se aplica à curadoria no Ethereum, já que bonding curves são planas e não têm efeito no Arbitrum.
-
-Todo subgraph tem uma bonding curve, onde são cunhadas ações de curadoria quando um usuário adiciona sinais **dentro** da curva. A bonding curve de cada subgraph é única; cada curve é arquitetada para que o preço da cunhagem de uma ação de curadoria num subgraph cresça de forma linear, sobre o número de ações cunhadas.
-
-![Preço por ações](/img/price-per-share.png)
-
-Como resultado, o preço aumenta de forma linear, o que significa que a compra de uma ação ficará mais cara temporalmente. Aqui está um exemplo; veja a bonding curve abaixo:
-
-![Bonding curve](/img/bonding-curve.png)
-
-Considere que temos dois curadores que cunham ações para um subgraph:
-
-- O Curador A é o primeiro a sinalizar no subgraph. Ao adicionar 120.000 GRT à curve, ele pode cunhar 2000 ações.
-- O sinal do Curador B chega no subgraph algum tempo depois. Para receber a mesma quantidade de ações que o Curador A, ele deveria adicionar 360.000 na curve.
-- Como ambos os curadores têm metade do total das ações de curadoria, eles receberiam uma quantia igual de ‘royalties’ de curadoria.
-- Se qualquer curador resolvesse queimar as suas 2000 ações de curadoria, ele receberia 360.000 GRT.
-- O curador restante passaria a receber todos os ‘royalties’ de curadoria daquele subgraph. Caso ele queimasse as suas ações para sacar GRT, ele receberia 120.000 GRT.
-- **RESUMINDO:** A valorização em GRT de ações de curadoria é determinada pela bonding curve, e pode ser volátil. Há o potencial para grandes prejuízos. Sinalizar precocemente significa que você coloca menos GRT para cada ação. Por tabela, isto significa que ganhas mais royalties de curadoria por GRT do que curadores que chegarem mais tarde para o mesmo subgraph.
-
-Em geral, uma bonding curve é uma curva matemática que define o relacionamento entre a reserva de token e o preço do ativo. No caso específico de curadoria de subgraphs, **o preço de cada ação de subgraph aumenta com cada token investido** e o **preço de cada ação cai com cada token vendido.**
-
-No caso do The Graph, é usada [a implementação da Bancor de uma fórmula de bonding curve](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA).
-
 Ainda não percebeu? Confira o nosso guia em vídeo sobre a Curadoria abaixo:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From f7cd62cee5af27adc971feae1c67525b988619a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:13 -0500
Subject: [PATCH 0725/1325] New translations curating.mdx (Russian)

---
 website/pages/ru/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/ru/network/curating.mdx b/website/pages/ru/network/curating.mdx
index d00988571920..1d05b5c92262 100644
--- a/website/pages/ru/network/curating.mdx
+++ b/website/pages/ru/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Куратор может выбрать конкретную версию подграфа для сигнализации, или же он может выбрать автоматическую миграцию своего сигнала на самую новую рабочую сборку этого подграфа. Оба варианта являются допустимыми стратегиями и имеют свои плюсы и минусы.
 
-Сигнализация на конкретной версии особенно полезна, когда один подграф используется несколькими dApps. Одному dApp может потребоваться регулярно обновлять подграф новыми функциями. Другой dApp может предпочесть использовать старую, хорошо протестированную версию подграфа. При первоначальной курации взимается стандартная комиссия в размере 1%.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Автоматическая миграция вашего сигнала на самую новую рабочую сборку может быть ценной, чтобы гарантировать непрерывное начисление комиссий за запросы. Каждый раз, когда вы осуществляете курирование, взимается комиссия в размере 1%. Вы также заплатите комиссию в размере 0,5% при каждой миграции. Разработчикам подграфов не рекомендуется часто публиковать новые версии - они должны заплатить комиссию на курирование в размере 0,5% на все автоматически мигрированные доли курации.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Риски
 
 1. Рынок запросов в The Graph по своей сути молод, и существует риск того, что ваш %APY может оказаться ниже, чем вы ожидаете, из-за зарождающейся динамики рынка.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Подграф может выйти из строя из-за ошибки. За неудавшийся подграф не начисляется плата за запрос. В результате вам придется ждать, пока разработчик исправит ошибку и выложит новую версию.
    - Если вы подписаны на новейшую версию подграфа, ваши общие ресурсы автоматически перейдут на эту новую версию. При этом будет взиматься кураторская комиссия в размере 0,5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. Как определить, какие подграфы являются высококачественными, чтобы подавать на них сигналы?
 
-Поиск высококачественных подграфов — это сложная задача, но её можно решить множеством различных способов. Как куратор, вы хотите искать надежные подграфы, которые генерируют объем запросов. Надежный подграф может быть ценным, если он полный, точный и удовлетворяет потребности dApp в данных. Плохо спроектированный подграф может потребовать пересмотра или повторной публикации и также может потерпеть неудачу. Критически важно для кураторов изучать архитектуру или код подграфа, чтобы оценить его ценность. В результате:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Кураторы могут использовать свое понимание сети, чтобы попытаться предсказать, как отдельный подграф может генерировать больший или меньший объем запросов в будущем
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. Какова стоимость обновления подграфа?
@@ -78,50 +76,14 @@ Migrating your curation shares to a new subgraph version incurs a curation tax o
 
 ### 5. Могу ли я продать свои кураторские доли?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bonding Curve 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Price per shares](/img/price-per-share.png)
-
-В результате цена растет линейно, а это означает, что со временем покупка акции станет дороже. Вот пример того, что мы имеем в виду, см. кривую связи ниже:
-
-![Кривая связи](/img/bonding-curve.png)
-
-Предположим, у нас есть два куратора, которые минтят доли для субграфа:
-
-- Куратор "А" первым сигнализирует о подграфе. Добавив 120 000 GRT на кривую, он может создать 2000 долей.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Поскольку оба куратора имеют половину от общего числа, они получат равное количество наград.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Оставшийся куратор теперь будет получать всё вознаграждение для этого подграфа. Если он сожжет свои для вывода GRT, он получит 120 000 GRT.
-- **TLDR:** Оценка GRT кураторских позиций определяется кривой связи и может быть волатильной. Есть вероятность понести большие потери. Если вы подадите сигнал раньше, это означает, что вы вложите меньше GRT за каждую отдельную долю. В свою очередь это означает, что вы получаете больше кураторских роялти на GRT, чем более поздние кураторы для того же субграфа.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-В случае с The Graph используется разработанная компанией [Bancor формула кривой связи](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA).
-
 Вы все еще в замешательстве? Ознакомьтесь с нашим видеоруководством по кураторству:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 0c790358c37edb392460dde4d43d517fbe51abd4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:14 -0500
Subject: [PATCH 0726/1325] New translations curating.mdx (Swedish)

---
 website/pages/sv/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/sv/network/curating.mdx b/website/pages/sv/network/curating.mdx
index 23a394b3a1a1..89b3b4d392f3 100644
--- a/website/pages/sv/network/curating.mdx
+++ b/website/pages/sv/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 En kurator kan välja att signalera på en specifik subgrafversion, eller så kan de välja att ha sin signal automatiskt migrerad till den nyaste produktionsversionen av den subgrafen. Båda är giltiga strategier och har sina egna för- och nackdelar.
 
-Att signalera på en specifik version är särskilt användbart när en subgraf används av flera dApps. En dApp kan behöva regelbundet uppdatera subgrafen med nya funktioner. En annan dApp kan föredra att använda en äldre, väldokumenterad subgrafversion. Vid initial kurering åläggs en standardavgift på 1%.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Att ha din signal automatiskt migrerad till den nyaste produktionsversionen kan vara värdefullt för att säkerställa att du fortsätter att ackumulera frågeavgifter. Varje gång du signalerar åläggs en kuratoravgift på 1%. Du kommer också att betala en kuratoravgift på 0,5% vid varje migration. Subgrafutvecklare uppmanas att inte publicera nya versioner för ofta - de måste betala en kuratoravgift på 0,5% på alla automatiskt migrerade kuratorandelar.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Risker
 
 1. Frågemarknaden är i grunden ung på The Graph och det finns en risk att din %APY kan vara lägre än du förväntar dig på grund av tidiga marknadsmekanik.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. En subgraf kan misslyckas på grund av en bugg. En misslyckad subgraf genererar inte frågeavgifter. Som ett resultat måste du vänta tills utvecklaren rättar felet och distribuerar en ny version.
    - Om du prenumererar på den nyaste versionen av en subgraf kommer dina andelar automatiskt att migreras till den nya versionen. Detta kommer att medföra en kuratoravgift på 0,5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. Hur bestämmer jag vilka subgrafer av hög kvalitet att signalera på?
 
-Att hitta högkvalitativa subgrafer är en komplex uppgift, men den kan närmas på många olika sätt. Som kurator vill du leta efter pålitliga subgrafer som genererar frågevolym. En pålitlig subgraf kan vara värdefull om den är komplett, korrekt och stöder en dApps datamässiga behov. En dåligt utformad subgraf kan behöva revideras eller publiceras på nytt och kan också misslyckas. Det är avgörande för kuratorer att granska en subgrafs arkitektur eller kod för att bedöma om en subgraf är värdefull. Som ett resultat:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Kuratorer kan använda sin förståelse för nätverket för att försöka förutsäga hur en enskild subgraf kan generera en högre eller lägre frågevolym i framtiden
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. Vad kostar det att uppdatera en subgraf?
@@ -78,50 +76,14 @@ Det föreslås att du inte uppdaterar dina subgrafer för ofta. Se frågan ovan
 
 ### 5. Kan jag sälja mina kuratorandelar?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Bindningskurva 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Pris per andel](/img/price-per-share.png)
-
-Som ett resultat ökar priset linjärt, vilket innebär att det blir dyrare att köpa en andel över tiden. Här är ett exempel på vad vi menar, se bindningskurvan nedan:
-
-![Bindningskurva](/img/bonding-curve.png)
-
-Låt oss säga att vi har två kuratorer som präglar andelar för en subgraf:
-
-- Kurator A är den första att signalera på subgrafen. Genom att lägga till 120 000 GRT i kurvan kan de prägla 2000 andelar.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Eftersom båda kuratorerna har hälften av det totala antalet kuratorandelar skulle de få lika mycket kuratorersättning.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Den återstående kuratorn skulle nu få all kuratorersättning för den subgrafen. Om de brände sina andelar för att ta ut GRT skulle de få 120 000 GRT.
-- **TLDR:** GRT-värderingen av kuratorandelar bestäms av bindningskurvan och kan vara volatil. Det finns potential att ådra sig stora förluster. Att signalera tidigt innebär att du satsar mindre GRT för varje andel. Detta innebär i förlängningen att du tjänar mer kuratorersättning per GRT än senare kuratorer för samma subgraf.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-I fallet med The Graph används [Bancors implementation av en bindningskurvformel](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA).
-
 Fortfarande förvirrad? Kolla in vår videohandledning om kurering nedan:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 478a7cb17e00dc31cabd8effdcbfe734434a5a26 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:15 -0500
Subject: [PATCH 0727/1325] New translations curating.mdx (Ukrainian)

---
 website/pages/uk/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/uk/network/curating.mdx b/website/pages/uk/network/curating.mdx
index eae0e3463a43..513644bac22c 100644
--- a/website/pages/uk/network/curating.mdx
+++ b/website/pages/uk/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Куратор може обрати подання сигналу на певну версію підграфа, або ж він може обрати автоматичне перенесення сигналу на найновішу версію цього підграфа. Обидва варіанти є прийнятними та мають свої плюси та мінуси.
 
-Подача сигналу на конкретну версію, є особливо корисною функцією, коли один підграф використовує декілька dApps. Одному dApp може знадобитися регулярно оновлювати підграф новими функціями. Інший dApp може віддати перевагу використанню старої, добре перевіреної версії підграфа. При первинній курації стягується стандартний відсоток у розмірі 1%.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Автоматичне переміщення вашого сигналу на найновішу версію може бути корисним для того, щоб ви продовжували нараховувати комісію за запити. Кожного разу, коли ви здійснюєте кураторську роботу, стягується плата за в розмірі 1%. Ви також сплачуєте 0,5% за кураторство, за кожну міграцію. Розробникам підграфів не рекомендується часто публікувати нові версії - вони повинні сплачувати 0.5% кураторам за всі автоматично переміщені частки кураторів.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Ризики
 
 1. Ринок запитів за своєю суттю молодий в Graph, і існує ризик того, що ваш %APY може бути нижчим, ніж ви очікуєте, через динаміку ринку, що зароджується.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Підграф може не працювати через різноманітні помилки (баги). Підграф, що не працює не стягує комісію за запити. В результаті вам доведеться почекати, поки розробник виправить усі помилки й випустить нову версію.
    - Якщо ви підключені до найновішої версії підграфу, ваші частки будуть автоматично перенесені до цієї нової версії. При цьому буде стягуватися податок на в розмірі 0,5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. Як вирішити, які підграфи є якісними для подачі сигналу?
 
-Пошук найякісніших підграфів є складним завданням, але до нього можна підійти різними способами. Як куратор, ви хочете шукати надійні підграфи, які сприяють збільшенню обсягу запитів. Надійний підграф може бути цінним, якщо він є повноцінним, чітким і відповідає потребам dApp в інформації. Погано організований підграф може потребувати перегляду або повторної редакції, а також може в кінцевому підсумку виявитися неефективним. Для кураторів дуже важливо переглянути інфраструктуру або код підграфа, щоб оцінити, чи є він цінним. Як результат:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Куратори можуть використовувати своє бачення мережі, щоб спробувати передбачити, як окремий підграф може генерувати більший або менший обсяг запитів у майбутньому
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. What’s the cost of updating a subgraph?
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. Чи можу я продати свої частки куратора?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Крива зв'язування 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Ціна за частку](/img/price-per-share.png)
-
-В результаті, ціна зростає лінійно, що означає, що з часом придбати одну частку буде все дорожче і дорожче. Ось приклад того, що ми маємо на увазі, див. криву зв'язування нижче:
-
-![Крива зв'язування](/img/bonding-curve.png)
-
-Уявімо, що у нас є два куратори, які мінтять частки для підграфа:
-
-- Куратор А першим подає сигнал на підграфа. Додавши до кривої 120 000 GRT, вони можуть змінтити 2000 штук.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Оскільки обидва куратори володіють половиною загальної кількості кураторських часток, вони отримають рівну суму винагороди за кураторство.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Куратор, що залишився, тепер отримає всю кураторську винагороду за цей підграф. Якби вони продали свої частки, щоб вивести GRT, вони б отримали лише 120 000 GRT.
-- **TLDR:** Оцінка кількості GRT кураторських часток визначається кривою зв'язування і може бути волатильною. Існує потенціал для зазнання значних втрат. Сигналізація на ранній стадії означає, що ви вкладаєте менше GRT на кожну частку. Це означає, що ви заробляєте більше винагороди, як куратор за кожний GRT токен, ніж пізніші куратори за один і той самий підграф.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-У випадку з Graph, застосовується, [впроваджена Bancor](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA), формула кривої зв'язування.
-
 Все ще спантеличені? Перегляньте нашу відео інструкцію нижче:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 590aede39356a7f3bdef98f9702b1e586a035853 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:16 -0500
Subject: [PATCH 0728/1325] New translations curating.mdx (Chinese Simplified)

---
 website/pages/zh/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/zh/network/curating.mdx b/website/pages/zh/network/curating.mdx
index cfeb33c6551b..1788ca600226 100644
--- a/website/pages/zh/network/curating.mdx
+++ b/website/pages/zh/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 策展人可以选择在特定的子图版本上发出信号，或者他们可以选择让他们的策展份额自动迁移到该子图的最新生产版本。 这两种策略都是有效的，都有各自的优点和缺点。
 
-当一个子图被多个 dApp 使用时，在特定版本上发出信号特别有用。 一个 dApp 可能需要定期更新子图的新特性。 另一个 dApp 可能更喜欢使用更旧的、经过良好测试的子图版本。 在初始策展时，会产生 1%的标准税。
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 让你的策展份额自动迁移到最新的生产构建，对确保你不断累积查询费用是有价值的。 每次你策展时，都会产生 1%的策展税。 每次迁移时，你也将支付 0.5%的策展税。 不鼓励子图开发人员频繁发布新版本--他们必须为所有自动迁移的策展份额支付 0.5%的策展税。
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## 风险
 
 1. 在Graph，查询市场本来就很年轻，由于市场动态刚刚开始，你的年收益率可能低于你的预期，这是有风险的。
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. 一个子图可能由于错误而失败。 一个失败的子图不会累积查询费用。 因此，你必须等待，直到开发人员修复错误并部署一个新的版本。
    - 如果你订阅了一个子图的最新版本，你的份额将自动迁移到该新版本。 这将产生 0.5%的策展税。
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. 如何决定哪些子图是高质量的信号？
 
-寻找高质量的子图是一项复杂的任务，但它可以通过许多不同的方式来实现。 作为策展人，你要寻找那些推动查询量的值得信赖的子图。 这些值得信赖的子图是有价值的，因为它们是完整的，准确的，并支持 dApp 的数据需求。 一个架构不良的子图可能需要修改或重新发布，也可能最终失败。 策展人审查子图的架构或代码，以评估一个子图是否有价值，这是至关重要的。 因此：
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- 策展人可以利用市场知识，尝试预测单个子图在未来可能产生更多或更少查询量
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. 升级一个子图的成本是多少？
@@ -78,50 +76,14 @@ Migrating your curation shares to a new subgraph version incurs a curation tax o
 
 ### 5. 我可以出售我的策展份额吗？
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## 收益率曲线 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![每份价格](/img/price-per-share.png)
-
-因此，价格是线性增长的，这意味着随着时间的推移，购买股票的成本会越来越高。 这里有一个例子说明我们的意思，请看下面的粘合曲线。
-
-![收益率曲线](/img/bonding-curve.png)
-
-考虑到我们有两个策展人，他们为一个子图铸造了份额：
-
-- 策展人 A 是第一个对子图发出信号的人。 通过在曲线中加入 120,000 GRT，他们能够铸造出 2000 股。
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- 由于两位策展人都持有策展人股份总数的一半，他们将获得同等数量的策展人使用费。
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- 剩下的策展人现在将收到该子图的所有策展人使用费。 如果他们烧掉他们的股份来提取 GRT，他们将得到 12 万 GRT。
-- **TLDR:** 策展人股份的 GRT 估值是由粘合曲线决定的，可能会有波动。 有可能出现大的收益，也有可能出现大的损失。 提前发出信号意味着你为每只股票投入的 GRT 较少。 推而广之，这意味着在相同的子图上，你比后来的策展人在每个 GRT 上赚取更多的策展人使用费。
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-在Graph 的案例中， [Bancor 对粘合曲线公式的实施](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) 被利用。
-
 还有困惑吗？ 点击下面查看管理视频指导：
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 23c524809d82d52086e16b405f900b0de89d4beb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:17 -0500
Subject: [PATCH 0729/1325] New translations curating.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/ur/network/curating.mdx b/website/pages/ur/network/curating.mdx
index b8baf93a16a1..bd7bb8b3f57f 100644
--- a/website/pages/ur/network/curating.mdx
+++ b/website/pages/ur/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 ایک کیوریٹر مخصوص سب گراف ورژن پر سگنل دینے کا انتخاب کر سکتا ہے، یا وہ اپنے سگنل کو خود بخود اس سب گراف کی جدید ترین پروڈکشن بلڈ میں منتقل کرنے کا انتخاب کر سکتا ہے۔ دونوں درست حکمت عملی ہیں اور ان کے اپنے فوائد اور نقصانات کے ساتھ آتے ہیں.
 
-ایک مخصوص ورژن پر سگنلنگ کرنا خاص طور پر فائدہ مند اس صورت میں ہے جب ایک سب گراف متعدد ڈیپ کے ذریع استعمال ہوتا ہو. ایک ڈیپ کو نئی خصوصیات کے ساتھ سب گراف کو باقاعدگی سے ڈی ایپ کرنے کی ضرورت پڑ سکتی ہے۔ایک اور ڈیپ پرانا، اچھی طرح سے تجربہ شدہ سب گراف ورژن استعمال کرنے کو ترجیح دے سکتا ہے. ابتدائی کیوریشن پر، 1% معیاری ٹیکس لاگو ہوتا ہے.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 آپ کے سگنل کو خود بخود جدید ترین پروڈکشن کی تعمیر میں منتقل کرنا اس بات کو یقینی بنانے کے لیے قابل قدر ہو سکتا ہے کہ آپ کیوری کی فیس جمع کرتے رہیں۔ جب بھی آپ کیوریشن کرتے ہیں، 1% کیوریشن ٹیکس لاگو ہوتا ہے۔ آپ ہر دفعہ منتقلی پر 0.5% کا کیوریشن ٹیکس ادا کریں گے. سب گراف ڈویلپرز کو نئے ورژنز کثرت سے شائع کرنے کی حوصلہ شکنی کی جاتی ہے - انہیں تمام خود کار طریقے سے منتقل کیوریشن شیئرز پر 0.5% کیوریشن ٹیکس ادا کرنا پڑتا ہے.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## خطرات
 
 1. گراف میں کیوری کی مارکیٹ فطری طور پر جوان ہے اور اس بات کا خطرہ ہے کہ آپ کا %APY مارکیٹ کی نئی حرکیات کی وجہ سے آپ کی توقع سے کم ہو سکتا ہے.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. ایک سب گراف ایک بگ کی وجہ سے ناکام ہو سکتا ہے. ایک ناکام سب گراف کیوری کی فیس جمع نہیں کرتا ہے. اس کے نتیجے میں،آپ کو انتظار کرنا پڑے گاجب تک کہ ڈویلپر اس بگ کو کو ٹھیک نہیں کرتا اور نیا ورژن تعینات کرتا ہے.
    - اگر آپ نےسب گراف کے نۓ ورژن کو سبسکرائب کیا ہے. آپ کے حصص خود بخود اس نئے ورژن میں منتقل ہو جائیں گے۔ اس پر 0.5% کیوریشن ٹیکس لگے گا.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. میں یہ کیسے طے کروں کہ کون سے سب گرافس اعلیٰ معیار کے ہیں؟
 
-اعلی معیار کے سب گراف تلاش کرنا پیچیدہ کام ہے. لیکن اس کوبہت سے مختلف طریقوں سے رابطہ کیا جا سکتا ہے. بطور کیوریٹر، آپ قابل اعتماد سب گرافس تلاش کرنا چاہتے ہیں جو کیوری کے حجم کو بڑھا رہے ہیں۔ایک قابل اعتماد سب گراف قابل قدر ہو سکتا ہے اگر یہ مکمل، درست، اور ڈیپ کے ڈیٹا کی ضروریات کی حمایت کرتا ہے۔ ایک ناقص تعمیراتی سب گراف کو نظر ثانی یا دوبارہ شائع کرنے کی ضرورت ہو سکتی ہے، اور یہ ناکامی بھی ختم ہو سکتی ہے۔کیوریٹرز کے لیے یہ اہم ہے کہ وہ سب گراف کے فن تعمیر یا کوڈ کا جائزہ لیں تاکہ یہ اندازہ لگایا جا سکے کہ آیا کوئی سب گراف قیمتی ہے۔ اس کے نتیجے میں:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- کیوریٹرز نیٹ ورک کے بارے میں اپنی سمجھ کا استعمال کرتے ہوئے یہ اندازہ لگا سکتے ہیں کہ کس طرح ایک انفرادی سب گراف مستقبل میں کیوری کا حجم زیادہ یا کم پیدا کر سکتا ہے
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. سب گراف کو اپ ڈیٹ کرنے کی کیا قیمت ہے؟
@@ -78,50 +76,14 @@ Migrating your curation shares to a new subgraph version incurs a curation tax o
 
 ### 5. کیا میں اپنے کیوریشن شیئرز بیچ سکتا ہوں؟
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## بانڈنگ کریو 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![فی حصص کی قیمت](/img/price-per-share.png)
-
-اس کے نتیجے میں،قیمتوں میں مسلسل اضافہ ہوتا ہے،اس کا مطلب ہے کہ وقت گزرنے کے ساتھ ساتھ شیئر خریدنا زیادہ مہنگا ہو جائے گا۔ یہاں پر ایک مثال ہے کی ہمارا کیا مطلب ہے، نیچے بانڈنگ وکر دیکھیں:
-
-![بانڈنگ وکر](/img/bonding-curve.png)
-
-فرض کریں ہمارے پاس دو کیوریٹر ہیں جو ایک سب گراف کے لیے شیئر کرتے ہیں:
-
-- سب گراف پر سب سے پہلے سگنل دینے والا کیوریٹر A ہے۔وکر میں 120,000 GRT شامل کرکے، وہ 2000 حصص کو ٹکسال کرنے کے قابل ہیں.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- چونکہ دونوں کیوریٹر کل کیوریشن شیئرز کا نصف حصہ رکھتے ہیں، اس لیے انہیں کیوریٹر رائلٹی کی مساوی رقم ملے گی.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- باقی کیورٹرز اب اس سب گراف کے لیے تمام کیوریٹر رائلٹی وصول کریں گے. اگر وہ GRT نکالنے کے لیے اپنے حصص جلاتے ہیں، تو وہ 120,000 GRT وصول کریں گے.
-- **TLDR:** کیوریشن شیئرز کی GRT ویلیویشن کا تعین بانڈنگ کریو سے ہوتا ہے اور یہ غیر مستحکم ہو سکتا ہے۔بڑے نقصان کا خدشہ ہے۔جلدی سگنل دینے کا مطلب ہے کہ آپ ہر شیئر کے لیے کم GRT لگاتے ہیں۔توسیع کے لحاظ سے، اس کا مطلب ہے کہ آپ اسی سب گراف کے لیے بعد کے کیوریٹروں کے مقابلے فی GRT زیادہ کیوریٹر رائلٹی حاصل کرتے ہیں.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-گراف کے معاملے میں،[بانڈنگ کریو فارمولے پر بنکور کا نفاذ](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) کا فائدہ اٹھایا جاتا ہے.
-
 ابھی بھی الجھن میں ہیں، ذیل میں ہماری کیوریشن ویڈیو گائیڈ دیکھیں:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 31fe2b351478c6778ee62a0b063663289c164def Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:18 -0500
Subject: [PATCH 0730/1325] New translations curating.mdx (Vietnamese)

---
 website/pages/vi/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/vi/network/curating.mdx b/website/pages/vi/network/curating.mdx
index c349ce0ccee3..b10717935904 100644
--- a/website/pages/vi/network/curating.mdx
+++ b/website/pages/vi/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 Curator có thể chọn phát tín hiệu trên một phiên bản subgraph cụ thể hoặc họ có thể chọn để tín hiệu của họ tự động chuyển sang bản dựng sản xuất mới nhất của subgraph đó. Cả hai đều là những chiến lược hợp lệ và đi kèm với những ưu và nhược điểm của riêng chúng.
 
-Signaling on a specific version is especially useful when one subgraph is used by multiple dApps. One dApp might need to regularly update the subgraph with new features. Another dApp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## Những rủi ro
 
 1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. Một subgraph có thể thất bại do một lỗi. Một subgraph thất bại không tích lũy phí truy vấn. Do đó, bạn sẽ phải đợi cho đến khi nhà phát triển sửa lỗi và triển khai phiên bản mới.
    - Nếu bạn đã đăng ký phiên bản mới nhất của một subgraph, các cổ phần của bạn sẽ tự động chuyển sang phiên bản mới đó. Điều này sẽ phát sinh một khoản thuế curation 0.5%.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. Làm cách nào để tôi quyết định xem các subgraph nào có chất lượng cao để báo hiệu?
 
-Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dApp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- Curator có thể sử dụng sự hiểu biết của họ về mạng để thử và dự đoán cách một subgraph riêng lẻ có thể tạo ra khối lượng truy vấn cao hơn hoặc thấp hơn trong tương lai
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. What’s the cost of updating a subgraph?
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. Tôi có thể bán cổ phần curation của mình không?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## Căn bản về Bonding Curve
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![Giá mỗi cổ phần](/img/price-per-share.png)
-
-Kết quả là, giá tăng tuyến tính, có nghĩa là giá mua cổ phần sẽ đắt hơn theo thời gian. Dưới đây là một ví dụ về ý của chúng tôi, hãy xem đường cong liên kết bên dưới:
-
-![Đường cong liên kết](/img/bonding-curve.png)
-
-Hãy xem xét chúng ta có hai người curator cùng đúc cổ phần của một subgraph:
-
-- Curator A là người đầu tiên phát tín hiệu trên subgraph này. Bằng cách thêm 120,000 GRT vào đường cong, anh ấy có thể kiếm được 2000 cổ phần.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- Vì cả hai người curator này đều nắm giữ một nửa tổng số cổ phần curate, họ sẽ nhận được một số tiền bản quyền của curator bằng nhau.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- Người curator còn lại bây giờ sẽ nhận được tất cả tiền bản quyền của curator cho subgraph đó. Nếu đốt cổ phần để rút GRT, anh ấy sẽ nhận được 120,000 GRT.
-- **TLDR:** The GRT valuation of curation shares is determined by the bonding curve and can be volatile. There is potential to incur big losses. Signaling early means you put in less GRT for each share. By extension, this means you earn more curator royalties per GRT than later curators for the same subgraph.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-Trong trường hợp của The Graph, [Triển khai của Bancor về công thức đường cong liên kết](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) được sử dụng.
-
 Vẫn còn thắc mắc? Xem video hướng dẫn Curation của chúng tôi bên dưới:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 5c8f08fd4b80de1b11229cc94ac75ffeb0525fac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:19 -0500
Subject: [PATCH 0731/1325] New translations curating.mdx (Marathi)

---
 website/pages/mr/network/curating.mdx | 58 +++++----------------------
 1 file changed, 10 insertions(+), 48 deletions(-)

diff --git a/website/pages/mr/network/curating.mdx b/website/pages/mr/network/curating.mdx
index 2bf60e3da154..5e9cadc79a04 100644
--- a/website/pages/mr/network/curating.mdx
+++ b/website/pages/mr/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 क्युरेटर विशिष्ट सबग्राफ आवृत्तीवर सिग्नल करणे निवडू शकतो किंवा ते त्यांचे सिग्नल त्या सबग्राफच्या नवीनतम उत्पादन बिल्डमध्ये स्वयंचलितपणे स्थलांतरित करणे निवडू शकतात. दोन्ही वैध धोरणे आहेत आणि त्यांच्या स्वतःच्या साधक आणि बाधकांसह येतात.
 
-एका विशिष्‍ट आवृत्‍तीवर सिग्नल करणे विशेषतः उपयोगी असते जेव्हा एक सबग्राफ एकाधिक dApps द्वारे वापरला जातो. एका dApp ला नवीन वैशिष्ट्यांसह सबग्राफ नियमितपणे अपडेट करण्याची आवश्यकता असू शकते. दुसरे dApp कदाचित जुनी, चांगली चाचणी केलेली सबग्राफ आवृत्ती वापरण्यास प्राधान्य देईल. सुरुवातीच्या क्युरेशनवर, 1% मानक कर लागतो.
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 तुमचा सिग्नल नवीनतम प्रोडक्शन बिल्डवर आपोआप स्थलांतरित होणे हे तुम्ही क्वेरी फी जमा करत असल्याचे सुनिश्चित करण्यासाठी मौल्यवान असू शकते. प्रत्येक वेळी तुम्ही क्युरेट करता तेव्हा 1% क्युरेशन कर लागतो. तुम्ही प्रत्येक स्थलांतरावर 0.5% क्युरेशन कर देखील द्याल. सबग्राफ विकसकांना वारंवार नवीन आवृत्त्या प्रकाशित करण्यापासून परावृत्त केले जाते - त्यांना सर्व स्वयं-स्थलांतरित क्युरेशन शेअर्सवर 0.5% क्युरेशन कर भरावा लागतो.
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## जोखीम
 
 1. द ग्राफमध्ये क्वेरी मार्केट मूळतः तरुण आहे आणि नवीन मार्केट डायनॅमिक्समुळे तुमचा %APY तुमच्या अपेक्षेपेक्षा कमी असण्याचा धोका आहे.
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. बगमुळे सबग्राफ अयशस्वी होऊ शकतो. अयशस्वी सबग्राफ क्वेरी शुल्क जमा करत नाही. परिणामी, विकसक बगचे निराकरण करेपर्यंत आणि नवीन आवृत्ती तैनात करेपर्यंत तुम्हाला प्रतीक्षा करावी लागेल.
    - तुम्ही सबग्राफच्या नवीनतम आवृत्तीचे सदस्यत्व घेतले असल्यास, तुमचे शेअर्स त्या नवीन आवृत्तीमध्ये स्वयंचलितपणे स्थलांतरित होतील. यावर 0.5% क्युरेशन कर लागेल.
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,9 +61,9 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. कोणते सबग्राफ उच्च दर्जाचे आहेत हे मी कसे ठरवू?
 
-उच्च-गुणवत्तेचे सबग्राफ शोधणे हे एक जटिल कार्य आहे, परंतु ते वेगवेगळ्या मार्गांनी संपर्क साधले जाऊ शकते. क्युरेटर म्हणून, तुम्हाला विश्वासार्ह सबग्राफ्स शोधायचे आहेत जे क्वेरी व्हॉल्यूम वाढवत आहेत. dApp च्या डेटा गरजा पूर्ण, अचूक आणि सपोर्ट करत असल्यास विश्वासार्ह सबग्राफ मौल्यवान असू शकतो. खराब आर्किटेक्‍ट सबग्राफ सुधारित करणे किंवा पुन्हा प्रकाशित करणे आवश्यक असू शकते आणि ते अयशस्वी देखील होऊ शकते. सबग्राफ मौल्यवान आहे की नाही याचे मूल्यांकन करण्यासाठी सबग्राफच्या आर्किटेक्चर किंवा कोडचे पुनरावलोकन करणे क्युरेटर्ससाठी महत्त्वपूर्ण आहे. परिणामी:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- क्युरेटर्स नेटवर्कबद्दलची त्यांची समज वापरून प्रयत्न करू शकतात आणि भविष्यात वैयक्तिक सबग्राफ अधिक किंवा कमी क्वेरी व्हॉल्यूम कसा निर्माण करू शकतो याचा अंदाज लावू शकतात
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
 - Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
 
 ### 3. What’s the cost of updating a subgraph?
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. मी माझे क्युरेशन शेअर्स विकू शकतो का?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## बाँडिंग वक्र 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![प्रति शेअर किंमत](/img/price-per-share.png)
-
-परिणामी, किंमत एकरेषेने वाढते, याचा अर्थ वेळोवेळी शेअर खरेदी करणे अधिक महाग होईल. आम्हाला काय म्हणायचे आहे याचे एक उदाहरण येथे आहे, खाली बाँडिंग वक्र पहा:
-
-![बाँडिंग वक्र](/img/bonding-curve.png)
-
-आमच्याकडे दोन क्युरेटर आहेत जे सबग्राफसाठी शेअर करतात याचा विचार करा:
-
-- क्युरेटर A हा सबग्राफवर सिग्नल देणारा पहिला आहे. वक्र मध्ये 120,000 GRT जोडून, ते 2000 शेअर्स मिंट करण्यास सक्षम आहेत.
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- दोन्ही क्युरेटर्सचे एकूण क्युरेशन शेअर्सचे अर्धे भाग असल्याने, त्यांना समान प्रमाणात क्युरेटर रॉयल्टी मिळेल.
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- उर्वरित क्युरेटर आता त्या सबग्राफसाठी सर्व क्युरेटर रॉयल्टी प्राप्त करतील. जर त्यांनी GRT काढण्यासाठी त्यांचे शेअर्स जाळले तर त्यांना 120,000 GRT मिळतील.
-- **TLDR:** क्युरेशन शेअर्सचे GRT मूल्यांकन बाँडिंग वक्र द्वारे निर्धारित केले जाते आणि ते अस्थिर असू शकते. मोठे नुकसान होण्याची शक्यता आहे. लवकर सिग्नल देणे म्हणजे तुम्ही प्रत्येक शेअरसाठी कमी GRT टाकता. विस्तारानुसार, याचा अर्थ तुम्ही त्याच सबग्राफसाठी नंतरच्या क्युरेटर्सपेक्षा प्रति GRT अधिक क्युरेटर रॉयल्टी मिळवता.
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-The Graph च्या बाबतीत, [बँकोरची बाँडिंग वक्र फॉर्मची अंमलबजावणी](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) फायदा घेतला जातो.
-
 अजूनही गोंधळलेले? खाली आमचे क्युरेशन व्हिडिओ मार्गदर्शक पहा:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From b8020726a664ba6c4bb0ef151eb21d0c140577de Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:20 -0500
Subject: [PATCH 0732/1325] New translations curating.mdx (Hindi)

---
 website/pages/hi/network/curating.mdx | 60 +++++----------------------
 1 file changed, 11 insertions(+), 49 deletions(-)

diff --git a/website/pages/hi/network/curating.mdx b/website/pages/hi/network/curating.mdx
index e9bf6371f0c3..34d446b1314f 100644
--- a/website/pages/hi/network/curating.mdx
+++ b/website/pages/hi/network/curating.mdx
@@ -8,9 +8,7 @@ Curators are critical to The Graph's decentralized economy. They use their knowl
 
 Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
 
-Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling Curators to a portion of future query fees that the subgraph drives.
-
-Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that curators use to let Indexers know that a subgraph is good to index; where GRT is added to a bonding curve for a subgraph. Indexers can trust the signal from a curator because upon signaling, curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
 
 Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
 
@@ -18,7 +16,7 @@ The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the
 
 When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
 
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+यदि आपको सेवा की गुणवत्ता बढ़ाने के लिए क्यूरेशन में सहायता की आवश्यकता है, तो कृपया Edge & Node टीम को support@thegraph.zendesk.com पर एक अनुरोध भेजें और उन सबग्राफ़्स का उल्लेख करें जिनमें आपको सहायता चाहिए।
 
 Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
 
@@ -30,11 +28,11 @@ Within the Curator tab in Graph Explorer, curators will be able to signal and un
 
 एक क्यूरेटर एक विशिष्ट सबग्राफ संस्करण पर संकेत देना चुन सकता है, या वे अपने सिग्नल को स्वचालित रूप से उस सबग्राफ के नवीनतम उत्पादन निर्माण में माइग्रेट करना चुन सकते हैं। दोनों मान्य रणनीतियाँ हैं और अपने स्वयं के पेशेवरों और विपक्षों के साथ आती हैं।
 
-एक विशिष्ट संस्करण पर संकेत देना विशेष रूप से तब उपयोगी होता है जब एक सबग्राफ का उपयोग कई डीएपी द्वारा किया जाता है। एक डीएपी को नई सुविधाओं के साथ सबग्राफ को नियमित रूप से अपडेट करने की आवश्यकता हो सकती है। एक और डीएपी पुराने, अच्छी तरह से परीक्षण किए गए सबग्राफ संस्करण का उपयोग करना पसंद कर सकता है। प्रारंभिक अवधि पर, 1% मानक कर लगाया जाता है।
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
 
 अपने सिग्नल को स्वचालित रूप से नवीनतम उत्पादन बिल्ड में माइग्रेट करना यह सुनिश्चित करने के लिए मूल्यवान हो सकता है कि आप क्वेरी शुल्क अर्जित करते रहें। हर बार जब आप क्यूरेट करते हैं, तो 1% क्यूरेशन टैक्स लगता है। आप हर माइग्रेशन पर 0.5% क्यूरेशन टैक्स भी देंगे। सबग्राफ डेवलपर्स को बार-बार नए संस्करण प्रकाशित करने से हतोत्साहित किया जाता है - उन्हें सभी ऑटो-माइग्रेटेड क्यूरेशन शेयरों पर 0.5% क्यूरेशन टैक्स देना पड़ता है।
 
-> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, initializes the bonding curve (even on Arbitrum), and also transfers tokens into the Graph proxy.
+> **Note**: किसी विशेष subgraph को संकेत देने वाला पहला पता पहला curator माना जाता है और उसे बाकी के curators की तुलना में बहुत अधिक gas-intensive काम करना होगा क्योंकि पहला curators curation share tokens को initializes करता है, bonding curve को initializes करता है, और Graph proxy में tokens भी transfer करता है।
 
 ## Withdrawing your GRT
 
@@ -49,8 +47,8 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## जोखिम
 
 1. क्वेरी बाजार द ग्राफ में स्वाभाविक रूप से युवा है और इसमें जोखिम है कि नवजात बाजार की गतिशीलता के कारण आपका %APY आपकी अपेक्षा से कम हो सकता है।
-2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned and the rest is deposited into the reserve supply of the bonding curve.
-3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dApp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+2. क्यूरेशन शुल्क  - जब कोई क्यूरेटर किसी सबग्राफ़ पर GRT सिग्नल करता है, तो उसे 1% क्यूरेशन टैक्स देना होता है। यह शुल्क जला दिया जाता है।
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. बग के कारण सबग्राफ विफल हो सकता है। एक विफल सबग्राफ क्वेरी शुल्क अर्जित नहीं करता है। नतीजतन, आपको तब तक इंतजार करना होगा जब तक कि डेवलपर बग को ठीक नहीं करता है और एक नया संस्करण तैनात करता है।
    - यदि आपने सबग्राफ के नवीनतम संस्करण की सदस्यता ली है, तो आपके शेयर उस नए संस्करण में स्वत: माइग्रेट हो जाएंगे। इस पर 0.5% क्यूरेशन टैक्स लगेगा।
    - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
@@ -63,10 +61,10 @@ By signalling on a subgraph, you will earn a share of all the query fees that th
 
 ### 2. मैं यह कैसे तय करूं कि कौन से सबग्राफ सिग्नल देने के लिए उच्च गुणवत्ता वाले हैं?
 
-उच्च-गुणवत्ता वाले सबग्राफ ढूँढना एक जटिल कार्य है, लेकिन इसे कई अलग-अलग तरीकों से संपर्क किया जा सकता है। क्यूरेटर के रूप में, आप भरोसेमंद सबग्राफ देखना चाहते हैं जो क्वेरी वॉल्यूम बढ़ा रहे हैं। एक भरोसेमंद सबग्राफ मूल्यवान हो सकता है यदि यह पूर्ण, सटीक है और डीएपी की डेटा जरूरतों का समर्थन करता है। खराब ढंग से तैयार किए गए सबग्राफ को संशोधित करने या फिर से प्रकाशित करने की आवश्यकता हो सकती है, और यह विफल भी हो सकता है। सबग्राफ मूल्यवान है या नहीं, इसका आकलन करने के लिए क्यूरेटर के लिए सबग्राफ के आर्किटेक्चर या कोड की समीक्षा करना महत्वपूर्ण है। नतीजतन:
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
 
-- क्यूरेटर नेटवर्क की अपनी समझ का उपयोग करके यह अनुमान लगाने की कोशिश कर सकते हैं कि कैसे एक व्यक्तिगत सबग्राफ भविष्य में उच्च या निम्न क्वेरी मात्रा उत्पन्न कर सकता है।
-- Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
+- क्यूरेटर नेटवर्क की अपनी समझ का उपयोग करके यह अनुमान लगाने की कोशिश कर सकते हैं कि भविष्य में कोई विशेष सबग्राफ़ अधिक या कम क्वेरी वॉल्यूम कैसे उत्पन्न कर सकता है।
+- क्यूरेटर को Graph Explorer के माध्यम से उपलब्ध मेट्रिक्स को भी समझना चाहिए। जैसे कि पिछले क्वेरी वॉल्यूम और सबग्राफ़ डेवलपर कौन है, ये मेट्रिक्स यह तय करने में मदद कर सकते हैं कि किसी सबग्राफ़ पर सिग्नलिंग करना उचित है या नहीं।
 
 ### 3. What’s the cost of updating a subgraph?
 
@@ -78,50 +76,14 @@ It’s suggested that you don’t update your subgraphs too frequently. See the
 
 ### 5. क्या मैं अपने क्यूरेशन शेयर बेच सकता हूँ?
 
-Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed) along the bonding curve for a particular subgraph. The amount of GRT needed to mint a new signal, and the amount of GRT you receive when you burn your existing signal are determined by that bonding curve:
+क्यूरेशन शेयरों को अन्य ERC20 टोकनों की तरह "खरीदा" या "बेचा" नहीं जा सकता, जिन्हें आप जानते होंगे। इन्हें केवल मिंट (निर्मित) या बर्न (नष्ट) किया जा सकता है।
 
-- As a Curator on Ethereum, you need to know that when you burn your curation shares to withdraw GRT, you can end up with more or less GRT than you initially deposited.
-- As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
 
 ### 6. Am I eligible for a curation grant?
 
 Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
 
-## Curating on Ethereum vs Arbitrum
-
-The behavior of the curation mechanism differs depending on the protocol chain deployment, notably, how the price of a subgraph share is calculated.
-
-The Graph Network's original deployment on Ethereum uses bonding curves to determine what the price of shares is: **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.** This means that curating puts your principal at risk, since it's not guaranteed you can sell your shares and get back your original investment.
-
-On Arbitrum, curating subgraphs becomes significantly simpler. The bonding curves are "flattened", their effect is nullified meaning no Curator will be able to realize gains at the expense of others. This allows Curators to signal or unsignal on subgraphs at any given time, at a consistent cost, and with very limited risk.
-
-If you are interested in curating on Ethereum and want to understand the details of bonding curves and their effects see [Bonding Curve 101](#bonding-curve-101). Please do your diligence to make sure you curate on subgraphs you trust. Creating a subgraph is permissionless, so people can create subgraphs and call them any name they'd like. For more guidance on curation risks, check out [The Graph Academy's Curation Guide.](https://thegraph.academy/curators/)
-
-## बॉन्डिंग कर्व 101
-
-> **Note**: this section only applies to curation on Ethereum since bonding curves are flat and have no effect on Arbitrum.
-
-Each subgraph has a bonding curve on which curation shares are minted when a user adds signal **into** the curve. Each subgraph’s bonding curve is unique. The bonding curves are architected so that the price to mint a curation share on a subgraph increases linearly, over the number of shares minted.
-
-![मूल्य प्रति शेयर](/img/price-per-share.png)
-
-नतीजतन, मूल्य रैखिक रूप से बढ़ता है, जिसका अर्थ है कि समय के साथ शेयर खरीदना अधिक महंगा हो जाएगा। यहाँ एक उदाहरण है कि हमारा क्या मतलब है, नीचे बॉन्डिंग कर्व देखें:
-
-![बंधन वक्र](/img/bonding-curve.png)
-
-विचार करें कि हमारे पास दो क्यूरेटर हैं जो मिंट एक सबग्राफ के लिए शेयर करते हैं:
-
-- क्यूरेटर ए सबसे पहले सबग्राफ पर संकेत देता है। कर्व में 120,000 जीआरटी जोड़कर, वे 2000 शेयरों का खनन करने में सक्षम हैं।
-- Curator B’s signal is on the subgraph later at some point. To receive the same amount of shares as Curator A, they would have to add 360,000 GRT into the curve.
-- चूंकि दोनों क्यूरेटर कुल क्यूरेशन शेयरों का आधा हिस्सा रखते हैं, इसलिए उन्हें क्यूरेटर रॉयल्टी की समान राशि प्राप्त होगी।
-- Now, if any of the curators were to burn their 2000 curation shares, they would receive 360,000 GRT.
-- शेष क्यूरेटर अब उस सबग्राफ के लिए सभी क्यूरेटर रॉयल्टी प्राप्त करेंगे। यदि वे GRT निकालने के लिए अपने शेयर जलाते हैं, तो उन्हें 120,000 GRT प्राप्त होंगे।
-- **TLDR:** क्यूरेशन शेयरों का GRT मूल्यांकन बॉन्डिंग कर्व द्वारा निर्धारित किया जाता है और अस्थिर हो सकता है। बड़ा नुकसान होने की संभावना है। जल्दी संकेत देने का मतलब है कि आप प्रत्येक शेयर के लिए कम जीआरटी डालते हैं। विस्तार से, इसका मतलब है कि आप उसी सबग्राफ के लिए बाद के क्यूरेटरों की तुलना में प्रति जीआरटी अधिक क्यूरेटर रॉयल्टी अर्जित करते हैं।
-
-In general, a bonding curve is a mathematical curve that defines the relationship between token supply and asset price. In the specific case of subgraph curation, **the price of each subgraph share increases with each token invested** and **the price of each share decreases with each token sold.**
-
-द ग्राफ़ के मामले में, [बैंकर का बॉन्डिंग कर्व फ़ॉर्मूला लागू करना](https://drive.google.com/file/d/0B3HPNP-GDn7aRkVaV3dkVl9NS2M/view?resourcekey=0-mbIgrdd0B9H8dPNRaeB_TA) लीवरेज्ड है।
-
 अभी भी उलझन में? नीचे हमारे क्यूरेशन वीडियो गाइड देखें:
 
 <VideoEmbed youtube="VytTEcf0dxQ" />

From 235977573b7543a5ecd1280f96da0f8d45a944a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:21 -0500
Subject: [PATCH 0733/1325] New translations curating.mdx (Swahili)

---
 website/pages/sw/network/curating.mdx | 89 +++++++++++++++++++++++++++
 1 file changed, 89 insertions(+)
 create mode 100644 website/pages/sw/network/curating.mdx

diff --git a/website/pages/sw/network/curating.mdx b/website/pages/sw/network/curating.mdx
new file mode 100644
index 000000000000..a5a63f3e2751
--- /dev/null
+++ b/website/pages/sw/network/curating.mdx
@@ -0,0 +1,89 @@
+---
+title: Curating
+---
+
+Curators are critical to The Graph's decentralized economy. They use their knowledge of the web3 ecosystem to assess and signal on the subgraphs that should be indexed by The Graph Network. Through Graph Explorer, Curators view network data to make signaling decisions. In turn, The Graph Network rewards Curators who signal on good quality subgraphs with a share of the query fees those subgraphs generate. The amount of GRT signaled is one of the key considerations for indexers when determining which subgraphs to index.
+
+## What Does Signaling Mean for The Graph Network?
+
+Before consumers can query a subgraph, it must be indexed. This is where curation comes into play. In order for Indexers to earn substantial query fees on quality subgraphs, they need to know what subgraphs to index. When Curators signal on a subgraph, it lets Indexers know that a subgraph is in demand and of sufficient quality that it should be indexed.
+
+Curators make The Graph network efficient and [signaling](#how-to-signal) is the process that Curators use to let Indexers know that a subgraph is good to index. Indexers can trust the signal from a Curator because upon signaling, Curators mint a curation share for the subgraph, entitling them to a portion of future query fees that the subgraph drives.
+
+Curator signals are represented as ERC20 tokens called Graph Curation Shares (GCS). Those that want to earn more query fees should signal their GRT to subgraphs that they predict will generate a strong flow of fees to the network. Curators cannot be slashed for bad behavior, but there is a deposit tax on Curators to disincentivize poor decision-making that could harm the integrity of the network. Curators will also earn fewer query fees if they curate on a low-quality subgraph because there will be fewer queries to process or fewer Indexers to process them.
+
+The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
+
+When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
+
+If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
+
+Indexers can find subgraphs to index based on curation signals they see in Graph Explorer (screenshot below).
+
+![Explorer subgraphs](/img/explorer-subgraphs.png)
+
+## How to Signal
+
+Within the Curator tab in Graph Explorer, curators will be able to signal and unsignal on certain subgraphs based on network stats. For a step-by-step overview of how to do this in Graph Explorer, [click here.](/network/explorer)
+
+A curator can choose to signal on a specific subgraph version, or they can choose to have their signal automatically migrate to the newest production build of that subgraph. Both are valid strategies and come with their own pros and cons.
+
+Signaling on a specific version is especially useful when one subgraph is used by multiple dapps. One dapp might need to regularly update the subgraph with new features. Another dapp might prefer to use an older, well-tested subgraph version. Upon initial curation, a 1% standard tax is incurred.
+
+Having your signal automatically migrate to the newest production build can be valuable to ensure you keep accruing query fees. Every time you curate, a 1% curation tax is incurred. You will also pay a 0.5% curation tax on every migration. Subgraph developers are discouraged from frequently publishing new versions - they have to pay a 0.5% curation tax on all auto-migrated curation shares.
+
+> **Note**: The first address to signal a particular subgraph is considered the first curator and will have to do much more gas-intensive work than the rest of the following curators because the first curator initializes the curation share tokens, and also transfers tokens into The Graph proxy.
+
+## Withdrawing your GRT
+
+Curators have the option to withdraw their signaled GRT at any time.
+
+Unlike the process of delegating, if you decide to withdraw your signaled GRT you will not have to wait for a cooldown period and will receive the entire amount (minus the 1% curation tax).
+
+Once a curator withdraws their signal, indexers may choose to keep indexing the subgraph, even if there's currently no active GRT signaled.
+
+However, it is recommended that curators leave their signaled GRT in place not only to receive a portion of the query fees, but also to ensure reliability and uptime of the subgraph.
+
+## Risks
+
+1. The query market is inherently young at The Graph and there is risk that your %APY may be lower than you expect due to nascent market dynamics.
+2. Curation Fee - when a curator signals GRT on a subgraph, they incur a 1% curation tax. This fee is burned.
+3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
+4. A subgraph can fail due to a bug. A failed subgraph does not accrue query fees. As a result, you’ll have to wait until the developer fixes the bug and deploys a new version.
+   - If you are subscribed to the newest version of a subgraph, your shares will auto-migrate to that new version. This will incur a 0.5% curation tax.
+   - If you have signaled on a specific subgraph version and it fails, you will have to manually burn your curation shares. You can then signal on the new subgraph version, thus incurring a 1% curation tax.
+
+## Curation FAQs
+
+### 1. What % of query fees do Curators earn?
+
+By signalling on a subgraph, you will earn a share of all the query fees that the subgraph generates. 10% of all query fees go to the Curators pro-rata to their curation shares. This 10% is subject to governance.
+
+### 2. How do I decide which subgraphs are high quality to signal on?
+
+Finding high-quality subgraphs is a complex task, but it can be approached in many different ways. As a Curator, you want to look for trustworthy subgraphs that are driving query volume. A trustworthy subgraph may be valuable if it is complete, accurate, and supports a dapp’s data needs. A poorly architected subgraph might need to be revised or re-published, and can also end up failing. It is critical for Curators to review a subgraph’s architecture or code in order to assess if a subgraph is valuable. As a result:
+
+- Curators can use their understanding of a network to try and predict how an individual subgraph may generate a higher or lower query volume in the future
+- Curators should also understand the metrics that are available through Graph Explorer. Metrics like past query volume and who the subgraph developer is can help determine whether or not a subgraph is worth signalling on.
+
+### 3. What’s the cost of updating a subgraph?
+
+Migrating your curation shares to a new subgraph version incurs a curation tax of 1%. Curators can choose to subscribe to the newest version of a subgraph. When curator shares get auto-migrated to a new version, Curators will also pay half curation tax, ie. 0.5%, because upgrading subgraphs is an on-chain action that costs gas.
+
+### 4. How often can I update my subgraph?
+
+It’s suggested that you don’t update your subgraphs too frequently. See the question above for more details.
+
+### 5. Can I sell my curation shares?
+
+Curation shares cannot be "bought" or "sold" like other ERC20 tokens that you may be familiar with. They can only be minted (created) or burned (destroyed).
+
+As a Curator on Arbitrum, you are guaranteed to get back the GRT you initially deposited (minus the tax).
+
+### 6. Am I eligible for a curation grant?
+
+Curation grants are determined individually on a case-by-case basis. If you need assistance with curation, please send a request to support@thegraph.zendesk.com.
+
+Still confused? Check out our Curation video guide below:
+
+<VideoEmbed youtube="VytTEcf0dxQ" />

From 1c24d4dc70ab15696917150d20fd241371849e08 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:23 -0500
Subject: [PATCH 0734/1325] New translations delegating.mdx (Romanian)

---
 website/pages/ro/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/ro/network/delegating.mdx b/website/pages/ro/network/delegating.mdx
index 81824234e072..eda60369e00a 100644
--- a/website/pages/ro/network/delegating.mdx
+++ b/website/pages/ro/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegator Guide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Listed below are the main risks of being a Delegator in the protocol.
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### The delegation unbonding period
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) _Note the 0.5% fee in the Delegation UI, as well as the 28 day
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *The top Indexer is giving Delegators 90% of the rewards. The
   middle one is giving Delegators 20%. The bottom one is giving Delegators ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculating Delegators expected return
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- A technical Delegator can also look at the Indexer's ability to use the Delegated tokens available to them. If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considering the query fee cut and indexing fee cut
 
-As described in the above sections, you should choose an Indexer that is transparent and honest about setting their Query Fee Cut and Indexing Fee Cuts. A Delegator should also look at the Parameters Cooldown time to see how much of a time buffer they have. After that is done, it is fairly simple to calculate the amount of rewards the Delegators are getting. The formula is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Considering the Indexer's delegation pool
 
-Another thing a Delegator has to consider is what proportion of the Delegation Pool they own. All delegation rewards are shared evenly, with a simple rebalancing of the pool determined by the amount the Delegator has deposited into the pool. This gives the Delegator a share of the pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considering the delegation capacity
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From f1ecca021468ae75a7f24c8b2e6e5363e586703f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:24 -0500
Subject: [PATCH 0735/1325] New translations delegating.mdx (Spanish)

---
 website/pages/es/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/es/network/delegating.mdx b/website/pages/es/network/delegating.mdx
index 2d1b5ab66ee3..8b5633c5e01b 100644
--- a/website/pages/es/network/delegating.mdx
+++ b/website/pages/es/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegar
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Guía del Delegador
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ A continuación se enumeran los principales riesgos de ser un Delegador en el pr
 
 Los Delegadores no pueden ser recortados por mal comportamiento, pero existe un impuesto sobre los Delegadores para desincentivar la toma de malas decisiones que puedan perjudicar la integridad de la red.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### El período de unbonding (desvinculación) de la delegación
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) _Ten en cuenta la tasa del 0,5% en la UI de la Delegación, así
@@ -41,9 +55,13 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Elige un Indexador fiable, que pague recompensas justas a sus Delegadores
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *El Indexador de arriba está dando a los Delegadores el 90% de
@@ -51,38 +69,52 @@ Indexing Reward Cut - The indexing reward cut is the portion of the rewards that
   Delegadores*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculando el retorno esperado para los Delegadores
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Un Delegador técnico también puede ver la capacidad de los Indexadores para usar los tokens que han sido delegados y la capacidad de disponibilidad a su favor. Si un Indexador no está asignando todos los tokens disponibles, no está obteniendo el beneficio máximo que podría obtener para sí mismo o para sus Delegadores.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Siempre ten en cuenta la tarifa por consulta y el recorte de recompensas para el Indexador
 
-Como se ha descrito en las secciones anteriores, debes elegir un indexador que sea transparente y honesto a la hora de establecer su corte de tarifa de consulta y cortes de tarifa de indexación. Un Delegador también debe fijarse en el tiempo de enfriamiento de los parámetros para ver de cuánto tiempo disponen. Una vez hecho esto, es bastante sencillo calcular la cantidad de recompensas que reciben los Delegadores. La fórmula es:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegación Imagen 3](/img/Delegation-Reward-Formula.png)
 
 ### Tener en cuenta el pool de delegación de cada Indexador
 
-Otra cosa que tiene que tener en cuenta un Delegador es qué proporción del Pool de Delegación posee. Todas las recompensas de la delegación se reparten de forma equitativa, con un simple reequilibrio del pool determinado por la cantidad que el Delegador haya depositado en el pool. De este modo, el Delegador recibe una parte del pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Fórmula para compartir](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Fórmula para compartir](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considerar la capacidad de delegación
 
-Otra cosa a tener en cuenta es la capacidad de delegación. Actualmente, el Ratio de Delegación está fijado en 16. Esto significa que si un Indexador ha stakeado 1.000.000 GRT, su Capacidad de Delegación es de 16.000.000 GRT de tokens delegados que puede utilizar en el protocolo. Cualquier token delegado que supere esta cantidad diluirá todas las recompensas del Delegador.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -90,16 +122,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### Error de "Transacción Pendiente" en MetaMask
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Ejemplo
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guía de la interfaz de usuario de la red
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 253d41585e833b4d7d564ebd2a4ef1f396d95151 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:25 -0500
Subject: [PATCH 0736/1325] New translations delegating.mdx (Arabic)

---
 website/pages/ar/network/delegating.mdx | 95 +++++++++++++++++--------
 1 file changed, 67 insertions(+), 28 deletions(-)

diff --git a/website/pages/ar/network/delegating.mdx b/website/pages/ar/network/delegating.mdx
index 18571df08c11..dd0a8164d29e 100644
--- a/website/pages/ar/network/delegating.mdx
+++ b/website/pages/ar/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## دليل المفوض
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,60 +34,84 @@ There are three sections in this guide:
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### فترة إلغاء التفويض
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
-<div sx={{ mx: 'auto', maxWidth: '400px' }}>لاحظ 0.5٪ رسوم التفويض ، بالإضافة إلى فترة 28 يوما لإلغاء التفويض.</div>
+<div sx={{ mx: 'auto', maxWidth: '400px' }}>
+  لاحظ 0.5٪ رسوم التفويض ، بالإضافة إلى فترة 28 يوما لإلغاء التفويض.
+</div>
 
 ### اختيار مفهرس جدير بالثقة مع عائد جيد للمفوضين
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
+
+#### Delegation Parameters
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   *المفهرس الأعلى يمنح المفوضين 90٪ من المكافآت. والمتوسط يمنح المفوضين 20٪. والأدنى يعطي المفوضين ~ 83٪.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-### حساب العائد المتوقع للمفوضين
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-A Delegator must consider a lot of factors when determining the return. These include:
+## Calculating Delegators Expected Return
 
-- يمكن للمفوض إلقاء نظرة على قدرة المفهرسين على استخدام التوكن المفوضة المتاحة لهم. إذا لم يقم المفهرس بتخصيص جميع التوكن المتاحة ، فإنه لا يكسب أقصى ربح يمكن أن يحققه لنفسه أو للمفوضين.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+A Delegator must consider the following factors to determine a return:
+
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### النظر في اقتطاع رسوم الاستعلام query fee cut واقتطاع رسوم الفهرسة indexing fee cut
 
-كما هو موضح في الأقسام أعلاه ، يجب عليك اختيار مفهرس يتسم بالشفافية والصدق بشأن اقتطاع رسوم الاستعلام Query Fee Cut واقتطاع رسوم الفهرسة Indexing Fee Cuts. يجب على المفوض أيضا إلقاء نظرة على بارامتارات Cooldown time لمعرفة مقدار الوقت المتاح لديهم. بعد الانتهاء من ذلك ، من السهل إلى حد ما حساب مقدار المكافآت التي يحصل عليها المفوضون. الصيغة هي:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![صورة التفويض 3](/img/Delegation-Reward-Formula.png)
 
 ### النظر في أسهم تفويض المفهرس
 
-باستخدام هذه الصيغة ، يمكننا أن نرى أنه من الممكن فعليا للمفهرس الذي يعرض 20٪ فقط للمفوضين ، أن يمنح المفوضين عائدا أفضل من المفهرس الذي يعطي 90٪ للمفوضين.
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![شارك الصيغة](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![شارك الصيغة](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### النظر في سعة التفويض (delegation capacity)
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -85,16 +119,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### مثال
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 1226a24841c6f2d788286f6a7f73d200c7a270b8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:26 -0500
Subject: [PATCH 0737/1325] New translations delegating.mdx (Czech)

---
 website/pages/cs/network/delegating.mdx | 95 +++++++++++++++++--------
 1 file changed, 66 insertions(+), 29 deletions(-)

diff --git a/website/pages/cs/network/delegating.mdx b/website/pages/cs/network/delegating.mdx
index d444c8edf2b3..249cd411e45a 100644
--- a/website/pages/cs/network/delegating.mdx
+++ b/website/pages/cs/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegování
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Průvodce delegáta
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Níže jsou uvedena hlavní rizika plynoucí z delegáta v protokolu.
 
 Delegáti nemohou být za špatné chování kráceni, ale existuje daň pro delegáty, která má odradit od špatného rozhodování, jež by mohlo poškodit integritu sítě.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Konec období vázanosti delegací
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Zrušení vázanosti delegací](/img/Delegation-Unbonding.png) _Všimněte si 0.5% poplatku v UI delegací a 28denní lhůty.
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Výběr důvěryhodného indexátora se spravedlivou odměnou pro delegáty
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Nejlepší indexátor dává delegátům 90 % odměn. Na prostřední dává
-  delegátům 20 % odměn. Spodní dává delegátům ~83 %.*
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Nejlepší indexátor dává delegátům 90 % odměn. Na
+  prostřední dává delegátům 20 % odměn. Spodní dává delegátům ~83 %.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Výpočet očekávaného výnosu delegátů
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Technický delegát se může také podívat na schopnost indexátoru používat dostupné delegované tokeny. Pokud Indexátor nealokuje všechny dostupné tokeny, nevydělává pro sebe ani pro své Delegáty maximální možný zisk.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### S ohledem na snížení poplatků za dotaz a indexaci
 
-Jak je popsáno v předchozích částech, měli byste si vybrat indexátor, který je transparentní a poctivý, pokud jde o nastavení snížení poplatků za dotaz a indexování. Delegovatel by se měl také podívat na dobu Cooldown parametrů, aby zjistil, jak velkou má časovou rezervu. Poté je poměrně jednoduché vypočítat výši odměn, které Delegátoři dostávají. Vzorec je následující:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegování Obrázek 3](/img/Delegation-Reward-Formula.png)
 
 ### Zohlednění fondu delegování indexátoru
 
-Další věcí, kterou musí delegát zvážit, je, jakou část fondu delegátů vlastní. Všechny odměny za delegování se rozdělují rovnoměrně, přičemž jednoduché vyvážení fondu se určuje podle částky, kterou delegát do fondu vložil. Delegát tak získá podíl na fondu:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Sdílet vzorec](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Sdílet vzorec](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Vzhledem ke kapacitě delegace
 
-Další věcí, kterou je třeba zvážit, je kapacita delegování. V současné době je poměr delegování nastaven na 16. To znamená, že pokud indexátor vsadil 1,000,000 GRT, jeho delegační kapacita je 16,000,000 GRT delegovaných tokenů, které může v protokolu použít. Jakékoli delegované tokeny nad toto množství rozředí všechny odměny delegátora.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### Chyba MetaMask "Čekající transakce"
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Příklad
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Videoprůvodce UI sítě
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 967ad4a8f03939f2c98fba6779c47255477d0d9b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:27 -0500
Subject: [PATCH 0738/1325] New translations delegating.mdx (German)

---
 website/pages/de/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/de/network/delegating.mdx b/website/pages/de/network/delegating.mdx
index 81824234e072..eda60369e00a 100644
--- a/website/pages/de/network/delegating.mdx
+++ b/website/pages/de/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegator Guide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Listed below are the main risks of being a Delegator in the protocol.
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### The delegation unbonding period
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) _Note the 0.5% fee in the Delegation UI, as well as the 28 day
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *The top Indexer is giving Delegators 90% of the rewards. The
   middle one is giving Delegators 20%. The bottom one is giving Delegators ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculating Delegators expected return
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- A technical Delegator can also look at the Indexer's ability to use the Delegated tokens available to them. If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considering the query fee cut and indexing fee cut
 
-As described in the above sections, you should choose an Indexer that is transparent and honest about setting their Query Fee Cut and Indexing Fee Cuts. A Delegator should also look at the Parameters Cooldown time to see how much of a time buffer they have. After that is done, it is fairly simple to calculate the amount of rewards the Delegators are getting. The formula is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Considering the Indexer's delegation pool
 
-Another thing a Delegator has to consider is what proportion of the Delegation Pool they own. All delegation rewards are shared evenly, with a simple rebalancing of the pool determined by the amount the Delegator has deposited into the pool. This gives the Delegator a share of the pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considering the delegation capacity
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 2f637402c37058457ceec224174fe234dd4f4946 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:28 -0500
Subject: [PATCH 0739/1325] New translations delegating.mdx (Italian)

---
 website/pages/it/network/delegating.mdx | 99 +++++++++++++++++--------
 1 file changed, 68 insertions(+), 31 deletions(-)

diff --git a/website/pages/it/network/delegating.mdx b/website/pages/it/network/delegating.mdx
index 11f73bec5765..d5c86e5ecf43 100644
--- a/website/pages/it/network/delegating.mdx
+++ b/website/pages/it/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegazione
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Guida per i delegator
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,86 @@ Di seguito sono elencati i principali rischi essere il Delegator nel protocollo.
 
 I delegator non possono essere penalizzati per un comportamento scorretto, ma c'è una tassa sui delegator per disincentivare un processo decisionale insufficiente che potrebbero danneggiare l'integrità della rete.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Il periodo di sblocco di delegazione
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Sblocco di Delegator](/img/Delegation-Unbonding.png) _Nota la commissione del 0,5% nel UI della delegazione, così
-  come il periodo di sblocco di 28 giorni. periodo di sblocco._
+  ![Sblocco di Delegator](/img/Delegation-Unbonding.png) _Nota la commissione del 0,5% nel UI della delegazione, così come il periodo di sblocco di 28 giorni.
+  periodo di sblocco._
 </div>
 
 ### Scegliere un Indexer affidabile con una giusta ricompensa per i Delegator
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Taglio delle ricompense dell'indicizzazione](/img/Indexing-Reward-Cut.png) *Il top Indexer sta dando ai Delegator il
-  90% delle ricompense. Il centrale dà ai Delegator il 20%. Quello in basso dà ai Delegator ~83%.*
+  ![Taglio delle ricompense dell'indicizzazione](/img/Indexing-Reward-Cut.png) *Il top Indexer sta dando ai Delegator il 90% delle ricompense. Il
+  centrale dà ai Delegator il 20%. Quello in basso dà ai Delegator ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calcolo del rendimento previsto dei Delegator
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Un Delegator tecnico può anche esaminare la capacità dell' Indexer di utilizzare i token delegati a sua disposizione. Se un Indexer non sta allocando tutti i token disponibili, non sta guadagnando il massimo profitto che potrebbe ottenere per sé o per i suoi Delegator.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considerando la riduzione delle tariffe di query e la riduzione delle tariffe di indicizzazione
 
-Come descritto nelle sezioni precedenti, è necessario scegliere un Indexer che sia trasparente e onesto nell'impostare il taglio delle tariffe di query e tagli delle tariffe di indicizzazione. Il Delegator dovrebbe anche controllare il tempo di Cooldown dei Parametri per vedere quanto tempo di riserva ha a disposizione. Una volta fatto questo, è abbastanza semplice calcolare la quantità delle ricompense che i Delegator ricevono. La formula è:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Immagine delegator 3](/img/Delegation-Reward-Formula.png)
 
 ### Considerando il delegation pool del Indexer
 
-Un altro aspetto che un Delegator deve considerare è il proporzione del Delegation Pool che possiede. Tutte le ricompense della delega sono condivise in modo uniforme, con un semplice ribilanciamento del pool determinato dall'importo che il Delegator ha depositato nel pool. In questo modo il Delegator ha una quota del pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Formula di condivisione](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Formula di condivisione](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considerando la capacità di delegazione
 
-Un altro aspetto da considerare è la capacità di Delegator. Attualmente, il Delegation Ratio è impostato su 16. Ciò significa che se un Indexer ha fatto un stake di 1,000,000 GRT, la sua Delegation Capacity è di 16,000,000 di GRT di token delegati che può utilizzare nel protocollo. Tutti i token delegati che superano questa quantità diluiranno tutte le ricompense dei Delegator.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Transazione in sospeso" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Esempio
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Guida video per UI della rete
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 52729ea07cfea7fd9a4ad919655969a101e2adbe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:30 -0500
Subject: [PATCH 0740/1325] New translations delegating.mdx (Japanese)

---
 website/pages/ja/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/ja/network/delegating.mdx b/website/pages/ja/network/delegating.mdx
index 80b87a30a8e2..f8aef10f6d04 100644
--- a/website/pages/ja/network/delegating.mdx
+++ b/website/pages/ja/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: 委任
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## デリゲーターガイド
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ There are three sections in this guide:
 
 デリゲーターは悪意の行動をしてもスラッシュされないが、デリゲーターにはデポジット税が課せられ、ネットワークの整合性を損なう可能性のある悪い意思決定を抑止します。
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### 委任期間無制限
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   デリゲーション UIの0.5%の手数料と、28日間のアンボンディング期間に注目してください。
@@ -40,47 +54,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### デリゲーターに公平な報酬を支払う信頼できるインデクサーの選択
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) ※上位インデクサーは委任者に90%の報酬を与えています。の
   中央のものは委任者に 20% を与えています。一番下のものは委任者に ~83% を与えています.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### デリゲーターの期待リターンを計算
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- デリゲーターは、インデクサーが利用可能なデリゲートトークンを使用する能力にも目を向けることができます。 もしインデクサーが利用可能なトークンをすべて割り当てていなければ、彼らは自分自身やデリゲーターのために得られる最大の利益を得られないことになります。
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### クエリフィーのカットとインデックスフィーのカットの検討
 
-上記のセクションで説明したように、クエリ料金カットとインデックス作成料金カットの設定について透明性があり誠実なインデクサーを選択する必要があります。デリゲーターは、パラメーターのクールダウン時間も調べて、どれだけの時間バッファーがあるかを確認する必要があります。その後、委任者が受け取る報酬の額を計算するのは非常に簡単です。式は次のとおりです。
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![デリゲーション イメージ 3](/img/Delegation-Reward-Formula.png)
 
 ### インデクサーのデリゲーションプールを考慮する
 
-委任者が考慮しなければならないもう 1 つのことは、自分が所有する委任プールの割合です。すべての委任報酬は均等に共有され、委任者がプールに入金した金額によって決定されるプールの単純なリバランスが行われます。これにより、委任者にプールのシェアが与えられます。
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![シェアの計算式](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![シェアの計算式](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### デリゲーションの容量を考慮する
 
-もうひとつ考慮しなければならないのが、デリゲーション能力です。 現在、デリゲーションレシオは 16 に設定されています。 これは、インデクサーが 1,000,000GRT をステークしている場合、そのデリゲーション容量はプロトコルで使用できる 16,000,000GRT のデリゲーショントークンであることを意味します。 この量を超えるデリゲートされたトークンは、全てのデリゲーター報酬を薄めてしまいます。
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -88,16 +120,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction "バグ
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### 例
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## ネットワーク UI のビデオガイド
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From fb9704ba870efff02fc0d17a28774bc31ad82479 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:31 -0500
Subject: [PATCH 0741/1325] New translations delegating.mdx (Korean)

---
 website/pages/ko/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/ko/network/delegating.mdx b/website/pages/ko/network/delegating.mdx
index 81824234e072..eda60369e00a 100644
--- a/website/pages/ko/network/delegating.mdx
+++ b/website/pages/ko/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegator Guide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Listed below are the main risks of being a Delegator in the protocol.
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### The delegation unbonding period
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) _Note the 0.5% fee in the Delegation UI, as well as the 28 day
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *The top Indexer is giving Delegators 90% of the rewards. The
   middle one is giving Delegators 20%. The bottom one is giving Delegators ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculating Delegators expected return
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- A technical Delegator can also look at the Indexer's ability to use the Delegated tokens available to them. If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considering the query fee cut and indexing fee cut
 
-As described in the above sections, you should choose an Indexer that is transparent and honest about setting their Query Fee Cut and Indexing Fee Cuts. A Delegator should also look at the Parameters Cooldown time to see how much of a time buffer they have. After that is done, it is fairly simple to calculate the amount of rewards the Delegators are getting. The formula is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Considering the Indexer's delegation pool
 
-Another thing a Delegator has to consider is what proportion of the Delegation Pool they own. All delegation rewards are shared evenly, with a simple rebalancing of the pool determined by the amount the Delegator has deposited into the pool. This gives the Delegator a share of the pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considering the delegation capacity
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From a3a9a37f749548e73d339ae95bd307fc66a162f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:32 -0500
Subject: [PATCH 0742/1325] New translations delegating.mdx (Dutch)

---
 website/pages/nl/network/delegating.mdx | 97 +++++++++++++++++--------
 1 file changed, 66 insertions(+), 31 deletions(-)

diff --git a/website/pages/nl/network/delegating.mdx b/website/pages/nl/network/delegating.mdx
index 80f125053f68..c0a3224f156c 100644
--- a/website/pages/nl/network/delegating.mdx
+++ b/website/pages/nl/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegeren
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegeerder Gids
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,84 @@ Hieronder staan de belangrijkste risico's van het zijn van een Delegeerder in he
 
 Delegeerders kunnen niet worden gestraft voor slecht gedrag, maar er is een belasting voor Delegeerders om slechte besluitvorming die de integriteit van het netwerk kan schaden te ontmoedigen.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Delegatieontbindingsperiode
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Let op de 0,5% belasting in de Delegatie UI, evenals de
-  28-daagse ontbindingsperiode_
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Let op de 0,5% belasting in de Delegatie UI, evenals de 28-daagse ontbindingsperiode_
 </div>
 
 ### Het kiezen van een betrouwbare Indexeerder met een eerlijke beloningsuitbetaling voor Delegeerders
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *De bovenste Indexeerder geeft Delegeerders 90% van de
-  beloningen. De middelste geeft Delegeerders 20%. De onderste geeft Delegeerders ~83%.*
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png)  *De bovenste Indexeerder geeft Delegeerders 90% van de beloningen. De middelste geeft Delegeerders 20%. De onderste geeft Delegeerders ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Het berekenen van de verwachte opbrengst van Delegeerders
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Een technische delegeerder kan ook kijken of een Indexeerder de aan hen beschikbaar gestelde gedelegeerde tokens wel volledig gebruikt. Als een Indexeerder niet alle beschikbare tokens toewijst, verdienen zij niet de maximale winst die mogelijk is voor zichzelf of hun Delegeerders.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Rekening houden met de query fee aandeel en indexing fee aandeel
 
-Zoals beschreven in de bovenstaande secties, moet je een Indexeerder kiezen die transparant en eerlijk is over het instellen van hun Query Fee Aandeel en Indexing Fee Aandeel. Een Delegeerder moet ook kijken naar de parameter "Cooldown Time" om te zien hoeveel van een tijdsbuffer ze hebben. Nadat dat is gedaan, is het vrij eenvoudig om de hoeveelheid beloningen te berekenen die Delegators ontvangen. De formule is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegatie Figuur 3](/img/Delegation-Reward-Formula.png)
 
 ### Rekening houden met de delegatie pool van een Indexeerder
 
-Een andere factor waarmee een Delegeerder rekening moet houden, is welk deel van de Delegatiepool zij bezitten. Alle beloningen uit delegatie worden gelijk verdeeld, overeenkomstig een eenvoudige herverdeling van de pool, die bepaald wordt door de hoeveelheid die de Delegeerder in de pool heeft gestort. Dit geeft de Delegeerder een aandeel in de pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Deel Formule](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Deel Formule](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Rekening houden met de delegatiecapaciteit
 
-Een andere factor om te overwegen is de delegatiecapaciteit. Momenteel is de Delegatie Ratio ingesteld op 16. Dit betekent dat als een Indexeerder 1.000.000 GRT heeft gestaked, hun Delegatiecapaciteit 16.000.000 GRT aan gedelegeerde tokens is die ze kunnen gebruiken in het protocol. Elke gedelegeerde token boven dit bedrag zal voor alle Delegeerders de beloningen verwateren.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +119,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Videohandleiding voor de netwerk-gebruikersomgeving
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From b27c20c4974c08b377d7ff3cc9183ab5afd45c52 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:33 -0500
Subject: [PATCH 0743/1325] New translations delegating.mdx (Polish)

---
 website/pages/pl/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/pl/network/delegating.mdx b/website/pages/pl/network/delegating.mdx
index 81824234e072..eda60369e00a 100644
--- a/website/pages/pl/network/delegating.mdx
+++ b/website/pages/pl/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegator Guide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Listed below are the main risks of being a Delegator in the protocol.
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### The delegation unbonding period
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) _Note the 0.5% fee in the Delegation UI, as well as the 28 day
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *The top Indexer is giving Delegators 90% of the rewards. The
   middle one is giving Delegators 20%. The bottom one is giving Delegators ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculating Delegators expected return
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- A technical Delegator can also look at the Indexer's ability to use the Delegated tokens available to them. If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considering the query fee cut and indexing fee cut
 
-As described in the above sections, you should choose an Indexer that is transparent and honest about setting their Query Fee Cut and Indexing Fee Cuts. A Delegator should also look at the Parameters Cooldown time to see how much of a time buffer they have. After that is done, it is fairly simple to calculate the amount of rewards the Delegators are getting. The formula is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Considering the Indexer's delegation pool
 
-Another thing a Delegator has to consider is what proportion of the Delegation Pool they own. All delegation rewards are shared evenly, with a simple rebalancing of the pool determined by the amount the Delegator has deposited into the pool. This gives the Delegator a share of the pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considering the delegation capacity
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From c157e0f76ad605f1df6e70870500481a9327fec6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:34 -0500
Subject: [PATCH 0744/1325] New translations delegating.mdx (Portuguese)

---
 website/pages/pt/network/delegating.mdx | 97 +++++++++++++++++--------
 1 file changed, 66 insertions(+), 31 deletions(-)

diff --git a/website/pages/pt/network/delegating.mdx b/website/pages/pt/network/delegating.mdx
index b321854faa52..97c25db9c751 100644
--- a/website/pages/pt/network/delegating.mdx
+++ b/website/pages/pt/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegação
 ---
 
-Os Delegantes são participantes da rede que delegam (por ex., "stake") GRT a um ou mais Indexadores. Estes contribuem à segurança da rede sem executar um Graph Node por conta própria.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Os Delegantes ganham uma porção das taxas de query e recompensas do Indexador ao delegar a ele. A quantidade de queries que um Indexador pode processar depende do próprio stake, do stake delegado e do preço que o Indexador cobra por cada consulta, portanto, quanto mais stake for alocado a um Indexador, mais queries ele pode processar.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Guia do Delegante
 
-Este guia explicará como ser um Delegante eficaz na Graph Network. Os Delegantes dividem a renda do protocolo com todos os Indexadores, com base no seu stake delegado. Um Delegante deve raciocinar bem para escolher Indexadores, baseado em vários fatores. Perceba que este guia não abordará passos como a configuração apropriada do MetaMask, já que essa informação está amplamente disponível na internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 Há três secções neste guia:
 
@@ -24,64 +34,84 @@ Veja abaixo os riscos principais de ser um Delegante no protocolo.
 
 Os Delegantes não podem ser punidos por mau comportamento, mas há uma taxa sobre Delegantes, para desencorajar más decisões que possam ferir a integridade da rede.
 
-É importante entender que, sempre que delega, o Delegante será cobrado 0.5%. Ou seja, se delegar 1000 GRT, automaticamente queimará 5 GRT.
+As a Delegator, it's important to understand the following:
 
-Por questões de segurança, um Delegante deve calcular o seu retorno potencial ao delegar a um Indexador. Por exemplo, um Delegante pode calcular quantos dias demorará até conseguir quitar a taxa de 0.5% na sua delegação.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### O período de separação da delegação
 
 Se um Delegado quiser cancelar a sua delegação, seus tokens estarão sujeitos a um período de 28 dias sem transferência, e também não poderá ganhar quaisquer recompensas por este período.
 
-Considere escolher um Indexador com muito cuidado. Se escolher um Indexador que não é de confiança, ou não fez um bom trabalho, talvez queira cancelar a sua delegação, o que implica em sacrificar muitas oportunidades de recompensa, o que pode ser tão lamentável quanto queimar GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Perceba a taxa de 0.5% na interface da Delegação, além do
-  período de separação de 28 dias._
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Perceba a taxa de 0.5% na interface da Delegação, além do período de separação de 28 dias._
 </div>
 
 ### Como escolher um Indexador de confiança, com um pagamento justo para Delegantes
 
-Este é um aspecto importante. Primeiro, vamos discutir três valores muito importantes: os Parâmetros de Delegação.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Porção da Recompensa de Indexação - Esta é a porção das recompensas que o Indexador guardará para si. Isto significa que, se esta for configurada para 100%, o Delegante receberá 0 recompensas de indexação. Se ver 80% na interface, isto significa que, como Delegado, receberá 20%. Importante saber que no começo da rede, as Recompensas de Indexação contarão como a maioria das recompensas.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *O Indexador acima está a dar 90% das recompensas aos Delegantes,
-  o do meio dá 20%, e o de baixo dá cerca de 83%.*
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *O Indexador acima está a dar 90% das recompensas aos Delegantes, o do meio dá 20%, e o de baixo dá cerca de 83%.*
 </div>
 
-- Porção da Taxa de Recompensa - Isto funciona exatamente como a Porção da Recompensa de Indexação. Porém, isto aplica-se explicitamente a retornos nas taxas de consulta coletadas pelo Indexador. Perceba que, no começo da rede, os retornos de taxas de query serão muito menores que a recompensa de indexação. Vale prestar atenção na rede para determinar quando as taxas de consulta na rede começarão a ser mais significantes.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-Como pode-se ver, há muito a considerar ao escolher o Indexador certo. É por isto que vale a pena explorar o [Discord do The Graph](https://discord.gg/graphprotocol) para determinar quais Indexadores tem as melhores reputações sociais e técnicas, a fim de recompensar Delegantes com consistência. Muitos dos Indexadores são ativos no Discord e estarão prontos para responder as suas perguntas. Muitos deles indexam há meses na testnet e fazem o seu melhor para ajudar os Delegantes a ganhar bons retornos, pois isto melhora a saúde e o êxito da rede.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Como calcular o retorno esperado dos Delegados
+## Calculating Delegators Expected Return
 
-Um Delegante tem muito a considerar ao determinar o retorno. Os fatores incluem:
+A Delegator must consider the following factors to determine a return:
 
-- Um Delegante técnico também pode examinar a habilidade do Indexador de usar os tokens Delegados a ele disponíveis. Se um Indexador não aloca todos os tokens disponíveis, eles não estão a ganhar o lucro máximo que poderia ser para si mesmo ou para os seus Delegados.
-- Agora mesmo, na rede, um Indexador pode escolher fechar uma alocação e resgatar as recompensas entre 1 e 28 dias. Então, é possível que um Indexador tenha muitas recompensas a resgatar, assim, diminuindo as suas recompensas totais. Isto deve ser considerado nos primeiros dias.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Como considerar as porções das taxas de query e de indexação
 
-Como dito nas seções acima, deve escolher um Indexador que seja transparente e honesto sobre a configuração das suas porções de taxas de query e de indexação. Um Delegante também deve verificar o tempo de recarga dos parâmetros, para ver quanto tempo de preparo ele tem. Tudo isto feito, é simples calcular as recompensas que os Delegantes ganham. A fórmula é:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Imagem de delegação 3](/img/Delegation-Reward-Formula.png)
 
 ### Como considerar o pool de delegação do Indexador
 
-Um Delegante também deve considerar a proporção do Pool de Delegação que tem. Todas as recompensas de delegação são divididas igualmente, com um rebalanço simples do pool determinado pela quantidade que o Delegado nele depositou. Isto dá ao delegado uma porção:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Fórmula de ações](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Esta fórmula mostra que é possível que um Indexador que oferece apenas 20% para os Delegantes, dê uma recompensa melhor que um que dá 90%.
+This gives the Delegator a share of the pool:
+
+![Fórmula de ações](/img/Share-Forumla.png)
 
-Um Delegante pode então fazer as contas para determinar que o Indexador que oferece 20% aos Delegantes oferece um retorno melhor.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Como considerar a capacidade de delegação
 
-Atualmente, a Proporção de Delegação é configurada em 16. Portanto, caso um Indexador tenha feito stake em 1.000.000 GRT, sua Capacidade de Delegação é 16.000.000 de tokens delegados que eles podem usar no protocolo. Quaisquer tokens delegados acima desta quantidade diluirão todas as recompensas do Delegante.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine que um Indexador tem 100.000.000 GRT delegados a ele, e a sua capacidade é de apenas 16.000.000 GRT. Efetivamente, 84.000.000 tokens GRT não estão em uso para ganhar tokens. E todos os Delegantes, e o Indexador, ganham muito menos recompensas do que deveriam ganhar.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Assim, um Delegante deve sempre considerar a Capacidade de Delegação de um Indexador, e levá-la em conta ao tomar decisões.
 
@@ -89,16 +119,21 @@ Assim, um Delegante deve sempre considerar a Capacidade de Delegação de um Ind
 
 ### Erro de "Transação Pendente" no MetaMask
 
-**Quando eu tento delegar a minha transação no MetaMask, ela aparece como "Pendente" ou "Na Fila" por mais tempo que o esperado. O que devo fazer?**
+1. Quando eu tento delegar a minha transação no MetaMask, ela aparece como "Pendente" ou "Na Fila" por mais tempo que o esperado. O que devo fazer?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Exemplo
 
-Às vezes, tentativas de delegar a Indexadores via MetaMask podem falhar e causar que tentativas de transação fiquem "Pendentes" ou "Em Fila" por períodos prolongados.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-Por exemplo, um utilizador pode tentar delegar com uma taxa de gás insuficiente em relação aos preços atuais, fazendo com que a tentativa de transação fique como "Pendente" na sua carteira do MetaMask por mais de 15 minutos. Quando isto ocorre, um utilizador pode tentar mais transações, mas estas só serão processadas até a transação inicial for minerada, já que as transações para um endereço devem ser processadas em ordem. Em tais casos, estas transações podem ser canceladas no MetaMask, mas as tentativas de transação acumularão taxas de gas sem nenhuma garantia que as tentativas seguintes terão êxito.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-Uma solução mais simples para este bug é a reinicialização do navegador (por ex., usar "abort:restart" na barra de endereço), o que cancelará todas as tentativas anteriores sem subtrair gas da carteira. Vários utilizadores que encontraram este problema relataram êxito nas transações após reiniciar o seu navegador e tentar delegar.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Guia de vídeo para a interface da rede
+## Video Guide
 
-Este guia em vídeo apresenta uma revisão completa desde documento e explica como considerar tudo nele durante as interações com a interface de utilizador.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From fc9f38417a4be995eeee9e9694f00a4e7481398f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:35 -0500
Subject: [PATCH 0745/1325] New translations delegating.mdx (Swedish)

---
 website/pages/sv/network/delegating.mdx | 100 ++++++++++++++++--------
 1 file changed, 69 insertions(+), 31 deletions(-)

diff --git a/website/pages/sv/network/delegating.mdx b/website/pages/sv/network/delegating.mdx
index 171c745fdd68..42363dfd0958 100644
--- a/website/pages/sv/network/delegating.mdx
+++ b/website/pages/sv/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegera
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegateringsguide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,87 @@ Här nedan listas huvudriskerna med att vara en Delegater i protokollet.
 
 Delegater kan inte "slashas" för dåligt beteende, men det finns en avgift för Delegater för att avskräcka dåligt beslutsfattande som kan skada nätverkets integritet.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Perioden för upphävande av delegering
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation upphävning](/img/Delegation-Unbonding.png) _Observera avgiften på 0,5% i Delegation UI, samt den 28 dagar
-  långa upphävningsperioden._
+  ![Delegation upphävning](/img/Delegation-Unbonding.png) _Observera avgiften
+på 0,5% i Delegation UI, samt den 28 dagar långa   upphävningsperioden._
 </div>
 
 ### Att välja en pålitlig Indexer med en rättvis belöningsutbetalning till Delegater
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Edward Cut](/img/Indexing-Reward-Cut.png) *Den översta Indexet ger Delegater 90% av belöningarna. Den
-  mellersta ger Delegater 20%. Den nedersta ger Delegater ~83%.*
+  ![Indexing Edward Cut](/img/Indexing-Reward-Cut.png) *Den översta Indexet ger
+Delegater 90% av belöningarna. Den   mellersta ger Delegater 20%. Den nedersta
+ger Delegater ~83%.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Beräkning av Delegaters förväntade avkastning
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- En teknisk Delegater kan också titta på Indexer's förmåga att använda de Delegerade tokens som är tillgängliga för dem. Om en Indexer inte allokerar alla tillgängliga tokens tjänar de inte maximal vinst de kunde för sig själva eller sina Delegater.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Att överväga frågebetalningsavgiften och indexeringsavgiften
 
-Som beskrivs i de ovanstående avsnitten bör du välja en Indexer som är öppen och ärlig om att sätta sina frågebetalningsavgifter och indexeringsavgifter. En Delegater bör också titta på Parametrarnas Kylningstid för att se hur mycket tidsskydd de har. Efter att detta är gjort är det ganska enkelt att beräkna den mängd belöningar som Delegaterna får. Formeln är:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegering Bild 3](/img/Delegation-Reward-Formula.png)
 
 ### Att överväga Indexer's delegeringspool
 
-En annan sak som en Delegater måste överväga är vilken proportion av Delegationspoolen de äger. Alla delegationsbelöningar delas jämnt, med en enkel omviktning av poolen som avgörs av det belopp som Delegaterna har deponerat i poolen. Det ger Delegaterna en andel av poolen:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Dela formel](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Dela formel](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Att överväga delegeringskapaciteten
 
-En annan sak att överväga är delegeringskapaciteten. För närvarande är Delegationsförhållandet inställt på 16. Det innebär att om en Indexer har satsat 1 000 000 GRT är deras Delegationskapacitet 16 000 000 GRT av Delegerade tokens som de kan använda i protokollet. Alla delegerade tokens över denna mängd kommer att utspäda alla Delegaternas belöningar.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +122,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### Metamask "Väntande transaktion" bugg
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Exempel
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Videoguide för nätverks-UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 0539ad586fcd09d2728819b7ca55e2140f1632c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:36 -0500
Subject: [PATCH 0746/1325] New translations delegating.mdx (Ukrainian)

---
 website/pages/uk/network/delegating.mdx | 97 +++++++++++++++++--------
 1 file changed, 66 insertions(+), 31 deletions(-)

diff --git a/website/pages/uk/network/delegating.mdx b/website/pages/uk/network/delegating.mdx
index be101087c591..8327acb60b7b 100644
--- a/website/pages/uk/network/delegating.mdx
+++ b/website/pages/uk/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Делегування
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Гайд для делегатів
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,84 @@ There are three sections in this guide:
 
 Делегати не можуть бути виключені за погану поведінку, але існує певний штраф для них, щоб позбавити стимулу щодо прийняття поганих рішень, які можуть зашкодити цілісності мережі.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Період розблокування делегації
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Зверніть увагу на комісію в розмірі 0,5% в Інтерфейсі для
-  делегацій, а також на 28-денний період розблокування._
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Зверніть увагу на комісію в розмірі 0,5% в Інтерфейсі для делегацій, а також на 28-денний період розблокування._
 </div>
 
 ### Вибір надійного індексатора зі справедливою винагородою для делегатів
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Найкращий індексатор віддає делегатам 90% від суми винагороди.
-  Середній - 20%. Найменший індексатор дає ~83%. *
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Найкращий індексатор віддає делегатам 90% від суми винагороди. Середній - 20%. Найменший індексатор дає ~83%. *
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Розрахунок очікуваного прибутку
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Технічно підкований делегат також може подивитися на ефективність індексатора використовувати делеговані токени, які йому доступні. Якщо індексатор не використовує всі наявні токени, він не отримує максимального прибутку, який міг би отримати сам або його делегати.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Розглянемо питання про отримання частини винагороди за індексацію та за запити
 
-Як описано в попередніх підрозділах, ви повинні обрати індексатора, який є відкритим і чесним у призначенні комісій за запити та за індексацію. Делегат також повинен звернути увагу на час перезарядження параметрів, щоб побачити, який часовий буфер він має. Після цього досить просто розрахувати суму винагороди, яку отримують делегати. Формула наступна:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Розглянемо пул делегацій індексатора
 
-Ще один момент, який повинен враховувати делегат, — це те, якою часткою пулу делегацій він володіє. Всі винагороди за делегацію розподіляються рівномірно, шляхом простого перерозподілу пулу, що визначається сумою, яку делегат вніс до пулу. Це дає делегату певну частку пулу:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Розглянемо ліміт делегування
 
-Інша річ, яку слід враховувати, — це ліміт делегування. Зараз коефіцієнт делегування встановлений на рівні 16. Це означає, що якщо індексатор застейкав 1 000 000 GRT, його ліміт делегації становить 16 000 000 GRT делегованих токенів, які він може використовувати в протоколі. Будь-які делеговані токени, що перевищують цю суму, розмивають всі винагороди делегата.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +119,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### Баг в гаманці MetaMask "Pending Transaction"
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Відеоінструкція, по взаємодії з інтерфейсом мережі Graph
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 62312b9254e72d9acebc7e89ee4815c73cdd6f9c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:37 -0500
Subject: [PATCH 0747/1325] New translations delegating.mdx (Chinese
 Simplified)

---
 website/pages/zh/network/delegating.mdx | 98 +++++++++++++++++--------
 1 file changed, 68 insertions(+), 30 deletions(-)

diff --git a/website/pages/zh/network/delegating.mdx b/website/pages/zh/network/delegating.mdx
index 572cd98d99bb..80ca76888364 100644
--- a/website/pages/zh/network/delegating.mdx
+++ b/website/pages/zh/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: 委托
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## 委托人指南
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,61 +34,84 @@ There are three sections in this guide:
 
 委托人不能因为不良行为而被取消，但对委托有税，以抑制可能损害网络完整性的不良决策。
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### 委托解约期
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
-<div sx={{ mx: 'auto', maxWidth: '400px' }}>请注意委托用户界面中的0.5%费用，以及28天的解约期。</div>
+<div sx={{ mx: 'auto', maxWidth: '400px' }}>
+  请注意委托用户界面中的0.5%费用，以及28天的解约期。
+</div>
 
 ### 选择一个为委托人提供公平的奖励分配的值得信赖的索引人
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
+
+#### Delegation Parameters
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *上 面的索引人分给委托人 90% 的收益。 中间的给委托人 20%。
-  下面的给委托人约 83%。
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *上 面的索引人分给委托人 90% 的收益。 中间的给委托人 20%。 下面的给委托人约 83%。
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-### 计算委托人的预期收益
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-A Delegator must consider a lot of factors when determining the return. These include:
+## Calculating Delegators Expected Return
 
-- 有技术的委托人还可以查看索引人使用他们可用的委托代币的能力。 如果索引人没有分配所有可用的代币，他们就不会为自己或他们的委托人赚取最大利润。
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+A Delegator must consider the following factors to determine a return:
+
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### 考虑到查询费用的分成和索引费用的分成
 
-如上文所述，你应该选择一个在设置他们的查询费分成和索引奖励分成方面透明和诚实的索引人。 委托人还应该看一下参数冷却时间，看看他们有多少时间缓冲区。 做完这些之后，计算委托人会获得的奖励金额就相当简单了。 计算公式是：
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![委托图片3](/img/Delegation-Reward-Formula.png)
 
 ### 考虑索引人委托池
 
-委托人必须考虑的另一件事是他们拥有的委托池的比例。 所有的委托奖励都是平均分配的，根据委托人存入池子的数额来决定池子的简单再平衡。 这使委托人就拥有了委托池的份额:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![共享公式](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![共享公式](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### 考虑委托容量
 
-另一个需要考虑的是委托容量。 目前，委托比例被设置为 16。 这意味着，如果一个索引人质押了100万GRT，他们的委托容量是 16,00万GRT 的委托代币，他们可以在协议中使用。 任何超过这个数量的委托代币将稀释所有的委托人奖励。
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -86,16 +119,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask“待定交易”错误
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### 示例
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## 网络界面视频指南
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 8ea493362837d961419b03def6181e5c99492c51 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:38 -0500
Subject: [PATCH 0748/1325] New translations delegating.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/delegating.mdx | 98 +++++++++++++++++--------
 1 file changed, 67 insertions(+), 31 deletions(-)

diff --git a/website/pages/ur/network/delegating.mdx b/website/pages/ur/network/delegating.mdx
index ac3591610138..5bc50cb9ce02 100644
--- a/website/pages/ur/network/delegating.mdx
+++ b/website/pages/ur/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: ڈیلیگیٹنگ
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## ڈیلیگیٹر گائیڈ
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,85 @@ There are three sections in this guide:
 
 برے رویۓ پر ڈیلیگیٹرز کو نہیں چھوڑا جا سکتا، لیکن ناقص فیصلہ سازی کی حوصلہ شکنی کے لیے ڈیلیگیٹرز پر ٹیکس ہے جو نیٹ ورک کی سالمیت کو نقصان پہنچا سکتا ہے.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### وفد کی بندش کی مدت
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  [ڈیلیگیشن ان بانڈنگ](/img/Delegation-Unbonding.png) _ڈیلیگیشن UI میں 0.5% فیس نوٹ کریں، ساتھ ہی 28 دن غیر بندھن کی
-  مدت۔_
+  [ڈیلیگیشن ان بانڈنگ](/img/Delegation-Unbonding.png) _ڈیلیگیشن UI میں 0.5% فیس نوٹ کریں، ساتھ ہی 28 دن
+  غیر بندھن کی مدت۔_
 </div>
 
 ### ڈیلیگیٹرز کے لیے منصفانہ انعامی ادائیگی کے ساتھ ایک قابل اعتماد انڈیکسر کا انتخاب کرنا
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![انڈیکسنگ ریوارڈ کٹ](/img/Indexing-Reward-Cut.png) *سب سے اوپر انڈیکسر ڈیلیگیٹرز کو 90% انعامات دے رہا ہے. درمیان
-  والا ڈیلیگیٹرز کو 20% دے رہا ہے۔ نیچے والا ڈیلیگیٹرز کو ~83% دے رہا ہے۔*
+  ![انڈیکسنگ ریوارڈ کٹ](/img/Indexing-Reward-Cut.png) *سب سے اوپر انڈیکسر ڈیلیگیٹرز کو 90% انعامات دے رہا ہے. درمیان والا ڈیلیگیٹرز کو 20% دے رہا ہے۔ نیچے والا ڈیلیگیٹرز کو ~83% دے رہا ہے۔*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### ڈیلیگیٹرز کی متوقع واپسی کا حساب لگانا
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- ایک ٹیکنیکل ڈیلیگیٹر انڈیکسر کی ان کے لیے دستیاب ڈیلیگیٹڈ ٹوکن استعمال کرنے کی صلاحیت کو بھی دیکھ سکتا ہے۔ اگرایک انڈیکسر دستیاب تمام ٹوکن مختص نہیں کر رہا ہے، وہ زیادہ سے زیادہ منافع نہیں کما رہے ہیں جو وہ اپنے یا اپنے ڈیلیگیٹرز کے لیے ہو سکتا ہے.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### کیوری فیس میں کمی اور انڈیکسنگ کی فیس میں کمی پر غور کرنا
 
-جیسا کہ اوپر والے حصوں میں بیان کیا گیا ہے، آپ کو ایک انڈیکسر کا انتخاب کرنا چاہیے جو ان کے کیوری کو ترتیب دینے کے بارے میں شفاف اور ایماندار ہو۔ فیس کٹ اور انڈیکسنگ فیس میں کٹوتی۔ ایک ڈیلیگیٹر کو پیرامیٹرز کولڈاؤن ٹائم کو بھی دیکھنا چاہئے تاکہ یہ معلوم ہو سکے کہ ان کے پاس کتنا ٹائم بفر ہے۔ اس کے مکمل ہونے کے بعد، ڈیلیگیٹرز کو ملنے والے انعامات کی مقدار کا حساب لگانا کافی آسان ہے۔ فارمولا ہے:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![ڈیلیگیشن کی تصویر 3](/img/Delegation-Reward-Formula.png)
 
 ### انڈیکسر کے ڈیلیگیشن پول پر غور کرنا
 
-ایک اور چیز جس پر ایک ڈیلیگیٹر کو غور کرنا ہوگا وہ یہ ہے کہ ڈیلیگیشن پول کا کتنا تناسب ان کے پاس ہے۔ تمام ڈیلیگیشن انعامات یکساں طور پر بانٹ دیے جاتے ہیں، پول کی ایک سادہ ری بیلنسنگ کے ساتھ جو ڈیلیگیٹر نے پول میں جمع کروائی ہے۔ یہ ڈیلیگیٹر کو پول کا حصہ دیتا ہے:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![فارمولہ شیئر کریں](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![فارمولہ شیئر کریں](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### ڈیلیگیشن کی صلاحیت کو مدنظر رکھتے ہوئے
 
-غور کرنے کی ایک اور چیز ڈیلیگیشن کی صلاحیت ہے۔ فی الحال، ڈیلیگیشن تناسب 16 پر سیٹ ہے۔ اس کا مطلب یہ ہے کہ اگر کسی انڈیکسر نے 1,000,000 GRT کا حصہ لگایا ہے، ان کی ڈیلیگیشن کی صلاحیت ڈیلیگیٹڈ ٹوکنز کی 16,000,000 GRT ہے جسے وہ پروٹوکول میں استعمال کر سکتے ہیں۔ اس رقم پر کوئی بھی ڈیلیگیٹ ٹوکن ڈیلیگیٹر کے تمام انعامات کو کم کردے گا.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +120,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### میٹا ماسک "پینڈنگ ٹرانزیکشن" بگ
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### مثال
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## نیٹ ورک UI کے لیے ویڈیو گائیڈ
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 482b14b11d8ab1afd26ec9dd3fa414e76ef95c03 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:39 -0500
Subject: [PATCH 0749/1325] New translations delegating.mdx (Vietnamese)

---
 website/pages/vi/network/delegating.mdx | 91 +++++++++++++++++--------
 1 file changed, 64 insertions(+), 27 deletions(-)

diff --git a/website/pages/vi/network/delegating.mdx b/website/pages/vi/network/delegating.mdx
index 94555fdaaf3b..64c0c29c9d8f 100644
--- a/website/pages/vi/network/delegating.mdx
+++ b/website/pages/vi/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Hướng dẫn Delegator
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,15 +34,19 @@ Lưu ý quan trọng là mỗi lần bạn ủy quyền, bạn sẽ bị tính p
 
 Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### Khoảng thời gian bỏ ràng buộc ủy quyền
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![Delegation unbonding](/img/Delegation-Unbonding.png) Lưu ý khoản phí 0.5% trong Giao diện người dùng Ủy quyền, cũng
@@ -41,47 +55,65 @@ Another thing to consider is how to choose an Indexer wisely. If you choose an I
 
 ### Chọn một indexer đáng tin cậy với phần thưởng hợp lý cho delegator
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) Indexer hàng đầu đang trao cho delegator 90% phần thưởng. Những
   Indexer tầm trung đang trao cho delegator 20%. Những Indexer dưới cùng đang trao cho delegator khoản 83%.
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Tính toán lợi nhuận dự kiến của Delegator
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- Một Delegator có trình độ kỹ thuật cũng có thể xem xét cách mà Indexer sử dụng các token được Ủy quyền khả dụng cho họ. Nếu một indexer không phân bổ tất cả các token khả dụng, họ sẽ không kiếm được lợi nhuận tối đa mà họ có thể dành cho chính họ hoặc Delegator của họ.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Xem xét Phần cắt Phí Truy vấn và Phần cắt Phí indexing
 
-As described in the above sections, you should choose an Indexer that is transparent and honest about setting their Query Fee Cut and Indexing Fee Cuts. A Delegator should also look at the Parameters Cooldown time to see how much of a time buffer they have. After that is done, it is fairly simple to calculate the amount of rewards the Delegators are getting. The formula is:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Xem xét Delegation pool của Indexer
 
-Another thing a Delegator has to consider is what proportion of the Delegation Pool they own. All delegation rewards are shared evenly, with a simple rebalancing of the pool determined by the amount the Delegator has deposited into the pool. This gives the Delegator a share of the pool:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Xem xét Delegation Capacity (Năng lực Ủy quyền)
 
-Another thing to consider is the delegation capacity. Currently, the Delegation Ratio is set to 16. This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of Delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Ví dụ
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 72b2b085d0cbed92cf0eed47b07b33f068f00a33 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:40 -0500
Subject: [PATCH 0750/1325] New translations delegating.mdx (Marathi)

---
 website/pages/mr/network/delegating.mdx | 97 +++++++++++++++++--------
 1 file changed, 67 insertions(+), 30 deletions(-)

diff --git a/website/pages/mr/network/delegating.mdx b/website/pages/mr/network/delegating.mdx
index 0380a837269d..8877d25721c4 100644
--- a/website/pages/mr/network/delegating.mdx
+++ b/website/pages/mr/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
 
 ## Delegator Guide
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
 
 There are three sections in this guide:
 
@@ -24,64 +34,86 @@ Listed below are the main risks of being a Delegator in the protocol.
 
 वाईट वर्तनासाठी प्रतिनिधींना कमी केले जाऊ शकत नाही, परंतु नेटवर्कच्या अखंडतेला हानी पोहोचवणाऱ्या खराब निर्णयक्षमतेला प्रोत्साहन देण्यासाठी प्रतिनिधींवर कर लावला जातो.
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+As a Delegator, it's important to understand the following:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
 
 ### The delegation unbonding period
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![प्रतिनिधी अनबॉन्डिंग](/img/Delegation-Unbonding.png) _डेलिगेशन UI मध्ये 0.5% शुल्क तसेच २८ दिवसांची नोंद घ्या
-  अनबॉन्डिंग कालावधी._
+   अनबॉन्डिंग कालावधी._
 </div>
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *टॉप इंडेक्सर प्रतिनिधींना 90% बक्षिसे देत आहे. द मधला
-  प्रतिनिधी 20% देत आहे. सर्वात खालचा भाग प्रतिनिधींना ~83% देत आहे.*
+  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *टॉप इंडेक्सर प्रतिनिधींना 90% बक्षिसे देत आहे. द
+   मधला प्रतिनिधी 20% देत आहे. सर्वात खालचा भाग प्रतिनिधींना ~83% देत आहे.*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
 
-### Calculating Delegators expected return
+## Calculating Delegators Expected Return
 
-A Delegator must consider a lot of factors when determining the return. These include:
+A Delegator must consider the following factors to determine a return:
 
-- तांत्रिक प्रतिनिधी त्यांच्याकडे उपलब्ध असलेले प्रतिनिधी टोकन वापरण्याची इंडेक्सरची क्षमता देखील पाहू शकतो. जर इंडेक्सर उपलब्ध असलेल्या सर्व टोकन्सचे वाटप करत नसेल, तर ते स्वतःसाठी किंवा त्यांच्या प्रतिनिधींसाठी जास्तीत जास्त नफा मिळवत नाहीत.
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
 
 ### Considering the query fee cut and indexing fee cut
 
-वरील विभागांमध्ये वर्णन केल्याप्रमाणे, तुम्ही एक इंडेक्सर निवडला पाहिजे जो त्यांच्या क्वेरी फी कट आणि इंडेक्सिंग फी कट सेट करण्याबद्दल पारदर्शक आणि प्रामाणिक असेल. त्यांच्याकडे किती वेळ बफर आहे हे पाहण्यासाठी प्रतिनिधीने पॅरामीटर्स कूलडाउन टाइम देखील पहावे. ते पूर्ण झाल्यानंतर, प्रतिनिधींना किती बक्षिसे मिळत आहेत याची गणना करणे अगदी सोपे आहे. सूत्र आहे:
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
 
 ![Delegation Image 3](/img/Delegation-Reward-Formula.png)
 
 ### Considering the Indexer's delegation pool
 
-प्रतिनिधीने विचारात घेण्याची आणखी एक गोष्ट म्हणजे त्यांच्या मालकीचे प्रतिनिधी पूल किती आहे. डेलिगेटरने पूलमध्ये जमा केलेल्या रकमेद्वारे निर्धारित पूलच्या साध्या पुनर्संतुलनासह, सर्व प्रतिनिधी पुरस्कार समान रीतीने सामायिक केले जातात. हे डेलिगेटरला पूलचा वाटा देते:
+Delegators should consider the proportion of the Delegation Pool they own.
 
-![Share formula](/img/Share-Forumla.png)
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
 
 ### Considering the delegation capacity
 
-विचारात घेण्यासारखी दुसरी गोष्ट म्हणजे प्रतिनिधींची क्षमता. सध्या, डेलिगेशन रेशो 16 वर सेट केले आहे. याचा अर्थ असा की जर एखाद्या इंडेक्सरने 1,000,000 GRT स्टेक केले असेल, तर त्यांची डेलिगेशन क्षमता 16,000,000 GRT डेलिगेटेड टोकन्स आहे जी ते प्रोटोकॉलमध्ये वापरू शकतात. या रकमेवरील कोणतेही डेलिगेट केलेले टोकन सर्व डेलिगेटर रिवॉर्ड्स कमी करतील.
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### MetaMask "Pending Transaction" Bug
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### उदाहरण
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
 
-## Video guide for the network UI
+## Video Guide
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+This video guide reviews this page while interacting with the UI.
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From 372da45aaa4a2cf1b4338a06184be36f48be6e5f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:41 -0500
Subject: [PATCH 0751/1325] New translations delegating.mdx (Hindi)

---
 website/pages/hi/network/delegating.mdx | 99 +++++++++++++++++--------
 1 file changed, 68 insertions(+), 31 deletions(-)

diff --git a/website/pages/hi/network/delegating.mdx b/website/pages/hi/network/delegating.mdx
index a9785500c51a..09c0de82002b 100644
--- a/website/pages/hi/network/delegating.mdx
+++ b/website/pages/hi/network/delegating.mdx
@@ -2,13 +2,23 @@
 title: Delegating
 ---
 
-Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers. Delegators help secure the network without running a Graph Node themselves.
+Delegator नेटवर्क के प्रतिभागी होते हैं जो एक या अधिक इंडेक्सर्स को जीआरटी (GRT) का प्रतिनिधित्व (यानी, "स्टेक") करते हैं।
 
-Delegators earn a portion of an Indexer's query fees and rewards by delegating to them. The amount of queries an Indexer can process depends on their own stake, the delegated stake, and the price the Indexer charges for each query. Therefore, the more stake that is allocated to an Indexer, the more potential queries they can process.
+- वे बिना खुद Graph Node चलाए नेटवर्क को सुरक्षित रखने में मदद करते हैं।
+
+- वे इंडेक्सर को डेलीगेट करके उनकी क्वेरी फीस और पुरस्कार का एक हिस्सा कमाते हैं।
+
+## यह कैसे काम करता है?
+
+Indexers द्वारा संसाधित किए जाने वाले क्वेरी की संख्या उनके स्वयं के हिस्से, **delegated stake**, और प्रत्येक क्वेरी के लिए Indexers द्वारा ली जाने वाली कीमत पर निर्भर करती है। इसलिए, जितना अधिक stake किसी Indexer को आवंटित किया जाता है, उतनी ही अधिक संभावित क्वेरी एक Indexer संसाधित कर सकता है।
 
 ## प्रतिनिधि गाइड
 
-This guide will explain how to be an effective Delegator in the Graph Network. Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. A Delegator must use their best judgment to choose Indexers based on multiple factors. Please note this guide will not cover steps such as setting up Metamask properly, as that information is widely available on the internet.
+The Graph Network में एक प्रभावशाली Delegator बनने के लिए सीखें।
+
+Delegator अपने डेलीगेटेड स्टेक के आधार पर सभी Indexer के साथ प्रोटोकॉल की कमाई साझा करते हैं। इसलिए, उन्हें कई कारकों के आधार पर Indexer का चयन करने के लिए अपने सर्वोत्तम विवेक का उपयोग करना चाहिए।
+
+> कृपया ध्यान दें कि यह गाइड 'MetaMask' को सही ढंग से सेट करने जैसे स्टेप्स को कवर नहीं करता है। Ethereum समुदाय वॉलेट्स के बारे में एक व्यापक संसाधन निम्नलिखित लिंक के माध्यम से प्रदान करता है ([source](https://ethereum.org/en/wallets/))।
 
 There are three sections in this guide:
 
@@ -24,64 +34,86 @@ There are three sections in this guide:
 
 प्रतिनिधियों को खराब व्यवहार के लिए कम नहीं किया जा सकता है, लेकिन खराब निर्णय लेने को हतोत्साहित करने के लिए प्रतिनिधियों पर एक कर है जो नेटवर्क की अखंडता को नुकसान पहुंचा सकता है।
 
-It is important to understand that every time you delegate, you will be charged 0.5%. This means that if you are delegating 1000 GRT, you will automatically burn 5 GRT.
+एक Delegator के रूप में, निम्नलिखित बातों को समझना महत्वपूर्ण है:
 
-In order to be safe, a Delegator should calculate their potential return when delegating to an Indexer. For example, a Delegator might calculate how many days it will take before they have earned back the 0.5% tax on their delegation.
+- आपसे हर बार डेलीगेट करने पर 0.5% चार्ज किया जाएगा। इसका मतलब है कि यदि आप 1,000 GRT डेलीगेट करते हैं, तो आप स्वचालित रूप से 5 GRT बर्न कर देंगे।
+
+- सुरक्षित रहने के लिए, आपको Indexer को डेलीगेट करते समय अपने संभावित रिटर्न की गणना करनी चाहिए। उदाहरण के लिए, आप यह गणना कर सकते हैं कि आपके डेलीगेशन पर 0.5% कर वापस कमाने में कितने दिन लगेंगे।
 
 ### प्रतिनिधिमंडल बंधन अवधि
 
 Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
 
-Another thing to consider is how to choose an Indexer wisely. If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT.
+### यह क्यों महत्वपूर्ण है?
+
+यदि आप किसी ऐसे Indexer का चयन करते हैं जो विश्वसनीय नहीं है या अच्छा काम नहीं कर रहा है, तो आप डेलीगेट को रद्द करना चाहेंगे। इसका मतलब है कि आप पुरस्कार कमाने के कई अवसर खो देंगे, जो GRT को जलाने के समान बुरा हो सकता है। परिणामस्वरूप, यह अनुशंसा की जाती है कि आप एक Indexer का चयन समझदारी से करें।
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![डेलिगेशन अनबॉन्डिंग](/img/Delegation-Unbonding.png) _डेलीगेशन UI में 0.5% शुल्क और साथ ही 28 दिन पर ध्यान दें बंधन
-  अवधि._
+  ![डेलिगेशन अनबॉन्डिंग](/img/Delegation-Unbonding.png) _डेलीगेशन UI में 0.5% शुल्क और साथ ही 28 दिन पर ध्यान दें
+   बंधन अवधि._
 </div>
 
 ### डेलीगेटर्स के लिए उचित इनाम भुगतान के साथ एक भरोसेमंद इंडेक्सर चुनना
 
-This is an important aspect to understand. First, let's discuss three very important values, which are the Delegation Parameters.
+एक विश्वसनीय Indexer को चुनने के लिए आपको डेलीगेशन पैरामीटर्स को समझना आवश्यक है।
 
-Indexing Reward Cut - The indexing reward cut is the portion of the rewards that the Indexer will keep for themselves. This means that if an Indexer's rewards are set to 100%, as a Delegator you will get 0 indexing rewards. If you see it set at 80% in the UI, that means as a Delegator, you will receive 20%. An important note - at the beginning of the network, Indexing Rewards will account for the majority of the rewards.
+#### डेलीगेशन पैरामीटर
+
+- **इंडेक्सिंग पुरस्कार कट** - पुरस्कार का वह हिस्सा जो Indexer अपने लिए रखेंगे।
+  - यदि किसी Indexer का पुरस्कार कट 100% पर सेट है, तो एक Delegator के रूप में, आपको 0 इंडेक्सिंग पुरस्कार मिलेंगे।
+  - यदि इसे 80% पर सेट किया गया है, तो एक Delegator के रूप में, आप 20% प्राप्त करेंगे।
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *शीर्ष इंडेक्सर डेलीगेटर्स को पुरस्कारों का 90% दे रहा है। बीच
-  वाला प्रतिनिधि को 20% दे रहा है। नीचे वाला डेलिगेटरों को ~83% दे रहा है।*
+  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *शीर्ष इंडेक्सर डेलीगेटर्स को पुरस्कारों का 90% दे रहा है। 
+   बीच वाला प्रतिनिधि को 20% दे रहा है। नीचे वाला डेलिगेटरों को ~83% दे रहा है।*
 </div>
 
-- Query Fee Cut - This works exactly like the Indexing Reward Cut. However, this applies explicitly to returns on the query fees the Indexer collects. It should be noted that at the start of the network, returns from query fees will be very small compared to the indexing reward. It is recommended that you pay attention to the network to determine when the query fees in the network will start to be more significant.
+- **क्वेरी शुल्क कटौती** - यह बिल्कुल 'Indexing Reward Cut' जैसा है, लेकिन यह उन रिटर्न पर लागू होता है जो 'query fees' से प्राप्त होते हैं जो Indexers एकत्र करते हैं।
+
+यहाँ आप देख सकते हैं, सही Indexer चुनने के लिए, आपको कई चीजों पर विचार करना होगा।
 
-As you can see, in order to choose the right Indexer, you must consider multiple things. This is why we highly recommend exploring [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which reward Delegators consistently. Many of the Indexers are very active in Discord and will be happy to answer your questions. Many of them have been Indexing for months on the testnet, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+- यह अत्यधिक अनुशंसा की जाती है कि आप [The Graph Discord](https://discord.gg/graphprotocol) को एक्सप्लोर करें ताकि यह पता लगाया जा सके कि कौन से Indexers के पास सबसे अच्छे सामाजिक और तकनीकी प्रतिष्ठा हैं और कौन से 'Delegators' को लगातार इनाम देते हैं।
+- बहुत से Indexers डिस्कॉर्ड में बहुत सक्रिय हैं और आपकी पूछताछ का जवाब देने में खुश होंगे।
+- उनमें से कई महीनों से इंडेक्सिंग कर रहे हैं, और वे Delegators को अच्छा लाभ कमाने में मदद करने के लिए अपना सर्वश्रेष्ठ कर रहे हैं, क्योंकि इससे नेटवर्क की स्वास्थ्य और सफलता में सुधार होता है।
 
-### डेलीगेटर्स की अपेक्षित वापसी की गणना
+## यहाँ पर 'Delegators' की अपेक्षित लाभ की गणना की जा रही है।
 
-A Delegator must consider a lot of factors when determining the return. These include:
+एक Delegator को एक वापसी निर्धारित करने के लिए निम्नलिखित कारकों पर विचार करना चाहिए:
 
-- एक तकनीकी डेलीगेटर इंडेक्सर की उनके लिए उपलब्ध प्रत्यायोजित टोकन का उपयोग करने की क्षमता को भी देख सकता है। यदि कोई इंडेक्सर उपलब्ध सभी टोकन आवंटित नहीं कर रहा है, तो वे स्वयं या उनके प्रतिनिधियों के लिए अधिकतम लाभ अर्जित नहीं कर रहे हैं।
-- Right now, in the network an Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. So, it is possible that an Indexer might have a lot of rewards they still need to collect, and thus, their total rewards are low. This should be taken into consideration in the early days.
+- एक Indexer की यह क्षमता है कि वह अपने पास उपलब्ध Delegated टोकन का उपयोग कर सके।
+  - यदि एक Indexer सभी उपलब्ध टोकन आवंटित नहीं कर रहा है, तो वे अपने लिए या अपने Delegators के लिए अधिकतम लाभ अर्जित नहीं कर रहे हैं।
+- पहले कुछ दिनों में डेलिगेटिंग पर ध्यान दें।
+  - एक Indexer किसी भी समय 1 से 28 दिनों के बीच एक आवंटन बंद करने और पुरस्कार एकत्र करने का विकल्प चुन सकता है। यह संभव है कि एक Indexer के पास अभी भी बहुत सारे पुरस्कार हों जिन्हें उन्हें एकत्र करना है, इसलिए उनके कुल पुरस्कार कम हो सकते हैं।
 
 ### प्रश्न शुल्क में कटौती और अनुक्रमण शुल्क में कटौती को ध्यान में रखते हुए
 
-जैसा कि ऊपर दिए गए अनुभागों में बताया गया है, आपको एक ऐसा इंडेक्सर चुनना चाहिए जो पारदर्शी हो और उनके प्रश्न शुल्क कट और इंडेक्सिंग शुल्क कटौती को सेट करने के बारे में ईमानदार हो। प्रतिनिधि को यह देखने के लिए कि उनके पास कितना समय बफर है, पैरामीटर्स कूलडाउन समय को भी देखना चाहिए। उसके बाद, प्रतिनिधियों को मिलने वाले पुरस्कारों की मात्रा की गणना करना काफी सरल है। सूत्र है:
+आपको एक ऐसा Indexer चुनना चाहिए जो अपनी क्वेरी शुल्क और इंडेक्सिंग शुल्क कटौती को निर्धारित करने में पारदर्शी और ईमानदार हो। इसके बाद, आप पैरामीटर्स कूलडाउन समय को देखना चाहिए कि आपके पास कितना समय बफर है। इसके बाद, अपने प्राप्त पुरस्कारों की गणना करना सरल है।
+
+सूत्र है:
 
 ![प्रतिनिधिमंडल छवि 3](/img/Delegation-Reward-Formula.png)
 
 ### अनुक्रमणिका के प्रतिनिधिमंडल पूल को ध्यान में रखते हुए
 
-एक अन्य बात पर एक प्रतिनिधि को विचार करना होता है कि वह प्रतिनिधिमंडल पूल का कितना अनुपात रखता है। सभी प्रतिनिधि पुरस्कारों को समान रूप से साझा किया जाता है, पूल के एक साधारण पुनर्संतुलन के साथ, प्रतिनिधि द्वारा पूल में जमा की गई राशि द्वारा निर्धारित किया जाता है। यह प्रतिनिधि को पूल का एक हिस्सा देता है:
+Delegators को प्रतिनिधि पूल में उनके स्वामित्व के अनुपात पर विचार करना चाहिए।
 
-![साझा सूत्र](/img/Share-Forumla.png)
+सभी 'प्रतिनिधि पुरस्कार' समान रूप से साझा किए जाते हैं, और पूल में पुनर्संतुलन उस राशि के आधार पर होता है जो Delegator ने पूल में जमा की होती है।
 
-Using this formula, we can see that it is possible for an Indexer offering only 20% to Delegators to actually provide a better reward than an Indexer giving 90%.
+यह Delegator को पूल का हिस्सा देता है:
+
+![साझा सूत्र](/img/Share-Forumla.png)
 
-Therefore, a Delegator can do the math to determine that the Indexer offering 20% to Delegators is offering a better return.
+> उपरोक्त सूत्र यह दर्शाता है कि एक Indexer जो केवल 20% को Delegators को प्रदान कर रहा है, एक Indexer की तुलना में बेहतर पुरस्कार प्रदान कर सकता है जो 90% दे रहा है। बस गणना करें ताकि सर्वश्रेष्ठ पुरस्कार निर्धारित हो सके।
 
 ### प्रतिनिधिमंडल की क्षमता को ध्यान में रखते हुए
 
-एक और बात पर विचार करना प्रतिनिधिमंडल की क्षमता है। वर्तमान में, प्रत्यायोजन अनुपात 16 पर सेट है। इसका अर्थ है कि यदि किसी अनुक्रमणिका ने 1,000,000 GRT दांव पर लगा दिया है, तो उनकी प्रत्यायोजन क्षमता प्रत्यायोजित टोकन की 16,000,000 GRT है जिसे वे प्रोटोकॉल में उपयोग कर सकते हैं। इस राशि से अधिक का कोई भी प्रत्यायोजित टोकन सभी प्रतिनिधि पुरस्कारों को कम कर देगा।
+अंत में, प्राधिकरण क्षमता पर विचार करें। वर्तमान में, प्राधिकरण अनुपात 16 पर सेट है।
 
-Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, all the Delegators and the Indexer, are earning way less rewards than they could be.
+#### यह क्यों मायने रखता है?
+
+यह मतलब है कि यदि एक Indexer ने 1,000,000 GRT स्टेक किया है, तो उनकी Delegation Capacity 16,000,000 GRT के अधिग्रहित टोकनों की है जिसका वे प्रोटोकॉल में उपयोग कर सकते हैं। इस मात्रा से अधिक कोई भी अधिग्रहित टोकन सभी Delegator पुरस्कारों को पतला कर देगा।
+
+एक Indexer के पास 100,000,000 GRT उनके लिए नामांकित हैं, लेकिन उनकी क्षमता केवल 16,000,000 GRT है। इसका मतलब है कि प्रभावी रूप से, 84,000,000 GRT टोकन उपयोग में नहीं हैं जिससे टोकन कमाई नहीं हो रही है। इसलिए, दोनों Delegators और Indexers उन पुरस्कारों को कम कमा रहे हैं जो वे कमा सकते थे।
 
 Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
 
@@ -89,16 +121,21 @@ Therefore, a Delegator should always consider the Delegation Capacity of an Inde
 
 ### मेटामास्क "लंबित लेन-देन" बग
 
-**When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?**
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+MetaMask के माध्यम से Indexers को प्रतिनिधित्व देने के प्रयास कभी-कभी विफल हो सकते हैं और इसके परिणामस्वरूप "Pending" या "Queued" लेनदेन के प्रयासों के लिए लंबे समय तक रुकावट हो सकती है।
+
+#### उदाहरण
 
-At times, attempts to delegate to indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+अगर आप वर्तमान कीमतों के सापेक्ष अपर्याप्त गैस शुल्क के साथ डेलीगेट करने का प्रयास करते हैं।
 
-For example, a user may attempt to delegate with an insufficient gas fee relative to the current prices, resulting in the transaction attempt displaying as "Pending" in their MetaMask wallet for 15+ minutes. When this occurs, a user can attempt subsequent transactions, but these will only be processed until the initial transaction is mined, as transactions for an address must be processed in order. In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+- यह क्रिया आपके MetaMask वॉलेट में लेनदेन के प्रयास को "Pending" के रूप में 15+ मिनट तक प्रदर्शित कर सकती है। जब ऐसा होता है, तो आप बाद के लेनदेन करने का प्रयास कर सकते हैं, लेकिन ये केवल तब तक संसाधित होंगे जब तक प्रारंभिक लेनदेन खनन नहीं किया गया है, क्योंकि किसी पते के लिए लेनदेन को क्रम में संसाधित करना आवश्यक है।
+- इस प्रकार के मामलों में, इन लेनदेन को MetaMask में रद्द किया जा सकता है, लेकिन लेनदेन के प्रयास गैस शुल्क को जमा करेंगे बिना यह गारंटी कि बाद के प्रयास सफल होंगे।
 
-A simpler resolution to this bug is restarting the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+इस बग का एक सरल समाधान ब्राउज़र को पुनः प्रारंभ करना है (उदाहरण के लिए, पता बार में "abort " का उपयोग करना), जो सभी पिछले प्रयासों को रद्द कर देगा बिना गैस को वॉलेट से घटाए। कई उपयोगकर्ताओं ने जिन्होंने इस समस्या का सामना किया है, उन्होंने अपने ब्राउज़र को पुनः प्रारंभ करने और 'delegation' करने का प्रयास करने के बाद सफल लेनदेन की रिपोर्ट की है।
 
-## नेटवर्क यूआई के लिए वीडियो गाइड
+## वीडियो गाइड
 
-This video guide fully reviews this document and explains how to consider everything in it while interacting with the UI.
+इस वीडियो गाइड इस पृष्ठ की समीक्षा करता है जबकि UI के साथ बातचीत करता है।
 
 <VideoEmbed youtube="2G7S2gdURdc" />

From fc483697b410704e3afd602ed9a70a455ca928cc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:42 -0500
Subject: [PATCH 0752/1325] New translations delegating.mdx (Swahili)

---
 website/pages/sw/network/delegating.mdx | 141 ++++++++++++++++++++++++
 1 file changed, 141 insertions(+)
 create mode 100644 website/pages/sw/network/delegating.mdx

diff --git a/website/pages/sw/network/delegating.mdx b/website/pages/sw/network/delegating.mdx
new file mode 100644
index 000000000000..eda60369e00a
--- /dev/null
+++ b/website/pages/sw/network/delegating.mdx
@@ -0,0 +1,141 @@
+---
+title: Delegating
+---
+
+Delegators are network participants who delegate (i.e., "stake") GRT to one or more Indexers.
+
+- They help secure the network without running a Graph Node themselves.
+
+- They earn a portion of an Indexer's query fees and rewards by delegating to them.
+
+## How does this work?
+
+The number of queries an Indexer can process depends on their own stake, **the delegated stake**, and the price the Indexer charges for each query. Therefore, the more stake allocated to an Indexer, the more potential queries an Indexer can process.
+
+## Delegator Guide
+
+Learn how to be an effective Delegator in The Graph Network.
+
+Delegators share the earnings of the protocol alongside all Indexers based on their delegated stake. Therefore, they must use their best judgment to choose Indexers based on multiple factors.
+
+> Please note this guide does not cover steps such as setting up MetaMask properly. The Ethereum community provides a comprehensive resource regarding wallets through the following link ([source](https://ethereum.org/en/wallets/)).
+
+There are three sections in this guide:
+
+- The risks of delegating tokens in The Graph Network
+- How to calculate expected returns as a Delegator
+- A video guide showing the steps to delegate in the Graph Network UI
+
+## Delegation Risks
+
+Listed below are the main risks of being a Delegator in the protocol.
+
+### The delegation tax
+
+Delegators cannot be slashed for bad behavior, but there is a tax on Delegators to disincentivize poor decision-making that could harm the integrity of the network.
+
+As a Delegator, it's important to understand the following:
+
+- You will be charged 0.5% every time you delegate. This means that if you delegate 1,000 GRT, you will automatically burn 5 GRT.
+
+- In order to be safe, you should calculate your potential return when delegating to an Indexer. For example, you might calculate how many days it will take before you have earned back the 0.5% tax on your delegation.
+
+### The delegation unbonding period
+
+Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day unbonding period. This means they cannot transfer their tokens or earn any rewards for 28 days.
+
+### Why is this important?
+
+If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
+
+<div sx={{ mx: 'auto', maxWidth: '400px' }}>
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Note the 0.5% fee in the Delegation UI, as well as the 28 day
+  unbonding period._
+</div>
+
+### Choosing a trustworthy Indexer with a fair reward payout for Delegators
+
+In order to understand how to choose a trustworthy Indexer, you need to understand the Delegation Parameters.
+
+#### Delegation Parameters
+
+- **Indexing Reward Cut** - The portion of the rewards the Indexer will keep for themselves.
+  - If an Indexer's reward cut is set to 100%, as a Delegator, you will get 0 indexing rewards.
+  - If it is set to 80%, as a Delegator, you will receive 20%.
+
+<div sx={{ mx: 'auto', maxWidth: '700px' }}>
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *The top Indexer is giving Delegators 90% of the rewards. The
+  middle one is giving Delegators 20%. The bottom one is giving Delegators ~83%.*
+</div>
+
+- **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
+
+As you can see, in order to choose the right Indexer, you must consider multiple things.
+
+- It is highly recommend that you explore [The Graph Discord](https://discord.gg/graphprotocol) to determine which Indexers have the best social and technical reputations and which ones reward Delegators consistently.
+- Many Indexers are very active in Discord and will be happy to answer your questions.
+- Many of them have been Indexing for months, and they are doing their best to help Delegators earn a good return, as it improves the health and success of the network.
+
+## Calculating Delegators Expected Return
+
+A Delegator must consider the following factors to determine a return:
+
+- Consider an Indexer's ability to use the Delegated tokens available to them.
+  - If an Indexer is not allocating all the tokens available, they are not earning the maximum profit they could be for themselves or their Delegators.
+- Pay attention to the first few days of delegating.
+  - An Indexer can choose to close an allocation and collect rewards anytime between 1 and 28 days. It is possible that an Indexer might have a lot of rewards they still need to collect, so their total rewards are low.
+
+### Considering the query fee cut and indexing fee cut
+
+You should choose an Indexer that is transparent and honest about setting their Query Fee and Indexing Fee Cuts. You should also look at the Parameters Cooldown time to see how much of a time buffer you have. After that is done, it is simple to calculate the amount of rewards you are getting.
+
+The formula is:
+
+![Delegation Image 3](/img/Delegation-Reward-Formula.png)
+
+### Considering the Indexer's delegation pool
+
+Delegators should consider the proportion of the Delegation Pool they own.
+
+All delegation rewards are shared evenly, with a pool rebalancing based on the amount the Delegator deposited into the pool.
+
+This gives the Delegator a share of the pool:
+
+![Share formula](/img/Share-Forumla.png)
+
+> The formula above shows that it is possible for an Indexer offering only 20% to Delegators to provide a better reward than an Indexer giving 90%. Simply do the math to determine the best reward.
+
+### Considering the delegation capacity
+
+Finally, consider the delegation capacity. Currently, the Delegation Ratio is set to 16.
+
+#### Why does this matter?
+
+This means that if an Indexer has staked 1,000,000 GRT, their Delegation Capacity is 16,000,000 GRT of delegated tokens that they can use in the protocol. Any delegated tokens over this amount will dilute all the Delegator rewards.
+
+Imagine an Indexer with 100,000,000 GRT delegated to them, but their capacity is only 16,000,000 GRT. This means effectively, 84,000,000 GRT tokens are not being used to earn tokens. So, both the Delegators and the Indexers are earning less rewards than they could be.
+
+Therefore, a Delegator should always consider the Delegation Capacity of an Indexer, and factor it into their decision making.
+
+## Delegator FAQs and Bugs
+
+### MetaMask "Pending Transaction" Bug
+
+1. When I try to delegate my transaction in MetaMask, it appears as "Pending" or "Queued" for longer than expected. What should I do?
+
+At times, attempts to delegate to Indexers via MetaMask can fail and result in prolonged periods of "Pending" or "Queued" transaction attempts.
+
+#### Example
+
+Let's say you attempt to delegate with an insufficient gas fee relative to the current prices.
+
+- This action can cause the transaction attempt to display as "Pending" in your MetaMask wallet for 15+ minutes. When this happens, you can attempt subsequent transactions, but these will only be processed until the initial transaction is mined because transactions for an address must be processed in order.
+- In such cases, these transactions can be cancelled in MetaMask, but the transactions attempts will accrue gas fees without any guarantee that subsequent attempts will be successful.
+
+A simple resolution to this bug is to restart the browser (e.g., using "abort:restart" in the address bar), which will cancel all previous attempts without gas being subtracted from the wallet. Several users who have encountered this issue have reported successful transactions after restarting their browser and attempting to delegate.
+
+## Video Guide
+
+This video guide reviews this page while interacting with the UI.
+
+<VideoEmbed youtube="2G7S2gdURdc" />

From 6aa0d7e361a3710a9db2fbb22d1610756fe116b8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:44 -0500
Subject: [PATCH 0753/1325] New translations explorer.mdx (Romanian)

---
 website/pages/ro/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/ro/network/explorer.mdx b/website/pages/ro/network/explorer.mdx
index bca2993eb0b3..02dca6ed2f9f 100644
--- a/website/pages/ro/network/explorer.mdx
+++ b/website/pages/ro/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-When you click into a subgraph, you’ll be able to test queries in the playground and be able to leverage network details to make informed decisions. You’ll also be able 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, which means that it’ll surface on the network to eventually serve queries.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-On each subgraph’s dedicated page, several details are surfaced. These include:
+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
@@ -31,26 +45,32 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ## Participants
 
-Within this tab, you’ll get a bird’s eye view of all the people that are participating in the network activities, such as Indexers, Delegators, and Curators. Below, we’ll go into an in-depth review of what each tab means for you.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Let’s start with the Indexers. Indexers are the backbone of the protocol, being the ones that stake on subgraphs, index them, and serve queries to anyone consuming subgraphs. In the Indexers table, you’ll be able to see an Indexers’ delegation parameters, their stake, how much they have staked to each subgraph, and how much revenue they have made off of query fees and indexing rewards. Deep dives below:
+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.
 
-- 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
+**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
+- 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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 2. Curators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve. By depositing GRT, Curators mint curation shares of a subgraph. As a result, Curators are eligible to earn a portion of the query fees that the subgraph they have signaled on generates. The bonding curve incentivizes Curators to curate the highest quality data sources. The Curator table in this section will allow you to see:
+In the The Curator table listed below you can see:
 
 - The date the Curator started curating
 - The number of GRT that was deposited
@@ -68,34 +92,36 @@ Curators can be community members, data consumers, or even subgraph developers w
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. 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. Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers seek to attract Delegators by offering them a portion of the indexing rewards and query fees that they earn.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-The Delegators table will allow you to see the active Delegators in the community, as well as metrics such as:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - The number of Indexers a Delegator is delegating towards
 - A Delegator’s original delegation
 - The rewards they have accumulated but have not withdrawn from the protocol
 - The realized rewards they withdrew from the protocol
 - Total amount of GRT they have currently in the protocol
-- The date they last delegated at
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-In the Network section, you will see global KPIs as well as 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.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - The current total network stake
 - The stake split between the Indexers and their Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocol parameters such as curation reward, inflation rate, and more
 - Current epoch rewards and fees
 
-A few key details that are worth mentioning:
+A few key details to note:
 
-- **Query fees represent the fees generated by the consumers**, and 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 the Indexers close their allocations towards the subgraphs they’ve been indexing. Thus the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days).
+- **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)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - The active epoch is the one in which Indexers are currently allocating stake and collecting query fees
   - The settling epochs are the ones in which the state channels are being settled. This means that the Indexers are subject to slashing if the consumers open disputes against them.
   - 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, thus being finalized.
+  - 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)
 
 ## Your User Profile
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### Profile Overview
 
-This is where you can see any current actions you took. This is also where you can find your profile information, description, and website (if you added one).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Subgraphs Tab
 
-If you click into the Subgraphs tab, you’ll see 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.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Indexing Tab
 
-If you click into the Indexing tab, you’ll find a table with all the active and historical allocations towards the subgraphs, as well as charts that you can analyze and see your past performance as an Indexer.
+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.
 
 This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics:
 
@@ -158,7 +189,9 @@ This section will also include details about your net Indexer rewards and net qu
 
 ### Delegating Tab
 
-Delegators are important to the Graph Network. A Delegator must use their knowledge to choose an Indexer that will provide a healthy return on rewards. Here you can find details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards.
+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.
 
 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.
 

From ff780b93e943a7fd89e832dc248d9b4d20120137 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:45 -0500
Subject: [PATCH 0754/1325] New translations explorer.mdx (Spanish)

---
 website/pages/es/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/es/network/explorer.mdx b/website/pages/es/network/explorer.mdx
index b2f43cebf2a2..7f8dee22a2e7 100644
--- a/website/pages/es/network/explorer.mdx
+++ b/website/pages/es/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Explorador de Graph
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgrafos
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-Cuando hagas clic en un subgrafo, podrás probar consultas en el playground y podrás aprovechar los detalles de la red para tomar decisiones informadas. También podrás señalar GRT en tu propio subgrafo o en los subgrafos de otros para que los indexadores sean conscientes de su importancia y calidad. Esto es fundamental porque señalar en un subgrafo incentiva su indexación, lo que significa que saldrá a la luz en la red para eventualmente entregar consultas.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Imagen de Explorer 2](/img/Subgraph-Details.png)
 
-En la página de cada subgrafo, aparecen varios detalles. Entre ellos se incluyen:
+On each subgraph’s dedicated page, you can do the following:
 
 - Señalar/dejar de señalar un subgrafo
 - Ver más detalles como gráficos, ID de implementación actual y otros metadatos
@@ -31,26 +45,32 @@ En la página de cada subgrafo, aparecen varios detalles. Entre ellos se incluye
 
 ## Participantes
 
-Dentro de esta pestaña, tendras una mirada general de todas las personas que están participando en las actividades de la red, como los Indexadores, los Delegadores y los Curadores. A continuación, revisaremos en profundidad lo que significa cada pestaña para ti.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexadores
 
 ![Imagen de Explorer 4](/img/Indexer-Pane.png)
 
-Comencemos con los Indexadores. Los Indexadores son la columna vertebral del protocolo, ya que son los que stakean en los subgrafos, los indexan y proveen consultas a cualquiera que consuma subgrafos. En la tabla de Indexadores, podrás ver los parámetros de delegación de un Indexador, su participación, cuánto han stakeado en cada subgrafo y cuántos ingresos han obtenido por las tarifas de consulta y las recompensas de indexación. Profundizaremos un poco más a continuación:
+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.
 
-- Query Fee Cut: es el porcentaje de los reembolsos obtenidos por la tarifa de consulta que el Indexador conserva cuando se divide con los Delegadores
-- Effective Reward Cut: es el recorte de recompensas por indexación que se aplica al pool de delegación. Si es negativo, significa que el Indexador está regalando parte de sus beneficios. Si es positivo, significa que el Indexador se queda con alguno de tus beneficios
-- Cooldown Remaining: el tiempo restante que le permitirá al Indexador cambiar los parámetros de delegación. Los plazos de configuración son ajustados por los Indexadores cuando ellos actualizan sus parámetros de delegación
-- Owned: esta es la participación (o el stake) depositado por el Indexador, la cual puede reducirse por su mal comportamiento
-- Delegated: participación de los Delegadores que puede ser asignada por el Indexador, pero que no se puede recortar
-- Allocated: es el stake que los indexadores están asignando activamente a los subgrafos que están indexando
-- Available Delegation Capacity: la cantidad de participación delegada que los Indexadores aún pueden recibir antes de que se sobredeleguen
+**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: estas son las tarifas totales que los usuarios (clientes) han pagado por todas las consultas de un Indexador
+- 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.
 
-Los Indexadores pueden ganar tanto comisiones de consulta como recompensas de indexación. Funcionalmente, esto ocurre cuando los participantes de la red delegan GRT a un Indexador. Esto permite a los Indexadores recibir tarifas de consulta y recompensas en función de sus parámetros de indexación. Los parámetros de indexación se establecen haciendo clic en la parte derecha de la tabla, o entrando en el perfil de un Indexador y haciendo clic en el botón "Delegar".
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Para obtener más información sobre cómo convertirte en un Indexador, puedes consultar la [documentación oficial](/network/indexing) o [The Graph Academy Indexer Guides.](https://thegraph.academy/delegators/ eligiendo-indexadores/)
 
@@ -58,9 +78,13 @@ Para obtener más información sobre cómo convertirte en un Indexador, puedes c
 
 ### 2. Curadores
 
-Los Curadores analizan los subgrafos para identificar cuáles son los de mayor calidad. Una vez que un Curador ha encontrado un subgrafo potencialmente atractivo, puede curarlo señalando su bonding curve. De este modo, los Curadores hacen saber a los Indexadores qué subgrafos son de alta calidad y deben ser indexados.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Los Curadores pueden ser miembros de la comunidad, consumidores de datos o incluso developers de subgrafos que señalan en sus propios subgrafos depositando tokens GRT en una bonding curve. Al depositar GRT, los Curadores anclan sus participaciones como curadores de un subgrafo. Como resultado, los Curadores son elegibles para ganar una parte de las tarifas de consulta que genera el subgrafo que han señalado. La bonding curve incentiva a los Curadores a curar fuentes de datos de la más alta calidad. La tabla de Curador en esta sección te permitirá ver:
+In the The Curator table listed below you can see:
 
 - La fecha en que el Curador comenzó a curar
 - El número de GRT que se depositaron
@@ -68,34 +92,36 @@ Los Curadores pueden ser miembros de la comunidad, consumidores de datos o inclu
 
 ![Imagen de Explorer 6](/img/Curation-Overview.png)
 
-Si deseas obtener más información sobre el rol de Curador, puedes hacerlo visitando los siguientes enlaces de [The Graph Academy](https://thegraph.academy/curators/) o [documentación oficial.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegadores
 
-Los Delegadores juegan un rol esencial en la seguridad y descentralización que conforman la red de The Graph. Participan en la red delegando (es decir, "stakeado") tokens GRT a uno o varios Indexadores. Sin Delegadores, es menos probable que los Indexadores obtengan recompensas y tarifas significativas. Por lo tanto, los Indexadores buscan atraer Delegadores ofreciéndoles una parte de las recompensas de indexación y las tarifas de consulta que ganan.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![Imagen de Explorer 7](/img/Delegation-Overview.png)
 
-La tabla de Delegadores te permitirá ver los Delegadores activos en la comunidad, así como las siguientes métricas:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - El número de Indexadores a los que delega este Delegador
 - La delegación principal de un Delegador
 - Las recompensas que han ido acumulando, pero que aún no han retirado del protocolo
 - Las recompensas realizadas, es decir, las que ya retiraron del protocolo
 - Cantidad total de GRT que tienen actualmente dentro del protocolo
-- La fecha en la que delegaron por última vez
+- The date they last delegated
 
-Si deseas obtener más información sobre cómo convertirte en Delegador, ¡no busques más! Todo lo que tienes que hacer es dirigirte a la [documentación oficial](/network/delegating) o [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Red
 
-En la sección red, verás los KPI globales, así como la capacidad de cambiar a una base por ciclo y analizar las métricas de la red con más detalle. Estos detalles te darán una idea de cómo se está desempeñando la red a lo largo del tiempo.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - La cantidad total de stake que circula en estos momentos
 - La participación que se divide entre los Indexadores y sus Delegadores
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Parámetros del protocolo como las recompensas de curación, tasa de inflación y más
 - Recompensas y tarifas del ciclo actual
 
-Algunos detalles clave que vale la pena mencionar:
+A few key details to note:
 
-- **Las tarifas de consulta representan las tarifas generadas por los consumidores**, y que pueden ser reclamadas (o no) por los Indexadores después de un período de al menos 7 ciclos (ver más abajo) después de que se han cerrado las asignaciones hacia los subgrafos y los datos que servían han sido validados por los consumidores.
-- **Las recompensas de indexación representan la cantidad de recompensas que los Indexadores reclamaron por la emisión de la red durante el ciclo.** Aunque la emisión del protocolo es fija, las recompensas solo se anclan una vez que los Indexadores cierran sus asignaciones hacia los subgrafos que han indexado. Por lo tanto, el número de recompensas por ciclo suele variar (es decir, durante algunos ciclos, es posible que los Indexadores hayan cerrado colectivamente asignaciones que han estado abiertas durante muchos días).
+- **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).
 
 ![Imagen de Explorer 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ En la sección de Epochs, puedes analizar, por cada epoch, métricas como:
   - El ciclo activo es aquel en la que los indexadores actualmente asignan su participación (staking) y cobran tarifas por consultas
   - Los ciclos liquidados son aquellos en los que ya se han liquidado las recompensas y demás métricas. Esto significa que los Indexadores están sujetos a recortes si los consumidores abren disputas en su contra.
   - 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.
-  - Los ciclos finalizados son los ciclos que no tienen reembolsos en cuanto a las tarifas de consulta, estos son reclamados por parte de los Indexadores, por lo que estos se consideran como finalizados.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Imagen de Explorer 9](/img/Epoch-Stats.png)
 
 ## Tu perfil de usuario
 
-Ahora que hemos hablado de las estadísticas de la red, pasemos a tu perfil personal. Tu perfil personal es el lugar donde puedes ver tu actividad personal dentro de la red, sin importar cómo estés participando en la red. Tu crypto wallet actuará como tu perfil de usuario, y desde tu dashboard podrás ver lo siguiente:
+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:
 
 ### Información general del perfil
 
-Aquí es donde puedes ver las acciones actuales que realizaste. Aquí también podrás encontrar la información de tu perfil, la descripción y el sitio web (si agregaste uno).
+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).
 
 ![Imagen de Explorer 10](/img/Profile-Overview.png)
 
 ### Pestaña de subgrafos
 
-Si haces clic en la pestaña subgrafos, verás tus subgrafos publicados. Esto no incluirá ningún subgrafo implementado con la modalidad de CLI o con fines de prueba; los subgrafos solo aparecerán cuando se publiquen en la red descentralizada.
+In the Subgraphs tab, you’ll see 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.
 
 ![Imagen de Explorer 11](/img/Subgraphs-Overview.png)
 
 ### Pestaña de indexación
 
-Si haces clic en la pestaña Indexación, encontrarás una tabla con todas las asignaciones activas e históricas hacia los subgrafos, así como gráficos que puedes analizar y ver tu desempeño anterior como Indexador.
+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.
 
 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:
 
@@ -158,7 +189,9 @@ Esta sección también incluirá detalles sobre las recompensas netas que obtien
 
 ### Pestaña de delegación
 
-Los Delegadores son importantes para la red de The Graph. Un Delegador debe usar su conocimiento para elegir un Indexador que le proporcionará un retorno saludable y sostenible. Aquí puedes encontrar detalles de tus delegaciones activas e históricas, junto con las métricas de los Indexadores a los que delegaste en el pasado.
+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.
 
 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.
 

From 05bbc5f913dabb4b348498a5e9892e42d86080c5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:46 -0500
Subject: [PATCH 0755/1325] New translations explorer.mdx (Arabic)

---
 website/pages/ar/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/ar/network/explorer.mdx b/website/pages/ar/network/explorer.mdx
index 4c82281ebc72..2024b24bcd1c 100644
--- a/website/pages/ar/network/explorer.mdx
+++ b/website/pages/ar/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![صورة المستكشف 1](/img/Subgraphs-Explorer-Landing.png)
 
-عند النقر على Subgraphs ، يمكنك اختبار الاستعلامات وستكون قادرا على الاستفادة من تفاصيل الشبكة لاتخاذ قرارات صائبة. سيمكنك ايضا من الإشارة إلى GRT على Subgraphs الخاص بك أو subgraphs الآخرين لجعل المفهرسين على علم بأهميته وجودته. هذا أمر مهم جدا وذلك لأن الإشارة ل Subgraphs تساعد المفهرسين في اختيار ذلك ال Subgraph لفهرسته ، مما يعني أنه سيظهر على الشبكة لتقديم الاستعلامات.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![صورة المستكشف 2](/img/Subgraph-Details.png)
 
-في كل صفحة مخصصة ل subgraphs ، تظهر العديد من التفاصيل. وهذا يتضمن
+On each subgraph’s dedicated page, you can do the following:
 
 - أشر/الغي الإشارة على Subgraphs
 - اعرض المزيد من التفاصيل مثل المخططات و ال ID الحالي وبيانات التعريف الأخرى
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## المشاركون
 
-Within this tab, you’ll get a bird’s eye view of all the people that are participating in the network activities, such as Indexers, Delegators, and Curators. Below, we’ll go into an in-depth review of what each tab means for you.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![صورة المستكشف 4](/img/Indexer-Pane.png)
 
-Let’s start with the Indexers. Indexers are the backbone of the protocol, being the ones that stake on subgraphs, index them, and serve queries to anyone consuming subgraphs. In the Indexers table, you’ll be able to see an Indexers’ delegation parameters, their stake, how much they have staked to each subgraph, and how much revenue they have made off of query fees and indexing rewards. Deep dives below:
+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.
 
-- اقتطاع رسوم الاستعلام Query Fee Cut - هي النسبة المئوية لخصم رسوم الاستعلام والتي يحتفظ بها المفهرس عند التقسيم مع المفوضين Delegators
-- اقتطاع المكافأة الفعالة Effective Reward Cut - هو اقتطاع مكافأة الفهرسة indexing reward cut المطبقة على مجموعة التفويضات. إذا كانت سالبة ، فهذا يعني أن المفهرس يتنازل عن جزء من مكافآته. إذا كانت موجبة، فهذا يعني أن المفهرس يحتفظ ببعض مكافآته
-- فترة التهدئة Cooldown المتبقية - هو الوقت المتبقي حتى يتمكن المفهرس من تغيير بارامترات التفويض. يتم إعداد فترات التهدئة من قبل المفهرسين عندما يقومون بتحديث بارامترات التفويض الخاصة بهم
-- مملوكة Owned - هذه هي حصة المفهرس المودعة ، والتي قد يتم شطبها بسبب السلوك الضار أو غير الصحيح
-- مفوضة Delegated - هي حصة مفوضة من قبل المفوضين والتي يمكن تخصيصها بواسطة المفهرس ، لكن لا يمكن شطبها
-- مخصصة Allocated - حصة يقوم المفهرسون بتخصيصها بشكل نشط نحو subgraphs التي يقومون بفهرستها
-- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated
+**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 - هذا هو إجمالي الرسوم التي دفعها المستخدمون للاستعلامات التي يقدمها المفهرس طوال الوقت
+- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time.
 - مكافآت المفهرس Indexer Rewards - هو مجموع مكافآت المفهرس التي حصل عليها المفهرس ومفوضيهم Delegators. تدفع مكافآت المفهرس ب GRT.
 
-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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 3. المفوضون Delegators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-يمكن للمنسقين أن يكونوا من أعضاء المجتمع أو من مستخدمي البيانات أو حتى من مطوري ال subgraph والذين يشيرون إلى ال subgraphs الخاصة بهم وذلك عن طريق إيداع توكن GRT في منحنى الترابط. وبإيداع GRT ، يقوم المنسقون بصك أسهم التنسيق في ال subgraph. نتيجة لذلك ، يكون المنسقون مؤهلين لكسب جزء من رسوم الاستعلام التي يُنشئها ال subgraph المشار إليها. يساعد منحنى الترابط المنسقين على تنسيق مصادر البيانات الأعلى جودة. جدول المنسق في هذا القسم سيسمح لك برؤية:
+In the The Curator table listed below you can see:
 
 - التاريخ الذي بدأ فيه المنسق بالتنسق
 - عدد ال GRT الذي تم إيداعه
@@ -68,34 +92,36 @@ Curators analyze subgraphs to identify which subgraphs are of the highest qualit
 
 ![صورة المستكشف 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. المفوضون Delegators
 
-يلعب المفوضون دورا رئيسيا في الحفاظ على الأمن واللامركزية في شبكة The Graph. يشاركون في الشبكة عن طريق تفويض (أي ، "Staking") توكن GRT إلى مفهرس واحد أو أكثر. بدون المفوضين، من غير المحتمل أن يربح المفهرسون مكافآت ورسوم مجزية. لذلك ، يسعى المفهرسون إلى جذب المفوضين من خلال منحهم جزءا من مكافآت الفهرسة ورسوم الاستعلام التي يكسبونها.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![صورة المستكشف 7](/img/Delegation-Overview.png)
 
-جدول المفوضين سيسمح لك برؤية المفوضين النشطين في المجتمع ، بالإضافة إلى مقاييس مثل:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - عدد المفهرسين المفوض إليهم
 - التفويض الأصلي للمفوض Delegator’s original delegation
 - المكافآت التي جمعوها والتي لم يسحبوها من البروتوكول
 - المكافآت التي تم سحبها من البروتوكول
 - كمية ال GRT التي يمتلكونها حاليا في البروتوكول
-- تاريخ آخر تفويض لهم
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-في قسم الشبكة ، سترى KPIs بالإضافة إلى القدرة على التبديل بين الفترات وتحليل مقاييس الشبكة بشكل مفصل. ستمنحك هذه التفاصيل فكرة عن كيفية أداء الشبكة بمرور الوقت.
+In this section, you can see global KPIs and view 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.
 
 ### نظره عامة
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - إجمالي حصة الشبكة الحالية
 - الحصة المقسمة بين المفهرسين ومفوضيهم
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - بارامترات البروتوكول مثل مكافأة التنسيق ومعدل التضخم والمزيد
 - رسوم ومكافآت الفترة الحالية
 
-بعض التفاصيل الأساسية الجديرة بالذكر:
+A few key details to note:
 
-- **Query fees represent the fees generated by the consumers**, and 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 the Indexers close their allocations towards the subgraphs they’ve been indexing. Thus the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days).
+- **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).
 
 ![صورة المستكشف 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - الفترة النشطة هي الفترة التي يقوم فيها المفهرسون حاليا بتخصيص الحصص وتحصيل رسوم الاستعلام
   - فترات التسوية هي تلك الفترات التي يتم فيها تسوية قنوات الحالة state channels. هذا يعني أن المفهرسين يكونون عرضة للشطب إذا فتح المستخدمون اعتراضات ضدهم.
   - فترات التوزيع هي تلك الفترات التي يتم فيها تسوية قنوات الحالة للفترات ويمكن للمفهرسين المطالبة بخصم رسوم الاستعلام الخاصة بهم.
-  - الفترات النهائية هي تلك الفترات التي ليس بها خصوم متبقية على رسوم الاستعلام للمطالبة بها من قبل المفهرسين ، وبالتالي يتم الانتهاء منها.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![صورة المستكشف 9](/img/Epoch-Stats.png)
 
 ## ملف تعريف المستخدم الخاص بك
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### نظرة عامة على الملف الشخصي
 
-هذا هو المكان الذي يمكنك فيه رؤية الإجراءات الحالية التي اتخذتها. وأيضا هو المكان الذي يمكنك فيه العثور على معلومات ملفك الشخصي والوصف وموقع الويب (إذا قمت بإضافته).
+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).
 
 ![صورة المستكشف 10](/img/Profile-Overview.png)
 
 ### تبويب ال Subgraphs
 
-إذا قمت بالنقر على تبويب Subgraphs ، فسترى ال subgraphs المنشورة الخاصة بك. لن يشمل ذلك أي subgraphs تم نشرها ب CLI لأغراض الاختبار - لن تظهر ال subgraphs إلا عند نشرها على الشبكة اللامركزية.
+In the Subgraphs tab, you’ll see 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.
 
 ![صورة المستكشف 11](/img/Subgraphs-Overview.png)
 
 ### تبويب الفهرسة
 
-إذا قمت بالنقر على تبويب الفهرسة "Indexing " ، فستجد جدولا به جميع المخصصات النشطة والتاريخية ل subgraphs ، بالإضافة إلى المخططات التي يمكنك تحليلها ورؤية أدائك السابق كمفهرس.
+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.
 
 هذا القسم سيتضمن أيضا تفاصيل حول صافي مكافآت المفهرس ورسوم الاستعلام الصافي الخاصة بك. سترى المقاييس التالية:
 
@@ -158,7 +189,9 @@ Now that we’ve talked about the network stats, let’s move on to your persona
 
 ### تبويب التفويض Delegating Tab
 
-المفوضون مهمون لشبكة the Graph. يجب أن يستخدم المفوض معرفته لاختيار مفهرسا يوفر عائدا على المكافآت. هنا يمكنك العثور على تفاصيل تفويضاتك النشطة والتاريخية ، مع مقاييس المفهرسين الذين قمت بتفويضهم.
+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.
 
 في النصف الأول من الصفحة ، يمكنك رؤية مخطط التفويض الخاص بك ، بالإضافة إلى مخطط المكافآت فقط. إلى اليسار ، يمكنك رؤية KPIs التي تعكس مقاييس التفويض الحالية.
 

From 1709f9b170504932fcd08415b11e58e0b468fcb2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:47 -0500
Subject: [PATCH 0756/1325] New translations explorer.mdx (Czech)

---
 website/pages/cs/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/cs/network/explorer.mdx b/website/pages/cs/network/explorer.mdx
index 5d12bb618838..e501104f13e9 100644
--- a/website/pages/cs/network/explorer.mdx
+++ b/website/pages/cs/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Průzkumník grafů
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Podgrafy
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Obrázek průzkumníka 1](/img/Subgraphs-Explorer-Landing.png)
 
-Po kliknutí do podgrafu budete moci testovat dotazy na hřišti a využívat podrobnosti o síti k přijímání informovaných rozhodnutí. Budete také moci signalizovat GRT na svém vlastním podgrafu nebo podgrafech ostatních, aby si indexátory uvědomily jeho důležitost a kvalitu. To je velmi důležité, protože signalizace na podgrafu motivuje k jeho indexaci, což znamená, že se v síti objeví a nakonec bude sloužit dotazům.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Obrázek průzkumníka 2](/img/Subgraph-Details.png)
 
-Na stránce věnované každému podgrafu se objeví několik podrobností. Patří mezi ně:
+On each subgraph’s dedicated page, you can do the following:
 
 - Signál/nesignál na podgraf
 - Zobrazit další podrobnosti, například grafy, ID aktuálního nasazení a další metadata
@@ -31,26 +45,32 @@ Na stránce věnované každému podgrafu se objeví několik podrobností. Pat
 
 ## Účastníci
 
-Na této kartě získáte přehled o všech osobách, které se podílejí na činnostech sítě, jako jsou indexátoři, delegáti a kurátoři. Níže si podrobně rozebereme, co pro vás jednotlivé karty znamenají.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexery
 
 ![Obrázek průzkumníka 4](/img/Indexer-Pane.png)
 
-Začněme u indexátorů. Základem protokolu jsou indexery, které sázejí na podgrafy, indexují je a obsluhují dotazy všech, kdo podgrafy spotřebovávají. V tabulce Indexers uvidíte parametry delegace indexerů, jejich podíl, kolik vsadili na jednotlivé podgrafy a kolik vydělali na poplatcích za dotazy a odměnách za indexování. Hlubší ponory níže:
+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.
 
-- Query Fee Cut - % slevy z poplatku za dotaz, které si indexátor ponechá při rozdělení s delegáty
-- Efektivní snížení odměny - indexační snížení odměny použité na fond delegací. Pokud je záporná, znamená to, že indexátor odevzdává část svých odměn. Pokud je kladná, znamená to, že si indexátor ponechává část svých odměn
-- Cooldown Remaining - doba, která zbývá do doby, kdy indexátor může změnit výše uvedené parametry delegování. Období Cooldown nastavují indexátory při aktualizaci parametrů delegování.
-- Owned - Jedná se o uložený podíl indexátora, který může být zkrácen za škodlivé nebo nesprávné chování.
-- Delegated - Podíl z delegátů, který může být přidělen indexátor, ale nemůže být zkrácen
-- Allocated - Podíl, který indexátory aktivně alokují k indexovaným podgrafy
-- Dostupná kapacita delegování - množství delegovaných podílů, které mohou indexátoři ještě obdržet, než dojde k jejich nadměrnému delegování
+**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.
-- Poplatky za dotazy - jedná se o celkové poplatky, které koncoví uživatelé zaplatili za dotazy z indexátoru za celou dobu
+- 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.
 
-Indexátoři mohou získat jak poplatky za dotazy, tak odměny za indexování. Funkčně k tomu dochází, když účastníci sítě delegují GRT na indexátor. To indexátorům umožňuje získávat poplatky za dotazování a odměny v závislosti na parametrech indexátoru. Parametry indexování se nastavují kliknutím na pravou stranu tabulky nebo vstupem do profilu indexátora a kliknutím na tlačítko "Delegate".
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Chcete-li se dozvědět více o tom, jak se stát indexátorem, můžete se podívat do [oficiální dokumentace](/network/indexing) nebo do [průvodců pro indexátory akademie graf.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ Chcete-li se dozvědět více o tom, jak se stát indexátorem, můžete se pod
 
 ### 2. Kurátoři
 
-Kurátoři analyzují podgrafy, aby určili, které podgrafy jsou nejkvalitnější. Jakmile kurátor najde potenciálně atraktivní podgraf, může jej kurátorovi signalizovat na jeho vazební křivce. Kurátoři tak dávají indexátorům vědět, které podgrafy jsou vysoce kvalitní a měly by být indexovány.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Kurátory mohou být členové komunity, konzumenti dat nebo dokonce vývojáři podgrafů, kteří signalizují své vlastní podgrafy tím, že vkládají žetony GRT do vazební křivky. Vložením GRT kurátoři razí kurátorské podíly podgrafu. V důsledku toho mají kurátoři nárok vydělat část poplatků za dotazy, které signalizovaný podgraf generuje. Vázací křivka motivuje kurátory ke kurátorství datových zdrojů nejvyšší kvality. Tabulka kurátorů v této části vám umožní vidět:
+In the The Curator table listed below you can see:
 
 - Datum, kdy kurátor zahájil kurátorskou činnost
 - Počet uložených GRT
@@ -68,34 +92,36 @@ Kurátory mohou být členové komunity, konzumenti dat nebo dokonce vývojáři
 
 ![Obrázek průzkumníka 6](/img/Curation-Overview.png)
 
-Pokud se chcete o roli kurátora dozvědět více, můžete tak učinit na následujících odkazech [The Graph Academy](https://thegraph.academy/curators/) nebo [oficiální dokumentace.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegáti
 
-Delegáti hrají klíčovou roli při udržování bezpečnosti a decentralizace sítě Graf. Podílejí se na síti tím, že delegují (tj. "sází") tokeny GRT jednomu nebo více indexátorům. Bez delegátů mají indexátoři menší šanci získat významné odměny a poplatky. Proto se indexátoři snaží přilákat delegáty tím, že jim nabízejí část odměn za indexování a poplatků za dotazy, které získají.
+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.
 
-Delegáti zase vybírají indexátory na základě řady různých proměnných, jako je výkonnost v minulosti, míra odměny za indexaci a snížení poplatků za dotaz. Svou roli může hrát i pověst v rámci komunity! Doporučujeme se s vybranými indexátory spojit prostřednictvím [Discord Grafu](https://discord.gg/graphprotocol) nebo [Fóra Grafu](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![Obrázek průzkumníka 7](/img/Delegation-Overview.png)
 
-Tabulka Delegáti vám umožní zobrazit aktivní delegáty v komunitě a také metriky, jako jsou:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Počet indexátorů, na které deleguje delegát
 - Původní delegace delegát
 - Odměny, které nashromáždili, ale z protokolu si je nevyzvedli
 - Realizované odměny odstranili z protokolu
 - Celkové množství GRT, které mají v současné době v protokolu
-- Datum, kdy byly naposledy delegovány na
+- The date they last delegated
 
-Pokud se chcete dozvědět více o tom, jak se stát delegátem, už nemusíte hledat dál! Stačí, když se vydáte na [oficiální dokumentaci](/network/delegating) nebo [Akademii Graf](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Síť
 
-V sekci Síť uvidíte globální klíčové ukazatele výkonnosti (KPI) a také možnost přepnout na základ epoch a detailněji analyzovat síťové metriky. Tyto podrobnosti vám poskytnou představu o tom, jak síť funguje v průběhu času.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - Současný celkový podíl v síti
 - Rozdělení stake mezi indexátory a jejich delegátory
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Parametry protokolu, jako je odměna za kurátorství, míra inflace a další
 - Odměny a poplatky současné epochy
 
-Několik klíčových informací, které stojí za zmínku:
+A few key details to note:
 
-- **Poplatky za dotazy představují poplatky generované spotřebiteli** a indexátory si je mohou nárokovat (nebo ne) po uplynutí nejméně 7 epoch (viz níže) poté, co byly jejich příděly vůči podgraf uzavřeny a data, která obsluhovali, byla potvrzena spotřebiteli.
-- ** Odměny za indexaci představují množství odměn, které indexátoři nárokovali ze síťové emise během epochy.** Ačkoli je emise protokolu pevně daná, odměny jsou vyraženy až poté, co indexátoři uzavřou své alokace vůči podgraf, které indexovali. Proto se počet odměn v jednotlivých epochách mění (tj. během některých epoch mohli indexátoři kolektivně uzavřít alokace, které byly otevřené mnoho dní).
+- **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).
 
 ![Obrázek průzkumníka 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ V části Epochy můžete na základě jednotlivých epoch analyzovat metriky, j
   - Aktivní epocha je ta, ve které indexéry právě přidělují podíl a vybírají poplatky za dotazy
   - Epoch zúčtování jsou ty, ve kterých se zúčtovávají stavové kanály. To znamená, že indexátoři podléhají krácení, pokud proti nim spotřebitelé zahájí spory.
   - 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.
-  - Finalizované epochy jsou epochy, u nichž indexátorům nezbývají žádné slevy z poplatků za dotaz, a jsou tedy finalizované.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Obrázek průzkumníka 9](/img/Epoch-Stats.png)
 
 ## Váš uživatelský profil
 
-Nyní, když jsme si řekli něco o statistikách sítě, přejděme k vašemu osobnímu profilu. Váš osobní profil je místem, kde vidíte svou aktivitu v síti, ať už se jí účastníte jakýmkoli způsobem. Vaše kryptopeněženka bude fungovat jako váš uživatelský profil a pomocí uživatelského panelu si ji budete moci prohlédnout:
+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:
 
 ### Přehled profilů
 
-Zde se zobrazují všechny aktuální akce, které jste provedli. Zde také najdete informace o svém profilu, popis a webové stránky (pokud jste si je přidali).
+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).
 
 ![Obrázek průzkumníka 10](/img/Profile-Overview.png)
 
 ### Tab Podgrafy
 
-Pokud kliknete na kartu podgrafy, zobrazí se vaše publikované podgrafy. Nebudou zde zahrnuty žádné podgrafy nasazené pomocí CLI pro účely testování - podgrafy se zobrazí až po jejich zveřejnění v decentralizované síti.
+In the Subgraphs tab, you’ll see 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.
 
 ![Obrázek průzkumníka 11](/img/Subgraphs-Overview.png)
 
 ### Tab Indexování
 
-Pokud kliknete na kartu Indexování, najdete tabulku se všemi aktivními a historickými alokacemi k dílčím grafy a také grafy, které můžete analyzovat a podívat se na svou minulou výkonnost jako indexátor.
+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.
 
 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:
 
@@ -158,7 +189,9 @@ Tato část bude také obsahovat podrobnosti o vašich čistých odměnách za i
 
 ### Tab Delegování
 
-Delegáti jsou pro síť Graf důležití. Delegát musí využít svých znalostí k výběru indexátora, který mu zajistí zdravou návratnost odměn. Zde najdete podrobnosti o svých aktivních a historických delegacích spolu s metrikami Indexátorů, ke kterým jste delegovali.
+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.
 
 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í.
 

From 32f56b03895b0fe7112b2b37ed398b1d48b6a355 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:48 -0500
Subject: [PATCH 0757/1325] New translations explorer.mdx (German)

---
 website/pages/de/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/de/network/explorer.mdx b/website/pages/de/network/explorer.mdx
index bca2993eb0b3..71f5b687a15d 100644
--- a/website/pages/de/network/explorer.mdx
+++ b/website/pages/de/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-When you click into a subgraph, you’ll be able to test queries in the playground and be able to leverage network details to make informed decisions. You’ll also be able 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, which means that it’ll surface on the network to eventually serve queries.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-On each subgraph’s dedicated page, several details are surfaced. These include:
+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
@@ -31,26 +45,32 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ## Participants
 
-Within this tab, you’ll get a bird’s eye view of all the people that are participating in the network activities, such as Indexers, Delegators, and Curators. Below, we’ll go into an in-depth review of what each tab means for you.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Let’s start with the Indexers. Indexers are the backbone of the protocol, being the ones that stake on subgraphs, index them, and serve queries to anyone consuming subgraphs. In the Indexers table, you’ll be able to see an Indexers’ delegation parameters, their stake, how much they have staked to each subgraph, and how much revenue they have made off of query fees and indexing rewards. Deep dives below:
+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.
 
-- 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
+**Besonderheiten**
+
+- 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
+- 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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 2. Curators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve. By depositing GRT, Curators mint curation shares of a subgraph. As a result, Curators are eligible to earn a portion of the query fees that the subgraph they have signaled on generates. The bonding curve incentivizes Curators to curate the highest quality data sources. The Curator table in this section will allow you to see:
+In the The Curator table listed below you can see:
 
 - The date the Curator started curating
 - The number of GRT that was deposited
@@ -68,34 +92,36 @@ Curators can be community members, data consumers, or even subgraph developers w
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. 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. Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers seek to attract Delegators by offering them a portion of the indexing rewards and query fees that they earn.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-The Delegators table will allow you to see the active Delegators in the community, as well as metrics such as:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - The number of Indexers a Delegator is delegating towards
 - A Delegator’s original delegation
 - The rewards they have accumulated but have not withdrawn from the protocol
 - The realized rewards they withdrew from the protocol
 - Total amount of GRT they have currently in the protocol
-- The date they last delegated at
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-In the Network section, you will see global KPIs as well as 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.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - The current total network stake
 - The stake split between the Indexers and their Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocol parameters such as curation reward, inflation rate, and more
 - Current epoch rewards and fees
 
-A few key details that are worth mentioning:
+A few key details to note:
 
-- **Query fees represent the fees generated by the consumers**, and 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 the Indexers close their allocations towards the subgraphs they’ve been indexing. Thus the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days).
+- **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)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - The active epoch is the one in which Indexers are currently allocating stake and collecting query fees
   - The settling epochs are the ones in which the state channels are being settled. This means that the Indexers are subject to slashing if the consumers open disputes against them.
   - 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, thus being finalized.
+  - 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)
 
 ## Your User Profile
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### Profile Overview
 
-This is where you can see any current actions you took. This is also where you can find your profile information, description, and website (if you added one).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Subgraphs Tab
 
-If you click into the Subgraphs tab, you’ll see 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.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Indexing Tab
 
-If you click into the Indexing tab, you’ll find a table with all the active and historical allocations towards the subgraphs, as well as charts that you can analyze and see your past performance as an Indexer.
+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.
 
 This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics:
 
@@ -158,7 +189,9 @@ This section will also include details about your net Indexer rewards and net qu
 
 ### Delegating Tab
 
-Delegators are important to the Graph Network. A Delegator must use their knowledge to choose an Indexer that will provide a healthy return on rewards. Here you can find details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards.
+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.
 
 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.
 

From 703f3a51e637ed84be41b0d51f709c4a61d1657d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:49 -0500
Subject: [PATCH 0758/1325] New translations explorer.mdx (Italian)

---
 website/pages/it/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/it/network/explorer.mdx b/website/pages/it/network/explorer.mdx
index f1d1a7a9f431..662aa790d17a 100644
--- a/website/pages/it/network/explorer.mdx
+++ b/website/pages/it/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraph
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-Quando si fa clic su un subgraph, è possibile testare le query nel playground e sfruttare i dettagli della rete per prendere decisioni informate. Sarà inoltre possibile segnalare il GRT sul proprio subgraph o su quello di altri per far capire agli Indexer la sua importanza e qualità. Questo è fondamentale perché la segnalazione di un subgraph ne incentiva l'indicizzazione, il che significa che verrà fuori dalla rete per servire le query.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-Nella pagina dedicata a ciascun subgraph vengono visualizzati diversi dettagli. Questi includono:
+On each subgraph’s dedicated page, you can do the following:
 
 - Segnala/non segnala i subgraph
 - Visualizza ulteriori dettagli, come grafici, ID di distribuzione corrente e altri metadati
@@ -31,26 +45,32 @@ Nella pagina dedicata a ciascun subgraph vengono visualizzati diversi dettagli.
 
 ## Partecipanti
 
-In questo tab è possibile avere una vista dall'alto di tutte le persone che partecipano alle attività della rete, come Indexer, Delegator e Curator. Di seguito, esamineremo in modo approfondito il significato di ogni tab per voi.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexer
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Cominciamo con gli Indexer. Gli Indexer sono la spina dorsale del protocollo, in quanto sono quelli che puntano sui subgraph, li indicizzano e servono le query a chiunque consumi i subgraph. Nella tabella degli Indexer, è possibile vedere i parametri di delega di un Indexer, la sua stake, quanto ha fatto il stake su ogni subgraph e quanto ha guadagnato con le tariffe di query e le ricompense per l'indicizzazione. Approfondimenti di seguito:
+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.
 
-- Query Fee Cut - la percentuale dei rimborsi delle tariffe di query che l'Indexer trattiene quando divide con i Delegator
-- Effective Reward Cut - il taglio della ricompensa di indicizzazione applicato al pool di delegator. Se è negativo, significa che l'Indexer sta cedendo parte delle sue ricompense. Se è positivo, significa che l'Indexer sta conservando una parte delle sue ricompense
-- Cooldown Remaining - il tempo rimanente prima che l'Indexer possa modificare i parametri di delega di cui sopra. I periodi di Cooldown sono impostati dagli Indexer quando aggiornano i loro parametri di delegazione
-- Owned - Si tratta del stake depositato dall'Indexer, che può essere ridotto in caso di comportamento dannoso o scorretto
-- Delegated - Stake del Delegator che può essere allocato dall'Indexer, ma non può essere tagliato
-- Allocated - Lo Stake che gli Indexer stanno attivamente allocando verso i subgraph che stanno indicizzando
-- Available Delegation Capacity - la quantità di stake delegato che gli Indexer possono ancora ricevere prima di diventare sovra-delegati
+**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 - è il totale delle tariffe che gli utenti finali hanno pagato per le query da un Indexer in tutto il tempo
+- 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.
 
-Gli Indexer possono guadagnare sia tariffe di query che ricompense per l'indicizzazione. Funzionalmente, ciò avviene quando i partecipanti alla rete delegano il GRT a un Indexer. Ciò consente agli Indexer di ricevere tariffe di query e ricompense in base ai loro parametri di indicizzazione. I parametri di indicizzazione si impostano facendo clic sul lato destro della tabella o accedendo al profilo dell'Indexer e facendo clic sul pulsante "Delegate".
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Per saperne di più su come diventare un Indexer, è possibile consultare la [documentazione ufficiale](/network/indexing) oppure [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ Per saperne di più su come diventare un Indexer, è possibile consultare la [do
 
 ### 2. Curator
 
-I Curator analizzano i subgraph per identificare quelli di maggiore qualità. Una volta che un Curator ha trovato un subgraph potenzialmente interessante, può curarlo segnalando la sua bonding curve. In questo modo, i Curator fanno sapere agli Indexer quali subgraph sono di alta qualità e dovrebbero essere indicizzati.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-I Curator possono essere membri della comunità, consumatori di dati o anche sviluppatori di subgraph che segnalano i propri subgraph depositando token GRT in una bonding curve. Depositando GRT, i Curator coniano quote di curation di un subgraph. Di conseguenza, i Curator hanno diritto a guadagnare una parte delle tariffe di query generate dal subgraph che hanno segnalato. La bonding curve incentiva i Curator a curare le fonti di dati di maggiore qualità. La tabella dei Curator in questa sezione consente di vedere:
+In the The Curator table listed below you can see:
 
 - La data in cui il Curator ha iniziato a curare
 - Il numero di GRT depositato
@@ -68,34 +92,36 @@ I Curator possono essere membri della comunità, consumatori di dati o anche svi
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-Per saperne di più sul ruolo del Curator, è possibile visitare i seguenti link [The Graph Academy](https://thegraph.academy/curators/) oppure la [documentazione ufficiale.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegator
 
-I Delegator svolgono un ruolo chiave nel mantenere la sicurezza e la decentralizzazione di The Graph Network. Partecipano alla rete delegando (cioè "staking") i token GRT a uno o più Indexer. Senza Delegator, gli Indexer hanno meno probabilità di guadagnare ricompense e commissioni significative. Pertanto, gli Indexer cercano di attrarre i Delegator offrendo loro una parte delle ricompense per l'indicizzazione e delle tariffe di query che guadagnano.
+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.
 
-I Delegator, a loro volta, selezionano gli Indexer in base a una serie di variabili diverse, come le prestazioni passate, i tassi di ricompensa per l'indicizzazione e le tariffe di query. Anche la reputazione all'interno della comunità può giocare un ruolo importante! Si consiglia di entrare in contatto con gli Indexer selezionati tramite [The Graph’s Discord](https://discord.gg/graphprotocol) oppure [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-La tabella dei Delegator consente di visualizzare i Delegator attivi nella comunità, oltre a metriche quali:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Il numero di Indexer verso cui un Delegator sta delegando
 - La delega originale di un Delegator
 - Le ricompense che hanno accumulato ma non ritirato dal protocollo
 - Le ricompense realizzate ritirate dal protocollo
 - Quantità totale di GRT che hanno attualmente nel protocollo
-- La data dell'ultima delegazione
+- The date they last delegated
 
-Se volete saperne di più su come diventare Delegator, non cercate oltre! Tutto ciò che dovete fare è andare alla [documentazione ufficiale](/network/delegating) oppure su [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## La rete
 
-Nella sezione Rete, oltre a trovare i KPI globali, è possibile passare a una base per epoche e analizzare le metriche di rete in modo più dettagliato. Questi dettagli danno un'idea dell'andamento della rete nel tempo.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - L'attuale stake totale della rete
 - La ripartizione dello stake tra gli Indexer e i loro Delegator
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Parametri di protocollo come la ricompensa per la curation, il tasso di inflazione e altro ancora
 - Premi e commissioni dell'epoca attuale
 
-Alcuni dettagli chiave che meritano di essere notati:
+A few key details to note:
 
-- **Le tariffe di query rappresentano le commissioni generate dai consumatori**, e possono essere reclamati (oppure no) dagli Indexer dopo un periodo di almeno 7 epoche (vedi sotto) dopo che le loro allocation verso i subgraph sono state chiuse e i dati che hanno servito sono stati convalidati dai consumatori.
-- **Le ricompense dell'indicizzazione rappresentano la quantità di ricompense che gli Indexer hanno richiesto all'emissione della rete durante l'epoca.** Sebbene l'emissione del protocollo sia fissa, le ricompense vengono coniate solo quando gli Indexer chiudono le loro allocation verso i subgraph che hanno indicizzato. Pertanto, il numero di ricompense per ogni epoca varia (ad esempio, durante alcune epoche, gli Indexer potrebbero aver chiuso collettivamente allocation aperte da molti giorni).
+- **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)
 
@@ -121,29 +147,34 @@ Nella sezione Epoche è possibile analizzare su base epocale metriche come:
   - L'epoca attiva è quella in cui gli Indexer stanno allocando le stake e riscuotendo le tariffe di query
   - Le epoche di assestamento sono quelle in cui i canali di stato sono in fase di definizione. Ciò significa che gli Indexer sono soggetti a taglio se i consumatori aprono controversie contro di loro.
   - 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.
-  - Le epoche finalizzate sono le epoche in cui gli Indexer non hanno più sconti sulle tariffe di query da richiedere e sono quindi finalizzate.
+  - 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)
 
 ## Il profilo utente
 
-Dopo aver parlato delle statistiche di rete, passiamo al profilo personale. Il vostro profilo personale è il luogo in cui potete vedere la vostra attività, indipendentemente da come state partecipando alla rete. Il vostro wallet fungerà da profilo utente e, grazie alla User Dashboard, sarete in grado di vedere:
+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:
 
 ### Panoramica del profilo
 
-Qui si possono vedere le azioni in corso. Qui si trovano anche le informazioni sul profilo, la descrizione e il sito web (se ne avete aggiunto uno).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Scheda di subgraph
 
-Se si fa clic sulla scheda Subgraph, si vedranno i subgraph pubblicati. Questi non includono i subgraph distribuiti con la CLI a scopo di test: i subgraph vengono visualizzati solo quando sono pubblicati sulla rete decentralizzata.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Scheda di indicizzazione
 
-Se si fa clic sulla scheda Indicizzazione, si troverà una tabella con tutte le allocation attive e storiche verso i subgraph, oltre a grafici che consentono di analizzare le performance passate come Indexer.
+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.
 
 Questa sezione include anche i dettagli sui compensi netti degli Indexer e sulle tariffe nette di query. Verranno visualizzate le seguenti metriche:
 
@@ -158,7 +189,9 @@ Questa sezione include anche i dettagli sui compensi netti degli Indexer e sulle
 
 ### Scheda di delege
 
-I delegator sono importanti per The Graph Network. Un Delegator deve utilizzare le proprie conoscenze per scegliere un Indexer che fornisca un buon ritorno sulle ricompense. Qui potete trovare i dettagli delle vostre delegazioni attive e storiche, insieme alle metriche degli Indexer verso cui avete delegato.
+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.
 
 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.
 

From 6f50489fb6e8c54f0dff2b3d901ff0407837b50c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:50 -0500
Subject: [PATCH 0759/1325] New translations explorer.mdx (Japanese)

---
 website/pages/ja/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/ja/network/explorer.mdx b/website/pages/ja/network/explorer.mdx
index 4d62708f191d..1fd4f1692eda 100644
--- a/website/pages/ja/network/explorer.mdx
+++ b/website/pages/ja/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: グラフエクスプローラ
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## サブグラフ
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![エクスプローラー画像1](/img/Subgraphs-Explorer-Landing.png)
 
-サブグラフをクリックすると、プレイグラウンドでクエリをテストすることができ、ネットワークの詳細を活用して情報に基づいた意思決定を行うことができます。 また、自分のサブグラフや他の人のサブグラフで GRT をシグナリングして、その重要性や品質をインデクサに認識させることができます。 これは、サブグラフにシグナルを送ることで、そのサブグラフがインデックス化され、最終的にクエリに対応するためにネットワーク上に現れてくることを意味するため、非常に重要です。
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![エクスプローラーイメージ 2](/img/Subgraph-Details.png)
 
-各サブグラフの専用ページでは、いくつかの詳細が表示されます。 その内容は以下の通りです：
+On each subgraph’s dedicated page, you can do the following:
 
 - サブグラフのシグナル/アンシグナル
 - チャート、現在のデプロイメント ID、その他のメタデータなどの詳細情報の表示
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## 参加者
 
-このタブでは、Indexer、Delegator、Curators など、ネットワークアクティビティに参加している全ての人を俯瞰できます。 以下では、各タブの意味を詳しく説明します。
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. インデクサー（Indexers）
 
 ![エクスプローラーイメージ 4](/img/Indexer-Pane.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.
 
-- Query Fee Cut - デリゲーターとの分配時にインデクサーが保持するクエリーフィーリベートの割合
-- Effective Reward Cut - デリゲーションプールに適用されるインデックス報酬のカット。 これがマイナスの場合、インデクサーが報酬の一部を手放していることを意味します。 プラスの場合は、インデクサーが報酬の一部を保持していることを意味します
-- Cooldown Remaining - インデクサーが上記のデリゲーションパラメータを変更できるようになるまでの残り時間です。 クールダウン期間は、インデクサーがデリゲーションパラメータを更新する際に設定します
-- Owned - インデクサーが預けているステークで、悪意のある行為や不正な行為があった場合にスラッシュされる可能性があります
-- Delegated- インデクサーによって割り当てることはできますが、スラッシュすることはできませんデリゲーターからのステーク
-- Allocated - インデックスを作成中のサブグラフに対してインデクサーが割り当てているステーク額
-- Available Delegation Capacity - インデクサーが過度に委任される前にまだ受け取ることができる委任されたステークの量
+**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 - あるインデクサーのクエリに対してエンドユーザーが支払った手数料の合計額です
+- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time.
 - Indexer Rewards - インデクサーとそのデリゲーターが過去に獲得したインデクサー報酬の総額。 インデクサー報酬は GRT の発行によって支払われます
 
-インデクサーはクエリ報酬とインデックス報酬の両方を得ることができます。 機能的には、ネットワーク参加者が GRT をインデクサーにデリゲーションしたときに発生します。 これにより、インデクサーはそのインデクサーパラメータに応じてクエリフィーや報酬を受け取ることができます。 インデックスパラメータの設定は、表の右側をクリックするか、インデクサーのプロフィールにアクセスして「Delegate」ボタンをクリックすることで行うことができます。
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 インデクサーになるには、[公式ドキュメント](/network/indexing)や[The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)を見てみてください。
 
@@ -58,9 +78,13 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ### 2. キュレーター
 
-キュレーターはサブグラフを分析し、どのサブグラフが最高品質であるかを特定します。 キュレーターが魅力的なサブグラフを見つけたら、そのボンディングカーブにシグナルを送ることでキュレーションすることができます。 そうすることで、キュレーターはインデクサーにどのサブグラフが高品質であり、インデックスを作成すべきかを知らせることができます。
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-キュレーターはコミュニティのメンバー、データ消費者、あるいはサブグラフの開発者でもあり、GRT トークンをボンディングカーブに預けることで自分のサブグラフにシグナルを送ります。 GRT を預け入れることで、キュレーターはサブグラフのキュレーションシェアを獲得します。 その結果、キュレーターは、自分がシグナルを送ったサブグラフが生成したクエリフィーの一部を得ることができます。 ボンディングカーブは、キュレーターが最高品質のデータソースをキュレーションする動機付けとして機能します。 このセクションの「Curator」テーブルでは、以下を確認することができます：
+In the The Curator table listed below you can see:
 
 - キュレーターがキュレーションを開始した日付
 - デポジットされた GRT の数
@@ -68,34 +92,36 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ![エクスプローラーイメージ ６](/img/Curation-Overview.png)
 
-キュレーターの役割についてさらに詳しく知りたい場合は、[The Graph Academy](https://thegraph.academy/curators/) か [official documentation.](/network/curating)を参照してください。
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. デリゲーター
 
-デリゲーターは、グラフネットワークの安全性と分散性を維持するための重要な役割を担っています。 デリゲーターは、GRT トークンを 1 人または複数のインデクサーにデリゲート（＝「ステーク」）することでネットワークに参加します。 デリゲーターがいなければ、インデクサーは大きな報酬や手数料を得ることができません。 そのため、インデクサーは獲得したインデクシング報酬やクエリフィーの一部をデリゲーターに提供することで、デリゲーターの獲得を目指します。
+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.
 
-デリゲーターは、過去のパフォーマンス、インデクシング報酬率、クエリ手数料の割引率など、さまざまな要因に基づいてインデクサーを選択します。コミュニティ内での評判もこれに影響を与える可能性があります！選ばれたインデクサーと連携することをお勧めします。それには[The Graph's Discord](https://discord.gg/graphprotocol)or[The Graph Forum](https://forum.thegraph.com/)を利用することができます！
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![エクスプローラーイメージ ７](/img/Delegation-Overview.png)
 
-「Delegators」テーブルでは、コミュニティ内のアクティブなデリゲーターを確認できるほか、以下のような指標も確認できます：
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - デリゲーターがデリゲーションしているインデクサー数
 - デリゲーターの最初のデリゲーション内容
 - デリゲーターが蓄積したがプロトコルから引き出していない報酬
 - プロトコルから撤回済みの報酬
 - 現在プロトコルに保持している GRT 総量
-- 最後にデリゲートした日
+- The date they last delegated
 
-委任者になる方法について詳しく知りたい場合は、もう探す必要はありません。 [公式ドキュメント](/network/delegating)または[The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers)にアクセスするだけです。
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## ネットワーク
 
-「Network」セクションでは、グローバルな KPI に加えて、エポック単位に切り替えてネットワークメトリクスをより詳細に分析する機能があります。 これらの詳細を見ることで、ネットワークが時系列でどのようなパフォーマンスをしているかを知ることができます。
+In this section, you can see global KPIs and view 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.
 
 ### 概要
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - 現在のネットワーク全体のステーク額
 - インデクサーとデリゲーター間のステーク配分
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - キュレーション報酬、インフレーション・レートなどのプロトコルパラメータ
 - 現在のエポックの報酬と料金
 
-特筆すべき重要な詳細をいくつか挙げます：
+A few key details to note:
 
-- **クエリフィーは消費者によって生成された報酬を表し**、サブグラフへの割り当てが終了し、提供したデータが消費者によって検証された後、少なくとも 7 エポック（下記参照）の期間後にインデクサが請求することができます（または請求しないこともできます）。
-- **I インデックス報酬は、エポック期間中にインデクサーがネットワーク発行から請求した報酬の量を表しています。**プロトコルの発行は固定されていますが、報酬はインデクサーがインデックスを作成したサブグラフへの割り当てを終了して初めてミントされます。 そのため、エポックごとの報酬数は変動します（例えば、あるエポックでは、インデクサーが何日も前から開いていた割り当てをまとめて閉じたかもしれません）。
+- **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).
 
 ![エクスプローラーイメージ ８](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ The overview section has all the current network metrics as well as some cumulat
   - アクティブエポックとは、インデクサーが現在ステークを割り当て、クエリフィーを収集しているエポックのこと
   - 決済エポックとは、状態のチャンネルを決済しているエポックのこと。 つまり、消費者がインデクサーに対して異議を唱えた場合、インデクサーはスラッシュされる可能性があるということ
   - 分配エポックとは、そのエポックの状態チャンネルが確定し、インデクサーがクエリフィーのリベートを請求できるようになるエポックのこと
-  - 確定したエポックとは、インデクサーが請求できるクエリフィーのリベートが残っていないエポックのことで、確定している
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![エクスプローラーイメージ ９](/img/Epoch-Stats.png)
 
 ## ユーザープロファイル
 
-ネットワーク統計について説明したので、個人プロファイルに移りましょう。個人プロファイルは、ネットワークへの参加方法に関係なく、ネットワーク アクティビティを確認できる場所です。クリプト ウォレットはユーザー プロファイルとして機能し、ユーザー ダッシュボードでは次の情報を確認できます。
+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:
 
 ### プロフィールの概要
 
-ここでは、あなたが現在行ったアクションを確認できます。 また、自分のプロフィール情報、説明、ウェブサイト（追加した場合）もここに表示されます。
+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).
 
 ![エクスプローラーイメージ 10](/img/Profile-Overview.png)
 
 ### サブグラフタブ
 
-「Subgraphs」タブをクリックすると、公開されているサブグラフが表示されます。 サブグラフは分散型ネットワークに公開されたときにのみ表示されます。
+In the Subgraphs tab, you’ll see 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.
 
 ![エクスプローラーイメージ 11](/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.
 
 このセクションには、インデクサー報酬とクエリフィーの詳細も含まれます。 以下のような指標が表示されます：
 
@@ -158,7 +189,9 @@ The overview section has all the current network metrics as well as some cumulat
 
 ### デリゲーションタブ
 
-デリゲーターは、グラフネットワークにとって重要な存在です。 デリゲーターは知見を駆使して、健全な報酬を提供するインデクサーを選ばなければなりません。 このタブでは、アクティブなデリゲーションの詳細と過去の履歴、そしてデリゲートしたインデクサーの各指標を確認することができます。
+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.
 
 ページの前半には、自分のデリゲーションチャートと報酬のみのチャートが表示されています。 左側には、現在のデリゲーションメトリクスを反映した KPI が表示されています。
 

From f4ecbd737ef8e187fe756e51c21f0c5b2aa7b89e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:51 -0500
Subject: [PATCH 0760/1325] New translations explorer.mdx (Korean)

---
 website/pages/ko/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/ko/network/explorer.mdx b/website/pages/ko/network/explorer.mdx
index bca2993eb0b3..02dca6ed2f9f 100644
--- a/website/pages/ko/network/explorer.mdx
+++ b/website/pages/ko/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-When you click into a subgraph, you’ll be able to test queries in the playground and be able to leverage network details to make informed decisions. You’ll also be able 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, which means that it’ll surface on the network to eventually serve queries.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-On each subgraph’s dedicated page, several details are surfaced. These include:
+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
@@ -31,26 +45,32 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ## Participants
 
-Within this tab, you’ll get a bird’s eye view of all the people that are participating in the network activities, such as Indexers, Delegators, and Curators. Below, we’ll go into an in-depth review of what each tab means for you.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Let’s start with the Indexers. Indexers are the backbone of the protocol, being the ones that stake on subgraphs, index them, and serve queries to anyone consuming subgraphs. In the Indexers table, you’ll be able to see an Indexers’ delegation parameters, their stake, how much they have staked to each subgraph, and how much revenue they have made off of query fees and indexing rewards. Deep dives below:
+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.
 
-- 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
+**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
+- 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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 2. Curators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve. By depositing GRT, Curators mint curation shares of a subgraph. As a result, Curators are eligible to earn a portion of the query fees that the subgraph they have signaled on generates. The bonding curve incentivizes Curators to curate the highest quality data sources. The Curator table in this section will allow you to see:
+In the The Curator table listed below you can see:
 
 - The date the Curator started curating
 - The number of GRT that was deposited
@@ -68,34 +92,36 @@ Curators can be community members, data consumers, or even subgraph developers w
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. 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. Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers seek to attract Delegators by offering them a portion of the indexing rewards and query fees that they earn.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-The Delegators table will allow you to see the active Delegators in the community, as well as metrics such as:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - The number of Indexers a Delegator is delegating towards
 - A Delegator’s original delegation
 - The rewards they have accumulated but have not withdrawn from the protocol
 - The realized rewards they withdrew from the protocol
 - Total amount of GRT they have currently in the protocol
-- The date they last delegated at
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-In the Network section, you will see global KPIs as well as 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.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - The current total network stake
 - The stake split between the Indexers and their Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocol parameters such as curation reward, inflation rate, and more
 - Current epoch rewards and fees
 
-A few key details that are worth mentioning:
+A few key details to note:
 
-- **Query fees represent the fees generated by the consumers**, and 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 the Indexers close their allocations towards the subgraphs they’ve been indexing. Thus the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days).
+- **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)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - The active epoch is the one in which Indexers are currently allocating stake and collecting query fees
   - The settling epochs are the ones in which the state channels are being settled. This means that the Indexers are subject to slashing if the consumers open disputes against them.
   - 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, thus being finalized.
+  - 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)
 
 ## Your User Profile
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### Profile Overview
 
-This is where you can see any current actions you took. This is also where you can find your profile information, description, and website (if you added one).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Subgraphs Tab
 
-If you click into the Subgraphs tab, you’ll see 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.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Indexing Tab
 
-If you click into the Indexing tab, you’ll find a table with all the active and historical allocations towards the subgraphs, as well as charts that you can analyze and see your past performance as an Indexer.
+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.
 
 This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics:
 
@@ -158,7 +189,9 @@ This section will also include details about your net Indexer rewards and net qu
 
 ### Delegating Tab
 
-Delegators are important to the Graph Network. A Delegator must use their knowledge to choose an Indexer that will provide a healthy return on rewards. Here you can find details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards.
+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.
 
 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.
 

From 30720c36c6764dcc1384e584300b4a440f27bed5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:53 -0500
Subject: [PATCH 0761/1325] New translations explorer.mdx (Dutch)

---
 website/pages/nl/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/nl/network/explorer.mdx b/website/pages/nl/network/explorer.mdx
index e372bdaa81d3..cb2be6378d2a 100644
--- a/website/pages/nl/network/explorer.mdx
+++ b/website/pages/nl/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Afbeelding 1](/img/Subgraphs-Explorer-Landing.png)
 
-Wanneer u op een subgraph klikt, kunt u query's testen in de playground en netwerkdetails gebruiken om geïnformeerde beslissingen te nemen. U kunt ook GRT signaleren op uw eigen subgraph of de subgraph van anderen om indexeerders bewust te maken van het belang en de kwaliteit ervan. Dit is cruciaal, want het signaleren op een subgraph stimuleert het om geïndexeerd te worden, wat betekent dat het op het netwerk zal verschijnen om uiteindelijk query's te serveren.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Afbeelding 2](/img/Subgraph-Details.png)
 
-Op elke pagina toegewijd aan een subgraph, worden verschillende details weergegeven. Bijvoorbeeld:
+On each subgraph’s dedicated page, you can do the following:
 
 - Het toevoegen/weghalen van signaal op een subgraph
 - Details zoals grafieken, huidige implementatie-ID en andere metadata
@@ -31,26 +45,32 @@ Op elke pagina toegewijd aan een subgraph, worden verschillende details weergege
 
 ## Deelnemers
 
-Binnen dit tabblad krijgt u een vogelvlucht van alle mensen die deelnemen aan de netwerkactiviteiten, zoals Indexeerders, Delegeerders en Curatoren. Hieronder zullen we dieper ingaan op wat elk tabblad voor u betekent.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Afbeelding 4](/img/Indexer-Pane.png)
 
-Laten we beginnen met de Indexers. Indexers zijn de ruggengraat van het protocol, zij zijn degenen die Grt staken op subgraphs, deze indexeren en query's leveren aan iedereen die de subgraphs gebruikt. In de tabel van de Indexers kunt u de delegatieparameters van een Indexer, hun inzet, hoeveel stake ze op elke subgraph en hoeveel inkomsten ze hebben gegenereerd uit queryvergoedingen en indexeringsbeloningen zien. Meer details hieronder:
+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.
 
-- Query Fee Cut - het % van de queryvergoedingen dat de Indexer behoudt na het delen met Delegeerders
-- Effective Reward Aandeel - de indexeringsbeloning die wordt toegepast op de Delegatie pool. Als dit negatief is, betekent dit dat de Indexeerder een deel van hun beloningen weggeeft. Als dit positief is, betekent dit dat de Indexeerder een deel van hun beloningen behoudt
-- Cooldown Remaining - de resterende tijd tot de Indexeerder de bovenstaande delegatieparameters kan wijzigen. Cooldown-perioden worden ingesteld door Indexeerders wanneer ze hun delegatieparameters bijwerken
-- Owned - Dit is de eigen stake van de Indexer, die kan worden verlaagd vanwege kwaadwillig of incorrect gedrag
-- Delegated - Dit is de stake van de Delegeerders die door de Indexeerders kunnen worden gebruikt, maar niet kunnen worden afgenomen bij kwaadwillig of incorrect gedrag van de Indexeerder
-- Allocated - Stake die Indexers actief alloceren aan de subgraphs die ze indexeren
-- Available Delegation Capacity - het bedrag van gedelegeerde inzet dat de Indexeerders nog kunnen ontvangen voordat ze overgedelegeerd worden
+**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 - dit zijn de totale kosten die eindgebruikers hebben betaald voor query's van een Indexer
+- 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.
 
-Indexeerders kunnen zowel queryvergoedingen als indexeringsbeloningen verdienen. Functioneel gebeurt dit wanneer netwerkdeelnemers GRT aan een Indexeerder delegeren. Hierdoor kunnen Indexeerders queryvergoedingen en beloningen ontvangen, afhankelijk van hun Indexeerder parameters. Indexeerparameters worden ingesteld door aan de rechterkant van de tabel te klikken, of door naar het profiel van een Indexeerder te gaan en op de knop "Delegate" te klikken.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Om meer te weten te komen over hoe je een Indexer kunt worden, kun je een kijkje nemen in de [officiële documentatie](/network/indexing) of de Indexeerdersgidsen van [The Graph Academy](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ Om meer te weten te komen over hoe je een Indexer kunt worden, kun je een kijkje
 
 ### 2. Curatoren
 
-Curatoren analyseren subgraphs om te identificeren welke subgraphs van de hoogste kwaliteit zijn. Zodra een Curator een potentieel aantrekkelijke subgraph heeft gevonden, kunnen ze deze cureren door te signaleren, met Grt, op de bonding curve. Door dit te doen, laten Curatoren Indexeerders weten welke subgraphs van hoge kwaliteit zijn en geïndexeerd moeten worden.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curatoren kunnen leden zijn van de community, dataconsumenten, of zelf subgraph-ontwikkelaars die op hun eigen subgraphs signaleren door GRT-tokens in een bonding curve te storten. Door GRT te storten, maken Curatoren curator-aandelen van een subgraph aan. Als gevolg hiervan komen Curatoren in aanmerking om een deel van de querykosten te verdienen die de subgraph waarop zijn hebben gesignaleerd gerenereert. De bonding curve stimuleert Curatoren om de hoogste kwaliteit data te cureren. De Curator-tabel in deze sectie laart je zien:
+In the The Curator table listed below you can see:
 
 - De datum waarop de curator is begonnen met cureren
 - Het gestorte aantal GRT
@@ -68,34 +92,36 @@ Curatoren kunnen leden zijn van de community, dataconsumenten, of zelf subgraph-
 
 ![Explorer Afbeelding 6](/img/Curation-Overview.png)
 
-Als je meer wilt weten over de rol van de Curator, kun je de volgende websites bezoeken: [The Graph Academy](https://thegraph.academy/curators/) of de [officiële documentatie.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegators
 
-Delegators spelen een belangrijke rol in het bewaken van de veiligheid en decentralisatie van het Graph Netwerk. Ze nemen deel aan het netwerk door hun GRT-tokens te delegeren aan één of meerdere Indexeerders. Zonder Delegators krijgen Indexeerders minder beloningen en vergoedingen. Daarom proberen Indexeerders Delegators aan te trekken door hen een deel van de indexeringsbeloningen en query-vergoedingen die zij verdienen aan te bieden.
+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.
 
-Delegators kiezen op hun beurt Indexeerders op basis van verschillende variabelen, zoals eerdere prestaties, hoeveelheid indexeringsbeloningen en hoeveelheid query-vergoedingen. Reputatie binnen de community kan hierbij ook een rol spelen. Het is aanbevolen om contact te leggen met de inderxers via [de Graph Discord](https://discord.gg/graphprotocol) of [het Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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 Afbeelding 7](/img/Delegation-Overview.png)
 
-De tabel met Delegators geeft je een overzicht van de actieve Delegators in de community, het laat ook de volgende statistieken zien:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Het aantal Indexeerders waaraan een Delegator heeft gedelegeerd
 - De oorspronkelijke delegatie van een Delegator
 - De beloningen die ze hebben opgebouwd, maar nog niet hebben opgenomen uit het protocol
 - De gerealiseerde beloningen die ze uit het protocol hebben opgenomen
 - Het totale bedrag aan GRT dat ze momenteel in het protocol hebben
-- De datum waarop ze voor het laatst hebben gedelegeerd
+- The date they last delegated
 
-Wil je meer leren over hoe je een Delegator kunt worden? Zoek niet verder! Het enige wat je hoeft te doen is naar de [official documentatie](/network/delegating) of [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) te gaan.
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Netwerk
 
-In het "Netwerk" gedeelte ziet u de prestatie-indicatoren, evenals de mogelijkheid om te wisselen naar een per-epoch basis en netwerkmetrieken gedetailleerder te analyseren. Deze details geven u een beeld van hoe het netwerk presteert over een bepaalde tijd.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - De huidige totale hoeveelheid GRT in het netwerk
 - De verdeling van de GRT tussen Indexeerders en hun Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocolparameters zoals curatiebeloningen, inflatiepercentage, en meer
 - Huidige epoch beloningen en kosten
 
-Een paar belangrijke details die het vermelden waard zijn:
+A few key details to note:
 
-- **Querykosten vertegenwoordigen de kosten die door de consumenten worden gegenereerd** en kunnen (of niet) door de indexeerders worden geclaimd na een periode van ten minste 7 epochs (zie hieronder) nadat hun allocaties naar de subgraphs zijn gesloten en de data die zij hebben geleverd is gevalideerd door de consumenten.
-- **Indexeringsbeloningen vertegenwoordigen de hoeveelheid beloningen die de Indexers hebben geclaimd van de netwerk uitgifte tijdens de epoch.** Hoewel de uitgifte van nieuwe Grt vaststaat, worden de beloningen pas gemunt nadat de Indexers hun allocaties naar de subgraphs die ze hebben geïndexeerd, sluiten. Daarom varieert het aantal beloningen per epoch (Bijvoorbeeld, tijdens sommige epochs, hebben Indexers mogelijk gezamenlijk allocaties gesloten die al vele dagen open stonden).
+- **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 Afbeelding 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ In de Epochs afdeling kun je per epoch verschillende metrieken analyseren, zoals
   - De actieve epoch is degene waarin Indexers momenteel Grt toewijzen en querykosten verzamelen
   - De afhandelende epochs zijn die waarin de state channels worden afgehandeld. Dit betekent dat Indexers te maken kunnen krijgen met slashing als consumenten geschillen tegen hen openen.
   - De distribuerende epochs zijn de epochs waarin de state channels voor de epochs worden afgehandeld en Indexeerders hun querykostenkorting kunnen claimen.
-  - De afgeronde epochs zijn de epochs waarin geen querykostenkortingen meer te claimen zijn door de Indexeerders, waardoor ze als afgerond worden beschouwd.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Explorer Afbeelding 9](/img/Epoch-Stats.png)
 
 ## Uw Gebruikersprofiel
 
-Nu we het hebben gehad over de netwerkstatistieken, laten we verder gaan met uw persoonlijk profiel. Uw persoonlijk profiel is de plek waar u uw netwerkactiviteit kunt zien, ongeacht hoe u deelneemt aan het netwerk. Uw crypto wallet fungeert als uw gebruikersprofiel, en met het gebruikersdashboard kunt u het volgende zien:
+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:
 
 ### Profieloverzicht
 
-Hier kunt u zien welke acties u onlangs hebt ondernomen. Dit is ook waar u uw profielinformatie, beschrijving, en website (als u er een hebt toegevoegd) kunt vinden.
+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).
 
 ![Explorer Afbeelding 10](/img/Profile-Overview.png)
 
 ### Subgraph Tab
 
-Als u op de Subgraphs tab klikt, ziet u uw gepubliceerde subgraphs. Dit bevat niet de subgraphs die geïmplementeerd zijn met de CLI voor testdoeleinden - subgraphs worden alleen weergegeven als ze zijn gepubliceerd op het gedecentraliseerde netwerk.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Afbeelding 11](/img/Subgraphs-Overview.png)
 
 ### Indexing Tab
 
-Als u op de Indexing tab klikt, vindt u een tabel met alle actieve en historische allocaties op de subgraphs, evenals grafieken waarmee u uw eerder prestaties als Indexeerder kunt analyseren.
+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.
 
 Dit gedeelte bevat ook details over uw netto indexeringsbeloningen en netto querykosten. U zult de volgende metrics zien:
 
@@ -158,7 +189,9 @@ Dit gedeelte bevat ook details over uw netto indexeringsbeloningen en netto quer
 
 ### Delegating Tab
 
-Delegators zijn belangrijk voor The Graph Network. Een Delegator moet hun kennis gebruiken om een Indexer te kiezen die een gezond rendement op beloningen zal bieden. Hier kunt u details vinden van uw actieve en historische delegaties, samen met de metrics van de Indexeerders waarnaar u hebt gedelegeerd.
+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.
 
 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.
 

From 6d9b25971b2b2cac813a7301ada89bc7c493c0c3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:54 -0500
Subject: [PATCH 0762/1325] New translations explorer.mdx (Polish)

---
 website/pages/pl/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/pl/network/explorer.mdx b/website/pages/pl/network/explorer.mdx
index 50c9a33dbbca..05b322667e92 100644
--- a/website/pages/pl/network/explorer.mdx
+++ b/website/pages/pl/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgrafy
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-When you click into a subgraph, you’ll be able to test queries in the playground and be able to leverage network details to make informed decisions. You’ll also be able 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, which means that it’ll surface on the network to eventually serve queries.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-On each subgraph’s dedicated page, several details are surfaced. These include:
+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
@@ -31,26 +45,32 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ## Participants
 
-Within this tab, you’ll get a bird’s eye view of all the people that are participating in the network activities, such as Indexers, Delegators, and Curators. Below, we’ll go into an in-depth review of what each tab means for you.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Let’s start with the Indexers. Indexers are the backbone of the protocol, being the ones that stake on subgraphs, index them, and serve queries to anyone consuming subgraphs. In the Indexers table, you’ll be able to see an Indexers’ delegation parameters, their stake, how much they have staked to each subgraph, and how much revenue they have made off of query fees and indexing rewards. Deep dives below:
+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.
 
-- 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
+**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
+- 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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 2. Curators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve. By depositing GRT, Curators mint curation shares of a subgraph. As a result, Curators are eligible to earn a portion of the query fees that the subgraph they have signaled on generates. The bonding curve incentivizes Curators to curate the highest quality data sources. The Curator table in this section will allow you to see:
+In the The Curator table listed below you can see:
 
 - The date the Curator started curating
 - The number of GRT that was deposited
@@ -68,34 +92,36 @@ Curators can be community members, data consumers, or even subgraph developers w
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. 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. Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers seek to attract Delegators by offering them a portion of the indexing rewards and query fees that they earn.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-The Delegators table will allow you to see the active Delegators in the community, as well as metrics such as:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - The number of Indexers a Delegator is delegating towards
 - A Delegator’s original delegation
 - The rewards they have accumulated but have not withdrawn from the protocol
 - The realized rewards they withdrew from the protocol
 - Total amount of GRT they have currently in the protocol
-- The date they last delegated at
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-In the Network section, you will see global KPIs as well as 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.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - The current total network stake
 - The stake split between the Indexers and their Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocol parameters such as curation reward, inflation rate, and more
 - Current epoch rewards and fees
 
-A few key details that are worth mentioning:
+A few key details to note:
 
-- **Query fees represent the fees generated by the consumers**, and 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 the Indexers close their allocations towards the subgraphs they’ve been indexing. Thus the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days).
+- **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)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - The active epoch is the one in which Indexers are currently allocating stake and collecting query fees
   - The settling epochs are the ones in which the state channels are being settled. This means that the Indexers are subject to slashing if the consumers open disputes against them.
   - 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, thus being finalized.
+  - 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)
 
 ## Your User Profile
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### Profile Overview
 
-This is where you can see any current actions you took. This is also where you can find your profile information, description, and website (if you added one).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Subgraphs Tab
 
-If you click into the Subgraphs tab, you’ll see 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.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Indexing Tab
 
-If you click into the Indexing tab, you’ll find a table with all the active and historical allocations towards the subgraphs, as well as charts that you can analyze and see your past performance as an Indexer.
+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.
 
 This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics:
 
@@ -158,7 +189,9 @@ This section will also include details about your net Indexer rewards and net qu
 
 ### Delegating Tab
 
-Delegators are important to the Graph Network. A Delegator must use their knowledge to choose an Indexer that will provide a healthy return on rewards. Here you can find details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards.
+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.
 
 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.
 

From 24e06ccac7ed0881a966b6c21fdb3cef3594dea8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:55 -0500
Subject: [PATCH 0763/1325] New translations explorer.mdx (Portuguese)

---
 website/pages/pt/network/explorer.mdx | 103 +++++++++++++++++---------
 1 file changed, 68 insertions(+), 35 deletions(-)

diff --git a/website/pages/pt/network/explorer.mdx b/website/pages/pt/network/explorer.mdx
index 11471e603cfa..31d87224dc8c 100644
--- a/website/pages/pt/network/explorer.mdx
+++ b/website/pages/pt/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Seja bem vindo ao Graph Explorer — ou, como gostamos de chamá-lo, o seu portal descentralizado ao mundo de dados de subgraphs e redes. 👩🏽‍🚀 O Graph Explorer consiste de vários componentes onde você pode interagir com outros programadores de subgraphs e dApps, Curadores, Indexadores e Delegantes. Para um resumo geral do Graph Explorer, confira o vídeo abaixo (ou continue a ler):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-Primeiramente, se acabou de lançar e editar o seu subgraph no Subgraph Studio, pode ver os seus próprios subgraphs finalizados (e também os dos outros) na rede descentralizada, na aba Subgraphs no topo da barra de navegação. Aqui, poderá achar o subgraph exato que procura com base na data de criação, quantidade de sinais, ou nome.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Imagem do Explorer 1](/img/Subgraphs-Explorer-Landing.png)
 
-Ao clicar em um subgraph, pode testar consultas no playground e aproveitar detalhes da rede para informar suas decisões. Também poderá sinalizar GRT no seu próprio subgraph, ou nos de outros, para que os indexadores tenham ciência da sua importância e qualidade. Isto é crítico, porque a sinalização em um subgraph o incentiva a ser indexado, o que significa que ele subirá na rede para eventualmente servir consultas.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Imagem do Explorer 2](/img/Subgraph-Details.png)
 
-Vários detalhes são exibidos na página dedicada de cada subgraph. Eles incluem:
+On each subgraph’s dedicated page, you can do the following:
 
 - Sinalização/cancelamento de sinais em subgraphs
 - Ver mais detalhes como gráficos, ID de lançamento atual, e outros metadados
@@ -31,26 +45,32 @@ Vários detalhes são exibidos na página dedicada de cada subgraph. Eles inclue
 
 ## Participantes
 
-Dentro desta aba, terá uma vista panorâmica de todas as pessoas que participam das atividades da rede, como Indexadores, Delegantes e Curadores. Abaixo, faremos uma revisão profunda do significado de cada aba.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexadores
 
 ![Imagem do Explorer 4](/img/Indexer-Pane.png)
 
-Vamos começar com os Indexadores. Estes são a coluna do protocolo; fazem staking em subgraphs, os indexam, e servem queries para qualquer consumidor de subgraphs. Na tábua Indexers, poderá ver os parâmetros de delegação dos Indexadores, os stakes deles, quantos stakes fizeram em cada subgraph, e a renda que ganharam de taxas de consulta e recompensas de indexação. Mais detalhes abaixo:
+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.
 
-- Porção de Taxa de Query — a % 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 depositados 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 estão a alocar ativamente 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 demais
+**Especificações**
+
+- 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.
 - 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 Consulta — as taxas totais que os utilizadores finais pagaram por queries de um Indexador durante todo o seu tempo
+- Query Fees - this is the total fees that end users have paid for queries from an Indexer over all time.
 - 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.
 
-Os indexadores podem ganhar taxas de consulta 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 consultas, a depender dos seus parâmetros de Indexador. Parâmetros de indexação são configurados no lado direito da tábua, ou ao entrar no perfil de um Indexador e clicar no botão "Delegate" (Delegar).
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 Para aprender mais sobre como tornar-se um Indexador, pode conferir a [documentação oficial](/network/indexing) ou [os guias de Indexador da Graph Academy.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ Para aprender mais sobre como tornar-se um Indexador, pode conferir a [documenta
 
 ### 2. Curadores
 
-Os Curadores analisam subgraphs, para identificar quais são de maior qualidade. Quando um Curador achar um subgraph atraente, ele pode curá-lo com sinais na sua bonding curve. Ao fazê-lo, os Curadores avisam aos Indexadores quais subgraphs têm qualidade alta e merecem ser indexados.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Os Curadores podem ser membros da comunidade, consumidores de dados, ou até mesmo programadores de subgraphs que sinalizam os seus próprios subgraphs com depósitos de tokens GRT em uma bonding curve. Ao depositar GRT, os Curadores cunham ações de curadoria em um subgraph. Como resultado, os Curadores têm direito a uma porção das taxas de consulta geradas pelo subgraph que sinalizaram. A bonding curve incentiva os Curadores a curar as fontes de dado de maior qualidade. A tábua de Curadoria nesta seção lhe mostrará:
+In the The Curator table listed below you can see:
 
 - A data em que o Curador começou a curar
 - O número de GRT depositado
@@ -68,34 +92,36 @@ Os Curadores podem ser membros da comunidade, consumidores de dados, ou até mes
 
 ![Imagem do Explorer 6](/img/Curation-Overview.png)
 
-Se quiser saber mais sobre o papel de Curador, pode visitar os seguintes atalhos, da [Graph Academy](https://thegraph.academy/curators/) ou [da documentação oficial.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegantes
 
-Os Delegantes têm um papel importante em manter a segurança e descentralização da Graph Network. Eles participam na rede com a delegação (por ex., "staking") de tokens GRT a um ou vários indexadores. Sem Delegantes, os Indexadores têm menos chances de atrair recompensas e taxas significativas. Então, os Indexadores procuram atrair Delegantes ao oferecê-los uma porção das recompensas de indexação e das taxas de query que ganham.
+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.
 
-Os Delegantes, por sua vez, selecionam Indexadores com base em um número de variáveis diferentes, como desempenho passado, recompensas de indexação, e porções de taxas de query. A reputação dentro da comunidade também importa! Vale a pena conectar-se com os indexadores selecionados através do [Discord](https://discord.gg/graphprotocol) ou do [Fórum](https://forum.thegraph.com/) do The Graph!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![Imagem do Explorer 7](/img/Delegation-Overview.png)
 
-A tábua de Delegantes permitirá-lhe ver os Delegantes ativos na comunidade, assim como métricas que incluem:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - O número de Indexadores aos quais um Delegante delega
 - A delegação original de um Delegante
 - As recompensas que acumularam, mas não sacaram, do protocolo
 - As recompensas realizadas que sacaram do protocolo
 - A quantidade total de GRT que têm no protocolo no momento
-- A última data em que delegaram
+- The date they last delegated
 
-Caso queira aprender mais sobre como tornar-se um Delegado, é só ir à [documentação oficial](/network/delegating) ou à [Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Rede
 
-Na seção de Rede, verá KPIs globais e poderá trocar para uma base por-epoch e analisar métricas de rede em mais detalhes. Estes detalhes darão-lhe uma ideia de como a rede se desempenha com o tempo.
+In this section, you can see global KPIs and view 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
+### Visão geral
 
-A secção de resumo tem todas as estatísticas atuais da rede, além de estatísticas cumulativas temporais. Aqui, poderá ver coisas como:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - O stake total atual da rede
 - O stake dividido entre os Indexadores e os seus Delegantes
@@ -104,10 +130,10 @@ A secção de resumo tem todas as estatísticas atuais da rede, além de estatí
 - Parâmetros de protocolo como recompensas de curadoria, ritmo de inflação, e mais
 - Recompensas e taxas na epoch atual
 
-Vale mencionar alguns detalhes importantes:
+A few key details to note:
 
-- **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 conseguiram da emissão da rede durante a epoch.** Apesar da emissão do protocolo ser fixa, as recompensas só são cunhadas 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, Indexers podem ter coletivamente fechado alocações que estavam abertas por muitos dias).
+- **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).
 
 ![Imagem do Explorer 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ Na seção de Epochs, pode analisar, numa base por epoch, métricas como:
   - A epoch ativa é aquela em que os Indexadores atualmente alocam stake e colecionam taxas de query
   - As epochs de estabelecimento são aquelas em que os canais de estado são estabelecidos. Portanto, os Indexadores são sujeitos a cortes caso os consumidores abram disputas contra eles.
   - 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 consulta para serem reivindicadas pelos Indexadores; assim, finalizadas.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Imagem do Explorer 9](/img/Epoch-Stats.png)
 
 ## Seu Perfil de Utilizador
 
-Agora que já falamos sobre as estatísticas da rede, vamos para o seu perfil pessoal. Este é o seu lugar para ver 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, poderá ver:
+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:
 
 ### Resumo do Perfil
 
-Aqui, pode ver quaisquer ações atuais que tomou; também é onde pode achar as suas informações do perfil, sua descrição, e o seu ‘website’ (se tiver adicionado um).
+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).
 
 ![Imagem do Explorer 10](/img/Profile-Overview.png)
 
 ### Aba de Subgraphs
 
-Se clicar na aba de Subgraphs, verá os seus subgraphs publicados. Isto não incluirá nenhum subgraph lançado com a CLI para fins de teste — os subgraphs só aparecerão após serem editados à rede descentralizada.
+In the Subgraphs tab, you’ll see 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.
 
 ![Imagem do Explorer 11](/img/Subgraphs-Overview.png)
 
 ### Aba de Indexação
 
-Se clicar na aba de Indexação, verá uma tábua com todas as alocações ativas e históricas aos subgraphs, além de gráficos para analisar e ver o seu desempenho passado como um Indexador.
+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.
 
 Esta secção também incluirá detalhes sobre as suas recompensas de Indexador e taxas de consulta. Verá as seguintes métricas:
 
@@ -158,7 +189,9 @@ Esta secção também incluirá detalhes sobre as suas recompensas de Indexador
 
 ### Aba de Delegação
 
-Os delegantes são importantes para a Graph Network. Um Delegador deve usar o seu conhecimento para escolher um Indexador que proverá um retorno saudável em recompensas. Aqui, pode achar detalhes das suas delegações ativas e históricas, além das métricas dos Indexadores aos quais delegou.
+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.
 
 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.
 

From 334629997598b9adb3e4474e9848be09f74bdbec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:56 -0500
Subject: [PATCH 0764/1325] New translations explorer.mdx (Swedish)

---
 website/pages/sv/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/sv/network/explorer.mdx b/website/pages/sv/network/explorer.mdx
index 41315fc0ab51..1d8facb1b4a8 100644
--- a/website/pages/sv/network/explorer.mdx
+++ b/website/pages/sv/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graf Utforskaren
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraffar
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Utforskaren Bild 1](/img/Subgraphs-Explorer-Landing.png)
 
-När du klickar in på en subgraff kan du testa frågor i lekplatsen och använda nätverksinformation för att fatta informerade beslut. Du kommer också att kunna signalera GRT på din egen subgraff eller andra subgraffar för att göra indexerare medvetna om dess vikt och kvalitet. Detta är avgörande eftersom signalering på en subgraff uppmuntrar den att indexeras, vilket innebär att den kommer att synas på nätverket för att så småningom utföra frågor.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Utforskaren Bild 2](/img/Subgraph-Details.png)
 
-På varje dedikerad sida för subgraff visas flera detaljer, inklusive:
+On each subgraph’s dedicated page, you can do the following:
 
 - Signalera/Sluta signalera på subgraffar
 - Visa mer detaljer som diagram, aktuell distributions-ID och annan metadata
@@ -31,26 +45,32 @@ På varje dedikerad sida för subgraff visas flera detaljer, inklusive:
 
 ## Deltagare
 
-Inom den här fliken får du en översikt över alla personer som deltar i nätverksaktiviteter, såsom indexerare, delegater och kuratorer. Nedan går vi igenom vad varje flik innebär för dig.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexerare
 
 ![Utforskaren Bild 4](/img/Indexer-Pane.png)
 
-Låt oss börja med indexerare. Indexerare är ryggraden i protokollet och de satsar på subgraffar, indexerar dem och serverar frågor till alla som konsumerar subgraffar. I indexerarens tabell kan du se indexerarens delegeringsparametrar, deras insats, hur mycket de har satsat på varje subgraff och hur mycket intäkter de har tjänat på frågeavgifter och indexeringsbelöningar. Här är några detaljer:
+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.
 
-- Andel av frågeavgift - den % av frågeavgifterna som indexeraren behåller när de delar med delegater
-- Effektiv belöningsandel - belöningsandelen för indexeringsbelöning som tillämpas på delegeringspoolen. Om den är negativ innebär det att indexeraren ger bort en del av sina belöningar. Om den är positiv innebär det att indexeraren behåller en del av sina belöningar
-- Nedkylningsåterstående - den tid som återstår tills indexeraren kan ändra ovanstående delegeringsparametrar. Nedkylningsperioder ställs upp av indexerare när de uppdaterar sina delegeringsparametrar
-- Ägd - Detta är indexerarens deponerade insats, som kan straffas för skadligt eller felaktigt beteende
-- Delegerad - Insats från delegater som kan tilldelas av indexeraren, men som inte kan straffas
-- Tilldelad - Insats som indexerare aktivt tilldelar till de subgraffar de indexerar
-- Tillgänglig delegeringskapacitet - mängden delegerad insats som indexerare fortfarande kan ta emot innan de blir överdelegerade
+**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.
-- Frågeavgifter - detta är de totala avgifter som slutanvändare har betalat för frågor från en indexerare över tid
+- 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.
 
-Indexerare kan tjäna både frågeavgifter och indexeringsbelöningar. Funktionellt sker detta när nätverksdeltagare delegerar GRT till en indexerare. Detta gör att indexerare kan få frågeavgifter och belöningar beroende på deras indexeringsparametrar. Indexeringsparametrar ställs in genom att klicka på höger sida av tabellen eller genom att gå in på indexerarens profil och klicka på "Delegera"-knappen.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 För att lära dig mer om hur du blir indexerare kan du titta på [officiell dokumentation](/Nätverk/indexing) eller [The Graf Academy Indexer-guiden.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ För att lära dig mer om hur du blir indexerare kan du titta på [officiell dok
 
 ### 2. Kuratorer
 
-Kuratorer analyserar subgraffar för att identifiera vilka subgraffar som har högst kvalitet. När en kurator har hittat en potentiellt attraktiv subgraff kan de kurera den genom att signalera på dess bindningskurva. På så sätt låter kuratorer indexerare veta vilka subgraffar som är av hög kvalitet och bör indexerad.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Kuratorer kan vara samhällsmedlemmar, datakonsumenter eller till och med subgraffutvecklare som signalerar på sina egna subgraffar genom att deponera GRT-token i en bindningskurva. Genom att deponera GRT skapar kuratorer kuratorandelar av en subgraff. Som ett resultat är kuratorer berättigade att tjäna en del av frågeavgifterna som subgraffen de har signalerat på genererar. Bindningskurvan uppmuntrar kuratorer att kurera de högsta kvalitetsdatakällorna. Kuratortabellen i detta avsnitt låter dig se:
+In the The Curator table listed below you can see:
 
 - Datumet då kuratorn började kurera
 - Antalet GRT som deponerades
@@ -68,34 +92,36 @@ Kuratorer kan vara samhällsmedlemmar, datakonsumenter eller till och med subgra
 
 ![Utforskaren Bild 6](/img/Curation-Overview.png)
 
-Om du vill lära dig mer om rollen som kurator kan du göra det genom att besöka följande länkar från [The Graph Academy](https://thegraph.academy/curators/) eller [officiell dokumentation.](/Nätverk/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegater
 
-Delegater spelar en nyckelroll för att upprätthålla säkerheten och decentraliseringen av The Graph Nätverk. De deltar i nätverket genom att delegera (det vill säga "satsa") GRT-tokens till en eller flera indexerare. Utan delegater är det mindre sannolikt att indexerare tjänar betydande belöningar och avgifter. Därför försöker indexerare locka delegater genom att erbjuda dem en del av indexeringsbelöningarna och frågeavgifterna de tjänar.
+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.
 
-Delegater väljer i sin tur Indexers baserat på ett antal olika variabler, såsom tidigare prestanda, belöningsräntor för indexering och andel av frågeavgifter. Rekommendation inom gemenskapen kan också spela en roll i detta! Det rekommenderas att ansluta med de indexers som valts via [The Graph's Discord](https://discord.gg/graphprotocol) eller [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![Utforskaren Bild 7](/img/Delegation-Overview.png)
 
-Delegattabellen kommer att låta dig se aktiva delegater i samhället, samt metriker som:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Antal indexerare en delegat delegerar till
 - En delegats ursprungliga delegation
 - Belöningar de har ackumulerat men inte har dragit tillbaka från protokollet
 - De realiserade belöningarna de drog tillbaka från protokollet
 - Totalt belopp av GRT som de för närvarande har i protokollet
-- Datumet då de senast delegerade
+- The date they last delegated
 
-Om du vill lära dig mer om hur du blir delegat, behöver du inte leta längre! Allt du behöver göra är att besöka [officiell dokumentation](/Nätverk/delegating) eller [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Nätverk
 
-I avsnittet Nätverk kommer du att se globala KPI:er samt möjligheten att växla till en per-epok-basis och analysera nätverksmetriker mer detaljerat. Dessa detaljer ger dig en uppfattning om hur nätverket presterar över tiden.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - Nuvarande totala nätverksinsats
 - Insatsen fördelad mellan indexerare och deras delegater
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protokollparametrar såsom kuratorbelöning, inflationstakt och mer
 - Nuvarande epokbelöningar och avgifter
 
-Några viktiga detaljer som är värda att nämna:
+A few key details to note:
 
-- **Frågeavgifter representerar avgifterna som genereras av användarna**, och de kan krävas (eller inte) av indexerare efter en period på minst 7 epoker (se nedan) efter att deras tilldelningar till subgraffar har avslutats och den data de serverat har validerats av användarna.
-- **Indexeringsbelöningar representerar mängden belöningar som indexerare har krävt från nätverksutgivningen under epoken.** Även om protokollutgivningen är fast, genereras belöningarna endast när indexerare stänger sina tilldelningar till subgraffar som de har indexerat. Därför varierar antalet belöningar per epok (det vill säga under vissa epoker kan indexerare sammanlagt stänga tilldelningar som har varit öppna i många dagar).
+- **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).
 
 ![Utforskaren Bild 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ I avsnittet Epoker kan du analysera på en per-epok-basis, metriker som:
   - Den aktiva epoken är den där indexerare för närvarande allokerar insats och samlar frågeavgifter
   - De avvecklande epokerna är de där statliga kanaler avvecklas. Detta innebär att indexerare är föremål för straff om användarna öppnar tvister mot dem.
   - De distribuerande epokerna är de epoker där statliga kanaler för epokerna avvecklas och indexerare kan kräva sina frågeavgiftsrabatter.
-  - De avslutade epokerna är de epoker som inte har några frågeavgiftsrabatter kvar att kräva av indexerare, och är därmed avslutade.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![Utforskaren Bild 9](/img/Epoch-Stats.png)
 
 ## Din användarprofil
 
-Nu när vi har pratat om nätverksstatistik, låt oss gå vidare till din personliga profil. Din personliga profil är platsen där du kan se din nätverksaktivitet, oavsett hur du deltar i nätverket. Din kryptoplånbok kommer att fungera som din användarprofil, och med Användardashboarden kan du se:
+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:
 
 ### Profilöversikt
 
-Här kan du se de senaste åtgärder du har vidtagit. Detta är också där du hittar din profilinformation, beskrivning och webbplats (om du har lagt till en).
+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).
 
 ![Utforskaren Bild 10](/img/Profile-Overview.png)
 
 ### Subgraffar-fliken
 
-Om du klickar på Subgraffar-fliken ser du dina publicerade subgraffar. Detta inkluderar inte några subgraffar som distribuerats med CLI för teständamål - subgraffar kommer bara att visas när de publiceras på det decentraliserade nätverket.
+In the Subgraphs tab, you’ll see 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.
 
 ![Utforskaren Bild 11](/img/Subgraphs-Overview.png)
 
 ### Indexeringstabell
 
-Om du klickar på Indexeringsfliken hittar du en tabell med alla aktiva och historiska tilldelningar till subgraffar, samt diagram som du kan analysera och se din tidigare prestanda som indexerare.
+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.
 
 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:
 
@@ -158,7 +189,9 @@ I det här avsnittet hittar du också information om dina nettobelöningar som i
 
 ### Delegattabell
 
-Delegater är viktiga för The Graph Nätverk. En delegat måste använda sin kunskap för att välja en indexerare som kommer att ge en hälsosam avkastning på belöningar. Här hittar du detaljer om dina aktiva och historiska delegationer, samt metriker för indexerare som du har delegerat till.
+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.
 
 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.
 

From 571efc0e476205bd31a35f7662722339aaab3567 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:57 -0500
Subject: [PATCH 0765/1325] New translations explorer.mdx (Ukrainian)

---
 website/pages/uk/network/explorer.mdx | 103 +++++++++++++++++---------
 1 file changed, 68 insertions(+), 35 deletions(-)

diff --git a/website/pages/uk/network/explorer.mdx b/website/pages/uk/network/explorer.mdx
index 9d8fa4ed8a8a..1246158a97f3 100644
--- a/website/pages/uk/network/explorer.mdx
+++ b/website/pages/uk/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Підграфи
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-Коли ви натискаєте на підграфа, ви зможете тестувати подачу запитів в дослідницькому просторі та зможете використовувати отримувані дані для прийняття обґрунтованих рішень. Ви також можете подати сигнал за допомогою GRT токенів на свій власний підграф або на підграфи інших, щоб індексатори знали про його цінність і якість певного підграфа. Це дуже важливо, тому що сигналізація підграфа стимулює його індексацію, а це означає, що він з'явиться в мережі, щоб в кінцевому підсумку обслуговувати запити.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-На спеціальній сторінці присвяченій кожному підграфу, висвітлюється декілька важливих відомостей. До них відносяться:
+On each subgraph’s dedicated page, you can do the following:
 
 - Наявність/відсутність сигналу на підграфах
 - Перегляд додаткових відомостей, таких як діаграми, поточний ID розгортання та інші ключові параметри
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## Учасники
 
-На цій вкладці ви зможете побачити з висоти пташиного польоту всіх користувачів, які беруть участь у діяльності мережі, таких як індексатори, делегати та куратори. Нижче ми детально розглянемо, що кожна вкладка означає для вас.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Індексатори
 
 ![Explorer Image 4](/img/Indexer-Pane.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.
 
-- 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
+**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
+- 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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 2. Curators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve. By depositing GRT, Curators mint curation shares of a subgraph. As a result, Curators are eligible to earn a portion of the query fees that the subgraph they have signaled on generates. The bonding curve incentivizes Curators to curate the highest quality data sources. The Curator table in this section will allow you to see:
+In the The Curator table listed below you can see:
 
 - The date the Curator started curating
 - The number of GRT that was deposited
@@ -68,34 +92,36 @@ Curators can be community members, data consumers, or even subgraph developers w
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. 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. Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers seek to attract Delegators by offering them a portion of the indexing rewards and query fees that they earn.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-The Delegators table will allow you to see the active Delegators in the community, as well as metrics such as:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - The number of Indexers a Delegator is delegating towards
 - A Delegator’s original delegation
 - The rewards they have accumulated but have not withdrawn from the protocol
 - The realized rewards they withdrew from the protocol
 - Total amount of GRT they have currently in the protocol
-- The date they last delegated at
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-In the Network section, you will see global KPIs as well as 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.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - The current total network stake
 - The stake split between the Indexers and their Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocol parameters such as curation reward, inflation rate, and more
 - Current epoch rewards and fees
 
-A few key details that are worth mentioning:
+A few key details to note:
 
-- **Query fees represent the fees generated by the consumers**, and 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 the Indexers close their allocations towards the subgraphs they’ve been indexing. Thus the per-epoch number of rewards varies (ie. during some epochs, Indexers might’ve collectively closed allocations that have been open for many days).
+- **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)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - The active epoch is the one in which Indexers are currently allocating stake and collecting query fees
   - The settling epochs are the ones in which the state channels are being settled. This means that the Indexers are subject to slashing if the consumers open disputes against them.
   - 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, thus being finalized.
+  - 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)
 
 ## Your User Profile
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### Profile Overview
 
-This is where you can see any current actions you took. This is also where you can find your profile information, description, and website (if you added one).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Subgraphs Tab
 
-If you click into the Subgraphs tab, you’ll see 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.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Indexing Tab
 
-If you click into the Indexing tab, you’ll find a table with all the active and historical allocations towards the subgraphs, as well as charts that you can analyze and see your past performance as an Indexer.
+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.
 
 This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics:
 
@@ -158,7 +189,9 @@ This section will also include details about your net Indexer rewards and net qu
 
 ### Delegating Tab
 
-Delegators are important to the Graph Network. A Delegator must use their knowledge to choose an Indexer that will provide a healthy return on rewards. Here you can find details of your active and historical delegations, along with the metrics of the Indexers that you delegated towards.
+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.
 
 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.
 

From 1ae7fc4e4ef1f40f7d0b3df91a28446c190967fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:45:58 -0500
Subject: [PATCH 0766/1325] New translations explorer.mdx (Chinese Simplified)

---
 website/pages/zh/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/zh/network/explorer.mdx b/website/pages/zh/network/explorer.mdx
index 2701151c884a..1c080a696a81 100644
--- a/website/pages/zh/network/explorer.mdx
+++ b/website/pages/zh/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph浏览器
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## 子图
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-当您单击子图时，您将能够在面板上测试查询，并能够利用网络详细信息做出明智决策。 您还可以在自己的子图或其他人的子图中发出 GRT 信号，以使索引人意识到其重要性和质量。 这很关键，因为子图上的信号会激励它被索引，这意味着它将出现在网络上，最终为查询提供服务。
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![资源管理器图像 2](/img/Subgraph-Details.png)
 
-在每个子图的专用页面上，会显示一些详细信息。 包括：
+On each subgraph’s dedicated page, you can do the following:
 
 - 子图上的信号/非信号
 - 查看详细信息，例如图表、当前部署 ID 和其他元数据
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## 参与者
 
-在此选项卡中，您可以鸟瞰所有参与网络活动的人员，例如索引人、委托人和策展人。 下面，我们将深入了解每个选项卡的意义。
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. 索引人
 
 ![资源管理器图片 4](/img/Indexer-Pane.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.
 
-- 查询费用划分 - 索引人与委托人划分查询费用的百分比
-- 有效的奖励划分 - 应用于委托池的索引奖励削减。 如果是负数，则意味着索引人正在赠送部分奖励。 如果是正数，则意味着索引人保留了他们的一些奖励
-- 冷却时间剩余 - 索引人可以更改上述委托参数之前的剩余时间。 冷却时间由索引人在更新委托参数时设置
-- 已拥有 - 索引人的存入份额，可能会因恶意或不正确的行为被削减
-- 已委托 - 委托人的份额可以由索引人分配，但不能被削减
-- 已分配 - 索引人积极分配给他们正在索引的子图
-- 可用委托容量 - 索引人在过度委托之前仍然可以收到的委托数量
+**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 发行支付。
 
-索引人可以获得查询费用和索引奖励。 从功能上讲，当网络参与者将 GRT 委托给索引人时，就会发生这种情况。 这使索引人能够根据其索引参数接收查询费用和奖励。 索引参数可以通过点击表格的右侧来设置，或者通过进入索引人的配置文件并点击“委托”按钮来设置。
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 要了解有关如何成为 Indexer 的更多信息，您可以查看[官方文档](/network/indexing) 或 [Graph Academy 索引器指南。](https://thegraph.academy/delegators/选择索引器/)
 
@@ -58,9 +78,13 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ### 2. 策展人
 
-策展人分析子图以确定哪些子图质量最高。 一旦策展人发现一个潜在有吸引力的子图，他们就可以通过在其粘合曲线上发出信号来设计。 在这样做时，策展人让索引人知道哪些子图是高质量的且应该被索引。
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-策展人可以是社区成员、数据消费者，甚至是子图开发者，他们通过将 GRT 代币放入粘合曲线来在自己的子图上发出信号。 通过存入 GRT，策展人铸造了子图的份额。 因此，策展人有资格获得他们发出信号的子图生成的一部分查询费用。 粘合曲线激励策展人设计最高质量的数据源。 本节中的策展人表将允许查看：
+In the The Curator table listed below you can see:
 
 - 策展人开始策展的日期
 - 已存入的 GRT 数量
@@ -68,34 +92,36 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ![资源管理器图片 6](/img/Curation-Overview.png)
 
-如果你想了解更多关于策展人的角色，可以访问 [Graph学院](https://thegraph.academy/curators/) 或[正式文档](/network/curating)。
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. 委托人
 
-委托人在维护 The Graph 网络的安全性和去中心化方面发挥着关键作用。 他们通过将 GRT 代币委托给一个或多个索引人（即“质押”）来参与网络。 如果没有委托人，索引人不太可能获得可观的奖励和费用。 因此，索引人试图通过向委托人提供他们获得的一部分索引奖励和查询费用来吸引委托人。
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![资源管理器图像 7](/img/Delegation-Overview.png)
 
-委托人表将允许您查看社区中的活跃委托人，以及以下指标：
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - 委托人委托给的索引人数量
 - 委托人的原始委托
 - 协议中已经产生但没有提现的奖励
 - 从协议中提取的已实现奖励
 - 目前在协议中的 GRT 总量
-- 上次授权的日期
+- The date they last delegated
 
-如果您想了解更多有关如何成为委托人的信息，不要犹豫！ 您可以前往 [正式文档](/network/delegating) 或者 [Graph学院](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## 网络
 
-在网络部分，您将看到全局 KPI 以及切换到每个时期的基础和更详细地分析网络指标的能力。 这些详细信息将让您了解网络随时间推移的表现。
+In this section, you can see global KPIs and view 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.
 
 ### 概述
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - 当前网络总份额
 - 索引人和他们的委托人之间的份额分配
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - 协议参数，例如管理奖励、通货膨胀率等
 - 当前时期奖励和费用
 
-一些值得一提的关键细节：
+A few key details to note:
 
-- **查询费用代表消费者产生的费用，**在他们对子图的分配已经关闭并且他们提供的数据已经被关闭后，在至少 7 个周期（见下文）之后，索引人可以要求（或不要求）它们得到消费者的认可。
-- **索引奖励表示索引器在该纪元内从网络发行中获得的奖励数额。**虽然协议发行是固定的，但只有在索引器关闭分配后才会产生奖励他们一直在索引的子图。因此，每个时期的奖励数量会有所不同（即，在某些时期，索引器可能会集体关闭已经开放很多天的分配）。
+- **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).
 
 ![资源管理器图像 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ The overview section has all the current network metrics as well as some cumulat
   - 活跃时期是索引人目前正在分配权益并收取查询费用的时期
   - 稳定时期是状态通道正在稳定的时期。 这意味着如果消费者对他们提出争议，索引人将受到严厉惩罚。
   - 分发时期是时期的状态通道正在结算的时期，索引人可以要求他们的查询费用回扣。
-  - 最终确定的时期是索引人没有留下查询费回扣的时期，因此被最终确定。
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![资源管理器图像 9](/img/Epoch-Stats.png)
 
 ## 您的用户资料
 
-既然我们已经讨论了网络统计信息，让我们继续讨论您的个人资料。 无论您以何种方式参与网络，您的个人资料都是您查看网络活动的地方。 您的加密钱包将作为您的用户资料，通过用户仪表板，您将能够看到：
+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:
 
 ### 个人资料概览
 
-您可以在此处查看您当前采取的任何操作。 您也可以在这里找到您的个人资料信息、描述和网站（如果您添加了）。
+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).
 
 ![资源管理器图像 10](/img/Profile-Overview.png)
 
 ### 子图标签
 
-如果单击子图选项卡，您将看到已发布的子图。 这将不包括为测试目的使用 CLI 部署的任何子图——子图只会在它们发布到去中心化网络时显示。
+In the Subgraphs tab, you’ll see 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.
 
 ![资源管理器图像 11](/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.
 
 本节还将包括有关您的净索引人奖励和净查询费用的详细信息。 您将看到以下指标：
 
@@ -158,7 +189,9 @@ The overview section has all the current network metrics as well as some cumulat
 
 ### 委托标签
 
-委托人对Graph 网络很重要。 委托人必须利用他们的知识来选择能够提供健康回报的索引人。 在这里，您可以找到您的活动和历史委托的详细信息，以及您委托给的索引人的指标。
+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.
 
 在页面的前半部分，您可以看到您的委托图表，以及仅奖励图表。 在左侧，您可以看到反映您当前委托指标的 KPI。
 

From b8f3ab16cd9a9db70147a1667cbe8333ac495b31 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:00 -0500
Subject: [PATCH 0767/1325] New translations explorer.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/ur/network/explorer.mdx b/website/pages/ur/network/explorer.mdx
index 09a259db5d50..15559398fc2e 100644
--- a/website/pages/ur/network/explorer.mdx
+++ b/website/pages/ur/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: گراف ایکسپلورر
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## سب گراف
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![ایکسپلورر امیج 1](/img/Subgraphs-Explorer-Landing.png)
 
-جب آپ سب گراف پر کلک کرتے ہیں، آپ پلے گراؤنڈ میں سوالات کی جانچ کر سکیں گے اور باخبر فیصلے کرنے کے لیے نیٹ ورک کی تفصیلات سے فائدہ اٹھا سکیں گے۔ آپ انڈیکسرز کو اس کی اہمیت اور معیار سے آگاہ کرنے کے لیے اپنے اپنے سب گراف یا دوسروں کے سب گراف پر بھی GRT کا اشارہ دے سکیں گے۔ یہ بہت اہم ہے کیونکہ سب گراف پر سگنلنگ اسے انڈیکس کرنے کی ترغیب دیتا ہے، جس کا مطلب ہے کہ یہ آخر کار سوالات کو پورا کرنے کے لیے نیٹ ورک پر ظاہر ہوگا.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![ایکسپلورر امیج 2](/img/Subgraph-Details.png)
 
-ہر سب گراف کے سرشار صفحے پر، کئی تفصیلات منظر عام پر آتی ہیں. یہ شامل ہیں:
+On each subgraph’s dedicated page, you can do the following:
 
 - سب گرافس پر سگنل/غیر سگنل
 - مزید تفصیلات دیکھیں جیسے چارٹس، موجودہ تعیناتی ID، اور دیگر میٹا ڈیٹا
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## امیدوار
 
-اس ٹیب کے اندر، آپ کو ان تمام لوگوں کا پرندوں کا نظارہ ملے گا جو نیٹ ورک کی سرگرمیوں میں حصہ لے رہے ہیں۔ جیسے انڈیکسرز، ڈیلیگیٹرز اور کیوریٹرز۔ ذیل میں، ہم اس بات کا گہرائی سے جائزہ لیں گے کہ آپ کے لیے ہر ٹیب کا کیا مطلب ہے.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### انڈیکسرز
 
 ![ایکسپلورر امیج 4](/img/Indexer-Pane.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.
 
-- کیوری کی فیس کٹوتی - استفسار کی فیس کی چھوٹ جو انڈیکسر ڈیلیگیٹرز کے ساتھ تقسیم کرتے وقت رکھتا ہے
-- مؤثر انعام کٹوتی - انڈیکسنگ انعام کٹوتی ڈیلیگیشن پول پر لاگو ہوتی ہے. اگر یہ منفی ہے، تو اس کا مطلب ہے کہ انڈیکسر اپنے انعامات کا کچھ حصہ دے رہا ہے۔ اگر یہ مثبت ہے، تو اس کا مطلب ہے کہ انڈیکسر اپنے کچھ انعامات رکھ رہا ہے
-- کولڈاؤن باقی ہے - باقی وقت جب تک کہ انڈیکسر مذکورہ بالا ڈیلیگیشن پیرامیٹرز کو تبدیل نہیں کر سکتا۔ انڈیکسرز جب اپنے ڈیلیگیشن پیرامیٹرز کو اپ ڈیٹ کرتے ہیں تو کولڈاؤن پیریڈز ترتیب دیے جاتے ہیں
-- ملکیت - یہ انڈیکسر کا جمع کردہ حصہ ہے، جسے بدنیتی پر مبنی یا غلط رویے کی وجہ سے کم کیا جا سکتا ہے
-- ڈیلیگیٹڈ - ڈیلیگیٹرز کی طرف سے حصہ جو انڈیکسر کے ذریعہ مختص کیا جاسکتا ہے، لیکن اسے کم نہیں کیا جاسکتا
-- مختص - اس بات کا دعویٰ کریں کہ انڈیکسرز ان سب گرافس کے لیے فعال طور پر مختص کر رہے ہیں جن کی وہ انڈیکس کر رہے ہیں
-- دستیاب ڈیلیگیشن کی صلاحیت - ڈیلیگیٹ حصص کی وہ مقدار جو انڈیکسرز کو زیادہ ڈیلیگیٹ ہونے سے پہلے بھی مل سکتی ہے
+**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 کے اجراء کے ذریعے ادا کیے جاتے ہیں.
 
-انڈیکسر کیوری کی فیس اور انڈیکسر انعامات دونوں حاصل کر سکتے ہیں. عملی طور پر، ایسا اس وقت ہوتا ہے جب نیٹ ورک کے شرکاء GRT انڈیکسر کو ڈیلیگیٹ کرتے ہیں۔ یہ انڈیکسرز کو ان کے انڈیکسر پیرامیٹرز کے لحاظ سے کیوری کی فیس اور انعامات وصول کرنے کے قابل بناتا ہے۔انڈیکسنگ پیرامیٹرز ٹیبل کے دائیں جانب کلک کرکے سیٹ کیے جاتے ہیں، یا انڈیکسر کے پروفائل میں جا کر اور "ڈیلیگیٹ" بٹن پر کلک کر کے.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 انڈیکسر بننے کے بارے میں مزید جاننے کے لیے، آپ [آفیشل دستاویزات](/network/indexing) یا [دی گراف اکیڈمی انڈیکسر گائیڈز۔](https://thegraph.academy/delegators/ پر ایک نظر ڈال سکتے ہیں۔ choosing-indexers/)
 
@@ -58,9 +78,13 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ### کیوریٹرز
 
-کیوریٹرز سب گراف کا تجزیہ کرتے ہیں تاکہ یہ شناخت کیا جا سکے کہ کون سے سب گراف اعلیٰ ترین معیار کے ہیں۔ ایک بار جب کیوریٹر کو ممکنہ طور پر پرکشش سب گراف مل گیا، وہ اس کے بانڈنگ وکر پر سگنل دے کر اسے درست کر سکتے ہیں۔ ایسا کرنے سے، کیوریٹرز انڈیکسرز کو بتاتے ہیں کہ کون سے سب گراف اعلیٰ معیار کے ہیں اور ان کی ترتیب ہونی چاہیے.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-کیوریٹر کمیونٹی کے ممبر ہو سکتے ہیں، ڈیٹا صارفین، یا یہاں تک کہ سب گراف ڈویلپرز جو GRT ٹوکن کو بانڈنگ کریو میں جمع کر کے اپنے پلے گراؤنڈ سب گراف پر سگنل دیتے ہیں۔ GRT جمع کر کے، کیوریٹرز ٹکسال ایک سب گراف کے کیوریشن شیئرز۔ نتیجے کے طور پر، کیوریٹرز کیوری فیس کا ایک حصہ حاصل کرنے کے اہل ہوتے ہیں جو انہوں نے جس سب گراف پر اشارہ کیا ہے وہ تیار کرتا ہے۔ بانڈنگ وکر کیوریٹرز کو اعلیٰ ترین کوالٹی ڈیٹا کے ذرائع کو درست کرنے کی ترغیب دیتا ہے۔ اس سیکشن میں کیوریٹر ٹیبل آپ کو یہ دیکھنے کی اجازت دے گا:
+In the The Curator table listed below you can see:
 
 - جس تاریخ کیوریٹر نے کیوریٹنگ شروع کی
 - GRT کا نمبر جو جمع کیا گیا تھا
@@ -68,34 +92,36 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ![ایکسپلورر امیج 6](/img/Curation-Overview.png)
 
-اگر آپ کیوریٹر کے کردار کے بارے میں مزید جاننا چاہتے ہیں، تو آپ [گراف اکیڈمی](https://thegraph.academy/curators/) یا کے درج ذیل لنکس پر جا کر ایسا کر سکتے ہیں۔ [آفیشل دستاویزات۔](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### ڈیلیگیٹرز
 
-ڈیلیگیٹرز گراف نیٹ ورک کی حفاظت اور ڈیسینٹرالائزیشن کو برقرار رکھنے میں کلیدی کردار ادا کرتے ہیں۔ وہ ایک یا ایک سے زیادہ انڈیکسرز کو GRT ٹوکن ڈیلیگیٹ (یعنی "اسٹیک")کر کے نیٹ ورک میں حصہ لیتے ہیں۔ ڈیلیگیٹرز کے بغیر، انڈیکسرز کے لیے اہم انعامات اور فیسیں حاصل کرنے کا امکان کم ہوتا ہے۔ لہٰذا، انڈیکسرز ڈیلیگیٹرزکو انڈیکسنگ کے انعامات اور استفسار کی فیس کا ایک حصہ پیش کرکے اپنی طرف متوجہ کرنے کی کوشش کرتے ہیں جو وہ کماتے ہیں.
+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.
 
-ڈیلیگیٹرز، بدلے میں، متعدد مختلف متغیرات کی بنیاد پر انڈیکسرز کو منتخب کرتے ہیں، جیسے کہ ماضی کی کارکردگی، انڈیکسنگ کے انعام کی شرح، اور کیوری فیس میں کمی۔ کمیونٹی کے اندر ساکھ بھی اس میں اہم کردار ادا کر سکتی ہے! [گراف ڈسکورڈ](https://discord.gg/graphprotocol) یا [گراف فورم](https://forum.thegraph.com/) کے ذریعے منتخب کردہ انڈیکسر کے ساتھ مربوط ہونے کی سفارش کی جاتی ہے!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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/)!
 
 ![ایکسپلورر امیج 7](/img/Delegation-Overview.png)
 
-ڈیلیگیٹرز ٹیبل آپ کو کمیونٹی میں فعال ڈیلیگیٹرز کے ساتھ ساتھ میٹرکس جیسے کہ:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - انڈیکسرز کی تعداد جن کی طرف ایک ڈیلیگیٹر ڈیلیٹ کر رہا ہے
 - ایک ڈیلیگیٹر کی حقیقی ڈیلیگیشن
 - وہ انعامات جو انہوں نے جمع کر لیے ہیں لیکن پروٹوکول سے دستبردار نہیں ہوئے ہیں
 - وہ انعامات جو انہوں نے پروٹوکول سے واپس لے لیے
 - پروٹوکول میں ان کے پاس موجود GRT کی کل رقم
-- جس تاریخ کو انہوں نے آخری بار ڈیلیگیٹ کیا تھا
+- The date they last delegated
 
-اگر آپ ڈیلیگیٹر بننے کے طریقے کے بارے میں مزید جاننا چاہتے ہیں تو مزید نہ دیکھیں! آپ کو صرف یہ کرنا ہے کہ [آفیشل دستاویزات](/network/delegating) یا [گراف اکیڈمی](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) کی طرف جانا ہے۔
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## نیٹ ورک
 
-نیٹ ورک سیکشن میں، آپ عالمی KPIs کے ساتھ ساتھ فی دور کی بنیاد پر سوئچ کرنے اور نیٹ ورک میٹرکس کا مزید تفصیل سے تجزیہ کرنے کی صلاحیت دیکھیں گے۔ یہ تفصیلات آپ کو اس بات کا احساس دلائیں گی کہ نیٹ ورک وقت کے ساتھ کیسا کارکردگی دکھا رہا ہے.
+In this section, you can see global KPIs and view 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.
 
 ### جائزہ
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - موجودہ کل نیٹ ورک کا حصہ
 - انڈیکسرز اور ان کے ڈیلیگیٹرز کے درمیان حصص کی تقسیم
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - پروٹوکول کے پیرامیٹرز جیسے کیوریشن انعام، افراط زر کی شرح، اور مزید
 - موجودہ دور کے انعامات اور فیس
 
-چند اہم تفصیلات جو قابل ذکر ہیں:
+A few key details to note:
 
-- **استفسار کی فیس صارفین کے ذریعہ تیار کردہ فیس کی نمائندگی کرتی ہے**، اور انڈیکسرز کے ذریعہ ان کا دعویٰ کیا جا سکتا ہے (یا نہیں) کم از کم 7 ادوار کی مدت کے بعد (نیچے ملاحظہ کریں) سب گرافس کے لیے ان کے مختص ہونے کے بعد اور صارفین کے ذریعہ ان کے فراہم کردہ ڈیٹا کی توثیق کر دی گئی ہے.
-- **انڈیکس کرنے والے انعامات ان انعامات کی مقدار کی نمائندگی کرتے ہیں جن کا دعویٰ انڈیکسرز کے اپوچ کے دوران نیٹ ورک کے اجراء سے کیا تھا۔** اگرچہ پروٹوکول کا اجراء طے ہے، انعامات صرف اس صورت میں ملتے ہیں جب انڈیکسرز ان سب گرافس کے لیے اپنی مختص رقم کو بند کر دیتے ہیں جو وہ انڈیکس کر رہے ہیں۔ اس طرح انعامات کی فی اپوچ تعداد مختلف ہوتی ہے(یعنی کچھ اپوچس کے دوران، انڈیکسرز نے اجتماعی طور پر بند کر دیے ہوں گے جو کئی دنوں سے کھلے ہوئے ہیں).
+- **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).
 
 ![ایکسپلورر امیج 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ The overview section has all the current network metrics as well as some cumulat
   - فعال ایپوک وہ ہے جس میں انڈیکسرز فی الحال حصص مختص کر رہے ہیں اور کیوری کی فیس جمع کر رہے ہیں
   - طے پانے والے اپوچس وہ ہیں جن میں ریاستی چینلز آباد ہو رہے ہیں۔ اس کا مطلب یہ ہے کہ اگر صارفین ان کے خلاف تنازعات کھولتے ہیں تو انڈیکسرز کو کم کیا جا سکتا ہے.
   - تقسیم کرنے والے اپوچس وہ ایپوکس ہیں جن میں ایپوکس کے لیے ریاستی چینلز طے کیے جا رہے ہیں اور انڈیکسرز اپنی کیوری کی فیس میں چھوٹ کا دعویٰ کر سکتے ہیں.
-  - حتمی شکل کے اپوچس وہ اپوچس ہیں جن میں انڈیکسرز کے ذریعہ دعویٰ کرنے کے لیے کوئی سوال فیس کی چھوٹ باقی نہیں رہتی، اس طرح حتمی شکل دی جاتی ہے.
+  - The finalized epochs are the epochs that have no query fee rebates left to claim by the Indexers.
 
 ![ایکسپلورر امیج 9](/img/Epoch-Stats.png)
 
 ## آپ کا صارف پروفائل
 
-اب جب کہ ہم نیٹ ورک کے اعدادوشمار کے بارے میں بات کر چکے ہیں، آئیے آپ کے ذاتی پروفائل پر چلتے ہیں۔ آپ کا ذاتی پروفائل آپ کے لیے اپنے نیٹ ورک کی سرگرمی دیکھنے کی جگہ ہے، چاہے آپ نیٹ ورک پر کس طرح شرکت کر رہے ہوں۔ آپ کا کریپٹو والیٹ آپ کے صارف پروفائل کے طور پر کام کرے گا، اور یوزر ڈیش بورڈ کے ساتھ، آپ یہ دیکھ سکیں گے:
+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:
 
 ### پروفائل کا جائزہ
 
-یہ وہ جگہ ہے جہاں آپ اپنی موجودہ کارروائیوں کو دیکھ سکتے ہیں. یہی وہ جگہ ہے جہاں آپ اپنی پروفائل کی معلومات، تفصیل، اور ویب سائٹ (اگر آپ نے شامل کی ہے) تلاش کر سکتے ہیں.
+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).
 
 ![ایکسپلورر امیج 10](/img/Profile-Overview.png)
 
 ### سب گرافس ٹیب
 
-اگر آپ سب گرافس ٹیب پر کلک کرتے ہیں، تو آپ کو اپنے شائع شدہ سب گرافس نظر آئیں گے۔ اس میں جانچ کے مقاصد کے لیے CLI کے ساتھ تعینات کوئی بھی سب گرافس شامل نہیں ہوں گے - سب گرافس صرف تب ظاہر ہوں گے جب وہ ڈیسینٹرالائزڈ نیٹ ورک پر شائع کیے جائیں گے.
+In the Subgraphs tab, you’ll see 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.
 
 ![ایکسپلورر امیج 11](/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.
 
 اس حصے میں آپ کے نیٹ انڈیکسر انعامات اور نیٹ استفسار کی فیس کے بارے میں تفصیلات بھی شامل ہوں گی۔ آپ کو درج ذیل میٹرکس نظر آئیں گے:
 
@@ -158,7 +189,9 @@ The overview section has all the current network metrics as well as some cumulat
 
 ### ڈیلگیٹنگ ٹیب
 
-ڈیلیگیٹرز گراف نیٹ ورک کے لیے اہم ہیں۔ ایک ڈیلیگیٹرزکو اپنے علم کا استعمال ایک انڈیکسر منتخب کرنے کے لیے کرنا چاہیے جو انعامات پر صحت مندانہ واپسی فراہم کرے۔ یہاں آپ اپنی فعال اور تاریخی ڈیلیگیشن کی تفصیلات حاصل کرسکتے ہیں، انڈیکسرز کے میٹرکس کے ساتھ جن کی طرف آپ نے ڈیلیگیٹ کیا ہے.
+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.
 
 صفحہ کے پہلے نصف میں، آپ اپنے ڈیلیگیشن چارٹ کے ساتھ ساتھ صرف انعامات کا چارٹ دیکھ سکتے ہیں، بائیں طرف، آپ KPIs دیکھ سکتے ہیں جو آپ کی موجودہ ڈیلیگیشن میٹرکس کی عکاسی کرتے ہیں.
 

From 7febc62078038790120bc9b3cab0e63649699e12 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:01 -0500
Subject: [PATCH 0768/1325] New translations explorer.mdx (Vietnamese)

---
 website/pages/vi/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/vi/network/explorer.mdx b/website/pages/vi/network/explorer.mdx
index f3c441eb0ab1..85dded99b651 100644
--- a/website/pages/vi/network/explorer.mdx
+++ b/website/pages/vi/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Trình khám phá Graph
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-Khi bạn nhấp vào một subgraph, bạn sẽ có thể thử các truy vấn trong playground và có thể tận dụng chi tiết mạng để đưa ra quyết định sáng suốt. Bạn cũng sẽ có thể báo hiệu GRT trên subgraph của riêng bạn hoặc các subgraph của người khác để làm cho các indexer nhận thức được tầm quan trọng và chất lượng của nó. Điều này rất quan trọng vì việc báo hiệu trên một subgraph khuyến khích nó được lập chỉ mục, có nghĩa là nó sẽ xuất hiện trên mạng để cuối cùng phục vụ các truy vấn.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-Trên trang chuyên dụng của mỗi subgraph, một số chi tiết được hiển thị. Bao gồm:
+On each subgraph’s dedicated page, you can do the following:
 
 - Báo hiệu / Hủy báo hiệu trên subgraph
 - 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
@@ -31,26 +45,32 @@ Trên trang chuyên dụng của mỗi subgraph, một số chi tiết được
 
 ## Những người tham gia
 
-Within this tab, you’ll get a bird’s eye view of all the people that are participating in the network activities, such as Indexers, Delegators, and Curators. Below, we’ll go into an in-depth review of what each tab means for you.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Image 4](/img/Indexer-Pane.png)
 
-Hãy bắt đầu với Indexers (Người lập chỉ mục). Các Indexers là xương sống của giao thức, là những người đóng góp vào các subgraph, lập chỉ mục chúng và phục vụ các truy vấn cho bất kỳ ai sử dụng subgraph. Trong bảng Indexers, bạn sẽ có thể thấy các thông số ủy quyền của Indexer, lượng stake của họ, số lượng họ đã stake cho mỗi subgraph và doanh thu mà họ đã kiếm được từ phí truy vấn và phần thưởng indexing. Đi sâu hơn:
+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.
 
-- Phần Cắt Phí Truy vấn - là % hoàn phí truy vấn mà Indexer giữ lại khi ăn chia với Delegators
-- Phần Cắt Thưởng Hiệu quả - phần thưởng indexing được áp dụng cho nhóm ủy quyền (delegation pool). Nếu là âm, điều đó có nghĩa là Indexer đang cho đi một phần phần thưởng của họ. Nếu là dương, điều đó có nghĩa là Indexer đang giữ lại một số phần thưởng của họ
-- Cooldown Remaining (Thời gian chờ còn lại) - thời gian còn lại cho đến khi Indexer có thể thay đổi các thông số ủy quyền ở trên. Thời gian chờ Cooldown được Indexers thiết lập khi họ cập nhật thông số ủy quyền của mình
-- Được sở hữu - Đây là tiền stake Indexer đã nạp vào, có thể bị phạt cắt giảm (slashed) nếu có hành vi độc hại hoặc không chính xác
-- Được ủy quyền - Lượng stake từ các Delegator có thể được Indexer phân bổ, nhưng không thể bị phạt cắt giảm
-- Được phân bổ - phần stake mà Indexers đang tích cực phân bổ cho các subgraph mà họ đang lập chỉ mục
-- Available Delegation Capacity - the amount of delegated stake the Indexers can still receive before they become over-delegated
+**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.
-- Phí Truy vấn - đây là tổng số phí mà người dùng cuối đã trả cho các truy vấn từ Indexer đến hiện tại
+- 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.
 
-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. Indexing parameters are set by clicking on the right-hand side of the table, or by going into an Indexer’s profile and clicking the “Delegate” button.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
 
@@ -58,9 +78,13 @@ To learn more about how to become an Indexer, you can take a look at the [offici
 
 ### 2. Curators
 
-Curators analyze subgraphs to identify which subgraphs are of the highest quality. Once a Curator has found a potentially attractive 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.
+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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-Curators có thể là các thành viên cộng đồng, người tiêu dùng dữ liệu hoặc thậm chí là nhà phát triển subgraph, những người báo hiệu trên subgraph của chính họ bằng cách nạp token GRT vào một đường cong liên kết. Bằng cách nạp GRT, Curator đúc ra cổ phần curation của một subgraph. Kết quả là, Curators có đủ điều kiện để kiếm một phần phí truy vấn mà subgraph mà họ đã báo hiệu tạo ra. Đường cong liên kết khuyến khích Curators quản lý các nguồn dữ liệu chất lượng cao nhất. Bảng Curator trong phần này sẽ cho phép bạn xem:
+In the The Curator table listed below you can see:
 
 - Ngày Curator bắt đầu curate
 - Số GRT đã được nạp
@@ -68,34 +92,36 @@ Curators có thể là các thành viên cộng đồng, người tiêu dùng d
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-If you want to learn more about the Curator role, you can do so by visiting the following links of [The Graph Academy](https://thegraph.academy/curators/) or [official documentation.](/network/curating)
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegators
 
-Delegators (Người Ủy quyền) đóng một vai trò quan trọng trong việc duy trì tính bảo mật và phân quyền của Mạng The Graph. Họ tham gia vào mạng bằng cách ủy quyền (tức là "staking") token GRT cho một hoặc nhiều indexer. Không có những Delegator, các Indexer ít có khả năng kiếm được phần thưởng và phí đáng kể. Do đó, Indexer tìm cách thu hút Delegator bằng cách cung cấp cho họ một phần của phần thưởng lập chỉ mục và phí truy vấn mà họ kiếm được.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-Bảng Delegators sẽ cho phép bạn xem các Delegator đang hoạt động trong cộng đồng, cũng như các chỉ số như:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - Số lượng Indexers mà một Delegator đang ủy quyền cho
 - Ủy quyền ban đầu của Delegator
 - Phần thưởng họ đã tích lũy nhưng chưa rút khỏi giao thức
 - Phần thưởng đã ghi nhận ra mà họ rút khỏi giao thức
 - Tổng lượng GRT mà họ hiện có trong giao thức
-- Ngày họ ủy quyền lần cuối cùng
+- The date they last delegated
 
-If you want to learn more about how to become a Delegator, look no further! All you have to do is to head over to the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Mạng lưới
 
-Trong phần Mạng lưới, bạn sẽ thấy các KPI toàn cầu cũng như khả năng chuyển sang cơ sở từng epoch và phân tích các chỉ số mạng chi tiết hơn. Những chi tiết này sẽ cho bạn biết mạng hoạt động như thế nào theo thời gian.
+In this section, you can see global KPIs and view 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
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - Tổng stake mạng hiện tại
 - Phần chia stake giữa Indexer và các Delegator của họ
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Các thông số giao thức như phần thưởng curation, tỷ lệ lạm phát,...
 - Phần thưởng và phí của epoch hiện tại
 
-Một vài chi tiết quan trọng đáng được đề cập:
+A few key details to note:
 
-- **Phí truy vấn đại diện cho phí do người tiêu dùng tạo ra**, và chúng có thể được Indexer yêu cầu (hoặc không) sau một khoảng thời gian ít nhất 7 epochs (xem bên dưới) sau khi việc phân bổ của họ cho các subgraph đã được đóng lại và dữ liệu mà chúng cung cấp đã được người tiêu dùng xác thực.
-- **Phần thưởng Indexing đại diện cho số phần thưởng mà Indexer đã yêu cầu được từ việc phát hành mạng trong epoch đó.** Mặc dù việc phát hành giao thức đã được cố định, nhưng phần thưởng chỉ nhận được sau khi Indexer đóng phân bổ của họ cho các subgraph mà họ đã lập chỉ mục. Do đó, số lượng phần thưởng theo từng epoch khác nhau (nghĩa là trong một số epoch, Indexer có thể đã đóng chung các phân bổ đã mở trong nhiều ngày).
+- **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)
 
@@ -121,29 +147,34 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
   - Epoch đang hoạt động là epoch mà Indexer hiện đang phân bổ cổ phần và thu phí truy vấn
   - Epoch đang giải quyết là những epoch mà các kênh trạng thái đang được giải quyết. Điều này có nghĩa là Indexers có thể bị phạt cắt giảm nếu người tiêu dùng công khai tranh chấp chống lại họ.
   - 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ọ.
-  - Epoch được hoàn tất là những epoch không còn khoản hoàn phí truy vấn nào để Indexer yêu cầu, do đó sẽ được hoàn thiện.
+  - 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)
 
 ## Hồ sơ Người dùng của bạn
 
-Now that we’ve talked about the network stats, let’s move on to your personal profile. Your personal profile is the place for you to see your network activity, no matter how you’re participating on the network. Your crypto wallet will act as your user profile, and with the User Dashboard, you’ll be able to see:
+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:
 
 ### Tổng quan Hồ sơ
 
-Đây là nơi bạn có thể xem bất kỳ hành động hiện tại nào bạn đã thực hiện. Đây cũng là nơi bạn có thể tìm thấy thông tin hồ sơ, mô tả và trang web của mình (nếu bạn đã thêm).
+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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Tab Subgraphs
 
-Nếu bạn nhấp vào tab Subgraphs, bạn sẽ thấy các subgraph đã xuất bản của mình. Điều này sẽ không bao gồm bất kỳ subgraph nào được triển khai với CLI cho mục đích thử nghiệm - các subgraph sẽ chỉ hiển thị khi chúng được xuất bản lên mạng phi tập trung.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### Tab Indexing
 
-Nếu bạn nhấp vào tab Indexing, bạn sẽ tìm thấy một bảng với tất cả các phân bổ hiện hoạt và lịch sử cho các subgraph, cũng như các biểu đồ mà bạn có thể phân tích và xem hiệu suất trước đây của mình với tư cách là Indexer.
+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.
 
 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:
 
@@ -158,7 +189,9 @@ Phần này cũng sẽ bao gồm thông tin chi tiết về phần thưởng Ind
 
 ### Tab Delegating
 
-Delegator rất quan trọng đối với Mạng The Graph. Một Delegator phải sử dụng kiến thức của họ để chọn một Indexer sẽ mang lại lợi nhuận lành mạnh từ các phần thưởng. Tại đây, bạn có thể tìm thấy thông tin chi tiết về các ủy quyền đang hoạt động và trong lịch sử của mình, cùng với các chỉ số của Indexer mà bạn đã ủy quyền.
+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.
 
 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.
 

From d5b7df61ab2020416de1536e4bd9113bec405137 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:02 -0500
Subject: [PATCH 0769/1325] New translations explorer.mdx (Marathi)

---
 website/pages/mr/network/explorer.mdx | 103 +++++++++++++++++---------
 1 file changed, 68 insertions(+), 35 deletions(-)

diff --git a/website/pages/mr/network/explorer.mdx b/website/pages/mr/network/explorer.mdx
index efbb87aa2820..1bf46de5f24a 100644
--- a/website/pages/mr/network/explorer.mdx
+++ b/website/pages/mr/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## Subgraphs
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
 
 ![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
 
-जेव्हा तुम्ही सबग्राफवर क्लिक करता, तेव्हा तुम्ही खेळाच्या मैदानात प्रश्नांची चाचणी घेण्यास सक्षम व्हाल आणि माहितीपूर्ण निर्णय घेण्यासाठी नेटवर्क तपशीलांचा फायदा घेण्यास सक्षम असाल. इंडेक्सर्सना त्याचे महत्त्व आणि गुणवत्तेची जाणीव करून देण्यासाठी तुम्ही तुमच्या स्वतःच्या सबग्राफवर किंवा इतरांच्या सबग्राफवर GRT सिग्नल करण्यास सक्षम असाल. हे गंभीर आहे कारण सबग्राफवर सिग्नल केल्याने ते अनुक्रमित होण्यासाठी प्रोत्साहन मिळते, याचा अर्थ असा आहे की शेवटी क्वेरी सर्व्ह करण्यासाठी ते नेटवर्कवर येईल.
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
 
 ![Explorer Image 2](/img/Subgraph-Details.png)
 
-On each subgraph’s dedicated page, several details are surfaced. These include:
+On each subgraph’s dedicated page, you can do the following:
 
 - Signal/Un-signal on subgraphs
 - चार्ट, वर्तमान उपयोजन आयडी आणि इतर मेटाडेटा यासारखे अधिक तपशील पहा
@@ -31,26 +45,32 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ## Participants
 
-या टॅबमध्‍ये, इंडेक्सर्स, डेलिगेटर्स आणि क्युरेटर्स यांसारख्या नेटवर्क अ‍ॅक्टिव्हिटीमध्ये भाग घेणाऱ्या सर्व लोकांचे विहंगम दृश्य तुम्हाला मिळेल. खाली, आम्ही प्रत्येक टॅबचा तुमच्यासाठी काय अर्थ होतो याचे सखोल पुनरावलोकन करू.
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
 
 ### 1. Indexers
 
 ![Explorer Image 4](/img/Indexer-Pane.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.
 
-- Query Fee Cut - the % of the query fee rebates that the Indexer keeps when splitting with Delegators
-- प्रभावी रिवॉर्ड कट - इंडेक्सिंग रिवॉर्ड कट डेलिगेशन पूलवर लागू केला जातो. जर ते नकारात्मक असेल, तर याचा अर्थ असा आहे की इंडेक्सर त्यांच्या पुरस्कारांचा काही भाग देत आहे. जर ते सकारात्मक असेल, तर याचा अर्थ असा की इंडेक्सर त्यांचे काही बक्षिसे ठेवत आहे
-- Cooldown Remaining - इंडेक्सर वरील डेलिगेशन पॅरामीटर्स बदलू शकत नाही तोपर्यंत उरलेला वेळ. इंडेक्सर्स जेव्हा त्यांचे डेलिगेशन पॅरामीटर्स अपडेट करतात तेव्हा कूलडाउन पीरियड्स सेट केले जातात
-- 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
-- उपलब्ध डेलिगेशन कॅपॅसिटी - इंडेक्सर्सना जास्त डेलिगेशन होण्याआधीही डेलिगेटेड स्टेकची रक्कम मिळू शकते
+**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 जारी करून दिले जातात.
 
-इंडेक्सर्स क्वेरी फी आणि इंडेक्सिंग रिवॉर्ड दोन्ही मिळवू शकतात. कार्यात्मकपणे, जेव्हा नेटवर्क सहभागी इंडेक्सरला GRT सोपवतात तेव्हा असे घडते. हे इंडेक्सर्सना त्यांच्या इंडेक्सर पॅरामीटर्सवर अवलंबून क्वेरी फी आणि रिवॉर्ड प्राप्त करण्यास सक्षम करते. इंडेक्सिंग पॅरामीटर्स टेबलच्या उजव्या बाजूला क्लिक करून किंवा इंडेक्सरच्या प्रोफाइलमध्ये जाऊन "प्रतिनिधी" बटणावर क्लिक करून सेट केले जातात.
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
 
 इंडेक्सर कसे व्हावे याबद्दल अधिक जाणून घेण्यासाठी, तुम्ही [अधिकृत दस्तऐवज](/network/indexing) किंवा [द ग्राफ अकादमी इंडेक्सर मार्गदर्शक](https://thegraph.academy/delegators/ पाहू शकता choosing-indexers/)
 
@@ -58,9 +78,13 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ### 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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
 
-क्युरेटर समुदाय सदस्य, डेटा ग्राहक किंवा अगदी सबग्राफ डेव्हलपर असू शकतात जे GRT टोकन बाँडिंग वक्रमध्ये जमा करून त्यांच्या स्वतःच्या सबग्राफवर सिग्नल करतात. GRT जमा करून, क्युरेटर्स सबग्राफचे क्युरेशन शेअर्स मिंट करतात. परिणामी, क्युरेटर्स क्वेरी फीचा एक भाग मिळविण्यास पात्र आहेत ज्यावर त्यांनी संकेत दिलेला सबग्राफ व्युत्पन्न करतो. बाँडिंग वक्र क्युरेटर्सना उच्च गुणवत्तेचा डेटा स्रोत तयार करण्यासाठी प्रोत्साहन देते. या विभागातील क्युरेटर टेबल तुम्हाला हे पाहण्याची परवानगी देईल:
+In the The Curator table listed below you can see:
 
 - The date the Curator started curating
 - The number of GRT that was deposited
@@ -68,34 +92,36 @@ On each subgraph’s dedicated page, several details are surfaced. These include
 
 ![Explorer Image 6](/img/Curation-Overview.png)
 
-तुम्हाला क्युरेटरच्या भूमिकेबद्दल अधिक जाणून घ्यायचे असल्यास, तुम्ही [द ग्राफ अकादमी](https://thegraph.academy/curators/) किंवा [अधिकृत दस्तऐवज](/network/curating) च्या खालील लिंक्सला भेट देऊन तसे करू शकता
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. Delegators
 
-द ग्राफ नेटवर्कची सुरक्षा आणि विकेंद्रीकरण राखण्यात प्रतिनिधी महत्त्वाची भूमिका बजावतात. ते एक किंवा एकाधिक इंडेक्सर्सना GRT टोकन्स सोपवून (म्हणजे "स्टेकिंग") नेटवर्कमध्ये सहभागी होतात. प्रतिनिधींशिवाय, इंडेक्सर्सना लक्षणीय बक्षिसे आणि शुल्क मिळण्याची शक्यता कमी असते. म्हणून, इंडेक्सर्स डेलिगेटर्सना इंडेक्सिंग रिवॉर्ड्स आणि त्यांनी कमावलेल्या क्वेरी फीचा एक भाग ऑफर करून त्यांना आकर्षित करण्याचा प्रयत्न करतात.
+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.
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
 
-The Delegators table will allow you to see the active Delegators in the community, as well as metrics such as:
+In the Delegators table you can see the active Delegators in the community and important metrics:
 
 - The number of Indexers a Delegator is delegating towards
 - A Delegator’s original delegation
 - The rewards they have accumulated but have not withdrawn from the protocol
 - The realized rewards they withdrew from the protocol
 - Total amount of GRT they have currently in the protocol
-- The date they last delegated at
+- The date they last delegated
 
-तुम्हाला प्रतिनिधी कसे व्हायचे याबद्दल अधिक जाणून घ्यायचे असल्यास, पुढे पाहू नका! तुम्हाला फक्त वर जावे लागेल[official documentation](/network/delegating) किंवा[आलेख अकादमी](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
 
 ## Network
 
-नेटवर्क विभागात, तुम्हाला जागतिक KPIs तसेच प्रत्येक युगाच्या आधारावर स्विच करण्याची आणि नेटवर्क मेट्रिक्सचे अधिक तपशीलवार विश्लेषण करण्याची क्षमता दिसेल. हे तपशील तुम्हाला कालांतराने नेटवर्क कसे कार्य करत आहे याची जाणीव देईल.
+In this section, you can see global KPIs and view 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.
 
-### सारांश
+### सविश्लेषण
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+The overview section has both all the current network metrics and some cumulative metrics over time:
 
 - The current total network stake
 - The stake split between the Indexers and their Delegators
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - Protocol parameters such as curation reward, inflation rate, and more
 - Current epoch rewards and fees
 
-A few key details that are worth mentioning:
+A few key details to note:
 
-- **क्वेरी फी ग्राहकांद्वारे व्युत्पन्न केलेल्या फीचे प्रतिनिधित्व करतात**, आणि उपग्राफसाठी त्यांचे वाटप बंद झाल्यानंतर किमान 7 युगांच्या कालावधीनंतर (खाली पहा) इंडेक्सर्सद्वारे त्यावर दावा केला जाऊ शकतो (किंवा नाही). आणि त्यांनी दिलेला डेटा ग्राहकांनी प्रमाणित केला आहे.
-- **इंडेक्सिंग रिवॉर्ड्स युगादरम्यान नेटवर्क जारी करण्यापासून निर्देशांककर्त्यांनी दावा केलेल्या पुरस्कारांच्या रकमेचे प्रतिनिधित्व करतात.** जरी प्रोटोकॉल जारी करणे निश्चित केले असले तरी, इंडेक्सर्सने त्यांचे वाटप बंद केल्यावरच बक्षिसे दिली जातात ते अनुक्रमित करत असलेल्या उपग्राफकडे. अशा प्रकारे प्रति-युगातील पुरस्कारांची संख्या बदलते (म्हणजे काही युगांदरम्यान, इंडेक्सर्सने अनेक दिवसांपासून खुले असलेले वाटप एकत्रितपणे बंद केले असावे).
+- **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)
 
@@ -121,29 +147,34 @@ 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)
 
 ## Your User Profile
 
-आता आम्ही नेटवर्क आकडेवारीबद्दल बोललो आहोत, चला तुमच्या वैयक्तिक प्रोफाइलकडे जाऊया. तुमची वैयक्तिक प्रोफाइल ही तुमची नेटवर्क गतिविधी पाहण्याचे ठिकाण आहे, तुम्ही नेटवर्कवर कसे भाग घेत आहात हे महत्त्वाचे नाही. तुमचे क्रिप्टो वॉलेट तुमचे वापरकर्ता प्रोफाइल म्हणून काम करेल आणि वापरकर्ता डॅशबोर्डसह तुम्ही हे पाहू शकाल:
+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:
 
 ### 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).
 
 ![Explorer Image 10](/img/Profile-Overview.png)
 
 ### Subgraphs Tab
 
-तुम्ही सबग्राफ टॅबवर क्लिक केल्यास, तुम्हाला तुमचे प्रकाशित सबग्राफ दिसतील. यामध्ये चाचणीच्या उद्देशांसाठी CLI सोबत तैनात केलेले कोणतेही सबग्राफ समाविष्ट केले जाणार नाहीत - सबग्राफ केवळ विकेंद्रित नेटवर्कवर प्रकाशित केल्यावरच दिसून येतील.
+In the Subgraphs tab, you’ll see 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.
 
 ![Explorer Image 11](/img/Subgraphs-Overview.png)
 
 ### 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.
 
 या विभागात तुमच्या निव्वळ इंडेक्सर रिवॉर्ड्स आणि नेट क्वेरी फीबद्दल तपशील देखील समाविष्ट असतील. तुम्हाला खालील मेट्रिक्स दिसतील:
 
@@ -158,7 +189,9 @@ In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
 
 ### Delegating Tab
 
-आलेख नेटवर्कसाठी प्रतिनिधी महत्वाचे आहेत. एखाद्या प्रतिनिधीने त्यांच्या ज्ञानाचा उपयोग असा इंडेक्सर निवडण्यासाठी केला पाहिजे जो पुरस्कारांवर निरोगी परतावा देईल. येथे तुम्ही तुमच्या सक्रिय आणि ऐतिहासिक प्रतिनिधी मंडळांचे तपशील, निर्देशांकांच्या मेट्रिक्ससह शोधू शकता ज्यांना तुम्ही नियुक्त केले आहे.
+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.
 
 पृष्‍ठाच्या पूर्वार्धात, तुम्‍ही तुमच्‍या डेलिगेशन चार्ट तसेच रिवॉर्ड-ओन्ली चार्ट पाहू शकता. डावीकडे, तुम्ही KPI पाहू शकता जे तुमचे वर्तमान प्रतिनिधीत्व मेट्रिक्स दर्शवतात.
 

From 5d850ef8952067cfd310c4cae18b86e6ac99798a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:03 -0500
Subject: [PATCH 0770/1325] New translations explorer.mdx (Hindi)

---
 website/pages/hi/network/explorer.mdx | 101 +++++++++++++++++---------
 1 file changed, 67 insertions(+), 34 deletions(-)

diff --git a/website/pages/hi/network/explorer.mdx b/website/pages/hi/network/explorer.mdx
index 7732e274ec69..286482ca5268 100644
--- a/website/pages/hi/network/explorer.mdx
+++ b/website/pages/hi/network/explorer.mdx
@@ -2,21 +2,35 @@
 title: Graph Explorer
 ---
 
-Welcome to Graph Explorer, or as we like to call it, your decentralized portal into the world of subgraphs and network data. 👩🏽‍🚀 Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators. For a general overview of Graph Explorer, check out the video below (or keep reading below):
+The Graph Explorer के बारे में जानें और सबग्राफ और नेटवर्क डेटा की दुनिया तक पहुंचें।
+
+Graph Explorer कई भागों में बंटा हुआ है जहां आप अन्य डेवलपर्स, dapp डेवलपर्स, Curators, Indexers और Delegators के साथ बातचीत कर सकते हैं।
+
+## वीडियो गाइड
+
+Graph Explorer का सामान्य अवलोकन करने के लिए, नीचे दिए गए वीडियो को देखें:
 
 <VideoEmbed youtube="u224xf7rEBY" />
 
 ## सबग्राफ
 
-First things first, if you just finished deploying and publishing your subgraph in Subgraph Studio, the Subgraphs tab on the top of the navigation bar is the place to view your own finished subgraphs (and the subgraphs of others) on the decentralized network. Here, you’ll be able to find the exact subgraph you’re looking for based on the date created, signal amount, or name.
+जैसे ही आप Subgraph Studio में अपना subgraph डिप्लॉय और पब्लिश कर लें, नेविगेशन बार के शीर्ष पर स्थित "subgraphs tab” पर क्लिक करें ताकि आप निम्नलिखित तक पहुंच सकें:
+
+- आपके अपने तैयार किए गए subgraphs
+- दूसरों द्वारा प्रकाशित subgraphs
+- आपके पास जिस विशेष subgraph की आवश्यकता है (निर्माण की तारीख, सिग्नल राशि, या नाम के आधार पर)।
 
 ![एक्सप्लोरर छवि 1](/img/Subgraphs-Explorer-Landing.png)
 
-जब आप एक सबग्राफ में क्लिक करते हैं, तो आप खेल के मैदान में प्रश्नों का परीक्षण कर पाएंगे और सूचित निर्णय लेने के लिए नेटवर्क विवरण का लाभ उठाने में सक्षम होंगे। आप अपने खुद के सबग्राफ या दूसरों के सबग्राफ पर जीआरटी का संकेत देने में भी सक्षम होंगे ताकि इंडेक्सर्स को इसके महत्व और गुणवत्ता से अवगत कराया जा सके। यह महत्वपूर्ण है क्योंकि एक सबग्राफ पर संकेतन इसे अनुक्रमित करने के लिए प्रोत्साहित करता है, जिसका अर्थ है कि यह अंततः प्रश्नों को पूरा करने के लिए नेटवर्क पर सतह पर आ जाएगा।
+जब आप एक subgraph पर क्लिक करते हैं, तो आप निम्नलिखित कर सकेंगे:
+
+- प्लेग्राउंड में परीक्षण प्रश्न करें और सूचनापूर्ण निर्णय लेने के लिए नेटवर्क विवरण का उपयोग करें।
+- अपने स्वयं के subgraph या दूसरों के subgraphs पर GRT का सिग्नल दें ताकि indexers इसकी महत्ता और गुणवत्ता के बारे में जागरूक हो सकें।
+- यह महत्वपूर्ण है क्योंकि एक subgraph पर संकेत देना इसे अनुक्रमित करने के लिए प्रोत्साहित करता है, जिसका अर्थ है कि यह अंततः नेटवर्क पर क्वेरीज़ को सेवा देने के लिए सामने आएगा।
 
 ![एक्सप्लोरर छवि 2](/img/Subgraph-Details.png)
 
-प्रत्येक सबग्राफ के समर्पित पृष्ठ पर, कई विवरण सामने आते हैं। इसमे शामिल है:
+हर subgraph के समर्पित पृष्ठ पर, आप निम्नलिखित कार्य कर सकते हैं:
 
 - सबग्राफ पर सिग्नल/अन-सिग्नल
 - चार्ट, वर्तमान परिनियोजन आईडी और अन्य मेटाडेटा जैसे अधिक विवरण देखें
@@ -31,26 +45,32 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ## प्रतिभागियों
 
-इस टैब के भीतर, आपको उन सभी लोगों का एक विहंगम दृश्य मिलेगा जो नेटवर्क गतिविधियों में भाग ले रहे हैं, जैसे कि इंडेक्सर्स, डेलिगेटर्स और क्यूरेटर। नीचे, हम इसकी गहन समीक्षा करेंगे कि प्रत्येक टैब आपके लिए क्या मायने रखता है।
+यह अनुभाग सभी 'participants' का एक दृष्टिकोण प्रदान करता है, जिसमें नेटवर्क में भाग लेने वाले सभी लोग शामिल हैं, जैसे Indexers, Delegators और Curators।
 
 ### 1. इंडेक्सर्स
 
 ![एक्सप्लोरर छवि 4](/img/Indexer-Pane.png)
 
-इंडेक्सर्स से शुरू करते हैं। इंडेक्सर्स प्रोटोकॉल की रीढ़ हैं, वे हैं जो सबग्राफ पर दांव लगाते हैं, उन्हें इंडेक्स करते हैं, और सबग्राफ का उपभोग करने वाले किसी भी व्यक्ति को पूछताछ करते हैं। इंडेक्सर्स टेबल में, आप इंडेक्सर्स के डेलिगेशन पैरामीटर्स, उनकी हिस्सेदारी, उन्होंने प्रत्येक सबग्राफ में कितना दांव लगाया है, और उन्होंने क्वेरी फीस और इंडेक्सिंग रिवार्ड्स से कितना राजस्व कमाया है, यह देखने में सक्षम होंगे। नीचे गहरा गोता:
+Indexer प्रोटोकॉल की रीढ़ हैं। वे सबग्राफ पर स्टेक करते हैं, उन्हें इंडेक्स करते हैं, और उन सभी को प्रश्न प्रदान करते हैं जो सबग्राफ का उपभोग करते हैं।
 
-- क्वेरी शुल्क में कटौती - क्वेरी शुल्क का % छूट देता है कि इंडेक्सर डेलिगेटर के साथ विभाजित होने पर रखता है
-- प्रभावी रिवार्ड कट - इंडेक्सिंग रिवॉर्ड कट डेलिगेशन पूल पर लागू होता है। यदि यह ऋणात्मक है, तो इसका अर्थ है कि अनुक्रमणक अपने पुरस्कारों का एक भाग दे रहा है। यदि यह धनात्मक है, तो इसका अर्थ है कि अनुक्रमणिका अपने कुछ पुरस्कार रख रहा है
-- कूलडाउन शेष - शेष समय जब तक अनुक्रमणिका उपरोक्त प्रत्यायोजन पैरामीटरों को परिवर्तित नहीं कर सकता। जब इंडेक्सर्स अपने डेलिगेशन पैरामीटर्स को अपडेट करते हैं तो कूलडाउन पीरियड्स को इंडेक्सर्स द्वारा सेट किया जाता है
-- स्वामित्व - यह इंडेक्सर की जमा हिस्सेदारी है, जिसे दुर्भावनापूर्ण या गलत व्यवहार के लिए घटाया जा सकता है
-- प्रत्यायोजित - डेलिगेटर्स से हिस्सेदारी जिसे इंडेक्सर द्वारा आवंटित किया जा सकता है, लेकिन इसे घटाया नहीं जा सकता
-- आबंटित - हिस्सेदारी जो इंडेक्सर सक्रिय रूप से उन सबग्राफ के लिए आवंटित कर रहे हैं जिन्हें वे इंडेक्स कर रहे हैं
-- उपलब्ध प्रत्यायोजित क्षमता - प्रत्यायोजित हिस्सेदारी की राशि जो सूचकांककर्ता अति प्रत्यायोजित होने से पहले प्राप्त कर सकते हैं
+Indexers तालिका में, आप Indexers के डेलीगेशन पैरामीटर, उनकी स्टेक, प्रत्येक subgraph के लिए उन्होंने कितना स्टेक किया है, और उन्होंने प्रश्न शुल्क और इंडेक्सिंग पुरस्कारों से कितना राजस्व प्राप्त किया है, देख सकते हैं।
+
+**विशिष्टताएँ**
+
+- क्वेरी फ़ी कट - वह % जो क्वेरी फ़ी रिबेट्स का हिस्सा है जो Indexer, Delegators के साथ बाँटते समय रखता है।
+- प्रभावी पुरस्कार कट - वह इंडेक्सिंग पुरस्कार कट जो डेलीगेशन पूल पर लागू होता है। यदि यह नकारात्मक है, तो इसका मतलब है कि इंडेक्सर अपने पुरस्कारों का एक हिस्सा दे रहा है। यदि यह सकारात्मक है, तो इसका मतलब है कि Indexer अपने कुछ पुरस्कार रख रहा है।
+- कूलडाउन शेष - वह समय जो उपरोक्त डेलीगेशन पैरामीटर को बदलने के लिए Indexer को बचा है। कूलडाउन अवधि वे होती हैं जो Indexers अपने डेलीगेशन पैरामीटर को अपडेट करते समय सेट करते हैं।
+- यह है Indexer का जमा किया गया हिस्सेदारी, जिसे दुष्ट या गलत व्यवहार के लिए काटा जा सकता है।
+- प्रतिनिधि - 'Delegators' से स्टेक जो 'Indexers' द्वारा आवंटित किया जा सकता है, लेकिन इसे स्लैश नहीं किया जा सकता।
+- आवंटित- वह स्टेक है जिसे Indexers उन subgraphs के लिए सक्रिय रूप से आवंटित कर रहे हैं जिन्हें वे इंडेक्स कर रहे हैं।
+- अवेलबल डेलीगेशन कैपेसिटी - वह मात्रा जो डेलीगेटेड स्टेक है, जो Indexers अभी भी प्राप्त कर सकते हैं इससे पहले कि वे ओवर-डेलीगेटेड हो जाएं।
 - अधिकतम प्रत्यायोजन क्षमता - प्रत्यायोजित हिस्सेदारी की अधिकतम राशि जिसे इंडेक्सर उत्पादक रूप से स्वीकार कर सकता है। आवंटन या पुरस्कार गणना के लिए एक अतिरिक्त प्रत्यायोजित हिस्सेदारी का उपयोग नहीं किया जा सकता है।
-- प्रश्न शुल्क - यह वह कुल शुल्क है जो अंतिम उपयोगकर्ताओं ने एक अनुक्रमणिका से प्रश्नों के लिए भुगतान किया है
+- क्वेरी शुल्क - यह कुल शुल्क है जो अंतिम उपयोगकर्ताओं ने सभी समय में एक Indexer से क्वेरी के लिए भुगतान किया है।
 - इंडेक्सर रिवार्ड्स - यह इंडेक्सर और उनके प्रतिनिधियों द्वारा हर समय अर्जित किए गए कुल इंडेक्सर पुरस्कार हैं। इंडेक्सर पुरस्कार का भुगतान जीआरटी जारी करने के माध्यम से किया जाता है।
 
-इंडेक्सर्स क्वेरी फीस और इंडेक्सिंग पुरस्कार दोनों अर्जित कर सकते हैं। कार्यात्मक रूप से, ऐसा तब होता है जब नेटवर्क प्रतिभागी किसी अनुक्रमणिका को GRT सौंपते हैं। यह इंडेक्सर्स को उनके इंडेक्सर पैरामीटर के आधार पर क्वेरी फीस और पुरस्कार प्राप्त करने में सक्षम बनाता है। तालिका के दायीं ओर क्लिक करके, या अनुक्रमणिका के प्रोफ़ाइल में जाकर और "प्रतिनिधि" बटन पर क्लिक करके अनुक्रमण पैरामीटर सेट किए जाते हैं।
+Indexers दोनों क्वेरी फीस और इंडेक्सिंग पुरस्कार कमा सकते हैं। कार्यात्मक रूप से, यह तब होता है जब नेटवर्क प्रतिभागी GRT को एक Indexer को सौंपते हैं। इससे Indexers को उनके Indexer पैरामीटर के आधार पर क्वेरी फीस और पुरस्कार प्राप्त होते हैं।
+
+- इंडेक्सिंग पैरामीटर को टेबल के दाहिने ओर क्लिक करके या किसी इंडेक्सर के प्रोफ़ाइल में जाकर 'Delegate' बटन पर क्लिक करके सेट किया जा सकता है।
 
 इंडेक्सर कैसे बनें, इस बारे में अधिक जानने के लिए, आप [आधिकारिक दस्तावेज़ीकरण](/network/indexing) या [द ग्राफ एकेडमी इंडेक्सर गाइड्स।](https://thegraph.academy/delegators/ पर नज़र डाल सकते हैं चूइंग-इंडेक्सर्स/)
 
@@ -58,9 +78,13 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ### 2. क्यूरेटर
 
-क्यूरेटर सबग्राफ का विश्लेषण यह पहचानने के लिए करते हैं कि कौन से सबग्राफ उच्चतम गुणवत्ता वाले हैं। एक बार क्यूरेटर को संभावित रूप से आकर्षक सबग्राफ मिल जाने के बाद, वे इसके बॉन्डिंग कर्व पर संकेत देकर इसे क्यूरेट कर सकते हैं। ऐसा करने में, क्यूरेटर इंडेक्सर्स को बताते हैं कि कौन से सबग्राफ उच्च गुणवत्ता वाले हैं और उन्हें इंडेक्स किया जाना चाहिए।
+क्यूरेटर subgraphs का विश्लेषण करते हैं ताकि यह पहचान सकें कि कौन से subgraphs उच्चतम गुणवत्ता के हैं। एक बार जब एक क्यूरेटर एक संभावित उच्च गुणवत्ता वाले subgraph को खोज लेता है, तो वे इसके बॉन्डिंग कर्व पर सिग्नल देकर इसे क्यूरेट कर सकते हैं। ऐसा करके, क्यूरेटर इंडेक्सर्स को बताते हैं कि कौन से subgraphs उच्च गुणवत्ता के हैं और उन्हें इंडेक्स किया जाना चाहिए।
+
+- क्यूरेटर समुदाय के सदस्य, डेटा उपभोक्ता, या यहां तक कि अपने Subgraphs पर संकेत देने के लिए GRT टोकन को बॉन्डिंग कर्व में जमा करके अपने स्वयं के Subgraph पर संकेत देने वाले सबग्रह डेवलपर्स भी हो सकते हैं।
+  - GRT जमा करके, Curators एक subgraph के curation shares का निर्माण करते हैं। इसके परिणामस्वरूप, वे उस subgraph से उत्पन्न query fees का एक भाग अर्जित कर सकते हैं जिस पर उन्होंने संकेत दिया है।
+  - "Bonding curve" क्यूरेटर्स को सबसे उच्च गुणवत्ता वाले डेटा स्रोतों को क्यूरेट करने के लिए प्रोत्साहित करता है।
 
-क्यूरेटर समुदाय के सदस्य, डेटा उपभोक्ता या यहां तक कि सबग्राफ डेवलपर भी हो सकते हैं, जो बॉन्डिंग कर्व में जीआरटी टोकन जमा करके अपने स्वयं के सबग्राफ पर संकेत देते हैं। जीआरटी जमा करके, क्यूरेटर एक सबग्राफ के क्यूरेशन शेयरों का निर्माण करते हैं। नतीजतन, क्यूरेटर क्वेरी फीस के एक हिस्से को अर्जित करने के लिए पात्र हैं, जो उपग्राफ उत्पन्न करता है, जिस पर उन्होंने संकेत दिया है। बॉन्डिंग कर्व क्यूरेटर को उच्चतम गुणवत्ता वाले डेटा स्रोतों को क्यूरेट करने के लिए प्रोत्साहित करता है। इस खंड में क्यूरेटर तालिका आपको देखने की अनुमति देगी:
+यहां 'Curator' तालिका में नीचे दी गई जानकारी को देख सकते हैं:
 
 - क्यूरेटर द्वारा क्यूरेट करना शुरू करने की तारीख
 - जमा किए गए जीआरटी की संख्या
@@ -68,34 +92,36 @@ First things first, if you just finished deploying and publishing your subgraph
 
 ![एक्सप्लोरर छवि 6](/img/Curation-Overview.png)
 
-यदि आप क्यूरेटर की भूमिका के बारे में अधिक जानना चाहते हैं, तो आप [द ग्राफ़ अकादमी](https://thegraph.academy/curators/) या [आधिकारिक दस्तावेज़ीकरण](/network/curating) के निम्न लिंक पर जाकर ऐसा कर सकते हैं।
+अगर आप 'Curator' भूमिका के बारे में अधिक जानना चाहते हैं, तो आप ऐसा कर सकते हैं, यहाँ पर जाएं: [official documentation.](/network/curating) या [The Graph Academy](https://thegraph.academy/curators/).
 
 ### 3. प्रतिनिधि
 
-द ग्राफ नेटवर्क की सुरक्षा और विकेंद्रीकरण को बनाए रखने में प्रतिनिधि महत्वपूर्ण भूमिका निभाते हैं। वे एक या एक से अधिक इंडेक्सर्स को GRT टोकन सौंपकर (यानी, "स्टेकिंग") नेटवर्क में भाग लेते हैं। डेलीगेटर्स के बिना, इंडेक्सर्स के महत्वपूर्ण पुरस्कार और शुल्क अर्जित करने की संभावना कम होती है। इसलिए, इंडेक्सर्स डेलिगेटर्स को इंडेक्सिंग रिवार्ड्स और उनके द्वारा अर्जित क्वेरी फीस के एक हिस्से की पेशकश करके आकर्षित करना चाहते हैं।
+The Graph Network की सुरक्षा और विकेंद्रीकरण को बनाए रखने में Delegators की महत्वपूर्ण भूमिका होती है। वे नेटवर्क में भाग लेते हैं 'delegating' (यानी, 'staking') करके और GRT tokens को एक या एक से अधिक Indexers को सौंपते हैं।
 
-Delegators, in turn, 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 this! It’s recommended to connect with the indexers selected via [The Graph’s Discord](https://discord.gg/graphprotocol) or [The Graph Forum](https://forum.thegraph.com/)!
+- Indexers के बिना, Delegators को महत्वपूर्ण पुरस्कार और शुल्क कमाने की संभावना कम होती है। इसलिए, Indexers अपने 'indexing rewards' और 'query fees' का एक हिस्सा देकर Delegators को आकर्षित करते हैं।
+- डेलीगेटर्स विभिन्न कारकों के आधार पर इंडेक्सर्स का चयन करते हैं, जैसे कि पिछले प्रदर्शन, इंडेक्सिंग इनाम दरें, और क्वेरी शुल्क कट।
+- सामुदायिक प्रतिष्ठा चयन प्रक्रिया में भी एक कारक हो सकती है। अनुशंसा की जाती है कि चुने हुए Indexers से [The Graph’s Discord](https://discord.gg/graphprotocol) या [The Graph Forum](https://forum.thegraph.com/) के माध्यम से जुड़ें!
 
 ![एक्सप्लोरर छवि 7](/img/Delegation-Overview.png)
 
-प्रतिनिधि तालिका आपको समुदाय में सक्रिय प्रतिनिधियों को देखने की अनुमति देगी, साथ ही मेट्रिक्स जैसे कि:
+Delegators तालिका में आप समुदाय में सक्रिय Delegators और महत्वपूर्ण मैट्रिक्स देख सकते हैं:
 
 - एक डेलीगेटर कितने इंडेक्सर्स की ओर डेलिगेट कर रहा है
 - एक प्रतिनिधि का मूल प्रतिनिधिमंडल
 - उन्होंने जो पुरस्कार जमा किए हैं, लेकिन प्रोटोकॉल से वापस नहीं लिए हैं
 - एहसास हुआ पुरस्कार वे प्रोटोकॉल से वापस ले लिया
 - वर्तमान में उनके पास प्रोटोकॉल में जीआरटी की कुल राशि है
-- जिस तारीख को उन्होंने आखिरी बार प्रत्यायोजित किया था
+- वे आखिरी बार 'delegated' की तारीख
 
-यदि आप प्रतिनिधि बनने के तरीके के बारे में अधिक जानना चाहते हैं, तो आगे मत देखिए! आपको बस इतना करना है कि [आधिकारिक दस्तावेज़ीकरण](/network/delegating) या [द ग्राफ़ अकादमी](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) पर जाना है।
+यदि आप Delegator बनने के बारे में अधिक जानना चाहते हैं, तो [आधिकारिक दस्तावेज़](/network/delegating) देखें या [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers) पर जाएं।
 
 ## नेटवर्क
 
-नेटवर्क अनुभाग में, आप वैश्विक KPI के साथ-साथ प्रति युग के आधार पर स्विच करने की क्षमता देखेंगे और नेटवर्क मेट्रिक्स का अधिक विस्तार से विश्लेषण करेंगे। ये विवरण आपको इस बात का बोध कराएंगे कि समय के साथ नेटवर्क कैसा प्रदर्शन कर रहा है।
+इस अनुभाग में, आप वैश्विक KPI देख सकते हैं और प्रति-युग आधार पर स्विच करने की क्षमता को देख सकते हैं और नेटवर्क मेट्रिक्स का अधिक विस्तार से विश्लेषण कर सकते हैं। ये विवरण आपको यह समझने में मदद करेंगे कि नेटवर्क समय के साथ कैसा प्रदर्शन कर रहा है।
 
 ### अवलोकन
 
-The overview section has all the current network metrics as well as some cumulative metrics over time. Here you can see things like:
+ओवरव्यू सेक्शन में वर्तमान नेटवर्क मैट्रिक्स और समय के साथ कुछ संचयी मैट्रिक्स दोनों शामिल हैं:
 
 - वर्तमान कुल नेटवर्क हिस्सेदारी
 - इंडेक्सर्स और उनके प्रतिनिधियों के बीच हिस्सेदारी विभाजित हो गई
@@ -104,10 +130,10 @@ The overview section has all the current network metrics as well as some cumulat
 - प्रोटोकॉल पैरामीटर जैसे क्यूरेशन रिवॉर्ड, महंगाई दर और बहुत कुछ
 - वर्तमान युग पुरस्कार और शुल्क
 
-कुछ प्रमुख विवरण जो ध्यान देने योग्य हैं:
+कुछ महत्वपूर्ण विवरण नोट करने के लिए:
 
-- **क्वेरी शुल्क उपभोक्ताओं द्वारा उत्पन्न शुल्क का प्रतिनिधित्व करते हैं**, और सबग्राफ के लिए उनके आवंटन बंद होने के बाद कम से कम 7 युगों (नीचे देखें) की अवधि के बाद इंडेक्सर्स द्वारा उनका दावा (या नहीं) किया जा सकता है। और उनके द्वारा प्रदान किए गए डेटा को उपभोक्ताओं द्वारा मान्य किया गया है।
-- **इंडेक्सिंग रिवार्ड्स युग के दौरान नेटवर्क जारी करने से इंडेक्सर्स द्वारा दावा किए गए पुरस्कारों की राशि का प्रतिनिधित्व करते हैं।** हालांकि प्रोटोकॉल जारी करना तय है, इंडेक्सर्स द्वारा अपने आवंटन को बंद करने के बाद ही पुरस्कार प्राप्त होते हैं। उन उप-अनुच्छेदों की ओर जिन्हें वे अनुक्रमित कर रहे हैं। इस प्रकार पुरस्कारों की प्रति-युग संख्या भिन्न होती है (अर्थात। कुछ युगों के दौरान, इंडेक्सर्स सामूहिक रूप से उन आवंटनों को बंद कर सकते हैं जो कई दिनों से खुले हैं)।
+- **क्वेरी शुल्क उन शुल्कों का प्रतिनिधित्व करते हैं जो उपभोक्ताओं द्वारा उत्पन्न होते हैं**। इन्हें Indexers द्वारा 7 युगों (नीचे देखें) की अवधि के बाद दावा किया जा सकता है (या नहीं) जब उनके आवंटन subgraphs की ओर बंद कर दिए गए हैं और जिन डेटा को उन्होंने प्रदान किया है, उसे उपभोक्ताओं द्वारा मान्य किया गया है।
+- **Indexing rewards उस राशि का प्रतिनिधित्व करते हैं जो Indexers ने उस अवधि के दौरान नेटवर्क जारी से दावा किया।** हालांकि प्रोटोकॉल जारी स्थिर है, इनाम तभी उत्पन्न होते हैं जब Indexers उन subgraphs के लिए अपनी अलोकन बंद कर देते हैं जिन्हें वे इंडेक्सिंग कर रहे थे। इसलिए, प्रति-अवधि इनाम की संख्या भिन्न होती है (उदाहरण के लिए, कुछ अवधियों के दौरान, Indexers ने सामूहिक रूप से कई दिनों से खुले अलोकन बंद किए हो सकते हैं)।
 
 ![एक्सप्लोरर छवि 8](/img/Network-Stats.png)
 
@@ -121,29 +147,34 @@ The overview section has all the current network metrics as well as some cumulat
   - सक्रिय युग वह है जिसमें इंडेक्सर्स वर्तमान में हिस्सेदारी आवंटित कर रहे हैं और क्वेरी फीस जमा कर रहे हैं
   - बसने वाले युग वे हैं जिनमें राज्य चैनलों को बसाया जा रहा है। इसका मतलब यह है कि अगर उपभोक्ता उनके खिलाफ विवाद खोलते हैं तो इंडेक्सर्स स्लैशिंग के अधीन हैं।
   - वितरण युग ऐसे युग हैं जिनमें युगों के लिए राज्य चैनल तय किए जा रहे हैं और अनुक्रमणकर्ता अपनी क्वेरी शुल्क छूट का दावा कर सकते हैं।
-  - अंतिम रूप दिए गए युग वे युग हैं जिनमें अनुक्रमणकों द्वारा दावा करने के लिए कोई क्वेरी शुल्क छूट नहीं बची है, इस प्रकार अंतिम रूप दिया जा रहा है।
+  - अंतिम चरण वे चरण हैं जिनमें Indexers द्वारा दावा करने के लिए कोई प्रश्न शुल्क छूट शेष नहीं है।
 
 ![एक्सप्लोरर छवि 9](/img/Epoch-Stats.png)
 
 ## आपका उपयोगकर्ता प्रोफ़ाइल
 
-अब जबकि हमने नेटवर्क आँकड़ों के बारे में बात कर ली है, चलिए आपकी व्यक्तिगत प्रोफ़ाइल पर चलते हैं। आपकी व्यक्तिगत प्रोफ़ाइल आपके लिए आपकी नेटवर्क गतिविधि देखने का स्थान है, चाहे आप नेटवर्क पर कैसे भी भाग ले रहे हों। आपका एथेरियम वॉलेट आपके उपयोगकर्ता प्रोफ़ाइल के रूप में कार्य करेगा, और उपयोगकर्ता डैशबोर्ड के साथ, आप देख पाएंगे:
+आपकी व्यक्तिगत प्रोफ़ाइल वह स्थान है जहां आप अपने नेटवर्क गतिविधि को देख सकते हैं, चाहे आपकी भूमिका नेटवर्क पर कुछ भी हो। आपका क्रिप्टो वॉलेट आपके उपयोगकर्ता प्रोफ़ाइल के रूप में कार्य करेगा, और उपयोगकर्ता डैशबोर्ड के साथ, आप निम्नलिखित टैब देख सकेंगे:
 
 ### प्रोफ़ाइल अवलोकन
 
-यह वह जगह है जहाँ आप अपने द्वारा की गई कोई भी वर्तमान कार्रवाई देख सकते हैं। यह वह जगह भी है जहां आप अपनी प्रोफ़ाइल जानकारी, विवरण और वेबसाइट (यदि आपने एक जोड़ा है) पा सकते हैं।
+इस खंड में, आप निम्नलिखित देख सकते हैं:
+
+- आपकी वर्तमान क्रियाओं में से कोई भी आपने किया है।
+- आपकी प्रोफ़ाइल जानकारी, विवरण, और वेबसाइट (यदि आपने एक जोड़ी है)।
 
 ![एक्सप्लोरर छवि 10](/img/Profile-Overview.png)
 
 ### सबग्राफ टैब
 
-यदि आप सबग्राफ टैब में क्लिक करते हैं, तो आप अपने प्रकाशित सबग्राफ देखेंगे। इसमें परीक्षण उद्देश्यों के लिए सीएलआई के साथ तैनात कोई सबग्राफ शामिल नहीं होगा - सबग्राफ केवल तभी दिखाई देंगे जब वे विकेंद्रीकृत नेटवर्क पर प्रकाशित होंगे।
+सबग्राफ टैब में, आप अपने प्रकाशित सबग्राफ को देखेंगे।
+
+> यह उन subgraphs को शामिल नहीं करेगा जो परीक्षण उद्देश्यों के लिए CLI के साथ तैनात किए गए हैं। subgraphs तब ही दिखाई देंगे जब उन्हें विकेंद्रीकृत नेटवर्क पर प्रकाशित किया जाएगा।
 
 ![एक्सप्लोरर छवि 11](/img/Subgraphs-Overview.png)
 
 ### अनुक्रमण टैब
 
-यदि आप इंडेक्सिंग टैब में क्लिक करते हैं, तो आपको सबग्राफ के लिए सभी सक्रिय और ऐतिहासिक आवंटन के साथ एक तालिका मिलेगी, साथ ही चार्ट भी मिलेंगे जिनका आप विश्लेषण कर सकते हैं और एक इंडेक्सर के रूप में अपने पिछले प्रदर्शन को देख सकते हैं।
+इंडेक्सिंग टैब में, आपको एक तालिका मिलेगी जिसमें सभी सक्रिय और ऐतिहासिक आवंटन सबग्राफ के प्रति हैं। आप चार्ट भी पाएंगे जहां आप एक Indexerके रूप में अपने पिछले प्रदर्शन को देख और विश्लेषण कर सकते हैं।
 
 इस खंड में आपके नेट इंडेक्सर रिवार्ड्स और नेट क्वेरी फीस के विवरण भी शामिल होंगे। आपको ये मेट्रिक दिखाई देंगे:
 
@@ -158,7 +189,9 @@ The overview section has all the current network metrics as well as some cumulat
 
 ### प्रतिनिधि टैब
 
-प्रतिनिधि ग्राफ़ नेटवर्क के लिए महत्वपूर्ण हैं। एक प्रतिनिधि को एक इंडेक्सर चुनने के लिए अपने ज्ञान का उपयोग करना चाहिए जो पुरस्कारों पर एक स्वस्थ रिटर्न प्रदान करेगा। यहां आप अपने सक्रिय और ऐतिहासिक प्रतिनिधिमंडलों का विवरण पा सकते हैं, साथ ही उन इंडेक्सर्स के मेट्रिक्स के साथ जिन्हें आपने प्रत्यायोजित किया है।
+Delegator ,The Graph नेटवर्क के लिए महत्वपूर्ण हैं। उन्हें अपने ज्ञान का उपयोग करके एक इंडेक्सर का चयन करना चाहिए जो पुरस्कारों पर स्वस्थ रिटर्न प्रदान करेगा।
+
+डेलीगेटर्स टैब में, आप अपनी सक्रिय और ऐतिहासिक डेलीगेशंस का विवरण पा सकते हैं, साथ ही उन Indexers के मेट्रिक्स भी जिनकी ओर आपने डेलीगेट किया है।
 
 पृष्ठ के पहले भाग में, आप अपना प्रतिनिधिमंडल चार्ट और साथ ही केवल-पुरस्कार चार्ट देख सकते हैं। बाईं ओर, आप वे KPI देख सकते हैं जो आपके वर्तमान डेलिगेशन मेट्रिक्स को दर्शाते हैं।
 

From 42b2facb8110fe0340f92040b9382600e298efb7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:05 -0500
Subject: [PATCH 0771/1325] New translations explorer.mdx (Swahili)

---
 website/pages/sw/network/explorer.mdx | 236 ++++++++++++++++++++++++++
 1 file changed, 236 insertions(+)
 create mode 100644 website/pages/sw/network/explorer.mdx

diff --git a/website/pages/sw/network/explorer.mdx b/website/pages/sw/network/explorer.mdx
new file mode 100644
index 000000000000..02dca6ed2f9f
--- /dev/null
+++ b/website/pages/sw/network/explorer.mdx
@@ -0,0 +1,236 @@
+---
+title: Graph Explorer
+---
+
+Learn about The Graph Explorer and access the world of subgraphs and network data.
+
+Graph Explorer consists of multiple parts where you can interact with other subgraph developers, dapp developers, Curators, Indexers, and Delegators.
+
+## Video Guide
+
+For a general overview of Graph Explorer, check out the video below:
+
+<VideoEmbed youtube="u224xf7rEBY" />
+
+## Subgraphs
+
+After you just finish deploying and publishing your subgraph in Subgraph Studio, click on the "subgraphs tab” at the top of the navigation bar to access the following:
+
+- Your own finished subgraphs
+- Subgraphs published by others
+- The exact subgraph you want (based on the date created, signal amount, or name).
+
+![Explorer Image 1](/img/Subgraphs-Explorer-Landing.png)
+
+When you click into a subgraph, you will be able to do the following:
+
+- 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.
+
+![Explorer Image 2](/img/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
+- 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
+
+![Explorer Image 3](/img/Explorer-Signal-Unsignal.png)
+
+## Participants
+
+This section provides a bird' s-eye view of all "participants," which includes everyone participating in the network, such as Indexers, Delegators, and Curators.
+
+### 1. Indexers
+
+![Explorer Image 4](/img/Indexer-Pane.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.
+
+**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.
+
+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.
+
+- Indexing parameters can be set by clicking on the right-hand side of the table or by going into an Indexer’s profile and clicking the “Delegate” button.
+
+To learn more about how to become an Indexer, you can take a look at the [official documentation](/network/indexing) or [The Graph Academy Indexer guides.](https://thegraph.academy/delegators/choosing-indexers/)
+
+![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.
+
+- Curators can be community members, data consumers, or even subgraph developers who signal on their own subgraphs by depositing GRT tokens into a bonding curve.
+  - By depositing GRT, Curators mint curation shares of a subgraph. As a result, they can earn a portion of the query fees generated by the subgraph they have signaled on.
+  - The bonding curve incentivizes Curators to curate the highest quality data sources.
+
+In the The Curator table listed below you can see:
+
+- The date the Curator started curating
+- The number of GRT that was deposited
+- The number of shares a Curator owns
+
+![Explorer Image 6](/img/Curation-Overview.png)
+
+If you want to learn more about the Curator role, you can do so by visiting [official documentation.](/network/curating) or [The Graph Academy](https://thegraph.academy/curators/).
+
+### 3. 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.
+
+- Without Delegators, Indexers are less likely to earn significant rewards and fees. Therefore, Indexers attract Delegators by offering them a portion of their indexing rewards and query fees.
+- 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)
+
+In the Delegators table you can see the active Delegators in the community and important metrics:
+
+- The number of Indexers a Delegator is delegating towards
+- A Delegator’s original delegation
+- The rewards they have accumulated but have not withdrawn from the protocol
+- The realized rewards they withdrew from the protocol
+- Total amount of GRT they have currently in the protocol
+- The date they last delegated
+
+If you want to learn more about how to become a Delegator, check out the [official documentation](/network/delegating) or [The Graph Academy](https://docs.thegraph.academy/official-docs/delegator/choosing-indexers).
+
+## Network
+
+In this section, you can see global KPIs and view 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
+
+The overview section has both all the current network metrics and some cumulative metrics over time:
+
+- The current total network stake
+- The stake split between the Indexers and their Delegators
+- Total supply, minted, and burned GRT since the network inception
+- Total Indexing rewards since the inception of the protocol
+- Protocol parameters such as curation reward, inflation rate, and more
+- Current epoch rewards and fees
+
+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)
+
+### Epochs
+
+In the Epochs section, you can analyze on a per-epoch basis, metrics such as:
+
+- Epoch start or end block
+- Query fees generated and indexing rewards collected during a specific epoch
+- Epoch status, which refers to the query fee collection and distribution and can have different states:
+  - The active epoch is the one in which Indexers are currently allocating stake and collecting query fees
+  - The settling epochs are the ones in which the state channels are being settled. This means that the Indexers are subject to slashing if the consumers open disputes against them.
+  - 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)
+
+## Your User Profile
+
+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:
+
+### 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).
+
+![Explorer Image 10](/img/Profile-Overview.png)
+
+### Subgraphs Tab
+
+In the Subgraphs tab, you’ll see 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.
+
+![Explorer Image 11](/img/Subgraphs-Overview.png)
+
+### 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.
+
+This section will also include details about your net Indexer rewards and net query fees. You’ll see the following metrics:
+
+- 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
+
+![Explorer Image 12](/img/Indexer-Stats.png)
+
+### Delegating Tab
+
+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.
+
+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 Delegator metrics you’ll see here in this tab include:
+
+- Total delegation rewards
+- Total unrealized rewards
+- Total 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).
+
+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.
+
+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).
+
+![Explorer Image 13](/img/Delegation-Stats.png)
+
+### 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.
+
+Within this tab, you’ll find an overview of:
+
+- All the subgraphs you're curating on with signal details
+- Share totals per subgraph
+- Query rewards per subgraph
+- Updated at date details
+
+![Explorer Image 14](/img/Curation-Stats.png)
+
+## 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)
+
+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.
+
+<div sx={{ mx: 'auto', maxWidth: '400px' }}>![Wallet details](/img/Wallet-Details.png)</div>

From 2f76477dde1515ca0f2a3d94fbad20697467a29f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:06 -0500
Subject: [PATCH 0772/1325] New translations indexing.mdx (Romanian)

---
 website/pages/ro/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/ro/network/indexing.mdx b/website/pages/ro/network/indexing.mdx
index 77013e86a790..0eb017b5be3f 100644
--- a/website/pages/ro/network/indexing.mdx
+++ b/website/pages/ro/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Many of the community-made dashboards include pending rewards values and they can be easily checked manually by following these steps:
 
-1. Query the [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) to get the IDs for all active allocations:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Port | Purpose                                                    | Routes                                                                  | CLI Argument   | Environment Variable   |
+| ---- | ---------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### The life of an allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 942141331b5536703a1e66e4bc9fa26e52aa82a4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:07 -0500
Subject: [PATCH 0773/1325] New translations indexing.mdx (Spanish)

---
 website/pages/es/network/indexing.mdx | 42 +++++++++++++--------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/website/pages/es/network/indexing.mdx b/website/pages/es/network/indexing.mdx
index a57c640869f9..076ee45d9703 100644
--- a/website/pages/es/network/indexing.mdx
+++ b/website/pages/es/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Muchos de los paneles creados por la comunidad incluyen valores de recompensas pendientes y se pueden verificar fácilmente de forma manual siguiendo estos pasos:
 
-1. Consulta el [ mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) para obtener los ID de todas las allocations activas:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -113,11 +113,11 @@ Los indexadores pueden diferenciarse aplicando técnicas avanzadas para tomar de
 - **Grande**: Preparado para indexar todos los subgrafos utilizados actualmente y atender solicitudes para el tráfico relacionado.
 
 | Configuración | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Pequeño | 4 | 8 | 1 | 4 | 16 |
-| Estándar | 8 | 30 | 1 | 12 | 48 |
-| Medio | 16 | 64 | 2 | 32 | 64 |
-| Grande | 72 | 468 | 3,5 | 48 | 184 |
+| ------------- |:--------------------------:|:-----------------------------------:|:---------------------------------:|:---------------------:|:------------------------------:|
+| Pequeño       |             4              |                  8                  |                 1                 |           4           |               16               |
+| Estándar      |             8              |                 30                  |                 1                 |          12           |               48               |
+| Medio         |             16             |                 64                  |                 2                 |          32           |               64               |
+| Grande        |             72             |                 468                 |                3,5                |          48           |              184               |
 
 ### ¿Qué precauciones básicas de seguridad debe tomar un Indexador?
 
@@ -149,20 +149,20 @@ Nota: Para admitir el escalado ágil, se recomienda que las inquietudes de consu
 
 #### Graph Node
 
-| Puerto | Objeto | Rutas | Argumento CLI | Variable de Entorno |
-| --- | --- | --- | --- | --- |
-| 8000 | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(para suscripciones a subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(para administrar implementaciones) | / | --admin-port | - |
-| 8030 | API de estado de indexación de subgrafos | /graphql | --index-node-port | - |
-| 8040 | Métricas de Prometheus | /metrics | --metrics-port | - |
+| Puerto | Objeto                                                         | Rutas                                                | Argumento CLI     | Variable de Entorno |
+| ------ | -------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------- |
+| 8000   | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                   |
+| 8001   | GraphQL WS<br />(para suscripciones a subgrafos)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                   |
+| 8020   | JSON-RPC<br />(para administrar implementaciones)        | /                                                    | --admin-port      | -                   |
+| 8030   | API de estado de indexación de subgrafos                       | /graphql                                             | --index-node-port | -                   |
+| 8040   | Métricas de Prometheus                                         | /metrics                                             | --metrics-port    | -                   |
 
 #### Servicio de Indexador
 
-| Puerto | Objeto | Rutas | Argumento CLI | Variable de Entorno |
-| --- | --- | --- | --- | --- |
-| 7600 | Servidor HTTP GraphQL<br />(para consultas de subgrafo pagadas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Métricas de Prometheus | /metrics | --metrics-port | - |
+| Puerto | Objeto                                                                | Rutas                                                                   | Argumento CLI  | Variable de Entorno    |
+| ------ | --------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600   | Servidor HTTP GraphQL<br />(para consultas de subgrafo pagadas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300   | Métricas de Prometheus                                                | /metrics                                                                | --metrics-port | -                      |
 
 #### Agente Indexador
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ La **CLI del Indexador** se conecta al agente Indexador, normalmente a través d
 
 - `graph indexer rules maybe [options] <deployment-id>` - Configura `thedecisionBasis` para un deploy en `rules`, de modo que el agente Indexador use las reglas de indexación para decidir si debe indexar este deploy.
 
-- `graph indexer actions get [options] <action-id>` - Obtiene una o más acciones usando `all` o deja `action-id` vacío para obtener todas las acciones. Un argumento adicional `--status` se puede utilizar para imprimir todas las acciones de un determinado estado.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Acción de allocation en fila
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### La vida de una allocation
 
-Después de ser creada por un Indexador, una allocation saludable pasa por cuatro fases.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From cafcf9e5b8a721f6952f79830636ab4bc16dc2e7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:09 -0500
Subject: [PATCH 0774/1325] New translations indexing.mdx (Arabic)

---
 website/pages/ar/network/indexing.mdx | 42 +++++++++++++--------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/website/pages/ar/network/indexing.mdx b/website/pages/ar/network/indexing.mdx
index 06055f703f94..849d5d13f7b5 100644
--- a/website/pages/ar/network/indexing.mdx
+++ b/website/pages/ar/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 تشتمل العديد من لوحات المعلومات التي أنشأها المجتمع على قيم المكافآت المعلقة ويمكن التحقق منها بسهولة يدويًا باتباع الخطوات التالية:
 
-1. استعلم عن [mainnet الفرعيةرسم بياني ](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) للحصول على IDs لجميع المخصصات النشطة:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 } query indexerAllocations
@@ -113,11 +113,11 @@ The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that
 - **كبيرة** - مُعدة لفهرسة جميع ال subgraphs المستخدمة حاليا وأيضا لخدمة طلبات حركة مرور البيانات ذات الصلة.
 
 | Setup | Postgres<br /> (CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory 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               |
 
 ### What are some basic security precautions an Indexer should take?
 
@@ -149,20 +149,20 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 #### Graph Node
 
-| المنفذ | الغرض | المسار | CLI Argument | متغيرات البيئة |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port-- | - |
-| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port-- | - |
-| 8020 | JSON-RPC <br /> (for managing deployments) | / | admin-port-- | - |
-| 8030 | Subgraph indexing status API | /graphql | index-node-port-- | - |
-| 8040 | Prometheus metrics | /metrics | metrics-port-- | - |
+| المنفذ | الغرض                                                   | المسار                                                              | CLI Argument      | متغيرات البيئة |
+| ------ | ------------------------------------------------------- | ------------------------------------------------------------------- | ----------------- | -------------- |
+| 8000   | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port--       | -              |
+| 8001   | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port--         | -              |
+| 8020   | JSON-RPC <br /> (for managing deployments)        | /                                                                   | admin-port--      | -              |
+| 8030   | Subgraph indexing status API                            | /graphql                                                            | index-node-port-- | -              |
+| 8040   | Prometheus metrics                                      | /metrics                                                            | metrics-port--    | -              |
 
 #### خدمة المفهرس
 
-| المنفذ | الغرض | المسار | CLI Argument | متغيرات البيئة |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP server <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | port-- | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | metrics-port-- | - |
+| المنفذ | الغرض                                                        | المسار                                                                      | CLI Argument   | متغيرات البيئة         |
+| ------ | ------------------------------------------------------------ | --------------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600   | GraphQL HTTP server <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | port--         | `INDEXER_SERVICE_PORT` |
+| 7300   | Prometheus metrics                                           | /metrics                                                                    | metrics-port-- | -                      |
 
 #### وكيل المفهرس(Indexer Agent)
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### عمر التخصيص allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 0260898b0c1e96064bbe5f3bbc09c16f75905973 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:10 -0500
Subject: [PATCH 0775/1325] New translations indexing.mdx (Czech)

---
 website/pages/cs/network/indexing.mdx | 42 +++++++++++++--------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/website/pages/cs/network/indexing.mdx b/website/pages/cs/network/indexing.mdx
index 7dbb2e7ced77..fe0a36c340ca 100644
--- a/website/pages/cs/network/indexing.mdx
+++ b/website/pages/cs/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Mnoho informačních panelů vytvořených komunitou obsahuje hodnoty čekajících odměn a lze je snadno zkontrolovat ručně podle následujících kroků:
 
-1. Dotazem na podgraf [mainnet](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) získáte ID všech aktivních alokací:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -113,11 +113,11 @@ Indexátory se mohou odlišovat použitím pokročilých technik pro rozhodován
 - **Large** - Připraveno k indexování všech aktuálně nepoužívaných příbuzných podgrafů.
 
 | Nastavení | Postgres<br />(CPUs) | Postgres<br />(paměť v GBs) | Postgres<br />(disk v TBs) | VMs<br />(CPUs) | VMs<br />(paměť v GBs) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Malé | 4 | 8 | 1 | 4 | 16 |
-| Standard | 8 | 30 | 1 | 12 | 48 |
-| Střední | 16 | 64 | 2 | 32 | 64 |
-| Velký | 72 | 468 | 3.5 | 48 | 184 |
+| --------- |:--------------------------:|:---------------------------------:|:--------------------------------:|:---------------------:|:----------------------------:|
+| Malé      |             4              |                 8                 |                1                 |           4           |              16              |
+| Standard  |             8              |                30                 |                1                 |          12           |              48              |
+| Střední   |             16             |                64                 |                2                 |          32           |              64              |
+| Velký     |             72             |                468                |               3.5                |          48           |             184              |
 
 ### Jaká jsou základní bezpečnostní opatření, která by měl indexátor přijmout?
 
@@ -149,20 +149,20 @@ Poznámka: Pro podporu agilního škálování se doporučuje oddělit dotazová
 
 #### Uzel Graf
 
-| Port | Účel | Trasy | CLI Argument | Proměnná prostředí |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(pro odběry podgrafů) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(pro správu nasazení) | / | --admin-port | - |
-| 8030 | Stav indexování podgrafů API | /graphql | --index-node-port | - |
-| 8040 | Metriky Prometheus | /metrics | --metrics-port | - |
+| Port | Účel                                                 | Trasy                                                | CLI Argument      | Proměnná prostředí |
+| ---- | ---------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
+| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
+| 8001 | GraphQL WS<br />(pro odběry podgrafů)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
+| 8020 | JSON-RPC<br />(pro správu nasazení)            | /                                                    | --admin-port      | -                  |
+| 8030 | Stav indexování podgrafů API                         | /graphql                                             | --index-node-port | -                  |
+| 8040 | Metriky Prometheus                                   | /metrics                                             | --metrics-port    | -                  |
 
 #### Služba Indexer
 
-| Port | Účel | Trasy | CLI Argument | Proměnná prostředí |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP server<br />(pro placené dotazy na podgrafy) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Metriky Prometheus | /metrics | --metrics-port | - |
+| Port | Účel                                                            | Trasy                                                                   | CLI Argument   | Proměnná prostředí     |
+| ---- | --------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(pro placené dotazy na podgrafy) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Metriky Prometheus                                              | /metrics                                                                | --metrics-port | -                      |
 
 #### Agent indexátoru
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ Navrhovaným nástrojem pro interakci s **Indexer Management API** je **Indexer
 
 - `možná pravidla indexování grafů [možnosti] <deployment-id>` - Nastaví `decisionBasis` pro nasazení na `rules`, takže agent Indexer bude při rozhodování o indexování tohoto nasazení používat pravidla indexování.
 
-- `Akce indexátoru grafu získají [možnosti] <action-id>` - Získá jednu nebo více akcí pomocí `all` nebo ponechá `action-id` prázdné pro získání všech akcí. Přídavný argument `--status` lze použít pro vypsání všech akcí určitého stavu.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Akce přidělení fronty
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### Životnost přídělu
 
-Po vytvoření indexátorem prochází zdravé přidělení čtyřmi stavy.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Aktivní** – Jakmile je alokace vytvořena v řetězci ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/ contract/staking/Staking.sol#L316)) je považován za **aktivní**. Část vlastního a/nebo delegovaného podílu indexeru je přidělena na nasazení podgrafu, což jim umožňuje nárokovat si odměny za indexování a obsluhovat dotazy pro toto nasazení podgrafu. Agent indexeru spravuje vytváření alokací na základě pravidel indexeru.
 

From 3b712e5f5c08f2491cf31e5e68cdbe8d089d12d2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:11 -0500
Subject: [PATCH 0776/1325] New translations indexing.mdx (German)

---
 website/pages/de/network/indexing.mdx | 42 +++++++++++++--------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/website/pages/de/network/indexing.mdx b/website/pages/de/network/indexing.mdx
index 68a96556ac68..3b704381d0f0 100644
--- a/website/pages/de/network/indexing.mdx
+++ b/website/pages/de/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Many of the community-made dashboards include pending rewards values and they can be easily checked manually by following these steps:
 
-1. Query the [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) to get the IDs for all active allocations:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -113,11 +113,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.
 
 | Konfiguration | Postgres<br />(CPUs) | Postgres<br />(Speicher in GB) | Postgres<br />(Festplatte in TB) | VMs<br />(CPUs) | VMs<br />(Speicher in GB) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Klein | 4 | 8 | 1 | 4 | 16 |
-| Standard | 8 | 30 | 1 | 12 | 48 |
-| Mittel | 16 | 64 | 2 | 32 | 64 |
-| Groß | 72 | 468 | 3.5 | 48 | 184 |
+| ------------- |:--------------------------:|:------------------------------------:|:--------------------------------------:|:---------------------:|:-------------------------------:|
+| Klein         |             4              |                  8                   |                   1                    |           4           |               16                |
+| Standard      |             8              |                  30                  |                   1                    |          12           |               48                |
+| Mittel        |             16             |                  64                  |                   2                    |          32           |               64                |
+| Groß          |             72             |                 468                  |                  3.5                   |          48           |               184               |
 
 ### What are some basic security precautions an Indexer should take?
 
@@ -149,20 +149,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer
 
 #### Der Graph-Knoten
 
-| Port | Zweck | Routen | CLI-Argument | Umgebungsvariable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(für Subgraf-Abonnements) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(zum Verwalten von Deployments) | / | --admin-port | - |
-| 8030 | Subgraf-Indizierungsstatus-API | /graphql | --index-node-port | - |
-| 8040 | Prometheus-Metriken | /metrics | --metrics-port | - |
+| Port | Zweck                                                 | Routen                                               | CLI-Argument      | Umgebungsvariable |
+| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | ----------------- |
+| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                 |
+| 8001 | GraphQL WS<br />(für Subgraf-Abonnements)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                 |
+| 8020 | JSON-RPC<br />(zum Verwalten von Deployments)   | /                                                    | --admin-port      | -                 |
+| 8030 | Subgraf-Indizierungsstatus-API                        | /graphql                                             | --index-node-port | -                 |
+| 8040 | Prometheus-Metriken                                   | /metrics                                             | --metrics-port    | -                 |
 
 #### Indexer Service
 
-| Port | Zweck | Routen | CLI-Argument | Umgebungsvariable |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL-HTTP-Server<br />(für kostenpflichtige Subgraf-Abfragen) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus-Metriken | /metrics | --metrics-port | - |
+| Port | Zweck                                                                  | Routen                                                                  | CLI-Argument   | Umgebungsvariable      |
+| ---- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL-HTTP-Server<br />(für kostenpflichtige Subgraf-Abfragen) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus-Metriken                                                    | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### The life of an allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 75899f79fc4811906dea3ce9e81ba3da09c7b746 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:12 -0500
Subject: [PATCH 0777/1325] New translations indexing.mdx (Italian)

---
 website/pages/it/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/it/network/indexing.mdx b/website/pages/it/network/indexing.mdx
index 8f09a9794a7e..183041694bb7 100644
--- a/website/pages/it/network/indexing.mdx
+++ b/website/pages/it/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Molte delle dashboard create dalla comunità includono i valori delle ricompense in sospeso, che possono essere facilmente controllate manualmente seguendo questi passaggi:
 
-1. Fare query su [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) per ottenere gli ID di tutte le allocazioni attive:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Gli Indexer possono differenziarsi applicando tecniche avanzate per prendere dec
 - **Medio** - Indexer di produzione che supporta 100 subgraph e 200-500 richieste al secondo.
 - **Grande** - È pronto a indicizzare tutti i subgraph attualmente utilizzati e a servire le richieste per il relativo traffico.
 
-| Setup | Postgres<br />(CPUs) | Postgres<br />(memoria in GBs) | Postgres<br />(disco in TBs) | VMs<br />(CPUs) | VMs<br />(memoria in GBs) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Piccolo | 4 | 8 | 1 | 4 | 16 |
-| Standard | 8 | 30 | 1 | 12 | 48 |
-| Medio | 16 | 64 | 2 | 32 | 64 |
-| Grande | 72 | 468 | 3.5 | 48 | 184 |
+| Setup    | Postgres<br />(CPUs) | Postgres<br />(memoria in GBs) | Postgres<br />(disco in TBs) | VMs<br />(CPUs) | VMs<br />(memoria in GBs) |
+| -------- |:--------------------------:|:------------------------------------:|:----------------------------------:|:---------------------:|:-------------------------------:|
+| Piccolo  |             4              |                  8                   |                 1                  |           4           |               16                |
+| Standard |             8              |                  30                  |                 1                  |          12           |               48                |
+| Medio    |             16             |                  64                  |                 2                  |          32           |               64                |
+| Grande   |             72             |                 468                  |                3.5                 |          48           |               184               |
 
 ### Quali sono le precauzioni di base per la sicurezza che un Indexer dovrebbe adottare?
 
@@ -149,20 +149,20 @@ Nota: Per supportare una scalabilità agile, si consiglia di separare le attivit
 
 #### Graph Node
 
-| Porta | Obiettivo | Routes | Argomento CLI | Variabile d'ambiente |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(per la gestione dei deployment) | / | --admin-port | - |
-| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
-| 8040 | Metriche di Prometheus | /metrics | --metrics-port | - |
+| Porta | Obiettivo                                                 | Routes                                               | Argomento CLI     | Variabile d'ambiente |
+| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000  | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001  | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020  | JSON-RPC<br />(per la gestione dei deployment)      | /                                                    | --admin-port      | -                    |
+| 8030  | Subgraph indexing status API                              | /graphql                                             | --index-node-port | -                    |
+| 8040  | Metriche di Prometheus                                    | /metrics                                             | --metrics-port    | -                    |
 
 #### Servizio Indexer
 
-| Porta | Obiettivo | Routes | Argomento CLI | Variabile d'ambiente |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP server<br />(per le query di subgraph a pagamento) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Metriche di Prometheus | /metrics | --metrics-port | - |
+| Porta | Obiettivo                                                             | Routes                                                                  | Argomento CLI  | Variabile d'ambiente   |
+| ----- | --------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600  | GraphQL HTTP server<br />(per le query di subgraph a pagamento) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300  | Metriche di Prometheus                                                | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ Il **Indexer CLI** si connette all'Indexer Agent, in genere tramite port-forward
 
 - `graph indexer rules maybe [options] <deployment-id>` — Impostare il `decisionBasis` per una distribuzione a `rules`, in modo che l' Indexer agent utilizzi le regole di indicizzazione per decidere se indicizzare questa distribuzione.
 
-- `graph indexer actions get [options] <action-id>` - Recuperare una o più azioni utilizzando `all` oppure lasciare `action-id` vuoto per ottenere tutte le azioni. Un'argomento aggiuntivo `--status` può essere usato per stampare tutte le azioni di un certo stato.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Azione di allocation della coda
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### La vita di un'allocazione
 
-Dopo essere stata creata da un Indexer, un'allocazione sana passa attraverso quattro stati.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 14a5518752607b86c4a7984bb631837a0e8598af Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:14 -0500
Subject: [PATCH 0778/1325] New translations indexing.mdx (Japanese)

---
 website/pages/ja/network/indexing.mdx | 48 +++++++++++++--------------
 1 file changed, 24 insertions(+), 24 deletions(-)

diff --git a/website/pages/ja/network/indexing.mdx b/website/pages/ja/network/indexing.mdx
index f7047e258c61..a1202e884ecc 100644
--- a/website/pages/ja/network/indexing.mdx
+++ b/website/pages/ja/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 コミュニティが作成したダッシュボードの多くには保留中の報酬値が含まれており、次の手順に従って手動で簡単に確認できます。
 
-1. [メインネット・サブグラフ](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet)にクエリして、全てのアクティブなアロケーションの ID を取得します。
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Use Etherscan to call `getRewards()`:
 - **Medium** - 100 個のサブグラフと 1 秒あたり 200 ～ 500 のリクエストをサポートするプロダクションインデクサー
 - **Large** - 現在使用されているすべてのサブグラフのインデックスを作成し、関連するトラフィックのリクエストに対応します
 
-| Setup | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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               |
 
 ### インデクサーが取るべきセキュリティ対策は？
 
@@ -149,20 +149,20 @@ Use Etherscan to call `getRewards()`:
 
 #### グラフノード
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC <br /> (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 <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC <br /> (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 <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Port | Purpose                                                      | Routes                                                                      | CLI Argument   | Environment Variable   |
+| ---- | ------------------------------------------------------------ | --------------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                           | /metrics                                                                    | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -476,7 +476,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -511,7 +511,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -544,7 +544,7 @@ graph indexer status
 
 - `graph indexer rules maybe [options] <deployment-id>` - 配置の`thedecisionBasis` を`rules`に設定し、インデクサーエージェントがインデキシングルールを使用して、この配置にインデックスを作成するかどうかを決定するようにします。
 
-- `graph indexer actions get [options] <action-id>` - `all` を使って一つ以上のアクションを取得するか、 `action-id` を空にすると全てのアクションを取得します。追加引数 `--status` は、特定のステータスのアクションをすべて出力するために使用されます。
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - キューの割り当てアクション。
 
@@ -730,10 +730,10 @@ default => 0.1 * $SYSTEM_LOAD;
 
 上記のモデルを使用したクエリのコスト計算の例:
 
-| クエリ                                                                       | 価格    |
+| クエリ                                                                          | 価格      |
 | ---------------------------------------------------------------------------- | ------- |
 | &#123; pairs(skip: 5000) &#123; id &#125; &#125;                             | 0.5 GRT |
-| &#123; トークン &#123; シンボル &#125; &#125;                                | 0.1 GRT |
+| &#123; トークン &#123; シンボル &#125; &#125;                                        | 0.1 GRT |
 | &#123; pairs(skip: 5000) &#123; id &#125; tokens &#123; symbol &#125; &#125; | 0.6 GRT |
 
 #### コストモデルの適用
@@ -809,7 +809,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### アロケーションの寿命
 
-インデクサーによって作成された後、健全なアロケーションは 4 つの状態を経ます。
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From c2e007a1bb2f3093e16c7e0a99572e52f16fdca1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:15 -0500
Subject: [PATCH 0779/1325] New translations indexing.mdx (Korean)

---
 website/pages/ko/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/ko/network/indexing.mdx b/website/pages/ko/network/indexing.mdx
index 77013e86a790..0eb017b5be3f 100644
--- a/website/pages/ko/network/indexing.mdx
+++ b/website/pages/ko/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Many of the community-made dashboards include pending rewards values and they can be easily checked manually by following these steps:
 
-1. Query the [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) to get the IDs for all active allocations:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Port | Purpose                                                    | Routes                                                                  | CLI Argument   | Environment Variable   |
+| ---- | ---------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### The life of an allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 518f5fb80f8b8e814a66583cc26c61b651ceb4e5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:16 -0500
Subject: [PATCH 0780/1325] New translations indexing.mdx (Dutch)

---
 website/pages/nl/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/nl/network/indexing.mdx b/website/pages/nl/network/indexing.mdx
index da03dc3c88d9..40c0fc8f131e 100644
--- a/website/pages/nl/network/indexing.mdx
+++ b/website/pages/nl/network/indexing.mdx
@@ -42,7 +42,7 @@ Het RewardsManager-contract heeft een read-only [getRewards](https://github.com/
 
 Veel van de door de community gemaakte dashboards bevatten waarden van ongerealiseerde beloningen en ze kunnen gemakkelijk handmatig worden gecontroleerd door deze stappen te volgen:
 
-1. Query de [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) om de ID's te krijgen voor alle actieve allocaties:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Indexeerders kunnen zich onderscheiden door geavanceerde technieken toe te passe
 - **Middel** - Indexer die 100 subgraphs ondersteund en 200-500 query's per seconde verwerkt.
 - **Groot** - Voorbereid om alle momenteel gebruikte subgraphs te indexeren en de bijbehorende query's te verwerken.
 
-| Setup | Postgres<br />(CPUs) | Postgres<br />(Geheugen in GBs) | Postgres<br />(schijf in TBs) | VMs<br />(CPUs) | VMs<br />(geheugen in GBs) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Klein | 4 | 8 | 1 | 4 | 16 |
-| Standaard | 8 | 30 | 1 | 12 | 48 |
-| Middel | 16 | 64 | 2 | 32 | 64 |
-| Groot | 72 | 468 | 3.5 | 48 | 184 |
+| Setup     | Postgres<br />(CPUs) | Postgres<br />(Geheugen in GBs) | Postgres<br />(schijf in TBs) | VMs<br />(CPUs) | VMs<br />(geheugen in GBs) |
+| --------- |:--------------------------:|:-------------------------------------:|:-----------------------------------:|:---------------------:|:--------------------------------:|
+| Klein     |             4              |                   8                   |                  1                  |           4           |                16                |
+| Standaard |             8              |                  30                   |                  1                  |          12           |                48                |
+| Middel    |             16             |                  64                   |                  2                  |          32           |                64                |
+| Groot     |             72             |                  468                  |                 3.5                 |          48           |               184                |
 
 ### Wat zijn enkele basisveiligheidsmaatregelen die een Indexeerder moet nemen?
 
@@ -149,20 +149,20 @@ Tip: Om wendbare schaalvergroting te ondersteunen, wordt aanbevolen om Query- en
 
 #### Graph Node
 
-| Poort | Doel | Routes | CLI-Argument | Omgevingsvariabele |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(voor subgraph query's) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(voor subgraph abonnementen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(voor het beheren van implementaties) | / | --admin-port | - |
-| 8030 | Subgraph indexeerstatus API | /graphql | --index-node-port | - |
-| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
+| Poort | Doel                                                      | Routes                                               | CLI-Argument      | Omgevingsvariabele |
+| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
+| 8000  | GraphQL HTTP server<br />(voor subgraph query's)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
+| 8001  | GraphQL WS<br />(voor subgraph abonnementen)        | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
+| 8020  | JSON-RPC<br />(voor het beheren van implementaties) | /                                                    | --admin-port      | -                  |
+| 8030  | Subgraph indexeerstatus API                               | /graphql                                             | --index-node-port | -                  |
+| 8040  | Prometheus metrics                                        | /metrics                                             | --metrics-port    | -                  |
 
 #### Indexer Service
 
-| Poort | Doel | Routes | CLI-Argument | Omgevingsvariabele |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP server<br />(voor betaalde subgraph query's) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Poort | Doel                                                            | Routes                                                                  | CLI-Argument   | Omgevingsvariabele     |
+| ----- | --------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600  | GraphQL HTTP server<br />(voor betaalde subgraph query's) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300  | Prometheus metrics                                              | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### The life of an allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 2e0d4f6258828ac07e909796d4ab2da377079d91 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:17 -0500
Subject: [PATCH 0781/1325] New translations indexing.mdx (Polish)

---
 website/pages/pl/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/pl/network/indexing.mdx b/website/pages/pl/network/indexing.mdx
index 77013e86a790..0eb017b5be3f 100644
--- a/website/pages/pl/network/indexing.mdx
+++ b/website/pages/pl/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Many of the community-made dashboards include pending rewards values and they can be easily checked manually by following these steps:
 
-1. Query the [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) to get the IDs for all active allocations:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Port | Purpose                                                    | Routes                                                                  | CLI Argument   | Environment Variable   |
+| ---- | ---------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### The life of an allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 4aaeed056c4aadff957ca26119ef51eb625451a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:19 -0500
Subject: [PATCH 0782/1325] New translations indexing.mdx (Portuguese)

---
 website/pages/pt/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/pt/network/indexing.mdx b/website/pages/pt/network/indexing.mdx
index 9542ff878e3d..36e588e4237e 100644
--- a/website/pages/pt/network/indexing.mdx
+++ b/website/pages/pt/network/indexing.mdx
@@ -42,7 +42,7 @@ O contrato RewardsManager tem uma função [getRewards](https://github.com/graph
 
 Muitos dos painéis feitos pela comunidade incluem valores pendentes de recompensas, que podem facilmente ser conferidos de forma manual ao seguir os seguintes passos:
 
-1. Consulte a [subgraph da mainnet](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) para conseguir as IDs de todas as alocações ativas:
+1. Consulte o [subgraph da mainnet](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) para conseguir as IDs para todas as alocações ativas:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Os Indexadores podem se diferenciar ao aplicar técnicas avançadas para decidir
 - **Médio** — Indexador de Produção. Apoia 100 subgraphs e 200 – 500 pedidos por segundo.
 - **Grande** — Preparado para indexar todos os subgraphs usados atualmente e servir pedidos para o tráfego relacionado.
 
-| Setup | Postgres<br />(CPUs) | Postgres<br />(memória em GBs) | Postgres<br />(disco em TBs) | VMs<br />(CPUs) | VMs<br />(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 |
+| Setup   | Postgres<br />(CPUs) | Postgres<br />(memória em GBs) | Postgres<br />(disco em TBs) | VMs<br />(CPUs) | VMs<br />(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               |
 
 ### Há alguma precaução básica de segurança que um Indexador deve tomar?
 
@@ -149,20 +149,20 @@ Nota: Para apoiar o escalamento ágil, recomendamos que assuntos de consulta e i
 
 #### Graph Node
 
-| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente |
-| --- | --- | --- | --- | --- |
-| 8000 | Servidor HTTP GraphQL<br />(para consultas de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | WS GraphQL<br />(para inscrições a subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(para gerir lançamentos) | / | --admin-port | - |
-| 8030 | API de status de indexamento 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<br />(para consultas de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001  | WS GraphQL<br />(para inscrições a subgraphs)           | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020  | JSON-RPC<br />(para gerir lançamentos)                  | /                                                    | --admin-port      | -                    |
+| 8030  | API de status de indexamento 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<br />(para consultas de subgraph pagas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| Porta | Propósito                                                           | Rotas                                                                   | Argumento CLI  | Variável de Ambiente   |
+| ----- | ------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600  | Servidor HTTP GraphQL<br />(para consultas de subgraph pagas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300  | Prometheus metrics                                                  | /metrics                                                                | --metrics-port | -                      |
 
 #### Agente Indexador
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ O **Indexer CLI** se conecta ao agente indexador, normalmente através do redire
 
 - `graph indexer rules maybe [options] <deployment-id>` — Configura a `decisionBasis` de um lançamento para obedecer o `rules`, comandando o agente indexador a usar regras de indexação para decidir se este lançamento será ou não indexado.
 
-- `graph indexer actions get [options] <action-id>` - Retira uma ou mais ações usando o `all`, ou deixa o `action-id` vazio para mostrar todas as ações. Um argumento adicional `--status` pode ser usado para imprimir no console todas as ações de um certo status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Fila da ação de alocação
 
@@ -811,7 +811,7 @@ Para configurar os parâmetros de delegação com a interface do Graph Explorer,
 
 ### A vida de uma alocação
 
-Após criada por um Indexador, uma alocação sadia passa por quatro estados.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Ativa** - Quando uma alocação é criada on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)), ela é considerada **ativa**. Uma porção do stake próprio e/ou delegado do Indexador é alocada a um lançamento de subgraph, que lhe permite resgatar recompensas de indexação e servir queries para aquele lançamento de subgraph. O agente indexador cria alocações baseada nas regras do Indexador.
 

From 1739e2adb5591f33a6db6fc7b3b3cc6303623edb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:20 -0500
Subject: [PATCH 0783/1325] New translations indexing.mdx (Russian)

---
 website/pages/ru/network/indexing.mdx | 48 +++++++++++++--------------
 1 file changed, 24 insertions(+), 24 deletions(-)

diff --git a/website/pages/ru/network/indexing.mdx b/website/pages/ru/network/indexing.mdx
index 56c4ddfb288b..978878e51f41 100644
--- a/website/pages/ru/network/indexing.mdx
+++ b/website/pages/ru/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Многие панели мониторинга, созданные сообществом, содержат ожидающие значения вознаграждений, и их можно легко проверить вручную, выполнив следующие действия:
 
-1. Запросите [подграф в основной сети](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet), чтобы получить идентификаторы всех активных распределений:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -113,11 +113,11 @@ Once an allocation has been closed the rebates are available to be claimed by th
 - **Large** – готовность индексировать все используемые в настоящее время подграфы и обслуживать запросы на соответствующий трафик.
 
 | Настройка | Postgres<br />(ЦП) | Postgres<br />(память в ГБ) | Postgres<br />(диск в ТБ) | VMs<br />(ЦП) | VMs<br />(память в ГБ) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| 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              |
 
 ### Какие основные меры безопасности следует предпринять индексатору?
 
@@ -149,26 +149,26 @@ Once an allocation has been closed the rebates are available to be claimed by th
 
 #### Graph Node
 
-| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
-| --- | --- | --- | --- | --- |
-| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(для подписок на подграфы) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(для управления процессом развертывания) | / | --admin-port | - |
-| 8030 | API для определения статуса индексирования подграфов | /graphql | --index-node-port | - |
-| 8040 | Показатели Prometheus | /metrics | --metrics-port | - |
+| Порт | Назначение                                                   | Расположение                                         | CLI-аргумент      | Переменная среды |
+| ---- | ------------------------------------------------------------ | ---------------------------------------------------- | ----------------- | ---------------- |
+| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                |
+| 8001 | GraphQL WS<br />(для подписок на подграфы)             | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                |
+| 8020 | JSON-RPC<br />(для управления процессом развертывания) | /                                                    | --admin-port      | -                |
+| 8030 | API для определения статуса индексирования подграфов         | /graphql                                             | --index-node-port | -                |
+| 8040 | Показатели Prometheus                                        | /metrics                                             | --metrics-port    | -                |
 
 #### Indexer Service
 
-| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
-| --- | --- | --- | --- | --- |
-| 7600 | HTTP-сервер GraphQL<br />(для платных запросов к подграфам) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Показатели Prometheus | /metrics | --metrics-port | - |
+| Порт | Назначение                                                        | Расположение                                                            | CLI-аргумент   | Переменная среды       |
+| ---- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | HTTP-сервер GraphQL<br />(для платных запросов к подграфам) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Показатели Prometheus                                             | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
-| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
-| --- | --- | --- | --- | --- |
-| 8000 | API для управления индексатором | / | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+| Порт | Назначение                      | Расположение | CLI-аргумент              | Переменная среды                        |
+| ---- | ------------------------------- | ------------ | ------------------------- | --------------------------------------- |
+| 8000 | API для управления индексатором | /            | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
 
 ### Настройка серверной инфраструктуры с помощью Terraform в Google Cloud
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ graph indexer status
 
 - `graph indexer rules maybe [options] <deployment-id>` — установите для развертывания `decisionBasis` значение `rules`, чтобы Indexer agent смог применить правила индексирования с целью решить, следует ли индексировать это развертывание.
 
-- `graph indexer actions get [options] <action-id>` – выберите одно или несколько действий, используя `all`, или оставьте `action-id` пустым, чтобы получить все действия. Дополнительный аргумент `--status` может использоваться для вывода всех действий для определенного статуса.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` – действие по распределению аллокаций в виде очереди
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### Срок существования аллокации
 
-После создания индексатором распределение проходит четыре состояния.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 494708daf50a8f580d49ea79f9de334de1702cfd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:21 -0500
Subject: [PATCH 0784/1325] New translations indexing.mdx (Swedish)

---
 website/pages/sv/network/indexing.mdx | 42 +++++++++++++--------------
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/website/pages/sv/network/indexing.mdx b/website/pages/sv/network/indexing.mdx
index 034d5742ef06..c249ed8f3404 100644
--- a/website/pages/sv/network/indexing.mdx
+++ b/website/pages/sv/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Många av gemenskapens egentillverkade instrument inkluderar värden för väntande belöningar och de kan enkelt kontrolleras manuellt genom att följa dessa steg:
 
-1. Fråga [mainnet-subgrafen](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) för att få ID:n för alla aktiva tilldelningar:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -113,11 +113,11 @@ Indexers kan skilja sig åt genom att tillämpa avancerade tekniker för att fat
 - **Stor** - Förberedd för att indexera alla för närvarande använda subgrafer och att ta emot förfrågningar för relaterad trafik.
 
 | Konfiguration | Postgres<br />(CPU:er) | Postgres<br />(minne i GB) | Postgres<br />(disk i TB) | VM:er<br />(CPU:er) | VM:er<br />(minne i GB) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Liten | 4 | 8 | 1 | 4 | 16 |
-| Standard | 8 | 30 | 1 | 12 | 48 |
-| Medium | 16 | 64 | 2 | 32 | 64 |
-| Stor | 72 | 468 | 3,5 | 48 | 184 |
+| ------------- |:----------------------------:|:--------------------------------:|:-------------------------------:|:-------------------------:|:-----------------------------:|
+| Liten         |              4               |                8                 |                1                |             4             |              16               |
+| Standard      |              8               |                30                |                1                |            12             |              48               |
+| Medium        |              16              |                64                |                2                |            32             |              64               |
+| Stor          |              72              |               468                |               3,5               |            48             |              184              |
 
 ### Vilka grundläggande säkerhetsåtgärder bör en Indexer vidta?
 
@@ -149,20 +149,20 @@ Observera: För att stödja smidig skalning rekommenderas det att fråge- och in
 
 #### Graf Node
 
-| Port | Syfte | Vägar | CLI-argument | Miljövariabel |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP-server<br />(för subgraf-förfrågningar) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(för subgraf-prenumerationer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(för hantering av distributioner) | / | --admin-port | - |
-| 8030 | Subgrafindexeringsstatus-API | /graphql | --index-node-port | - |
-| 8040 | Prometheus-metrar | /metrics | --metrics-port | - |
+| Port | Syfte                                                      | Vägar                                                | CLI-argument      | Miljövariabel |
+| ---- | ---------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------- |
+| 8000 | GraphQL HTTP-server<br />(för subgraf-förfrågningar) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -             |
+| 8001 | GraphQL WS<br />(för subgraf-prenumerationer)        | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -             |
+| 8020 | JSON-RPC<br />(för hantering av distributioner)      | /                                                    | --admin-port      | -             |
+| 8030 | Subgrafindexeringsstatus-API                               | /graphql                                             | --index-node-port | -             |
+| 8040 | Prometheus-metrar                                          | /metrics                                             | --metrics-port    | -             |
 
 #### Indexertjänst
 
-| Port | Syfte | Vägar | CLI-argument | Miljövariabel |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP-server<br />(för betalda subgraf-förfrågningar) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus-metrar | /metrics | --metrics-port | - |
+| Port | Syfte                                                              | Vägar                                                                   | CLI-argument   | Miljövariabel          |
+| ---- | ------------------------------------------------------------------ | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP-server<br />(för betalda subgraf-förfrågningar) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus-metrar                                                  | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexeragent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ Det föreslagna verktyget för att interagera med **Indexer Management API** är
 
 - `graph indexer rules maybe [options] <deployment-id>` — Ange `decisionBasis` för en distribution till `rules`, så kommer Indexeragenten att använda indexeringsregler för att avgöra om den ska indexera den här distributionen.
 
-- `graph indexer actions get [options] <action-id>` - Hämta en eller flera åtgärder med `all` eller lämna `action-id` tomt för att hämta alla åtgärder. Ett ytterligare argument `--status` kan användas för att skriva ut alla åtgärder med en viss status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Köa allokationsåtgärd
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### En allokations livscykel
 
-Efter att ha skapats av en Indexer går en sund allokering igenom fyra tillstånd.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 30047fd073c9faf77cb7882a5a64869a5d1e4234 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:23 -0500
Subject: [PATCH 0785/1325] New translations indexing.mdx (Ukrainian)

---
 website/pages/uk/network/indexing.mdx | 48 +++++++++++++--------------
 1 file changed, 24 insertions(+), 24 deletions(-)

diff --git a/website/pages/uk/network/indexing.mdx b/website/pages/uk/network/indexing.mdx
index 56860303c428..8c30f75568e8 100644
--- a/website/pages/uk/network/indexing.mdx
+++ b/website/pages/uk/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Багато інформаційних панелей, створених спільнотою, містять очікувані значення винагород, і їх можна легко перевірити вручну, виконавши ці кроки:
 
-1. Надішліть запит на [підграф в основній мережі](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet), щоб отримати ідентифікатори всіх активних розподілів:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 запит indexerAllocations {
@@ -113,11 +113,11 @@ Query fees are collected by the gateway and distributed to indexers according to
 - **Large** - підготовлений для індексації всіх підграфів, що використовуються наразі, і обслуговування запитів на відповідний трафік.
 
 | Налаштування | Postgres<br />(CPU) | Postgres<br />(пам'ять в GB) | Postgres<br />(диск у ТБ) | VMs<br />(Центральні CPU) | VMs<br />(пам'ять у ГБ) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| 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              |
 
 ### Яких основних заходів безпеки повинен дотримуватися індексатор?
 
@@ -149,26 +149,26 @@ Query fees are collected by the gateway and distributed to indexers according to
 
 #### Graph Node
 
-| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
-| --- | --- | --- | --- | --- |
-| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт | - |
-| 8001 | GraphQL WS<br />(для підписок на підграфи) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(для керування розгортаннями) | / | --admin-port | - |
-| 8030 | API стану індексації підграфів | /graphql | --index-node-port | - |
-| 8040 | Метрики Prometheus | /metrics | --metrics-port | - |
+| Порт | Призначення                                               | Розташування                                         | Аргумент CLI      | Перемінна оточення |
+| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
+| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт       | -                  |
+| 8001 | GraphQL WS<br />(для підписок на підграфи)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
+| 8020 | JSON-RPC<br />(для керування розгортаннями)         | /                                                    | --admin-port      | -                  |
+| 8030 | API стану індексації підграфів                            | /graphql                                             | --index-node-port | -                  |
+| 8040 | Метрики Prometheus                                        | /metrics                                             | --metrics-port    | -                  |
 
 #### Служба індексації
 
-| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
-| --- | --- | --- | --- | --- |
-| 7600 | HTTP-сервер GraphQL<br />(для платних запитів до підграфів) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Метрики Prometheus | /metrics | --metrics-port | - |
+| Порт | Призначення                                                       | Розташування                                                            | Аргумент CLI   | Перемінна оточення     |
+| ---- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | HTTP-сервер GraphQL<br />(для платних запитів до підграфів) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Метрики Prometheus                                                | /metrics                                                                | --metrics-port | -                      |
 
 #### Агент індексації
 
-| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
-| --- | --- | --- | --- | --- |
-| 8000 | API для керування індексатором | / | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+| Порт | Призначення                    | Розташування | Аргумент CLI              | Перемінна оточення                      |
+| ---- | ------------------------------ | ------------ | ------------------------- | --------------------------------------- |
+| 8000 | API для керування індексатором | /            | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
 
 ### Налаштування серверної інфраструктури з використанням Terraform на Google Cloud
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ graph indexer status
 
 - `graph indexer rules maybe [options] <deployment-id>` — установіть `decisionBasis` для розгортання на `rules`, щоб агент індексатора використовував правила індексування, щоб вирішити, чи індексувати це розгортання.
 
-- `graph indexer actions get [options] <action-id>` - отримання однієї або декількох дій за допомогою `all` або можливість залишити `action-id` пустим, щоб отримати всі дії. Додатковий аргумент `--status` можна використовувати для виведення всіх дій певного статусу.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` – розподіл черги
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### Термін розподілу
 
-Після створення індексатором правильний розподіл проходить через чотири стани.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From d9a3842820b9a266d0160ffa81f0d9a2e7abe8b2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:24 -0500
Subject: [PATCH 0786/1325] New translations indexing.mdx (Chinese Simplified)

---
 website/pages/zh/network/indexing.mdx | 51 ++++++++++++++-------------
 1 file changed, 26 insertions(+), 25 deletions(-)

diff --git a/website/pages/zh/network/indexing.mdx b/website/pages/zh/network/indexing.mdx
index 36d5e4858150..9451572c8438 100644
--- a/website/pages/zh/network/indexing.mdx
+++ b/website/pages/zh/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 许多社区制作的仪表板包含悬而未决的奖励值，通过以下步骤可以很容易地手动检查这些值:
 
-1. 查询[主网子图](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) 以获取所有活动分配的 ID：
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -113,11 +113,11 @@ Query fees are collected by the gateway and distributed to indexers according to
 - **大型** -准备对当前使用的所有子图进行索引，并为相关流量的请求提供服务。
 
 | 设置 | (CPU 数量) | (内存 GB) | (硬盘 TB) | (CPU 数量) | (内存 GB) |
-| ---- | :--------: | :-------: | :-------: | :--------: | :-------: |
-| 小型 |     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   |
 
 ### 索引人应该采取哪些基本的安全防范措施？
 
@@ -149,26 +149,26 @@ Query fees are collected by the gateway and distributed to indexers according to
 
 #### Graph 节点
 
-| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS <br />（用于子图订阅） | /subgraphs/id/... <br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC <br />（用于管理部署） | / | --admin-port | - |
-| 8030 | 子图索引状态 API | /graphql | --index-node-port | - |
-| 8040 | Prometheus 指标 | /metrics | --metrics-port | - |
+| 端口   | 用途                                   | 路径                                                                  | CLI 参数            | 环境 变量 |
+| ---- | ------------------------------------ | ------------------------------------------------------------------- | ----------------- | ----- |
+| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port       | -     |
+| 8001 | GraphQL WS <br />（用于子图订阅）      | /subgraphs/id/... <br />/subgraphs/name/.../...               | --ws-port         | -     |
+| 8020 | JSON-RPC <br />（用于管理部署）        | /                                                                   | --admin-port      | -     |
+| 8030 | 子图索引状态 API                           | /graphql                                                            | --index-node-port | -     |
+| 8040 | Prometheus 指标                        | /metrics                                                            | --metrics-port    | -     |
 
 #### 索引人服务
 
-| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP 服务器<br /> （用于付费子图查询） | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus 指标 | /metrics | --metrics-port | - |
+| 端口   | 用途                                      | 路径                                                                          | CLI 参数         | 环境 变量                  |
+| ---- | --------------------------------------- | --------------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP 服务器<br /> （用于付费子图查询） | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus 指标                           | /metrics                                                                    | --metrics-port | -                      |
 
 #### 索引人代理
 
-| 端口 | 用途           | 路径 | CLI 参数                  | 环境 变量                               |
-| ---- | -------------- | ---- | ------------------------- | --------------------------------------- |
-| 8000 | 索引人管理 API | /    | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+| 端口   | 用途        | 路径 | CLI 参数                    | 环境 变量                                   |
+| ---- | --------- | -- | ------------------------- | --------------------------------------- |
+| 8000 | 索引人管理 API | /  | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
 
 ### 在谷歌云上使用 Terraform 建立服务器基础设施
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -486,6 +486,7 @@ graph-indexer-agent start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database indexer \
+  --allocation-management auto \
   | pino-pretty
 ```
 
@@ -511,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -544,7 +545,7 @@ graph indexer status
 
 - `graph indexer rules maybe [options] <deployment-id>` —将部署的 `thedecisionBasis`设置为`规则`, 这样索引人代理将使用索引规则来决定是否对这个部署进行索引。
 
-- `graph indexer actions get [options] <action-id>`使用 `all` 获取一个或多个操作，或者将 `action-id` 保持为空以获取所有操作。一个附加的参数—— `status` 可以用来打印出某个状态的所有操作。
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` -队列分配操作
 
@@ -730,7 +731,7 @@ default => 0.1 * $SYSTEM_LOAD;
 
 使用上述模型的查询成本计算示例：
 
-| 询问                                                                         | 价格    |
+| 询问                                                                           | 价格      |
 | ---------------------------------------------------------------------------- | ------- |
 | &#123; pairs(skip: 5000) &#123; id &#125; &#125;                             | 0.5 GRT |
 | &#123; tokens &#123; symbol &#125; &#125;                                    | 0.1 GRT |
@@ -809,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### 分配的生命周期
 
-在被索引人创建之后，健康的分配会经历四个状态。
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 879a7e6fa98d8cdbc0b8d6fec40489af1227787c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:25 -0500
Subject: [PATCH 0787/1325] New translations indexing.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/ur/network/indexing.mdx b/website/pages/ur/network/indexing.mdx
index f640a613ae68..59933c810c92 100644
--- a/website/pages/ur/network/indexing.mdx
+++ b/website/pages/ur/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 کمیونٹی کے بنائے ہوئے بہت سے ڈیش بورڈز میں زیر التواء انعامات کی قدریں شامل ہیں اور ان اقدامات پر عمل کر کے انہیں آسانی سے دستی طور پر چیک کیا جا سکتا ہے:
 
-1. تمام فعال ایلوکیشنز کی IDs حاصل کرنے کے لیے [mainnet سب گراف](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) کو کیوری کریں:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ query indexerAllocations {
 - **درمیانہ** - پروڈکشن انڈیکسر 100 سب گراف اور 200-500 درخواستیں فی سیکنڈ کو اٹھا سکتا ہے.
 - **بڑا** - تمام فی الحال زیر استعمال سب گرافس کو انڈیکس کرنے اور متعلقہ ٹریفک کے لیے درخواستیں پیش کرنے کے لیے تیار ہے.
 
-| سیٹ اپ | Postgres<br />(CPUs) | Postgres<br />(GBs میں میموری) | Postgres<br />(TBs میں ڈسک) | VMs<br />(CPUs) | VMs<br />(GBs میں میموری) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| چھوٹا | 4 | 8 | 1 | 4 | 16 |
-| معیاری | 8 | 30 | 1 | 12 | 48 |
-| درمیانہ | 16 | 64 | 2 | 32 | 64 |
-| بڑا | 72 | 468 | 3.5 | 48 | 184 |
+| سیٹ اپ  | Postgres<br />(CPUs) | Postgres<br />(GBs میں میموری) | Postgres<br />(TBs میں ڈسک) | VMs<br />(CPUs) | VMs<br />(GBs میں میموری) |
+| ------- |:--------------------------:|:------------------------------------:|:---------------------------------:|:---------------------:|:-------------------------------:|
+| چھوٹا   |             4              |                  8                   |                 1                 |           4           |               16                |
+| معیاری  |             8              |                  30                  |                 1                 |          12           |               48                |
+| درمیانہ |             16             |                  64                  |                 2                 |          32           |               64                |
+| بڑا     |             72             |                 468                  |                3.5                |          48           |               184               |
 
 ### وہ کون سی چند بنیادی حفاظتی تدابیر ہیں جو ایک انڈیکسر کو اختیار کرنی چاہیے؟
 
@@ -149,20 +149,20 @@ query indexerAllocations {
 
 #### گراف نوڈ
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے) | / | --admin-port | - |
-| 8030 | سب گراف انڈیکسنگ اسٹیٹس API | /graphql | --index-node-port | - |
-| 8040 | Prometheus میٹرکس | /metrics | --metrics-port | - |
+| Port | Purpose                                                   | Routes                                               | CLI Argument      | Environment Variable |
+| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے)          | /                                                    | --admin-port      | -                    |
+| 8030 | سب گراف انڈیکسنگ اسٹیٹس API                               | /graphql                                             | --index-node-port | -                    |
+| 8040 | Prometheus میٹرکس                                         | /metrics                                             | --metrics-port    | -                    |
 
 #### انڈیکسر سروس
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP server<br />(ادا شدہ سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus میٹرکس | /metrics | --metrics-port | - |
+| Port | Purpose                                                           | Routes                                                                  | CLI Argument   | Environment Variable   |
+| ---- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(ادا شدہ سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus میٹرکس                                                 | /metrics                                                                | --metrics-port | -                      |
 
 #### انڈیکسر ایجنٹ
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ graph indexer status
 
 - `graph indexer rules maybe [options] <deployment-id>` — تعیناتی کے لیے `decisionBasis` کو `rules` پر سیٹ کریں، تاکہ انڈیکسر ایجنٹ یہ فیصلہ کرنے کے لیے انڈیکسنگ کے اصول استعمال کرے کہ آیا اس تعیناتی کو انڈیکس کرنا ہے.
 
-- `graph indexer actions get [options] <action-id>` - `all` کا استعمال کرتے ہوئے ایک یا زیادہ کارروائیاں حاصل کریں یا تمام کارروائیاں حاصل کرنے کے لیے `action-id` کو خالی چھوڑ دیں. ایک اضافی argument `--status` کو کسی خاص status کی تمام کارروائیاں کو پرنٹ کرنے کے لیے استعمال کیا جا سکتا ہے.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - قطار(Queue) مختص کرنے کی کارروائی
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### ایک ایلوکیشن کا دورانیہ
 
-ایک انڈیکسر کے ذریعہ بنائے جانے کے بعد ایک صحت مند ایلوکیشن چار مرحلوں سے گزرتا ہے.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From caff0ad58dc94b3d53e2a37b4428c342ce1727dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:27 -0500
Subject: [PATCH 0788/1325] New translations indexing.mdx (Vietnamese)

---
 website/pages/vi/network/indexing.mdx | 44 +++++++++++++--------------
 1 file changed, 22 insertions(+), 22 deletions(-)

diff --git a/website/pages/vi/network/indexing.mdx b/website/pages/vi/network/indexing.mdx
index fca0bd12028a..b19e9f99a983 100644
--- a/website/pages/vi/network/indexing.mdx
+++ b/website/pages/vi/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 Nhiều trang tổng quan (dashboard) do cộng đồng tạo bao gồm các giá trị phần thưởng đang chờ xử lý và bạn có thể dễ dàng kiểm tra chúng theo cách thủ công bằng cách làm theo các bước sau:
 
-1. Truy vấn [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) để nhận ID cho tất cả phần phân bổ đang hoạt động:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Indexer có thể tự phân biệt bản thân bằng cách áp dụng các k
 - **Medium** - Production Indexer supporting 100 subgraphs and 200-500 requests per second.
 - **Lớn** - Được chuẩn bị để index tất cả các subgraph hiện đang được sử dụng và phục vụ các yêu cầu cho lưu lượng truy cập liên quan.
 
-| Cài đặt | Postgres<br />(CPUs) | Postgres<br />(bộ nhớ tính bằng GB) | Postgres<br />(đĩa tính bằng TB) | VMs<br />(CPUs) | VMs<br />(bộ nhớ tính bằng GB) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Nhỏ | 4 | 8 | 1 | 4 | 16 |
-| Tiêu chuẩn | 8 | 30 | 1 | 12 | 48 |
-| Trung bình | 16 | 64 | 2 | 32 | 64 |
-| Lớn | 72 | 468 | 3.5 | 48 | 184 |
+| Cài đặt     | Postgres<br />(CPUs) | Postgres<br />(bộ nhớ tính bằng GB) | Postgres<br />(đĩa tính bằng TB) | VMs<br />(CPUs) | VMs<br />(bộ nhớ tính bằng GB) |
+| ----------- |:--------------------------:|:-----------------------------------------:|:--------------------------------------:|:---------------------:|:------------------------------------:|
+| Nhỏ         |             4              |                     8                     |                   1                    |           4           |                  16                  |
+| Tiêu chuẩn  |             8              |                    30                     |                   1                    |          12           |                  48                  |
+| Trung bình |             16             |                    64                     |                   2                    |          32           |                  64                  |
+| Lớn         |             72             |                    468                    |                  3.5                   |          48           |                 184                  |
 
 ### What are some basic security precautions an Indexer should take?
 
@@ -149,20 +149,20 @@ Lưu ý: Để hỗ trợ mở rộng quy mô nhanh, bạn nên tách các mối
 
 #### Graph Node
 
-| Cổng | Mục đích | Tuyến | Đối số CLI | Biến môi trường |
-| --- | --- | --- | --- | --- |
-| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(cho các đăng ký subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(để quản lý triển khai) | / | --admin-port | - |
-| 8030 | API trạng thái lập chỉ mục Subgraph | /graphql | --index-node-port | - |
-| 8040 | Số liệu Prometheus | /metrics | --metrics-port | - |
+| Cổng | Mục đích                                                    | Tuyến                                                | Đối số CLI        | Biến môi trường |
+| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
+| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
+| 8001 | GraphQL WS<br />(cho các đăng ký subgraph)            | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
+| 8020 | JSON-RPC<br />(để quản lý triển khai)                 | /                                                    | --admin-port      | -               |
+| 8030 | API trạng thái lập chỉ mục Subgraph                         | /graphql                                             | --index-node-port | -               |
+| 8040 | Số liệu Prometheus                                          | /metrics                                             | --metrics-port    | -               |
 
 #### Dịch vụ Indexer
 
-| Cổng | Mục đích | Tuyến | Đối số CLI | Biến môi trường |
-| --- | --- | --- | --- | --- |
-| 7600 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph có trả phí) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Số liệu Prometheus | /metrics | --metrics-port | - |
+| Cổng | Mục đích                                                               | Tuyến                                                                   | Đối số CLI     | Biến môi trường        |
+| ---- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph có trả phí) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Số liệu Prometheus                                                     | /metrics                                                                | --metrics-port | -                      |
 
 #### Đại lý Indexer
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ The **Indexer CLI** connects to the Indexer agent, typically through port-forwar
 
 - `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
 
-- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additonal argument `--status` can be used to print out all actions of a certain status.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
 
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### Tuổi thọ của một phân bổ
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From 7b63cde19312f78b0f7378fbfec37e275bfae8da Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:28 -0500
Subject: [PATCH 0789/1325] New translations indexing.mdx (Marathi)

---
 website/pages/mr/network/indexing.mdx | 46 +++++++++++++--------------
 1 file changed, 23 insertions(+), 23 deletions(-)

diff --git a/website/pages/mr/network/indexing.mdx b/website/pages/mr/network/indexing.mdx
index 93c7e0cf5b0f..4f87435bda60 100644
--- a/website/pages/mr/network/indexing.mdx
+++ b/website/pages/mr/network/indexing.mdx
@@ -42,7 +42,7 @@ The RewardsManager contract has a read-only [getRewards](https://github.com/grap
 
 समुदायाने बनवलेल्या अनेक डॅशबोर्डमध्ये प्रलंबित पुरस्कार मूल्यांचा समावेश आहे आणि ते या चरणांचे अनुसरण करून सहजपणे व्यक्तिचलितपणे तपासले जाऊ शकतात:
 
-1. Query the [mainnet subgraph](https://thegraph.com/hosted-service/subgraph/graphprotocol/graph-network-mainnet) to get the IDs for all active allocations:
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
 
 ```graphql
 query indexerAllocations {
@@ -112,12 +112,12 @@ Once an allocation has been closed the rebates are available to be claimed by th
 - **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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
-| --- | :-: | :-: | :-: | :-: | :-: |
-| Small | 4 | 8 | 1 | 4 | 16 |
-| मानक | 8 | 30 | 1 | 12 | 48 |
-| Medium | 16 | 64 | 2 | 32 | 64 |
-| Large | 72 | 468 | 3.5 | 48 | 184 |
+| Setup  | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
+| ------ |:--------------------------:|:-----------------------------------:|:---------------------------------:|:---------------------:|:------------------------------:|
+| Small  |             4              |                  8                  |                 1                 |           4           |               16               |
+| मानक   |             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?
 
@@ -149,20 +149,20 @@ Once an allocation has been closed the rebates are available to be claimed by th
 
 #### आलेख नोड
 
-| बंदर | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(for managing deployments) | / | --admin-port | - |
-| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
-| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
+| बंदर | Purpose                                               | Routes                                               | CLI Argument      | Environment Variable |
+| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(for managing deployments)        | /                                                    | --admin-port      | -                    |
+| 8030 | Subgraph indexing status API                          | /graphql                                             | --index-node-port | -                    |
+| 8040 | Prometheus metrics                                    | /metrics                                             | --metrics-port    | -                    |
 
 #### Indexer Service
 
-| बंदर | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
+| बंदर | Purpose                                                    | Routes                                                                  | CLI Argument   | Environment Variable   |
+| ---- | ---------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
 
 #### Indexer Agent
 
@@ -477,7 +477,7 @@ graph-indexer-agent start \
   --index-node-ids default \
   --indexer-management-port 18000 \
   --metrics-port 7040 \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   --default-allocation-amount 100 \
   --register true \
   --inject-dai true \
@@ -512,7 +512,7 @@ graph-indexer-service start \
   --postgres-username <DB_USERNAME> \
   --postgres-password <DB_PASSWORD> \
   --postgres-database is_staging \
-  --network-subgraph-endpoint https://gateway.network.thegraph.com/network \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
   | pino-pretty
 ```
 
@@ -545,7 +545,7 @@ graph indexer status
 
 - `ग्राफ इंडेक्सर नियम कदाचित [options] <deployment-id>` — उपयोजनासाठी `decisionBasis` सेट करा `नियम`, जेणेकरून इंडेक्सर एजंट हे उपयोजन अनुक्रमित करायचे की नाही हे ठरवण्यासाठी अनुक्रमणिका नियम वापरा.
 
-- `ग्राफ इंडेक्सर क्रियांना [options] <action-id>` मिळतात - `सर्व` वापरून एक किंवा अधिक क्रिया मिळवा किंवा मिळवण्यासाठी `action-id` रिकामे ठेवा सर्व क्रिया. विशिष्ट स्थितीच्या सर्व क्रिया मुद्रित करण्यासाठी अतिरिक्त युक्तिवाद `--status` वापरला जाऊ शकतो.
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
 
 - `ग्राफ इंडेक्सर क्रिया रांग वाटप <deployment-id> <अलोकेशन-रक्कम>` - रांग वाटप क्रिया
 
@@ -623,7 +623,7 @@ graph indexer rules delete QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
 - Indexer can use the `indexer-cli` to view all queued actions
 - इंडेक्सर (किंवा इतर सॉफ्टवेअर) `indexer-cli` वापरून रांगेतील क्रिया मंजूर किंवा रद्द करू शकतात. मंजूर आणि रद्द आदेश इनपुट म्हणून अॅक्शन आयडीचा अॅरे घेतात.
 - अंमलबजावणी कर्मचारी नियमितपणे मंजूर कृतींसाठी रांगेत मतदान करतात. ते रांगेतील `मंजूर` क्रिया पकडेल, त्या कार्यान्वित करण्याचा प्रयत्न करेल आणि अंमलबजावणीच्या स्थितीनुसार `यशस्वी` किंवा `अयशस्वी< वर db मधील मूल्ये अपडेट करेल. /code>.</li>
-  <li>एखादी कृती यशस्वी झाल्यास कार्यकर्ता खात्री करेल की एक अनुक्रमणिका नियम उपस्थित आहे जो एजंटला वाटप कसे व्यवस्थापित करावे हे सांगते, एजंट <code>ऑटो` किंवा ` मध्ये असताना मॅन्युअल क्रिया करताना उपयुक्त oversight` मोड.
+<li>एखादी कृती यशस्वी झाल्यास कार्यकर्ता खात्री करेल की एक अनुक्रमणिका नियम उपस्थित आहे जो एजंटला वाटप कसे व्यवस्थापित करावे हे सांगते, एजंट <code>ऑटो` किंवा ` मध्ये असताना मॅन्युअल क्रिया करताना उपयुक्त oversight` मोड.
 - इंडेक्सर कारवाईच्या अंमलबजावणीचा इतिहास पाहण्यासाठी कृती रांगेचे निरीक्षण करू शकतो आणि आवश्यक असल्यास क्रिया आयटमची अंमलबजावणी अयशस्वी झाल्यास पुन्हा मंजूर आणि अद्यतनित करू शकतो. कृती रांग रांगेत लावलेल्या आणि केलेल्या सर्व क्रियांचा इतिहास प्रदान करते.
 
 Data model:
@@ -810,7 +810,7 @@ To set the delegation parameters using Graph Explorer interface, follow these st
 
 ### The life of an allocation
 
-After being created by an Indexer a healthy allocation goes through four states.
+After being created by an Indexer a healthy allocation goes through two states.
 
 - **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
 

From c6ebc02051dbdc08d234d60d2349cac4118d40d5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:30 -0500
Subject: [PATCH 0790/1325] New translations indexing.mdx (Swahili)

---
 website/pages/sw/network/indexing.mdx | 819 ++++++++++++++++++++++++++
 1 file changed, 819 insertions(+)
 create mode 100644 website/pages/sw/network/indexing.mdx

diff --git a/website/pages/sw/network/indexing.mdx b/website/pages/sw/network/indexing.mdx
new file mode 100644
index 000000000000..0eb017b5be3f
--- /dev/null
+++ b/website/pages/sw/network/indexing.mdx
@@ -0,0 +1,819 @@
+---
+title: Indexing
+---
+
+Indexers are node operators in The Graph Network that stake Graph Tokens (GRT) in order to provide indexing and query processing services. Indexers earn query fees and indexing rewards for their services. They also earn query fees that are rebated according to an exponential rebate function.
+
+GRT that is staked in the protocol is subject to a thawing period and can be slashed if Indexers are malicious and serve incorrect data to applications or if they index incorrectly. Indexers also earn rewards for delegated stake from Delegators, to contribute to the network.
+
+Indexers select subgraphs to index based on the subgraph’s curation signal, where Curators stake GRT in order to indicate which subgraphs are high-quality and should be prioritized. Consumers (eg. applications) can also set parameters for which Indexers process queries for their subgraphs and set preferences for query fee pricing.
+
+<Difficulty level="ADVANCED" />
+
+## FAQ
+
+### What is the minimum stake required to be an Indexer on the network?
+
+The minimum stake for an Indexer is currently set to 100K GRT.
+
+### What are the revenue streams for an Indexer?
+
+**Query fee rebates** - Payments for serving queries on the network. These payments are mediated via state channels between an Indexer and a gateway. Each query request from a gateway contains a payment and the corresponding response a proof of query result validity.
+
+**Indexing rewards** - Generated via a 3% annual protocol wide inflation, the indexing rewards are distributed to Indexers who are indexing subgraph deployments for the network.
+
+### How are indexing rewards distributed?
+
+Indexing rewards come from protocol inflation which is set to 3% annual issuance. They are distributed across subgraphs based on the proportion of all curation signal on each, then distributed proportionally to Indexers based on their allocated stake on that subgraph. **An allocation must be closed with a valid proof of indexing (POI) that meets the standards set by the arbitration charter in order to be eligible for rewards.**
+
+Numerous tools have been created by the community for calculating rewards; you'll find a collection of them organized in the [Community Guides collection](https://www.notion.so/Community-Guides-abbb10f4dba040d5ba81648ca093e70c). You can also find an up to date list of tools in the #Delegators and #Indexers channels on the [Discord server](https://discord.gg/graphprotocol). Here we link a [recommended allocation optimiser](https://github.com/graphprotocol/allocation-optimizer) integrated with the indexer software stack.
+
+### What is a proof of indexing (POI)?
+
+POIs are used in the network to verify that an Indexer is indexing the subgraphs they have allocated on. A POI for the first block of the current epoch must be submitted when closing an allocation for that allocation to be eligible for indexing rewards. A POI for a block is a digest for all entity store transactions for a specific subgraph deployment up to and including that block.
+
+### When are indexing rewards distributed?
+
+Allocations are continuously accruing rewards while they're active and allocated within 28 epochs. Rewards are collected by the Indexers, and distributed whenever their allocations are closed. That happens either manually, whenever the Indexer wants to force close them, or after 28 epochs a Delegator can close the allocation for the Indexer, but this results in no rewards. 28 epochs is the max allocation lifetime (right now, one epoch lasts for ~24h).
+
+### Can pending indexing rewards be monitored?
+
+The RewardsManager contract has a read-only [getRewards](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/rewards/RewardsManager.sol#L316) function that can be used to check the pending rewards for a specific allocation.
+
+Many of the community-made dashboards include pending rewards values and they can be easily checked manually by following these steps:
+
+1. Query the [mainnet subgraph](https://thegraph.com/explorer/subgraphs/9Co7EQe5PgW3ugCUJrJgRv4u9zdEuDJf8NvMWftNsBH8?view=Query&chain=arbitrum-one) to get the IDs for all active allocations:
+
+```graphql
+query indexerAllocations {
+  indexer(id: "<INDEXER_ADDRESS>") {
+    allocations {
+      activeForIndexer {
+        allocations {
+          id
+        }
+      }
+    }
+  }
+}
+```
+
+Use Etherscan to call `getRewards()`:
+
+- Navigate to [Etherscan interface to Rewards contract](https://etherscan.io/address/0x9Ac758AB77733b4150A901ebd659cbF8cB93ED66#readProxyContract)
+
+* To call `getRewards()`:
+  - Expand the **9. getRewards** dropdown.
+  - Enter the **allocationID** in the input.
+  - Click the **Query** button.
+
+### What are disputes and where can I view them?
+
+Indexer's queries and allocations can both be disputed on The Graph during the dispute period. The dispute period varies, depending on the type of dispute. Queries/attestations have 7 epochs dispute window, whereas allocations have 56 epochs. After these periods pass, disputes cannot be opened against either of allocations or queries. When a dispute is opened, a deposit of a minimum of 10,000 GRT is required by the Fishermen, which will be locked until the dispute is finalized and a resolution has been given. Fisherman are any network participants that open disputes.
+
+Disputes have **three** possible outcomes, so does the deposit of the Fishermen.
+
+- If the dispute is rejected, the GRT deposited by the Fishermen will be burned, and the disputed Indexer will not be slashed.
+- If the dispute is settled as a draw, the Fishermen's deposit will be returned, and the disputed Indexer will not be slashed.
+- If the dispute is accepted, the GRT deposited by the Fishermen will be returned, the disputed Indexer will be slashed and the Fishermen will earn 50% of the slashed GRT.
+
+Disputes can be viewed in the UI in an Indexer's profile page under the `Disputes` tab.
+
+### What are query fee rebates and when are they distributed?
+
+Query fees are collected by the gateway and distributed to indexers according to the exponential rebate function (see GIP [here](https://forum.thegraph.com/t/gip-0051-exponential-query-fee-rebates-for-indexers/4162)). The exponential rebate function is proposed as a way to ensure indexers achieve the best outcome by faithfully serving queries. It works by incentivizing Indexers to allocate a large amount of stake (which can be slashed for erring when serving a query) relative to the amount of query fees they may collect.
+
+Once an allocation has been closed the rebates are available to be claimed by the Indexer. Upon claiming, the query fee rebates are distributed to the Indexer and their Delegators based on the query fee cut and the exponential rebate function.
+
+### What is query fee cut and indexing reward cut?
+
+The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that the Indexer may set along with cooldownBlocks to control the distribution of GRT between the Indexer and their Delegators. See the last steps in [Staking in the Protocol](/network/indexing#stake-in-the-protocol) for instructions on setting the delegation parameters.
+
+- **queryFeeCut** - the % of query fee rebates that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the query fees earned when an allocation is closed with the other 5% going to the Delegators.
+
+- **indexingRewardCut** - the % of indexing rewards that will be distributed to the Indexer. If this is set to 95%, the Indexer will receive 95% of the indexing rewards when an allocation is closed and the Delegators will split the other 5%.
+
+### How do Indexers know which subgraphs to index?
+
+Indexers may differentiate themselves by applying advanced techniques for making subgraph indexing decisions but to give a general idea we'll discuss several key metrics used to evaluate subgraphs in the network:
+
+- **Curation signal** - The proportion of network curation signal applied to a particular subgraph is a good indicator of the interest in that subgraph, especially during the bootstrap phase when query voluming is ramping up.
+
+- **Query fees collected** - The historical data for volume of query fees collected for a specific subgraph is a good indicator of future demand.
+
+- **Amount staked** - Monitoring the behavior of other Indexers or looking at proportions of total stake allocated towards specific subgraphs can allow an Indexer to monitor the supply side for subgraph queries to identify subgraphs that the network is showing confidence in or subgraphs that may show a need for more supply.
+
+- **Subgraphs with no indexing rewards** - Some subgraphs do not generate indexing rewards mainly because they are using unsupported features like IPFS or because they are querying another network outside of mainnet. You will see a message on a subgraph if it is not generating indexing rewards.
+
+### What are the hardware requirements?
+
+- **Small** - Enough to get started indexing several subgraphs, will likely need to be expanded.
+- **Standard** - Default setup, this is what is used in the example k8s/terraform deployment manifests.
+- **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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
+
+- **Operator wallet** - Setting up an operator wallet is an important precaution because it allows an Indexer to maintain separation between their keys that control stake and those that are in control of day-to-day operations. See [Stake in Protocol](/network/indexing#stake-in-the-protocol) for instructions.
+
+- **Firewall** - Only the Indexer service needs to be exposed publicly and particular attention should be paid to locking down admin ports and database access: the Graph Node JSON-RPC endpoint (default port: 8030), the Indexer management API endpoint (default port: 18000), and the Postgres database endpoint (default port: 5432) should not be exposed.
+
+## Infrastructure
+
+At the center of an Indexer's infrastructure is the Graph Node which monitors the indexed networks, extracts and loads data per a subgraph definition and serves it as a [GraphQL API](/about/#how-the-graph-works). The Graph Node needs to be connected to an endpoint exposing data from each indexed network; an IPFS node for sourcing data; a PostgreSQL database for its store; and Indexer components which facilitate its interactions with the network.
+
+- **PostgreSQL database** - The main store for the Graph Node, this is where subgraph data is stored. The Indexer service and agent also use the database to store state channel data, cost models, indexing rules, and allocation actions.
+
+- **Data endpoint** - For EVM-compatible networks, Graph Node needs to be connected to an endpoint that exposes an EVM-compatible JSON-RPC API. This may take the form of a single client or it could be a more complex setup that load balances across multiple. It's important to be aware that certain subgraphs will require particular client capabilities such as archive mode and/or the parity tracing API.
+
+- **IPFS node (version less than 5)** - Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during subgraph deployment to fetch the subgraph manifest and all linked files. Network Indexers do not need to host their own IPFS node, an IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+
+- **Indexer service** - Handles all required external communications with the network. Shares cost models and indexing statuses, passes query requests from gateways on to a Graph Node, and manages the query payments via state channels with the gateway.
+
+- **Indexer agent** - Facilitates the Indexers interactions on chain including registering on the network, managing subgraph deployments to its Graph Node/s, and managing allocations.
+
+- **Prometheus metrics server** - The Graph Node and Indexer components log their metrics to the metrics server.
+
+Note: To support agile scaling, it is recommended that query and indexing concerns are separated between different sets of nodes: query nodes and index nodes.
+
+### Ports overview
+
+> **Important**: Be careful about exposing ports publicly - **administration ports** should be kept locked down. This includes the the Graph Node JSON-RPC and the Indexer management endpoints detailed below.
+
+#### Graph Node
+
+| Port | Purpose                                               | Routes                                               | CLI Argument      | Environment Variable |
+| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
+
+#### Indexer Agent
+
+| Port | Purpose                | Routes | CLI Argument              | Environment Variable                    |
+| ---- | ---------------------- | ------ | ------------------------- | --------------------------------------- |
+| 8000 | Indexer management API | /      | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+
+### Setup server infrastructure using Terraform on Google Cloud
+
+> Note: Indexers can alternatively use AWS, Microsoft Azure, or Alibaba.
+
+#### Install prerequisites
+
+- Google Cloud SDK
+- Kubectl command line tool
+- Terraform
+
+#### Create a Google Cloud Project
+
+- Clone or navigate to the [Indexer repository](https://github.com/graphprotocol/indexer).
+
+- Navigate to the `./terraform` directory, this is where all commands should be executed.
+
+```sh
+cd terraform
+```
+
+- Authenticate with Google Cloud and create a new project.
+
+```sh
+gcloud auth login
+project=<PROJECT_NAME>
+gcloud projects create --enable-cloud-apis $project
+```
+
+- Use the Google Cloud Console's billing page to enable billing for the new project.
+
+- Create a Google Cloud configuration.
+
+```sh
+proj_id=$(gcloud projects list --format='get(project_id)' --filter="name=$project")
+gcloud config configurations create $project
+gcloud config set project "$proj_id"
+gcloud config set compute/region us-central1
+gcloud config set compute/zone us-central1-a
+```
+
+- Enable required Google Cloud APIs.
+
+```sh
+gcloud services enable compute.googleapis.com
+gcloud services enable container.googleapis.com
+gcloud services enable servicenetworking.googleapis.com
+gcloud services enable sqladmin.googleapis.com
+```
+
+- Create a service account.
+
+```sh
+svc_name=<SERVICE_ACCOUNT_NAME>
+gcloud iam service-accounts create $svc_name \
+  --description="Service account for Terraform" \
+  --display-name="$svc_name"
+gcloud iam service-accounts list
+# Get the email of the service account from the list
+svc=$(gcloud iam service-accounts list --format='get(email)'
+--filter="displayName=$svc_name")
+gcloud iam service-accounts keys create .gcloud-credentials.json \
+  --iam-account="$svc"
+gcloud projects add-iam-policy-binding $proj_id \
+  --member serviceAccount:$svc \
+  --role roles/editor
+```
+
+- Enable peering between database and Kubernetes cluster that will be created in the next step.
+
+```sh
+gcloud compute addresses create google-managed-services-default \
+  --prefix-length=20 \
+  --purpose=VPC_PEERING \
+  --network default \
+  --global \
+  --description 'IP Range for peer networks.'
+gcloud services vpc-peerings connect \
+  --network=default \
+  --ranges=google-managed-services-default
+```
+
+- Create minimal terraform configuration file (update as needed).
+
+```sh
+indexer=<INDEXER_NAME>
+cat > terraform.tfvars <<EOF
+project = "$proj_id"
+indexer = "$indexer"
+database_password = "<database passowrd>"
+EOF
+```
+
+#### Use Terraform to create infrastructure
+
+Before running any commands, read through [variables.tf](https://github.com/graphprotocol/indexer/blob/main/terraform/variables.tf) and create a file `terraform.tfvars` in this directory (or modify the one we created in the last step). For each variable where you want to override the default, or where you need to set a value, enter a setting into `terraform.tfvars`.
+
+- Run the following commands to create the infrastructure.
+
+```sh
+# Install required plugins
+terraform init
+
+# View plan for resources to be created
+terraform plan
+
+# Create the resources (expect it to take up to 30 minutes)
+terraform apply
+```
+
+Download credentials for the new cluster into `~/.kube/config` and set it as your default context.
+
+```sh
+gcloud container clusters get-credentials $indexer
+kubectl config use-context $(kubectl config get-contexts --output='name'
+| grep $indexer)
+```
+
+#### Creating the Kubernetes components for the Indexer
+
+- Copy the directory `k8s/overlays` to a new directory `$dir,` and adjust the `bases` entry in `$dir/kustomization.yaml` so that it points to the directory `k8s/base`.
+
+- Read through all the files in `$dir` and adjust any values as indicated in the comments.
+
+Deploy all resources with `kubectl apply -k $dir`.
+
+### Graph Node
+
+[Graph Node](https://github.com/graphprotocol/graph-node) is an open source Rust implementation that event sources the Ethereum blockchain to deterministically update a data store that can be queried via the GraphQL endpoint. Developers use subgraphs to define their schema, and a set of mappings for transforming the data sourced from the blockchain and the Graph Node handles syncing the entire chain, monitoring for new blocks, and serving it via a GraphQL endpoint.
+
+#### Getting started from source
+
+#### Install prerequisites
+
+- **Rust**
+
+- **PostgreSQL**
+
+- **IPFS**
+
+- **Additional Requirements for Ubuntu users** - To run a Graph Node on Ubuntu a few additional packages may be needed.
+
+```sh
+sudo apt-get install -y clang libpg-dev libssl-dev pkg-config
+```
+
+#### Setup
+
+1. Start a PostgreSQL database server
+
+```sh
+initdb -D .postgres
+pg_ctl -D .postgres -l logfile start
+createdb graph-node
+```
+
+2. Clone [Graph Node](https://github.com/graphprotocol/graph-node) repo and build the source by running `cargo build`
+
+3. Now that all the dependencies are setup, start the Graph Node:
+
+```sh
+cargo run -p graph-node --release -- \
+  --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
+  --ethereum-rpc [NETWORK_NAME]:[URL] \
+  --ipfs https://ipfs.network.thegraph.com
+```
+
+#### Getting started using Docker
+
+#### Prerequisites
+
+- **Ethereum node** - By default, the docker compose setup will use mainnet: [http://host.docker.internal:8545](http://host.docker.internal:8545) to connect to the Ethereum node on your host machine. You can replace this network name and url by updating `docker-compose.yaml`.
+
+#### Setup
+
+1. Clone Graph Node and navigate to the Docker directory:
+
+```sh
+git clone https://github.com/graphprotocol/graph-node
+cd graph-node/docker
+```
+
+2. For linux users only - Use the host IP address instead of `host.docker.internal` in the `docker-compose.yaml`using the included script:
+
+```sh
+./setup.sh
+```
+
+3. Start a local Graph Node that will connect to your Ethereum endpoint:
+
+```sh
+docker-compose up
+```
+
+### Indexer components
+
+To successfully participate in the network requires almost constant monitoring and interaction, so we've built a suite of Typescript applications for facilitating an Indexers network participation. There are three Indexer components:
+
+- **Indexer agent** - The agent monitors the network and the Indexer's own infrastructure and manages which subgraph deployments are indexed and allocated towards on chain and how much is allocated towards each.
+
+- **Indexer service** - The only component that needs to be exposed externally, the service passes on subgraph queries to the graph node, manages state channels for query payments, shares important decision making information to clients like the gateways.
+
+- **Indexer CLI** - The command line interface for managing the Indexer agent. It allows Indexers to manage cost models, manual allocations, actions queue, and indexing rules.
+
+#### Getting started
+
+The Indexer agent and Indexer service should be co-located with your Graph Node infrastructure. There are many ways to set up virtual execution environments for your Indexer components; here we'll explain how to run them on baremetal using NPM packages or source, or via kubernetes and docker on the Google Cloud Kubernetes Engine. If these setup examples do not translate well to your infrastructure there will likely be a community guide to reference, come say hi on [Discord](https://discord.gg/graphprotocol)! Remember to [stake in the protocol](/network/indexing#stake-in-the-protocol) before starting up your Indexer components!
+
+#### From NPM packages
+
+```sh
+npm install -g @graphprotocol/indexer-service
+npm install -g @graphprotocol/indexer-agent
+
+# Indexer CLI is a plugin for Graph CLI, so both need to be installed:
+npm install -g @graphprotocol/graph-cli
+npm install -g @graphprotocol/indexer-cli
+
+# Indexer service
+graph-indexer-service start ...
+
+# Indexer agent
+graph-indexer-agent start ...
+
+# Indexer CLI
+#Forward the port of your agent pod if using Kubernetes
+kubectl port-forward pod/POD_ID 18000:8000
+graph indexer connect http://localhost:18000/
+graph indexer ...
+```
+
+#### From source
+
+```sh
+# From Repo root directory
+yarn
+
+# Indexer Service
+cd packages/indexer-service
+./bin/graph-indexer-service start ...
+
+# Indexer agent
+cd packages/indexer-agent
+./bin/graph-indexer-service start ...
+
+# Indexer CLI
+cd packages/indexer-cli
+./bin/graph-indexer-cli indexer connect http://localhost:18000/
+./bin/graph-indexer-cli indexer ...
+```
+
+#### Using docker
+
+- Pull images from the registry
+
+```sh
+docker pull ghcr.io/graphprotocol/indexer-service:latest
+docker pull ghcr.io/graphprotocol/indexer-agent:latest
+```
+
+Or build images locally from source
+
+```sh
+# Indexer service
+docker build \
+  --build-arg NPM_TOKEN=<npm-token> \
+  -f Dockerfile.indexer-service \
+  -t indexer-service:latest \
+# Indexer agent
+docker build \
+  --build-arg NPM_TOKEN=<npm-token> \
+  -f Dockerfile.indexer-agent \
+  -t indexer-agent:latest \
+```
+
+- Run the components
+
+```sh
+docker run -p 7600:7600 -it indexer-service:latest ...
+docker run -p 18000:8000 -it indexer-agent:latest ...
+```
+
+**NOTE**: After starting the containers, the Indexer service should be accessible at [http://localhost:7600](http://localhost:7600) and the Indexer agent should be exposing the Indexer management API at [http://localhost:18000/](http://localhost:18000/).
+
+#### Using K8s and Terraform
+
+See the [Setup Server Infrastructure Using Terraform on Google Cloud](/network/indexing#setup-server-infrastructure-using-terraform-on-google-cloud) section
+
+#### Usage
+
+> **NOTE**: All runtime configuration variables may be applied either as parameters to the command on startup or using environment variables of the format `COMPONENT_NAME_VARIABLE_NAME`(ex. `INDEXER_AGENT_ETHEREUM`).
+
+#### Indexer agent
+
+```sh
+graph-indexer-agent start \
+  --ethereum <MAINNET_ETH_ENDPOINT> \
+  --ethereum-network mainnet \
+  --mnemonic <MNEMONIC> \
+  --indexer-address <INDEXER_ADDRESS> \
+  --graph-node-query-endpoint http://localhost:8000/ \
+  --graph-node-status-endpoint http://localhost:8030/graphql \
+  --graph-node-admin-endpoint http://localhost:8020/ \
+  --public-indexer-url http://localhost:7600/ \
+  --indexer-geo-coordinates <YOUR_COORDINATES> \
+  --index-node-ids default \
+  --indexer-management-port 18000 \
+  --metrics-port 7040 \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
+  --default-allocation-amount 100 \
+  --register true \
+  --inject-dai true \
+  --postgres-host localhost \
+  --postgres-port 5432 \
+  --postgres-username <DB_USERNAME> \
+  --postgres-password <DB_PASSWORD> \
+  --postgres-database indexer \
+  --allocation-management auto \
+  | pino-pretty
+```
+
+#### Indexer service
+
+```sh
+SERVER_HOST=localhost \
+SERVER_PORT=5432 \
+SERVER_DB_NAME=is_staging \
+SERVER_DB_USER=<DB_USERNAME> \
+SERVER_DB_PASSWORD=<DB_PASSWORD> \
+graph-indexer-service start \
+  --ethereum <MAINNET_ETH_ENDPOINT> \
+  --ethereum-network mainnet \
+  --mnemonic <MNEMONIC> \
+  --indexer-address <INDEXER_ADDRESS> \
+  --port 7600 \
+  --metrics-port 7300 \
+  --graph-node-query-endpoint http://localhost:8000/ \
+  --graph-node-status-endpoint http://localhost:8030/graphql \
+  --postgres-host localhost \
+  --postgres-port 5432 \
+  --postgres-username <DB_USERNAME> \
+  --postgres-password <DB_PASSWORD> \
+  --postgres-database is_staging \
+  --network-subgraph-endpoint http://query-node-0:8000/subgraphs/id/QmUzRg2HHMpbgf6Q4VHKNDbtBEJnyp5JWCh2gUX9AV6jXv \
+  | pino-pretty
+```
+
+#### Indexer CLI
+
+The Indexer CLI is a plugin for [`@graphprotocol/graph-cli`](https://www.npmjs.com/package/@graphprotocol/graph-cli) accessible in the terminal at `graph indexer`.
+
+```sh
+graph indexer connect http://localhost:18000
+graph indexer status
+```
+
+#### Indexer management using Indexer CLI
+
+The suggested tool for interacting with the **Indexer Management API** is the **Indexer CLI**, an extension to the **Graph CLI**. The Indexer agent needs input from an Indexer in order to autonomously interact with the network on the behalf of the Indexer. The mechanism for defining Indexer agent behavior are **allocation management** mode and **indexing rules**. Under auto mode, an Indexer can use **indexing rules** to apply their specific strategy for picking subgraphs to index and serve queries for. Rules are managed via a GraphQL API served by the agent and known as the Indexer Management API. Under manual mode, an Indexer can create allocation actions using **actions queue** and explicitly approve them before they get executed. Under oversight mode, **indexing rules** are used to populate **actions queue** and also require explicit approval for execution.
+
+#### Usage
+
+The **Indexer CLI** connects to the Indexer agent, typically through port-forwarding, so the CLI does not need to run on the same server or cluster. To help you get started, and to provide some context, the CLI will briefly be described here.
+
+- `graph indexer connect <url>` - Connect to the Indexer management API. Typically the connection to the server is opened via port forwarding, so the CLI can be easily operated remotely. (Example: `kubectl port-forward pod/<indexer-agent-pod> 8000:8000`)
+
+- `graph indexer rules get [options] <deployment-id> [<key1> ...]` - Get one or more indexing rules using `all` as the `<deployment-id>` to get all rules, or `global` to get the global defaults. An additional argument `--merged` can be used to specify that deployment specific rules are merged with the global rule. This is how they are applied in the Indexer agent.
+
+- `graph indexer rules set [options] <deployment-id> <key1> <value1> ...` - Set one or more indexing rules.
+
+- `graph indexer rules start [options] <deployment-id>` - Start indexing a subgraph deployment if available and set its `decisionBasis` to `always`, so the Indexer agent will always choose to index it. If the global rule is set to always then all available subgraphs on the network will be indexed.
+
+- `graph indexer rules stop [options] <deployment-id>` - Stop indexing a deployment and set its `decisionBasis` to never, so it will skip this deployment when deciding on deployments to index.
+
+- `graph indexer rules maybe [options] <deployment-id>` — Set the `decisionBasis` for a deployment to `rules`, so that the Indexer agent will use indexing rules to decide whether to index this deployment.
+
+- `graph indexer actions get [options] <action-id>` - Fetch one or more actions using `all` or leave `action-id` empty to get all actions. An additional argument `--status` can be used to print out all actions of a certain status.
+
+- `graph indexer action queue allocate <deployment-id> <allocation-amount>` - Queue allocation action
+
+- `graph indexer action queue reallocate <deployment-id> <allocation-id> <allocationAmount>` - Queue reallocate action
+
+- `graph indexer action queue unallocate <deployment-id> <allocation-id>` - Queue unallocate action
+
+- `graph indexer actions cancel [<action-id> ...]` - Cancel all action in the queue if id is unspecified, otherwise cancel array of id with space as separator
+
+- `graph indexer actions approve [<action-id> ...]` - Approve multiple actions for execution
+
+- `graph indexer actions execute approve` - Force the worker to execute approved actions immediately
+
+All commands which display rules in the output can choose between the supported output formats (`table`, `yaml`, and `json`) using the `-output` argument.
+
+#### Indexing rules
+
+Indexing rules can either be applied as global defaults or for specific subgraph deployments using their IDs. The `deployment` and `decisionBasis` fields are mandatory, while all other fields are optional. When an indexing rule has `rules` as the `decisionBasis`, then the Indexer agent will compare non-null threshold values on that rule with values fetched from the network for the corresponding deployment. If the subgraph deployment has values above (or below) any of the thresholds it will be chosen for indexing.
+
+For example, if the global rule has a `minStake` of **5** (GRT), any subgraph deployment which has more than 5 (GRT) of stake allocated to it will be indexed. Threshold rules include `maxAllocationPercentage`, `minSignal`, `maxSignal`, `minStake`, and `minAverageQueryFees`.
+
+Data model:
+
+```graphql
+type IndexingRule {
+    identifier: string
+    identifierType: IdentifierType
+    decisionBasis: IndexingDecisionBasis!
+    allocationAmount: number | null
+    allocationLifetime: number | null
+    autoRenewal: boolean
+    parallelAllocations: number | null
+    maxAllocationPercentage: number | null
+    minSignal: string | null
+    maxSignal: string | null
+    minStake: string | null
+    minAverageQueryFees: string | null
+    custom: string | null
+    requireSupported: boolean | null
+  }
+
+IdentifierType {
+  deployment
+  subgraph
+  group
+}
+
+IndexingDecisionBasis {
+  rules
+  never
+  always
+  offchain
+}
+```
+
+Example usage of indexing rule:
+
+```
+graph indexer rules offchain QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
+
+graph indexer rules set QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK decisionBasis always allocationAmount 123321 allocationLifetime 14 autoRenewal false requireSupported false
+
+graph indexer rules stop QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
+
+graph indexer rules delete QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
+```
+
+#### Actions queue CLI
+
+The indexer-cli provides an `actions` module for manually working with the action queue. It uses the **Graphql API** hosted by the indexer management server to interact with the actions queue.
+
+The action execution worker will only grab items from the queue to execute if they have `ActionStatus = approved`. In the recommended path actions are added to the queue with ActionStatus = queued, so they must then be approved in order to be executed on-chain. The general flow will look like:
+
+- Action added to the queue by the 3rd party optimizer tool or indexer-cli user
+- Indexer can use the `indexer-cli` to view all queued actions
+- Indexer (or other software) can approve or cancel actions in the queue using the `indexer-cli`. The approve and cancel commands take an array of action ids as input.
+- The execution worker regularly polls the queue for approved actions. It will grab the `approved` actions from the queue, attempt to execute them, and update the values in the db depending on the status of execution to `success` or `failed`.
+- If an action is successful the worker will ensure that there is an indexing rule present that tells the agent how to manage the allocation moving forward, useful when taking manual actions while the agent is in `auto` or `oversight` mode.
+- The indexer can monitor the action queue to see a history of action execution and if needed re-approve and update action items if they failed execution. The action queue provides a history of all actions queued and taken.
+
+Data model:
+
+```graphql
+Type ActionInput {
+    status: ActionStatus
+    type: ActionType
+    deploymentID: string | null
+    allocationID: string | null
+    amount: string | null
+    poi: string | null
+    force: boolean | null
+    source: string
+    reason: string | null
+    priority: number | null
+}
+
+ActionStatus {
+  queued
+  approved
+  pending
+  success
+  failed
+  canceled
+}
+
+ActionType {
+  allocate
+  unallocate
+  reallocate
+  collect
+}
+```
+
+Example usage from source:
+
+```bash
+graph indexer actions get all
+
+graph indexer actions get --status queued
+
+graph indexer actions queue allocate QmeqJ6hsdyk9dVbo1tvRgAxWrVS3rkERiEMsxzPShKLco6 5000
+
+graph indexer actions queue reallocate QmeqJ6hsdyk9dVbo1tvRgAxWrVS3rkERiEMsxzPShKLco6 0x4a58d33e27d3acbaecc92c15101fbc82f47c2ae5 55000
+
+graph indexer actions queue unallocate QmeqJ6hsdyk9dVbo1tvRgAxWrVS3rkERiEMsxzPShKLco6 0x4a58d33e27d3acbaecc92c15101fbc82f47c2ae
+
+graph indexer actions cancel
+
+graph indexer actions approve 1 3 5
+
+graph indexer actions execute approve
+```
+
+Note that supported action types for allocation management have different input requirements:
+
+- `Allocate` - allocate stake to a specific subgraph deployment
+
+  - required action params:
+    - deploymentID
+    - amount
+
+- `Unallocate` - close allocation, freeing up the stake to reallocate elsewhere
+
+  - required action params:
+    - allocationID
+    - deploymentID
+  - optional action params:
+    - poi
+    - force (forces using the provided POI even if it doesn’t match what the graph-node provides)
+
+- `Reallocate` - atomically close allocation and open a fresh allocation for the same subgraph deployment
+
+  - required action params:
+    - allocationID
+    - deploymentID
+    - amount
+  - optional action params:
+    - poi
+    - force (forces using the provided POI even if it doesn’t match what the graph-node provides)
+
+#### Cost models
+
+Cost models provide dynamic pricing for queries based on market and query attributes. The Indexer Service shares a cost model with the gateways for each subgraph for which they intend to respond to queries. The gateways, in turn, use the cost model to make Indexer selection decisions per query and to negotiate payment with chosen Indexers.
+
+#### Agora
+
+The Agora language provides a flexible format for declaring cost models for queries. An Agora price model is a sequence of statements that execute in order for each top-level query in a GraphQL query. For each top-level query, the first statement which matches it determines the price for that query.
+
+A statement is comprised of a predicate, which is used for matching GraphQL queries, and a cost expression which when evaluated outputs a cost in decimal GRT. Values in the named argument position of a query may be captured in the predicate and used in the expression. Globals may also be set and substituted in for placeholders in an expression.
+
+Example cost model:
+
+```
+# This statement captures the skip value,
+# uses a boolean expression in the predicate to match specific queries that use `skip`
+# and a cost expression to calculate the cost based on the `skip` value and the SYSTEM_LOAD global
+query { pairs(skip: $skip) { id } } when $skip > 2000 => 0.0001 * $skip * $SYSTEM_LOAD;
+
+# This default will match any GraphQL expression.
+# It uses a Global substituted into the expression to calculate cost
+default => 0.1 * $SYSTEM_LOAD;
+```
+
+Example query costing using the above model:
+
+| Query                                                                        | Price   |
+| ---------------------------------------------------------------------------- | ------- |
+| &#123; pairs(skip: 5000) &#123; id &#125; &#125;                             | 0.5 GRT |
+| &#123; tokens &#123; symbol &#125; &#125;                                    | 0.1 GRT |
+| &#123; pairs(skip: 5000) &#123; id &#125; tokens &#123; symbol &#125; &#125; | 0.6 GRT |
+
+#### Applying the cost model
+
+Cost models are applied via the Indexer CLI, which passes them to the Indexer Management API of the Indexer agent for storing in the database. The Indexer Service will then pick them up and serve the cost models to gateways whenever they ask for them.
+
+```sh
+indexer cost set variables '{ "SYSTEM_LOAD": 1.4 }'
+indexer cost set model my_model.agora
+```
+
+## Interacting with the network
+
+### Stake in the protocol
+
+The first steps to participating in the network as an Indexer are to approve the protocol, stake funds, and (optionally) set up an operator address for day-to-day protocol interactions.
+
+> Note: For the purposes of these instructions Remix will be used for contract interaction, but feel free to use your tool of choice ([OneClickDapp](https://oneclickdapp.com/), [ABItopic](https://abitopic.io/), and [MyCrypto](https://www.mycrypto.com/account) are a few other known tools).
+
+Once an Indexer has staked GRT in the protocol, the [Indexer components](/network/indexing#indexer-components) can be started up and begin their interactions with the network.
+
+#### Approve tokens
+
+1. Open the [Remix app](https://remix.ethereum.org/) in a browser
+
+2. In the `File Explorer` create a file named **GraphToken.abi** with the [token ABI](https://raw.githubusercontent.com/graphprotocol/contracts/mainnet-deploy-build/build/abis/GraphToken.json).
+
+3. With `GraphToken.abi` selected and open in the editor, switch to the `Deploy and run transactions` section in the Remix interface.
+
+4. Under environment select `Injected Web3` and under `Account` select your Indexer address.
+
+5. Set the GraphToken contract address - Paste the GraphToken contract address (`0xc944E90C64B2c07662A292be6244BDf05Cda44a7`) next to `At Address` and click the `At address` button to apply.
+
+6. Call the `approve(spender, amount)` function to approve the Staking contract. Fill in `spender` with the Staking contract address (`0xF55041E37E12cD407ad00CE2910B8269B01263b9`) and `amount` with the tokens to stake (in wei).
+
+#### Stake tokens
+
+1. Open the [Remix app](https://remix.ethereum.org/) in a browser
+
+2. In the `File Explorer` create a file named **Staking.abi** with the staking ABI.
+
+3. With `Staking.abi` selected and open in the editor, switch to the `Deploy and run transactions` section in the Remix interface.
+
+4. Under environment select `Injected Web3` and under `Account` select your Indexer address.
+
+5. Set the Staking contract address - Paste the Staking contract address (`0xF55041E37E12cD407ad00CE2910B8269B01263b9`) next to `At Address` and click the `At address` button to apply.
+
+6. Call `stake()` to stake GRT in the protocol.
+
+7. (Optional) Indexers may approve another address to be the operator for their Indexer infrastructure in order to separate the keys that control the funds from those that are performing day to day actions such as allocating on subgraphs and serving (paid) queries. In order to set the operator call `setOperator()` with the operator address.
+
+8. (Optional) In order to control the distribution of rewards and strategically attract Delegators Indexers can update their delegation parameters by updating their indexingRewardCut (parts per million), queryFeeCut (parts per million), and cooldownBlocks (number of blocks). To do so call `setDelegationParameters()`. The following example sets the queryFeeCut to distribute 95% of query rebates to the Indexer and 5% to Delegators, set the indexingRewardCutto distribute 60% of indexing rewards to the Indexer and 40% to Delegators, and set `thecooldownBlocks` period to 500 blocks.
+
+```
+setDelegationParameters(950000, 600000, 500)
+```
+
+### Setting delegation parameters
+
+The `setDelegationParameters()` function in the [staking contract](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol) is essential for Indexers, allowing them to set parameters that define their interactions with Delegators, influencing their reward sharing and delegation capacity.
+
+### How to set delegation parameters
+
+To set the delegation parameters using Graph Explorer interface, follow these steps:
+
+1. Navigate to [Graph Explorer](https://thegraph.com/explorer/).
+2. Connect your wallet. Choose multisig (such as Gnosis Safe) and then select mainnet. Note: You will need to repeat this process for Arbitrum One.
+3. Connect the wallet you have as a signer.
+4. Navigate to the 'Settings' section and select 'Delegation Parameters'. These parameters should be configured to achieve an effective cut within the desired range. Upon entering values in the provided input fields, the interface will automatically calculate the effective cut. Adjust these values as necessary to attain the desired effective cut percentage.
+5. Submit the transaction to the network.
+
+> Note: This transaction will need to be confirmed by the multisig wallet signers.
+
+### The life of an allocation
+
+After being created by an Indexer a healthy allocation goes through two states.
+
+- **Active** - Once an allocation is created on-chain ([allocateFrom()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L316)) it is considered **active**. A portion of the Indexer's own and/or delegated stake is allocated towards a subgraph deployment, which allows them to claim indexing rewards and serve queries for that subgraph deployment. The Indexer agent manages creating allocations based on the Indexer rules.
+
+- **Closed** - An Indexer is free to close an allocation once 1 epoch has passed ([closeAllocation()](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/contracts/staking/Staking.sol#L335)) or their Indexer agent will automatically close the allocation after the **maxAllocationEpochs** (currently 28 days). When an allocation is closed with a valid proof of indexing (POI) their indexing rewards are distributed to the Indexer and its Delegators ([learn more](/network/indexing/#how-are-indexing-rewards-distributed)).
+
+Indexers are recommended to utilize offchain syncing functionality to sync subgraph deployments to chainhead before creating the allocation on-chain. This feature is especially useful for subgraphs that may take longer than 28 epochs to sync or have some chances of failing undeterministically.

From beb12d046f953475253d0750aa2301a50906d86d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:31 -0500
Subject: [PATCH 0791/1325] New translations overview.mdx (Romanian)

---
 website/pages/ro/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/ro/network/overview.mdx b/website/pages/ro/network/overview.mdx
index 16214028dbc9..0779d9a6cb00 100644
--- a/website/pages/ro/network/overview.mdx
+++ b/website/pages/ro/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Overview
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From ccb0cbcf790fc7a1befa8fa2e700504a72756a4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:32 -0500
Subject: [PATCH 0792/1325] New translations overview.mdx (Spanish)

---
 website/pages/es/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/es/network/overview.mdx b/website/pages/es/network/overview.mdx
index bd83a749410e..79bf2e4c1921 100644
--- a/website/pages/es/network/overview.mdx
+++ b/website/pages/es/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Visión general de la red
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Descripción
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Economía de los tokens](/img/Network-roles@2x.png)
 
-Para garantizar la seguridad económica de la red de The Graph y la integridad de los datos que se consultan, los participantes hacen stake y utilizan Graph Tokens ([GRT](/tokenomics)). GRT es un token de utilidad que se utiliza para asignar recursos en la red y es un estándar ERC-20.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 041c6fe3bac849f14f8c1b4d48a07deeddf6a5ea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:33 -0500
Subject: [PATCH 0793/1325] New translations overview.mdx (Arabic)

---
 website/pages/ar/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/ar/network/overview.mdx b/website/pages/ar/network/overview.mdx
index 08469cdc547b..c6fdf2fdc81f 100644
--- a/website/pages/ar/network/overview.mdx
+++ b/website/pages/ar/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## نظره عامة
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![اقتصاد الـ Token](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 61ed33d9cf56808469c8fdf09d6e5467bcacc24d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:34 -0500
Subject: [PATCH 0794/1325] New translations overview.mdx (Czech)

---
 website/pages/cs/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/cs/network/overview.mdx b/website/pages/cs/network/overview.mdx
index 0060dfc506a4..aeb16e0d488e 100644
--- a/website/pages/cs/network/overview.mdx
+++ b/website/pages/cs/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Přehled sítě
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Přehled
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-Pro zajištění ekonomické bezpečnosti sítě Graf a integrity dotazovaných dat účastníci sázejí a používají graf tokeny ([GRT](/tokenomics)). GRT je pracovní užitkový token, který má hodnotu ERC-20 a slouží k přidělování zdrojů v síti.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 339508e6a1e20711a09ad8ea87fc625b7cc9bec2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:35 -0500
Subject: [PATCH 0795/1325] New translations overview.mdx (German)

---
 website/pages/de/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/de/network/overview.mdx b/website/pages/de/network/overview.mdx
index 16214028dbc9..e89a12cde9bd 100644
--- a/website/pages/de/network/overview.mdx
+++ b/website/pages/de/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Overview
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Besonderheiten
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 437b74163329a4fdb46854cd1dd9c8d396c9221f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:36 -0500
Subject: [PATCH 0796/1325] New translations overview.mdx (Italian)

---
 website/pages/it/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/it/network/overview.mdx b/website/pages/it/network/overview.mdx
index 05337a3f3eca..298945cefa41 100644
--- a/website/pages/it/network/overview.mdx
+++ b/website/pages/it/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Panoramica della rete
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Panoramica
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Economia del token](/img/Network-roles@2x.png)
 
-Per garantire la sicurezza economica di The Graph Network e l'integrità dei dati interrogati, i partecipanti puntano e utilizzano i Graph Token ([GRT](/tokenomics)). Il GRT è un work utility token, è ERC-20 utilizzato per fare allocation di risorse nella rete.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From c824590a53ff305f8335f91bf5fa5f3abdcd692e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:37 -0500
Subject: [PATCH 0797/1325] New translations overview.mdx (Japanese)

---
 website/pages/ja/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/ja/network/overview.mdx b/website/pages/ja/network/overview.mdx
index de1a9994f545..d46303b4c294 100644
--- a/website/pages/ja/network/overview.mdx
+++ b/website/pages/ja/network/overview.mdx
@@ -2,14 +2,20 @@
 title: ネットワークの概要
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## 概要
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![トークンエコノミクス](/img/Network-roles@2x.png)
 
-The Graph Network の経済的安全性と照会されるデータの完全性を確保するために、参加者は Graph トークン ([GRT](/tokenomics)) をステークして使用します。 GRT は、ネットワークでリソースを割り当てるために使用される ERC-20 であるワーク ユーティリティ トークンです。
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From cf07288e16fd44e06bf0bb8de5b1e2ae9ccfcc2d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:38 -0500
Subject: [PATCH 0798/1325] New translations overview.mdx (Korean)

---
 website/pages/ko/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/ko/network/overview.mdx b/website/pages/ko/network/overview.mdx
index 16214028dbc9..0779d9a6cb00 100644
--- a/website/pages/ko/network/overview.mdx
+++ b/website/pages/ko/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Overview
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 8a68f68aa105ebb05d10528ad4131a3010339ac3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:39 -0500
Subject: [PATCH 0799/1325] New translations overview.mdx (Dutch)

---
 website/pages/nl/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/nl/network/overview.mdx b/website/pages/nl/network/overview.mdx
index 16214028dbc9..0779d9a6cb00 100644
--- a/website/pages/nl/network/overview.mdx
+++ b/website/pages/nl/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Overview
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 9a19a32936378986a6dfb65306373e1bf7b666ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:40 -0500
Subject: [PATCH 0800/1325] New translations overview.mdx (Polish)

---
 website/pages/pl/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/pl/network/overview.mdx b/website/pages/pl/network/overview.mdx
index 16214028dbc9..0779d9a6cb00 100644
--- a/website/pages/pl/network/overview.mdx
+++ b/website/pages/pl/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Overview
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 1a0c111f9ea2b24fa2d07c1afbd5b7420f86f2b8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:41 -0500
Subject: [PATCH 0801/1325] New translations overview.mdx (Portuguese)

---
 website/pages/pt/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/pt/network/overview.mdx b/website/pages/pt/network/overview.mdx
index f9004acd111c..f2cff6868d75 100644
--- a/website/pages/pt/network/overview.mdx
+++ b/website/pages/pt/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Visão Geral da Rede
 ---
 
-A Graph Network é um protocolo descentralizado de indexação projetado para organizar dados de blockchain. Aplicativos usam o GraphQL para consultar APIs abertas chamadas de subgraphs, a fim de retirar dados indexados na rede. Com o The Graph, programadores podem construir aplicativos sem servidor, executados totalmente em infraestrutura pública.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Visão Geral
+## How does it work?
 
-A Graph Network consiste de Indexadores, Curadores e Delegantes que fornecem serviços à rede e servem dados para aplicativos Web3. Os consumidores usam os aplicativos e consomem os dados.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Especificações
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Economia de Token](/img/Network-roles@2x.png)
 
-Para garantir a segurança económica da Graph Network, e a integridade de dados em consultas, os participantes depositam e usam Graph Tokens ([GRT](/tokenomics)). O GRT é um token de utilidade de trabalho ERC-20 usado para alocar recursos na rede.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Os Indexadores, Curadores e Delegantes ativos podem prover serviços e ganhar uma renda da rede, proporcional à quantidade de trabalho que realizam e ao seu stake em GRT.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From dde7d878386bc4fae9db828f8af662b648546ec9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:42 -0500
Subject: [PATCH 0802/1325] New translations overview.mdx (Russian)

---
 website/pages/ru/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/ru/network/overview.mdx b/website/pages/ru/network/overview.mdx
index d36a6f7d4094..d201c743d2f4 100644
--- a/website/pages/ru/network/overview.mdx
+++ b/website/pages/ru/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Обзор
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Специфические особенности
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Токеномика](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 43e636856df26dfccdef9ac1e1f796765fb12fdf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:43 -0500
Subject: [PATCH 0803/1325] New translations overview.mdx (Swedish)

---
 website/pages/sv/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/sv/network/overview.mdx b/website/pages/sv/network/overview.mdx
index c90c1d462939..a8af86bb9142 100644
--- a/website/pages/sv/network/overview.mdx
+++ b/website/pages/sv/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Nätverksöversikt
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Översikt
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Tokenekonomi](/img/Network-roles@2x.png)
 
-För att säkerställa den ekonomiska säkerheten för The Graph Nätverk och integriteten hos den data som frågas, satsar deltagare och använder Graph Tokens ([GRT](/tokenomics)). GRT är en arbetsnyttighetstoken som är en ERC-20-token som används för att allokera resurser i nätverket.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 5d6f44c871b1c0685759b28476fd133ff1ac494b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:44 -0500
Subject: [PATCH 0804/1325] New translations overview.mdx (Turkish)

---
 website/pages/tr/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/tr/network/overview.mdx b/website/pages/tr/network/overview.mdx
index 16214028dbc9..9b46dfc882bf 100644
--- a/website/pages/tr/network/overview.mdx
+++ b/website/pages/tr/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Overview
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Ayrıntılar
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From f5679a30570f7366fd1aabc8cf08beb7669be983 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:46 -0500
Subject: [PATCH 0805/1325] New translations overview.mdx (Ukrainian)

---
 website/pages/uk/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/uk/network/overview.mdx b/website/pages/uk/network/overview.mdx
index 1a9f3f00fc43..60c044309f09 100644
--- a/website/pages/uk/network/overview.mdx
+++ b/website/pages/uk/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Загальний огляд мережі
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Короткий огляд
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Економіка токенів](/img/Network-roles@2x.png)
 
-Для забезпечення економічної безпеки The Graph Network і цілісності даних, що запитуються, учасники стейкають і використовують Graph токени ([GRT](/tokenomics)). GRT - це функціональний (utility) токен, який існує в мережі ERC-20 та використовується для розподілу ресурсів в мережі.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 5255bf6625e22746fdb0066a6c4fa414a1d4fde9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:46 -0500
Subject: [PATCH 0806/1325] New translations overview.mdx (Chinese Simplified)

---
 website/pages/zh/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/zh/network/overview.mdx b/website/pages/zh/network/overview.mdx
index 58d3359f6692..b2ab6df18b27 100644
--- a/website/pages/zh/network/overview.mdx
+++ b/website/pages/zh/network/overview.mdx
@@ -2,14 +2,20 @@
 title: 网络概述
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## 概述
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![代币经济学](/img/Network-roles@2x.png)
 
-为了确保Graph网络的经济安全和被查询数据的完整性，参与者持有并使用Graph代币（[GRT](/tokenomics)）。GRT是一种工作实用代币，是一种用于在网络中分配资源的ERC-20代币。
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 6ba156c37fce6f25201233e356dcbc0de5acbd46 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:47 -0500
Subject: [PATCH 0807/1325] New translations overview.mdx (Urdu (Pakistan))

---
 website/pages/ur/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/ur/network/overview.mdx b/website/pages/ur/network/overview.mdx
index dd09e61c8425..4ad830a6a841 100644
--- a/website/pages/ur/network/overview.mdx
+++ b/website/pages/ur/network/overview.mdx
@@ -2,14 +2,20 @@
 title: نیٹ ورک کا جائزہ
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## جائزہ
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![ٹوکن اکنامکس](/img/Network-roles@2x.png)
 
-گراف نیٹ ورک کی اقتصادی حفاظت اور کیوری کیے جانے والے ڈیٹا کی سالمیت کو یقینی بنانے کے لیے، شرکاء گراف ٹوکنز ([GRT](/tokenomics)) کو داؤ پر لگاتے اور استعمال کرتے ہیں۔ GRT ایک ورک یوٹیلیٹی ٹوکن ہے جو کہ نیٹ ورک میں وسائل مختص کرنے کے لیے استعمال ہونے والا ERC-20 ہے.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 587cf840ee3ed5cfd69e9ea824b75066f7e55722 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:49 -0500
Subject: [PATCH 0808/1325] New translations overview.mdx (Vietnamese)

---
 website/pages/vi/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/vi/network/overview.mdx b/website/pages/vi/network/overview.mdx
index bfdd5a7ea294..0779d9a6cb00 100644
--- a/website/pages/vi/network/overview.mdx
+++ b/website/pages/vi/network/overview.mdx
@@ -2,14 +2,20 @@
 title: Network Overview
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## Tổng quan
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![Token Economics](/img/Network-roles@2x.png)
 
-To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20 used to allocate resources in the network.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 8de57661b5da94853dbc261dcd8d217d2d685df7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:50 -0500
Subject: [PATCH 0809/1325] New translations overview.mdx (Marathi)

---
 website/pages/mr/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/mr/network/overview.mdx b/website/pages/mr/network/overview.mdx
index 79ef11647660..f3726794f033 100644
--- a/website/pages/mr/network/overview.mdx
+++ b/website/pages/mr/network/overview.mdx
@@ -2,14 +2,20 @@
 title: नेटवर्क विहंगावलोकन
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
 
-## सारांश
+## How does it work?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
 
 ![टोकन इकॉनॉमिक्स](/img/Network-roles@2x.png)
 
-ग्राफ नेटवर्कची आर्थिक सुरक्षितता आणि विचारल्या जाणार्‍या डेटाची अखंडता सुनिश्चित करण्यासाठी, सहभागी ग्राफ टोकन ([GRT](/tokenomics)) घेतात आणि वापरतात. GRT एक कार्य उपयुक्तता टोकन आहे जो नेटवर्कमध्ये संसाधने वाटप करण्यासाठी वापरला जाणारा ERC-20 आहे.
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 1deac46bb052e920f4290a06d45f40acd0ae3df8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:51 -0500
Subject: [PATCH 0810/1325] New translations overview.mdx (Hindi)

---
 website/pages/hi/network/overview.mdx | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/website/pages/hi/network/overview.mdx b/website/pages/hi/network/overview.mdx
index b9ff51cb4f59..a6e15286eced 100644
--- a/website/pages/hi/network/overview.mdx
+++ b/website/pages/hi/network/overview.mdx
@@ -2,14 +2,20 @@
 title: नेटवर्क अवलोकन
 ---
 
-The Graph Network is a decentralized indexing protocol for organizing blockchain data. Applications use GraphQL to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+The Graph Network एक विकेन्द्रीकृत अनुक्रमण प्रोटोकॉल है जो ब्लॉकचेन डेटा को व्यवस्थित करने के लिए है।
 
-## अवलोकन
+## यह कैसे काम करता है?
 
-The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to Web3 applications. Consumers use the applications and consume the data.
+ऐप्लिकेशन [GraphQL](/querying/graphql-api/) का उपयोग करके सबग्राफ़ कहलाने वाले ओपन एपीआई को क्वेरी करते हैं और नेटवर्क पर अनुक्रमित डेटा को पुनः प्राप्त करते हैं। The Graph के साथ, डेवलपर्स बिना सर्वर वाले एप्लिकेशन बना सकते हैं जो पूरी तरह से सार्वजनिक बुनियादी ढांचे पर चलते हैं।
+
+## विशिष्टताएँ
+
+The Graph Network में Indexers, Curators और Delegators शामिल हैं जो नेटवर्क को सेवाएँ प्रदान करते हैं और वेब3 अनुप्रयोगों को डेटा सेवा करते हैं।
 
 ![टोकन अर्थशास्त्र](/img/Network-roles@2x.png)
 
-द ग्राफ़ नेटवर्क की आर्थिक सुरक्षा और क्वेरी किए जा रहे डेटा की अखंडता सुनिश्चित करने के लिए, प्रतिभागी ग्राफ़ टोकन ([GRT](/tokenomics)) को दांव पर लगाते हैं और उनका उपयोग करते हैं। GRT एक वर्क यूटिलिटी टोकन है जो एक ERC-20 है जिसका उपयोग नेटवर्क में संसाधन आवंटित करने के लिए किया जाता है। प्रसंग
+### अर्थशास्त्र
+
+The Graph Network की आर्थिक सुरक्षा सुनिश्चित करने और डेटा की सत्यता को बनाए रखने के लिए, प्रतिभागी Graph Tokens ([GRT](/tokenomics)) का स्टेक करते हैं और उनका उपयोग करते हैं। GRT एक कार्य उपयोगिता टोकन है जो ERC-20 है, जिसका उपयोग नेटवर्क में संसाधनों को आवंटित करने के लिए किया जाता है।
 
-Active Indexers, Curators, and Delegators can provide services and earn income from the network, proportional to the amount of work they perform and their GRT stake.
+सक्रिय Indexers, Curators, और Delegators सेवाएँ प्रदान कर सकते हैं और नेटवर्क से आय अर्जित कर सकते हैं। वे जो आय अर्जित करते हैं, वह उनके द्वारा किए गए कार्य की मात्रा और उनके GRT हिस्सेदारी के अनुपात में होती है।

From 9ca620deebce08255708d90fc9e122c655084e2a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:52 -0500
Subject: [PATCH 0811/1325] New translations overview.mdx (Swahili)

---
 website/pages/sw/network/overview.mdx | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/sw/network/overview.mdx

diff --git a/website/pages/sw/network/overview.mdx b/website/pages/sw/network/overview.mdx
new file mode 100644
index 000000000000..0779d9a6cb00
--- /dev/null
+++ b/website/pages/sw/network/overview.mdx
@@ -0,0 +1,21 @@
+---
+title: Network Overview
+---
+
+The Graph Network is a decentralized indexing protocol for organizing blockchain data.
+
+## How does it work?
+
+Applications use [GraphQL](/querying/graphql-api/) to query open APIs called subgraphs and retrieve data that is indexed on the network. With The Graph, developers can build serverless applications that run entirely on public infrastructure.
+
+## Specifics
+
+The Graph Network consists of Indexers, Curators, and Delegators that provide services to the network and serve data to web3 applications.
+
+![Token Economics](/img/Network-roles@2x.png)
+
+### Economics
+
+To ensure economic security of The Graph Network and the integrity of data being queried, participants stake and use Graph Tokens ([GRT](/tokenomics)). GRT is a work utility token that is an ERC-20, which is used to allocate resources in the network.
+
+Active Indexers, Curators, and Delegators can provide services and earn income from the network. The income they earn is proportional to the amount of work they perform and their GRT stake.

From 8ebee716360681ad4b471cb138446189204d213c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:46:59 -0500
Subject: [PATCH 0812/1325] New translations publishing-a-subgraph.mdx
 (Portuguese)

---
 .../pt/publishing/publishing-a-subgraph.mdx   | 66 +++++++++----------
 1 file changed, 33 insertions(+), 33 deletions(-)

diff --git a/website/pages/pt/publishing/publishing-a-subgraph.mdx b/website/pages/pt/publishing/publishing-a-subgraph.mdx
index 11e9eb60f822..acbf7b78103f 100644
--- a/website/pages/pt/publishing/publishing-a-subgraph.mdx
+++ b/website/pages/pt/publishing/publishing-a-subgraph.mdx
@@ -2,48 +2,48 @@
 title: Como Editar um Subgraph na Rede Descentralizada
 ---
 
-Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network.
+Após [lançar o seu subgraph ao Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) e prepará-lo para entrar em produção, será possível editá-lo na rede descentralizada.
 
-When you publish a subgraph to the decentralized network, you make it available for:
+Ao editar um subgraph à rede descentralizada, ele será disponibilizado para:
 
-- [Curators](/network/curating) to begin curating it.
-- [Indexers](/network/indexing) to begin indexing it.
+- Curadoria por [Curadores](/network/curating).
+- Indexação por [Indexadores](/network/indexing).
 
 <VideoEmbed youtube="satdwdbvzAQ" />
 
-Check out the list of [supported networks](/developing/supported-networks).
+Confira a lista de [redes apoiadas](/developing/supported-networks).
 
-## Publishing from Subgraph Studio
+## Edição do Subgraph Studio
 
-1. Go to the [Subgraph Studio](https://thegraph.com/studio/) dashboard
-2. Click on the **Publish** button
-3. Your subgraph will now be visible in [Graph Explorer](https://thegraph.com/explorer/).
+1. Entre no painel do [Subgraph Studio](https://thegraph.com/studio/)
+2. Clique no botão **Publish** (Editar)
+3. O seu subgraph passará a ser visível no [Graph Explorer](https://thegraph.com/explorer/).
 
-All published versions of an existing subgraph can:
+Todas as versões editadas de um subgraph existente podem:
 
-- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq).
+- Ser editadas ao Arbitrum One. [Aprenda mais sobre a Graph Network no Arbitrum](/arbitrum/arbitrum-faq).
 
-- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published.
+- Indexar dados em quaisquer das [redes apoiadas](/developing/supported-networks), independente da rede na qual o subgraph foi editado.
 
 ### Como atualizar metadados para um subgraph editado
 
-- After publishing your subgraph to the decentralized network, you can update the metadata anytime in Subgraph Studio.
-- Once you’ve saved your changes and published the updates, they will appear in Graph Explorer.
-- It's important to note that this process will not create a new version since your deployment has not changed.
+- Após editar o seu subgraph à rede descentralizada, será possível editar os metadados a qualquer hora no Subgraph Studio.
+- Após salvar as suas mudanças e publicar as atualizações, elas aparecerão no Graph Explorer.
+- É importante notar que este processo não criará uma nova versão, já que a sua edição não terá mudado.
 
 ## Publicação da CLI
 
-As of version 0.73.0, you can also publish your subgraph with the [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
+Desde a versão 0.73.0, é possível editar o seu subgraph com a [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
 
-1. Open the `graph-cli`.
-2. Use the following commands: `graph codegen && graph build` then `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.
+1. Abra a `graph-cli`.
+2. Use os seguintes comandos: `graph codegen && graph build` e depois `graph publish`.
+3. Uma janela será aberta para o programador conectar a sua carteira, adicionar metadados e lançar o seu subgraph finalizado a uma rede de sua escolha.
 
 ![cli-ui](/img/cli-ui.png)
 
-### Customizing your deployment
+### Como personalizar o seu lançamento
 
-You can upload your subgraph build to a specific IPFS node and further customize your deployment with the following flags:
+É possível enviar a sua build a um node IPFS específico e personalizar ainda mais o seu lançamento com as seguintes flags:
 
 ```
 USAGE
@@ -51,29 +51,29 @@ USAGE
     <value>]
 
 FLAGS
-  -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
-  --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
-  --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
+  -h, --help                   Mostra ajuda da CLI.
+  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Envia resultados da build a um node IPFS.
+  --ipfs-hash=<value>          Hash IPFS do manifest do subgraph a ser lançado.
+  --protocol-network=<option>  [default: arbitrum-one] A rede a ser usada para o lançamento do subgraph.
                                <options: arbitrum-one|arbitrum-sepolia>
-  --subgraph-id=<value>        Subgraph ID to publish to.
-  --webapp-url=<value>         [default: https://cli.thegraph.com/publish] URL of the web UI you want to use to deploy.
+  --subgraph-id=<value>        ID do Subgraph a ser publicada.
+  --webapp-url=<value>         [default: https://cli.thegraph.com/publish] URL da UI na web que queres usar para o lançamento.
 
 ```
 
 ## Como adicionar sinal ao seu subgraph
 
-Developers can add GRT signal to their subgraphs to incentivize Indexers to query the subgraph.
+Programadores podem adicionar sinal de GRT aos seus subgraphs para incentivar Indexadores a consultarem o subgraph.
 
-- If a subgraph is eligible for indexing rewards, Indexers who provide a "proof of indexing" will receive a GRT reward, based on the amount of GRT signalled.
+- Se um subgraph for elegível para recompensas de indexação, Indexadores que providenciarem uma "prova de indexação" receberão uma recompensa em GRT com base na quantidade de GRT sinalizada.
 
-- You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
+- É possível conferir a elegibilidade a recompensas de indexação com base no uso de ferramentas de subgraph [aqui](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
 
-- Specific supported networks can be checked [here](/developing/supported-networks).
+- Redes apoiadas específicas podem ser conferidas [aqui](/developing/supported-networks).
 
 > Adicionar sinais a um subgraph que não for elegível não atrairá mais Indexadores.
 
-> If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph.
+> Se o seu subgraph for elegível a recompensas, recomendamos que cure o seu próprio subgraph com, no mínimo, 3000 GRT para atrair mais Indexadores ao seu subgraph.
 
 O [Indexador de Atualização do Nascer do Sol](/sunrise/#what-is-the-upgrade-indexer) garante a indexação de todos os subgraphs. No entanto, sinalizar GRT em um subgraph em particular atrairá mais Indexadores a ele. Este incentivo de Indexadores adicionais via curadoria visa melhorar a qualidade do serviço de queries ao reduzir a latência e melhorar a disponibilidade da rede.
 
@@ -91,4 +91,4 @@ Como alternativa, é possível adicionar sinais em GRT a um subgraph editado a p
 
 ![Sinal do Explorer](/img/signal-from-explorer.png)
 
-Learn more about [Curating](/network/curating/) on The Graph Network.
+Saiba mais sobre [Curadoria](/network/curating/) na Graph Network.

From 164e5faf33e5ba5f03573f3ab5109b45723121d2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:05 -0500
Subject: [PATCH 0813/1325] New translations publishing-a-subgraph.mdx (Hindi)

---
 .../hi/publishing/publishing-a-subgraph.mdx   | 71 +++++++++----------
 1 file changed, 35 insertions(+), 36 deletions(-)

diff --git a/website/pages/hi/publishing/publishing-a-subgraph.mdx b/website/pages/hi/publishing/publishing-a-subgraph.mdx
index 8881f9fa93fd..d851b7952e7e 100644
--- a/website/pages/hi/publishing/publishing-a-subgraph.mdx
+++ b/website/pages/hi/publishing/publishing-a-subgraph.mdx
@@ -2,78 +2,77 @@
 title: विकेंद्रीकृत नेटवर्क के लिए एक सबग्राफ प्रकाशित करना
 ---
 
-Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network.
+आपके द्वारा [Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) पर 'subgraph' को तैनात करने के बाद और यह उत्पादन के लिए तैयार हो जाने पर, आप इसे विकेंद्रीकृत नेटवर्क पर प्रकाशित कर सकते हैं।
 
-When you publish a subgraph to the decentralized network, you make it available for:
+जब आप एक subgraph को विकेंद्रीकृत नेटवर्क पर प्रकाशित करते हैं, तो आप इसे उपलब्ध कराते हैं:
 
-- [Curators](/network/curating) to begin curating it.
-- [Indexers](/network/indexing) to begin indexing it.
+- [Curators](/network/curating) को इसे क्यूरेट करना शुरू करने के लिए।
+- [Indexers](/network/indexing) को इसे इंडेक्स करना शुरू करने के लिए।
 
 <VideoEmbed youtube="satdwdbvzAQ" />
 
-Check out the list of [supported networks](/developing/supported-networks).
+नीचे दिए गए [supported networks](/developing/supported-networks) की सूची देखें।
 
-## Publishing from Subgraph Studio
+## Subgraph Studio से प्रकाशित
 
-1. Go to the [Subgraph Studio](https://thegraph.com/studio/) dashboard
-2. Click on the **Publish** button
-3. Your subgraph will now be visible in [Graph Explorer](https://thegraph.com/explorer/).
+1. जाएँ [Subgraph Studio](https://thegraph.com/studio/) डैशबोर्ड
+2. **प्रकाशित करें** बटन पर क्लिक करें
+3. आपका subgraph अब [Graph Explorer](https://thegraph.com/explorer/) में दिखाई देगा।
 
-All published versions of an existing subgraph can:
+एक मौजूदा subgraph के सभी प्रकाशित संस्करण कर सकते हैं:
 
-- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq).
+- Arbitrum One पर प्रकाशित करें। [Arbitrum पर The Graph Network के बारे में अधिक जानें](/arbitrum/arbitrum-faq)।
 
-- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published.
+- किसी भी [समर्थित नेटवर्क](/developing/supported-networks) पर डेटा इंडेक्स करें, चाहे वह नेटवर्क हो जिस पर subgraph प्रकाशित किया गया था।
 
 ### प्रकाशित सबग्राफ के लिए मेटाडेटा अपडेट करना
 
-- After publishing your subgraph to the decentralized network, you can update the metadata anytime in Subgraph Studio.
-- Once you’ve saved your changes and published the updates, they will appear in Graph Explorer.
-- It's important to note that this process will not create a new version since your deployment has not changed.
+- अपने सबग्राफ को विकेंद्रीकृत नेटवर्क पर प्रकाशित करने के बाद, आप Subgraph Studio में किसी भी समय मेटाडेटा को अपडेट कर सकते हैं।
+- एक बार जब आप अपने परिवर्तनों को सहेज लेते हैं और अपडेट प्रकाशित कर देते हैं, तो वे Graph Explorer में दिखाई देंगे।
+- यह ध्यान रखना महत्वपूर्ण है कि इस प्रक्रिया से कोई नया संस्करण नहीं बनेगा क्योंकि आपका डिप्लॉयमेंट नहीं बदला है।
 
 ## Publishing from the CLI
 
-As of version 0.73.0, you can also publish your subgraph with the [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
+Version 0.73.0 के अनुसार, आप अपने subgraph को[` graph-cli `](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)के साथ भी publish कर सकते हैं।
 
-1. Open the `graph-cli`.
-2. Use the following commands: `graph codegen && graph build` then `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.
+1. `graph-cli` खोलें।
+2. निम्नलिखित कमांड का उपयोग करें: `graph codegen && graph build` फिर `graph publish`।
+3. एक विंडो खुलेगी, जो आपको अपनी वॉलेट कनेक्ट करने, मेटाडेटा जोड़ने, और अपने अंतिम Subgraph को आपकी पसंद के नेटवर्क पर डिप्लॉय करने की अनुमति देगी।
 
 ![cli-ui](/img/cli-ui.png)
 
-### Customizing your deployment
+### अपने डिप्लॉयमेंट को अनुकूलित करना
 
-You can upload your subgraph build to a specific IPFS node and further customize your deployment with the following flags:
+आप अपने Subgraph बिल्ड को एक विशेष IPFSनोड पर अपलोड कर सकते हैं और निम्नलिखित फ्लैग्स के साथ अपने डिप्लॉयमेंट को और अनुकूलित कर सकते हैं:
 
 ```
 USAGE
-  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url
-    <value>]
+  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url <value>]
 
 FLAGS
-  -h, --help                   Show CLI help.
-  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
-  --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
-  --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
+  -h, --help CLI सहायता दिखाएं।
+  -i, --ipfs=<value> [default: https://api.thegraph.com/ipfs/api/v0] बिल्ड परिणामों को 'IPFS node' पर अपलोड करें।
+  --ipfs-hash=<value> डिप्लॉय करने के लिए 'subgraph manifest' का IPFS हैश।
+  --protocol-network=<option> [default: arbitrum-one] 'subgraph deployment' के लिए उपयोग करने वाला नेटवर्क।
                                <options: arbitrum-one|arbitrum-sepolia>
-  --subgraph-id=<value>        Subgraph ID to publish to.
-  --webapp-url=<value>         [default: https://cli.thegraph.com/publish] URL of the web UI you want to use to deploy.
+  --subgraph-id=<value> 'Subgraph' ID जिसे प्रकाशित किया जाएगा।
+  --webapp-url=<value> [default: https://cli.thegraph.com/publish] वह URL जहां आप 'web UI' का उपयोग करके डिप्लॉय करना चाहते हैं।
 
 ```
 
 ## Adding signal to your subgraph
 
-Developers can add GRT signal to their subgraphs to incentivize Indexers to query the subgraph.
+डेवलपर्स अपने Subgraph में GRT सिग्नल जोड़ सकते हैं ताकि Indexer को Subgraph पर क्वेरी करने के लिए प्रेरित किया जा सके।
 
-- If a subgraph is eligible for indexing rewards, Indexers who provide a "proof of indexing" will receive a GRT reward, based on the amount of GRT signalled.
+- यदि कोई Subgraph इंडेक्सिंग पुरस्कारों के लिए पात्र है, तो जो Indexer "इंडेक्सिंग का प्रमाण" प्रदान करते हैं, उन्हें संकेतित GRTकी मात्रा के आधार पर GRT पुरस्कार मिलेगा।
 
-- You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
+- आप उपग्राफ फीचर उपयोग के आधार पर इंडेक्सिंग पुरस्कार पात्रता की जांच [यहाँ](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) कर सकते हैं।
 
-- Specific supported networks can be checked [here](/developing/supported-networks).
+- विशिष्ट समर्थित नेटवर्क की जांच [यहाँ](/developing/supported-networks) की जा सकती है।
 
 > Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers.
 
-> If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph.
+> यदि आपका Subgraph पुरस्कारों के लिए पात्र है, तो यह अनुशंसा की जाती है कि आप अपने Subgraph को कम से कम 3,000 GRT के साथ क्यूरेट करें ताकि अधिक Indexer को आपके सबग्राफ़ को इंडेक्स करने के लिए आकर्षित किया जा सके।
 
 The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
 
@@ -83,7 +82,7 @@ Indexers can find subgraphs to index based on curation signals they see in Graph
 
 ![एक्सप्लोरर सबग्राफ](/img/explorer-subgraphs.png)
 
-Subgraph Studio enables you to add signal to your subgraph by adding GRT to your subgraph's curation pool in the same transaction it is published.
+Subgraph Studio आपको अपने सबग्राफ़ में सिग्नल जोड़ने की सुविधा देता है, जिसमें आप अपने सबग्राफ़ के क्यूरेशन पूल में उसी लेन-देन के साथ GRT जोड़ सकते हैं, जब इसे प्रकाशित किया जाता है.
 
 ![क्यूरेशन पूल](/img/curate-own-subgraph-tx.png)
 
@@ -91,4 +90,4 @@ Alternatively, you can add GRT signal to a published subgraph from Graph Explore
 
 ![Signal from Explorer](/img/signal-from-explorer.png)
 
-Learn more about [Curating](/network/curating/) on The Graph Network.
+The Graph नेटवर्क पर [Curating](/network/curating/) के बारे में अधिक जानें।

From 87b1ad106b308c61352a857e7c8cc910c0bb4dbd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:06 -0500
Subject: [PATCH 0814/1325] New translations publishing-a-subgraph.mdx
 (Swahili)

---
 .../sw/publishing/publishing-a-subgraph.mdx   | 94 +++++++++++++++++++
 1 file changed, 94 insertions(+)
 create mode 100644 website/pages/sw/publishing/publishing-a-subgraph.mdx

diff --git a/website/pages/sw/publishing/publishing-a-subgraph.mdx b/website/pages/sw/publishing/publishing-a-subgraph.mdx
new file mode 100644
index 000000000000..9de36745a95b
--- /dev/null
+++ b/website/pages/sw/publishing/publishing-a-subgraph.mdx
@@ -0,0 +1,94 @@
+---
+title: Publishing a Subgraph to the Decentralized Network
+---
+
+Once you have [deployed your subgraph to Subgraph Studio](/deploying/deploying-a-subgraph-to-studio) and it's ready to go into production, you can publish it to the decentralized network.
+
+When you publish a subgraph to the decentralized network, you make it available for:
+
+- [Curators](/network/curating) to begin curating it.
+- [Indexers](/network/indexing) to begin indexing it.
+
+<VideoEmbed youtube="satdwdbvzAQ" />
+
+Check out the list of [supported networks](/developing/supported-networks).
+
+## Publishing from Subgraph Studio
+
+1. Go to the [Subgraph Studio](https://thegraph.com/studio/) dashboard
+2. Click on the **Publish** button
+3. Your subgraph will now be visible in [Graph Explorer](https://thegraph.com/explorer/).
+
+All published versions of an existing subgraph can:
+
+- Be published to Arbitrum One. [Learn more about The Graph Network on Arbitrum](/arbitrum/arbitrum-faq).
+
+- Index data on any of the [supported networks](/developing/supported-networks), regardless of the network on which the subgraph was published.
+
+### Updating metadata for a published subgraph
+
+- After publishing your subgraph to the decentralized network, you can update the metadata anytime in Subgraph Studio.
+- Once you’ve saved your changes and published the updates, they will appear in Graph Explorer.
+- It's important to note that this process will not create a new version since your deployment has not changed.
+
+## Publishing from the CLI
+
+As of version 0.73.0, you can also publish your subgraph with the [`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli).
+
+1. Open the `graph-cli`.
+2. Use the following commands: `graph codegen && graph build` then `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)
+
+### Customizing your deployment
+
+You can upload your subgraph build to a specific IPFS node and further customize your deployment with the following flags:
+
+```
+USAGE
+  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url
+    <value>]
+
+FLAGS
+  -h, --help                   Show CLI help.
+  -i, --ipfs=<value>           [default: https://api.thegraph.com/ipfs/api/v0] Upload build results to an IPFS node.
+  --ipfs-hash=<value>          IPFS hash of the subgraph manifest to deploy.
+  --protocol-network=<option>  [default: arbitrum-one] The network to use for the subgraph deployment.
+                               <options: arbitrum-one|arbitrum-sepolia>
+  --subgraph-id=<value>        Subgraph ID to publish to.
+  --webapp-url=<value>         [default: https://cli.thegraph.com/publish] URL of the web UI you want to use to deploy.
+
+```
+
+## Adding signal to your subgraph
+
+Developers can add GRT signal to their subgraphs to incentivize Indexers to query the subgraph.
+
+- If a subgraph is eligible for indexing rewards, Indexers who provide a "proof of indexing" will receive a GRT reward, based on the amount of GRT signalled.
+
+- You can check indexing reward eligibility based on subgraph feature usage [here](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md).
+
+- Specific supported networks can be checked [here](/developing/supported-networks).
+
+> Adding signal to a subgraph which is not eligible for rewards will not attract additional Indexers.
+
+> If your subgraph is eligible for rewards, it is recommended that you curate your own subgraph with at least 3,000 GRT in order to attract additional indexers to index your subgraph.
+
+The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
+
+When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on this specific version.
+
+Indexers can find subgraphs to index based on curation signals they see in Graph Explorer.
+
+![Explorer subgraphs](/img/explorer-subgraphs.png)
+
+Subgraph Studio enables you to add signal to your subgraph by adding GRT to your subgraph's curation pool in the same transaction it is published.
+
+![Curation Pool](/img/curate-own-subgraph-tx.png)
+
+Alternatively, you can add GRT signal to a published subgraph from Graph Explorer.
+
+![Signal from Explorer](/img/signal-from-explorer.png)
+
+Learn more about [Curating](/network/curating/) on The Graph Network.

From 68448b2f64b1079e98d71d7d85ea492a24d5e87e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:08 -0500
Subject: [PATCH 0815/1325] New translations distributed-systems.mdx (French)

---
 .../pages/fr/querying/distributed-systems.mdx  | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/fr/querying/distributed-systems.mdx b/website/pages/fr/querying/distributed-systems.mdx
index cc52558ba647..270b55bfd86d 100644
--- a/website/pages/fr/querying/distributed-systems.mdx
+++ b/website/pages/fr/querying/distributed-systems.mdx
@@ -34,21 +34,21 @@ Le graph fournit l'API `block : { number_gte: $minBlock }`, qui garantit que la
 Nous pouvons utiliser `number_gte` pour nous assurer que le temps ne recule jamais lorsque nous interrogeons des données dans une boucle. Voici un exemple :
 
 ```javascript
-/// Met à jour la variable protocol.paused avec la dernière valeur
+/// Met à jour la variable protocol.paused avec la dernière valeur 
 /// connue dans une boucle en la récupérant en utilisant The Graph.
 async function updateProtocolPaused() {
   // Il est correct de commencer avec minBlock à 0. La requête sera servie
   // en utilisant le dernier bloc disponible. Définir minBlock à 0 revient
   // à omettre cet argument.
   let minBlock = 0
-
+  
   for (;;) {
-    // Planifie une promesse qui sera prête une fois que le prochain bloc
+    // Planifie une promesse qui sera prête une fois que le prochain bloc 
     // Ethereum sera probablement disponible.
     const nextBlock = new Promise((f) => {
       setTimeout(f, 14000)
     })
-
+ 
     const query = `
         query GetProtocol($minBlock: Int!) {
             protocol(block: { number_gte: $minBlock }  id: "0") {
@@ -60,14 +60,14 @@ async function updateProtocolPaused() {
                 }
             }
         }`
-
+    
     const variables = { minBlock }
     const response = await graphql(query, variables)
     minBlock = response._meta.block.number
-
+    
     // TODO: Faites quelque chose avec les données de réponse ici au lieu de les journaliser.
     console.log(response.protocol.paused)
-
+    
     // Dort pour attendre le prochain bloc
     await nextBlock
   }
@@ -87,9 +87,9 @@ async function getDomainNames() {
   let pages = 5
   const perPage = 1000
 
-  // La première requête obtiendra la première page de résultats et obtiendra également le
+  // La première requête obtiendra la première page de résultats et obtiendra également le 
   // hachage du bloc afin que le reste des requêtes soit cohérent avec la première.
-  const listDomainsQuery = `
+ const listDomainsQuery = `
     query ListDomains($perPage: Int!) {
         domains(first: $perPage) {
             name

From 49e7030bca6fcca824074dcf5ca53ceed1059b02 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:16 -0500
Subject: [PATCH 0816/1325] New translations distributed-systems.mdx (Swedish)

---
 .../pages/sv/querying/distributed-systems.mdx | 24 +++++++++----------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/website/pages/sv/querying/distributed-systems.mdx b/website/pages/sv/querying/distributed-systems.mdx
index 365340f65a1b..3143d4859eb8 100644
--- a/website/pages/sv/querying/distributed-systems.mdx
+++ b/website/pages/sv/querying/distributed-systems.mdx
@@ -84,8 +84,8 @@ Här kommer vi att använda argumentet `block: { hash: $blockHash }` för att bi
 /// Gets a list of domain names from a single block using pagination
 async function getDomainNames() {
   // Set a cap on the maximum number of items to pull.
-  let pages = 5
-  const perPage = 1000
+  let pages = 5;
+  const perPage = 1000;
 
   // The first query will get the first page of results and also get the block
   // hash so that the remainder of the queries are consistent with the first.
@@ -100,34 +100,34 @@ async function getDomainNames() {
                 hash
             }
         }
-    }`
+    }`;
 
-  let data = await graphql(listDomainsQuery, { perPage })
-  let result = data.domains.map((d) => d.name)
-  let blockHash = data._meta.block.hash
+  let data = await graphql(listDomainsQuery, { perPage });
+  let result = data.domains.map((d) => d.name);
+  let blockHash = data._meta.block.hash;
 
-  let query
+  let query;
   // Continue fetching additional pages until either we run into the limit of
   // 5 pages total (specified above) or we know we have reached the last page
   // because the page has fewer entities than a full page.
   while (data.domains.length == perPage && --pages) {
-    let lastID = data.domains[data.domains.length - 1].id
+    let lastID = data.domains[data.domains.length - 1].id;
     query = `
         query ListDomains($perPage: Int!, $lastID: ID!, $blockHash: Bytes!) {
             domains(first: $perPage, where: { id_gt: $lastID }, block: { hash: $blockHash }) {
                 name
                 id
             }
-        }`
+        }`;
 
-    data = await graphql(query, { perPage, lastID, blockHash })
+    data = await graphql(query, { perPage, lastID, blockHash });
 
     // Accumulate domain names into the result
     for (domain of data.domains) {
-      result.push(domain.name)
+      result.push(domain.name);
     }
   }
-  return result
+  return result;
 }
 ```
 

From 45d82f0b218d8b572315e29ddd2782b872ebbcfb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:21 -0500
Subject: [PATCH 0817/1325] New translations distributed-systems.mdx (Swahili)

---
 .../pages/sw/querying/distributed-systems.mdx | 134 ++++++++++++++++++
 1 file changed, 134 insertions(+)
 create mode 100644 website/pages/sw/querying/distributed-systems.mdx

diff --git a/website/pages/sw/querying/distributed-systems.mdx b/website/pages/sw/querying/distributed-systems.mdx
new file mode 100644
index 000000000000..85337206bfd3
--- /dev/null
+++ b/website/pages/sw/querying/distributed-systems.mdx
@@ -0,0 +1,134 @@
+---
+title: Distributed Systems
+---
+
+The Graph is a protocol implemented as a distributed system.
+
+Connections fail. Requests arrive out of order. Different computers with out-of-sync clocks and states process related requests. Servers restart. Re-orgs happen between requests. These problems are inherent to all distributed systems but are exacerbated in systems operating at a global scale.
+
+Consider this example of what may occur if a client polls an Indexer for the latest data during a re-org.
+
+1. Indexer ingests block 8
+2. Request served to the client for block 8
+3. Indexer ingests block 9
+4. Indexer ingests block 10A
+5. Request served to the client for block 10A
+6. Indexer detects reorg to 10B and rolls back 10A
+7. Request served to the client for block 9
+8. Indexer ingests block 10B
+9. Indexer ingests block 11
+10. Request served to the client for block 11
+
+From the point of view of the Indexer, things are progressing forward logically. Time is moving forward, though we did have to roll back an uncle block and play the block under consensus forward on top of it. Along the way, the Indexer serves requests using the latest state it knows about at that time.
+
+From the point of view of the client, however, things appear chaotic. The client observes that the responses were for blocks 8, 10, 9, and 11 in that order. We call this the "block wobble" problem. When a client experiences block wobble, data may appear to contradict itself over time. The situation worsens when we consider that Indexers do not all ingest the latest blocks simultaneously, and your requests may be routed to multiple Indexers.
+
+It is the responsibility of the client and server to work together to provide consistent data to the user. Different approaches must be used depending on the desired consistency as there is no one right program for every problem.
+
+Reasoning through the implications of distributed systems is hard, but the fix may not be! We've established APIs and patterns to help you navigate some common use-cases. The following examples illustrate those patterns but still elide details required by production code (like error handling and cancellation) to not obfuscate the main ideas.
+
+## Polling for updated data
+
+The Graph provides the `block: { number_gte: $minBlock }` API, which ensures that the response is for a single block equal or higher to `$minBlock`. If the request is made to a `graph-node` instance and the min block is not yet synced, `graph-node` will return an error. If `graph-node` has synced min block, it will run the response for the latest block. If the request is made to an Edge & Node Gateway, the Gateway will filter out any Indexers that have not yet synced min block and make the request for the latest block the Indexer has synced.
+
+We can use `number_gte` to ensure that time never travels backward when polling for data in a loop. Here is an example:
+
+```javascript
+/// Updates the protocol.paused variable to the latest
+/// known value in a loop by fetching it using The Graph.
+async function updateProtocolPaused() {
+  // It's ok to start with minBlock at 0. The query will be served
+  // using the latest block available. Setting minBlock to 0 is the
+  // same as leaving out that argument.
+  let minBlock = 0
+
+  for (;;) {
+    // Schedule a promise that will be ready once
+    // the next Ethereum block will likely be available.
+    const nextBlock = new Promise((f) => {
+      setTimeout(f, 14000)
+    })
+
+    const query = `
+        query GetProtocol($minBlock: Int!) {
+            protocol(block: { number_gte: $minBlock }  id: "0") {
+              paused
+            }
+            _meta {
+                block {
+                    number
+                }
+            }
+        }`
+
+    const variables = { minBlock }
+    const response = await graphql(query, variables)
+    minBlock = response._meta.block.number
+
+    // TODO: Do something with the response data here instead of logging it.
+    console.log(response.protocol.paused)
+
+    // Sleep to wait for the next block
+    await nextBlock
+  }
+}
+```
+
+## Fetching a set of related items
+
+Another use-case is retrieving a large set or, more generally, retrieving related items across multiple requests. Unlike the polling case (where the desired consistency was to move forward in time), the desired consistency is for a single point in time.
+
+Here we will use the `block: { hash: $blockHash }` argument to pin all of our results to the same block.
+
+```javascript
+/// Gets a list of domain names from a single block using pagination
+async function getDomainNames() {
+  // Set a cap on the maximum number of items to pull.
+  let pages = 5
+  const perPage = 1000
+
+  // The first query will get the first page of results and also get the block
+  // hash so that the remainder of the queries are consistent with the first.
+  const listDomainsQuery = `
+    query ListDomains($perPage: Int!) {
+        domains(first: $perPage) {
+            name
+            id
+        }
+        _meta {
+            block {
+                hash
+            }
+        }
+    }`
+
+  let data = await graphql(listDomainsQuery, { perPage })
+  let result = data.domains.map((d) => d.name)
+  let blockHash = data._meta.block.hash
+
+  let query
+  // Continue fetching additional pages until either we run into the limit of
+  // 5 pages total (specified above) or we know we have reached the last page
+  // because the page has fewer entities than a full page.
+  while (data.domains.length == perPage && --pages) {
+    let lastID = data.domains[data.domains.length - 1].id
+    query = `
+        query ListDomains($perPage: Int!, $lastID: ID!, $blockHash: Bytes!) {
+            domains(first: $perPage, where: { id_gt: $lastID }, block: { hash: $blockHash }) {
+                name
+                id
+            }
+        }`
+
+    data = await graphql(query, { perPage, lastID, blockHash })
+
+    // Accumulate domain names into the result
+    for (domain of data.domains) {
+      result.push(domain.name)
+    }
+  }
+  return result
+}
+```
+
+Note that in case of a re-org, the client will need to retry from the first request to update the block hash to a non-uncle block.

From ab9dfa2dd94b8ca68a6e8c5f9409808108df2ce5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:23 -0500
Subject: [PATCH 0818/1325] New translations querying-best-practices.mdx
 (Romanian)

---
 .../ro/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/ro/querying/querying-best-practices.mdx b/website/pages/ro/querying/querying-best-practices.mdx
index 32d1415b20fa..6e085cfe7bf1 100644
--- a/website/pages/ro/querying/querying-best-practices.mdx
+++ b/website/pages/ro/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From cdd929e8ca616dd83dcb66898a4882a3c5e67f98 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:24 -0500
Subject: [PATCH 0819/1325] New translations querying-best-practices.mdx
 (French)

---
 .../fr/querying/querying-best-practices.mdx   | 143 +++++++++---------
 1 file changed, 69 insertions(+), 74 deletions(-)

diff --git a/website/pages/fr/querying/querying-best-practices.mdx b/website/pages/fr/querying/querying-best-practices.mdx
index 007b5752c493..fcd071700739 100644
--- a/website/pages/fr/querying/querying-best-practices.mdx
+++ b/website/pages/fr/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Bonnes pratiques d'interrogation
 ---
 
-Le Graph fournit un moyen décentralisé d’interroger les données des blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-Les données du réseau Graph sont exposées via une API GraphQL, ce qui facilite l'interrogation des données avec le langage GraphQL.
-
-Cette page vous guidera à travers les règles essentielles du langage GraphQL et les meilleures pratiques en matière de requêtes GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Interroger une API GraphQL
 
-### L'anatomie d'une requête GraphQL
+### The Anatomy of a GraphQL Query
 
 Contrairement à l'API REST, une API GraphQL repose sur un schéma qui définit les requêtes qui peuvent être effectuées.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-Bien que la liste des choses à faire et à ne pas faire syntaxiquement soit longue, voici les règles essentielles à garder à l'esprit lorsqu'il s'agit d'écrire des requêtes GraphQL :
+## Rules for Writing GraphQL Queries
 
 - Chaque `queryName` ne doit être utilisé qu'une seule fois par opération.
 - Chaque `champ` ne doit être utilisé qu'une seule fois dans une sélection (on ne peut pas interroger `id` deux fois sous `token`)
@@ -61,24 +59,24 @@ Bien que la liste des choses à faire et à ne pas faire syntaxiquement soit lon
 - Dans une liste de variables donnée, chacune d’elles doit être unique.
 - Toutes les variables définies doivent être utilisées.
 
-Toutes les variables définies doivent être utilisées.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Envoi d'une requête à une API GraphQL
 
-GraphQL est un langage et un ensemble de conventions qui transportent via HTTP.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-Cela signifie que vous pouvez interroger une API GraphQL en utilisant le standard `fetch` (nativement ou via `@whatwg-node/fetch` ou `isomorphic-fetch`).
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Cependant, comme indiqué dans ["Requête à partir d'une application"](/querying/querying-from-an-application), nous vous recommandons d'utiliser notre `graph-client` qui prend en charge des fonctionnalités uniques telles que :
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Gestion des subgraphs inter-chaînes : interrogation à partir de plusieurs subgraphs en une seule requête
 - [Suivi automatique des blocs](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Pagination automatique](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Résultat entièrement typé
 
-Voici comment interroger The Graph avec `graph-client` :
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-D'autres alternatives client GraphQL sont couvertes dans ["Requête à partir d'une application"](/querying/querying-from-an-application).
-
-Maintenant que nous avons couvert les règles de base de la syntaxe des requêtes GraphQL, examinons maintenant les meilleures pratiques d'écriture de requêtes GraphQL.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ Maintenant que nous avons couvert les règles de base de la syntaxe des requête
 
 ### Écrivez toujours des requêtes statiques
 
-Une (mauvaise) pratique courante consiste à créer dynamiquement des chaînes de requête comme suit :
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-Bien que l'extrait ci-dessus produise une requête GraphQL valide, **il présente de nombreux inconvénients** :
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - cela rend **plus difficile de comprendre** la requête dans son ensemble
 - les développeurs sont **responsables de nettoyer en toute sécurité l'interpolation de chaîne**
 - ne pas envoyer les valeurs des variables dans le cadre des paramètres de la requête **empêcher une éventuelle mise en cache côté serveur**
 - cela **empêche les outils d'analyser statiquement la requête** (ex : Linter, ou outils de génération de types)
 
-Pour cette raison, il est recommandé de toujours écrire les requêtes sous forme de chaînes statiques :
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-Cela apporte de **de nombreux avantages** :
+Doing so brings **many advantages**:
 
 - Requêtes **faciles à lire et à maintenir**
 - Le serveur GraphQL **gère la désinfection des variables**
 - Les **variables peuvent être mises en cache** au niveau du serveur
 - **Les requêtes peuvent être analysées statiquement par des outils** (plus d'informations à ce sujet dans les sections suivantes)
 
-**Remarque : Comment inclure des champs de manière conditionnelle dans les requêtes statiques**
+### How to include fields conditionally in static queries
 
-Nous pourrions vouloir inclure le champ `owner` uniquement dans une condition particulière.
+You might want to include the `owner` field only on a particular condition.
 
-Pour cela, nous pouvons exploiter la directive `@include(if:...)` comme suit :
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Remarque : La directive opposée est `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL est devenu célèbre pour son slogan « Demandez ce que vous voulez ».
-
-Pour cette raison, il n'existe aucun moyen, dans GraphQL, d'obtenir tous les champs disponibles sans avoir à les lister individuellement.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-Lorsque vous interrogez les API GraphQL, pensez toujours à interroger uniquement les champs qui seront réellement utilisés.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-Les collections d’entités sont une cause fréquente de surextraction. Par défaut, les requêtes récupèrent 100 entités dans une collection, ce qui est généralement bien plus que ce qui sera réellement utilisé, par exemple pour l'affichage à l'utilisateur. Les requêtes doivent donc presque toujours être définies explicitement en premier et s'assurer qu'elles ne récupèrent que le nombre d'entités dont elles ont réellement besoin. Cela s'applique non seulement aux collections de niveau supérieur dans une requête, mais encore plus aux collections d'entités imbriquées.
+- Lorsque vous interrogez les API GraphQL, pensez toujours à interroger uniquement les champs qui seront réellement utilisés.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Par exemple, dans la requête suivante :
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-La réponse pourrait contenir 100 transactions pour chacun des 100 jetons.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Si l'application n'a besoin que de 10 transactions, la requête doit explicitement définir `first: 10` dans le champ transactions.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-Votre application peut nécessiter l'interrogation de plusieurs types de données comme suit :
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Bien que cette implémentation soit totalement valide, elle nécessitera deux allers-retours avec l'API GraphQL.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-Heureusement, il est également possible d'envoyer plusieurs requêtes dans la même requête GraphQL comme suit :
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Cette approche **améliorera les performances globales** en réduisant le temps passé sur le réseau (vous évite un aller-retour vers l'API) et fournira un **implémentation plus concise**.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Tirer parti des fragments GraphQL
 
-Une fonctionnalité utile pour écrire des requêtes GraphQL est GraphQL Fragment.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-En regardant la requête suivante, vous remarquerez que certains champs sont répétés sur plusieurs ensembles de sélection (`{ ... }`) :
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-De tels champs répétés (`id`, `active`, `status`) posent de nombreux problèmes :
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- plus difficile à lire pour des requêtes plus approfondies
-- lors de l'utilisation d'outils qui génèrent des types TypeScript basés sur des requêtes (_plus d'informations à ce sujet dans la dernière section_), `newDelegate` et `oldDelegate` entraînera deux interfaces en ligne distinctes.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-Une version refactorisée de la requête serait la suivante :
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-L'utilisation de GraphQL `fragment` améliorera la lisibilité (en particulier à grande échelle) mais entraînera également une meilleure génération de types TypeScript.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-Lors de l'utilisation de l'outil de génération de types, la requête ci-dessus générera un type `DelegateItemFragment` approprié (_voir la dernière section "Outils"_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### Bonnes pratiques et erreurs à éviter avec les fragments GraphQL
 
-**La base du fragment doit être un type**
+### La base du fragment doit être un type
 
-Un Fragment ne peut pas être basé sur un type non applicable, en bref, **sur un type n'ayant pas de champs** :
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` est un **scalaire** (type natif "plain") qui ne peut pas être utilisé comme base d'un fragment.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Comment diffuser un fragment**
+#### Comment diffuser un fragment
 
-Les fragments sont définis sur des types spécifiques et doivent être utilisés en conséquence dans les requêtes.
+Fragments are defined on specific types and should be used accordingly in queries.
 
 L'exemple:
 
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` et `oldDelegate` sont de type `Transcoder`.
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-Il n'est pas possible de diffuser ici un fragment de type `Vote`.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Définir Fragment comme une unité commerciale atomique de données**
+#### Définir Fragment comme une unité commerciale atomique de données
 
-Le fragment GraphQL doit être défini en fonction de son utilisation.
+GraphQL `Fragment`s must be defined based on their usage.
 
-Pour la plupart des cas d'utilisation, définir un fragment par type (en cas d'utilisation répétée de champs ou de génération de type) est suffisant.
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Voici une règle générale pour utiliser Fragment :
+Here is a rule of thumb for using fragments:
 
-- lorsque des champs du même type sont répétés dans une requête, regroupez-les dans un Fragment
-- lorsque des champs similaires mais différents sont répétés, créez plusieurs fragments, ex  :
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # fragment de base (utilisé principalement pour les listes)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## Les outils indispensables
+## The Essential Tools
 
 ### Explorateurs Web GraphQL
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### Linting GraphQL
 
-Afin de suivre les meilleures pratiques et les règles syntaxiques mentionnées ci-dessus, il est fortement recommandé d'utiliser le flux de travail et les outils IDE suivants.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ Afin de suivre les meilleures pratiques et les règles syntaxiques mentionnées
 - `@graphql-eslint/no-unused variables`: une variable donnée doit-elle rester inutilisée ?
 - et plus !
 
-Cela vous permettra de **détecter les erreurs sans même tester les requêtes** sur le playground ni les exécuter en production!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### Plugins IDE
 
-**VSCode et GraphQL**
+**VSCode and GraphQL**
 
-L'[extension GraphQL VSCode](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) est un excellent ajout à votre flux de travail de développement pour obtenir :
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- coloration syntaxique
-- suggestions d'autocomplétion
-- validation par rapport au schéma
-- snippets
-- aller à la définition des fragments et des types d'entrée
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Si vous utilisez `graphql-eslint`, l'[extension ESLint VSCode](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) est un incontournable pour visualiser correctement les erreurs et les avertissements intégrés dans votre code.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij et GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-Le [plug-in JS GraphQL](https://plugins.jetbrains.com/plugin/8097-graphql/) améliorera considérablement votre expérience lorsque vous travaillez avec GraphQL en fournissant :
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- coloration syntaxique
-- suggestions d'autocomplétion
-- validation par rapport au schéma
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Plus d'informations sur cet [article WebStorm](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) qui présente toutes les principales fonctionnalités du plugin.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From e1be1feef9a62b85042e94b389a46a51096795a5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:25 -0500
Subject: [PATCH 0820/1325] New translations querying-best-practices.mdx
 (Spanish)

---
 .../es/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/es/querying/querying-best-practices.mdx b/website/pages/es/querying/querying-best-practices.mdx
index 82e8d0cb9da2..8336be7374a7 100644
--- a/website/pages/es/querying/querying-best-practices.mdx
+++ b/website/pages/es/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Mejores Prácticas para Consultas
 ---
 
-The Graph proporciona una forma descentralizada de consultar datos de la blockchain.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-Los datos de The Graph Network se exponen a través de una API GraphQL, lo que facilita la consulta de datos con el lenguaje GraphQL.
-
-Esta página te guiará a través de las reglas esenciales del lenguaje GraphQL y las mejores prácticas de consulta GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Consulta de una API GraphQL
 
-### Anatomía de una consulta GraphQL
+### The Anatomy of a GraphQL Query
 
 A diferencia de la API REST, una API GraphQL se basa en un esquema que define las consultas que se pueden realizar.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-Aunque la lista de lo que se debe y no se debe hacer sintácticamente es larga, estas son las reglas esenciales que hay que tener en cuenta a la hora de escribir consultas GraphQL:
+## Rules for Writing GraphQL Queries
 
 - Cada `queryName` sólo debe utilizarse una vez por operación.
 - Cada `field` debe utilizarse una sola vez en una selección (no podemos consultar el `id` dos veces bajo `token`)
@@ -61,9 +59,9 @@ Aunque la lista de lo que se debe y no se debe hacer sintácticamente es larga,
 - En una lista dada de variables, cada una de ellas debe ser única.
 - Deben utilizarse todas las variables definidas.
 
-Si no se siguen las reglas anteriores, se producirá un error de la API Graph.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Envío de una consulta a una API GraphQL
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Manejo de subgrafos cross-chain: Consulta de varios subgrafos en una sola consulta
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Las variables pueden almacenarse en caché** a nivel de servidor
 - **Las consultas pueden ser analizadas estáticamente por herramientas** (más información al respecto en las secciones siguientes)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- más difícil de leer para consultas más extensas
-- cuando se utilizan herramientas que generan tipos TypeScript basados en consultas (_más sobre esto en la última sección_), `newDelegate` y `oldDelegate` darán como resultado dos interfaces en línea distintas.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### Qué hacer y qué no hacer con los GraphQL Fragments
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- cuando se repiten campos del mismo tipo en una consulta, agruparlos en un Fragment
-- cuando se repiten campos similares pero no iguales, crear varios Fragments, ej:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## Las herramientas esenciales
+## The Essential Tools
 
 ### Exploradores web GraphQL
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- resaltado de sintaxis
-- sugerencias de autocompletar
-- validación según el esquema
-- fragmentos
-- ir a la definición de fragments y tipos de entrada
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- resaltado de sintaxis
-- sugerencias de autocompletar
-- validación según el esquema
-- fragmentos
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 05e9e686db28ad729b93279be2100465f051c757 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:26 -0500
Subject: [PATCH 0821/1325] New translations querying-best-practices.mdx
 (Arabic)

---
 .../ar/querying/querying-best-practices.mdx   | 85 +++++++++----------
 1 file changed, 40 insertions(+), 45 deletions(-)

diff --git a/website/pages/ar/querying/querying-best-practices.mdx b/website/pages/ar/querying/querying-best-practices.mdx
index 1068236fc184..99d7ed349b04 100644
--- a/website/pages/ar/querying/querying-best-practices.mdx
+++ b/website/pages/ar/querying/querying-best-practices.mdx
@@ -2,21 +2,19 @@
 title: أفضل الممارسات للاستعلام
 ---
 
-يوفر The Graph طريقة لامركزية للاستعلام عن البيانات من سلاسل الكتل.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-يتم عرض بيانات شبكة Graph من خلال GraphQL API ، مما يسهل الاستعلام عن البيانات باستخدام لغة GraphQL.
-
-ستوجهك هذه الصفحة خلال القواعد الأساسية للغة GraphQL وأفضل ممارسات استعلامات GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## الاستعلام عن واجهة برمجة تطبيقات GraphQL
 
-### بنية استعلام GraphQL
+### The Anatomy of a GraphQL Query
 
 على عكس REST API ، فإن GraphQL API مبنية على مخطط يحدد الاستعلامات التي يمكن تنفيذها.
 
-على سبيل المثال ، طلب الاستعلام للحصول على توكن باستخدام استعلام `token` سيبدو كما يلي:
+على سبيل المثال ، طلب الاستعلام للحصول على توكن باستخدام استعلام ` token ` سيبدو كما يلي:
 
 ```graphql
 query GetToken($id: ID!) {
@@ -40,7 +38,7 @@ query GetToken($id: ID!) {
 
 تستخدم استعلامات GraphQL لغة GraphQL ، التي تم تحديدها في [المواصفات](https://spec.graphql.org/).
 
-يتكون استعلام `GetToken` أعلاه من أجزاء متعددة للغة (تم استبدالها أدناه بـ placeholders `[...]`):
+يتكون استعلام ` GetToken ` أعلاه من أجزاء متعددة للغة (تم استبدالها أدناه بـ placeholders ` [...] `):
 
 ```graphql
 query [operationName]([variableName]: [variableType]) {
@@ -52,18 +50,18 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-على الرغم من أن قائمة القواعد التي يجب اتباعها طويلة، إلا أن هناك قواعد أساسية يجب أخذها في الاعتبار عند كتابة استعلامات GraphQL:
+## Rules for Writing GraphQL Queries
 
-- يجب استخدام كل `queryName` مرة واحدة فقط لكل عملية.
-- يجب استخدام كل `field` مرة واحدة فقط في التحديد (لا يمكننا الاستعلام عن `id` مرتين ضمن `token`)
+- يجب استخدام كل ` queryName ` مرة واحدة فقط لكل عملية.
+- يجب استخدام كل ` field ` مرة واحدة فقط في التحديد (لا يمكننا الاستعلام عن ` id ` مرتين ضمن ` token `)
 - Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer).
 - يجب أن يكون أي متغير تم تعيينه لوسيط متطابقًا مع نوعه.
 - في قائمة المتغيرات المعطاة ، يجب أن يكون كل واحد منها فريدًا.
 - يجب استخدام جميع المتغيرات المحددة.
 
-إذا لم تتبع القواعد المذكورة أعلاه ، فستحدث خطأ من Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### إرسال استعلام إلى GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - التعامل مع ال subgraph عبر السلاسل: الاستعلام من عدة subgraphs عبر استعلام واحد
 - [تتبع الكتلة التلقائي](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - ** يمكن تخزين المتغيرات مؤقتًا ** على مستوى الخادم
 - ** يمكن تحليل طلبات البحث بشكل ثابت بواسطة الأدوات ** (المزيد حول هذا الموضوع في الأقسام التالية)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- عند استخدام الأدوات التي تنشئ أنواع TypeScript بناءً على الاستعلامات (_المزيد عن ذلك في القسم الأخير_)، و `newDelate` و `oldDelegate` سينتج عنهما واجهتين مضمنتان متمايزتين.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### ما يجب فعله وما لا يجب فعله في GraphQL Fragment
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- عند تكرار الحقول من نفس النوع في استعلام ، قم بتجميعها في Fragment
-- عند تكرار الحقول متشابهه ولكن غير متطابقة ، قم بإنشاء fragments متعددة ، على سبيل المثال:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## الأدوات الأساسية
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -461,8 +456,8 @@ In order to keep up with the mentioned above best practices and syntactic rules,
 
 [Setup the "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) config will enforce essential rules such as:
 
-- `@ graphql-eslint / field-on-right-type`: هل يتم استخدام الحقل على النوع المناسب؟
-- `@ graphql-eslint / no-unused variables`: هل يجب أن يبقى المتغير المعطى غير مستخدم؟
+- ` @ graphql-eslint / field-on-right-type `: هل يتم استخدام الحقل على النوع المناسب؟
+- ` @ graphql-eslint / no-unused variables `: هل يجب أن يبقى المتغير المعطى غير مستخدم؟
 - و اكثر!
 
 This will allow you to **catch errors without even testing queries** on the playground or running them in production!
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- اقتراحات الإكمال التلقائي
-- validation against schema
-- snippets
-- انتقل إلى تعريف ال fragment وأنواع الإدخال
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- اقتراحات الإكمال التلقائي
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From f31e81c64a7339f277ba1eae667daae5308f41c7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:27 -0500
Subject: [PATCH 0822/1325] New translations querying-best-practices.mdx
 (Czech)

---
 .../cs/querying/querying-best-practices.mdx   | 149 +++++++++---------
 1 file changed, 72 insertions(+), 77 deletions(-)

diff --git a/website/pages/cs/querying/querying-best-practices.mdx b/website/pages/cs/querying/querying-best-practices.mdx
index f2fb16bcf8b7..85f43c8b931d 100644
--- a/website/pages/cs/querying/querying-best-practices.mdx
+++ b/website/pages/cs/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Osvědčené postupy dotazování
 ---
 
-Graf poskytuje decentralizovaný způsob dotazování na data z blockchainů.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-Data sítě Graf jsou zpřístupněna prostřednictvím GraphQL API, což usnadňuje dotazování na data pomocí jazyka GraphQL.
-
-Tato stránka vás provede základními pravidly jazyka GraphQL a osvědčenými postupy pro dotazy GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Dotazování GraphQL API
 
-### Anatomie dotazu GraphQL
+### The Anatomy of a GraphQL Query
 
 Na rozdíl od rozhraní REST API je GraphQL API postaveno na schématu, které definuje, jaké dotazy lze provádět.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-I když je seznam syntaktických doporučení a doporučení dlouhý, zde jsou základní pravidla, která je třeba mít na paměti, pokud jde o psaní dotazů GraphQL:
+## Rules for Writing GraphQL Queries
 
 - Každý `název dotazu` smí být při jedné operaci použit pouze jednou.
 - Každé `pole` musí být ve výběru použito pouze jednou (pod `token` se nemůžeme dvakrát dotazovat na `id`)
@@ -61,24 +59,24 @@ I když je seznam syntaktických doporučení a doporučení dlouhý, zde jsou z
 - V daném seznamu proměnných musí být každá z nich jedinečná.
 - Musí být použity všechny definované proměnné.
 
-Nedodržení výše uvedených pravidel skončí chybou Graf API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-Kompletní seznam pravidel s příklady kódu naleznete v naší příručce [GraphQL Validations](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Odeslání dotazu na GraphQL API
 
-GraphQL je jazyk a sada konvencí, které se přenášejí přes protokol HTTP.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-To znamená, že se můžete dotazovat na GraphQL API pomocí standardního `fetch` (nativně nebo pomocí `@whatwg-node/fetch` nebo `isomorphic-fetch`).
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Jak je však uvedeno v části ["Dotazování z aplikace"](/querying/querying-from-an-application), doporučujeme používat našeho `graf-klienta`, který podporuje jedinečné funkce, jako např:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Manipulace s podgrafy napříč řetězci: Dotazování z více podgrafů v jednom dotazu
 - [Automatické sledování](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatické stránkování](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Plně zadaný výsledekv
 
-Zde se dozvíte, jak zadat dotaz do Grafu pomocí `graph-client`:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-Další alternativy klienta GraphQL jsou popsány v ["Dotazování z aplikace"](/querying/querying-from-an-application).
-
-Nyní, když jsme se seznámili se základními pravidly syntaxe dotazů GraphQL, se podíváme na osvědčené postupy psaní dotazů GraphQL.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ Nyní, když jsme se seznámili se základními pravidly syntaxe dotazů GraphQL
 
 ### Vždy pište statické dotazy
 
-Běžnou (špatnou) praxí je dynamické vytváření řetězců dotazů následujícím způsobem:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-Výše uvedený úryvek sice vytvoří platný dotaz GraphQL, ale **má mnoho nevýhod**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - je **těžší porozumět** dotazu jako celku
 - vývojáři jsou **zodpovědní za bezpečnou úpravu interpolace řetězců**
 - neposílat hodnoty proměnných jako součást parametrů požadavku **zabránit případnému ukládání do mezipaměti na straně serveru**
 - **zabraňuje nástrojům staticky analyzovat dotaz** (např.: Linter nebo nástroje pro generování typů)
 
-Z tohoto důvodu se doporučuje psát dotazy vždy jako statické řetězce:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-To přináší **mnoho výhod**:
+Doing so brings **many advantages**:
 
 - **Snadné čtení a údržba** dotazů
 - GraphQL **server zpracovává sanitizaci proměnných**
 - **Proměnné lze ukládat do mezipaměti** na úrovni serveru
 - **Nástroje mohou staticky analyzovat dotazy** (více v následujících kapitolách)
 
-**Poznámka: Jak podmíněně zahrnout pole do statických dotazů**
+### How to include fields conditionally in static queries
 
-Pole `vlastník` můžeme chtít zahrnout pouze při splnění určité podmínky.
+You might want to include the `owner` field only on a particular condition.
 
-K tomu můžeme využít direktivu `@include(if:...)` takto:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Poznámka: Opačným direktivou je `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL se proslavil sloganem „Požádejte o to, co chcete“.
-
-Z tohoto důvodu neexistuje způsob, jak v GraphQL získat všechna dostupná pole, aniž byste je museli vypisovat jednotlivě.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-Při dotazování na GraphQL vždy myslete na to, abyste dotazovali pouze pole, která budou skutečně použita.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-Častou příčinou nadměrného načítání jsou kolekce entit. Ve výchozím nastavení dotazy načtou 100 entit v kolekci, což je obvykle mnohem více, než kolik se skutečně použije, např. pro zobrazení uživateli. Dotazy by proto měly být téměř vždy nastaveny explicitně jako první a měly by zajistit, aby načítaly pouze tolik entit, kolik skutečně potřebují. To platí nejen pro kolekce nejvyšší úrovně v dotazu, ale ještě více pro vnořené kolekce entit.
+- Při dotazování na GraphQL vždy myslete na to, abyste dotazovali pouze pole, která budou skutečně použita.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Například v následujícím dotazu:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-Odpověď může obsahovat 100 transakcí pro každý ze 100 tokenů.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Pokud aplikace potřebuje pouze 10 transakcí, měl by dotaz explicitně nastavit parametr `first: 10` v poli transakcí.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-Vaše aplikace může vyžadovat dotazování na více typů dat takto:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Přestože je tato implementace zcela platná, bude vyžadovat dva požadavky na GraphQL API.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-Naštěstí je také možné odeslat více dotazů v jednom požadavku GraphQL, a to následujícím způsobem:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Tento přístup **zlepší celkový výkon** tím, že zkrátí čas strávený na síti (ušetří vám cestu k API) a poskytne **stručnější implementaci**.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Využití fragmentů GraphQL
 
-Užitečnou funkcí pro psaní dotazů GraphQL je GraphQL Fragment.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-Při pohledu na následující dotaz si všimnete, že některá pole se opakují ve více výběrových sadách (`{ ... }`):
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-Taková opakovaná pole (`id`, `active`, `status`) přinášejí mnoho problémů:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- hůře čitelné pro rozsáhlejší dotazy
-- při použití nástrojů, které generují typy TypeScript na základě dotazů (_více o tom v poslední části_), budou `newDelegate` a `oldDelegate` mít za následek dvě samostatné inline rozhraní.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-Přepracovaná verze dotazu by byla následující:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Použití GraphQL `fragment` zlepší čitelnost (zejména v měřítku), ale také povede k lepšímu generování typůTypeScript.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-Při použití nástroje pro generování typů vygeneruje výše uvedený dotaz vhodný typ `DelegateItemFragment` (_viz poslední část "Nástroje"_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### Co dělat a nedělat s fragmenty GraphQL
 
-**Základem fragmentu musí být typ**
+### Základem fragmentu musí být typ
 
-Fragment nemůže být založen na nepoužitelném typu, zkrátka **na typu, který nemá pole**:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` je **skalární** (nativní "jednoduchý" typ), který nelze použít jako základ fragmentu.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Jak šířit fragment**
+#### Jak šířit fragment
 
-Fragmenty jsou definovány na konkrétních typech a podle toho by se měly používat v dotazech.
+Fragments are defined on specific types and should be used accordingly in queries.
 
 Příklad:
 
@@ -409,18 +404,18 @@ fragment VoteItem on Vote {
 
 `newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-Fragment typu `Vote` zde není možné šířit.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Definice fragmentu jako atomické obchodní jednotky dat**
+#### Definice fragmentu jako atomické obchodní jednotky dat
 
-Fragment GraphQL musí být definován na základě jejich použití.
+GraphQL `Fragment`s must be defined based on their usage.
 
-Pro většinu případů použití stačí definovat jeden fragment pro každý typ (v případě opakovaného použití polí nebo generování typů).
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Zde je praktický postup pro použití Fragmentu:
+Here is a rule of thumb for using fragments:
 
-- pokud se v dotazu opakují pole stejného typu, seskupte je do fragmentu
-- pokud se opakují podobná, ale ne stejná pole, vytvořte více fragmentů, např:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,51 +438,51 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## Základní nástroje
+## The Essential Tools
 
 ### Weboví průzkumníci GraphQL
 
-Iterace dotazů jejich spouštěním v aplikaci může být obtížná. Z tohoto důvodu neváhejte použít [Graph Explorer](https://thegraph.com/explorer) k testování dotazů před jejich přidáním do aplikace. Průzkumník grafů vám poskytne předkonfigurované hřiště GraphQL pro testování vašich dotazů.
+Iterating over queries by running them in your application can be cumbersome. For this reason, don't hesitate to use [Graph Explorer](https://thegraph.com/explorer) to test your queries before adding them to your application. Graph Explorer will provide you a preconfigured GraphQL playground to test your queries.
 
-Pokud hledáte flexibilnější způsob ladění/testování dotazů, jsou k dispozici další podobné web nástroje, například [Altair](https://altairgraphql.dev/) a [GraphiQL](https://graphiql-online.com/graphiql).
+If you are looking for a more flexible way to debug/test your queries, other similar web-based tools are available such as [Altair](https://altairgraphql.dev/) and [GraphiQL](https://graphiql-online.com/graphiql).
 
 ### GraphQL Linting
 
-Abyste mohli dodržovat výše uvedené osvědčené postupy a syntaktická pravidla, doporučujeme používat následující workflow a nástroje IDE.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
-[GraphQL ESLint](https://the-guild.dev/graphql/eslint/docs/getting-started) vám pomůže udržet si přehled o nejlepších postupech GraphQL bez většího úsilí.
+[GraphQL ESLint](https://the-guild.dev/graphql/eslint/docs/getting-started) will help you stay on top of GraphQL best practices with zero effort.
 
-[Nastavení konfigurace "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) prosadí základní pravidla, jako jsou:
+[Setup the "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) config will enforce essential rules such as:
 
 - `@graphql-eslint/fields-on-correct-type`: je pole použito na správném typu?
 - `@graphql-eslint/no-unused variables`: má daná proměnná zůstat nepoužitá?
 - a další!
 
-To vám umožní **odhalit chyby i bez testování dotazů** na hřišti nebo jejich spuštění ve výrobě!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### IDE zásuvné
 
-**VSCode a GraphQL**
+**VSCode and GraphQL**
 
-Rozšíření [GraphQL VSCode](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) je vynikajícím doplňkem vašeho vývojového pracovního postup:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- zvýraznění syntaxe
-- návrhy automatického dokončování
-- validace proti schéma
-- snippets
-- přejít na definici fragmentů a vstupních typů
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Pokud používáte `graphql-eslint`, je rozšíření [ESLint VSCode](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) nutností pro správnou vizualizaci chyb a varování v kódu.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij a GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-Zásuvný modul [JS GraphQL](https://plugins.jetbrains.com/plugin/8097-graphql/) výrazně zlepší vaše zkušenosti při práci s GraphQL tím, že poskytuje:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- zvýraznění syntaxe
-- návrhy automatického dokončování
-- validace proti schématu
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Další informace najdete v tomto [článku o WebStormu](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/), který představuje všechny hlavní funkce zásuvného.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From e9d73098dc40de9a1bb65da95e46fd24eec1b8bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:28 -0500
Subject: [PATCH 0823/1325] New translations querying-best-practices.mdx
 (German)

---
 .../de/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/de/querying/querying-best-practices.mdx b/website/pages/de/querying/querying-best-practices.mdx
index 32d1415b20fa..6e085cfe7bf1 100644
--- a/website/pages/de/querying/querying-best-practices.mdx
+++ b/website/pages/de/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From ed95c29d1224bc1b43d688702898cfacef57c910 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:29 -0500
Subject: [PATCH 0824/1325] New translations querying-best-practices.mdx
 (Italian)

---
 .../it/querying/querying-best-practices.mdx   | 145 +++++++++---------
 1 file changed, 70 insertions(+), 75 deletions(-)

diff --git a/website/pages/it/querying/querying-best-practices.mdx b/website/pages/it/querying/querying-best-practices.mdx
index 169d9258b397..cdfe37cd6e51 100644
--- a/website/pages/it/querying/querying-best-practices.mdx
+++ b/website/pages/it/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph fornisce un modo decentralizzato per effettuare query dei dati delle blockchain.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-I dati di The Graph network sono esposti attraverso un API GraphQL, che facilita query dei dati con il linguaggio GraphQL.
-
-Questa pagina vi guiderà attraverso le regole essenziali del linguaggio GraphQL e le best practice delle query in GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Effettuare query con API GraphQL
 
-### L'anatomia di una query GraphQL
+### The Anatomy of a GraphQL Query
 
 A differenza del REST API, un GraphQL API si basa su uno schema che definisce le query che possono essere eseguite.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-Sebbene l'elenco delle cose da fare e da non fare a livello sintattico sia lungo, ecco le regole essenziali da tenere a mente quando si tratta di scrivere query GraphQL:
+## Rules for Writing GraphQL Queries
 
 - Ogni `queryName` deve essere usato una sola volta per ogni operazione.
 - Ogni `field` deve essere utilizzato una sola volta in una selezione (non si può effettuare query di `id` due volte sotto `token`)
@@ -61,24 +59,24 @@ Sebbene l'elenco delle cose da fare e da non fare a livello sintattico sia lungo
 - In un determinato elenco di variabili, ciascuna di esse deve essere unica.
 - Tutte le variabili definite devono essere utilizzate.
 
-Se non si rispettano le regole di cui sopra, si ottiene un errore dall'API Graph.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Invio di una query a un API GraphQL
 
-GraphQL è un linguaggio e una serie di convenzioni che si trasportano su HTTP.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-Significa che è possibile effettuare query di un API GraphQL utilizzando lo standard `fetch` (in modo nativo o tramite `@whatwg-node/fetch` or `isomorphic-fetch`).
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Tuttavia, come indicato in ["Eseguire una query da un'applicazione"](/querying/querying-from-an-application), si consiglia di utilizzare il nostro `graph-client` che supporta caratteristiche uniche come:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Gestione dei subgraph a cross-chain: effettuare query di più subgraph in un'unica query
 - [Tracciamento automatico dei blocchi](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Paginazione automatica](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Risultato completamente tipizzato
 
-Ecco come effettuare query di The Graph con `graph-client`:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-Altre alternative di client GraphQL sono trattate in ["Eseguire una query da un'applicazione"](/querying/querying-from-an-application).
-
-Ora che abbiamo trattato le regole di base della sintassi delle query GraphQL, esaminiamo le best practices di scrittura delle query GraphQL.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ Ora che abbiamo trattato le regole di base della sintassi delle query GraphQL, e
 
 ### Scrivere sempre query statiche
 
-Una pratica comune (sbagliata) è quella di costruire dinamicamente le stringhe di query come segue:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-Sebbene lo snippet di cui sopra produca una GraphQL query valida, **ha molti svantaggi**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - rende **più difficile la comprensione** della query nel suo insieme
 - gli sviluppatori sono **responsabili della sanificazione sicura dell'interpolazione delle stringhe**
 - non inviare i valori delle variabili come parte dei parametri della richiesta **previene eventuali cache sul lato server**
 - **impedisce agli strumenti di analizzare staticamente la query** (ad esempio, Linter o strumenti di generazione dei tipi)
 
-Per questo motivo, si consiglia di scrivere sempre le query come stringhe statiche:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-Questo comporta **molti vantaggi**:
+Doing so brings **many advantages**:
 
 - Query **facili da leggere e da mantenere**
 - Il server GraphQL **gestisce la sanificazione delle variabili**
 - **Le variabili possono essere messe in cache** a livello di server
 - **Le query possono essere analizzate staticamente dagli strumenti** (maggiori informazioni nelle sezioni successive)
 
-**Nota: come includere i campi in modo condizionato nelle query statiche**
+### How to include fields conditionally in static queries
 
-Si potrebbe voler includere il campo `owner` solo in una condizione particolare.
+You might want to include the `owner` field only on a particular condition.
 
-Per questo possiamo sfruttare la direttiva `@include(if:...)` come segue:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Nota: La direttiva opposta è `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL è diventato famoso per il suo slogan "Chiedi quello che vuoi".
-
-Per questo motivo, non c'è modo, in GraphQL, di ottenere tutti i campi disponibili senza doverli elencare singolarmente.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-Quando si interrogano le GraphQL API, si deve sempre pensare di effettuare query di solo i campi che verranno effettivamente utilizzati.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-Una causa comune di over-fetching sono le collezioni di entità. Per impostazione predefinita, le query recuperano 100 entità in un collezione, che di solito sono molte di più di quelle effettivamente utilizzate, ad esempio per la visualizzazione all'utente. Le query dovrebbero quindi essere impostate quasi sempre in modo esplicito e assicurarsi di recuperare solo il numero di entità di cui hanno effettivamente bisogno. Questo vale non solo per le collezioni di primo livello in una query, ma ancora di più per le collezioni di entità annidate.
+- Quando si interrogano le GraphQL API, si deve sempre pensare di effettuare query di solo i campi che verranno effettivamente utilizzati.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Ad esempio, nella seguente query:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-La risposta potrebbe contenere 100 transazioni per ciascuno dei 100 token.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Se l'applicazione ha bisogno solo di 10 transazioni, la query deve impostare esplicitamente `first: 10` sul campo transazioni.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-L'applicazione potrebbe richiedere di effettuare query di più tipi di dati, come di seguito indicato:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Sebbene questa implementazione sia assolutamente valida, richiederà due viaggi di andata e ritorno con API GraphQL.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-Fortunatamente, è anche possibile inviare più query nella stessa richiesta GraphQL, come segue:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Questo approccio **migliorerà le prestazioni complessive** riducendo il tempo trascorso sulla rete (si risparmia un viaggio di andata e ritorno verso l'API) e fornirà **un'implementazione più concisa**.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Sfruttare i frammenti GraphQL
 
-Una funzione utile per scrivere GraphQL query è GraphQL Fragment.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-Osservando la seguente query, si noterà che alcuni campi sono ripetuti su Selection-Sets multipli (`{ ... }`):
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-Tali campi ripetuti (`id`, `active`, `status`) comportano molti problemi:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- più difficile da leggere per le query più estese
-- quando si usano strumenti che generano tipi TypeScript basati su query (_per saperne di più nell'ultima sezione_), `newDelegate` e `oldDelegate` risulteranno in due interfacce inline distinte.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-Una versione riadattata della query sarebbe la seguente:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-L'uso di GraphQL `fragment` migliorerà la leggibilità (soprattutto in scala), ma anche la generazione di tipi TypeScript.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-Quando si usa lo strumento di generazione dei tipi, la query di cui sopra genererà un tipo `DelegateItemFragment` corretto (_vedi l'ultima sezione "Strumenti"_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### I frammenti GraphQL da fare e da non fare
 
-**La base del frammento deve essere un tipo**
+### La base del frammento deve essere un tipo
 
-Un frammento non può essere basato su un tipo non applicabile, in breve, **su un tipo che non ha campi**:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,13 +375,13 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` è un **scalare** (tipo nativo "semplice") che non può essere usato come base di un frammento.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Come diffondere un frammento**
+#### Come diffondere un frammento
 
-I frammenti sono definiti su tipi specifici e devono essere usati di conseguenza nelle query.
+Fragments are defined on specific types and should be used accordingly in queries.
 
-Esempio:
+Example:
 
 ```graphql
 query {
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` e `oldDelegate` sono di tipo `Transcoder`.
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-Non è possibile diffondere un frammento di tipo `Vote` qui.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Definire il frammento come unità aziendale atomica di dati**
+#### Definire il frammento come unità aziendale atomica di dati
 
-I Fragment GraphQL devono essere definiti in base al loro utilizzo.
+GraphQL `Fragment`s must be defined based on their usage.
 
-Per la maggior parte dei casi d'uso, è sufficiente definire un fragment per tipo (nel caso di utilizzo di campi ripetuti o di generazione di tipi).
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Ecco una regola empirica per l'utilizzo di Fragment:
+Here is a rule of thumb for using fragments:
 
-- quando i campi dello stesso tipo si ripetono in una query, raggrupparli in un Fragment
-- quando si ripetono campi simili ma non uguali, creare più fragment, ad esempio:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## Gli strumenti essenziali
+## The Essential Tools
 
 ### Esploratori web GraphQL
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### Linting di GraphQL
 
-Per tenere il passo con le best practice e le regole sintattiche di cui sopra, si consiglia vivamente di utilizzare i seguenti strumenti di workflow e IDE.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ Per tenere il passo con le best practice e le regole sintattiche di cui sopra, s
 - `@graphql-eslint/no-unused variables`: una determinata variabile deve rimanere inutilizzata?
 - e altro ancora!
 
-Questo vi permetterà di **cogliere gli errori senza nemmeno testare le query** sul playground o eseguirle in produzione!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### Plugin IDE
 
-**VSCode e GraphQL**
+**VSCode and GraphQL**
 
-[L'estensione GraphQL VSCode](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) è un'eccellente aggiunta al vostro flusso di lavoro di sviluppo:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- evidenziazione della sintassi
-- suggerimenti per il completamento automatico
-- validazione rispetto allo schema
-- frammenti
-- vai alla definizione dei frammenti e dei tipi dell'input
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Se si utilizza `graphql-eslint`, [l'estensione ESLint VSCode](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) è indispensabile per visualizzare correttamente gli errori e gli avvertimenti inseriti nel codice.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij e GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[Il plugin JS GraphQL](https://plugins.jetbrains.com/plugin/8097-graphql/) migliorerà significativamente l'esperienza di lavoro con GraphQL fornendo:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- evidenziazione della sintassi
-- suggerimenti per il completamento automatico
-- validazione rispetto allo schema
-- frammenti
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Maggiori informazioni in questo [articolo di WebStorm](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) che illustra tutte le caratteristiche principali del plugin.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From c5036eb457930f7a7b08df78208dc40b742c15fe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:31 -0500
Subject: [PATCH 0825/1325] New translations querying-best-practices.mdx
 (Japanese)

---
 .../ja/querying/querying-best-practices.mdx   | 143 +++++++++---------
 1 file changed, 69 insertions(+), 74 deletions(-)

diff --git a/website/pages/ja/querying/querying-best-practices.mdx b/website/pages/ja/querying/querying-best-practices.mdx
index dc58ec63e7bb..d8b9c04cf7a7 100644
--- a/website/pages/ja/querying/querying-best-practices.mdx
+++ b/website/pages/ja/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: クエリのベストプラクティス
 ---
 
-The Graphは、ブロックチェーンのデータをクエリするための分散化された方法を提供します。
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The GraphのネットワークのデータはGraphQL APIで公開され、GraphQL言語によるデータクエリーが容易になります。
-
-このページでは、GraphQLの言語ルールとGraphQLクエリのベストプラクティスに必要不可欠な情報をご案内しています。
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## GraphQL APIのクエリ
 
-### GraphQLクエリの構造
+### The Anatomy of a GraphQL Query
 
 REST APIとは異なり、GraphQL APIは実行可能なクエリを定義するSchemaをベースに構築されています。
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-構文の「やるべきこと」「やってはいけないこと」を挙げればきりがありませんが、ここではGraphQLクエリを書く際に覚えておきたい基本的なルールを紹介します：
+## Rules for Writing GraphQL Queries
 
 - 各`queryName`は、1回の操作で1回だけ使用しなければなりません。
 - 各`フィールド`は、選択の中で一度だけ使用しなければなりません(`トークン`の下に`id`を二度照会することはできません)。
@@ -61,24 +59,24 @@ query [operationName]([variableName]: [variableType]) {
 - 与えられた変数のリストにおいて、各変数は一意でなければなりません。
 - 定義された変数はすべて使用する必要があります。
 
-上記のルールに従わない場合、Graph APIからエラーが発生します。
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### GraphQL APIへのクエリの送信
 
-GraphQLは、HTTPを介して転送される言語と一連の規約です。
+GraphQL is a language and set of conventions that transport over HTTP.
 
-これは、標準の`fetch`（ネイティブであれば、`@whatwg-node/fetch`や`isomorphic-fetch`を介しても）を使用して、GraphQL APIにクエリを送信できることを意味します。
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-ただし、「[アプリケーションからのクエリ](/querying/querying-from-an-application)」で述べたように、以下のような固有の機能をサポートする`graph-client`を使用することをおすすめします。
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - クロスチェーンのサブグラフ処理：1回のクエリで複数のサブグラフからクエリを実行可能
 - [自動ブロック追跡](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [自動ページング](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - 完全なタイプ付け結果
 
-`graph-client` を使用してグラフをクエリする方法は次のとおりです。
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-その他の GraphQL クライアントの代替手段については、[「アプリケーションからのクエリ」](/querying/querying-from-an-application) で説明します。
-
-GraphQL クエリ構文の基本ルールを説明したので、今度は GraphQL クエリ記述のベスト プラクティスを見てみましょう。
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ GraphQL クエリ構文の基本ルールを説明したので、今度は Graph
 
 ### 常に静的なクエリを記述
 
-一般的な (悪い) プラクティスは、次のようにクエリ文字列を動的に構築することです。
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-上記のスニペットは有効な GraphQL クエリを生成しますが、**多くの欠点**があります。
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - クエリ全体を**理解するのが難しくなります**。
 - 開発者は、**文字列補間を安全にサニタイズする責任がある**ということです。
 - リクエストパラメータの一部として変数の値を送信しないでください。**サーバー側でのキャッシュの可能性を防止**
 - それは ** ツールがクエリを静的に分析するのを防ぐ** (例: Linter、またはタイプ生成ツール) です。
 
-このため、クエリは常に静的文字列として記述することをお勧めします:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-そうすることで**多くのメリット**がもたらされます:
+Doing so brings **many advantages**:
 
 - **読みやすく、メンテナンスしやすい**クエリ
 - GraphQLの**サーバーは、変数のサニタイズを処理します**
 - サーバーレベルで**変数がキャッシュできます**。
 - **ツールでクエリを静的に分析できる**（これについては、次のセクションで詳しく説明します。）
 
-**注: 静的クエリに条件付きでフィールドを含める方法**
+### How to include fields conditionally in static queries
 
-特定の条件でのみ `owner` フィールドを含めることができます。
+You might want to include the `owner` field only on a particular condition.
 
-このために、次のように `@include(if:...)` ディレクティブを利用できます:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-注: 反対のディレクティブは `@skip(if: ...)` です。
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL は、「欲しいものを聞いてください」というキャッチフレーズで有名になりました。
-
-このため、GraphQLでは、個々にリストすることなくすべての利用可能なフィールドを取得する方法はありません。
+GraphQL became famous for its "Ask for what you want" tagline.
 
-GraphQL APIをクエリする際には、実際に使用するフィールドのみをクエリするように常に考えてください。
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-過剰なデータ取得の一般的な原因は、エンティティのコレクションです。デフォルトでは、クエリはコレクション内のエンティティを100個取得しますが、通常、実際に使用される量（たとえば、ユーザーに表示される量）よりもはるかに多いです。そのため、クエリはほぼ常に`first`を明示的に設定し、実際に必要なだけのエンティティを取得するようにする必要があります。これは、クエリ内のトップレベルのコレクションだけでなく、さらにエンティティのネストされたコレクションにも当てはまります。
+- GraphQL APIをクエリする際には、実際に使用するフィールドのみをクエリするように常に考えてください。
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-たとえば、次のクエリでは:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-応答には、100 個のトークンごとに 100 個のトランザクションが含まれる可能性があります。
+The response could contain 100 transactions for each of the 100 tokens.
 
-アプリケーションが 10 トランザクションのみを必要とする場合、クエリではトランザクション フィールドに `first: 10` を明示的に設定する必要があります。
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-アプリケーションでは、次のように複数の種類のデータをクエリする必要がある場合があります:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-この実装は完全に有効ですが、GraphQL API を使用した 2 つの往復が必要になります。
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-幸いなことに、次のように同じ GraphQL リクエストで複数のクエリを送信することも有効です:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -307,13 +302,13 @@ query GetTokensandCounters {
 `
 ```
 
-このアプローチは、ネットワークに費やす時間を減少させる（APIへの往復を省略する）ため、**全体的なパフォーマンスを向上させます**。また、**より簡潔な実装**を提供します。
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### GraphQLフラグメントの活用
 
-GraphQL クエリを作成するのに役立つ機能は、GraphQL Fragment です。
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-次のクエリを見ると、いくつかのフィールドが複数のSelection-Sets（`{ ... }`）で繰り返されていることがわかります：
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -333,12 +328,12 @@ query {
 }
 ```
 
-このような繰り返しフィールド (`id`、`active`、`status`) は、多くの問題を引き起こします。
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- より広範囲なクエリに対応するために読みにくくなります
-- クエリに基づいて TypeScript 型を生成するツールを使用する場合 (_前のセクションで詳しく説明します_)、`newDelegate` および `oldDelegate` は、2 つの異なるインライン インターフェイスになります。
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-クエリのリファクタリングされたバージョンは次のようになります:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -362,15 +357,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-GraphQLの`fragment`を使用すると、可読性が向上します（特に大規模な場合）し、さらにはより良いTypeScriptの型生成にも結びつきます。
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-型生成ツールを使用すると、上記のクエリは適切な`DelegateItemFragment`型を生成します（_最後の「ツール」セクションを参照_）。
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQLフラグメントの注意点
 
-**フラグメントベースは型である必要があります**
+### フラグメントベースは型である必要があります
 
-フラグメントは、適用できない型、つまり**フィールドを持たない型**に基づくことはできません。
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -378,11 +373,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` は**スカラー** (ネイティブの「プレーン」タイプ) であり、フラグメントのベースとして使用できません。
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**フラグメントを拡散する方法**
+#### フラグメントを拡散する方法
 
-フラグメントは特定のタイプに定義されているため、クエリではそれに応じて使用する必要があります。
+Fragments are defined on specific types and should be used accordingly in queries.
 
 例：
 
@@ -405,20 +400,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` と `oldDelegate` のタイプは `Transcoder` です。
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-ここでタイプ `Vote` のフラグメントを拡散することはできません。
+It is not possible to spread a fragment of type `Vote` here.
 
-**フラグメントをデータのアトミックなビジネス単位として定義する**
+#### フラグメントをデータのアトミックなビジネス単位として定義する
 
-GraphQL フラグメントは、その使用法に基づいて定義する必要があります。
+GraphQL `Fragment`s must be defined based on their usage.
 
-ほとんどのユースケースでは、1つのタイプに対して1つのフラグメントを定義すること（繰り返しフィールドの使用または型生成の場合）で十分です。
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Fragment を使用する場合の経験則は次のとおりです:
+Here is a rule of thumb for using fragments:
 
-- 同じ型のフィールドがクエリ内で繰り返される場合、それらをFragmentでグループ化します。
-- 同じフィールドが繰り返される場合、複数のフラグメントを作成します。
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -441,7 +436,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## 必須ツール
+## The Essential Tools
 
 ### GraphQL ウェブベースのエクスプローラ
 
@@ -451,7 +446,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### GraphQL Linting
 
-上記で述べたベストプラクティスと構文ルールに従うためには、以下のワークフローとIDEツールを使用することを強くお勧めします。
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -463,29 +458,29 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 - `@graphql-eslint/no-unused variables`: 与えられた変数は未使用のままであるべきか？
 - ともっと
 
-これにより、 プレイグラウンドでクエリをテストしたり、本番環境で実行したりせずに**エラーをキャッチできる** ようになります。
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### IDE plugins
 
-**VSCodeとGraphQL**
+**VSCode and GraphQL**
 
-The [GraphQL VSCode Extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is a great addition to your development workflow, allowing you to:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- 構文の強調表示
-- オートコンプリートの提案
-- スキーマに対する検証
-- snippets
-- フラグメントと入力タイプの定義に移動
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-`graphql-eslint`を使用している場合、[ESLint VSCode拡張機能](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)はエラーや警告を正しくコード内に表示するために必須です。
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij および GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[JS GraphQLプラグイン](https://plugins.jetbrains.com/plugin/8097-graphql/)は、以下を提供することで、GraphQLを使用する際のエクスペリエンスを大幅に向上させます。
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- 構文の強調表示
-- オートコンプリートの提案
-- スキーマに対する検証
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-詳細は、この[WebStorm の記事](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/)で、プラグインの主な機能をすべて紹介しています。
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 4e5391f8d41ce664cdf41d62d79ef6e0c8fd053a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:32 -0500
Subject: [PATCH 0826/1325] New translations querying-best-practices.mdx
 (Korean)

---
 .../ko/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/ko/querying/querying-best-practices.mdx b/website/pages/ko/querying/querying-best-practices.mdx
index 32d1415b20fa..6e085cfe7bf1 100644
--- a/website/pages/ko/querying/querying-best-practices.mdx
+++ b/website/pages/ko/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 6aa5411134b10797c60cd18a411b161d21dc0c80 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:33 -0500
Subject: [PATCH 0827/1325] New translations querying-best-practices.mdx
 (Dutch)

---
 .../nl/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/nl/querying/querying-best-practices.mdx b/website/pages/nl/querying/querying-best-practices.mdx
index 32d1415b20fa..6e085cfe7bf1 100644
--- a/website/pages/nl/querying/querying-best-practices.mdx
+++ b/website/pages/nl/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 11b678c02f514e82b614c5d27856ef8d854b1fba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:34 -0500
Subject: [PATCH 0828/1325] New translations querying-best-practices.mdx
 (Polish)

---
 .../pl/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/pl/querying/querying-best-practices.mdx b/website/pages/pl/querying/querying-best-practices.mdx
index 32d1415b20fa..6e085cfe7bf1 100644
--- a/website/pages/pl/querying/querying-best-practices.mdx
+++ b/website/pages/pl/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From a9c1fd435a446d8a439e810fad42044a396dca4b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:35 -0500
Subject: [PATCH 0829/1325] New translations querying-best-practices.mdx
 (Portuguese)

---
 .../pt/querying/querying-best-practices.mdx   | 157 +++++++++---------
 1 file changed, 76 insertions(+), 81 deletions(-)

diff --git a/website/pages/pt/querying/querying-best-practices.mdx b/website/pages/pt/querying/querying-best-practices.mdx
index ce52c559c287..895e871ab11a 100644
--- a/website/pages/pt/querying/querying-best-practices.mdx
+++ b/website/pages/pt/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Etiqueta de Query
 ---
 
-O The Graph fornece um método descentralizado de consultar dados de blockchains em query.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-Os dados da rede do The Graph são expostos por uma API GraphQL, o que facilita queries de dados com a linguagem GraphQL.
-
-Este é um guia sobre as regras essenciais da linguagem GraphQL, e a etiqueta em queries com GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Queries numa API GraphQL
 
-### A anatomia de um query GraphQL
+### The Anatomy of a GraphQL Query
 
 Ao contrário da REST API, uma API GraphQL é construída em cima de um Schema que define quais queries podem ser realizados.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-Enquanto a lista de sintaxes proibidas e permitidas é longa, veja a seguir as regras essenciais quando se trata de escrever queries GraphQL:
+## Rules for Writing GraphQL Queries
 
 - Cada `queryName` deve ser usado apenas uma vez por operação.
 - Cada `field` deve ser usado apenas uma vez numa seleção (não podemos consultar a `id` duas vezes sob o `token`)
@@ -61,24 +59,24 @@ Enquanto a lista de sintaxes proibidas e permitidas é longa, veja a seguir as r
 - Em uma lista dada de variáveis, cada uma delas deve ser única.
 - Todas as variáveis definidas devem ser usadas.
 
-Não seguir as regras acima causará um erro da API do Graph.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-Para uma lista completa de regras com exemplos de código, veja o nosso [guia de Validações GraphQL](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Como enviar um query a uma API GraphQL
 
-GraphQL é uma linguagem e conjunto de convenções que transportam através do HTTP.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-Ou seja, dá para fazer um query numa API GraphQL com o `fetch` normal (nativamente ou via `@whatwg-node/fetch` ou `isomorphic-fetch`).
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Porém, como dito em ["Queries num Aplicativo"](/querying/querying-from-an-application), é melhor usar o nosso `graph-client`, que apoia funções como:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Gestão de Subgraph Cross-chain: Queries de múltiplos subgraphs numa única consulta
 - [Rastreamento Automático de Blocos](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Paginação Automática](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Resultado totalmente digitado
 
-Aqui está como fazer queries para o The Graph com o `graph-client`:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-Falamos sobre mais alternativas de cliente GraphQL em ["Queries num Aplicativo"](/querying/querying-from-an-application).
-
-Agora que cobrimos as regras básicas da sintaxe de queries GraphQL, vamos agora ver como escrever bons queries no GraphQL.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ Agora que cobrimos as regras básicas da sintaxe de queries GraphQL, vamos agora
 
 ### Sempre escreva consultas estáticas
 
-É (um erro) comum construir strings de consulta dinamicamente, como a seguir:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-Enquanto o trecho acima produz um query válido no GraphQL, **isto traz muitas desvantagens**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - ela **dificulta** a consulta na totalidade
 - os programadores são **responsáveis por higienizar com segurança a interpolação de string**
 - não mandar os valores das variáveis como parte dos parâmetros de pedido **impede um possível caching no lado do servidor**
 - ela **impede as ferramentas de analisar estaticamente a consulta** (por ex. Linter ou ferramentas de geração de tipo)
 
-Por isto, é recomendado sempre escrever queries como strings estáticas:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-Isto traz **muitas vantagens**:
+Doing so brings **many advantages**:
 
 - Queries **fáceis de ler e manter**
 - O **servidor GraphQL cuida da higienização de variáveis**
 - **Variáveis podem ser cacheadas** no nível do servidor
 - **Queries podem ser analisados estaticamente por ferramentas** (mais sobre isto nas seções seguintes)
 
-**Nota: Como incluir campos condicionalmente em queries estáticos**
+### How to include fields conditionally in static queries
 
-Talvez você queira incluir o campo `owner` com uma condição particular.
+You might want to include the `owner` field only on a particular condition.
 
-Para isto, use a diretiva `@include(if:...)` a seguir:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Nota: a diretiva oposta é `@skip(if: ...)`.
-
-### Ask for what you want
+> Note: The opposite directive is `@skip(if: ...)`.
 
-O GraphQL ficou famoso por sua frase de efeito "pergunte pelo que queres".
+### Pergunte pelo que queres
 
-Por isto, no GraphQL, não há como obter todos os campos disponíveis sem ter que listá-los individualmente.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-Ao consultar APIs GraphQL, sempre considere fazer query apenas dos campos que serão usados.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-Over-fetching é normalmente causado pela coleção de entidades. Por natureza, os queries retirarão 100 entidades em uma coleção, muito mais do que realmente será usado; por ex., para fins de amostra ao usuário. Portanto, queries devem quase sempre ser configurados primeiro, com a garantia de que só retirarão quantas entidades forem necessárias. Isto serve não só para coleções de alto nível em uma consulta, mas mais ainda para coleções aninhadas de entidades.
+- Ao consultar APIs GraphQL, sempre considere fazer query apenas dos campos que serão usados.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Por exemplo, no query seguinte:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,11 +213,11 @@ query listTokens {
 }
 ```
 
-A resposta pode conter 100 transações para cada um dos 100 tokens.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Se o aplicativo só precisa de 10 transações, o query deve configurar explicitamente `first: 10` no campo de transações.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
-### Use a single query to request multiple records
+### Use uma única query para pedir vários registros
 
 By default, subgraphs have a singular entity for one record. For multiple records, use the plural entities and filter: `where: {id_in:[X,Y,Z]}` or `where: {volume_gt:100000}`
 
@@ -254,9 +249,9 @@ query ManyRecords {
 }
 ```
 
-### Combine multiple queries in a single request
+### Combine múltiplas queries em um único pedido
 
-O seu aplicativo pode exigir queries de múltiplos tipos de dados, como a seguir:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Enquanto esta implementação é totalmente válida, ela exigirá duas rondas totais com a API GraphQL.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-Felizmente, também vale enviar múltiplos queries no mesmo pedido à GraphQL, como a seguir:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Este método **melhorará o desempenho geral** ao reduzir o tempo gasto na rede (pois, poupa-lhe de uma viagem ao redor da API) e fornecerá **implementações mais concisas**.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Como Aproveitar Fragmentos GraphQL
 
-Uma boa ferramenta para escrever queries GraphQL é o GraphQL Fragment.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-No seguinte query, perceba que alguns campos são repetidos em vários Selection-Sets (`{ ... }`):
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-Estes campos repetidos (`id`, `active`, `status`) trazem muitos problemas:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- difíceis de ler para consultas mais extensivas
-- ao usar ferramentas que geram tipos TypeScript baseados em queries (_mais sobre isto na última seção_), `newDelegate` e `oldDelegate` retornarão duas interfaces distintas em linha.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-Refatorado, o query ficaria assim:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Usar o `fragment` do GraphQL melhorará a legibilidade (especialmente em escala) e também melhorará a geração de tipos TypeScript.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-Ao usar a ferramenta de geração de tipos, o query acima gerará um tipo `DelegateItemFragment` apropriado (_veja a última seção "Ferramentas"_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### O que fazer e o que não fazer em Fragments GraphQL
 
-**A base do fragment deve ser um tipo**
+### A base do fragment deve ser um tipo
 
-Um Fragment não pode ser baseado num tipo não aplicável; ou seja, **um tipo sem campos**:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-O `BigInt` é um **escalar** (tipo "plano" nativo) que não pode ser usado como a base de um fragment.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Como espalhar um Fragment**
+#### Como espalhar um Fragment
 
-Fragments são definidos em tipos específicos e devem ser usados de acordo nos queries.
+Fragments are defined on specific types and should be used accordingly in queries.
 
 Exemplo:
 
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` e `oldDelegate` são do tipo `Transcoder`.
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-Não é possível espalhar um fragment do tipo `Vote` aqui.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Defina o Fragment como uma unidade de negócios atômica de dados**
+#### Defina o Fragment como uma unidade de negócios atômica de dados
 
-O Fragment GraphQL deve ser definido baseado no seu uso.
+GraphQL `Fragment`s must be defined based on their usage.
 
-Para a maioria dos casos de uso, definir um fragment por tipo (no caso do uso repetido de campos ou geração de tipos) já basta.
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Aqui estão algumas regras básicas para o uso de Fragments:
+Here is a rule of thumb for using fragments:
 
-- quando campos do mesmo tipo repetem em um query, agrupe-os em um Fragment
-- quando campos parecidos (mas não idênticos) repetem, crie múltiplos fragmentos, por ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,51 +438,51 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## Ferramentas essenciais
+## The Essential Tools
 
 ### Exploradores do GraphQL baseados em web
 
-Pode ser até chato executar queries no seu aplicativo para iterar sobre elas. Por isto, não hesite em usar o [Graph Explorer](https://thegraph.com/explorer) para testar as suas queries antes de adicioná-las. O Graph Explorer lhe providenciará um ambiente de testes GraphQL pré-configurado para testar as suas queries.
+Iterating over queries by running them in your application can be cumbersome. For this reason, don't hesitate to use [Graph Explorer](https://thegraph.com/explorer) to test your queries before adding them to your application. Graph Explorer will provide you a preconfigured GraphQL playground to test your queries.
 
-Se procura uma maneira mais flexível de debugar/testar as suas consultas, há outras ferramentas baseadas em web, como [Altair](https://altairgraphql.dev/) e [GraphiQL](https://graphiql-online.com/graphiql).
+If you are looking for a more flexible way to debug/test your queries, other similar web-based tools are available such as [Altair](https://altairgraphql.dev/) and [GraphiQL](https://graphiql-online.com/graphiql).
 
 ### GraphQL Linting
 
-Para acompanhar as melhores práticas e regras sintáticas ditas acima, vale muito usar o workflow e as ferramentas IDE a seguir.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
-O [GraphQL ESLint](https://the-guild.dev/graphql/eslint/docs/getting-started) ajudará-lhe a aperfeiçoar as melhores práticas no GraphQL sem nenhum esforço.
+[GraphQL ESLint](https://the-guild.dev/graphql/eslint/docs/getting-started) will help you stay on top of GraphQL best practices with zero effort.
 
-[Preparar a configuração "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) irá impor regras essenciais, como:
+[Setup the "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) config will enforce essential rules such as:
 
 - `@graphql-eslint/fields-on-correct-type`: um campo está num tipo apropriado?
 - `@graphql-eslint/no-unused variables`: uma variável usada deve ficar sem uso?
 - e mais!
 
-Isto permitirá-lhe **detectar erros até mesmo sem testar queries** no playground ou executá-las na produção!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### Plugins IDE
 
-**VSCode e GraphQL**
+**VSCode and GraphQL**
 
-A [extensão GraphQL VSCode](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) é ótima para o seu workflow de desenvolvimento. Com ela, você consegue:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- destaque de sintaxe
-- sugestões de autocomplete
-- validação contra schema
-- snippets
-- definições para fragments e tipos de entrada
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Se usa o `graphql-eslint`, a [extensão ESLint VSCode](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) é indispensável para visualizar corretamente os erros e avisos em inline no seu código.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij e GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-O [plugin JS GraphQL](https://plugins.jetbrains.com/plugin/8097-graphql/) melhorará muito a sua experiência de trabalho com o GraphQL, pois proverá:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- destaque de sintaxe
-- sugestões de autocomplete
-- validação contra schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Mais informações [neste artigo da WebStorm](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/), que mostra todos os recursos principais do plugin.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 0acde5cbbaed2b820ec2646f2e06e6238ee8c2c9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:37 -0500
Subject: [PATCH 0830/1325] New translations querying-best-practices.mdx
 (Russian)

---
 .../ru/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/ru/querying/querying-best-practices.mdx b/website/pages/ru/querying/querying-best-practices.mdx
index 475478a343c9..8363d0264d43 100644
--- a/website/pages/ru/querying/querying-best-practices.mdx
+++ b/website/pages/ru/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Лучшие практики
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From e91653613b93018c5ede26007d179a112c6fcef3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:38 -0500
Subject: [PATCH 0831/1325] New translations querying-best-practices.mdx
 (Swedish)

---
 .../sv/querying/querying-best-practices.mdx   | 169 +++++++++---------
 1 file changed, 82 insertions(+), 87 deletions(-)

diff --git a/website/pages/sv/querying/querying-best-practices.mdx b/website/pages/sv/querying/querying-best-practices.mdx
index abe7e8a0aba4..0acb3a3f0351 100644
--- a/website/pages/sv/querying/querying-best-practices.mdx
+++ b/website/pages/sv/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Bästa praxis för förfrågningar
 ---
 
-The Graph tillhandahåller ett decentraliserat sätt att hämta data från blockkedjor.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph-nätverkets data exponeras genom ett GraphQL API, vilket gör det enklare att fråga data med GraphQL-språket.
-
-Den här sidan kommer att guida dig genom de grundläggande reglerna för GraphQL-språket och bästa praxis för GraphQL-frågor.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Att fråga ett GraphQL API
 
-### Anatomien av en GraphQL-fråga
+### The Anatomy of a GraphQL Query
 
 Till skillnad från REST API bygger ett GraphQL API på ett schema som definierar vilka frågor som kan utföras.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-Listan över syntaktiska do's and don'ts är lång, men här är de viktigaste reglerna att tänka på när det gäller att skriva GraphQL-förfrågningar:
+## Rules for Writing GraphQL Queries
 
 - Varje `queryName` får endast användas en gång per operation.
 - Varje `field` får bara användas en gång i ett urval (vi kan inte fråga `id` två gånger under `token`)
@@ -61,27 +59,27 @@ Listan över syntaktiska do's and don'ts är lång, men här är de viktigaste r
 - I en given lista med variabler måste var och en av dem vara unik.
 - Alla definierade variabler måste användas.
 
-Om du inte följer ovanstående regler kommer du att få ett felmeddelande från Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Att skicka en fråga till ett GraphQL API
 
-GraphQL är ett språk och en uppsättning konventioner som transporteras över HTTP.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-Det innebär att du kan ställa en fråga till ett GraphQL API med hjälp av standard `fetch` (nativt eller via `@whatwg-node/fetch` eller `isomorphic-fetch`).
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Men, som det anges i ["Frågehantering från en applikation"](/querying/querying-from-an-application), rekommenderar vi att du använder vår `graph-client` som stöder unika funktioner som:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Hantering av subgrafer över olika blockkedjor: Frågehantering från flera subgrafer i en enda fråga
 - [Automatisk blockspårning](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatisk paginering](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fullt typad resultat
 
-Så här ställer du en fråga till The Graph med `graph-client`:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
-import { execute } from '../.graphclient'
+import { execute } from "../.graphclient";
 
 const query = `
 query GetToken($id: ID!) {
@@ -90,21 +88,19 @@ query GetToken($id: ID!) {
     owner
   }
 }
-`
+`;
 const variables = { id: '1' }
 
 async function main() {
-  const result = await execute(query, variables)
+  const result = await execute(query, variables);
   // `result` är fullständigt typad!
-  console.log(result)
+  console.log(result);
 }
 
 main()
 ```
 
-Fler GraphQL-klientalternativ behandlas i ["Querying from an Application"](/querying/querying-from-an-application).
-
-Nu när vi har gått igenom de grundläggande reglerna för syntax för GraphQL-förfrågningar ska vi titta på bästa praxis för att skriva GraphQL-förfrågningar.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,35 +108,35 @@ Nu när vi har gått igenom de grundläggande reglerna för syntax för GraphQL-
 
 ### Skriv alltid statiska frågor
 
-En vanlig (dålig) praxis är att dynamiskt bygga upp frågesträngar enligt följande:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
-const id = params.id
-const fields = ['id', 'owner']
+const id = params.id;
+const fields = ["id", "owner"];
 const query = `
 query GetToken {
   token(id: ${id}) {
-    ${fields.join('\n')}
+    ${fields.join("\n")}
   }
 }
-`
+`;
 
 // Execute query...
 ```
 
-Medan det tidigare avsnittet genererar en giltig GraphQL-fråga har den **många nackdelar**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - det gör det **svårare att förstå** frågan som helhet
 - utvecklare är **ansvariga för att säkert sanera stränginterpolationen**
 - att inte skicka värdena av variablerna som en del av förfrågningsparametrarna **förhindrar möjlig cache på servern**
 - det **hindrar verktyg från statisk analys av frågan** (exempel: Linter eller typgenereringsverktyg)
 
-Av dessa skäl rekommenderas det alltid att skriva frågor som statiska strängar:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
-import { execute } from 'your-favorite-graphql-client'
+import { execute } from "your-favorite-graphql-client";
 
-const id = params.id
+const id = params.id;
 const query = `
 query GetToken($id: ID!) {
   token(id: $id) {
@@ -148,7 +144,7 @@ query GetToken($id: ID!) {
     owner
   }
 }
-`
+`;
 
 const result = await execute(query, {
   variables: {
@@ -157,23 +153,23 @@ const result = await execute(query, {
 })
 ```
 
-Detta medför **många fördelar**:
+Doing so brings **many advantages**:
 
 - **Lättlästa och underhållna** frågor
 - GraphQL **server hanterar sanitet av variabler**
 - **Variabler kan cachas** på serversidan
 - **Frågor kan statiskt analyseras av verktyg** (mer om detta i följande avsnitt)
 
-**Observera: Hur man inkluderar fält villkorligt i statiska frågor**
+### How to include fields conditionally in static queries
 
-Ibland vill vi inkludera fältet `owner` endast under vissa villkor.
+You might want to include the `owner` field only on a particular condition.
 
-För detta kan vi utnyttja direktivet `@include(if:...)` på följande sätt:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
-import { execute } from 'your-favorite-graphql-client'
+import { execute } from "your-favorite-graphql-client";
 
-const id = params.id
+const id = params.id;
 const query = `
 query GetToken($id: ID!, $includeOwner: Boolean) {
   token(id: $id) {
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Observera: Det motsatta direktivet är `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL blev känd för sitt motto "Be om det du vill ha".
-
-Av den anledningen finns det ingen möjlighet i GraphQL att få alla tillgängliga fält utan att behöva lista dem individuellt.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-När du frågar GraphQL API:er, tänk alltid på att endast fråga efter de fält som faktiskt kommer att användas.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-En vanlig orsak till överhämtning är samlingar av enheter. Som standard kommer frågor att hämta 100 enheter i en samling, vilket vanligtvis är mycket mer än vad som faktiskt kommer att användas, t.ex., för att visas för användaren. Därför bör frågor nästan alltid ange first explicit och se till att de bara hämtar så många enheter som de faktiskt behöver. Detta gäller inte bara för toppnivåsamlingar i en fråga, utan ännu mer för inbäddade samlingar av enheter.
+- När du frågar GraphQL API:er, tänk alltid på att endast fråga efter de fält som faktiskt kommer att användas.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Till exempel, i följande fråga:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-Svaret kan innehålla 100 transaktioner för varje av de 100 tokens.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Om applikationen bara behöver 10 transaktioner bör frågan explicit ange `first: 10` på transaktionsfältet.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-Din applikation kan kräva att du ställer flera typer av datafrågor enligt följande:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Medan denna implementation är helt giltig kräver den två rundturer med GraphQL API:n.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-Lyckligtvis är det också giltigt att skicka flera frågor i samma GraphQL-begäran enligt följande:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Detta tillvägagångssätt kommer att **förbättra den övergripande prestandan** genom att minska tiden som spenderas på nätverket (sparar en omväg till API:n) och kommer att ge en **mer koncis implementation**.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Dra nytta av GraphQL-fragment
 
-En användbar funktion för att skriva GraphQL-frågor är GraphQL-fragment.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-Om vi tittar på följande fråga kommer du att märka att vissa fält upprepas över flera urvalssatser (`{ ... }`):
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-Sådana upprepade fält (`id`, `active`, `status`) medför många problem:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- svårare att läsa för mer omfattande frågor
-- när du använder verktyg som genererar TypeScript-typer baserat på frågor (_mer om det i den sista avsnittet_), kommer `newDelegate` och `oldDelegate` att resultera i två olika inline-gränssnitt.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-En omstrukturerad version av frågan skulle vara följande:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Att använda GraphQL `fragment` kommer att förbättra läsbarheten (särskilt i större skala) och leda till bättre generering av TypeScript-typer.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-När du använder verktyget för typsgenerering kommer den ovanstående frågan att generera en korrekt typ av `DelegateItemFragment` (_se sista avsnittet_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### Dos and Don'ts för GraphQL Fragment
 
-**Fragmentbas måste vara en typ**
+### Fragmentbas måste vara en typ
 
-Ett fragment kan inte baseras på en oanvändbar typ, kort sagt, **på en typ som inte har fält**:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` är en **skalär** (inbyggd "vanlig" typ) som inte kan användas som grund för ett fragment.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Hur man sprider ett fragment**
+#### Hur man sprider ett fragment
 
-Fragment är definierade på specifika typer och bör användas i enlighet med det i frågor.
+Fragments are defined on specific types and should be used accordingly in queries.
 
 Exempel:
 
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` och `oldDelegate` är av typen `Transcoder`.
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-Det är inte möjligt att sprida ett fragment av typ `Vote` här.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Definiera fragment som en atomisk affärsenhet för data**
+#### Definiera fragment som en atomisk affärsenhet för data
 
-GraphQL Fragment måste definieras baserat på deras användning.
+GraphQL `Fragment`s must be defined based on their usage.
 
-För de flesta användningsfall är det tillräckligt att definiera ett fragment per typ (i fallet med upprepade fält eller typgenerering).
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Här är en tumregel för användning av fragment:
+Here is a rule of thumb for using fragments:
 
-- när fält av samma typ upprepas i en fråga, gruppera dem i ett fragment
-- när liknande men inte samma fält upprepas, skapa flera fragment, t.ex.
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## De väsentliga verktygen
+## The Essential Tools
 
 ### Webbaserade GraphQL-upptäckare
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### GraphQL Linting
 
-För att hålla dig uppdaterad med de tidigare nämnda bästa praxis och syntaktiska regler rekommenderas det starkt att använda följande arbetsflöde och IDE-verktyg.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ För att hålla dig uppdaterad med de tidigare nämnda bästa praxis och syntakt
 - `@graphql-eslint/no-unused variables`: bör en given variabel förbli oanvänd?
 - och mer!
 
-Detta kommer att tillåta dig att **upptäcka fel utan ens att testa frågor** på lekplatsen eller köra dem i produktion!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### IDE-tillägg
 
-**VSCode och GraphQL**
+**VSCode and GraphQL**
 
-[GraphQL VSCode-tillägget](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) är ett utmärkt komplement till din utvecklingsarbetsflöde för att få:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntaxmarkering
-- autokompletteringsförslag
-- validering mot schema
-- snuttar
-- gå till definition för fragment och inmatningstyper
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Om du använder `graphql-eslint` är [ESLint VSCode-tillägget](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) ett måste för att visualisera fel och varningar korrekt infogade i din kod.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij och GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[JS GraphQL-tillägget](https://plugins.jetbrains.com/plugin/8097-graphql/) kommer att förbättra din upplevelse av att arbeta med GraphQL genom att tillhandahålla:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntaxmarkering
-- autokompletteringsförslag
-- validering mot schema
-- snuttar
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Mer information om denna [WebStorm-artikel](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) som visar upp alla tilläggets huvudfunktioner.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From ae37d215a1a6daf1a1732f6952b771f377dc9c22 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:39 -0500
Subject: [PATCH 0832/1325] New translations querying-best-practices.mdx
 (Turkish)

---
 .../tr/querying/querying-best-practices.mdx   | 141 +++++++++---------
 1 file changed, 68 insertions(+), 73 deletions(-)

diff --git a/website/pages/tr/querying/querying-best-practices.mdx b/website/pages/tr/querying/querying-best-practices.mdx
index 3878ac485e8f..f5cc0521e5b3 100644
--- a/website/pages/tr/querying/querying-best-practices.mdx
+++ b/website/pages/tr/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,24 +59,24 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
-GraphQL, HTTP aracılığıyla aktarım yapan bir dil ve kurallar bütünüdür.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-Bu, bir GraphQL API'sini standart `fetch` kullanarak (yerel olarak yada `@whatwg-node/fetch` veya `isomorphic-fetch`) sorgulayabileceğiniz anlamına gelir.
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Ancak, ["Bir Uygulamadan Sorgulama"](/querying/querying-from-an-application) bölümünde belirtildiği gibi, aşağıdaki gibi benzersiz özellikleri destekleyen `graph-client`'ımızı kullanmanızı öneririz:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Graph'ı `graph-client` ile nasıl sorgulayacağınız aşağıda açıklanmıştır:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-Daha fazla GraphQL istemci alternatifi ["Bir Uygulamadan Sorgulama"](/querying/querying-from-an-application) bölümünde ele alınmıştır.
-
-GraphQL sorguları sözdiziminin temel kurallarını ele aldığımıza göre, şimdi GraphQL sorgusu yazmanın en iyi uygulamalarına bakalım.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ GraphQL sorguları sözdiziminin temel kurallarını ele aldığımıza göre, 
 
 ### Always write static queries
 
-Yaygın (hatalı) bir yöntem, sorgu dizelerini aşağıdaki gibi dinamik olarak oluşturmaktır:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-Yukarıdaki kod parçacığı geçerli bir GraphQL sorgusu oluştursa da, **birçok dezavantajı vardır**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - it makes it **harder to understand** the query as a whole
 - developers are **responsible for safely sanitizing the string interpolation**
 - not sending the values of the variables as part of the request parameters **prevent possible caching on server-side**
 - it **prevents tools from statically analyzing the query** (ex: Linter, or type generations tools)
 
-Bu nedenle, sorguların her zaman statik dizeler olarak yazılması önerilir:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-Bunu yapmak **birçok avantajı** beraberinde getirir:
+Doing so brings **many advantages**:
 
 - **Easy to read and maintain** queries
 - The GraphQL **server handles variables sanitization**
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Not: Alanları statik sorgulara koşullu olarak dahil etme**
+### How to include fields conditionally in static queries
 
-`owner` alanını yalnızca belirli bir koşulda dahil etmek isteyebiliriz.
+You might want to include the `owner` field only on a particular condition.
 
-Bunun için `@include(if:...)` direktifinden aşağıdaki şekilde yararlanabiliriz:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Not: Zıt direktif `@skip(if: ...)` şeklindedir.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL, "Ne istiyorsanız isteyin" sloganıyla ünlenmiştir.
-
-Bu nedenle, GraphQL'de mevcut tüm alanları tek tek listelemeden almanın bir yolu yoktur.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-GraphQL API'leri sorgularken, her zaman sadece gerçekten kullanılacak alanları sorgulamayı düşünmelisiniz.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-Aşırı alma'nın(over-fetching) yaygın bir nedeni varlık koleksiyonlarıdır. Varsayılan olarak, sorgular bir koleksiyondaki 100 varlığı getirecektir, bu da genellikle kullanıcıya göstermek için gerçekte kullanılacak olandan çok daha fazladır. Bu nedenle sorgular neredeyse her zaman ilk olarak açıkça ayarlanmalı ve yalnızca gerçekten ihtiyaç duydukları kadar varlık getirdiklerinden emin olmalıdırlar. Bu sadece bir sorgudaki üst düzey koleksiyonlar için değil, aynı zamanda iç içe geçmiş varlık koleksiyonları için de geçerlidir.
+- GraphQL API'leri sorgularken, her zaman sadece gerçekten kullanılacak alanları sorgulamayı düşünmelisiniz.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Örneğin, aşağıdaki sorguda:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-Yanıt, 100 tokenin her biri için 100 işlem içerebilir.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Uygulama yalnızca 10 işleme ihtiyaç duyuyorsa, sorgu işlemler alanında `first: 10`'u açıkça ayarlamalıdır.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-Uygulamanız aşağıdaki gibi birden fazla veri türünü sorgulamayı gerektirebilir:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Bu uygulama tamamen geçerli olsa da, GraphQL API ile iki git-gel gerektirecektir.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-Neyse ki, aşağıdaki gibi aynı GraphQL isteğinde birden fazla sorgu göndermek de geçerlidir:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Bu yaklaşım, ağ üzerinde harcanan zamanı azaltarak **genel performansı artıracak** (API'ye gidiş gelişten tasarruf etmenizi sağlar) ve daha **kısa bir uygulama** sağlayacaktır.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Leverage GraphQL Fragments
 
-GraphQL sorguları yazmak için yararlı bir özellik GraphQL Fragment'tir.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-Aşağıdaki sorguya baktığınızda, bazı alanların birden fazla Seçim Setinde tekrarlandığını fark edeceksiniz (`{ ... }`):
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-Bu tür tekrarlanan alanlar (`id`, `active`, `status`) birçok sorunu beraberinde getirir:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-Sorgunun yeniden yapılandırılmış bir versiyonu aşağıdaki gibi olacaktır:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-GraphQL `fragment` kullanımı okunabilirliği artıracak (özellikle ölçeklendirmede) ve aynı zamanda daha iyi TypeScript tipleri üretilmesini sağlayacaktır.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-Tip oluşturma aracı kullanıldığında, yukarıdaki sorgu uygun bir `DelegateItemFragment` tipi oluşturacaktır (_son "Tools" bölümüne göz atın_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment tabanı bir tip olmalıdır**
+### Fragment tabanı bir tip olmalıdır
 
-Bir Fragment uygulanabilir olmayan bir tipe, kısacası **alanları olmayan bir tipe** dayandırılamaz:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` bir **skalerdir** (yerel "plain" tip) ve bir parçanın tabanı olarak kullanılamaz.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Fragment Nasıl Yayılır**
+#### Fragment Nasıl Yayılır
 
-Fragmentler belirli tiplerde tanımlanmıştır ve sorgularda buna göre kullanılmalıdır.
+Fragments are defined on specific types and should be used accordingly in queries.
 
 Örnek:
 
@@ -409,18 +404,18 @@ fragment VoteItem on Vote {
 
 `newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-`Vote` tipi bir parçayı buraya yaymak mümkün değildir.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Fragment'ı atomik bir veri iş birimi olarak tanımlayın**
+#### Fragment'ı atomik bir veri iş birimi olarak tanımlayın
 
-GraphQL Fragment kullanımlarına göre tanımlanmalıdır.
+GraphQL `Fragment`s must be defined based on their usage.
 
-Çoğu kullanım durumu için, tip başına bir parça tanımlamak (tekrarlanan alan kullanımı veya tip üretimi durumunda) yeterlidir.
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-İşte Fragment kullanımı için temel bir kural:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### GraphQL Linting
 
-Yukarıda belirtilen en iyi uygulamalara ve sözdizimsel kurallara ayak uydurmak için aşağıdaki iş akışı ve IDE araçlarının kullanılması şiddetle tavsiye edilir.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ Yukarıda belirtilen en iyi uygulamalara ve sözdizimsel kurallara ayak uydurmak
 - `@graphql-eslint/no-unused variables`: should a given variable stay unused?
 - and more!
 
-Bu, sorguları öğrenme ortamında **test etmeden** veya üretimde çalıştırmadan bile hataları yakalamanızı sağlayacaktır!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### IDE plugins
 
-**VSCode ve GraphQL**
+**VSCode and GraphQL**
 
-GraphQL [VSCode uzantısı](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql), geliştirme iş akışınız için mükemmel bir eklentidir:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Eğer `graphql-eslint` kullanıyorsanız, [ESLint VSCode uzantısı](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) kodunuzdaki hataları ve uyarıları doğru bir şekilde görselleştirmek için olmazsa olmazdır.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij ve GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[JS GraphQL eklentisi](https://plugins.jetbrains.com/plugin/8097-graphql/), GraphQL ile çalışırken deneyiminizi önemli ölçüde arttırcaktır:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Eklentinin tüm ana özelliklerini gösteren bu [WebStorm makalesinde](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) daha fazla bilgi bulabilirsiniz.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From d9ecf78f84e5801ea850689fed3700315573c44e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:40 -0500
Subject: [PATCH 0833/1325] New translations querying-best-practices.mdx
 (Ukrainian)

---
 .../uk/querying/querying-best-practices.mdx   | 145 +++++++++---------
 1 file changed, 70 insertions(+), 75 deletions(-)

diff --git a/website/pages/uk/querying/querying-best-practices.mdx b/website/pages/uk/querying/querying-best-practices.mdx
index d8fafba633eb..ed5a0e2b4af4 100644
--- a/website/pages/uk/querying/querying-best-practices.mdx
+++ b/website/pages/uk/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Найкращі практики виконання запитів
 ---
 
-The Graph забезпечує децентралізований спосіб запиту даних з блокчейнів.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-Дані мережі The Graph відображаються через GraphQL API, що полегшує запити даних за допомогою мови програмування GraphQL.
-
-Ця сторінка допоможе вам ознайомитися з основними правилами мови GraphQL та найкращими практиками виконання запитів в GraphQL.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Запити в GraphQL API
 
-### Анатомія запитів на GraphQL
+### The Anatomy of a GraphQL Query
 
 На відміну від REST API, GraphQL API побудований на основі Schema, яка визначає, які запити можуть бути виконані.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-Хоча список синтаксичних "можна" і "не можна" довгий, ось основні правила, про які слід пам'ятати, коли йдеться про написання запитів в GraphQL:
+## Rules for Writing GraphQL Queries
 
 - Кожне `queryName` може бути використане лише один раз за одну операцію.
 - Кожне `field` може бути використане лише один раз за вибірку (ми не можемо запитувати `id` двічі `token`)
@@ -61,24 +59,24 @@ query [operationName]([variableName]: [variableType]) {
 - У заданому списку змінних кожна з них має бути унікальною.
 - Всі задані змінні повинні бути використаними.
 
-Недотримання вищевказаних правил призведе до отримання помилки від Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Відправлення запиту до GraphQL API
 
-GraphQL - це мова програмування і набір механізмів, які передаються через HTTP.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-Це означає, що ви можете запитувати API GraphQL, використовуючи стандартні команди `fetch` (безпосередньо або через `@whatwg-node/fetch` or `isomorphic-fetch`).
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-Проте, як зазначено в ["Querying from an Application"](/querying/querying-from-an-application), ми рекомендуємо використовувати `graph-client`, який підтримує такі унікальні функції, як:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Робота з кросс-чейн підграфами: Отримання інформації з декількох підграфів за один запит
 - [Автоматичне відстежування блоків](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Автоматична розбивка на сторінки](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Повністю введений результат
 
-Тут ви можете побачити, як робити запит в The Graph через `graph-client`:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-Інші альтернативні GraphQL клієнти описані в ["Querying from an Application"](/querying/querying-from-an-application).
-
-Тепер, коли ми розглянули основні правила синтаксису запитів GraphQL, розгляньмо найкращі практики написання запитів в GraphQL.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ main()
 
 ### Завжди пишіть статичні запити
 
-Поширеною (негативною) практикою є динамічна побудова рядків запитів наступним чином:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-У наведеному вище фрагменті створено коректний запит до GraphQL, **він має багато недоліків**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - це ** ускладнює розуміння** запиту в цілому
 - розробник ** відповідає за безпечне очищення інтерполяції рядків**
 - не передається значення змінних у складі параметрів запиту **, щоб запобігти можливому кешуванню на стороні сервера **
 - це ** не дозволяє інструментам статично аналізувати запит ** (Linter, або інструменти для генерації типів)
 
-З цієї причини рекомендується завжди писати запити як статичні рядки:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-Це приносить **багато користі**:
+Doing so brings **many advantages**:
 
 - **Легко читати та обслуговувати** запити
 - The Graph Ql **сервер обробляє очищення змінних**
 - **Змінні можуть бути кешовані** на рівні сервера
 - **Запити можна статично аналізувати за допомогою інструментів** (більше про це в наступних розділах)
 
-**Примітка: Як умовно додавати поля в статичні запити**
+### How to include fields conditionally in static queries
 
-Можливо, ми захочемо додати поле `owner` лише за певних умов.
+You might want to include the `owner` field only on a particular condition.
 
-Для цього ми можемо використовувати директиву `@include(if:...)` наступним чином:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-Примітка: Протилежною директивою є `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL став відомим завдяки своєму слогану "Ask what you want" ("Проси, що хочеш").
-
-З цієї причини в GraphQL не існує способу отримати всі доступні поля без необхідності виведення кожного з них окремо.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-Запитуючи API GraphQL, завжди запитуйте тільки ті поля, які дійсно будуть використовуватися.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-Поширеною причиною надмірної вибірки є колекції об'єктів. За замовчуванням запити отримують 100 об'єктів з колекції, що зазвичай набагато більше, ніж буде використано, наприклад, для демонстрації користувачеві. Тому в запитах майже завжди слід явно встановлювати перше значення, і переконатися, що вони отримують стільки об'єктів, скільки їм насправді потрібно. Це стосується не лише колекцій верхнього рівня в запиті, але й навіть більше - відкладених колекцій об'єктів.
+- Запитуючи API GraphQL, завжди запитуйте тільки ті поля, які дійсно будуть використовуватися.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-Наприклад, у наступному запиті:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-Результат може містити 100 транзакцій для кожного зі 100 токенів.
+The response could contain 100 transactions for each of the 100 tokens.
 
-Якщо програмі потрібно лише 10 транзакцій, у запиті слід явно задати `first: 10` у полі транзакцій.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-Ваша програма може потребувати запитів до декількох типів даних, як показано нижче:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-Хоча ця версія є цілком прийнятною, вона потребуватиме двох раундів звернень до API GraphQL.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-На щастя, також допустимо надсилати декілька запитів в одному до GraphQL, як показано нижче:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-Такий підхід **покращить загальну продуктивність** за рахунок зменшення часу, витраченого на мережу (заощадить вам час на повернення до API) і забезпечить **компактнішу реалізацію**.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### Використання фрагментів GraphQL
 
-Корисною функцією для написання запитів до GraphQL є GraphQL Fragment.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-Дивлячись на наступний запит, ви помітите, що деякі поля повторюються в декількох Selection-Sets (`{ ... }`):
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-Такі поля, що повторюються (`id`, `active`, `status`) створюють багато проблем:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- важче читається для більш розгорнутих запитів
-- при використанні інструментів, які генерують типи TypeScript на основі запитів (_детальніше про це в останньому розділі_), `newDelegate` і `oldDelegate` призводять до появи двох різних вбудованих інтерфейсів.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-Рефакторизована версія запиту виглядатиме наступним чином:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Використання GraphQL `fragment` покращить зручність читання (особливо в масштабі), а також призведе до кращої генерації типів TypeScript.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-При використанні інструменту генерації типів, вищенаведений запит згенерує правильний `DelegateItemFragment` тип (_див. попередній розділ "Tools"_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### Фрагмент GraphQL, що можна і що не можна робити
 
-**База фрагменту повинна бути типом**
+### База фрагменту повинна бути типом
 
-Фрагмент не може ґрунтуватися на незастосовному типі, тобто на типі, що не має полів, тобто **на типі, що не має полів**:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,13 +375,13 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` - це **скалярний** (нативний "звичайний" тип), який не можна використовувати як основу фрагмента.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**Як розповсюдити Фрагмент**
+#### Як розповсюдити Фрагмент
 
-Фрагменти визначені для певних типів і повинні використовуватися в запитах відповідно до цього.
+Fragments are defined on specific types and should be used accordingly in queries.
 
-Приклад:
+Example:
 
 ```graphql
 query {
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` та `oldDelegate` відносяться до типу `Transcoder`.
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-Неможливо розповсюдити фрагмент типу `Vote` тут.
+It is not possible to spread a fragment of type `Vote` here.
 
-**Визначте фрагмент як атомну бізнес-одиницю даних**
+#### Визначте фрагмент як атомну бізнес-одиницю даних
 
-Фрагменти GraphQL повинні бути заданими на основі їх використання.
+GraphQL `Fragment`s must be defined based on their usage.
 
-Для більшості випадків використання достатньо визначити один фрагмент для кожного типу (у випадку повторного використання полів або генерації типів).
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Ось практичне правило використання Фрагмента:
+Here is a rule of thumb for using fragments:
 
-- коли поля одного типу повторюються в запиті, згрупуйте їх у Фрагмент
-- коли повторюються схожі, але не однакові поля, створіть кілька фрагментів, наприклад:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## Необхідні інструменти
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### GraphQL Linting
 
-Для того, щоб відповідати вищезгаданим найкращим практикам і синтаксичним правилам, настійно рекомендується використовувати наступні робочі алгоритми та інструменти IDE.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 - `@graphql-eslint/no-unused variables`: чи повинна дана змінна залишатися невикористаною?
 - та більше!
 
-Це дозволить вам **помічати помилки, навіть не тестуючи запити** в тестовому просторі або запускати їх у якості продукту!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### Плагіни IDE
 
-**VSCode і GraphQL**
+**VSCode and GraphQL**
 
-[GraphQL VSCode розширення](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) є чудовим доповненням до вашого процесу розробки, щоб отримати:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- виділення синтаксису
-- автозаповнення пропозицій
-- валідацію за схемою
-- фрагменти
-- перехід до визначення для фрагментів і типів вхідних даних
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-Якщо ви використовуєте `graphql-eslint`, [ESLint VSCode розширення](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint), що вкрай необхідне для правильної візуалізації помилок та попереджень, закладених у вашому коді.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij і GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) значно покращить ваш досвід роботи з GraphQL, надавши:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- виділення синтаксису
-- автозаповнення пропозицій
-- валідацію за схемою
-- фрагменти
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-Більше інформації можна знайти тут [у статті від WebStorm](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/), де продемонстровано всі основні функції плагіна.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 20b61e8096983a560e74c7ce09d8388abb0098a9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:41 -0500
Subject: [PATCH 0834/1325] New translations querying-best-practices.mdx
 (Chinese Simplified)

---
 .../zh/querying/querying-best-practices.mdx   | 143 +++++++++---------
 1 file changed, 69 insertions(+), 74 deletions(-)

diff --git a/website/pages/zh/querying/querying-best-practices.mdx b/website/pages/zh/querying/querying-best-practices.mdx
index 0f1af234da9e..9f09b3c3e636 100644
--- a/website/pages/zh/querying/querying-best-practices.mdx
+++ b/website/pages/zh/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: 查询最佳实践
 ---
 
-Graph提供了一种从区块链查询数据的去中心化方式。
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-Graph网络的数据通过GraphQL API公开，使得使用GraphQL语言查询数据更加容易。
-
-本页将指导您了解基本的GraphQL语言规则和GraphQL查询最佳实践。
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## 查询GraphQL API
 
-### GraphQL查询的剖析
+### The Anatomy of a GraphQL Query
 
 与REST API不同，GraphQL API构建在定义可以执行哪些查询的模式之上。
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-虽然语法的“是”和“不是”的列表很长，但在编写 GraphQL 查询时，以下是需要记住的重要规则:
+## Rules for Writing GraphQL Queries
 
 - 每个操作只能使用一次 `queryName`。
 - 每个`field`在选择中只能使用一次(我们不能在`token`下查询 `id` 两次)
@@ -61,24 +59,24 @@ query [operationName]([variableName]: [variableType]) {
 - 在给定的变量列表中，每个变量必须是唯一的。
 - 必须使用所有已定义的变量。
 
-不遵循上述规则将以 GraphAPI 返回的错误结束。
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### 向 GraphQL API 发送查询
 
-GraphQL 是一种通过 HTTP 传输的语言和一组协议。
+GraphQL is a language and set of conventions that transport over HTTP.
 
-这意味着您可以使用标准`fetch`(本机或通过`@whatwg-node/提取`或`isomorphic-fetch`) 查询 GraphQL API。
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-但是，正如[“从应用程序查询”](/querying/querying-from-an-application)中所说，我们建议您使用我们的`graph-client`，该客户端支持以下独特功能:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - 跨链子图处理: 在一个查询中从多个子图进行查询
 - [自动区块跟踪](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [自动分页](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - 完全类型化的结果
 
-以下是如何使用 `Graph-client` 查询Graph:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-[“从应用程序查询”](/querying/querying-from-an-application)中介绍了更多的 GraphQL 客户端替代方案。
-
-现在我们已经介绍了 GraphQL 查询语法的基本规则，接下来让我们看看 GraphQL 查询编写的最佳实践。
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ main()
 
 ### 始终编写静态查询
 
-一个常见的(不好的) 实践是动态构建查询字符串，如下所示:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-虽然上面的代码生成了一个有效的 GraphQL 查询，但是**它有很多缺点**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - 它使得从整体上**理解查询变得更加困难**
 - 开发人员**负责安全地消毒字符串插值**
 - 如果不将变量的值作为请求参数的一部分发送，则可能会**阻止服务器端的缓存**
 - 它**阻止工具静态分析查询**(例如: Linter 或类型生成工具)
 
-因此，建议始终将查询写为静态字符串:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-这样做有**很多好处**:
+Doing so brings **many advantages**:
 
 - **易于阅读和维护**查询
 - GraphQL **服务器处理变量的净化**
 - 可以在服务器级别**缓存变量**
 - **查询可以通过工具进行静态分析**(下面几节将详细介绍)
 
-**注意: 如何在静态查询中有条件地包括字段**
+### How to include fields conditionally in static queries
 
-我们可能希望仅在特定条件下包括 `owner` 字段。
+You might want to include the `owner` field only on a particular condition.
 
-为此，我们可以利用`@include (if:...)`，如下所示:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-注意：相反的指令是@skip（if：…）。
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL以其“问你所想”的口号而闻名。
-
-因此，在GraphQL中，不单独列出所有可用字段，就无法获取所有可用字段。
+GraphQL became famous for its "Ask for what you want" tagline.
 
-在查询GraphQL API时，请始终考虑只查询实际使用的字段。
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-过度获取的一个常见原因是实体集合。默认情况下，查询将获取集合中的100个实体，这通常比实际使用的实体多得多，例如，用于向用户显示的实体。因此，查询几乎总是首先显式设置，并确保它们只获取实际需要的实体。这不仅适用于查询中的一层集合，更适用于实体的嵌套集合。
+- 在查询GraphQL API时，请始终考虑只查询实际使用的字段。
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-例如，在以下查询中：
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-该响应可以包含100个代币中的100个交易。
+The response could contain 100 transactions for each of the 100 tokens.
 
-如果应用程序只需要10个交易，那么查询应该首先在交易字段上显式设置：`first: 10`。
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-您的应用程序可能需要查询多种类型的数据，如下所示：
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-虽然这个实现是完全有效的，但它需要使用GraphQL API进行两次交互。
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-幸运的是，在同一GraphQL请求中发送多个查询也是有效的，如下所示：
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-这种方法将通过减少在网络上花费的时间来**提高整体性能**（为您节省API交互的时间），并提供**更简洁的实现**。
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### 利用GraphQL片段
 
-编写GraphQL查询的一个有用功能是GraphQL片段。
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-查看以下查询，您会注意到某些字段在多个选择集(`{ ... }`) 中重复：
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-此类重复字段（`id`、`active`、`status`）会带来许多问题：
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- 当查询更广泛时将更难阅读
-- 当使用基于查询生成TypeScript类型的工具时（_上一节将详细介绍_），`newDelegate`和`oldDelegate`将产生两个不同的内联接口。
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-查询的重构版本如下：
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-使用GraphQL`fragment`将提高可读性（特别是在规模上），也将使更好的TypeScript类型生成。
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-当使用类型生成工具时，上述查询将生成一个正确的`DelegateItemFragment`类型（_请参阅上一节“工具”_）。
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL片段的注意事项
 
-**片段必须是一种类型**
+### 片段必须是一种类型
 
-片段不能基于不适用的类型，简而言之，**基于没有字段的类型**：
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt`是一个**标量**（原生“纯”类型），不能用作片段的基础类型。
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**如何传播片段**
+#### 如何传播片段
 
-片段是在特定类型上定义的，应该在查询中相应地使用。
+Fragments are defined on specific types and should be used accordingly in queries.
 
 例子:
 
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` 和 `oldDelegate` 属于`Transcoder`类型。
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-无法在此处传播`Vote`类型的片段。
+It is not possible to spread a fragment of type `Vote` here.
 
-**将片段定义为数据的原子业务单元。**
+#### 将片段定义为数据的原子业务单元。
 
-GraphQL Fragment必须根据其用法进行定义。
+GraphQL `Fragment`s must be defined based on their usage.
 
-对于大多数用例，为每个类型定义一个片段（在重复使用字段或生成类型的情况下）就足够。
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-以下是使用Fragment的经验法则：
+Here is a rule of thumb for using fragments:
 
-- 当相同类型的字段在查询中重复时，将它们分组为片段
-- 当重复类似但不相同的字段时，创建多个片段，例如：
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (主要在上架中使用)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## 重要工具
+## The Essential Tools
 
 ### GraphQL基于web的浏览器
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### GraphQL Linting
 
-为了跟上提到的最佳实践和语法规则，强烈建议使用以下工作流和IDE工具。
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 - `@graphql-eslint/no-unused variables`: 给定的变量是否应该保持未使用状态？
 - 还有更多！
 
-这将允许您**捕获错误，而无需在playground上测试查询**或在生产环境中运行查询！
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### IDE插件
 
-**VSCode和GraphQL**
+**VSCode and GraphQL**
 
-[GraphQL VSCode扩展](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql)是对开发工作流的一个极好补充，可以获得：
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- 语法高亮显示
-- 自动完成建议
-- 根据模式验证
-- 片段
-- 转到片段和输入类型的定义
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-如果您使用的是`graphql-eslit`，[ESLintVSCode扩展](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)是正确可视化代码中内联的错误和警告的必备工具。
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij和GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[JS GraphQL插件](https://plugins.jetbrains.com/plugin/8097-graphql/)将通过提供以下功能显著改善您在使用GraphQL时的体验：
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- 语法高亮显示
-- 自动完成建议
-- 根据模式验证
-- 片段
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-有关这篇[WebStorm文章](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/)的更多信息，其中展示了插件的所有主要功能。
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 7edfbfabdd41f1c6beafac16f311c498038cc8d9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:42 -0500
Subject: [PATCH 0835/1325] New translations querying-best-practices.mdx (Urdu
 (Pakistan))

---
 .../ur/querying/querying-best-practices.mdx   | 145 +++++++++---------
 1 file changed, 70 insertions(+), 75 deletions(-)

diff --git a/website/pages/ur/querying/querying-best-practices.mdx b/website/pages/ur/querying/querying-best-practices.mdx
index 297edf934885..cd9942f43ea4 100644
--- a/website/pages/ur/querying/querying-best-practices.mdx
+++ b/website/pages/ur/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: بہترین طریقوں سے کیوری کرنا
 ---
 
-گراف بلاکچینز سے ڈیٹا کو کیوری کرنے کا ایک ڈیسینٹرالائزڈ طریقہ فراہم کرتا ہے.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-گراف نیٹ ورک کا ڈیٹا GraphQL API کے ذریعے ظاہر کیا جاتا ہے، جس سے GraphQL لینگویج کے ساتھ ڈیٹا سے کیوری کرنا آسان ہو جاتا ہے.
-
-یہ صفحہ GraphQL لینگویج کے ضروری اصولوں اور GraphQL کیوریز کے بہترین طریقوں کے بارے میں آپ کی رہنمائی کرے گا.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## ایک GraphQL API کا کیوری کرنا
 
-### GraphQL کے کیوری کی اناٹومی
+### The Anatomy of a GraphQL Query
 
 REST API کے برعکس، ایک GraphQL API ایک اسکیما پر بنایا گیا ہے جو اس بات کی وضاحت کرتا ہے کہ کون سے کیوری کیے جا سکتے ہیں.
 
@@ -52,33 +50,33 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-اگرچہ نحوی کرنے اور نہ کرنے کی فہرست طویل ہے، لیکن GraphQL کی کیوریز لکھنے کی بات کرتے وقت ذہن میں رکھنے کے لیے ضروری اصول یہ ہیں:
+## Rules for Writing GraphQL Queries
 
 - ہر ایک `queryName` کو فی آپریشن صرف ایک بار استعمال کیا جانا چاہیے.
-- ہر ایک `field` کو انتخاب میں صرف ایک بار استعمال کیا جانا چاہیے (ہم `token` کے تحت دو بار `id` سے کیوری نہیں کرسکتے ہیں)
+- ہر ایک ` field ` کو انتخاب میں صرف ایک بار استعمال کیا جانا چاہیے (ہم `token` کے تحت دو بار `id` سے کیوری نہیں کرسکتے ہیں)
 - Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer).
 - کسی دلیل کو تفویض کردہ کوئی بھی متغیر اس کی قسم سے مماثل ہونا چاہیے.
 - متغیرات کی دی گئی فہرست میں، ان میں سے ہر ایک منفرد ہونا چاہیے.
 - تمام متعین متغیرات کو استعمال کیا جانا چاہیے.
 
-مندرجہ بالا قواعد کی پیروی کرنے میں ناکامی گراف API کی غلطی کے ساتھ ختم ہو جائے گی.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### GraphQL API کو ایک کیوری بھیجنا
 
-GraphQL ایک لینگویج اور کنونشنز کا مجموعہ ہے جو HTTP پر نقل و حمل کرتا ہے.
+GraphQL is a language and set of conventions that transport over HTTP.
 
-اس کا مطلب ہے کہ آپ معیاری `fetch` (مقامی طور پر یا `@whatwg-node/fetch` یا `isomorphic-fetch` کے ذریعے) کا استعمال کرتے ہوئے GraphQL API سے کیوری کرسکتے ہیں.
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-تاہم، جیسا کہ ["ایک درخواست سے کیوری کرنا"](/querying/querying-from-an-application) میں بتایا گیا ہے، ہم آپ کو ہمارا `graph-client` استعمال کرنے کی تجویز کرتے ہیں جو منفرد خصوصیات کی حمایت کرتا ہے جیسے:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - کراس چین سب گراف ہینڈلنگ: ایک کیوری میں متعدد سب گرافس سے کیوری کرنا
 - [خودکار بلاک ٹریکنگ](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [خودکار صفحہ بندی](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - مکمل طور پر ٹائپ شدہ نتیجہ
 
-`graph-client` کے ساتھ گراف سے کیوری کرنے کا طریقہ یہاں ہے:
+Here's how to query The Graph with `graph-client`:
 
 ```tsx
 import { execute } from '../.graphclient'
@@ -102,9 +100,7 @@ async function main() {
 main()
 ```
 
-مزید GraphQL کلائنٹ متبادلات کا احاطہ ["ایک درخواست سے کیوری کرنا"](/querying/querying-from-an-application) میں کیا گیا ہے.
-
-اب جب کہ ہم نے GraphQL کیوریز کی ترکیب کے بنیادی اصولوں کا احاطہ کیا ہے، آئیے اب GraphQL کیوری تحریر کے بہترین طریقوں کو دیکھتے ہیں.
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
 ---
 
@@ -112,7 +108,7 @@ main()
 
 ### ہمیشہ جامد کیوریز لکھیں
 
-ایک عام (خراب) پریکٹس مندرجہ ذیل طور پر کیوری کے سٹرنگس کو متحرک طور پر بنانا ہے:
+A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
 const id = params.id
@@ -128,14 +124,14 @@ query GetToken {
 // Execute query...
 ```
 
-جبکہ مذکورہ بالا ٹکڑا ایک درست GraphQL کیوری پیدا کرتا ہے، **اس میں بہت سی خرابیاں ہیں**:
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
 
 - یہ مجموعی طور پر کیوری کو **سمجھنا مشکل** بناتا ہے
 - ڈویلپرز **سٹرنگ انٹرپولیشن کو محفوظ طریقے سے صاف کرنے کے ذمہ دار ہیں**
 - متغیر کی ویلیوس کو درخواست کے پیرامیٹرز کے حصے کے طور پر نہ بھیجنا **سرور سائیڈ پر ممکنہ کیشنگ کو روکتا ہے**
 - یہ **ٹولز کو کیوری کا مستحکم تجزیہ کرنے سے روکتا ہے** (مثال کے طور پر: Linter، یا جنریشنز ٹولز ٹائپ کریں)
 
-اس وجہ سے، کیوریز کو ہمیشہ جامد سٹرنگس کے طور پر لکھنے کی سفارش کی جاتی ہے:
+For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -157,18 +153,18 @@ const result = await execute(query, {
 })
 ```
 
-ایسا کرنے سے **بہت سے فائدے** ہوتے ہیں:
+Doing so brings **many advantages**:
 
 - کیوریز کو **پڑھنے اور برقرار رکھنے میں آسانی**
 - GraphQL **سرور متغیرات کو صاف کرتا ہے**
 - سرور کی سطح پر **متغیرات کو کیش کیا جا سکتا ہے**
 - **کیوریز کا مستحکم طور پر ٹولز کے ذریعے تجزیہ کیا جا سکتا ہے** (مندرجہ ذیل حصوں میں اس پر مزید)
 
-**نوٹ: جامد کیوریز میں فیلڈز کو مشروط طور پر کیسے شامل کیا جائے**
+### How to include fields conditionally in static queries
 
-ہم صرف ایک خاص شرط پر `owner` فیلڈ کو شامل کرنا چاہتے ہیں.
+You might want to include the `owner` field only on a particular condition.
 
-اس کے لیے، ہم ذیل میں `@include(if:...)` ہدایت کا فائدہ اٹھا سکتے ہیں:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,19 +187,18 @@ const result = await execute(query, {
 })
 ```
 
-نوٹ: مخالف ہدایت `@skip(if: ...)` ہے.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
-GraphQL اپنی "جو چاہو مانگو" ٹیگ لائن کے لیے مشہور ہوا.
-
-اس وجہ سے، GraphQL میں، تمام دستیاب فیلڈز کو انفرادی طور پر فہرست بنائے بغیر حاصل کرنے کا کوئی طریقہ نہیں ہے.
+GraphQL became famous for its "Ask for what you want" tagline.
 
-GraphQL APIs سے کیوری کرتے وقت، ہمیشہ صرف ان فیلڈز سے کیوری کرنے کے بارے میں سوچیں جو حقیقت میں استعمال ہوں گے.
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-اوور فیچنگ کی ایک عام وجہ ہستیوں کا مجموعہ ہے۔ پہلے سے طے شدہ طور پر، کیوریز ایک مجموعہ میں 100 ہستیوں کو حاصل کریں گے، جو عام طور پر اس سے کہیں زیادہ ہوتا ہے جو اصل میں استعمال کیا جائے گا، مثلاً، صارف کو دکھانے کے لیے۔ اس لیے کیوریز کو تقریباً ہمیشہ پہلے واضح طور پر سیٹ کرنا چاہیے، اور اس بات کو یقینی بنانا چاہیے کہ وہ صرف اتنی ہی ہستیوں کو حاصل کریں جتنی انھیں درحقیقت ضرورت ہے۔ اس کا اطلاق نہ صرف کیوری میں اعلیٰ سطحی مجموعوں پر ہوتا ہے، بلکہ اس سے بھی زیادہ ہستیوں کے گھریلو مجموعوں پر ہوتا ہے.
+- GraphQL APIs سے کیوری کرتے وقت، ہمیشہ صرف ان فیلڈز سے کیوری کرنے کے بارے میں سوچیں جو حقیقت میں استعمال ہوں گے.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
-مثال کے طور پر، درج ذیل کیوری میں:
+For example, in the following query:
 
 ```graphql
 query listTokens {
@@ -218,9 +213,9 @@ query listTokens {
 }
 ```
 
-جواب میں 100 ٹوکنز میں سے ہر ایک کے لیے 100 ٹرانزیکشن ہو سکتے ہیں.
+The response could contain 100 transactions for each of the 100 tokens.
 
-اگر ایپلیکیشن کو صرف 10 ٹرانزیکشنز کی ضرورت ہے، کیوری کو واضح طور پر ٹرانزیکشنز فیلڈ پر `first: 10` سیٹ کرنا چاہیے.
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
 
 ### Use a single query to request multiple records
 
@@ -256,7 +251,7 @@ query ManyRecords {
 
 ### Combine multiple queries in a single request
 
-آپ کی درخواست کو درج ذیل کے طور پر متعدد قسم کے ڈیٹا سے کیوری کرنے کی ضرورت ہو سکتی ہے:
+Your application might require querying multiple types of data as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -286,9 +281,9 @@ const [tokens, counters] = Promise.all(
 )
 ```
 
-جب کہ یہ نفاذ مکمل طور پر درست ہے، اس کے لیے GraphQL API کے ساتھ دو چکر لگانے کی ضرورت ہوگی.
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
 
-خوش قسمتی سے، درج ذیل کے طور پر ایک ہی GraphQL درخواست میں متعدد کیوریز بھیجنا بھی درست ہے:
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
 
 ```graphql
 import { execute } from "your-favorite-graphql-client"
@@ -309,13 +304,13 @@ query GetTokensandCounters {
 const  { result: { tokens, counters } } = execute(query)
 ```
 
-یہ نقطہ نظر نیٹ ورک پر گزارے جانے والے وقت کو کم کرکے (آپ کو API کا ایک راؤنڈ ٹرپ بچاتا ہے) **مجموعی کارکردگی کو بہتر بنائے گا** اور ایک **مزید جامع نفاذ** فراہم کرے گا.
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
 
 ### لیوریج GraphQL فریگمنٹس
 
-GraphQL کیوریز لکھنے کے لیے ایک مددگار خصوصیت GraphQL فریگمنٹ ہے.
+A helpful feature to write GraphQL queries is GraphQL Fragment.
 
-درج ذیل کیوری کو دیکھتے ہوئے، آپ دیکھیں گے کہ کچھ فیلڈز کو متعدد سلیکشن سیٹس (`{ ... }`) میں دہرایا جاتا ہے:
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
 
 ```graphql
 query {
@@ -335,12 +330,12 @@ query {
 }
 ```
 
-اس طرح کے دہرائے جانے والے فیلڈز (`id`, `active`, `status`) بہت سے مسائل لاتے ہیں:
+Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- مزید وسیع کیوریز کے لیے پڑھنا مشکل ہے
-- ایسے ٹولز کا استعمال کرتے وقت جو کیوریز کی بنیاد پر ٹائپ اسکرپٹ کی قسمیں تیار کرتے ہیں (_آخری حصے میں اس پر مزید_)، `newDelegate` اور `oldDelegate` کے نتیجے میں دو الگ الگ ان لائن انٹرفیس ہوں گے.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
-کیوری کا ایک ریفیکٹر ورژن درج ذیل ہوگا:
+A refactored version of the query would be the following:
 
 ```graphql
 query {
@@ -364,15 +359,15 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-GraphQL `fragment` کا استعمال پڑھنے کی اہلیت کو بہتر بنائے گا (خاص طور پر پیمانے پر) لیکن اس کے نتیجے میں ٹائپ اسکپٹ ٹائپس جینریشن بہتر ہوں گی.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
-ٹائپ جنریشن ٹول کا استعمال کرتے وقت، مندرجہ بالا کیوری ایک مناسب `DelegateItemFragment` قسم پیدا کرے گا (_آخری "ٹولز" سیکشن دیکھیں_).
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL فریگمنٹ کیا کریں اور نہ کریں
 
-**فریگمنٹ بیس ایک ٹائپ کا ہونا چاہیے**
+### فریگمنٹ بیس ایک ٹائپ کا ہونا چاہیے
 
-ایک فریگمینٹ غیر قابل اطلاق ٹائپ پر مبنی نہیں ہو سکتا، مختصراً، **اس ٹائپ پر جس میں فیلڈز نہیں ہیں**:
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
 ```graphql
 fragment MyFragment on BigInt {
@@ -380,11 +375,11 @@ fragment MyFragment on BigInt {
 }
 ```
 
-`BigInt` ایک **اسکالر** (مقامی "سادہ" ٹائپ) ہے جسے فریگمینٹس کی بنیاد کے طور پر استعمال نہیں کیا جاسکتا.
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**فریگمینٹ پھیلانے کا طریقہ**
+#### فریگمینٹ پھیلانے کا طریقہ
 
-فریگمینٹس کی وضاحت مخصوص ٹائپس پر کی جاتی ہے اور اس کے مطابق کیوریز میں استعمال کیا جانا چاہیے.
+Fragments are defined on specific types and should be used accordingly in queries.
 
 مثال:
 
@@ -407,20 +402,20 @@ fragment VoteItem on Vote {
 }
 ```
 
-`newDelegate` اور `oldDelegate` ٹائپ `Transcoder` ہیں.
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
 
-یہاں `Vote` ٹائپ کے فریگمینٹس کو پھیلانا ممکن نہیں ہے.
+It is not possible to spread a fragment of type `Vote` here.
 
-**فریگمنٹ کو ڈیٹا کی ایٹم بزنس یونٹ کے طور پر بیان کریں**
+#### فریگمنٹ کو ڈیٹا کی ایٹم بزنس یونٹ کے طور پر بیان کریں
 
-GraphQL فریگمنٹ کو ان کے استعمال کی بنیاد پر بیان کیا جانا چاہیے.
+GraphQL `Fragment`s must be defined based on their usage.
 
-زیادہ تر استعمال کے کیس کے لیے، فی ٹائپ کے ایک فریگمینٹ کی وضاحت کرنا (بار بار فیلڈز کے استعمال یا ٹائپ جنریشن کی صورت میں) کافی ہے.
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-فریگمینٹ استعمال کرنے کے لیے یہاں انگوٹھے کا اصول ہے:
+Here is a rule of thumb for using fragments:
 
-- جب ایک ہی قسم کے فیلڈز کو ایک کیوری میں دہرایا جاتا ہے، تو انہیں ایک فریگمینٹ میں گروپ کریں
-- جب ایک جیسے لیکن ایک جیسے فیلڈز کو دہرایا نہیں جاتا ہے، تو متعدد فریگمینٹس بنائیں، مثال کے طور پر:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## ضروری اوزار
+## The Essential Tools
 
 ### GraphQL ویب پر مبنی ایکسپلوررز
 
@@ -453,7 +448,7 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 
 ### GraphQL لنٹنگ
 
-مذکورہ بالا بہترین طریقوں اور نحوی اصولوں کو برقرار رکھنے کے لیے، درج ذیل ورک فلو اور IDE ٹولز کو استعمال کرنے کی انتہائی سفارش کی جاتی ہے.
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
 
 **GraphQL ESLint**
 
@@ -465,29 +460,29 @@ If you are looking for a more flexible way to debug/test your queries, other sim
 - `@graphql-eslint/no-unused variables`: کیا دیئے گئے متغیر کو غیر استعمال شدہ رہنا چاہئے؟
 - اور مزید!
 
-یہ آپ کو پلے گراؤنڈ میں یا انہیں پروڈکشن میں چلانے کے **کیوریز کی جانچ کیے بغیر بھی غلطیوں کو پکڑنے** کی اجازت دے گا!
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
 
 ### IDE plugins
 
-**VSCode اور GraphQL**
+**VSCode and GraphQL**
 
-[GraphQL VSCode ایکسٹینشن](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) حاصل کرنے کے لیے آپ کے ترقیاتی ورک فلو میں ایک بہترین اضافہ ہے:
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- نحو کو نمایاں کرنا
-- خودکار تکمیل کی تجاویز
-- اسکیما کے خلاف توثیق
-- ٹکڑے
-- ٹکڑوں اور ان پٹ کی اقسام کے لیے تعریف پر جائیں
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
-اگر آپ `graphql-eslint` استعمال کر رہے ہیں، تو [ESLint VSCode ایکسٹینشن](https://marketplace. visualstudio. com/items? itemName=dbaeumer. vscode-eslint) ہے آپ کے کوڈ میں موجود غلطیوں اور انتباہات کو درست طریقے سے دیکھنا ضروری ہے.
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
-**WebStorm/Intellij اور GraphQL**
+**WebStorm/Intellij and GraphQL**
 
-[JS GraphQL پلگ ان](https://plugins.jetbrains.com/plugin/8097-graphql/) فراہم کر کے GraphQL کے ساتھ کام کرتے ہوئے آپ کے تجربے کو نمایاں طور پر بہتر بنائے گا:
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- نحو کو نمایاں کرنا
-- خودکار تکمیل کی تجاویز
-- اسکیما کے خلاف توثیق
-- ٹکڑے
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-اس [ویب سٹورم مضمون](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) پر مزید معلومات جو پلگ ان کی تمام اہم خصوصیات کو ظاہر کرتا ہے.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 9ece273d0e17be5d64d91bb8fb9a2cfc40337208 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:43 -0500
Subject: [PATCH 0836/1325] New translations querying-best-practices.mdx
 (Vietnamese)

---
 .../vi/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/vi/querying/querying-best-practices.mdx b/website/pages/vi/querying/querying-best-practices.mdx
index 32d1415b20fa..6e085cfe7bf1 100644
--- a/website/pages/vi/querying/querying-best-practices.mdx
+++ b/website/pages/vi/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-The Graph network's data is exposed through a GraphQL API, making it easier to query data with the GraphQL language.
-
-This page will guide you through the essential GraphQL language rules and GraphQL queries best practices.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-While the list of syntactic do's and don'ts is long, here are the essential rules to keep in mind when it comes to writing GraphQL queries:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ While the list of syntactic do's and don'ts is long, here are the essential rule
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- when using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From a56d4915a09f9e5b93ddde909ce2712f261a10cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:45 -0500
Subject: [PATCH 0837/1325] New translations querying-best-practices.mdx
 (Marathi)

---
 .../mr/querying/querying-best-practices.mdx   | 73 +++++++++----------
 1 file changed, 34 insertions(+), 39 deletions(-)

diff --git a/website/pages/mr/querying/querying-best-practices.mdx b/website/pages/mr/querying/querying-best-practices.mdx
index 138fd7d2aa6f..5112da12c581 100644
--- a/website/pages/mr/querying/querying-best-practices.mdx
+++ b/website/pages/mr/querying/querying-best-practices.mdx
@@ -2,17 +2,15 @@
 title: Querying Best Practices
 ---
 
-The Graph provides a decentralized way to query data from blockchains.
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
 
-ग्राफ नेटवर्कचा डेटा GraphQL API द्वारे उघड केला जातो, ज्यामुळे GraphQL भाषेसह डेटाची क्वेरी करणे सोपे होते.
-
-हे पृष्‍ठ तुम्हाला GraphQL भाषेचे अत्यावश्यक नियम आणि GraphQL क्वेरी सर्वोत्तम पद्धतींबद्दल मार्गदर्शन करेल.
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
 
 ---
 
 ## Querying a GraphQL API
 
-### The anatomy of a GraphQL query
+### The Anatomy of a GraphQL Query
 
 REST API च्या विपरीत, GraphQL API एका स्कीमावर तयार केले जाते जे कोणत्या क्वेरी पूर्ण केल्या जाऊ शकतात हे परिभाषित करते.
 
@@ -52,7 +50,7 @@ query [operationName]([variableName]: [variableType]) {
 }
 ```
 
-सिंटॅक्टिक करा आणि करू नका याची यादी लांब असताना, ग्राफक्यूएल क्वेरी लिहिताना लक्षात ठेवण्याचे आवश्यक नियम येथे आहेत:
+## Rules for Writing GraphQL Queries
 
 - Each `queryName` must only be used once per operation.
 - Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
@@ -61,9 +59,9 @@ query [operationName]([variableName]: [variableType]) {
 - In a given list of variables, each of them must be unique.
 - All defined variables must be used.
 
-Failing to follow the above rules will end with an error from the Graph API.
+> Note: Failing to follow these rules will result in an error from The Graph API.
 
-For a complete list of rules with code examples, please look at our [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
 
 ### Sending a query to a GraphQL API
 
@@ -71,7 +69,7 @@ GraphQL is a language and set of conventions that transport over HTTP.
 
 It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
 
-However, as stated in ["Querying from an Application"](/querying/querying-from-an-application), we recommend you to use our `graph-client` that supports unique features such as:
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
@@ -104,8 +102,6 @@ main()
 
 More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
 
-Now that we covered the basic rules of GraphQL queries syntax, let's now look at the best practices of GraphQL query writing.
-
 ---
 
 ## Best Practices
@@ -164,11 +160,11 @@ Doing so brings **many advantages**:
 - **Variables can be cached** at server-level
 - **Queries can be statically analyzed by tools** (more on this in the following sections)
 
-**Note: How to include fields conditionally in static queries**
+### How to include fields conditionally in static queries
 
-We might want to include the `owner` field only on a particular condition.
+You might want to include the `owner` field only on a particular condition.
 
-For this, we can leverage the `@include(if:...)` directive as follows:
+For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
 import { execute } from 'your-favorite-graphql-client'
@@ -191,7 +187,7 @@ const result = await execute(query, {
 })
 ```
 
-Note: The opposite directive is `@skip(if: ...)`.
+> Note: The opposite directive is `@skip(if: ...)`.
 
 ### Ask for what you want
 
@@ -199,9 +195,8 @@ GraphQL became famous for its "Ask for what you want" tagline.
 
 For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
 
-When querying GraphQL APIs, always think of querying only the fields that will be actually used.
-
-A common cause of over-fetching is collections of entities. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. Queries should therefore almost always set first explicitly, and make sure they only fetch as many entities as they actually need. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
 
 For example, in the following query:
 
@@ -337,8 +332,8 @@ query {
 
 Such repeated fields (`id`, `active`, `status`) bring many issues:
 
-- harder to read for more extensive queries
-- प्रश्नांवर आधारित TypeScript प्रकार व्युत्पन्न करणारी साधने वापरताना (_त्यावर शेवटच्या विभागात अधिक_), `newDelegate` आणि `oldDelegate` या दोन वेगळ्या इनलाइनचा परिणाम होईल इंटरफेस.
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
 
 A refactored version of the query would be the following:
 
@@ -364,13 +359,13 @@ fragment DelegateItem on Transcoder {
 }
 ```
 
-Using GraphQL `fragment` will improve readability (especially at scale) but also will result in better TypeScript types generation.
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
 
 When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
 
 ### GraphQL Fragment do's and don'ts
 
-**Fragment base must be a type**
+### Fragment base must be a type
 
 A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
 
@@ -382,7 +377,7 @@ fragment MyFragment on BigInt {
 
 `BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
 
-**How to spread a Fragment**
+#### How to spread a Fragment
 
 Fragments are defined on specific types and should be used accordingly in queries.
 
@@ -411,16 +406,16 @@ fragment VoteItem on Vote {
 
 It is not possible to spread a fragment of type `Vote` here.
 
-**Define Fragment as an atomic business unit of data**
+#### Define Fragment as an atomic business unit of data
 
-GraphQL Fragment must be defined based on their usage.
+GraphQL `Fragment`s must be defined based on their usage.
 
 For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
 
-Here is a rule of thumb for using Fragment:
+Here is a rule of thumb for using fragments:
 
-- when fields of the same type are repeated in a query, group them in a Fragment
-- when similar but not the same fields are repeated, create multiple fragments, ex:
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
 
 ```graphql
 # base fragment (mostly used in listing)
@@ -443,7 +438,7 @@ fragment VoteWithPoll on Vote {
 
 ---
 
-## The essential tools
+## The Essential Tools
 
 ### GraphQL web-based explorers
 
@@ -473,11 +468,11 @@ This will allow you to **catch errors without even testing queries** on the play
 
 The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
-- go to definition for fragments and input types
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
 
 If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
 
@@ -485,9 +480,9 @@ If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketp
 
 The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
 
-- syntax highlighting
-- autocomplete suggestions
-- validation against schema
-- snippets
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
 
-More information on this [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) that showcases all the plugin's main features.
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From 6061fa9b78795efae29d966dd45592d515277678 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:46 -0500
Subject: [PATCH 0838/1325] New translations querying-best-practices.mdx
 (Swahili)

---
 .../sw/querying/querying-best-practices.mdx   | 488 ++++++++++++++++++
 1 file changed, 488 insertions(+)
 create mode 100644 website/pages/sw/querying/querying-best-practices.mdx

diff --git a/website/pages/sw/querying/querying-best-practices.mdx b/website/pages/sw/querying/querying-best-practices.mdx
new file mode 100644
index 000000000000..6e085cfe7bf1
--- /dev/null
+++ b/website/pages/sw/querying/querying-best-practices.mdx
@@ -0,0 +1,488 @@
+---
+title: Querying Best Practices
+---
+
+The Graph provides a decentralized way to query data from blockchains. Its data is exposed through a GraphQL API, making it easier to query with the GraphQL language.
+
+Learn the essential GraphQL language rules and best practices to optimize your subgraph.
+
+---
+
+## Querying a GraphQL API
+
+### The Anatomy of a GraphQL Query
+
+Unlike REST API, a GraphQL API is built upon a Schema that defines which queries can be performed.
+
+For example, a query to get a token using the `token` query will look as follows:
+
+```graphql
+query GetToken($id: ID!) {
+  token(id: $id) {
+    id
+    owner
+  }
+}
+```
+
+which will return the following predictable JSON response (_when passing the proper `$id` variable value_):
+
+```json
+{
+  "token": {
+    "id": "...",
+    "owner": "..."
+  }
+}
+```
+
+GraphQL queries use the GraphQL language, which is defined upon [a specification](https://spec.graphql.org/).
+
+The above `GetToken` query is composed of multiple language parts (replaced below with `[...]` placeholders):
+
+```graphql
+query [operationName]([variableName]: [variableType]) {
+  [queryName]([argumentName]: [variableName]) {
+    # "{ ... }" express a Selection-Set, we are querying fields from `queryName`.
+    [field]
+    [field]
+  }
+}
+```
+
+## Rules for Writing GraphQL Queries
+
+- Each `queryName` must only be used once per operation.
+- Each `field` must be used only once in a selection (we cannot query `id` twice under `token`)
+- Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer).
+- Any variable assigned to an argument must match its type.
+- In a given list of variables, each of them must be unique.
+- All defined variables must be used.
+
+> Note: Failing to follow these rules will result in an error from The Graph API.
+
+For a complete list of rules with code examples, check out [GraphQL Validations guide](/release-notes/graphql-validations-migration-guide/).
+
+### Sending a query to a GraphQL API
+
+GraphQL is a language and set of conventions that transport over HTTP.
+
+It means that you can query a GraphQL API using standard `fetch` (natively or via `@whatwg-node/fetch` or `isomorphic-fetch`).
+
+However, as mentioned in ["Querying from an Application"](/querying/querying-from-an-application), it's recommended to use `graph-client`, which supports the following unique features:
+
+- Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
+- [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
+- [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
+- Fully typed result
+
+Here's how to query The Graph with `graph-client`:
+
+```tsx
+import { execute } from '../.graphclient'
+
+const query = `
+query GetToken($id: ID!) {
+  token(id: $id) {
+    id
+    owner
+  }
+}
+`
+const variables = { id: '1' }
+
+async function main() {
+  const result = await execute(query, variables)
+  // `result` is fully typed!
+  console.log(result)
+}
+
+main()
+```
+
+More GraphQL client alternatives are covered in ["Querying from an Application"](/querying/querying-from-an-application).
+
+---
+
+## Best Practices
+
+### Always write static queries
+
+A common (bad) practice is to dynamically build query strings as follows:
+
+```tsx
+const id = params.id
+const fields = ['id', 'owner']
+const query = `
+query GetToken {
+  token(id: ${id}) {
+    ${fields.join('\n')}
+  }
+}
+`
+
+// Execute query...
+```
+
+While the above snippet produces a valid GraphQL query, **it has many drawbacks**:
+
+- it makes it **harder to understand** the query as a whole
+- developers are **responsible for safely sanitizing the string interpolation**
+- not sending the values of the variables as part of the request parameters **prevent possible caching on server-side**
+- it **prevents tools from statically analyzing the query** (ex: Linter, or type generations tools)
+
+For this reason, it is recommended to always write queries as static strings:
+
+```tsx
+import { execute } from 'your-favorite-graphql-client'
+
+const id = params.id
+const query = `
+query GetToken($id: ID!) {
+  token(id: $id) {
+    id
+    owner
+  }
+}
+`
+
+const result = await execute(query, {
+  variables: {
+    id,
+  },
+})
+```
+
+Doing so brings **many advantages**:
+
+- **Easy to read and maintain** queries
+- The GraphQL **server handles variables sanitization**
+- **Variables can be cached** at server-level
+- **Queries can be statically analyzed by tools** (more on this in the following sections)
+
+### How to include fields conditionally in static queries
+
+You might want to include the `owner` field only on a particular condition.
+
+For this, you can leverage the `@include(if:...)` directive as follows:
+
+```tsx
+import { execute } from 'your-favorite-graphql-client'
+
+const id = params.id
+const query = `
+query GetToken($id: ID!, $includeOwner: Boolean) {
+  token(id: $id) {
+    id
+    owner @include(if: $includeOwner)
+  }
+}
+`
+
+const result = await execute(query, {
+  variables: {
+    id,
+    includeOwner: true,
+  },
+})
+```
+
+> Note: The opposite directive is `@skip(if: ...)`.
+
+### Ask for what you want
+
+GraphQL became famous for its "Ask for what you want" tagline.
+
+For this reason, there is no way, in GraphQL, to get all available fields without having to list them individually.
+
+- When querying GraphQL APIs, always think of querying only the fields that will be actually used.
+- Make sure queries only fetch as many entities as you actually need. By default, queries will fetch 100 entities in a collection, which is usually much more than what will actually be used, e.g., for display to the user. This applies not just to top-level collections in a query, but even more so to nested collections of entities.
+
+For example, in the following query:
+
+```graphql
+query listTokens {
+  tokens {
+    # will fetch up to 100 tokens
+    id
+    transactions {
+      # will fetch up to 100 transactions
+      id
+    }
+  }
+}
+```
+
+The response could contain 100 transactions for each of the 100 tokens.
+
+If the application only needs 10 transactions, the query should explicitly set `first: 10` on the transactions field.
+
+### Use a single query to request multiple records
+
+By default, subgraphs have a singular entity for one record. For multiple records, use the plural entities and filter: `where: {id_in:[X,Y,Z]}` or `where: {volume_gt:100000}`
+
+Example of inefficient querying:
+
+```graphql
+query SingleRecord {
+  entity(id: X) {
+    id
+    name
+  }
+}
+query SingleRecord {
+  entity(id: Y) {
+    id
+    name
+  }
+}
+```
+
+Example of optimized querying:
+
+```graphql
+query ManyRecords {
+  entities(where: { id_in: [X, Y] }) {
+    id
+    name
+  }
+}
+```
+
+### Combine multiple queries in a single request
+
+Your application might require querying multiple types of data as follows:
+
+```graphql
+import { execute } from "your-favorite-graphql-client"
+
+const tokensQuery = `
+query GetTokens {
+  tokens(first: 50) {
+    id
+    owner
+  }
+}
+`
+const countersQuery = `
+query GetCounters {
+  counters {
+    id
+    value
+  }
+}
+`
+
+const [tokens, counters] = Promise.all(
+  [
+    tokensQuery,
+    countersQuery,
+  ].map(execute)
+)
+```
+
+While this implementation is totally valid, it will require two round trips with the GraphQL API.
+
+Fortunately, it is also valid to send multiple queries in the same GraphQL request as follows:
+
+```graphql
+import { execute } from "your-favorite-graphql-client"
+
+const query = `
+query GetTokensandCounters {
+  tokens(first: 50) {
+    id
+    owner
+  }
+  counters {
+    id
+    value
+  }
+}
+`
+
+const  { result: { tokens, counters } } = execute(query)
+```
+
+This approach will **improve the overall performance** by reducing the time spent on the network (saves you a round trip to the API) and will provide a **more concise implementation**.
+
+### Leverage GraphQL Fragments
+
+A helpful feature to write GraphQL queries is GraphQL Fragment.
+
+Looking at the following query, you will notice that some fields are repeated across multiple Selection-Sets (`{ ... }`):
+
+```graphql
+query {
+  bondEvents {
+    id
+    newDelegate {
+      id
+      active
+      status
+    }
+    oldDelegate {
+      id
+      active
+      status
+    }
+  }
+}
+```
+
+Such repeated fields (`id`, `active`, `status`) bring many issues:
+
+- More extensive queries become harder to read.
+- When using tools that generate TypeScript types based on queries (_more on that in the last section_), `newDelegate` and `oldDelegate` will result in two distinct inline interfaces.
+
+A refactored version of the query would be the following:
+
+```graphql
+query {
+  bondEvents {
+    id
+    newDelegate {
+      ...DelegateItem
+    }
+    oldDelegate {
+      ...DelegateItem
+    }
+  }
+}
+
+# we define a fragment (subtype) on Transcoder
+# to factorize repeated fields in the query
+fragment DelegateItem on Transcoder {
+  id
+  active
+  status
+}
+```
+
+Using GraphQL `fragment` will improve readability (especially at scale) and result in better TypeScript types generation.
+
+When using the types generation tool, the above query will generate a proper `DelegateItemFragment` type (_see last "Tools" section_).
+
+### GraphQL Fragment do's and don'ts
+
+### Fragment base must be a type
+
+A Fragment cannot be based on a non-applicable type, in short, **on type not having fields**:
+
+```graphql
+fragment MyFragment on BigInt {
+  # ...
+}
+```
+
+`BigInt` is a **scalar** (native "plain" type) that cannot be used as a fragment's base.
+
+#### How to spread a Fragment
+
+Fragments are defined on specific types and should be used accordingly in queries.
+
+Example:
+
+```graphql
+query {
+  bondEvents {
+    id
+    newDelegate {
+      ...VoteItem # Error! `VoteItem` cannot be spread on `Transcoder` type
+    }
+    oldDelegate {
+      ...VoteItem
+    }
+  }
+}
+
+fragment VoteItem on Vote {
+  id
+  voter
+}
+```
+
+`newDelegate` and `oldDelegate` are of type `Transcoder`.
+
+It is not possible to spread a fragment of type `Vote` here.
+
+#### Define Fragment as an atomic business unit of data
+
+GraphQL `Fragment`s must be defined based on their usage.
+
+For most use-case, defining one fragment per type (in the case of repeated fields usage or type generation) is sufficient.
+
+Here is a rule of thumb for using fragments:
+
+- When fields of the same type are repeated in a query, group them in a `Fragment`.
+- When similar but different fields are repeated, create multiple fragments, for instance:
+
+```graphql
+# base fragment (mostly used in listing)
+fragment Voter on Vote {
+  id
+  voter
+}
+
+# extended fragment (when querying a detailed view of a vote)
+fragment VoteWithPoll on Vote {
+  id
+  voter
+  choiceID
+  poll {
+    id
+    proposal
+  }
+}
+```
+
+---
+
+## The Essential Tools
+
+### GraphQL web-based explorers
+
+Iterating over queries by running them in your application can be cumbersome. For this reason, don't hesitate to use [Graph Explorer](https://thegraph.com/explorer) to test your queries before adding them to your application. Graph Explorer will provide you a preconfigured GraphQL playground to test your queries.
+
+If you are looking for a more flexible way to debug/test your queries, other similar web-based tools are available such as [Altair](https://altairgraphql.dev/) and [GraphiQL](https://graphiql-online.com/graphiql).
+
+### GraphQL Linting
+
+In order to keep up with the mentioned above best practices and syntactic rules, it is highly recommended to use the following workflow and IDE tools.
+
+**GraphQL ESLint**
+
+[GraphQL ESLint](https://the-guild.dev/graphql/eslint/docs/getting-started) will help you stay on top of GraphQL best practices with zero effort.
+
+[Setup the "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) config will enforce essential rules such as:
+
+- `@graphql-eslint/fields-on-correct-type`: is a field used on a proper type?
+- `@graphql-eslint/no-unused variables`: should a given variable stay unused?
+- and more!
+
+This will allow you to **catch errors without even testing queries** on the playground or running them in production!
+
+### IDE plugins
+
+**VSCode and GraphQL**
+
+The [GraphQL VSCode extension](https://marketplace.visualstudio.com/items?itemName=GraphQL.vscode-graphql) is an excellent addition to your development workflow to get:
+
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+- Go to definition for fragments and input types
+
+If you are using `graphql-eslint`, the [ESLint VSCode extension](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) is a must-have to visualize errors and warnings inlined in your code correctly.
+
+**WebStorm/Intellij and GraphQL**
+
+The [JS GraphQL plugin](https://plugins.jetbrains.com/plugin/8097-graphql/) will significantly improve your experience while working with GraphQL by providing:
+
+- Syntax highlighting
+- Autocomplete suggestions
+- Validation against schema
+- Snippets
+
+For more information on this topic, check out the [WebStorm article](https://blog.jetbrains.com/webstorm/2019/04/featured-plugin-js-graphql/) which showcases all the plugin's main features.

From b00609cb06c97c9be6ff2ae2b126cff193ebebf8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:47 -0500
Subject: [PATCH 0839/1325] New translations querying-from-an-application.mdx
 (Romanian)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/ro/querying/querying-from-an-application.mdx b/website/pages/ro/querying/querying-from-an-application.mdx
index 84c489360087..2e9b52d3dac7 100644
--- a/website/pages/ro/querying/querying-from-an-application.mdx
+++ b/website/pages/ro/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Pasul 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Pasul 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Pasul 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Pasul 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### Pasul 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Pasul 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Pasul 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### Pasul 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From a5dc00ccedf5613d6af9a52450185168f81e6443 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:48 -0500
Subject: [PATCH 0840/1325] New translations querying-from-an-application.mdx
 (French)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/fr/querying/querying-from-an-application.mdx b/website/pages/fr/querying/querying-from-an-application.mdx
index d469aa5124fe..7d79bc448cea 100644
--- a/website/pages/fr/querying/querying-from-an-application.mdx
+++ b/website/pages/fr/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Interrogation à partir d'une application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (point de terminaison de test)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-À l'aide du point de terminaison GraphQL, vous pouvez utiliser diverses bibliothèques client GraphQL pour interroger le subgraph et remplir votre application avec les données indexées par le subgraph.
-
-Voici quelques-uns des clients GraphQL les plus populaires de l'écosystème et comment les utiliser :
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## Clients GraphQL
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph fournit son propre client GraphQL, `graph-client` qui prend en charge des fonctionnalités uniques telles que :
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Gestion des subgraphs inter-chaînes : interrogation à partir de plusieurs subgraphs en une seule requête
 - [Suivi automatique des blocs](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Pagination automatique](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Résultat entièrement typé
 
-Également intégré aux clients GraphQL populaires tels qu'Apollo et URQL et compatible avec tous les environnements (React, Angular, Node.js, React Native), l'utilisation de `graph-client` vous offrira la meilleure expérience d'interaction avec The Graphique.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Voyons comment récupérer les données d'un subgraph avec `graphql-client`.
+#### Étape 1
 
-Pour commencer, assurez-vous d'installer le CLI du graph client dans votre projet:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Étape 2
+
 Définissez votre requête dans un fichier `.graphql` (ou dans votre fichier `.js` ou `.ts`) :
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Ensuite, créez un fichier de configuration (appelé `.graphclientrc.yml`) et pointez vers vos points de terminaison GraphQL fournis par The Graph, par exemple :
+#### Étape 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-L’exécution de la commande CLI Graph Client suivante générera du code JavaScript tapé et prêt à être utilisé :
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Enfin, mettez à jour votre fichier `.ts` pour utiliser les documents GraphQL typés générés :
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -132,33 +144,35 @@ function App() {
 }
 ```
 
-**⚠️ Avis important**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` est parfaitement intégré à d'autres clients GraphQL tels que le client Apollo, URQL ou React Query ; vous [trouverez des exemples dans le référentiel officiel](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Cependant, si vous choisissez d'utiliser un autre client, gardez à l'esprit que **vous ne pourrez pas utiliser la gestion des subgraphs inter-chaînes ou la pagination automatique, qui sont des fonctionnalités essentielles pour les requêtes. Le graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Le client Apollo
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-Le [Client Apollo](https://www.apollographql.com/docs/) est le client GraphQL omniprésent dans l'écosystème front-end.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Disponible pour React, Angular, Vue, Ember, iOS et Android, Apollo Client, bien que le client le plus lourd, apporte de nombreuses fonctionnalités pour créer une interface utilisateur avancée sur GraphQL :
+### Fetch Data with Apollo Client
 
-- gestion avancée des erreurs
-- pagination
-- data prefetching
-- optimistic UI
-- gestion de l'État local
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Voyons comment récupérer les données d'un subgraph avec le client Apollo dans un projet Web.
+#### Étape 1
 
-Tout d'abord, installez `@apollo/client` et `graphql` :
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Ensuite, vous pouvez interroger l'API avec le code suivant :
+#### Étape 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -191,6 +205,8 @@ client
   })
 ```
 
+#### Étape 3
+
 Pour utiliser des variables, vous pouvez transmettre un argument `variables` à la requête :
 
 ```javascript
@@ -222,24 +238,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Une autre option est [URQL](https://formidable.com/open-source/urql/) qui est disponible dans les environnements Node.js, React/Preact, Vue et Svelte, avec des fonctionnalités plus avancées. caractéristiques:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Système de cache flexible
 - Conception extensible (facilitant l’ajout de nouvelles fonctionnalités par-dessus)
 - Offre légère (~ 5 fois plus légère que Apollo Client)
 - Prise en charge des téléchargements de fichiers et du mode hors ligne
 
-Voyons comment récupérer les données d'un subgraph avec URQL dans un projet Web.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-Tout d'abord, installez `urql` et `graphql` :
+#### Étape 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Ensuite, vous pouvez interroger l'API avec le code suivant :
+#### Étape 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 0b059be1a3990ed119ae3083a62800d6b8e2f462 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:49 -0500
Subject: [PATCH 0841/1325] New translations querying-from-an-application.mdx
 (Spanish)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/es/querying/querying-from-an-application.mdx b/website/pages/es/querying/querying-from-an-application.mdx
index 7a23241a3451..d15fea274da7 100644
--- a/website/pages/es/querying/querying-from-an-application.mdx
+++ b/website/pages/es/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Consultar desde una Aplicación
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (endpoint de prueba)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Usando el endpoint de GraphQL, puedes usar varias librerías de Clientes de GraphQL para consultar el subgrafo y rellenar tu aplicación con los datos indexados por el subgrafo.
-
-A continuación se presentan un par de clientes GraphQL más populares en el ecosistema y cómo utilizarlos:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## Clientes de GraphQL
+## Using Popular GraphQL Clients
 
-### Cliente de Graph
+### Graph Client
 
-The Graph proporciona su propio cliente GraphQL, `graph-client`, que admite características únicas como:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Manejo de subgrafos cross-chain: consultas desde múltiples subgrafos en una sola consulta
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Resultado completamente tipificado
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Paso 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Paso 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Paso 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Cliente Apollo
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Paginación
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling (manejo avanzado de errores)
-- pagination (paginado)
-- data prefetching (captura previa de datos)
-- optimistic UI (interfaz de usuario optimista)
-- local state management (gestión de estado local)
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Paso 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-A continuación, puedes consultar la API con el siguiente código:
+#### Paso 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Paso 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system (Sistema de caché flexible)
 - Extensible design (Diseño extensible, que facilita agregar nuevas capacidades encima)
 - Lightweight bundle (Paquete ligero, ~5 veces más ligero que Apollo Client)
 - Soporte para carga de archivos y modo fuera de línea
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Paso 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-A continuación, puedes consultar la API con el siguiente código:
+#### Paso 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From da4c13e860abc5776bd637e1ddb8be433d9931ca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:50 -0500
Subject: [PATCH 0842/1325] New translations querying-from-an-application.mdx
 (Arabic)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/ar/querying/querying-from-an-application.mdx b/website/pages/ar/querying/querying-from-an-application.mdx
index e415babb3be5..552464f28803 100644
--- a/website/pages/ar/querying/querying-from-an-application.mdx
+++ b/website/pages/ar/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: الاستعلام من التطبيق
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (اختبار endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-استعلامات (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-استعلامات (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-باستخدام GraphQL endpoint ، يمكنك استخدام العديد من مكتبات GraphQL Client للاستعلام عن ال Subgraph وملء تطبيقك بالبيانات المفهرسة بواسطة ال Subgraph.
-
-في ما يلي بعض عملاء GraphQL الأكثر شيوعا في النظام البيئي وكيفية استخدامها:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - التعامل مع ال subgraph عبر السلاسل: الاستعلام من عدة subgraphs عبر استعلام واحد
 - [تتبع الكتلة التلقائي](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [ترقيم الصفحات التلقائي](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - نتيجة مكتوبة بالكامل
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Step 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Step 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Step 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### عميل Apollo
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Step 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-بعد ذلك يمكنك الاستعلام عن API بالكود التالي:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Step 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Step 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-بعد ذلك يمكنك الاستعلام عن API بالكود التالي:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From d3c817eafbfed99b4aa5001452a92326b7270a4f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:51 -0500
Subject: [PATCH 0843/1325] New translations querying-from-an-application.mdx
 (Czech)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/cs/querying/querying-from-an-application.mdx b/website/pages/cs/querying/querying-from-an-application.mdx
index 89f7bbab0067..20538749ff25 100644
--- a/website/pages/cs/querying/querying-from-an-application.mdx
+++ b/website/pages/cs/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Dotazování z aplikace
 ---
 
-Po nasazení podgrafu do aplikace Podgraf Studio nebo Graf Explorer se zobrazí koncový bod GraphQL API, který by měl vypadat takto:
+Learn how to query The Graph from your application.
 
-**Podgraf Studio (testovací koncový bod)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Podgraf Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Průzkumník grafů**
+### Průzkumník grafů
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Pomocí koncového bodu GraphQL můžete použít různé knihovny GraphQL Client k dotazování podgrafu a naplnění aplikace daty indexovanými podgraf.
-
-Zde je několik nejoblíbenějších klientů GraphQL v ekosystému a návod, jak je používat:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## Klienti GraphQL
+## Using Popular GraphQL Clients
 
-### Graf klient
+### Graph Client
 
-Graf poskytuje vlastního klienta GraphQL, `graph-client`, který podporuje jedinečné funkce, jako jsou:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Manipulace s podgrafy napříč řetězci: Dotazování z více podgrafů v jednom dotazu
 - [Automatické sledování](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatické stránkování](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Plně zadaný výsledekv
 
-Je také integrován s populárními klienty GraphQL, jako jsou Apollo a URQL, a je kompatibilní se všemi prostředími (React, Angular, Node.js, React Native).Použití `graph-client` vám poskytne nejlepší zážitek z interakce s Graf.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Podívejme se, jak načíst data z podgrafu pomocí `graphql-client`.
+#### Krok 1
 
-Chcete-li začít, nezapomeňte si do projektu nainstalovat Graf Client CLI:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Krok 2
+
 Definujte svůj dotaz v souboru `.graphql` (nebo v souboru `.js` nebo `.ts`):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Poté vytvořte konfigurační soubor (nazvaný `.graphclientrc.yml`) a odkažte v něm například na koncové body GraphQL poskytnuté službou Graf:
+#### Krok 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Spuštěním následujícího příkazu Graf Client CLI se vygeneruje kód JavaScriptu připravený k použití:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Nakonec aktualizujte soubor `.ts` tak, aby používal vygenerované dokumenty GraphQL:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Důležité upozornění**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` je dokonale integrován s dalšími klienty GraphQL, jako je klient Apollo, URQL nebo React Query; [příklady najdete v oficiálním repozitáři](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Pokud se však rozhodnete pro jiného klienta, mějte na paměti, že **nebudete moci používat funkci Cross-chain podgraf Obsluha nebo Automatické pagination, což jsou základní funkce pro dotazování v Grafu**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Klient Apollo
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Klient Apollo](https://www.apollographql.com/docs/) je všudypřítomný klient GraphQL v ekosystému front-end.
+- Advanced error handling
+- Stránkování
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Klient Apollo je k dispozici pro React, Angular, Vue, Ember, iOS a Android, ačkoli je nejtěžším klientem, přináší mnoho funkcí pro budování pokročilého UI na základě GraphQL:
+### Fetch Data with Apollo Client
 
-- pokročilé zpracování chyb
-- stránkování
-- přednačítání dat
-- optimistické UI
-- místní státní správa
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Podívejme se, jak načíst data z podgrafu pomocí klienta Apollo ve web projektu.
+#### Krok 1
 
-Nejprve nainstalujte `@apollo/client` a `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Pak se můžete dotazovat API pomocí následujícího kódu:
+#### Krok 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Krok 3
+
 Chcete-li použít proměnné, můžete dotazu předat argument `variables`:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Další možností je [URQL](https://formidable.com/open-source/urql/), která je k dispozici v prostředích Node.js, React/Preact, Vue a Svelte a má pokročilejší funkce:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexibilní systém mezipaměti
 - Rozšiřitelný design (usnadňuje přidávání nových funkcí)
 - Lehký svazek (~5x lehčí než Apollo Client)
 - Podpora nahrávání souborů a režimu offline
 
-Podívejme se, jak načíst data z podgrafu pomocí jazyka URQL ve web projektu.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-Nejprve nainstalujte `urql` a `graphql`:
+#### Krok 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Pak se můžete dotazovat API pomocí následujícího kódu:
+#### Krok 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From ccc74b1098f54275075e61d0ddd4c76471ec6af9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:53 -0500
Subject: [PATCH 0844/1325] New translations querying-from-an-application.mdx
 (German)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/de/querying/querying-from-an-application.mdx b/website/pages/de/querying/querying-from-an-application.mdx
index 84c489360087..510accf3c883 100644
--- a/website/pages/de/querying/querying-from-an-application.mdx
+++ b/website/pages/de/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Schritt 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Schritt 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Schritt 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Schritt 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### Schritt 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Schritt 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Schritt 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### Schritt 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 6be18e32fc11ebc15f9bea803a9f05076e579c6f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:54 -0500
Subject: [PATCH 0845/1325] New translations querying-from-an-application.mdx
 (Italian)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/it/querying/querying-from-an-application.mdx b/website/pages/it/querying/querying-from-an-application.mdx
index 46116b99cfc8..2ff14e1cf885 100644
--- a/website/pages/it/querying/querying-from-an-application.mdx
+++ b/website/pages/it/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Eseguire una query da un'applicazione
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (endpoint di test)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Utilizzando il GraphQL endpoint, si possono usare varie librerie GraphQL Client per interrogare il subgraph e popolare l'applicazione con i dati indicizzati dal subgraph.
-
-Ecco un paio dei GraphQL client più diffusi nell'ecosistema e come utilizzarli:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## I GraphQL client
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph fornisce il proprio client GraphQL, `graph-client`, che supporta caratteristiche uniche come:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Gestione dei subgraph a cross-chain: effettuare query di più subgraph in un'unica query
 - [Tracciamento automatico dei blocchi](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Paginazione automatica](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Risultato completamente tipizzato
 
-Integrato anche con i client GraphQL più diffusi, come Apollo e URQL, e compatibile con tutti gli ambienti (React, Angular, Node.js, React Native), l'uso di `graph-client` vi darà la migliore esperienza di interazione con The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Vediamo come recuperare i dati da un subgraph con `graphql-client`.
+#### Step 1
 
-Per iniziare, assicuratevi di installare il Graph Client CLI nel vostro progetto:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Step 2
+
 Definire la query in un file `.graphql` (o in un file `.js` o `.ts`):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Quindi, creare un file di configurazione (chiamato `.graphclientrc.yml`) e puntare agli endpoint GraphQL forniti da The Graph, ad esempio:
+#### Step 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-L'esecuzione del seguente comando The Graph Client CLI genererà codice JavaScript digitato e pronto all'uso:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Infine, aggiornare il file `.ts` per utilizzare i documenti GraphQL digitati generati:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Avviso importante**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` è perfettamente integrato con altri client GraphQL come Apollo client, URQL o React Query; [troverete degli esempi nel repository ufficiale](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Tuttavia, se scegliete un altro client, tenete presente che **non sarete in grado di utilizzare la gestione dei Subgraph Cross-chain o la Paginazione Automatica, che sono caratteristiche fondamentali per effettuare query di The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Client Apollo
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Client Apollo](https://www.apollographql.com/docs/) è il client GraphQL onnipresente nell'ecosistema front-end.
+- Advanced error handling
+- Impaginazione
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Disponibile per React, Angular, Vue, Ember, iOS e Android, Apollo Client, sebbene sia il client più pesante, offre molte funzionalità per costruire UI avanzate in cima a GraphQL:
+### Fetch Data with Apollo Client
 
-- gestione avanzata degli errori
-- paginazione
-- prefetching dei dati
-- UI ottimistica
-- gestione statale locale
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Vediamo come recuperare i dati da un subgraph con il Apollo client in un progetto web.
+#### Step 1
 
-Per prima cosa, installare `@apollo/client` e `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Quindi è possibile effettuare query del'API con il seguente codice:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Step 3
+
 Per usare le variabili, si può passare un argomento `variables` alla query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Un'altra opzione è [URQL](https://formidable.com/open-source/urql/), disponibile negli ambienti Node.js, React/Preact, Vue e Svelte, con caratteristiche più avanzate:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Sistema di cache flessibile
 - Design estensibile (facilita l'aggiunta di nuove funzionalità)
 - Bundle leggero (~5 volte più leggero del Apollo Сlient)
 - Supporto per il caricamento di file e la modalità offline
 
-Vediamo come recuperare i dati da un subgraph con il URQL in un progetto web.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-Per prima cosa, installare `urql` e `graphql`:
+#### Step 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Quindi è possibile effettuare query del'API con il seguente codice:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 1dca9cda22c2aa56c487aab3bdb09041071d5aef Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:55 -0500
Subject: [PATCH 0846/1325] New translations querying-from-an-application.mdx
 (Japanese)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/ja/querying/querying-from-an-application.mdx b/website/pages/ja/querying/querying-from-an-application.mdx
index d0a76e24847e..2b8a5074d11e 100644
--- a/website/pages/ja/querying/querying-from-an-application.mdx
+++ b/website/pages/ja/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: アプリケーションからのクエリ
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (テスト用エンドポイント)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**グラフエクスプローラ**
+### グラフエクスプローラ
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-GraphQL エンドポイントを使用すると、さまざまな GraphQL クライアントライブラリを使用してサブグラフをクエリし、サブグラフによってインデックス化されたデータをアプリに入力することができます。
-
-ここでは、エコシステムで人気のある GraphQL クライアントをいくつか紹介し、その使い方を説明します:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graphは、独自のGraphQLクライアント`graph-client`を提供し、以下のような独自の機能をサポートしています：
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - クロスチェーンのサブグラフ処理：1回のクエリで複数のサブグラフからクエリを実行可能
 - [自動ブロック追跡](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [自動ページング](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - 完全なタイプ付け結果
 
-さらに、ApolloやURQLなどの人気のあるGraphQLクライアントと統合され、すべての環境（React、Angular、Node.js、React Native）と互換性があり、`graph-client`を使用することで、The Graphとの対話の最良のエクスペリエンスが得られます。
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
 
-以下は、`graphql-client`を使用してサブグラフからデータを取得する方法を見てみましょう。
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-始める前に、プロジェクトにThe Graph Client CLIをインストールしてください。
+#### ステップ1
+
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### ステップ2
+
 `.graphql` ファイルでクエリを定義します (または、`.js` または `.ts` ファイルにインラインで)。
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-次に、設定ファイル（`.graphclientrc.yml`と呼ばれる）を作成し、The Graphが提供するGraphQLエンドポイントを指定します。例えば：
+#### ステップ 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-以下のThe Graph Client CLIコマンドを実行すると、型付けされたJavaScriptコードが生成され、すぐに使用できる状態になります。
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-最後に、生成された型付きのGraphQLドキュメントを使用するために、`.ts`ファイルを更新してください。
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ 重要なお知らせ**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client`は、Apolloクライアント、URQL、React Queryなどの他のGraphQLクライアントと完全に統合されています。公式リポジトリには[例があります](https://github.com/graphprotocol/graph-client/tree/main/examples)。
+### Apollo Client
 
-ただし、別のクライアントを選択する場合は、**クロスチェーンサブグラフ処理や自動ページネーションといった、The Graphのクエリングの中核的な機能を利用できないことに注意してください。**
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo クライアント
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo Client](https://www.apollographql.com/docs/)は、フロントエンドエコシステムで広く使われているGraphQLクライアントです。
+- Advanced error handling
+- ページネーション
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-React、Angular、Vue、Ember、iOS、およびAndroid向けに利用可能なApollo Clientは、最も重いクライアントですが、GraphQLを基にした高度なUIを構築するための多くの機能を提供します。
+### Fetch Data with Apollo Client
 
-- 高度なエラー処理
-- ページネーション
-- データのプリフェッチ
-- 楽観的な UI
-- ローカル状態管理
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Apollo Clientを使用してウェブプロジェクトでサブグラフからデータを取得する方法を見てみましょう。
+#### ステップ1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-その後、以下のコードで API をクエリできます:
+#### ステップ2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### ステップ 3
+
 変数を使用するには、クエリに`variables`引数を渡すことができます：
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-もう一つの選択肢は[URQL](https://formidable.com/open-source/urql/)で、Node.js、React/Preact、Vue、およびSvelteの環境で利用でき、より高度な機能が備わっています。
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - 柔軟なキャッシュ システム
 - Extensible design（新しい機能の追加を容易にする）
 - Lightweight bundle（Apollo Clientの約5倍の軽さ）
 - ファイルアップロードとオフラインモードに対応
 
-URQLを使用してウェブプロジェクトでサブグラフからデータを取得する方法を見てみましょう。
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-まず、`urql`と`graphql`をインストールします:
+#### ステップ1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-その後、以下のコードで API をクエリできます:
+#### ステップ2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From f5946d100db5499d8ba00389fd2aaaeb232dce5c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:56 -0500
Subject: [PATCH 0847/1325] New translations querying-from-an-application.mdx
 (Korean)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/ko/querying/querying-from-an-application.mdx b/website/pages/ko/querying/querying-from-an-application.mdx
index 84c489360087..a9f8162ebcf0 100644
--- a/website/pages/ko/querying/querying-from-an-application.mdx
+++ b/website/pages/ko/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Step 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Step 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Step 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Step 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Step 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Step 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 910ea75b9fa9abae2d9dd89d919242468fdbf0ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:57 -0500
Subject: [PATCH 0848/1325] New translations querying-from-an-application.mdx
 (Dutch)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/nl/querying/querying-from-an-application.mdx b/website/pages/nl/querying/querying-from-an-application.mdx
index b58a928084c3..45c84601b934 100644
--- a/website/pages/nl/querying/querying-from-an-application.mdx
+++ b/website/pages/nl/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Verkenner**
+### Graph Verkenner
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Stap 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Stap 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Stap 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Stap 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### Stap 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Stap 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Stap 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### Stap 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 9075e37f2f0b541f1df93a6782316dab7cc26c6c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:58 -0500
Subject: [PATCH 0849/1325] New translations querying-from-an-application.mdx
 (Polish)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/pl/querying/querying-from-an-application.mdx b/website/pages/pl/querying/querying-from-an-application.mdx
index 84c489360087..2198e511b69e 100644
--- a/website/pages/pl/querying/querying-from-an-application.mdx
+++ b/website/pages/pl/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Krok 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Krok 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Krok 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Krok 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### Krok 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Krok 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Krok 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### Krok 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 571f79028d53229d706c5dbae96bf7053af72f08 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:47:59 -0500
Subject: [PATCH 0850/1325] New translations querying-from-an-application.mdx
 (Portuguese)

---
 .../querying/querying-from-an-application.mdx | 100 +++++++++++-------
 1 file changed, 61 insertions(+), 39 deletions(-)

diff --git a/website/pages/pt/querying/querying-from-an-application.mdx b/website/pages/pt/querying/querying-from-an-application.mdx
index de13777f23d5..477899816aab 100644
--- a/website/pages/pt/querying/querying-from-an-application.mdx
+++ b/website/pages/pt/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Como Fazer Queries de um Aplicativo
 ---
 
-Quando um subgraph for lançado ao Subgraph Studio ou ao Graph Explorer, receberá o endpoint para a sua API GraphQL, que deve parecer com isto:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (endpoint de teste)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-O endpoint GraphQL permite usar várias bibliotecas do Cliente GraphQL, para consultar o subgraph e popular o seu aplicativo com os dados indexados pelo subgraph.
-
-Aqui estão alguns dos clientes GraphQL mais populares no ecossistema, e como usá-los:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## Clientes GraphQL
+## Using Popular GraphQL Clients
 
-### Cliente Graph
+### Graph Client
 
-O The Graph fornece um cliente GraphQL próprio, `graph-client`, que apoia recursos únicos como:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Gestão de Subgraph Cross-chain: Queries de múltiplos subgraphs numa única consulta
 - [Rastreamento Automático de Blocos](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Paginação Automática](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Resultado totalmente digitado
 
-Também é integrado com clientes GraphQL populares como Apollo e URQL, e compatível com todos os ambientes, (React, Angular, Node.js, React Native); usar o `graph-client` proverá a melhor experiência para interagir com o The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Vamos ver como retirar dados de um subgraph com o `graphql-client`.
+#### Passo 1
 
-Para começar, instale a Graph Client CLI no seu projeto:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Passo 2
+
 Defina o seu query num arquivo `.graphql` (ou alinhado no seu arquivo `.js` ou `.ts`):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Depois, crie um arquivo de configuração (chamado `.graphclientrc.yml`) e aponte aos seus endpoints GraphQL oferecidos pelo The Graph, por exemplo:
+#### Passo 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,19 +98,23 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Executar o seguinte comando na Graph Client CLI gerará códigos JavaScript digitados e prontos para uso:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finalmente, atualize o seu arquivo `.ts` para usar os documentos digitados em GraphQL já gerados:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
 // ...
 // nós importamos tipos e documentos em graphql do código gerado
-;`..graphclient/`
+(`..graphclient/`)
 import { ExampleQueryDocument, ExampleQueryQuery, execute } from '../.graphclient'
 
 function App() {
@@ -135,33 +147,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Aviso importante**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-O `graph-client` é perfeitamente integrado com outros clientes GraphQL como Apollo, URQL, ou React Query; [veja exemplos no repositório oficial](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Porém, se escolher usar outro cliente, lembre que **não haverá como usar a Gestão de Subgraph Cross-Chain ou a Paginação Automática, estes recursos importantes para queries no The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-O [cliente Apollo](https://www.apollographql.com/docs/) é o cliente GraphQL mais ubíquo no ecossistema do front-end.
+- Advanced error handling
+- Paginação
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Disponível para React, Angular, Vue, Ember, iOS e Android, o cliente Apollo, apesar de ser o mais pesado, traz muitos recursos para construir interfaces de utilizador avançadas em cima do GraphQL:
+### Fetch Data with Apollo Client
 
-- tratamento de erros avançado
-- paginação
-- prefetching de dados
-- UI otimista
-- gestão de estado local
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Vamos ver como retirar dados de um subgraph com o cliente Apollo num projeto de web.
+#### Passo 1
 
-Primeiro, instale o `@apollo/client` e o `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Depois, faça um query na API com o seguinte código:
+#### Passo 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -194,6 +208,8 @@ client
   })
 ```
 
+#### Passo 3
+
 Para usar variáveis, dá para passar um argumento `variables` ao query:
 
 ```javascript
@@ -225,24 +241,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Há também o [URQL](https://formidable.com/open-source/urql/), que está disponível nos ambientes Node.js, React/Preact, Vue e Svelte, com ferramentas mais avançadas:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Sistema de cache flexível
 - Design extensível (mais fácil adicionar novas capacidades em cima dele)
 - Pacote leve (cerca de 5x mais leve que o Apollo)
 - Apoio para envios de arquivo e modo offline
 
-Vamos ver como retirar dados de um subgraph com o URQL num projeto de web.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-Primeiro, instale o `urql` e o `graphql`:
+#### Passo 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Depois, faça um query na API com o seguinte código:
+#### Passo 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From e4fe516d57e19a29914e7dc81900b844d08accfc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:00 -0500
Subject: [PATCH 0851/1325] New translations querying-from-an-application.mdx
 (Russian)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/ru/querying/querying-from-an-application.mdx b/website/pages/ru/querying/querying-from-an-application.mdx
index 84c489360087..a0f1fde989db 100644
--- a/website/pages/ru/querying/querying-from-an-application.mdx
+++ b/website/pages/ru/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Шаг 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Шаг 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Шаг 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Пагинация
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Шаг 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### Шаг 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Шаг 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Шаг 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### Шаг 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 940ece7eb4dec2ceccf7bcd51d637c3a96dd1113 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:02 -0500
Subject: [PATCH 0852/1325] New translations querying-from-an-application.mdx
 (Swedish)

---
 .../querying/querying-from-an-application.mdx | 128 ++++++++++--------
 1 file changed, 75 insertions(+), 53 deletions(-)

diff --git a/website/pages/sv/querying/querying-from-an-application.mdx b/website/pages/sv/querying/querying-from-an-application.mdx
index 6e653e81b539..cf26ba6cac68 100644
--- a/website/pages/sv/querying/querying-from-an-application.mdx
+++ b/website/pages/sv/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Att göra förfrågningar från en Applikation
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testslutpunkt)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraf Studion
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graf Utforskaren**
+### Graf Utforskaren
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Genom att använda GraphQL-slutpunkten kan du använda olika GraphQL-klientbibliotek för att göra förfrågningar till undergrafen och fylla din app med de data som indexeras av undergrafen.
-
-Här är ett par av de populärare GraphQL-klienterna i ekosystemet och hur du använder dem:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL-klienter
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph tillhandahåller sin egen GraphQL-klient, graph-client, som stödjer unika funktioner som:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Hantering av undergrafer över blockkedjor: Förfrågan från flera undergrafer i en enda förfrågan
 - [Automatisk Blockspårning](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatisk Paginering](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fullständigt typad resultat
 
-Även integrerad med populära GraphQL-clients som Apollo och URQL och kompatibel med alla miljöer (React, Angular, Node.js, React Native), kommer användning av `graph-client` att ge dig den bästa upplevelsen för interaktion med The Graf.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Låt oss titta på hur du hämtar data från en undergraf med `graphql-client`.
+#### Steg 1
 
-För att komma igång, se till att installera The Graph Client CLI i ditt projekt:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Steg 2
+
 Definiera din förfrågan i en `.graphql`-fil (eller inline i din `.js` eller `.ts`-fil):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Därefter, skapa en konfigurationsfil (kallad `.graphclientrc.yml`) och peka till dina GraphQL-slutpunkter som tillhandahålls av The Graph, till exempel:
+#### Steg 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Kör följande The Graph Client CLI-kommando för att generera typade och klara att använda JavaScript-kod:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Slutligen, uppdatera din `.ts`-fil för att använda de genererade typade GraphQL-dokumenten:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,38 +146,40 @@ function App() {
 export default App
 ```
 
-**⚠️ Viktig uppmärksamhet**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` är perfekt integrerad med andra GraphQL-klienter som Apollo-klient, URQL eller React Query; du kommer att [finna exempel i det officiella arkivet](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Men om du väljer att gå med en annan klient, kom ihåg att **du inte kommer att kunna använda Cross-chain Subgraph Handling eller Automatic Pagination, som är kärnfunktionerna för att fråga The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) är den vanliga GraphQL-klienten i front-end-ekosystemet.
+- Advanced error handling
+- Paginering
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Tillgänglig för React, Angular, Vue, Ember, iOS och Android, bringar Apollo Client, även om den tyngsta klienten, många funktioner för att bygga avancerad UI ovanpå GraphQL:
+### Fetch Data with Apollo Client
 
-- avancerad felhantering
-- paginering
-- datavisning i förväg
-- optimistiskt UI
-- lokal statshantering
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Låt oss titta på hur du hämtar data från en undergraf med Apollo-klienten i ett webbprojekt.
+#### Steg 1
 
-Först installerar du `@apollo/client` och `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Sedan kan du göra en förfrågan till API:et med följande kod:
+#### Steg 2
+
+Query the API with the following code:
 
 ```javascript
-import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
+import { ApolloClient, InMemoryCache, gql } from "@apollo/client";
 
-const APIURL = 'https://api.studio.thegraph.com/query//<SUBGRAPH_NAME>/'
+const APIURL = "https://api.studio.thegraph.com/query//<SUBGRAPH_NAME>/";
 
 const tokensQuery = `
   query {
@@ -176,23 +190,25 @@ const tokensQuery = `
       metadataURI
     }
   }
-`
+`;
 
 const client = new ApolloClient({
   uri: APIURL,
   cache: new InMemoryCache(),
-})
+});
 
 client
   .query({
     query: gql(tokensQuery),
   })
-  .then((data) => console.log('Subgraph data: ', data))
+  .then((data) => console.log("Subgraph data: ", data))
   .catch((err) => {
-    console.log('Error fetching data: ', err)
+    console.log("Error fetching data: ", err);
   })
 ```
 
+#### Steg 3
+
 För att använda variabler kan du skicka in ett `variables` argument till förfrågan:
 
 ```javascript
@@ -207,46 +223,52 @@ const tokensQuery = `
       metadataURI
     }
   }
-`
+`;
 
 client
   .query({
     query: gql(tokensQuery),
     variables: {
       first: 10,
-      orderBy: 'createdAtTimestamp',
-      orderDirection: 'desc',
+      orderBy: "createdAtTimestamp",
+      orderDirection: "desc",
     },
   })
-  .then((data) => console.log('Subgraph data: ', data))
+  .then((data) => console.log("Subgraph data: ", data))
   .catch((err) => {
-    console.log('Error fetching data: ', err)
+    console.log("Error fetching data: ", err);
   })
 ```
 
-### URQL
+### URQL Overview
 
-Ett annat alternativ är [URQL](https://formidable.com/open-source/urql/) som är tillgänglig inom Node.js, React/Preact, Vue och Svelte-miljöer, med fler avancerade funktioner:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexibelt cachelagersystem
 - Utbyggbar design (förenklar tillägg av nya funktioner på toppen)
 - Lättviktsbundle (~5 gånger lättare än Apollo-klienten)
 - Stöd för filöverföringar och offline-läge
 
-Låt oss titta på hur du hämtar data från en undergraf med URQL i ett webbprojekt.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-Först installerar du `urql` och `graphql`:
+#### Steg 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Sedan kan du göra en förfrågan till API:et med följande kod:
+#### Steg 2
+
+Query the API with the following code:
 
 ```javascript
-import { createClient } from 'urql'
+import { createClient } from "urql";
 
-const APIURL = 'https://api.thegraph.com/subgraphs/name/username/subgraphname'
+const APIURL = "https://api.thegraph.com/subgraphs/name/username/subgraphname";
 
 const tokensQuery = `
   query {
@@ -257,11 +279,11 @@ const tokensQuery = `
       metadataURI
     }
   }
-`
+`;
 
 const client = createClient({
   url: APIURL,
-})
+});
 
 const data = await client.query(tokensQuery).toPromise()
 ```

From aa95fdc7338407ec68d2e11f9856c77472ae9548 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:03 -0500
Subject: [PATCH 0853/1325] New translations querying-from-an-application.mdx
 (Turkish)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/tr/querying/querying-from-an-application.mdx b/website/pages/tr/querying/querying-from-an-application.mdx
index 5b0c2bb4de44..1de846d6c066 100644
--- a/website/pages/tr/querying/querying-from-an-application.mdx
+++ b/website/pages/tr/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Stüdyosu
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Gezgini**
+### Graph Gezgini
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Using the GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with the data indexed by the subgraph.
-
-Here are a couple of the more popular GraphQL clients in the ecosystem and how to use them:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Ayrıca Apollo ve URQL gibi popüler GraphQL istemcileriyle entegre edilmiş ve React, Angular, Node.js, React Native gibi tüm ortamlarla uyumlu olan `graph-client`'ı kullanmak, Graph ile etkileşimde bulunmanız için en iyi deneyimi sunacaktır.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Şimdi `graphql-client` ile bir subgraph'dan nasıl veri alınacağına bakalım.
+#### 1. Adım
 
-Başlamak için, projenize The Graph Client CLI'yi yüklediğinizden emin olun:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### 2. Adım
+
 Sorgunuzu bir `.graphql` dosyasında (veya `.js` yada `.ts` dosyanızda satır içi olarak) tanımlayın:
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Ardından, bir yapılandırma dosyası oluşturun (`.graphclientrc.yml` adında) ve Graph tarafından sağlanan GraphQL uç noktalarına işaret edin, örneğin:
+#### 3. Adım
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Aşağıdaki The Graph Client CLI komutunu çalıştırmak, yazılmış ve kullanıma hazır JavaScript kodunu oluşturacaktır:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Son olarak, oluşturulan GraphQL belgelerini kullanmak için `.ts` dosyanızı güncelleyin:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Önemli uyarı**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client`, Apollo istemcisi, URQL veya React Query gibi diğer GraphQL istemcileriyle mükemmel bir şekilde entegre edilmiştir; [örnekleri resmi Github deposunda bulacaksınız](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Ancak, başka bir istemci kullanmayı tercih ederseniz, **Graph'ı sorgulamak için temel özellikler olan Zincirler Arası Subgraph İşleme veya Otomatik Sayfalandırma özelliklerini kullanamayacağınızı** unutmayın.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo istemcisi](https://www.apollographql.com/docs/), önyüz ekosisteminde her yerde bulunan GraphQL istemcisidir.
+- Advanced error handling
+- Sayfalandırma
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-React, Angular, Vue, Ember, iOS ve Android için kullanılabilir olan Apollo İstemcisi, en ağır istemci olmasına rağmen, GraphQL üzerine gelişmiş arayüzler geliştirmek için birçok özellik sunar:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Bir web projesinde Apollo istemcisi ile bir subgraph'tan nasıl veri çekileceğine bakalım.
+#### 1. Adım
 
-İlk olarak, `@apollo/client` ve `graphql`'i yükleyin:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### 2. Adım
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### 3. Adım
+
 Değişkenleri kullanmak için sorguya bir `variables` bağımsız değişkeni aktarabilirsiniz:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Diğer bir seçenek ise Node.js, React/Preact, Vue ve Svelte ortamlarında kullanılabilen ve daha gelişmiş özelliklere sahip [URQL](https://formidable.com/open-source/urql/)'dir:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Bir web projesinde URQL ile bir subgraph'tan nasıl veri çekileceğne bakalım.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-İlk olarak, `urql` ve `graphql`'i yükleyin:
+#### 1. Adım
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### 2. Adım
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From b1bb52adfe28fb686a3ed0fcc872372f3aaec001 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:04 -0500
Subject: [PATCH 0854/1325] New translations querying-from-an-application.mdx
 (Ukrainian)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/uk/querying/querying-from-an-application.mdx b/website/pages/uk/querying/querying-from-an-application.mdx
index 790a9aeb183d..08650c70ea92 100644
--- a/website/pages/uk/querying/querying-from-an-application.mdx
+++ b/website/pages/uk/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Отримання запиту з додатка
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (тестування кінцевої точки)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Субграф Студія
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Використовуючи кінцеву точку GraphQL, ви можете використовувати різні клієнтські бібліотеки GraphQL для запитів до підграфа і заповнення вашого додатка даними, проіндексованими підграфом.
-
-Ось декілька найпопулярніших GraphQL-клієнтів в екосистемі та способи їх використання:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-Graph надає власний GraphQL client, `graph-client`, який підтримує унікальні можливості, такі як:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Робота з кросс-чейн підграфами: Отримання інформації з декількох підграфів за один запит
 - [Автоматичне відстежування блоків](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Автоматична розбивка на сторінки](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Повністю введений результат
 
-Окрім того, інтегрований з популярними GraphQL-клієнтами, такими як Apollo та URQL, і сумісний з усіма середовищами (React, Angular, Node.js, React Native), використання `graph-client` дасть вам найкращий досвід взаємодії з The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Розгляньмо, як отримати дані з сабграфа за допомогою `graphql-client`.
+#### Step 1
 
-Щоб почати, переконайтеся, що ви встановили The Graph Client CLI у вашому проєкті:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Step 2
+
 Опишіть ваш запит у файлі `.graphql` (або вставленому у ваш файл `.js` або `.ts`):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Потім створіть файл конфігурації (з назвою `.graphclientrc.yml`) і вкажіть у ньому кінцеві точки GraphQL, запропоновані The Graph, до прикладу:
+#### Step 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Виконання наступної команди The Graph Client CLI згенерує введений і готовий до використання JavaScript код:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Наостанок, оновіть ваш файл `.ts`, щоб використовувати згенеровані типізовані документи GraphQL:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Важливе зауваження**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` чудово інтегрований з іншими GraphQL-клієнтами, такими як Apollo client, URQL або React Query; ви можете знайти [ приклади в офіційному репозиторії](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-Однак, якщо ви вирішите використовувати інший клієнт, майте на увазі, що **ви не зможете використовувати крос-чейн обробку підграфів або Automatic Pagination на сторінки, які є основними функціями для запитів до The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) - це розповсюджений клієнт GraphQL у фронт-енд екосистемі.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Доступний для React, Angular, Vue, Ember, iOS та Android, Apollo Client, хоча і є найважчим клієнтом, надає багато можливостей для створення розширеного інтерфейсу користувача поверх GraphQL:
+### Fetch Data with Apollo Client
 
-- покращена система обробки помилок
-- пагінація
-- попередня вибірка даних
-- оптимістичний інтерфейс користувача
-- місцеве публічне керування
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Розгляньмо, як отримати дані з підграфа за допомогою клієнта Apollo у вебпроєкті.
+#### Step 1
 
-Спочатку, установіть `@apollo/client` і `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Після цього ви можете зробити запит до API за допомогою наступного коду:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Step 3
+
 Щоб використовувати змінні, ви можете вказати в запиті аргумент `variables`:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Іншим варіантом є [URQL](https://formidable.com/open-source/urql/), який доступний у середовищах Node.js, React/Preact, Vue та Svelte, з більш розширеними можливостями:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Гнучка кеш-система
 - Динамічний дизайн (полегшує додавання нових функцій)
 - Полегшений варіант (приблизно в 5 разів легший за Apollo Client)
 - Підтримка завантаження файлів та офлайн-режиму
 
-Розгляньмо, як отримати дані з підграфа за допомогою URQL у вебпроєкті.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-Для початку, установіть `urql` та `graphql`:
+#### Step 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Після цього ви можете зробити запит до API за допомогою наступного коду:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 5c1a27fa00db41226fdb8dfbe7a1eb41f3fefdb4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:05 -0500
Subject: [PATCH 0855/1325] New translations querying-from-an-application.mdx
 (Chinese Simplified)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/zh/querying/querying-from-an-application.mdx b/website/pages/zh/querying/querying-from-an-application.mdx
index 1ae178eb6137..f76433cad995 100644
--- a/website/pages/zh/querying/querying-from-an-application.mdx
+++ b/website/pages/zh/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: 从应用程序中进行查询
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**子图工作室（测试端点）**
+## Getting GraphQL Endpoint
 
-```sh
-查询 (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### 子图工作室
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph浏览器**
+### Graph浏览器
 
-```sh
-查询 (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-使用 GraphQL 端点，你可以使用各种 GraphQL 客户端库来查询子图，并用子图索引的数据来填充你的应用程序。
-
-下面是生态系统中几个比较流行的 GraphQL 客户端以及如何使用它们。
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL客户端
+## Using Popular GraphQL Clients
 
-### Graph 客户端
+### Graph Client
 
-Graph提供了自己的GraphQL客户端，`graph-client`支持以下独特功能：
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - 跨链子图处理: 在一个查询中从多个子图进行查询
 - [自动区块追踪](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [自动分页](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - 完全类型化的结果
 
-还与流行的GraphQL客户端（如Apollo和URQL）集成，并与所有环境（React、Angular、Node.js、React Native）兼容，使用`graph-client`将为您提供与Graph交互的最佳体验。
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
 
-让我们看看如何使用 `graphql-client` 从子图获取数据。
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-首先，请确保在项目中安装 Graph Client CLI:
+#### 步骤1
+
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### 步骤2
+
 在`.graphql` 文件中定义查询(或在`.js` or `.ts`文件中内联):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-然后，创建一个配置文件(名为`. grapclientrc.yml`)并指向Graph 提供的 GraphQL 端点，例如:
+#### 步骤3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-运行以下 Graph Client CLI 命令将生成类型化的并可以投入使用 的JavaScript 代码:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-最后，更新`.ts` 文件以使用生成的类型化 GraphQL 文档:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️重要告示**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` 与其他 GraphQL 客户端(如 Apollo client、 URQL 或 React Query)完美地集成; 您可以在[正式存储库中找到示例](https://github.com/graphprotocol/graph-client/tree/main/examples)。
+### Apollo Client
 
-但是，如果您选择使用另一个客户端，请记住**您将无法使用跨链子图处理或自动分页，这是查询Graph 的核心功能**。
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo 客户端
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo 客户端](https://www.apollographql.com/docs/)是前端生态系统中无处不在的 GraphQL 客户端。
+- Advanced error handling
+- 分页
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Apollo Client可用于React、Angular、Vue、Ember、iOS和Android，虽然是重量级的客户端，但它在GraphQL之上提供了许多构建高级UI的功能：
+### Fetch Data with Apollo Client
 
-- 高级错误处理
-- 分页
-- 数据预取
-- 优化用户界面
-- 本地状态管理
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-让我们看看如何在一个web项目中用 Apollo 客户端从子图中获取数据。
+#### 步骤1
 
-首先，安装`@apollo/client` 和`graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-然后你可以用以下代码查询 API：
+#### 步骤2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### 步骤3
+
 要使用变量，你可以在查询中传递一个`变量参数` 。
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-另一个选项是 [URQL](https://formidable.com/open-source/urql/)，它可以在 Node.js、 React/Preact、 Vue 和 Svelte 环境中使用，具有更高级的特性:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - 灵活的缓存系统
 - 可扩展设计(使在它上面添加新功能变得容易)
 - 轻量级捆绑包(比 Apollo Client 小约5倍)
 - 支持文件上传和离线模式
 
-让我们看看如何在一个网络项目中用 URQL 从子图中获取数据。
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-首先，安装`urql`和 `graphql`:
+#### 步骤1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-然后你可以用以下代码查询 API：
+#### 步骤2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 7dd79b6417579befdb65a7590963751bdfcb9f29 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:06 -0500
Subject: [PATCH 0856/1325] New translations querying-from-an-application.mdx
 (Urdu (Pakistan))

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/ur/querying/querying-from-an-application.mdx b/website/pages/ur/querying/querying-from-an-application.mdx
index 833f78775679..be463518efcb 100644
--- a/website/pages/ur/querying/querying-from-an-application.mdx
+++ b/website/pages/ur/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: ایپلیکیشن سے کیوری
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**سب گراف اسٹوڈیو (ٹیسٹنگ اینڈ پوائنٹ)**
+## Getting GraphQL Endpoint
 
-```sh
-کیوریز (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### سب گراف سٹوڈیو
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**گراف ایکسپلورر**
+### گراف ایکسپلورر
 
-```sh
-کیوریز (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-GraphQL اینڈ پوائنٹ کا استعمال کرتے ہوئے، آپ سب گراف سے کیوری کرنے کے لیے مختلف GraphQL کلائنٹ لائبریریوں کا استعمال کر سکتے ہیں اور اپنی ایپ کو سب گراف کے ذریعے ترتیب کردہ ڈیٹا کے ساتھ آباد کر سکتے ہیں.
-
-یہاں ایکو سسٹم میں کچھ زیادہ مقبول GraphQL کلائنٹس ہیں اور ان کا استعمال کیسے کریں:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL کلائنٹ
+## Using Popular GraphQL Clients
 
-### گراف کلائنٹ
+### Graph Client
 
-گراف اپنا GraphQL کلائنٹ فراہم کر رہا ہے، `graph-client` جو منفرد خصوصیات کو سپورٹ کرتا ہے جیسے:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - کراس چین سب گراف ہینڈلنگ: ایک کیوری میں متعدد سب گرافس سے کیوری کرنا
 - [خودکار بلاک ٹریکنگ](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [خودکار صفحہ بندی](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - مکمل طور پر ٹائپ شدہ نتیجہ
 
-نیز مقبول GraphQL کلائنٹس جیسے کہ اپولو اور URQL کے ساتھ مربوط اور تمام ماحول کے ساتھ مطابقت رکھتا ہے (ری ایکٹ، اینگولر، نوڈ جے ایس، ری ایکٹ نیٹیو)، `graph-client` کا استعمال آپ کو گراف کے ساتھ بات چیت کرنے کا بہترین تجربہ فراہم کرے گا.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
 
-آئیے دیکھتے ہیں کہ `graphql-client` کے ساتھ سب گراف سے ڈیٹا کیسے حاصل کیا جائے.
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-شروع کرنے کے لیے، اپنے پروجیکٹ میں گراف کلائنٹ CLI کو میں انسٹال کرنا یقینی بنائیں:
+#### پہلا قدم
+
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### دوسرا قدم
+
 اپنے کیوری کی وضاحت `.graphql` فائل میں کریں (یا آپ کی `.js` یا `.ts` فائل میں ان لائن):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-پھر، ایک کنفیگریشن فائل بنائیں (جسے `.graphclientrc.yml` کہا جاتا ہے) اور گراف کی طرف سے فراہم کردہ اپنے GraphQL اینڈ پوائنٹس کی طرف اشارہ کریں، مثال کے طور پر:
+#### تیسرا قدم
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-درج ذیل گراف کلائنٹ CLI کمانڈ کو چلانے سے ٹائپ شدہ اور جاوا اسکرپٹ کوڈ استعمال کرنے کے لیے تیار ہو جائے گا:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 گراف کلائنٹ کی تعمیر
 ```
 
-آخر میں، اپنی `.ts` فائل کو اپ ڈیٹ کریں تاکہ تیار کردہ ٹائپ شدہ GraphQL دستاویزات استعمال کریں:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ اہم اطلاع**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` بالکل دوسرے GraphQL کلائنٹس جیسے اپولو کلائنٹ، URQL، یا React کیوری کے ساتھ مربوط ہے۔ آپ کو [آفیشل ریپوزٹری میں مثالیں ملیں گی](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-تاہم، اگر آپ کسی دوسرے کلائنٹ کے ساتھ جانے کا انتخاب کرتے ہیں، ذہن میں رکھیں کہ **آپ کراس چین سب گراف ہینڈلنگ یا خودکار صفحہ بندی استعمال کرنے کے قابل نہیں ہوں گے، جو گراف سے کیوری کرنے کی بنیادی خصوصیات ہیں**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### اپولو کلائنٹ
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[اپولو کلائنٹ](https://www.apollographql.com/docs/) فرنٹ اینڈ ایکو سسٹم پر ہر جگہ موجود GraphQL کلائنٹ ہے.
+- Advanced error handling
+- صفحہ بندی
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-React، Angular، Vue، Ember، iOS، اور Android کے لیے دستیاب، اپولو کلائنٹ، اگرچہ سب سے بھاری کلائنٹ ہے، GraphQL کے اوپری حصے میں جدید UI بنانے کے لیے بہت سی خصوصیات لاتا ہے:
+### Fetch Data with Apollo Client
 
-- ایڈوانس ایرر ہینڈلنگ
-- صفحہ بندی
-- ڈیٹا پری فیچنگ
-- پر امید UI
-- مقامی ریاستی انتظام
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-آئیے دیکھتے ہیں کہ ویب پروجیکٹ میں اپولو کلائنٹ کے ساتھ سب گراف سے ڈیٹا کیسے حاصل کیا جائے.
+#### پہلا قدم
 
-پہلے، `@apollo/client` اور `graphql` انسٹال کریں:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-پھر آپ درج ذیل کوڈ کے ساتھ API سے کیوری کرسکتے ہیں:
+#### دوسرا قدم
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### تیسرا قدم
+
 متغیرات کو استعمال کرنے کے لیے، آپ پر کیوری `variables` دلیل دے سکتے ہیں:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-ایک اور آپشن [URQL](https://formidable.com/open-source/urql/) ہے جو Node.js، React/Preact، Vue، اور Svelte ماحول میں دستیاب ہے، جس میں زیادہ جدید ہے۔ خصوصیات:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - لچکدار کیش سسٹم
 - قابل توسیع ڈیزائن (اس کے اوپر نئی صلاحیتوں کو شامل کرنے میں آسانی)
 - ہلکا پھلکا بنڈل (اپولو کلائنٹ سے ~5x ہلکا)
 - فائل اپ لوڈز اور آف لائن موڈ کے لیے سپورٹ
 
-آئیے دیکھتے ہیں کہ ویب پروجیکٹ میں URQL کے ساتھ سب گراف سے ڈیٹا کیسے حاصل کیا جائے.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-پہلے، `urql` اور `graphql` انسٹال کریں:
+#### پہلا قدم
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-پھر آپ درج ذیل کوڈ کے ساتھ API سے کیوری کرسکتے ہیں:
+#### دوسرا قدم
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 58f17e1bd6f5b2adefd5078cde9f30105d020117 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:07 -0500
Subject: [PATCH 0857/1325] New translations querying-from-an-application.mdx
 (Vietnamese)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/vi/querying/querying-from-an-application.mdx b/website/pages/vi/querying/querying-from-an-application.mdx
index b4d1c351093b..91c7faf04ea2 100644
--- a/website/pages/vi/querying/querying-from-an-application.mdx
+++ b/website/pages/vi/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Truy vấn từ một ứng dụng
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (điểm cuối thử nghiệm)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Trình khám phá Graph**
+### Trình khám phá Graph
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-Sử dụng điểm cuối GraphQL, bạn có thể sử dụng các thư viện GraphQL Client khác nhau để truy vấn subgraph và điền vào ứng dụng của bạn với dữ liệu được lập chỉ mục bởi subgraph.
-
-Dưới đây là một số ứng dụng khách GraphQL phổ biến hơn trong hệ sinh thái và cách sử dụng chúng:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### Step 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### Step 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### Step 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### Step 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Sau đó, bạn có thể truy vấn API bằng mã sau:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### Step 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### Step 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Sau đó, bạn có thể truy vấn API bằng mã sau:
+#### Step 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 4377e02130dc697a1e75c5fe14fe5dac5c86f052 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:08 -0500
Subject: [PATCH 0858/1325] New translations querying-from-an-application.mdx
 (Marathi)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/mr/querying/querying-from-an-application.mdx b/website/pages/mr/querying/querying-from-an-application.mdx
index 2a9300bc31c2..cd8f118b6db8 100644
--- a/website/pages/mr/querying/querying-from-an-application.mdx
+++ b/website/pages/mr/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: Querying from an Application
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**Subgraph Studio (testing endpoint)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-GraphQL एंडपॉइंट वापरून, तुम्ही सबग्राफची क्वेरी करण्यासाठी आणि सबग्राफद्वारे अनुक्रमित केलेल्या डेटासह तुमचा अॅप पॉप्युलेट करण्यासाठी विविध GraphQL क्लायंट लायब्ररी वापरू शकता.
-
-इकोसिस्टममधील आणखी काही लोकप्रिय ग्राफक्यूएल क्लायंट आणि ते कसे वापरायचे ते येथे आहेत:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL clients
+## Using Popular GraphQL Clients
 
-### Graph client
+### Graph Client
 
-The Graph is providing it own GraphQL client, `graph-client` that supports unique features such as:
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
 
 - Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
 - [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - Fully typed result
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### 1 ली पायरी
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### पायरी 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### पायरी 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### Apollo client
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### 1 ली पायरी
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-Then you can query the API with the following code:
+#### पायरी 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### पायरी 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - Extensible design (easing adding new capabilities on top of it)
 - Lightweight bundle (~5x lighter than Apollo Client)
 - Support for file uploads and offline mode
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### 1 ली पायरी
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-Then you can query the API with the following code:
+#### पायरी 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From 2cd4dfbb98cb5f16d0abb6c0ac57451a2f2ef24f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:09 -0500
Subject: [PATCH 0859/1325] New translations querying-from-an-application.mdx
 (Hindi)

---
 .../querying/querying-from-an-application.mdx | 98 ++++++++++++-------
 1 file changed, 60 insertions(+), 38 deletions(-)

diff --git a/website/pages/hi/querying/querying-from-an-application.mdx b/website/pages/hi/querying/querying-from-an-application.mdx
index ca17bd01c802..56b0d3f933c2 100644
--- a/website/pages/hi/querying/querying-from-an-application.mdx
+++ b/website/pages/hi/querying/querying-from-an-application.mdx
@@ -2,42 +2,46 @@
 title: एक एप्लिकेशन से क्वेरी करना
 ---
 
-Once a subgraph is deployed to Subgraph Studio or to Graph Explorer, you will be given the endpoint for your GraphQL API that should look something like this:
+Learn how to query The Graph from your application.
 
-**सबग्राफ स्टूडियो (परीक्षण समापन बिंदु)**
+## Getting GraphQL Endpoint
 
-```sh
-Queries (HTTP)
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
 https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
 ```
 
-**Graph Explorer**
+### Graph Explorer
 
-```sh
-Queries (HTTP)
+```
 https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
 ```
 
-ग्राफक्यूएल एंडपॉइंट का उपयोग करके, आप सबग्राफ को क्वेरी करने के लिए विभिन्न ग्राफक्लाइन क्लाइंट लाइब्रेरी का उपयोग कर सकते हैं और सबग्राफ द्वारा अनुक्रमित डेटा के साथ अपने ऐप को पॉप्युलेट कर सकते हैं।
-
-यहां पारिस्थितिकी तंत्र में कुछ अधिक लोकप्रिय ग्राफक्यूएल ग्राहक हैं और उनका उपयोग कैसे करें:
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
 
-## GraphQL क्लाइंट
+## Using Popular GraphQL Clients
 
-### ग्राफ क्लाइंट
+### Graph Client
 
-ग्राफ़ इसे अपना ग्राफ़िकल क्लाइंट प्रदान कर रहा है, `ग्राफ़-क्लाइंट` जो अनूठी विशेषताओं का समर्थन करता है जैसे:
+The Graph अपना खुद का GraphQL क्लाइंट प्रदान कर रहा है, `graph-client` जो अनोखी सुविधाओं का समर्थन करता है जैसे:
 
 - क्रॉस-चेन सबग्राफ हैंडलिंग: एक ही क्वेरी में कई सबग्राफ से पूछताछ
 - [स्वचालित ब्लॉक ट्रैकिंग](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
 - [स्वचालित पृष्ठांकन](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
 - पूरी तरह से टाइप किया गया परिणाम
 
-Also integrated with popular GraphQL clients such as Apollo and URQL and compatible with all environments (React, Angular, Node.js, React Native), using `graph-client` will give you the best experience for interacting with The Graph.
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
 
-Let's look at how to fetch data from a subgraph with `graphql-client`.
+#### स्टेप 1
 
-To get started, make sure to install The Graph Client CLI in your project:
+Install The Graph Client CLI in your project:
 
 ```sh
 yarn add -D @graphprotocol/client-cli
@@ -45,6 +49,8 @@ yarn add -D @graphprotocol/client-cli
 npm install --save-dev @graphprotocol/client-cli
 ```
 
+#### चरण 2
+
 Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
 
 ```graphql
@@ -72,7 +78,9 @@ query ExampleQuery {
 }
 ```
 
-Then, create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+#### चरण 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
 
 ```yaml
 # .graphclientrc.yml
@@ -90,13 +98,17 @@ documents:
   - ./src/example-query.graphql
 ```
 
-Running the following The Graph Client CLI command will generate typed and ready to use JavaScript code:
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
 
 ```sh
 graphclient build
 ```
 
-Finally, update your `.ts` file to use the generated typed GraphQL documents:
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
 
 ```tsx
 import React, { useEffect } from 'react'
@@ -134,33 +146,35 @@ function App() {
 export default App
 ```
 
-**⚠️ Important notice**
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
 
-`graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you will [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples).
+### Apollo Client
 
-However, if you choose to go with another client, keep in mind that **you won't be able to get to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
 
-### अपोलो ग्राहक
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
 
-[Apollo client](https://www.apollographql.com/docs/) is the ubiquitous GraphQL client on the front-end ecosystem.
+- Advanced error handling
+- पृष्ठ पर अंक लगाना
+- Data prefetching
+- Optimistic UI
+- Local state management
 
-Available for React, Angular, Vue, Ember, iOS, and Android, Apollo Client, although the heaviest client, brings many features to build advanced UI on top of GraphQL:
+### Fetch Data with Apollo Client
 
-- advanced error handling
-- pagination
-- data prefetching
-- optimistic UI
-- local state management
+Let's look at how to fetch data from a subgraph with Apollo client:
 
-Let's look at how to fetch data from a subgraph with Apollo client in a web project.
+#### स्टेप 1
 
-First, install `@apollo/client` and `graphql`:
+Install `@apollo/client` and `graphql`:
 
 ```sh
 npm install @apollo/client graphql
 ```
 
-फिर आप निम्नलिखित कोड के साथ एपीआई से पूछ सकते हैं:
+#### चरण 2
+
+Query the API with the following code:
 
 ```javascript
 import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
@@ -193,6 +207,8 @@ client
   })
 ```
 
+#### चरण 3
+
 To use variables, you can pass in a `variables` argument to the query:
 
 ```javascript
@@ -224,24 +240,30 @@ client
   })
 ```
 
-### URQL
+### URQL Overview
 
-Another option is [URQL](https://formidable.com/open-source/urql/) which is available within Node.js, React/Preact, Vue, and Svelte environments, with more advanced features:
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
 
 - Flexible cache system
 - एक्स्टेंसिबल डिज़ाइन (इसके शीर्ष पर नई क्षमताओं को जोड़ना आसान)
 - लाइटवेट बंडल (अपोलो क्लाइंट की तुलना में ~ 5x हल्का)
 - फ़ाइल अपलोड और ऑफ़लाइन मोड के लिए समर्थन
 
-Let's look at how to fetch data from a subgraph with URQL in a web project.
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
 
-First, install `urql` and `graphql`:
+#### स्टेप 1
+
+Install `urql` and `graphql`:
 
 ```sh
 npm install urql graphql
 ```
 
-फिर आप निम्नलिखित कोड के साथ एपीआई से पूछ सकते हैं:
+#### चरण 2
+
+Query the API with the following code:
 
 ```javascript
 import { createClient } from 'urql'

From f749ae3a5adc840d3b9e11e6b0ae4e1a45d28b0c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:10 -0500
Subject: [PATCH 0860/1325] New translations querying-from-an-application.mdx
 (Swahili)

---
 .../querying/querying-from-an-application.mdx | 289 ++++++++++++++++++
 1 file changed, 289 insertions(+)
 create mode 100644 website/pages/sw/querying/querying-from-an-application.mdx

diff --git a/website/pages/sw/querying/querying-from-an-application.mdx b/website/pages/sw/querying/querying-from-an-application.mdx
new file mode 100644
index 000000000000..a9f8162ebcf0
--- /dev/null
+++ b/website/pages/sw/querying/querying-from-an-application.mdx
@@ -0,0 +1,289 @@
+---
+title: Querying from an Application
+---
+
+Learn how to query The Graph from your application.
+
+## Getting GraphQL Endpoint
+
+Once a subgraph is deployed to [Subgraph Studio](https://thegraph.com/studio/) or [Graph Explorer](https://thegraph.com/explorer), you will be given the endpoint for your GraphQL API that should look something like this:
+
+### Subgraph Studio
+
+```
+https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>
+```
+
+### Graph Explorer
+
+```
+https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>
+```
+
+With your GraphQL endpoint, you can use various GraphQL Client libraries to query the subgraph and populate your app with data indexed by the subgraph.
+
+## Using Popular GraphQL Clients
+
+### Graph Client
+
+The Graph is providing its own GraphQL client, `graph-client` that supports unique features such as:
+
+- Cross-chain Subgraph Handling: Querying from multiple subgraphs in a single query
+- [Automatic Block Tracking](https://github.com/graphprotocol/graph-client/blob/main/packages/block-tracking/README.md)
+- [Automatic Pagination](https://github.com/graphprotocol/graph-client/blob/main/packages/auto-pagination/README.md)
+- Fully typed result
+
+> Note: `graph-client` is integrated with other popular GraphQL clients such as Apollo and URQL, which are compatible with environments such as React, Angular, Node.js, and React Native. As a result, using `graph-client` will provide you with an enhanced experience for working with The Graph.
+
+### Fetch Data with Graph Client
+
+Let's look at how to fetch data from a subgraph with `graph-client`:
+
+#### Step 1
+
+Install The Graph Client CLI in your project:
+
+```sh
+yarn add -D @graphprotocol/client-cli
+# or, with NPM:
+npm install --save-dev @graphprotocol/client-cli
+```
+
+#### Step 2
+
+Define your query in a `.graphql` file (or inlined in your `.js` or `.ts` file):
+
+```graphql
+query ExampleQuery {
+  # this one is coming from compound-v2
+  markets(first: 7) {
+    borrowRate
+    cash
+    collateralFactor
+  }
+  # this one is coming from uniswap-v2
+  pair(id: "0x00004ee988665cdda9a1080d5792cecd16dc1220") {
+    id
+    token0 {
+      id
+      symbol
+      name
+    }
+    token1 {
+      id
+      symbol
+      name
+    }
+  }
+}
+```
+
+#### Step 3
+
+Create a configuration file (called `.graphclientrc.yml`) and point to your GraphQL endpoints provided by The Graph, for example:
+
+```yaml
+# .graphclientrc.yml
+sources:
+  - name: uniswapv2
+    handler:
+      graphql:
+        endpoint: https://api.thegraph.com/subgraphs/name/uniswap/uniswap-v2
+  - name: compoundv2
+    handler:
+      graphql:
+        endpoint: https://api.thegraph.com/subgraphs/name/graphprotocol/compound-v2
+
+documents:
+  - ./src/example-query.graphql
+```
+
+#### Step 4
+
+Run the following The Graph Client CLI command to generate typed and ready to use JavaScript code:
+
+```sh
+graphclient build
+```
+
+#### Step 5
+
+Update your `.ts` file to use the generated typed GraphQL documents:
+
+```tsx
+import React, { useEffect } from 'react'
+// ...
+// we import types and typed-graphql document from the generated code (`..graphclient/`)
+import { ExampleQueryDocument, ExampleQueryQuery, execute } from '../.graphclient'
+
+function App() {
+  const [data, setData] = React.useState<ExampleQueryQuery>()
+
+  useEffect(() => {
+    execute(ExampleQueryDocument, {}).then((result) => {
+      setData(result?.data)
+    })
+  }, [setData])
+  return (
+    <div className="App">
+      <header className="App-header">
+        <img src={logo} className="App-logo" alt="logo" />
+        <p>Graph Client Example</p>
+        <fieldset>
+          {data && (
+            <form>
+              <label>Data</label>
+              <br />
+              <textarea value={JSON.stringify(data, null, 2)} readOnly rows={25} />
+            </form>
+          )}
+        </fieldset>
+      </header>
+    </div>
+  )
+}
+
+export default App
+```
+
+> **Important Note:** `graph-client` is perfectly integrated with other GraphQL clients such as Apollo client, URQL, or React Query; you can [find examples in the official repository](https://github.com/graphprotocol/graph-client/tree/main/examples). However, if you choose to go with another client, keep in mind that **you won't be able to use Cross-chain Subgraph Handling or Automatic Pagination, which are core features for querying The Graph**.
+
+### Apollo Client
+
+[Apollo client](https://www.apollographql.com/docs/) is a common GraphQL client on front-end ecosystems. It's available for React, Angular, Vue, Ember, iOS, and Android.
+
+Although it's the heaviest client, it has many features to build advanced UI on top of GraphQL:
+
+- Advanced error handling
+- Pagination
+- Data prefetching
+- Optimistic UI
+- Local state management
+
+### Fetch Data with Apollo Client
+
+Let's look at how to fetch data from a subgraph with Apollo client:
+
+#### Step 1
+
+Install `@apollo/client` and `graphql`:
+
+```sh
+npm install @apollo/client graphql
+```
+
+#### Step 2
+
+Query the API with the following code:
+
+```javascript
+import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
+
+const APIURL = 'https://api.studio.thegraph.com/query//<SUBGRAPH_NAME>/'
+
+const tokensQuery = `
+  query {
+    tokens {
+      id
+      tokenID
+      contentURI
+      metadataURI
+    }
+  }
+`
+
+const client = new ApolloClient({
+  uri: APIURL,
+  cache: new InMemoryCache(),
+})
+
+client
+  .query({
+    query: gql(tokensQuery),
+  })
+  .then((data) => console.log('Subgraph data: ', data))
+  .catch((err) => {
+    console.log('Error fetching data: ', err)
+  })
+```
+
+#### Step 3
+
+To use variables, you can pass in a `variables` argument to the query:
+
+```javascript
+const tokensQuery = `
+  query($first: Int, $orderBy: BigInt, $orderDirection: String) {
+    tokens(
+      first: $first, orderBy: $orderBy, orderDirection: $orderDirection
+    ) {
+      id
+      tokenID
+      contentURI
+      metadataURI
+    }
+  }
+`
+
+client
+  .query({
+    query: gql(tokensQuery),
+    variables: {
+      first: 10,
+      orderBy: 'createdAtTimestamp',
+      orderDirection: 'desc',
+    },
+  })
+  .then((data) => console.log('Subgraph data: ', data))
+  .catch((err) => {
+    console.log('Error fetching data: ', err)
+  })
+```
+
+### URQL Overview
+
+[URQL](https://formidable.com/open-source/urql/) is available within Node.js, React/Preact, Vue, and Svelte environments, with some more advanced features:
+
+- Flexible cache system
+- Extensible design (easing adding new capabilities on top of it)
+- Lightweight bundle (~5x lighter than Apollo Client)
+- Support for file uploads and offline mode
+
+### Fetch data with URQL
+
+Let's look at how to fetch data from a subgraph with URQL:
+
+#### Step 1
+
+Install `urql` and `graphql`:
+
+```sh
+npm install urql graphql
+```
+
+#### Step 2
+
+Query the API with the following code:
+
+```javascript
+import { createClient } from 'urql'
+
+const APIURL = 'https://api.thegraph.com/subgraphs/name/username/subgraphname'
+
+const tokensQuery = `
+  query {
+    tokens {
+      id
+      tokenID
+      contentURI
+      metadataURI
+    }
+  }
+`
+
+const client = createClient({
+  url: APIURL,
+})
+
+const data = await client.query(tokensQuery).toPromise()
+```

From 82a8c50ee4bf9827776adce044f8fb2dc8a694d9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:12 -0500
Subject: [PATCH 0861/1325] New translations querying-the-graph.mdx (Romanian)

---
 website/pages/ro/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/ro/querying/querying-the-graph.mdx b/website/pages/ro/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/ro/querying/querying-the-graph.mdx
+++ b/website/pages/ro/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 14a9694811b285bf45d5cba2202f93910af0c87e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:13 -0500
Subject: [PATCH 0862/1325] New translations querying-the-graph.mdx (French)

---
 website/pages/fr/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/fr/querying/querying-the-graph.mdx b/website/pages/fr/querying/querying-the-graph.mdx
index 70023beddd1c..1b838400c6d3 100644
--- a/website/pages/fr/querying/querying-the-graph.mdx
+++ b/website/pages/fr/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Interroger The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Vous pouvez également utiliser le terrain de jeu GraphQL dans l'onglet « Terrain de jeu » pour interroger un subgraph dans The Graph Explorer](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 63194b8fed7c5b81691c7fc7926858fd9b2ca3e8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:14 -0500
Subject: [PATCH 0863/1325] New translations querying-the-graph.mdx (Spanish)

---
 website/pages/es/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/es/querying/querying-the-graph.mdx b/website/pages/es/querying/querying-the-graph.mdx
index eb097ce2bdb6..fc87e026d7a1 100644
--- a/website/pages/es/querying/querying-the-graph.mdx
+++ b/website/pages/es/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Consultando The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Panel de Consulta de Subgrafos](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 5415debd45796d6a7298a1fabbccc734d769dc8c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:15 -0500
Subject: [PATCH 0864/1325] New translations querying-the-graph.mdx (Arabic)

---
 website/pages/ar/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/ar/querying/querying-the-graph.mdx b/website/pages/ar/querying/querying-the-graph.mdx
index aeef84cbe5a9..1255e0e88a51 100644
--- a/website/pages/ar/querying/querying-the-graph.mdx
+++ b/website/pages/ar/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![نافذة الاستعلام عن Subgraph](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From a71d972eac357303095d05093066d8cb96a95dc3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:16 -0500
Subject: [PATCH 0865/1325] New translations querying-the-graph.mdx (Czech)

---
 website/pages/cs/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/cs/querying/querying-the-graph.mdx b/website/pages/cs/querying/querying-the-graph.mdx
index ac2e872c87d2..b6baece6bdaa 100644
--- a/website/pages/cs/querying/querying-the-graph.mdx
+++ b/website/pages/cs/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Dotazování na graf
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Podokno podgrafů dotazů](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 8328941f60d60755e9d77c2044932982d00fc820 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:17 -0500
Subject: [PATCH 0866/1325] New translations querying-the-graph.mdx (German)

---
 website/pages/de/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/de/querying/querying-the-graph.mdx b/website/pages/de/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/de/querying/querying-the-graph.mdx
+++ b/website/pages/de/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From cfa40678203123a27d9b4bf225aa0d72a280d46e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:18 -0500
Subject: [PATCH 0867/1325] New translations querying-the-graph.mdx (Italian)

---
 website/pages/it/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/it/querying/querying-the-graph.mdx b/website/pages/it/querying/querying-the-graph.mdx
index c98fe01cfe4a..2041f36072de 100644
--- a/website/pages/it/querying/querying-the-graph.mdx
+++ b/website/pages/it/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Effettuare query di The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Riquadro del Subgraph della Query](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 426e5664a242bb0c85be679f62dba67cbbd86b6f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:19 -0500
Subject: [PATCH 0868/1325] New translations querying-the-graph.mdx (Japanese)

---
 website/pages/ja/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/ja/querying/querying-the-graph.mdx b/website/pages/ja/querying/querying-the-graph.mdx
index 91cb67a2b7dd..663be78da991 100644
--- a/website/pages/ja/querying/querying-the-graph.mdx
+++ b/website/pages/ja/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: The Graphのクエリ
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![クエリ サブグラフ ペイン](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 9a876880c128f502bd4e86e2946b437cc20203bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:20 -0500
Subject: [PATCH 0869/1325] New translations querying-the-graph.mdx (Korean)

---
 website/pages/ko/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/ko/querying/querying-the-graph.mdx b/website/pages/ko/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/ko/querying/querying-the-graph.mdx
+++ b/website/pages/ko/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 8db6cefadac6b1ab5247dcc22b7cd6a4009aaf59 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:21 -0500
Subject: [PATCH 0870/1325] New translations querying-the-graph.mdx (Dutch)

---
 website/pages/nl/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/nl/querying/querying-the-graph.mdx b/website/pages/nl/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/nl/querying/querying-the-graph.mdx
+++ b/website/pages/nl/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From c496c38a8e4194e5091414754e0525bef435c638 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:22 -0500
Subject: [PATCH 0871/1325] New translations querying-the-graph.mdx (Polish)

---
 website/pages/pl/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/pl/querying/querying-the-graph.mdx b/website/pages/pl/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/pl/querying/querying-the-graph.mdx
+++ b/website/pages/pl/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 45b1f6207523ab3dbf3c866c15ebeabbb3e566e3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:23 -0500
Subject: [PATCH 0872/1325] New translations querying-the-graph.mdx
 (Portuguese)

---
 website/pages/pt/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/pt/querying/querying-the-graph.mdx b/website/pages/pt/querying/querying-the-graph.mdx
index 48bbd28e2fed..ae925ba0856a 100644
--- a/website/pages/pt/querying/querying-the-graph.mdx
+++ b/website/pages/pt/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Queries no The Graph
 ---
 
-Quando um subgraph é editado na Graph Network, é possível visitar a sua página de detalhes no [Graph Explorer](https://thegraph.com/explorer) e usar a aba "Playground" para explorar a API GraphQL lançada para o subgraph, emitir queries e visualizar o schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Por favor, confira a [API de Queries](/querying/graphql-api) para uma referência completa em como fazer queries das entidades do subgraph. É possível ler sobre as melhores práticas de querying em GraphQL [aqui](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ Quando um subgraph é editado na Graph Network, é possível visitar a sua pági
 
 Cada subgraph publicado à Graph Network tem um URL singular de query no Graph Explorer para fazer queries diretos que podem ser encontrados ao navegar até a página de detalhes do subgraph e clicar no botão "Query" no canto superior direito.
 
-![Consultar o Painel do Subgraph](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Aprenda mais sobre queries de um aplicativo [aqui](/querying/querying-from-an-application).
 

From d46278812ff395e91949e34d6cf3e785a5a72a62 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:24 -0500
Subject: [PATCH 0873/1325] New translations querying-the-graph.mdx (Russian)

---
 website/pages/ru/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/querying/querying-the-graph.mdx b/website/pages/ru/querying/querying-the-graph.mdx
index 54f6c329b3a5..230016e09682 100644
--- a/website/pages/ru/querying/querying-the-graph.mdx
+++ b/website/pages/ru/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Запрос The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Панель запроса субграфа](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 7589d437143fb3fff2c79bc27d4288ef2303c8c7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:25 -0500
Subject: [PATCH 0874/1325] New translations querying-the-graph.mdx (Swedish)

---
 website/pages/sv/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/sv/querying/querying-the-graph.mdx b/website/pages/sv/querying/querying-the-graph.mdx
index d0f9a79274bd..6d6618616eb2 100644
--- a/website/pages/sv/querying/querying-the-graph.mdx
+++ b/website/pages/sv/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Fråga The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Panel för att fråga subgraf](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 87e5323db7a0f77aacd4ca4a3b4439b3ce567c48 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:26 -0500
Subject: [PATCH 0875/1325] New translations querying-the-graph.mdx (Turkish)

---
 website/pages/tr/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/tr/querying/querying-the-graph.mdx b/website/pages/tr/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/tr/querying/querying-the-graph.mdx
+++ b/website/pages/tr/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 247d2a3328ff89eddae731e0220bda339edaae1f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:27 -0500
Subject: [PATCH 0876/1325] New translations querying-the-graph.mdx (Ukrainian)

---
 website/pages/uk/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/uk/querying/querying-the-graph.mdx b/website/pages/uk/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/uk/querying/querying-the-graph.mdx
+++ b/website/pages/uk/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From bb4e92e257bff682081d295f135dd1ba14188ab3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:28 -0500
Subject: [PATCH 0877/1325] New translations querying-the-graph.mdx (Chinese
 Simplified)

---
 website/pages/zh/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/zh/querying/querying-the-graph.mdx b/website/pages/zh/querying/querying-the-graph.mdx
index 84ad6f212b9d..de89bd6af491 100644
--- a/website/pages/zh/querying/querying-the-graph.mdx
+++ b/website/pages/zh/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: 查询Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![查询子图镶嵌](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From f21e00fb4ca81d8f6b11ec8b6769802f06d336ff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:29 -0500
Subject: [PATCH 0878/1325] New translations querying-the-graph.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/ur/querying/querying-the-graph.mdx b/website/pages/ur/querying/querying-the-graph.mdx
index ffa73e39614b..3228643fd71c 100644
--- a/website/pages/ur/querying/querying-the-graph.mdx
+++ b/website/pages/ur/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: گراف سے کیوری کرنا
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![سب گراف پین سے کیوری کریں](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From ba69b77e7127def22856121e6097df721a34b506 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:30 -0500
Subject: [PATCH 0879/1325] New translations querying-the-graph.mdx
 (Vietnamese)

---
 website/pages/vi/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/vi/querying/querying-the-graph.mdx b/website/pages/vi/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/vi/querying/querying-the-graph.mdx
+++ b/website/pages/vi/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From ad7f4ace98c79e5ed82b5af66685ab589589ed76 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:31 -0500
Subject: [PATCH 0880/1325] New translations querying-the-graph.mdx (Marathi)

---
 website/pages/mr/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/mr/querying/querying-the-graph.mdx b/website/pages/mr/querying/querying-the-graph.mdx
index a573683573c5..1255e0e88a51 100644
--- a/website/pages/mr/querying/querying-the-graph.mdx
+++ b/website/pages/mr/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: Querying The Graph
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![Query Subgraph Pane](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 6e9cad77e0b8051fa2a1be4be73c232e3c7981b5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:32 -0500
Subject: [PATCH 0881/1325] New translations querying-the-graph.mdx (Hindi)

---
 website/pages/hi/querying/querying-the-graph.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/hi/querying/querying-the-graph.mdx b/website/pages/hi/querying/querying-the-graph.mdx
index 531f99cf77e3..54d07075671a 100644
--- a/website/pages/hi/querying/querying-the-graph.mdx
+++ b/website/pages/hi/querying/querying-the-graph.mdx
@@ -2,7 +2,7 @@
 title: ग्राफ़ को क्वेरी करना
 ---
 
-When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "Playground" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
 
 > Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
 
@@ -10,7 +10,9 @@ When a subgraph is published to The Graph Network, you can visit its subgraph de
 
 Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
 
-![क्वेरी सबग्राफ फलक](/img/query-subgraph-pane.png)
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
 
 Learn more about querying from an application [here](/querying/querying-from-an-application).
 

From 8193c25fc9f2cf556ed296300859bcc6bb7e92ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:34 -0500
Subject: [PATCH 0882/1325] New translations querying-the-graph.mdx (Swahili)

---
 .../pages/sw/querying/querying-the-graph.mdx  | 21 +++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/sw/querying/querying-the-graph.mdx

diff --git a/website/pages/sw/querying/querying-the-graph.mdx b/website/pages/sw/querying/querying-the-graph.mdx
new file mode 100644
index 000000000000..1255e0e88a51
--- /dev/null
+++ b/website/pages/sw/querying/querying-the-graph.mdx
@@ -0,0 +1,21 @@
+---
+title: Querying The Graph
+---
+
+When a subgraph is published to The Graph Network, you can visit its subgraph details page on [Graph Explorer](https://thegraph.com/explorer) and use the "query" tab to explore the deployed GraphQL API for the subgraph, issuing queries and viewing the schema.
+
+> Please see the [Query API](/querying/graphql-api) for a complete reference on how to query the subgraph's entities. You can learn about GraphQL querying best practices [here](/querying/querying-best-practices)
+
+> Note: If you encounter 405 errors with a GET request to the Graph Explorer URL, please switch to a POST request instead.
+
+Each subgraph published to The Graph Network has a unique query URL in Graph Explorer for making direct queries that you can find by navigating to the subgraph details page and clicking on the "Query" button on the top right corner.
+
+![Query Subgraph Button](/img/query-button-screenshot.png)
+
+![Query Subgraph URL](/img/query-url-screenshot.png)
+
+Learn more about querying from an application [here](/querying/querying-from-an-application).
+
+As you can notice, this query URL must use a unique API key. You can create and manage your API keys in [Subgraph Studio](https://thegraph.com/studio), in the "API Keys" section. Learn more about how to use Subgraph Studio [here](/deploying/subgraph-studio).
+
+Subgraph Studio users start on a Free Plan, which allows them to make 100,000 queries per month. Additional queries are available on the Growth Plan, which offers usage based pricing for additional queries, payable by credit card, or GRT on Arbitrum. You can learn more about billing [here](/billing).

From 8839568e6e930f8914172aa95546e901c1f41e5b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:35 -0500
Subject: [PATCH 0883/1325] New translations assemblyscript-migration-guide.mdx
 (Romanian)

---
 .../ro/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx
index 85f6903a6c69..17224699570d 100644
--- a/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From daee45779c22886ab049770172035dd3271be7a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:36 -0500
Subject: [PATCH 0884/1325] New translations assemblyscript-migration-guide.mdx
 (French)

---
 .../assemblyscript-migration-guide.mdx            | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx
index 49e76d908653..619ba98b326a 100644
--- a/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 Vous devrez renommer vos variables en double si vous conservez une observation de variables.
-
 ### Comparaisons nulles
-
 En effectuant la mise à niveau sur votre subgraph, vous pouvez parfois obtenir des erreurs comme celles-ci :
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 Pour résoudre, vous pouvez simplement remplacer l'instruction `if` par quelque chose comme ceci :
 
 ```typescript
@@ -213,7 +209,7 @@ Dans ces cas-là, vous pouvez utiliser la fonction `changetype<T>` :
 class Bytes extends Uint8Array {}
 
 let uint8Array = new Uint8Array(2)
-changetype<Bytes>(uint8Array) // fonctionne :)
+changetype<Bytes>(uint8Array ) // fonctionne :)
 ```
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 Pour résoudre ce problème, vous pouvez créer une variable pour l'accès à cette propriété afin que le compilateur puisse effectuer la vérification magique de la nullité :
 
 ```typescript
@@ -406,7 +401,7 @@ type Total @entity {
 let total = Total.load('latest')
 
 if (total === null) {
-  total = new Total('latest') // initialise déjà les propriétés non-nullables
+    total = new Total('latest') // initialise déjà les propriétés non-nullables
 }
 
 total.amount = total.amount + BigInt.fromI32(1)
@@ -488,12 +483,12 @@ Vous ne pouvez désormais plus définir de champs dans vos types qui sont des li
 
 ```graphql
 type Something @entity {
-  id: Bytes!
+    id: Bytes!
 }
 
 type MyEntity @entity {
-  id: Bytes!
-  invalidField: [Something]! # n'est plus valide
+    id: Bytes!
+    invalidField: [Something]! # n'est plus valide
 }
 ```
 

From 40ffeba03075e2fed911dc8c991490eca1e812ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:37 -0500
Subject: [PATCH 0885/1325] New translations assemblyscript-migration-guide.mdx
 (Spanish)

---
 .../es/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/es/release-notes/assemblyscript-migration-guide.mdx b/website/pages/es/release-notes/assemblyscript-migration-guide.mdx
index bfc973f982dd..c3770a5c9ef7 100644
--- a/website/pages/es/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/es/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 Tendrás que cambiar el nombre de las variables duplicadas si tienes una variable shadowing.
-
 ### Comparaciones Nulas
-
 Al hacer la actualización en un subgrafo, a veces pueden aparecer errores como estos:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 Para solucionarlo puedes simplemente cambiar la declaración `if` por algo así:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 Para solucionar este problema, puedes crear una variable para ese acceso a la propiedad de manera que el compilador pueda hacer la magia de la comprobación de nulidad:
 
 ```typescript

From 22ed59e175f428e6f93a24fe90de8e5141781bee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:38 -0500
Subject: [PATCH 0886/1325] New translations assemblyscript-migration-guide.mdx
 (Arabic)

---
 .../ar/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx
index 84e00f13b4e1..9674f1777573 100644
--- a/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ let a = a + b
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 ستحتاج إلى إعادة تسمية المتغيرات المكررة إذا كان لديك variable shadowing.
-
 ### مقارانات Null
-
 من خلال إجراء الترقية على ال Subgraph الخاص بك ، قد تحصل أحيانًا على أخطاء مثل هذه:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 لحل المشكلة يمكنك ببساطة تغيير عبارة `if` إلى شيء مثل هذا:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 لإصلاح هذه المشكلة ، يمكنك إنشاء متغير للوصول إلى الخاصية حتى يتمكن المترجم من القيام بعملية التحقق من الـ nullability:
 
 ```typescript

From 43f05c47b77d7e7dd46744e8af1c43b03a171b90 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:39 -0500
Subject: [PATCH 0887/1325] New translations assemblyscript-migration-guide.mdx
 (Czech)

---
 .../cs/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx b/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx
index d1b9eb00bc04..e59516868de6 100644
--- a/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 Pokud jste použili stínování proměnných, musíte duplicitní proměnné přejmenovat.
-
 ### Nulová srovnání
-
 Při aktualizaci podgrafu může někdy dojít k těmto chybám:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 Pro vyřešení můžete jednoduše změnit příkaz `if` na něco takového:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 Chcete-li tento problém vyřešit, můžete vytvořit proměnnou pro přístup k této vlastnosti, aby překladač mohl provést kouzlo kontroly nulovatelnosti:
 
 ```typescript

From c910ff9de74bc930ab2144f5d8e7c2fea5d87bf1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:41 -0500
Subject: [PATCH 0888/1325] New translations assemblyscript-migration-guide.mdx
 (German)

---
 .../de/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/de/release-notes/assemblyscript-migration-guide.mdx b/website/pages/de/release-notes/assemblyscript-migration-guide.mdx
index fb1ad8beb382..058c48b32e6f 100644
--- a/website/pages/de/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/de/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From 53387091580af15a8a70f122e2241e842975f12a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:42 -0500
Subject: [PATCH 0889/1325] New translations assemblyscript-migration-guide.mdx
 (Italian)

---
 .../it/release-notes/assemblyscript-migration-guide.mdx    | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/website/pages/it/release-notes/assemblyscript-migration-guide.mdx b/website/pages/it/release-notes/assemblyscript-migration-guide.mdx
index b6bd7ecc38d2..64cbf23decf7 100644
--- a/website/pages/it/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/it/release-notes/assemblyscript-migration-guide.mdx
@@ -59,7 +59,7 @@ dataSources:
 2. Aggiornare il `graph-cli` in uso alla versione `ultima` eseguendo:
 
 ```bash
-# se è installato globalmente
+# se è installato globalmente 
 npm install --global @graphprotocol/graph-cli@latest
 
 # o nel proprio subgraph, se è una dipendenza di dev
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 È necessario rinominare le variabili duplicate se si dispone di un'ombreggiatura delle variabili.
-
 ### Confronti nulli
-
 Eseguendo l'aggiornamento sul subgraph, a volte si possono ottenere errori come questi:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 Per risolvere il problema è sufficiente modificare l'istruzione `if` in qualcosa di simile:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 Per risolvere questo problema, si può creare una variabile per l'accesso alla proprietà, in modo che il compilatore possa fare la magia del controllo di annullabilità:
 
 ```typescript

From 29dc555b0de5a70ea19269603957deda0959e7ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:43 -0500
Subject: [PATCH 0890/1325] New translations assemblyscript-migration-guide.mdx
 (Japanese)

---
 .../ja/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx
index 766fbb6c80a3..82a7d23de3f8 100644
--- a/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 変数シャドウイングを行っていた場合は、重複する変数の名前を変更する必要があります。
-
 ### Null 比較
-
 サブグラフのアップグレードを行うと、時々以下のようなエラーが発生することがあります。
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 解決するには、 `if` 文を以下のように変更するだけです。
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 この問題を解決するには、そのプロパティアクセスのための変数を作成して、コンパイラが nullability check のマジックを行うようにします。
 
 ```typescript

From 1326805e77516a0d0361543328346dc6d2813d38 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:44 -0500
Subject: [PATCH 0891/1325] New translations assemblyscript-migration-guide.mdx
 (Korean)

---
 .../ko/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx
index 85f6903a6c69..17224699570d 100644
--- a/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From 4bead84f8898c7537084df479c993d2ba7670a0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:45 -0500
Subject: [PATCH 0892/1325] New translations assemblyscript-migration-guide.mdx
 (Dutch)

---
 .../nl/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx b/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx
index 85f6903a6c69..17224699570d 100644
--- a/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From 327411bc5aa1d4c81135340b0b19bb0eb49300a7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:46 -0500
Subject: [PATCH 0893/1325] New translations assemblyscript-migration-guide.mdx
 (Polish)

---
 .../pl/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx b/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx
index 85f6903a6c69..17224699570d 100644
--- a/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From feafd10d2171aad18415ce5547380f58df762199 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:47 -0500
Subject: [PATCH 0894/1325] New translations assemblyscript-migration-guide.mdx
 (Portuguese)

---
 .../pt/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx b/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx
index ce410b9ed255..df425838fea1 100644
--- a/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 Renomeie as suas variáveis duplicadas, se tinha o sombreamento variável.
-
 ### Comparações de Nulos
-
 Ao fazer a atualização no seu subgraph, às vezes aparecem erros como este:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 Para resolver isto, basta mudar a declaração `if` para algo assim:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 Para consertar este problema, vale criar uma variável para aquele acesso à propriedade, para que o compilador faça a magia da checagem de anulabilidade:
 
 ```typescript

From 6ec799cf940243c0a665d50e2c15920c9c610e6d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:49 -0500
Subject: [PATCH 0895/1325] New translations assemblyscript-migration-guide.mdx
 (Russian)

---
 .../assemblyscript-migration-guide.mdx        | 152 +++++++++++++++++-
 1 file changed, 150 insertions(+), 2 deletions(-)

diff --git a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
index 255e27b7d743..efcb37d2c28d 100644
--- a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
@@ -27,8 +27,12 @@ title: Руководство по миграции AssemblyScript
 - Добавлена поддержка литеральных строк шаблона ([v0.18.17](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.17))
 - Добавление `encodeURI(Component)` и `decodeURI(Component)` ([v0.18.27](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.27))
 - Добавление `toString`, `toDateString` и `toTimeString` к `Date` ([v0.18.29](https://github.com/ AssemblyScript/assemblyscript/releases/tag/v0.18.29))
-- Добавление `toUTCString` для `Date` (v0.18.30)
-- Добавление встроенного типа `nonnull/NonNullable` ([v0.19.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.19.2))
+- Добавление `toUTCString` для `Date` (
+v0.18.30</а>)</li> 
+  
+  - Добавление встроенного типа `nonnull/NonNullable` ([v0.19.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.19.2))</ul> 
+
+
 
 ### Оптимизации
 
@@ -37,15 +41,21 @@ title: Руководство по миграции AssemblyScript
 - Кэширование большего количества обращений к полям в std Map и Set ([v0.17.8](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.17.8))
 - Оптимизация по двум степеням в `ipow32/64` ([v0.18.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.2))
 
+
+
 ### Прочее
 
 - Тип литерала массива теперь можно определить по его содержимому ([v0.9.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.0))
 - Стандартная библиотека обновлена до версии Unicode 13.0.0 ([v0.10.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.0))
 
+
+
 ## Как выполнить обновление?
 
 1. Измените мэппинги `apiVersion` в `subgraph.yaml` на `0.0.6`:
 
+
+
 ```yaml
 ...
 dataSources:
@@ -56,8 +66,11 @@ dataSources:
       ...
 ```
 
+
 2. Обновите используемый Вами `graph-cli` до `latest` версии, выполнив:
 
+
+
 ```bash
 # если он у Вас установлен глобально
 npm install --global @graphprotocol/graph-cli@latest
@@ -66,21 +79,31 @@ npm install --global @graphprotocol/graph-cli@latest
 npm install --save-dev @graphprotocol/graph-cli@latest
 ```
 
+
 3. Сделайте то же самое для `graph-ts`, но вместо глобальной установки сохраните его в своих основных зависимостях:
 
+
+
 ```bash
 npm install --save @graphprotocol/graph-ts@latest
 ```
 
+
 4. Следуйте остальной части руководства, чтобы исправить языковые изменения.
 5. Снова запустите `codegen` и `deploy`.
 
+
+
 ## Критические изменения
 
+
+
 ### Обнуляемость
 
 В более старой версии AssemblyScript можно было создать такой код:
 
+
+
 ```typescript
 function load(): Value | null { ... }
 
@@ -88,8 +111,11 @@ let maybeValue = load();
 maybeValue.aMethod();
 ```
 
+
 Однако в новой версии, поскольку значение обнуляемо, требуется проверка, например, такая:
 
+
+
 ```typescript
 let maybeValue = load()
 
@@ -98,28 +124,39 @@ if (maybeValue) {
 }
 ```
 
+
 Или принудительно вот такая:
 
+
+
 ```typescript
 let maybeValue = load()! // прерывается во время выполнения, если значение равно null
 
 maybeValue.aMethod()
 ```
 
+
 Если Вы не уверены, что выбрать, мы рекомендуем всегда использовать безопасную версию. Если значение не существует, Вы можете просто выполнить раннее выражение if с возвратом в обработчике субграфа.
 
+
+
 ### Затенение переменных
 
 Раньше можно было сделать [затенение переменных](https://en.wikipedia.org/wiki/Variable_shadowing) и код, подобный этому, работал:
 
+
+
 ```typescript
 let a = 10
 let b = 20
 let a = a + b
 ```
 
+
 Однако теперь это больше невозможно, и компилятор возвращает эту ошибку:
 
+
+
 ```typescript
 ERROR TS2451: Cannot redeclare block-scoped variable 'a'
 
@@ -128,12 +165,16 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
 in assembly/index.ts(4,3)
 ```
 
+
 Вам нужно будет переименовать дублированные переменные, если Вы используете затенение переменных.
 
+
 ### Нулевые сравнения
 
 Выполняя обновление своего субграфа, иногда Вы можете получить такие ошибки:
 
+
+
 ```typescript
 ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' is not assignable to type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt'.
      if (decimals == null) {
@@ -141,8 +182,11 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
  in src/mappings/file.ts(41,21)
 ```
 
+
 Чтобы решить эту проблему, Вы можете просто изменить оператор `if` на что-то вроде этого:
 
+
+
 ```typescript
   if (!decimals) {
 
@@ -151,17 +195,23 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
   if (decimals === null) {
 ```
 
+
 Подобное относится к случаям, когда вместо == используется !=.
 
+
+
 ### Кастинг
 
 Раньше для кастинга обычно использовалось ключевое слово `as`, например:
 
+
+
 ```typescript
 let byteArray = new ByteArray(10)
 let uint8Array = byteArray as Uint8Array // equivalent to: <Uint8Array>byteArray
 ```
 
+
 Однако это работает только в двух случаях:
 
 - Примитивный кастинг (между такими типами, как `u8`, `i32`, `bool`; например: `let b: isize = 10; b as usize`);
@@ -169,6 +219,8 @@ let uint8Array = byteArray as Uint8Array // equivalent to: <Uint8Array>byteArray
 
 Примеры:
 
+
+
 ```typescript
 // примитивный кастинг
 let a: usize = 10
@@ -176,6 +228,9 @@ let b: isize = 5
 let c: usize = a + (b as usize)
 ```
 
+
+
+
 ```typescript
 // укрупнение по наследованию классов
 class Bytes extends Uint8Array {}
@@ -184,11 +239,14 @@ let bytes = new Bytes(2)
 // <Uint8Array>bytes // то же, что: bytes as Uint8Array
 ```
 
+
 Есть два сценария, в которых Вы можете захотеть выполнить преобразование, но использовать `as`/`<T>var` **небезопасно**:
 
 - Понижение уровня наследования классов (superclass → subclass)
 - Между двумя типами, имеющими общий супер класс
 
+
+
 ```typescript
 // понижение уровня наследования классов
 class Bytes extends Uint8Array {}
@@ -197,6 +255,9 @@ let uint8Array = new Uint8Array(2)
 // <Bytes>uint8Array // перерывы в работе :(
 ```
 
+
+
+
 ```typescript
 // между двумя типами, имеющими общий суперкласс
 class Bytes extends Uint8Array {}
@@ -206,8 +267,11 @@ let bytes = new Bytes(2)
 // <ByteArray>bytes // перерывы в работе :(
 ```
 
+
 В таких случаях можно использовать функцию `changetype<T>`:
 
+
+
 ```typescript
 // понижение уровня наследования классов
 class Bytes extends Uint8Array {}
@@ -216,6 +280,9 @@ let uint8Array = new Uint8Array(2)
 changetype<Bytes>(uint8Array) // работает :)
 ```
 
+
+
+
 ```typescript
 // между двумя типами, имеющими общий суперкласс
 class Bytes extends Uint8Array {}
@@ -225,8 +292,11 @@ let bytes = new Bytes(2)
 changetype<ByteArray>(bytes) // работает :)
 ```
 
+
 Если Вы просто хотите удалить значение NULL, Вы можете продолжать использовать оператор `as` (или `<T>variable`), но помните, что значение не может быть нулевым, иначе оно сломается.
 
+
+
 ```typescript
 // удалить значение NULL
 let previousBalance = AccountBalance.load(balanceId) // AccountBalance | null
@@ -238,6 +308,7 @@ if (previousBalance != null) {
 let newBalance = new AccountBalance(balanceId)
 ```
 
+
 В случае обнуления мы рекомендуем Вам обратить внимание на [функцию проверки обнуления](https://www.assemblyscript.org/basics.html#nullability-checks), это сделает ваш код чище 🙂
 
 Также мы добавили еще несколько статических методов в некоторые типы, чтобы облегчить кастинг:
@@ -247,10 +318,14 @@ let newBalance = new AccountBalance(balanceId)
 - BigInt.fromByteArray
 - ByteArray.fromBigInt
 
+
+
 ### Проверка нулевого значения с доступом к свойству
 
 Чтобы применить [функцию проверки на нулевое значение](https://www.assemblyscript.org/basics.html#nullability-checks), Вы можете использовать операторы `if` или тернарный оператор (`?` и `:`) следующим образом:
 
+
+
 ```typescript
 let something: string | null = 'data'
 
@@ -267,8 +342,11 @@ if (something) {
 }
 ```
 
+
 Однако это работает только тогда, когда Вы выполняете `if` / тернарную операцию для переменной, а не для доступа к свойству, например:
 
+
+
 ```typescript
 class Container {
   data: string | null
@@ -280,8 +358,11 @@ container.data = 'data'
 let somethingOrElse: string = container.data ? container.data : 'else' // не компилируется
 ```
 
+
 В результате чего выдается ошибка:
 
+
+
 ```typescript
 ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/string/String'.
 
@@ -289,8 +370,11 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
 
+
 Чтобы решить эту проблему, Вы можете создать переменную для доступа к этому свойству, чтобы компилятор мог выполнять проверку допустимости значений NULL:
 
+
+
 ```typescript
 class Container {
   data: string | null
@@ -304,10 +388,15 @@ let data = container.data
 let somethingOrElse: string = data ? data : 'else' // компилируется просто отлично :)
 ```
 
+
+
+
 ### Перегрузка оператора при доступе к свойствам
 
 Если Вы попытаетесь суммировать (например) тип, допускающий значение Null (из доступа к свойству), с типом, не допускающим значение Null, компилятор AssemblyScript вместо того, чтобы выдать предупреждение об ошибке компиляции, предупреждающую, что одно из значений допускает значение Null, просто компилируется молча, давая возможность сломать код во время выполнения.
 
+
+
 ```typescript
 class BigInt extends Uint8Array {
   @operator('+')
@@ -330,8 +419,11 @@ let wrapper = new Wrapper(y)
 wrapper.n = wrapper.n + x // не выдает ошибок времени компиляции, как это должно быть
 ```
 
+
 Мы открыли вопрос по этому поводу для компилятора AssemblyScript, но пока, если Вы выполняете подобные операции в своих мэппингах субграфов, Вам следует изменить их так, чтобы перед этим выполнялась проверка на нулевое значение.
 
+
+
 ```typescript
 let wrapper = new Wrapper(y)
 
@@ -342,26 +434,37 @@ if (!wrapper.n) {
 wrapper.n = wrapper.n + x // теперь `n` гарантированно будет BigInt
 ```
 
+
+
+
 ### Инициализация значения
 
 Если у Вас есть такой код:
 
+
+
 ```typescript
 var value: Type // null
 value.x = 10
 value.y = 'content'
 ```
 
+
 Он будет скомпилирован, но сломается во время выполнения. Это происходит из-за того, что значение не было инициализировано, поэтому убедитесь, что Ваш субграф инициализировал свои значения, например так:
 
+
+
 ```typescript
 var value = new Type() // initialized
 value.x = 10
 value.y = 'content'
 ```
 
+
 Также, если у Вас есть свойства, допускающие значение NULL, в объекте GraphQL, например:
 
+
+
 ```graphql
 type Total @entity {
   id: Bytes!
@@ -369,8 +472,11 @@ type Total @entity {
 }
 ```
 
+
 И у Вас есть код, аналогичный этому:
 
+
+
 ```typescript
 let total = Total.load('latest')
 
@@ -381,8 +487,11 @@ if (total === null) {
 total.amount = total.amount + BigInt.fromI32(1)
 ```
 
+
 Вам необходимо убедиться, что значение `total.amount` инициализировано, потому что, если Вы попытаетесь получить доступ к сумме, как в последней строке, произойдет сбой. Таким образом, Вы либо инициализируете его первым:
 
+
+
 ```typescript
 let total = Total.load('latest')
 
@@ -394,8 +503,11 @@ if (total === null) {
 total.tokens = total.tokens + BigInt.fromI32(1)
 ```
 
+
 Или Вы можете просто изменить свою схему GraphQL, чтобы не использовать тип, допускающий значение NULL для этого свойства. Тогда мы инициализируем его нулем на этапе `codegen` 😉
 
+
+
 ```graphql
 type Total @entity {
   id: Bytes!
@@ -403,6 +515,9 @@ type Total @entity {
 }
 ```
 
+
+
+
 ```typescript
 let total = Total.load('latest')
 
@@ -413,10 +528,15 @@ if (total === null) {
 total.amount = total.amount + BigInt.fromI32(1)
 ```
 
+
+
+
 ### Инициализация свойств класса
 
 Если Вы экспортируете какие-либо классы со свойствами, которые являются другими классами (декларированными Вами или стандартной библиотекой), то это выглядит следующим образом:
 
+
+
 ```typescript
 class Thing {}
 
@@ -425,8 +545,11 @@ export class Something {
 }
 ```
 
+
 Компилятор выдаст ошибку, потому что Вам нужно либо добавить инициализатор для свойств, являющихся классами, либо добавить оператор `!`:
 
+
+
 ```typescript
 export class Something {
   constructor(public value: Thing) {}
@@ -449,44 +572,63 @@ export class Something {
 }
 ```
 
+
+
+
 ### Инициализация массива
 
 Класс `Array` по-прежнему принимает число для инициализации длины списка, однако Вам следует соблюдать осторожность, поскольку такие операции, как `.push`, фактически увеличивают размер, а не добавляют его в начало, например:
 
+
+
 ```typescript
 let arr = new Array<string>(5) // ["", "", "", "", ""]
 
 arr.push('something') // ["", "", "", "", "", "something"] // size 6 :(
 ```
 
+
 В зависимости от используемых типов, например, допускающих значение NULL, и способа доступа к ним, можно столкнуться с ошибкой времени выполнения, подобной этой:
 
+
+
 ```
 ERRO Handler skipped due to execution failure, error: Mapping aborted at ~lib/array.ts, line 110, column 40, with message: Element type must be nullable if array is holey  wasm backtrace:     0: 0x19c4 - <unknown>!~lib/@graphprotocol/graph-ts/index/format         1: 0x1e75 - <unknown>!~lib/@graphprotocol/graph-ts/common/collections/Entity#constructor        2: 0x30b9 - <unknown>!node_modules/@graphprotocol/graph-ts/global/global/id_of_type
 ```
 
+
 Для того чтобы фактически начать, Вы должны либо инициализировать `Array` нулевым размером, следующим образом:
 
+
+
 ```typescript
 let arr = new Array<string>(0) // []
 
 arr.push('something') // ["something"]
 ```
 
+
 Или Вы должны изменить его через индекс:
 
+
+
 ```typescript
 let arr = new Array<string>(5) // ["", "", "", "", ""]
 
 arr[0] = 'something' // ["something", "", "", "", ""]
 ```
 
+
+
+
 ### Схема GraphQL
 
 Это не прямое изменение AssemblyScript, но Вам, возможно, придется обновить файл `schema.graphql`.
 
 Теперь Вы больше не можете определять поля в своих типах, которые являются списками, не допускающими значение NULL. Если у Вас такая схема:
 
+
+
 ```graphql
 type Something @entity {
   id: Bytes!
@@ -498,8 +640,11 @@ type MyEntity @entity {
 }
 ```
 
+
 Вам нужно добавить `!` к элементу типа List, например, так:
 
+
+
 ```graphql
 type Something @entity {
   id: Bytes!
@@ -511,8 +656,11 @@ type MyEntity @entity {
 }
 ```
 
+
 Изменение произошло из-за различий в допустимости значений NULL между версиями AssemblyScript и связано с файлом `src/generated/schema.ts` (путь по умолчанию, возможно, Вы его изменили).
 
+
+
 ### Прочее
 
 - `Map#set` и `Set#add` согласованы со спецификацией, произведён возврат к `this` ([v0.9.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.2))

From 9b449ff713e08dae5fe3ac26c51b8c9a26f45c92 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:50 -0500
Subject: [PATCH 0896/1325] New translations assemblyscript-migration-guide.mdx
 (Swedish)

---
 .../assemblyscript-migration-guide.mdx        | 127 +++++++++---------
 1 file changed, 61 insertions(+), 66 deletions(-)

diff --git a/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx b/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx
index 97c6bb95635a..afa4a7df4747 100644
--- a/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx
@@ -91,17 +91,17 @@ maybeValue.aMethod();
 Men i den nyare versionen, eftersom värdet är nullable, måste du kontrollera, så här:
 
 ```typescript
-let maybeValue = load()
+let maybeValue = load();
 
 if (maybeValue) {
-  maybeValue.aMethod() // `maybeValue` is not null anymore
+  maybeValue.aMethod(); // `maybeValue` is not null anymore
 }
 ```
 
 Eller gör så här:
 
 ```typescript
-let maybeValue = load()! // bryts i runtime om värdet är null
+let maybeValue = load()!; // bryts i runtime om värdet är null
 
 maybeValue.aMethod()
 ```
@@ -113,8 +113,8 @@ Om du är osäker på vilken du ska välja, rekommenderar vi alltid att använda
 Tidigare kunde du använda [variabelskuggning](https://en.wikipedia.org/wiki/Variable_shadowing) och kod som detta skulle fungera:
 
 ```typescript
-let a = 10
-let b = 20
+let a = 10;
+let b = 20;
 let a = a + b
 ```
 
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 Du måste döpa om dina duplicerade variabler om du hade variabelskuggning.
-
 ### Jämförelser med nollvärden
-
 När du gör uppgraderingen av din subgraf kan du ibland få fel som dessa:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 För att lösa problemet kan du helt enkelt ändra `if`-satsen till något i den här stilen:
 
 ```typescript
@@ -158,8 +154,8 @@ Samma gäller om du använder != istället för ==.
 Det vanliga sättet att göra kasting tidigare var att bara använda nyckelordet `as`, som så här:
 
 ```typescript
-let byteArray = new ByteArray(10)
-let uint8Array = byteArray as Uint8Array // motsvarande: <Uint8Array>byteArray
+let byteArray = new ByteArray(10);
+let uint8Array = byteArray as Uint8Array; // motsvarande: <Uint8Array>byteArray
 ```
 
 Detta fungerar dock endast i två scenarier:
@@ -171,8 +167,8 @@ Exempel:
 
 ```typescript
 // primitive casting
-let a: usize = 10
-let b: isize = 5
+let a: usize = 10;
+let b: isize = 5;
 let c: usize = a + (b as usize)
 ```
 
@@ -180,7 +176,7 @@ let c: usize = a + (b as usize)
 // upcasting on class inheritance
 class Bytes extends Uint8Array {}
 
-let bytes = new Bytes(2)
+let bytes = new Bytes(2);
 // <Uint8Array>bytes // same as: bytes as Uint8Array
 ```
 
@@ -193,7 +189,7 @@ Det finns två scenarier där du kan vilja casta, men att använda `as`/`<T>var`
 // downcasting om klassarv
 class Bytes extends Uint8Array {}
 
-let uint8Array = new Uint8Array(2)
+let uint8Array = new Uint8Array(2);
 // <Bytes>uint8Array // breaks in runtime :(
 ```
 
@@ -202,7 +198,7 @@ let uint8Array = new Uint8Array(2)
 class Bytes extends Uint8Array {}
 class ByteArray extends Uint8Array {}
 
-let bytes = new Bytes(2)
+let bytes = new Bytes(2);
 // <ByteArray>bytes // breaks in runtime :(
 ```
 
@@ -212,8 +208,8 @@ I dessa fall kan du använda funktionen `changetype<T>`:
 // downcasting om klassarv
 class Bytes extends Uint8Array {}
 
-let uint8Array = new Uint8Array(2)
-changetype<Bytes>(uint8Array) // works :)
+let uint8Array = new Uint8Array(2);
+changetype<Bytes>(uint8Array); // works :)
 ```
 
 ```typescript
@@ -221,18 +217,18 @@ changetype<Bytes>(uint8Array) // works :)
 class Bytes extends Uint8Array {}
 class ByteArray extends Uint8Array {}
 
-let bytes = new Bytes(2)
-changetype<ByteArray>(bytes) // works :)
+let bytes = new Bytes(2);
+changetype<ByteArray>(bytes); // works :)
 ```
 
 Om du bara vill ta bort nullability kan du fortsätta använda `as`-operatorn (eller `<T>variable`), men se till att du vet att värdet inte kan vara null, annars kommer det att bryta.
 
 ```typescript
 // ta bort ogiltighet
-let previousBalance = AccountBalance.load(balanceId) // AccountBalance | null
+let previousBalance = AccountBalance.load(balanceId); // AccountBalance | null
 
 if (previousBalance != null) {
-  return previousBalance as AccountBalance // safe remove null
+  return previousBalance as AccountBalance; // safe remove null
 }
 
 let newBalance = new AccountBalance(balanceId)
@@ -252,18 +248,18 @@ Vi har också lagt till några fler statiska metoder i vissa typer för att unde
 För att använda [nullability check feature](https://www.assemblyscript.org/basics.html#nullability-checks) kan du använda antingen `if`-satser eller den ternära operatorn (`?` och `:`) så här:
 
 ```typescript
-let something: string | null = 'data'
+let something: string | null = "data";
 
-let somethingOrElse = something ? something : 'else'
+let somethingOrElse = something ? something : "else";
 
 // or
 
-let somethingOrElse
+let somethingOrElse;
 
 if (something) {
-  somethingOrElse = something
+  somethingOrElse = something;
 } else {
-  somethingOrElse = 'else'
+  somethingOrElse = "else";
 }
 ```
 
@@ -274,10 +270,10 @@ class Container {
   data: string | null
 }
 
-let container = new Container()
-container.data = 'data'
+let container = new Container();
+container.data = "data";
 
-let somethingOrElse: string = container.data ? container.data : 'else' // Kompilerar inte
+let somethingOrElse: string = container.data ? container.data : "else"; // Kompilerar inte
 ```
 
 Vilket ger detta fel:
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 För att åtgärda problemet kan du skapa en variabel för den egenskapen så att kompilatorn kan utföra den magiska nollbarhetskontrollen:
 
 ```typescript
@@ -296,12 +291,12 @@ class Container {
   data: string | null
 }
 
-let container = new Container()
-container.data = 'data'
+let container = new Container();
+container.data = "data";
 
-let data = container.data
+let data = container.data;
 
-let somethingOrElse: string = data ? data : 'else' // kompilerar helt okej :)
+let somethingOrElse: string = data ? data : "else"; // kompilerar helt okej :)
 ```
 
 ### Operatörsöverladdning med egenskapsaccess
@@ -310,7 +305,7 @@ Om du försöker summera (till exempel) en nullable typ (från en property acces
 
 ```typescript
 class BigInt extends Uint8Array {
-  @operator('+')
+  @operator("+")
   plus(other: BigInt): BigInt {
     // ...
   }
@@ -320,26 +315,26 @@ class Wrapper {
   public constructor(public n: BigInt | null) {}
 }
 
-let x = BigInt.fromI32(2)
-let y: BigInt | null = null
+let x = BigInt.fromI32(2);
+let y: BigInt | null = null;
 
-x + y // ge kompileringsfel om ogiltighet
+x + y; // ge kompileringsfel om ogiltighet
 
-let wrapper = new Wrapper(y)
+let wrapper = new Wrapper(y);
 
-wrapper.n = wrapper.n + x // ger inte kompileringsfel som det borde
+wrapper.n = wrapper.n + x; // ger inte kompileringsfel som det borde
 ```
 
 Vi har öppnat en fråga om AssemblyScript-kompilatorn för detta, men om du gör den här typen av operationer i dina subgraf-mappningar bör du ändra dem så att de gör en null-kontroll innan den.
 
 ```typescript
-let wrapper = new Wrapper(y)
+let wrapper = new Wrapper(y);
 
 if (!wrapper.n) {
-  wrapper.n = BigInt.fromI32(0)
+  wrapper.n = BigInt.fromI32(0);
 }
 
-wrapper.n = wrapper.n + x // nu är `n` garanterat ett BigInt
+wrapper.n = wrapper.n + x; // nu är `n` garanterat ett BigInt
 ```
 
 ### Initialisering av värde
@@ -347,17 +342,17 @@ wrapper.n = wrapper.n + x // nu är `n` garanterat ett BigInt
 Om du har någon kod som denna:
 
 ```typescript
-var value: Type // null
-value.x = 10
-value.y = 'content'
+var value: Type; // null
+value.x = 10;
+value.y = "content"
 ```
 
 Det kommer att kompilera men brytas vid körning, det händer eftersom värdet inte har initialiserats, så se till att din subgraf har initialiserat sina värden, så här:
 
 ```typescript
-var value = new Type() // initialized
-value.x = 10
-value.y = 'content'
+var value = new Type(); // initialized
+value.x = 10;
+value.y = "content"
 ```
 
 Även om du har nullable properties i en GraphQL-entitet, som denna:
@@ -372,10 +367,10 @@ type Total @entity {
 Och du har en kod som liknar den här:
 
 ```typescript
-let total = Total.load('latest')
+let total = Total.load("latest");
 
 if (total === null) {
-  total = new Total('latest')
+  total = new Total("latest")
 }
 
 total.amount = total.amount + BigInt.fromI32(1)
@@ -384,11 +379,11 @@ total.amount = total.amount + BigInt.fromI32(1)
 Du måste se till att initialisera värdet `total.amount`, för om du försöker komma åt som i den sista raden för summan, kommer det att krascha. Så antingen initialiserar du det först:
 
 ```typescript
-let total = Total.load('latest')
+let total = Total.load("latest")
 
 if (total === null) {
-  total = new Total('latest')
-  total.amount = BigInt.fromI32(0)
+  total = new Total("latest")
+  total.amount = BigInt.fromI32(0);
 }
 
 total.tokens = total.tokens + BigInt.fromI32(1)
@@ -404,10 +399,10 @@ type Total @entity {
 ```
 
 ```typescript
-let total = Total.load('latest')
+let total = Total.load("latest");
 
 if (total === null) {
-  total = new Total('latest') // initierar redan icke-nullställbara egenskaper
+  total = new Total("latest"); // initierar redan icke-nullställbara egenskaper
 }
 
 total.amount = total.amount + BigInt.fromI32(1)
@@ -435,17 +430,17 @@ export class Something {
 // or
 
 export class Something {
-  value: Thing
+  value: Thing;
 
   constructor(value: Thing) {
-    this.value = value
+    this.value = value;
   }
 }
 
 // or
 
 export class Something {
-  value!: Thing
+  value!: Thing;
 }
 ```
 
@@ -454,9 +449,9 @@ export class Something {
 Klassen `Array` accepterar fortfarande ett tal för att initiera längden på listan, men du bör vara försiktig eftersom operationer som `.push` faktiskt ökar storleken istället för att lägga till i början, till exempel:
 
 ```typescript
-let arr = new Array<string>(5) // ["", "", "", "", ""]
+let arr = new Array<string>(5); // ["", "", "", "", ""]
 
-arr.push('something') // ["", "", "", "", "", "something"] // size 6 :(
+arr.push("something"); // ["", "", "", "", "", "something"] // size 6 :(
 ```
 
 Beroende på vilka typer du använder, t.ex. nullable-typer, och hur du kommer åt dem, kan du stöta på ett runtime-fel som det här:
@@ -468,17 +463,17 @@ ERRO Handler skipped due to execution failure, error: Mapping aborted at ~lib/ar
 För att faktiskt trycka i början bör du antingen initiera `Array` med storlek noll, så här:
 
 ```typescript
-let arr = new Array<string>(0) // []
+let arr = new Array<string>(0); // []
 
-arr.push('something') // ["something"]
+arr.push("something"); // ["something"]
 ```
 
 Eller så bör du mutera den via index:
 
 ```typescript
-let arr = new Array<string>(5) // ["", "", "", "", ""]
+let arr = new Array<string>(5); // ["", "", "", "", ""]
 
-arr[0] = 'something' // ["something", "", "", "", ""]
+arr[0] = "something"; // ["something", "", "", "", ""]
 ```
 
 ### GraphQL-schema

From cbe4a9d288263afbf711318b14e964b151afc89f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:51 -0500
Subject: [PATCH 0897/1325] New translations assemblyscript-migration-guide.mdx
 (Turkish)

---
 .../tr/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx
index a8bb2e376807..fd305a2ca624 100644
--- a/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From 07f1dc931862e999aca1ca26998bdf511f5061a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:52 -0500
Subject: [PATCH 0898/1325] New translations assemblyscript-migration-guide.mdx
 (Ukrainian)

---
 .../uk/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx b/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx
index 85f6903a6c69..17224699570d 100644
--- a/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From 0f6bb2e5e8235c5c51362e1df6064eadbfd669f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:54 -0500
Subject: [PATCH 0899/1325] New translations assemblyscript-migration-guide.mdx
 (Chinese Simplified)

---
 .../zh/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx b/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx
index 622bdeef307e..3ff2d318c88f 100644
--- a/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 如果您有变量遮蔽的情况，则需要重命名重名变量。
-
 ### 空值比较
-
 对子图进行升级后，有时您可能会遇到如下错误：
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 要解决此问题，您只需将 `if` 语句更改为如下所示代码：
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 要解决此问题，您可以为该属性访问创建一个变量，以便编译器可以执行可空性检查：
 
 ```typescript

From e6e1aca1f1d1b689bc697b3ea419c766b18fc3ff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:55 -0500
Subject: [PATCH 0900/1325] New translations assemblyscript-migration-guide.mdx
 (Urdu (Pakistan))

---
 .../ur/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx
index 31439d43c505..9c8d0512a4eb 100644
--- a/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 اگر آپ کے پاس متغیر شیڈونگ ہے تو آپ کو اپنے ڈپلیکیٹ متغیرات کا نام تبدیل کرنے کی ضرورت ہوگی.
-
 ### کالعدم موازنہ
-
 اپنے سب گراف پر اپ گریڈ کرنے سے، بعض اوقات آپ کو اس طرح کی غلطیاں مل سکتی ہیں:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 حل کرنے کے لیے آپ صرف `if` اسٹیٹمنٹ کو اس طرح تبدیل کر سکتے ہیں:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 اس مسئلے کو حل کرنے کے لیے، آپ اس پراپرٹی تک رسائی کے لیے ایک متغیر بنا سکتے ہیں تاکہ مرتب کرنے والا منسوخی چیک میجک کر سکے:
 
 ```typescript

From d27af5032b9e34bdb495d7ebfa488135d7f90e03 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:56 -0500
Subject: [PATCH 0901/1325] New translations assemblyscript-migration-guide.mdx
 (Vietnamese)

---
 .../vi/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx b/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx
index 69c36218d8af..8536b657e78a 100644
--- a/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 Bạn sẽ cần đổi tên các biến trùng lặp của mình nếu bạn có che biến.
-
 ### So sánh Null
-
 Bằng cách thực hiện nâng cấp trên subgraph của bạn, đôi khi bạn có thể gặp các lỗi như sau:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 Để giải quyết, bạn có thể chỉ cần thay đổi câu lệnh `if` thành một cái gì đó như sau:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 Để khắc phục sự cố này, bạn có thể tạo một biến cho quyền truy cập thuộc tính đó để trình biên dịch có thể thực hiện phép thuật kiểm tra tính nullability:
 
 ```typescript

From d2700d698aaedb98f0448f171be07cefff80dc67 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:57 -0500
Subject: [PATCH 0902/1325] New translations assemblyscript-migration-guide.mdx
 (Marathi)

---
 .../mr/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx
index a170ebec8cda..2d735415bebb 100644
--- a/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ However now this isn't possible anymore, and the compiler returns this error:
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 You'll need to rename your duplicate variables if you had variable shadowing.
-
 ### Null Comparisons
-
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -288,7 +284,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript

From 3cd15530cf22d0fc965497abce39fd9115ebe536 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:48:58 -0500
Subject: [PATCH 0903/1325] New translations assemblyscript-migration-guide.mdx
 (Hindi)

---
 .../hi/release-notes/assemblyscript-migration-guide.mdx      | 5 -----
 1 file changed, 5 deletions(-)

diff --git a/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx b/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx
index 6bc091a4083a..031b1d2dd195 100644
--- a/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx
@@ -127,11 +127,8 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
 यदि आपके पास वेरिएबल शैडोइंग है, तो आपको अपने डुप्लिकेट वेरिएबल्स का नाम बदलने की आवश्यकता होगी।
-
 ### Null Comparisons
-
 अपने सबग्राफ पर अपग्रेड करने से, कभी-कभी आपको इस तरह की त्रुटियाँ मिल सकती हैं:
 
 ```typescript
@@ -140,7 +137,6 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
 हल करने के लिए आप केवल `if` कथन को कुछ इस तरह से बदल सकते हैं:
 
 ```typescript
@@ -287,7 +283,6 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
 
    let somethingOrElse: string = container.data ? container.data : "else";
 ```
-
 इस समस्या को ठीक करने के लिए, आप उस प्रॉपर्टी एक्सेस के लिए एक वेरिएबल बना सकते हैं ताकि कंपाइलर अशक्तता जांच जादू कर सके:
 
 ```typescript

From bebbeabd7bde3cf4d5542cd2fdfba6b856e379db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:00 -0500
Subject: [PATCH 0904/1325] New translations assemblyscript-migration-guide.mdx
 (Swahili)

---
 .../assemblyscript-migration-guide.mdx        | 519 ++++++++++++++++++
 1 file changed, 519 insertions(+)
 create mode 100644 website/pages/sw/release-notes/assemblyscript-migration-guide.mdx

diff --git a/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx b/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx
new file mode 100644
index 000000000000..17224699570d
--- /dev/null
+++ b/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx
@@ -0,0 +1,519 @@
+---
+title: AssemblyScript Migration Guide
+---
+
+Up until now, subgraphs have been using one of the [first versions of AssemblyScript](https://github.com/AssemblyScript/assemblyscript/tree/v0.6) (v0.6). Finally we've added support for the [newest one available](https://github.com/AssemblyScript/assemblyscript/tree/v0.19.10) (v0.19.10)! 🎉
+
+That will enable subgraph developers to use newer features of the AS language and standard library.
+
+This guide is applicable for anyone using `graph-cli`/`graph-ts` below version `0.22.0`. If you're already at a higher than (or equal) version to that, you've already been using version `0.19.10` of AssemblyScript 🙂
+
+> Note: As of `0.24.0`, `graph-node` can support both versions, depending on the `apiVersion` specified in the subgraph manifest.
+
+## Features
+
+### New functionality
+
+- `TypedArray`s can now be built from `ArrayBuffer`s by using the [new `wrap` static method](https://www.assemblyscript.org/stdlib/typedarray.html#static-members) ([v0.8.1](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.8.1))
+- New standard library functions: `String#toUpperCase`, `String#toLowerCase`, `String#localeCompare`and `TypedArray#set` ([v0.9.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.0))
+- Added support for x instanceof GenericClass ([v0.9.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.2))
+- Added `StaticArray<T>`, a more efficient array variant ([v0.9.3](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.3))
+- Added `Array<T>#flat` ([v0.10.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.0))
+- Implemented `radix` argument on `Number#toString` ([v0.10.1](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.1))
+- Added support for separators in floating point literals ([v0.13.7](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.13.7))
+- Added support for first class functions ([v0.14.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.14.0))
+- Add builtins: `i32/i64/f32/f64.add/sub/mul` ([v0.14.13](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.14.13))
+- Implement `Array/TypedArray/String#at` ([v0.18.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.2))
+- Added support for template literal strings ([v0.18.17](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.17))
+- Add `encodeURI(Component)` and `decodeURI(Component)` ([v0.18.27](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.27))
+- Add `toString`, `toDateString` and `toTimeString` to `Date` ([v0.18.29](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.29))
+- Add `toUTCString` for `Date` ([v0.18.30](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.30))
+- Add `nonnull/NonNullable` builtin type ([v0.19.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.19.2))
+
+### Optimizations
+
+- `Math` functions such as `exp`, `exp2`, `log`, `log2` and `pow` have been replaced by faster variants ([v0.9.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.0))
+- Slightly optimize `Math.mod` ([v0.17.1](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.17.1))
+- Cache more field accesses in std Map and Set ([v0.17.8](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.17.8))
+- Optimize for powers of two in `ipow32/64` ([v0.18.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.2))
+
+### Other
+
+- The type of an array literal can now be inferred from its contents ([v0.9.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.0))
+- Updated stdlib to Unicode 13.0.0 ([v0.10.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.0))
+
+## How to upgrade?
+
+1. Change your mappings `apiVersion` in `subgraph.yaml` to `0.0.6`:
+
+```yaml
+...
+dataSources:
+  ...
+    mapping:
+      ...
+      apiVersion: 0.0.6
+      ...
+```
+
+2. Update the `graph-cli` you're using to the `latest` version by running:
+
+```bash
+# if you have it globally installed
+npm install --global @graphprotocol/graph-cli@latest
+
+# or in your subgraph if you have it as a dev dependency
+npm install --save-dev @graphprotocol/graph-cli@latest
+```
+
+3. Do the same for `graph-ts`, but instead of installing globally, save it in your main dependencies:
+
+```bash
+npm install --save @graphprotocol/graph-ts@latest
+```
+
+4. Follow the rest of the guide to fix the language breaking changes.
+5. Run `codegen` and `deploy` again.
+
+## Breaking changes
+
+### Nullability
+
+On the older version of AssemblyScript, you could create code like this:
+
+```typescript
+function load(): Value | null { ... }
+
+let maybeValue = load();
+maybeValue.aMethod();
+```
+
+However on the newer version, because the value is nullable, it requires you to check, like this:
+
+```typescript
+let maybeValue = load()
+
+if (maybeValue) {
+  maybeValue.aMethod() // `maybeValue` is not null anymore
+}
+```
+
+Or force it like this:
+
+```typescript
+let maybeValue = load()! // breaks in runtime if value is null
+
+maybeValue.aMethod()
+```
+
+If you are unsure which to choose, we recommend always using the safe version. If the value doesn't exist you might want to just do an early if statement with a return in you subgraph handler.
+
+### Variable Shadowing
+
+Before you could do [variable shadowing](https://en.wikipedia.org/wiki/Variable_shadowing) and code like this would work:
+
+```typescript
+let a = 10
+let b = 20
+let a = a + b
+```
+
+However now this isn't possible anymore, and the compiler returns this error:
+
+```typescript
+ERROR TS2451: Cannot redeclare block-scoped variable 'a'
+
+ let a = a + b;
+ ~~~~~~~~~~~~~
+in assembly/index.ts(4,3)
+```
+You'll need to rename your duplicate variables if you had variable shadowing.
+### Null Comparisons
+By doing the upgrade on your subgraph, sometimes you might get errors like these:
+
+```typescript
+ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' is not assignable to type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt'.
+     if (decimals == null) {
+                     ~~~~
+ in src/mappings/file.ts(41,21)
+```
+To solve you can simply change the `if` statement to something like this:
+
+```typescript
+  if (!decimals) {
+
+  // or
+
+  if (decimals === null) {
+```
+
+The same applies if you're doing != instead of ==.
+
+### Casting
+
+The common way to do casting before was to just use the `as` keyword, like this:
+
+```typescript
+let byteArray = new ByteArray(10)
+let uint8Array = byteArray as Uint8Array // equivalent to: <Uint8Array>byteArray
+```
+
+However this only works in two scenarios:
+
+- Primitive casting (between types such as `u8`, `i32`, `bool`; eg: `let b: isize = 10; b as usize`);
+- Upcasting on class inheritance (subclass → superclass)
+
+Examples:
+
+```typescript
+// primitive casting
+let a: usize = 10
+let b: isize = 5
+let c: usize = a + (b as usize)
+```
+
+```typescript
+// upcasting on class inheritance
+class Bytes extends Uint8Array {}
+
+let bytes = new Bytes(2)
+// <Uint8Array>bytes // same as: bytes as Uint8Array
+```
+
+There are two scenarios where you may want to cast, but using `as`/`<T>var` **isn't safe**:
+
+- Downcasting on class inheritance (superclass → subclass)
+- Between two types that share a superclass
+
+```typescript
+// downcasting on class inheritance
+class Bytes extends Uint8Array {}
+
+let uint8Array = new Uint8Array(2)
+// <Bytes>uint8Array // breaks in runtime :(
+```
+
+```typescript
+// between two types that share a superclass
+class Bytes extends Uint8Array {}
+class ByteArray extends Uint8Array {}
+
+let bytes = new Bytes(2)
+// <ByteArray>bytes // breaks in runtime :(
+```
+
+For those cases, you can use the `changetype<T>` function:
+
+```typescript
+// downcasting on class inheritance
+class Bytes extends Uint8Array {}
+
+let uint8Array = new Uint8Array(2)
+changetype<Bytes>(uint8Array) // works :)
+```
+
+```typescript
+// between two types that share a superclass
+class Bytes extends Uint8Array {}
+class ByteArray extends Uint8Array {}
+
+let bytes = new Bytes(2)
+changetype<ByteArray>(bytes) // works :)
+```
+
+If you just want to remove nullability, you can keep using the `as` operator (or `<T>variable`), but make sure you know that value can't be null, otherwise it will break.
+
+```typescript
+// remove nullability
+let previousBalance = AccountBalance.load(balanceId) // AccountBalance | null
+
+if (previousBalance != null) {
+  return previousBalance as AccountBalance // safe remove null
+}
+
+let newBalance = new AccountBalance(balanceId)
+```
+
+For the nullability case we recommend taking a look at the [nullability check feature](https://www.assemblyscript.org/basics.html#nullability-checks), it will make your code cleaner 🙂
+
+Also we've added a few more static methods in some types to ease casting, they are:
+
+- Bytes.fromByteArray
+- Bytes.fromUint8Array
+- BigInt.fromByteArray
+- ByteArray.fromBigInt
+
+### Nullability check with property access
+
+To use the [nullability check feature](https://www.assemblyscript.org/basics.html#nullability-checks) you can use either `if` statements or the ternary operator (`?` and `:`) like this:
+
+```typescript
+let something: string | null = 'data'
+
+let somethingOrElse = something ? something : 'else'
+
+// or
+
+let somethingOrElse
+
+if (something) {
+  somethingOrElse = something
+} else {
+  somethingOrElse = 'else'
+}
+```
+
+However that only works when you're doing the `if` / ternary on a variable, not on a property access, like this:
+
+```typescript
+class Container {
+  data: string | null
+}
+
+let container = new Container()
+container.data = 'data'
+
+let somethingOrElse: string = container.data ? container.data : 'else' // doesn't compile
+```
+
+Which outputs this error:
+
+```typescript
+ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/string/String'.
+
+   let somethingOrElse: string = container.data ? container.data : "else";
+                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+```
+To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
+
+```typescript
+class Container {
+  data: string | null
+}
+
+let container = new Container()
+container.data = 'data'
+
+let data = container.data
+
+let somethingOrElse: string = data ? data : 'else' // compiles just fine :)
+```
+
+### Operator overloading with property access
+
+If you try to sum (for example) a nullable type (from a property access) with a non nullable one, the AssemblyScript compiler instead of giving a compile time error warning that one of the values is nullable, it just compiles silently, giving chance for the code to break at runtime.
+
+```typescript
+class BigInt extends Uint8Array {
+  @operator('+')
+  plus(other: BigInt): BigInt {
+    // ...
+  }
+}
+
+class Wrapper {
+  public constructor(public n: BigInt | null) {}
+}
+
+let x = BigInt.fromI32(2)
+let y: BigInt | null = null
+
+x + y // give compile time error about nullability
+
+let wrapper = new Wrapper(y)
+
+wrapper.n = wrapper.n + x // doesn't give compile time errors as it should
+```
+
+We've opened a issue on the AssemblyScript compiler for this, but for now if you do these kind of operations in your subgraph mappings, you should change them to do a null check before it.
+
+```typescript
+let wrapper = new Wrapper(y)
+
+if (!wrapper.n) {
+  wrapper.n = BigInt.fromI32(0)
+}
+
+wrapper.n = wrapper.n + x // now `n` is guaranteed to be a BigInt
+```
+
+### Value initialization
+
+If you have any code like this:
+
+```typescript
+var value: Type // null
+value.x = 10
+value.y = 'content'
+```
+
+It will compile but break at runtime, that happens because the value hasn't been initialized, so make sure your subgraph has initialized their values, like this:
+
+```typescript
+var value = new Type() // initialized
+value.x = 10
+value.y = 'content'
+```
+
+Also if you have nullable properties in a GraphQL entity, like this:
+
+```graphql
+type Total @entity {
+  id: Bytes!
+  amount: BigInt
+}
+```
+
+And you have code similar to this:
+
+```typescript
+let total = Total.load('latest')
+
+if (total === null) {
+  total = new Total('latest')
+}
+
+total.amount = total.amount + BigInt.fromI32(1)
+```
+
+You'll need to make sure to initialize the `total.amount` value, because if you try to access like in the last line for the sum, it will crash. So you either initialize it first:
+
+```typescript
+let total = Total.load('latest')
+
+if (total === null) {
+  total = new Total('latest')
+  total.amount = BigInt.fromI32(0)
+}
+
+total.tokens = total.tokens + BigInt.fromI32(1)
+```
+
+Or you can just change your GraphQL schema to not use a nullable type for this property, then we'll initialize it as zero on the `codegen` step 😉
+
+```graphql
+type Total @entity {
+  id: Bytes!
+  amount: BigInt!
+}
+```
+
+```typescript
+let total = Total.load('latest')
+
+if (total === null) {
+  total = new Total('latest') // already initializes non-nullable properties
+}
+
+total.amount = total.amount + BigInt.fromI32(1)
+```
+
+### Class property initialization
+
+If you export any classes with properties that are other classes (declared by you or by the standard library) like this:
+
+```typescript
+class Thing {}
+
+export class Something {
+  value: Thing
+}
+```
+
+The compiler will error because you either need to add an initializer for the properties that are classes, or add the `!` operator:
+
+```typescript
+export class Something {
+  constructor(public value: Thing) {}
+}
+
+// or
+
+export class Something {
+  value: Thing
+
+  constructor(value: Thing) {
+    this.value = value
+  }
+}
+
+// or
+
+export class Something {
+  value!: Thing
+}
+```
+
+### Array initialization
+
+The `Array` class still accepts a number to initialize the length of the list, however you should take care because operations like `.push` will actually increase the size instead of adding to the beginning, for example:
+
+```typescript
+let arr = new Array<string>(5) // ["", "", "", "", ""]
+
+arr.push('something') // ["", "", "", "", "", "something"] // size 6 :(
+```
+
+Depending on the types you're using, eg nullable ones, and how you're accessing them, you might encounter a runtime error like this one:
+
+```
+ERRO Handler skipped due to execution failure, error: Mapping aborted at ~lib/array.ts, line 110, column 40, with message: Element type must be nullable if array is holey  wasm backtrace:     0: 0x19c4 - <unknown>!~lib/@graphprotocol/graph-ts/index/format         1: 0x1e75 - <unknown>!~lib/@graphprotocol/graph-ts/common/collections/Entity#constructor        2: 0x30b9 - <unknown>!node_modules/@graphprotocol/graph-ts/global/global/id_of_type
+```
+
+To actually push at the beginning you should either, initialize the `Array` with size zero, like this:
+
+```typescript
+let arr = new Array<string>(0) // []
+
+arr.push('something') // ["something"]
+```
+
+Or you should mutate it via index:
+
+```typescript
+let arr = new Array<string>(5) // ["", "", "", "", ""]
+
+arr[0] = 'something' // ["something", "", "", "", ""]
+```
+
+### GraphQL schema
+
+This is not a direct AssemblyScript change, but you may have to update your `schema.graphql` file.
+
+Now you no longer can define fields in your types that are Non-Nullable Lists. If you have a schema like this:
+
+```graphql
+type Something @entity {
+  id: Bytes!
+}
+
+type MyEntity @entity {
+  id: Bytes!
+  invalidField: [Something]! # no longer valid
+}
+```
+
+You'll have to add an `!` to the member of the List type, like this:
+
+```graphql
+type Something @entity {
+  id: Bytes!
+}
+
+type MyEntity @entity {
+  id: Bytes!
+  invalidField: [Something!]! # valid
+}
+```
+
+This changed because of nullability differences between AssemblyScript versions, and it's related to the `src/generated/schema.ts` file (default path, you might have changed this).
+
+### Other
+
+- Aligned `Map#set` and `Set#add` with the spec, returning `this` ([v0.9.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.2))
+- Arrays no longer inherit from ArrayBufferView, but are now distinct ([v0.10.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.0))
+- Classes initialized from object literals can no longer define a constructor ([v0.10.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.0))
+- The result of a `**` binary operation is now the common denominator integer if both operands are integers. Previously, the result was a float as if calling `Math/f.pow` ([v0.11.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.11.0))
+- Coerce `NaN` to `false` when casting to `bool` ([v0.14.9](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.14.9))
+- When shifting a small integer value of type `i8`/`u8` or `i16`/`u16`, only the 3 respectively 4 least significant bits of the RHS value affect the result, analogous to the result of an `i32.shl` only being affected by the 5 least significant bits of the RHS value. Example: `someI8 << 8` previously produced the value `0`, but now produces `someI8` due to masking the RHS as `8 & 7 = 0` (3 bits) ([v0.17.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.17.0))
+- Bug fix of relational string comparisons when sizes differ ([v0.17.8](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.17.8))

From 6a79ced625d7c8f6b3071f37d1155a5f6aeea836 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:01 -0500
Subject: [PATCH 0905/1325] New translations billing.mdx (Romanian)

---
 website/pages/ro/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ro/billing.mdx b/website/pages/ro/billing.mdx
index 37f9c840d00b..dec5cfdadc12 100644
--- a/website/pages/ro/billing.mdx
+++ b/website/pages/ro/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From b04ddcd04c9448469875ce51673dd9da9b87b794 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:02 -0500
Subject: [PATCH 0906/1325] New translations billing.mdx (French)

---
 website/pages/fr/billing.mdx | 250 +++++++++++++++++------------------
 1 file changed, 125 insertions(+), 125 deletions(-)

diff --git a/website/pages/fr/billing.mdx b/website/pages/fr/billing.mdx
index cb3b4c99bb2b..610c9ff09b00 100644
--- a/website/pages/fr/billing.mdx
+++ b/website/pages/fr/billing.mdx
@@ -2,173 +2,173 @@
 title: Facturation
 ---
 
-## Subgraph Billing Plans
+## Les Plans de Facturation des Subgraphs
 
-There are two plans to use when querying subgraphs on The Graph Network.
+Il y a deux plans à utiliser lorsqu'on interroge les subgraphs sur le réseau de The Graph.
 
-- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling their dapp.
+- **Le Plan Gratuit**: Le Plan Gratuit comprend 100,000 requêtes mensuelles gratuites avec un accès complet à l'environnement de test de Subgraph Studio. Ce plan est conçu pour les amateurs, les participants aux hackathons et ceux qui ont des projets annexes pour essayer The Graph avant de faire évoluer leur dApp.
 
-- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card. The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+- **Plan de croissance**: Le plan de croissance comprend tout ce qui est inclus dans le plan gratuit avec toutes les requêtes après 100 000 requêtes mensuelles nécessitant des paiements en GRT ou par carte de crédit. Le plan de croissance est suffisamment flexible pour couvrir les besoins des équipes qui ont établi des dapps à dans une variété de cas d'utilisation.
 
 <VideoEmbed youtube="Nn771WagX2I" />
 
-## Query Payments with credit card
+## Paiements de Requêtes avec Carte de Crédit⁠
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
-  1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-  2. Cliquez sur le bouton « Connecter le portefeuille » dans le coin supérieur droit de la page. Vous serez redirigé vers la page de sélection du portefeuille. Sélectionnez votre portefeuille et cliquez sur "Connecter".
-  3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
-  4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details.
-- Invoices will be processed at the end of each month and require an active credit card on file for all queries beyond the free plan quota.
+- Pour mettre en place la facturation par carte de crédit/débit, les utilisateurs doivent accéder à Subgraph Studio (https://thegraph.com/studio/)
+  1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/billing/).
+  2. Cliquez sur le bouton "Connecter le portefeuille" dans le coin supérieur droit de la page. Vous serez redirigé vers la page de sélection des portefeuilles. Sélectionnez votre portefeuille et cliquez sur "Connecter".
+  3. Choisissez « Mettre à niveau votre abonnement » si vous effectuez une mise à niveau depuis le plan gratuit, ou choisissez « Gérer l'abonnement » si vous avez déjà ajouté des GRT à votre solde de facturation par le passé. Ensuite, vous pouvez estimer le nombre de requêtes pour obtenir une estimation du prix, mais ce n'est pas une étape obligatoire.
+  4. Pour choisir un paiement par carte de crédit, choisissez “Credit card” comme mode de paiement et remplissez les informations de votre carte de crédit. Ceux qui ont déjà utilisé Stripe peuvent utiliser la fonctionnalité Link pour remplir automatiquement leurs informations.
+- Les factures seront traitées à la fin de chaque mois et nécessitent une carte de crédit valide enregistrée sur votre compte pour toute requête au-delà du quota du plan gratuit.
 
-## Query Payments with GRT
+## Paiements de Requêtes avec du GRT
 
-Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph Network. With GRT, invoices will be processed at the end of each month and require a sufficient balance of GRT to make queries beyond the Free Plan quota of 100,000 monthly queries. You'll be required to pay fees generated from your API keys. Using the billing contract, you'll be able to:
+Les utilisateurs de subgraphs peuvent utiliser le jeton natif de The Graph (GRT) pour payer les requêtes sur le réseau The Graph. Avec le GRT, les factures seront traitées à la fin de chaque mois et nécessiteront un solde suffisant de GRT pour effectuer des requêtes au-delà du quota du plan gratuit de 100 000 requêtes mensuelles. Vous devrez payer les frais générés par vos clés API. En utilisant le contrat de facturation, vous pourrez :
 
 - Ajoutez et retirez du GRT du solde de votre compte.
 - Gardez une trace de vos soldes en fonction du montant de GRT que vous avez ajouté au solde de votre compte, du montant que vous avez supprimé et de vos factures.
 - Payez automatiquement les factures en fonction des frais de requête générés, à condition qu'il y ait suffisamment de GRT dans le solde de votre compte.
 
-### GRT on Arbitrum or Ethereum
+### GRT sur Arbitrum ou Ethereum
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+Le système de facturation de The Graph accepte le GRT sur Arbitrum, et les utilisateurs devront disposer d'ETH sur Arbitrum pour payer le gaz. Bien que le protocole The Graph ait commencé sur le réseau principal d'Ethereum, toutes les activités, y compris les contrats de facturation, sont désormais réalisées sur Arbitrum One.
 
-To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+L'utilisation du GRT sur Arbitrum est nécessaire pour le paiement des requêtes. Voici quelques options pour en acquérir :
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Si vous avez déjà des GRT sur Ethereum, vous pouvez les transférer vers Arbitrum. Vous pouvez le faire via l'option de transfert de GRT fournie dans Subgraph Studio ou en utilisant l'un des ponts suivants :
 
-- [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+- [Le pont Arbitrum](https://bridge.arbitrum.io/?l2ChainId=42161)
 - [TransferTo](https://transferto.xyz/swap)
 
-- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap.
+- Si vous possédez déjà des actifs sur Arbitrum, vous pouvez les échanger contre du GRT via un protocole d'échange comme Uniswap.
 
-- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange.
+- Alternativement, vous pouvez acquérir du GRT directement sur Arbitrum via un échange décentralisé.
 
-> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
+> Cette section est rédigée en supposant que vous avez déjà des GRT dans votre portefeuille et que vous êtes sur Arbitrum. Si vous n'avez pas de GRT, vous pouvez apprendre comment obtenir des GRT [ici](#getting-grt).
 
-Once you bridge GRT, you can add it to your billing balance.
+Une fois que vous avez transféré du GRT, vous pouvez l'ajouter à votre solde de facturation.
 
-### Adding GRT using a wallet
+### Ajout de GRT à l'aide d'un portefeuille
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Cliquez sur le bouton « Connecter le portefeuille » dans le coin supérieur droit de la page. Vous serez redirigé vers la page de sélection du portefeuille. Sélectionnez votre portefeuille et cliquez sur "Connecter".
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable.
-8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-9. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/billing/).
+2. Cliquez sur le bouton "Connecter le portefeuille" dans le coin supérieur droit de la page. Vous serez redirigé vers la page de sélection des portefeuilles. Sélectionnez votre portefeuille et cliquez sur "Connecter".
+3. Cliquez sur le bouton « Manage » situé dans le coin supérieur droit. Les nouveaux utilisateurs verront l'option « Upgrade to Growth plan » (Passer au plan de croissance), tandis que les utilisateurs existants devront sélectionner « Deposit from wallet » (Déposer depuis le portefeuille).
+4. Utilisez le curseur pour estimer le nombre de requêtes que vous prévoyez d’effectuer sur une base mensuelle.
+   - Pour des suggestions sur le nombre de requêtes que vous pouvez utiliser, consultez notre page **Foire aux questions**.
+5. Choisissez "Cryptocurrency". Le GRT est actuellement la seule cryptomonnaie acceptée sur le réseau The Graph.
+6. Sélectionnez le nombre de mois pour lesquels vous souhaitez effectuer un paiement anticipé.
+   - Le paiement anticipé ne vous engage pas sur une utilisation future. Vous ne serez facturé que pour ce que vous utiliserez et vous pourrez retirer votre solde à tout moment.
+7. Choisissez le réseau à partir duquel vous déposez vos GRT. Les GRT sur Arbitrum ou Ethereum sont tous deux acceptables.
+8. Cliquez sur "Autoriser l'accès au GRT" puis spécifiez le montant de GRT qui peut être prélevé de votre portefeuille.
+   - Si vous payez à l'avance pour plusieurs mois, vous devez autoriser l'accès au montant correspondant. Cette interaction ne coûtera aucun gaz.
+9. Enfin, cliquez sur « Add GRT to Billing Balance ». Cette transaction nécessitera des ETH sur Arbitrum pour couvrir les coûts du gaz.
 
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+- Notez que les GRT déposés depuis Arbitrum seront traités en quelques instants tandis que les GRT déposés depuis Ethereum prendront environ 15-20 minutes pour être traités. Une fois la transaction confirmée, vous verrez les GRT ajoutés à votre solde de compte.
 
-### Withdrawing GRT using a wallet
+### Retirer des GRT en utilisant un portefeuille
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
-4. Enter the amount of GRT you would like to withdraw.
-5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
-6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
+1. Accédez à la [page de facturation de Subgraph Studio](https://thegraph.com/studio/billing/).
+2. Cliquez sur le bouton "Connect Wallet" dans le coin supérieur droit de la page. Sélectionnez votre portefeuille et cliquez sur "Connect".
+3. Cliquez sur le bouton « Gérer » dans le coin supérieur droit de la page. Sélectionnez « Retirer des GRT ». Un panneau latéral apparaîtra.
+4. Entrez le montant de GRT que vous voudriez retirer.
+5. Cliquez 'Withdraw GRT' pour retirer les GRT de votre solde de compte. Signez la transaction associée dans votre portefeuille. Cela coûtera du gaz. Les GRT seront envoyés à votre portefeuille Arbitrum.
+6. Une fois que la transaction est confirmée, vous verrez le GRT qu'on a retiré de votre solde du compte dans votre portefeuille Arbitrum.
 
 ### Ajout de GRT à l'aide d'un portefeuille multisig
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas.
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+1. Allez à la page [Facturation de Studio Subgraph](https://thegraph.com/studio/billing/).
+2. Cliquez sur le bouton "Connect Wallet" dans le coin supérieur droit de la page. Sélectionnez votre portefeuille et cliquez sur "Connect". Si vous utilisez [Gnosis-Safe](https://gnosis-safe.io/), vous pourrez connecter votre multisig ainsi que votre portefeuille de signature. Ensuite, signez le message associé. Cela ne coûtera aucun gaz.
+3. Cliquez sur le bouton « Manage » situé dans le coin supérieur droit. Les nouveaux utilisateurs verront l'option « Upgrade to Growth plan » (Passer au plan de croissance), tandis que les utilisateurs existants devront sélectionner « Deposit from wallet » (Déposer depuis le portefeuille).
+4. Utilisez le curseur pour estimer le nombre de requêtes que vous prévoyez d’effectuer sur une base mensuelle.
+   - Pour des suggestions sur le nombre de requêtes que vous pouvez utiliser, consultez notre page **Foire aux questions**.
+5. Choisissez "Cryptocurrency". Le GRT est actuellement la seule cryptomonnaie acceptée sur le réseau The Graph.
+6. Sélectionnez le nombre de mois pour lesquels vous souhaitez effectuer un paiement anticipé.
+   - Le paiement anticipé ne vous engage pas sur une utilisation future. Vous ne serez facturé que pour ce que vous utiliserez et vous pourrez retirer votre solde à tout moment.
+7. Choisissez le réseau à partir duquel vous déposez vos GRT. Les GRT sur Arbitrum ou Ethereum, les deux sont acceptables. 8. Cliquez sur "Allow GRT Access", et puis spécifiez le montant de GRT qui peut être prélevé de votre portefeuille.
+   - Si vous payez à l'avance pour plusieurs mois, vous devez autoriser l'accès au montant correspondant. Cette interaction ne coûtera aucun gaz.
+8. Enfin, cliquez sur « Add GRT to Billing Balance ». Cette transaction nécessitera des ETH sur Arbitrum pour couvrir les coûts du gaz.
 
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+- Notez que les GRT déposés depuis Arbitrum seront traités en quelques instants tandis que les GRT déposés depuis Ethereum prendront environ 15-20 minutes pour être traités. Une fois la transaction confirmée, vous verrez les GRT ajoutés à votre solde de compte.
 
-## Getting GRT
+## Obtenir du GRT
 
-This section will show you how to get GRT to pay for query fees.
+Cette section vous montrera comment obtenir du GRT pour payer les frais de requête.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing GRT on Coinbase.
+Voici un guide étape par étape pour acheter de GRT sur Coinbase.
 
-1. Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page.
-4. Select the currency you want to purchase. Select GRT.
-5. Select the payment method. Select your preferred payment method.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase. Review your purchase and click "Buy GRT".
-8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT.
-9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page.
-   - Click on the "Send" button next to the GRT account.
-   - Enter the amount of GRT you want to send and the wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction. -Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet.
+1. Accédez à [Coinbase](https://www.coinbase.com/) et créez un compte.
+2. Dès que vous aurez créé un compte, vous devrez vérifier votre identité par le biais d'un processus connu sous le nom de KYC (Know Your Customer ou Connaître Votre Client). Il s'agit d'une procédure standard pour toutes les plateformes d'échange de crypto-monnaies centralisées ou dépositaires.
+3. Une fois votre identité vérifiée, vous pouvez acheter des GRT. Pour ce faire, cliquez sur le bouton « Acheter/Vendre » en haut à droite de la page.
+4. Sélectionnez la devise que vous souhaitez acheter. Sélectionnez GRT.
+5. Sélectionnez le mode de paiement. Sélectionnez votre mode de paiement préféré.
+6. Sélectionnez la quantité de GRT que vous souhaitez acheter.
+7. Vérifiez votre achat. Vérifiez votre achat et cliquez sur "Buy GRT".
+8. Confirmez votre achat. Confirmez votre achat et vous aurez acheté des GRT avec succès.
+9. Vous pouvez transférer les GRT de votre compte vers votre portefeuille tel que [MetaMask](https://metamask.io/).
+   - Pour transférer les GRT dans votre portefeuille, cliquez sur le bouton "Accounts" en haut à droite de la page.
+   - Cliquez sur le bouton "Send" à côté du compte GRT.
+   - Entrez le montant de GRT que vous souhaitez envoyer et l'adresse du portefeuille vers laquelle vous souhaitez l'envoyer.
+   - Cliquez sur "Continue" et confirmez votre transaction. -Veuillez noter que pour des montants d'achat plus importants, Coinbase peut vous demander d'attendre 7 à 10 jours avant de transférer le montant total vers un portefeuille.
 
-You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+Vous pouvez en savoir plus sur l'obtention de GRT sur Coinbase [ici](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
 
 ### Binance
 
-This will be a step by step guide for purchasing GRT on Binance.
+Ceci est un guide étape par étape pour l'achat des GRT sur Binance.
 
-1. Go to [Binance](https://www.binance.com/en) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner.
-4. You will be taken to a page where you can select the currency you want to purchase. Select GRT.
-5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase and click "Buy GRT".
-8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
-9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
-   - Click on the "wallet" button, click withdraw, and select GRT.
-   - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction.
+1. Allez sur [Binance](https://www.binance.com/en) et créez un compte.
+2. Dès que vous aurez créé un compte, vous devrez vérifier votre identité par le biais d'un processus connu sous le nom de KYC (Know Your Customer ou Connaître Votre Client). Il s'agit d'une procédure standard pour toutes les plateformes d'échange de crypto-monnaies centralisées ou dépositaires.
+3. Une fois votre identité vérifiée, vous pouvez acheter des GRT. Pour ce faire, cliquez sur le bouton « Acheter maintenant » sur la bannière de la page d'accueil.
+4. Vous accéderez à une page où vous pourrez sélectionner la devise que vous souhaitez acheter. Sélectionnez GRT.
+5. Choisissez votre mode de paiement préféré. Vous pourrez payer avec différentes devises fiduciaires telles que l'euro, le dollar américain, etc.
+6. Sélectionnez la quantité de GRT que vous souhaitez acheter.
+7. Confirmez votre achat et cliquez sur « Acheter des GRT ».
+8. Confirmez votre achat et vous pourrez voir vos GRT dans votre portefeuille Binance Spot.
+9. Vous pouvez retirer les GRT de votre compte vers votre portefeuille tel que [MetaMask](https://metamask.io/).
+   - [Pour retirer](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) des GRT dans votre portefeuille, ajoutez l'adresse de votre portefeuille à la liste blanche des retraits.
+   - Cliquez sur le bouton « portefeuille », cliquez sur retrait et sélectionnez GRT.
+   - Saisissez le montant de GRT que vous souhaitez envoyer et l'adresse du portefeuille sur liste blanche à laquelle vous souhaitez l'envoyer.
+   - Cliquer sur « Continuer » et confirmez votre transaction.
 
-You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+Vous pouvez en savoir plus sur l'obtention de GRT sur Binance [ici](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
 
 ### Uniswap
 
-This is how you can purchase GRT on Uniswap.
+Voici comment vous pouvez acheter des GRT sur Uniswap.
 
-1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet.
-2. Select the token you want to swap from. Select ETH.
-3. Select the token you want to swap to. Select GRT.
-   - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
-4. Enter the amount of ETH you want to swap.
-5. Click "Swap".
-6. Confirm the transaction in your wallet and you wait for the transaction to process.
+1. Accédez à [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) et connectez votre portefeuille.
+2. Sélectionnez le jeton dont vous souhaitez échanger. Sélectionnez ETH.
+3. Sélectionnez le jeton vers lequel vous souhaitez échanger. Sélectionnez GRT.
+   - Assurez-vous que vous échangez contre le bon jeton. L'adresse du contrat intelligent GRT sur Arbitrum One est la suivante : [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+4. Entrez le montant d'ETH que vous souhaitez échanger.
+5. Cliquez sur « Échanger ».
+6. Confirmez la transaction dans votre portefeuille et attendez qu'elle soit traitée.
 
-You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
+Vous pouvez en savoir plus sur l'obtention de GRT sur Uniswap [ici](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
 
-## Getting Ether
+## Obtenir de l'Ether⁠
 
-This section will show you how to get Ether (ETH) to pay for transaction fees or gas costs. ETH is necessary to execute operations on the Ethereum network such as transferring tokens or interacting with contracts.
+Cette section vous montrera comment obtenir de l'Ether (ETH) pour payer les frais de transaction ou les coûts de gaz. L'ETH est nécessaire pour exécuter des opérations sur le réseau Ethereum telles que le transfert de jetons ou l'interaction avec des contrats.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing ETH on Coinbase.
-
-1.  Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3.  Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
-8.  Confirm your purchase and you will have successfully purchased ETH.
-9.  You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/).
-    - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page.
-    - Click on the "Send" button next to the ETH account.
-    - Enter the amount of ETH you want to send and the wallet address you want to send it to.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
+Ce sera un guide étape par étape pour acheter de l'ETH sur Coinbase.
+
+1.  Accédez à [Coinbase](https://www.coinbase.com/) et créez un compte.
+2.  Une fois que vous avez créé un compte, vérifiez votre identité via un processus appelé KYC (ou Know Your Customer). l s'agit d'une procédure standard pour toutes les plateformes d'échange de crypto-monnaies centralisées ou dépositaires.
+3.  Une fois que vous avez vérifié votre identité, achetez de l'ETH en cliquant sur le bouton « Acheter/Vendre » en haut à droite de la page.
+4.  Choisissez la devise que vous souhaitez acheter. Sélectionnez ETH.
+5.  Sélectionnez votre mode de paiement préféré.
+6.  Entrez le montant d'ETH que vous souhaitez acheter.
+7.  Vérifiez votre achat et cliquez sur « Acheter des Ethereum ».
+8.  Confirmez votre achat et vous aurez acheté avec succès de l'ETH.
+9.  Vous pouvez transférer l'ETH de votre compte Coinbase vers votre portefeuille tel que [MetaMask](https://metamask.io/).
+    - Pour transférer l'ETH vers votre portefeuille, cliquez sur le bouton « Comptes » en haut à droite de la page.
+    - Cliquez sur le bouton « Envoyer » à côté du compte ETH.
+    - Entrez le montant d'ETH que vous souhaitez envoyer et l'adresse du portefeuille vers lequel vous souhaitez l'envoyer.
+    - Assurez-vous que vous envoyez à votre adresse de portefeuille Ethereum sur Arbitrum One.
     - Cliquez sur "Continuer" et confirmez votre transaction.
 
 Vous pouvez en savoir plus sur l'obtention d'ETH sur Coinbase [ici](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
@@ -185,29 +185,29 @@ Ce sera un guide étape par étape pour acheter des ETH sur Binance.
 6.  Entrez le montant d'ETH que vous souhaitez acheter.
 7.  Vérifiez votre achat et cliquez sur « Acheter ETH ».
 8.  Confirmez votre achat et vous verrez votre ETH dans votre portefeuille Binance Spot.
-9.  You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/).
-    - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist.
+9.  Vous pouvez retirer l'ETH de votre compte vers votre portefeuille tel que [MetaMask](https://metamask.io/).
+    - Pour retirer l'ETH vers votre portefeuille, ajoutez l'adresse de votre portefeuille à la liste blanche de retrait.
     - Cliquez sur le bouton « portefeuille », cliquez sur retirer et sélectionnez ETH.
     - Entrez le montant d'ETH que vous souhaitez envoyer et l'adresse du portefeuille sur liste blanche à laquelle vous souhaitez l'envoyer.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
+    - Assurez-vous que vous envoyez à votre adresse de portefeuille Ethereum sur Arbitrum One.
     - Cliquez sur "Continuer" et confirmez votre transaction.
 
 Vous pouvez en savoir plus sur l'obtention d'ETH sur Binance [ici](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
 
-## Billing FAQs
+## FAQ sur la facturation
 
-### How many queries will I need?
+### De combien de requêtes aurai-je besoin ?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+Vous n'avez pas besoin de savoir à l'avance combien de requêtes vous aurez besoin. Vous ne serez facturé que pour ce que vous utilisez et vous pourrez retirer des GRT de votre compte à tout moment.
 
-We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
+Nous vous recommandons de surestimer le nombre de requêtes dont vous aurez besoin afin de ne pas avoir à recharger votre solde fréquemment. Pour les applications de petite et moyenne taille, une bonne estimation consiste à commencer par 1 à 2 millions de requêtes par mois et à surveiller de près l'utilisation au cours des premières semaines. Pour les applications plus grandes, une bonne estimation consiste à utiliser le nombre de visites quotidiennes que reçoit votre site multiplié par le nombre de requêtes que votre page la plus active effectue à son ouverture.
 
-Of course, both new and existing users can reach out to Edge & Node's BD team for a consult to learn more about anticipated usage.
+Bien entendu, les nouveaux utilisateurs et les utilisateurs existants peuvent contacter l'équipe BD d'Edge &amp ; Node pour une consultation afin d'en savoir plus sur l'utilisation prévue.
 
-### Can I withdraw GRT from my billing balance?
+### Puis-je retirer du GRT de mon solde de facturation ?
 
-Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
+Oui, vous pouvez toujours retirer les GRT qui n'ont pas déjà été utilisés pour des requêtes de votre solde de facturation. Le contrat de facturation est uniquement conçu pour transférer des GRT de l'Ethereum Mainnet vers le réseau Arbitrum. Si vous souhaitez transférer vos GRT d'Arbitrum vers le réseau principal Ethereum, vous devrez utiliser le [pont Arbitrum](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### Que se passe-t-il lorsque mon solde de facturation est épuisé ? Vais-je recevoir un avertissement ?
 
-You will receive several email notifications before your billing balance runs out.
+Vous recevrez plusieurs notifications par e-mail avant que votre solde de facturation ne soit épuisé.

From 090ebaae9e494d20aa050334592dd599fb0f3c7f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:03 -0500
Subject: [PATCH 0907/1325] New translations billing.mdx (Spanish)

---
 website/pages/es/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/es/billing.mdx b/website/pages/es/billing.mdx
index e73e074a8b44..604244a22148 100644
--- a/website/pages/es/billing.mdx
+++ b/website/pages/es/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Haz clic en el botón "Conectar wallet" en la esquina superior derecha de la página. Serás redirigido a la página de selección de wallet. Selecciona tu wallet y haz clic en "Conectar".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 59f99033635c7726a793b943ec2116a1434016db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:04 -0500
Subject: [PATCH 0908/1325] New translations billing.mdx (Arabic)

---
 website/pages/ar/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ar/billing.mdx b/website/pages/ar/billing.mdx
index 68ee9ca693bd..42aa104673bb 100644
--- a/website/pages/ar/billing.mdx
+++ b/website/pages/ar/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. انقر على زر "توصيل المحفظة" في الزاوية اليمنى العليا من الصفحة. ستتم إعادة توجيهك إلى صفحة اختيار المحفظة. حدد محفظتك وانقر على "توصيل".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From c3bcea9ad9313ecd95fc768ad6a40e8f68d47d32 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:05 -0500
Subject: [PATCH 0909/1325] New translations billing.mdx (Czech)

---
 website/pages/cs/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/cs/billing.mdx b/website/pages/cs/billing.mdx
index 8eb2b1e0bd2e..c308319f4286 100644
--- a/website/pages/cs/billing.mdx
+++ b/website/pages/cs/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Klikněte na tlačítko "Připojit peněženku" v pravém horním rohu stránky. Budete přesměrováni na stránku pro výběr peněženky. Vyberte svou peněženku a klikněte na "Připojit".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ Více informací o získání ETH na Binance se dozvíte [zde](https://www.binan
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 770918cb395e38616728eda983bed6baa75ef6b5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:07 -0500
Subject: [PATCH 0910/1325] New translations billing.mdx (German)

---
 website/pages/de/billing.mdx | 286 +++++++++++++++++------------------
 1 file changed, 143 insertions(+), 143 deletions(-)

diff --git a/website/pages/de/billing.mdx b/website/pages/de/billing.mdx
index 37f9c840d00b..5b390c4adf5e 100644
--- a/website/pages/de/billing.mdx
+++ b/website/pages/de/billing.mdx
@@ -2,212 +2,212 @@
 title: Billing
 ---
 
-## Subgraph Billing Plans
+## Subgraph Abrechnungspläne
 
-There are two plans to use when querying subgraphs on The Graph Network.
+Es gibt zwei Pläne für die Abfrage von Subgraphen in The Graph Network.
 
-- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling their dapp.
+- <strong x-id=„1“>Free Plan</strong>: Der Free Plan beinhaltet 100.000 kostenlose monatliche Abfragen mit vollem Zugriff auf die Subgraph Studio Testumgebung. Dieser Plan ist für Hobbyisten, Hackathon-Teilnehmer und diejenigen mit Nebenprojekten gedacht, die The Graph ausprobieren möchten, bevor sie ihre Dapp skalieren.
 
-- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card. The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+- <strong x-id=„1“>Growth Plan</strong>: Der Growth Plan beinhaltet alles, was im Free Plan enthalten ist, wobei alle Abfragen nach 100.000 monatlichen Abfragen eine Zahlung mit GRT oder Kreditkarte erfordern. Der Growth Plan ist flexibel genug, um Teams abzudecken, die Dapps für eine Vielzahl von Anwendungsfällen entwickelt haben.
 
 <VideoEmbed youtube="Nn771WagX2I" />
 
-## Query Payments with credit card
+## Abfrage Zahlungen mit Kreditkarte
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
-  1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+- Um die Abrechnung mit Kredit-/Debitkarten einzurichten, müssen die Benutzer Subgraph Studio (https://thegraph.com/studio/) aufrufen
+  1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
-  3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
-  4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details.
-- Invoices will be processed at the end of each month and require an active credit card on file for all queries beyond the free plan quota.
+  3. Wählen Sie „ Upgrade Plan“, wenn Sie vom Free Plan upgraden oder wählen Sie „Manage Plan“, wenn Sie GRT bereits in der Vergangenheit zu Ihrem Abrechnungssaldo hinzugefügt haben. Als Nächstes können Sie die Anzahl der Abfragen schätzen, um einen Kostenvoranschlag zu erhalten, dieser Schritt ist jedoch nicht erforderlich.
+  4. Um eine Zahlung per Kreditkarte zu wählen, wählen Sie „Kreditkarte“ als Zahlungsmethode und geben Sie Ihre Kreditkartendaten ein. Diejenigen, die Stripe bereits verwendet haben, können die Funktion „Link“ verwenden, um ihre Daten automatisch auszufüllen.
+- Die Rechnungen werden am Ende eines jeden Monats erstellt. Für alle Abfragen, die über das kostenlose Kontingent hinausgehen, muss eine aktive Kreditkarte hinterlegt sein.
 
-## Query Payments with GRT
+## Abfrage von Zahlungen mit GRT
 
-Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph Network. With GRT, invoices will be processed at the end of each month and require a sufficient balance of GRT to make queries beyond the Free Plan quota of 100,000 monthly queries. You'll be required to pay fees generated from your API keys. Using the billing contract, you'll be able to:
+Subgraph-Nutzer können The Graph Token (oder GRT) verwenden, um für Abfragen im The Graph Network zu bezahlen. Mit GRT werden Rechnungen am Ende eines jeden Monats bearbeitet und erfordern ein ausreichendes Guthaben an GRT, um Abfragen über die Free-Plan-Quote von 100.000 monatlichen Abfragen hinaus durchzuführen. Sie müssen die von Ihren API-Schlüsseln generierten Gebühren bezahlen. Mit dem Abrechnungsvertrag können Sie:
 
 - Add and withdraw GRT from your account balance.
 - Keep track of your balances based on how much GRT you have added to your account balance, how much you have removed, and your invoices.
 - Automatically pay invoices based on query fees generated, as long as there is enough GRT in your account balance.
 
-### GRT on Arbitrum or Ethereum
+### GRT auf Arbitrum oder Ethereum
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+Das Abrechnungssystem von The Graph akzeptiert GRT auf Arbitrum, und die Nutzer benötigen ETH auf Arbitrum, um ihr Gas zu bezahlen. Während das The Graph-Protokoll auf dem Ethereum Mainnet begann, finden alle Aktivitäten, einschließlich der Abrechnungsverträge, nun auf Arbitrum One statt.
 
-To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Um für Abfragen zu bezahlen, brauchen Sie GRT auf Arbitrum. Hier sind ein paar verschiedene Möglichkeiten, dies zu erreichen:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Wenn Sie bereits GRT auf Ethereum haben, können Sie es zu Arbitrum überbrücken. Sie können dieses über GRT-Bridging-Option in Subgraph Studio tun oder eine der folgenden Bridges verwenden:
 
-- [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
-- [TransferTo](https://transferto.xyz/swap)
+- [Die Arbitrum Brücke](https://bridge.arbitrum.io/?l2ChainId=42161)
+- [Übertragen auf](https://transferto.xyz/swap)
 
-- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap.
+- Wenn du bereits Assets auf Arbitrum hast, kannst du sie über ein Swapping-Protokoll wie Uniswap in GRT tauschen.
 
-- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange.
+- Alternativ können Sie GRT auch direkt auf Arbitrum über einen dezentralen Handelsplatz erwerben.
 
-> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
+> In diesem Abschnitt wird davon ausgegangen, dass du bereits GRT in deiner Wallet hast und auf Arbitrum bist. Wenn Sie keine GRT haben, können Sie erfahren, wie Sie GRT [hier](#getting-grt) bekommen.
 
-Once you bridge GRT, you can add it to your billing balance.
+Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen.
 
-### Adding GRT using a wallet
+### Hinzufügen von GRT mit einer Wallet
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable.
-8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-9. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
-
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
-
-### Withdrawing GRT using a wallet
-
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
-4. Enter the amount of GRT you would like to withdraw.
-5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
-6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
+3. Wählen Sie die Schaltfläche „ Manage “ in der oberen rechten Ecke. Erstmalige Nutzer sehen die Option „Upgrade auf den Wachstumsplan“, während wiederkehrende Nutzer auf „Von der Wallet einzahlen“ klicken.
+4. Verwenden Sie den Slider, um die Anzahl der Abfragen zu schätzen, die Sie monatlich erwarten.
+   - Vorschläge für die Anzahl der Abfragen, die Sie verwenden können, finden Sie auf unserer Seite <strong x-id=„1“>Häufig gestellte Fragen</strong>.
+5. Wählen Sie „Kryptowährung“. GRT ist derzeit die einzige Kryptowährung, die im The Graph Network akzeptiert wird.
+6. Wählen Sie die Anzahl der Monate, die Sie im Voraus bezahlen möchten.
+   - Die Zahlung im Voraus verpflichtet Sie nicht zu einer zukünftigen Nutzung. Ihnen wird nur das berechnet, was Sie verbrauchen, und Sie können Ihr Guthaben jederzeit abheben.
+7. Wählen Sie das Netzwerk, über das Sie Ihr GRT einzahlen. GRT auf Arbitrum oder Ethereum sind beide akzeptabel.
+8. Klicken Sie auf „GRT-Zugriff zulassen“ und geben Sie dann die Menge an GRT an, die von Ihrer Wallet genommen werden kann.
+   - Wenn Sie für mehrere Monate im Voraus bezahlen, müssen Sie den Zugriff auf den Betrag erlauben, der diesem Betrag entspricht. Diese Interaktion kostet kein Gas.
+9. Zum Schluss klicken Sie auf „GRT zu Rechnungssaldo hinzufügen“. Für diese Transaktion wird ETH auf Arbitrum benötigt, um die Gaskosten zu decken.
+
+- Beachten Sie, dass GRT, die von Arbitrum eingezahlt werden, innerhalb weniger Augenblicke verarbeitet werden, während GRT, die von Ethereum eingezahlt werden, etwa 15-20 Minuten zur Verarbeitung benötigen. Sobald die Transaktion bestätigt wurde, wird das GRT zu Ihrem Kontostand hinzugefügt.
+
+### GRT über eine Wallet abheben
+
+1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
+2. Klicken Sie auf die Schaltfläche „Connect Wallet“ in der oberen rechten Ecke der Seite. Wählen Sie Ihre Wallet aus und klicken Sie auf „Verbinden“.
+3. Klicken Sie auf die Schaltfläche „Verwalten“ in der oberen rechten Ecke der Seite. Wählen Sie „GRT abheben“. Ein Seitenfenster wird angezeigt.
+4. Geben Sie den Betrag der GRT ein, den Sie abheben möchten.
+5. Klicken Sie auf „GRT abheben“, um die GRT von Ihrem Kontostand abzuheben. Unterschreiben Sie die zugehörige Transaktion in Ihrer Wallet. Dies kostet Gas. Die GRT werden an Ihre Arbitrum Wallet gesendet.
+6. Sobald die Transaktion bestätigt ist, werden die GRT von Ihrem Kontostand in Ihrem Arbitrum Wallet abgezogen.
 
 ### Adding GRT using a multisig wallet
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas.
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
+2. Klicke auf die Schaltfläche „Wallet verbinden“ in der oberen rechten Ecke der Seite. Wähle deine Wallet aus und klicke auf „Verbinden“. Wenn du die [Gnosis-Safe](https://gnosis-safe.io/) verwendest, kannst du sowohl deine Multisig-Wallet als auch deine Signatur-Wallet verbinden. Anschließend unterschreibe die zugehörige Nachricht. Dies verursacht keine Gasgebühren.
+3. Wählen Sie die Schaltfläche „ Manage “ in der oberen rechten Ecke. Erstmalige Nutzer sehen die Option „Upgrade auf den Wachstumsplan“, während wiederkehrende Nutzer auf „Von der Wallet einzahlen“ klicken.
+4. Verwenden Sie den Slider, um die Anzahl der Abfragen zu schätzen, die Sie monatlich erwarten.
+   - Vorschläge für die Anzahl der Abfragen, die Sie verwenden können, finden Sie auf unserer Seite <strong x-id=„1“>Häufig gestellte Fragen</strong>.
+5. Wählen Sie „Kryptowährung“. GRT ist derzeit die einzige Kryptowährung, die im The Graph Network akzeptiert wird.
+6. Wählen Sie die Anzahl der Monate, die Sie im Voraus bezahlen möchten.
+   - Die Zahlung im Voraus verpflichtet Sie nicht zu einer zukünftigen Nutzung. Ihnen wird nur das berechnet, was Sie verbrauchen, und Sie können Ihr Guthaben jederzeit abheben.
+7. Wählen Sie das Netzwerk, über das Sie Ihr GRT einzahlen. GRT auf Arbitrum oder Ethereum sind beide akzeptabel. 8. Klicken Sie auf „GRT-Zugang erlauben“ und geben Sie dann den Betrag an GRT an, der von Ihrer Wallet genommen werden kann.
+   - Wenn Sie für mehrere Monate im Voraus bezahlen, müssen Sie den Zugriff auf den Betrag erlauben, der diesem Betrag entspricht. Diese Interaktion kostet kein Gas.
+8. Zum Schluss klicken Sie auf „GRT zu Rechnungssaldo hinzufügen“. Für diese Transaktion wird ETH auf Arbitrum benötigt, um die Gaskosten zu decken.
 
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+- Beachten Sie, dass GRT, die von Arbitrum eingezahlt werden, innerhalb weniger Augenblicke verarbeitet werden, während GRT, die von Ethereum eingezahlt werden, etwa 15-20 Minuten zur Verarbeitung benötigen. Sobald die Transaktion bestätigt wurde, wird das GRT zu Ihrem Kontostand hinzugefügt.
 
-## Getting GRT
+## GRT abrufen
 
-This section will show you how to get GRT to pay for query fees.
+In diesem Abschnitt erfahren Sie, wie Sie GRT dazu bringen können, die Abfragegebühren zu bezahlen.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing GRT on Coinbase.
+Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Coinbase.
 
-1. Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page.
-4. Select the currency you want to purchase. Select GRT.
-5. Select the payment method. Select your preferred payment method.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase. Review your purchase and click "Buy GRT".
-8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT.
-9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page.
-   - Click on the "Send" button next to the GRT account.
-   - Enter the amount of GRT you want to send and the wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction. -Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet.
+1. Gehen Sie zu <a href=„https://www.coinbase.com/“>Coinbase</a> und erstellen Sie ein Konto.
+2. Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
+3. Sobald Sie Ihre Identität überprüft haben, können Sie GRT kaufen. Dazu klicken Sie auf die Schaltfläche „Kaufen/Verkaufen“ oben rechts auf der Seite.
+4. Wählen Sie die Währung, die Sie kaufen möchten. Wählen Sie GRT.
+5. Wählen Sie die Zahlungsmethode aus. Wählen Sie Ihre bevorzugte Zahlungsmethode aus.
+6. Wählen Sie die Menge an GRT, die Sie kaufen möchten.
+7. Überprüfen Sie Ihren Einkauf. Überprüfen Sie Ihren Einkauf und klicken Sie auf „GRT kaufen“.
+8. Bestätigen Sie Ihren Kauf. Bestätigen Sie Ihren Kauf und Sie haben GRT erfolgreich gekauft.
+9. Sie können die GRT von Ihrem Konto auf Ihre Wallet wie <a href=„https://metamask.io/“>MetaMask</a> übertragen.
+   - Um GRT auf Ihre Wallet zu übertragen, klicken Sie auf die Schaltfläche „Konten“ oben rechts auf der Seite.
+   - Klicken Sie auf die Schaltfläche „Senden“ neben dem GRT Konto.
+   - Geben Sie den Betrag an GRT ein, den Sie senden möchten, und die Wallet-Adresse, an die Sie ihn senden möchten.
+   - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion. -Bitte beachten Sie, dass Coinbase Sie bei größeren Kaufbeträgen möglicherweise 7-10 Tage warten lässt, bevor Sie den vollen Betrag in eine Krypto-Wallet überweisen.
 
-You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+Sie können mehr über den Erwerb von GRT auf Coinbase <a href=„https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency“>hier</a> erfahren.
 
 ### Binance
 
-This will be a step by step guide for purchasing GRT on Binance.
+Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Binance.
 
-1. Go to [Binance](https://www.binance.com/en) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner.
-4. You will be taken to a page where you can select the currency you want to purchase. Select GRT.
-5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase and click "Buy GRT".
-8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
-9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
-   - Click on the "wallet" button, click withdraw, and select GRT.
-   - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction.
+1. Gehen Sie auf <a href=„https://www.binance.com/en“>Binance</a> und erstellen Sie ein Konto.
+2. Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
+3. Sobald Sie Ihre Identität überprüft haben, können Sie GRT kaufen. Dazu klicken Sie auf die Schaltfläche „Jetzt kaufen“ auf dem Banner der Homepage.
+4. Sie werden zu einer Seite weitergeleitet, auf der Sie die Währung auswählen können, die Sie kaufen möchten. Wählen Sie GRT.
+5. Wählen Sie Ihre bevorzugte Zahlungsmethode. Sie können mit verschiedenen Fiat-Währungen wie Euro, US-Dollar und mehr bezahlen.
+6. Wählen Sie die Menge an GRT, die Sie kaufen möchten.
+7. Überprüfen Sie Ihren Kauf und klicken Sie auf „GRT kaufen“.
+8. Bestätigen Sie Ihren Kauf und Sie werden Ihr GRT in Ihrer Binance Spot Wallet sehen können.
+9. Sie können GRT von Ihrem Konto auf Ihre Wallet wie <a href=„https://metamask.io/“>MetaMask</a> abheben.
+   - <a href=„https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570“>Um GRT auf Ihr Wallet abzuheben</a>, fügen Sie die Adresse Ihres Wallets zur Whitelist für Abhebungen hinzu.
+   - Klicken Sie auf die Schaltfläche „Wallet“, klicken Sie auf Abheben und wählen Sie GRT.
+   - Geben Sie den GRT-Betrag ein, den Sie senden möchten, und die Wallet-Adresse, die auf der Whitelist steht.
+   - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion.
 
-You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+Sie können mehr über den Erwerb von GRT auf Binance <a href=„https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582“>hier</a> erfahren.
 
 ### Uniswap
 
-This is how you can purchase GRT on Uniswap.
+So können Sie GRT auf Uniswap kaufen.
 
-1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet.
-2. Select the token you want to swap from. Select ETH.
-3. Select the token you want to swap to. Select GRT.
-   - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
-4. Enter the amount of ETH you want to swap.
-5. Click "Swap".
-6. Confirm the transaction in your wallet and you wait for the transaction to process.
+1. Gehen Sie auf <a href=„https://app.uniswap.org/swap?chain=arbitrum“>Uniswap</a> und verbinden Sie Ihre Wallet.
+2. Wählen Sie den Token, von dem Sie tauschen möchten. Wählen Sie ETH.
+3. Wählen Sie den Token, in den Sie tauschen möchten. Wählen Sie GRT.
+   - Stelle sicher, dass du den richtigen Token tauschst. Die Smart-Contract-Adresse von GRT auf Arbitrum One ist: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+4. Geben Sie den Betrag an ETH ein, den Sie tauschen möchten.
+5. Klicken Sie auf „Swap“.
+6. Bestätigen Sie die Transaktion in Ihrer Wallet und warten Sie auf die Abwicklung der Transaktion.
 
-You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
+Sie können mehr über den Erwerb von GRT auf Uniswap <a href=„https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-“>hier</a> erfahren.
 
-## Getting Ether
+## Ether erhalten
 
-This section will show you how to get Ether (ETH) to pay for transaction fees or gas costs. ETH is necessary to execute operations on the Ethereum network such as transferring tokens or interacting with contracts.
+In diesem Abschnitt erfahren Sie, wie Sie Ether (ETH) erhalten können, um Transaktionsgebühren oder Gaskosten zu bezahlen. ETH ist notwendig, um Operationen im Ethereum-Netzwerk auszuführen, wie z. B. die Übertragung von Token oder die Interaktion mit Verträgen.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing ETH on Coinbase.
-
-1.  Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3.  Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
-8.  Confirm your purchase and you will have successfully purchased ETH.
-9.  You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/).
-    - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page.
-    - Click on the "Send" button next to the ETH account.
-    - Enter the amount of ETH you want to send and the wallet address you want to send it to.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
-    - Click "Continue" and confirm your transaction.
-
-You can learn more about getting ETH on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Coinbase.
+
+1.  Gehen Sie zu <a href=„https://www.coinbase.com/“>Coinbase</a> und erstellen Sie ein Konto.
+2.  Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
+3.  Sobald Sie Ihre Identität bestätigt haben, können Sie ETH kaufen, indem Sie auf die Schaltfläche „Kaufen/Verkaufen“ oben rechts auf der Seite klicken.
+4.  Wählen Sie die Währung, die Sie kaufen möchten. Wählen Sie ETH.
+5.  Wählen Sie die gewünschte Zahlungsmethode.
+6.  Geben Sie die Menge an ETH ein, die Sie kaufen möchten.
+7.  Überprüfen Sie Ihren Kauf und klicken Sie auf „ETH kaufen“.
+8.  Bestätigen Sie Ihren Kauf und Sie haben erfolgreich ETH gekauft.
+9.  Sie können die ETH von Ihrem Coinbase-Konto auf Ihr Wallet wie <a href=„https://metamask.io/“>MetaMask</a> übertragen.
+    - Um die ETH auf Ihre Wallet zu übertragen, klicken Sie auf die Schaltfläche „Konten“ oben rechts auf der Seite.
+    - Klicken Sie auf die Schaltfläche „Senden“ neben dem ETH-Konto.
+    - Geben Sie den ETH-Betrag ein, den Sie senden möchten, und die Wallet-Adresse, an die Sie ihn senden möchten.
+    - Stellen Sie sicher, dass Sie an Ihre Ethereum Wallet Adresse auf Arbitrum One senden.
+    - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion.
+
+Sie können mehr über den Erwerb von ETH auf Coinbase <a href=„https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency“>hier</a> erfahren.
 
 ### Binance
 
-This will be a step by step guide for purchasing ETH on Binance.
+Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von ETH auf Binance.
 
-1.  Go to [Binance](https://www.binance.com/en) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3.  Once you have verified your identity, purchase ETH by clicking on the "Buy Now" button on the homepage banner.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
-8.  Confirm your purchase and you will see your ETH in your Binance Spot Wallet.
-9.  You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/).
-    - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist.
-    - Click on the "wallet" button, click withdraw, and select ETH.
-    - Enter the amount of ETH you want to send and the whitelisted wallet address you want to send it to.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
-    - Click "Continue" and confirm your transaction.
+1.  Gehen Sie auf <a href=„https://www.binance.com/en“>Binance</a> und erstellen Sie ein Konto.
+2.  Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
+3.  Sobald Sie Ihre Identität verifiziert haben, kaufen Sie ETH, indem Sie auf die Schaltfläche „Jetzt kaufen“ auf dem Banner der Homepage klicken.
+4.  Wählen Sie die Währung, die Sie kaufen möchten. Wählen Sie ETH.
+5.  Wählen Sie die gewünschte Zahlungsmethode.
+6.  Geben Sie die Menge an ETH ein, die Sie kaufen möchten.
+7.  Überprüfen Sie Ihren Kauf und klicken Sie auf „ETH kaufen“.
+8.  Bestätigen Sie Ihren Kauf und Sie werden Ihre ETH in Ihrer Binance Spot Wallet sehen.
+9.  Sie können die ETH von Ihrem Konto auf Ihr Wallet wie <a href=„https://metamask.io/“>MetaMask</a> abheben.
+    - Um die ETH auf Ihre Wallet abzuheben, fügen Sie die Adresse Ihrer Wallet zur Abhebungs-Whitelist hinzu.
+    - Klicken Sie auf die Schaltfläche „Wallet“, klicken Sie auf „withdraw“ und wählen Sie ETH.
+    - Geben Sie den ETH-Betrag ein, den Sie senden möchten, und die Adresse der Wallet, die auf der Whitelist steht, an die Sie den Betrag senden möchten.
+    - Stellen Sie sicher, dass Sie an Ihre Ethereum Wallet Adresse auf Arbitrum One senden.
+    - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion.
 
-You can learn more about getting ETH on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+Sie können mehr über den Erwerb von ETH auf Binance <a href=„https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582“>hier</a> erfahren.
 
-## Billing FAQs
+## FAQs zur Rechnungsstellung
 
-### How many queries will I need?
+### Wie viele Abfragen benötige ich?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+Sie müssen nicht im Voraus wissen, wie viele Abfragen Sie benötigen werden. Ihnen wird nur das berechnet, was Sie verbrauchen, und Sie können jederzeit GRT von Ihrem Konto abheben.
 
-We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
+Wir empfehlen Ihnen, die Anzahl der Abfragen, die Sie benötigen, zu überschlagen, damit Sie Ihr Guthaben nicht häufig aufstocken müssen. Eine gute Schätzung für kleine bis mittelgroße Anwendungen ist, mit 1 Mio. bis 2 Mio. Abfragen pro Monat zu beginnen und die Nutzung in den ersten Wochen genau zu überwachen. Bei größeren Anwendungen ist es sinnvoll, die Anzahl der täglichen Besuche auf Ihrer Website mit der Anzahl der Abfragen zu multiplizieren, die Ihre aktivste Seite beim Öffnen auslöst.
 
-Of course, both new and existing users can reach out to Edge & Node's BD team for a consult to learn more about anticipated usage.
+Natürlich können sich sowohl neue als auch bestehende Nutzer an das BD-Team von Edge & Node wenden, um mehr über die voraussichtliche Nutzung zu erfahren.
 
-### Can I withdraw GRT from my billing balance?
+### Kann ich GRT von meinem Rechnungssaldo abheben?
 
-Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
+Ja, Sie können jederzeit GRT, die nicht bereits für Abfragen verwendet wurden, von Ihrem Abrechnungskonto abheben. Der Abrechnungsvertrag ist nur dafür gedacht, GRT aus dem Ethereum-Mainnet in das Arbitrum-Netzwerk zu übertragen. Wenn Sie Ihr GRT von Arbitrum zurück ins Ethereum-Mainnet transferieren möchten, müssen Sie den [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### Was passiert, wenn mein Guthaben aufgebraucht ist? Werde ich eine Warnung erhalten?
 
-You will receive several email notifications before your billing balance runs out.
+Sie erhalten mehrere E-Mail-Benachrichtigungen, bevor Ihr Guthaben aufgebraucht ist.

From 211eb783afb04b45d874c49ac1b11125aedc22fa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:08 -0500
Subject: [PATCH 0911/1325] New translations billing.mdx (Italian)

---
 website/pages/it/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/it/billing.mdx b/website/pages/it/billing.mdx
index 37f9c840d00b..dec5cfdadc12 100644
--- a/website/pages/it/billing.mdx
+++ b/website/pages/it/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From d938226decc9af24f288c34db1009489ae236a94 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:09 -0500
Subject: [PATCH 0912/1325] New translations billing.mdx (Japanese)

---
 website/pages/ja/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ja/billing.mdx b/website/pages/ja/billing.mdx
index c41bdbafe2e5..a8c32eefdd56 100644
--- a/website/pages/ja/billing.mdx
+++ b/website/pages/ja/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. ページ右上の「Connect Wallet」をクリックします。ウォレット選択ページに遷移します。ウォレットを選択し、「Connect」をクリックします。
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ BinanceでETHを入手する詳細については、[こちら](https://www.bina
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From a6725e4c9951f17ce0c5b0aab9bb34351fc7db1e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:10 -0500
Subject: [PATCH 0913/1325] New translations billing.mdx (Korean)

---
 website/pages/ko/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ko/billing.mdx b/website/pages/ko/billing.mdx
index 37f9c840d00b..dec5cfdadc12 100644
--- a/website/pages/ko/billing.mdx
+++ b/website/pages/ko/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 2cdb5faf6cf25daba0a858e62819ac5c4a95451f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:12 -0500
Subject: [PATCH 0914/1325] New translations billing.mdx (Dutch)

---
 website/pages/nl/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/nl/billing.mdx b/website/pages/nl/billing.mdx
index 37f9c840d00b..dec5cfdadc12 100644
--- a/website/pages/nl/billing.mdx
+++ b/website/pages/nl/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 2c701b16e7932108a6a323d396cb1a63f9146c64 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:13 -0500
Subject: [PATCH 0915/1325] New translations billing.mdx (Polish)

---
 website/pages/pl/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/pl/billing.mdx b/website/pages/pl/billing.mdx
index 37f9c840d00b..dec5cfdadc12 100644
--- a/website/pages/pl/billing.mdx
+++ b/website/pages/pl/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 7c419a68199e4cf5bf0c88bbba8b72ea952e3f5a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:14 -0500
Subject: [PATCH 0916/1325] New translations billing.mdx (Portuguese)

---
 website/pages/pt/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/pt/billing.mdx b/website/pages/pt/billing.mdx
index 45abd7514130..a9694e876d05 100644
--- a/website/pages/pt/billing.mdx
+++ b/website/pages/pt/billing.mdx
@@ -14,7 +14,7 @@ Há dois planos disponíveis para queries de subgraphs na Graph Network.
 
 ## Pagamentos de Queries com cartão de crédito
 
-- Para configurar opções de pagamento no cartão, os utilizadores deverão acessar o Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/billing/).
   2. Clique no botão "Connect Wallet" (Conectar Carteira) no canto superior direito da página. Isto levará à página de seleção de carteira; lá, selecione a sua carteira e clique em "Connect".
   3. Escolha "atualizar plano" se está a atualizar do Plano Grátis, ou escolha "Gerir plano" se já adicionou GRT ao seu saldo de cobrança no passado. Depois, é possível estimar o número de queries para conseguir uma estimativa de preço, mas isto não é obrigatório.
@@ -69,7 +69,7 @@ Quando fizeres bridge do GRT, será possível adicioná-lo ao seu saldo de cobra
 
 1. Entre na [página de Cobranças do Subgraph Studio](https://thegraph.com/studio/billing/).
 2. Clique no botão "Connect Wallet" (Conectar Carteira) no canto superior direito da página, selecione a sua carteira e clique em "Connect".
-3. Clique no botão "Manage" (Gerir) no canto superior direito da página. Selecione "Withdraw GRT" (Sacar GRT). Um painel lateral aparecerá.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Insira a quantia de GRT que quer sacar.
 5. Clique em 'Withdraw GRT' (Sacar GRT) para sacar o GRT do seu saldo. Assine a transação associada na sua carteira — isto custa gas. O GRT será enviado à sua carteira Arbitrum.
 6. Quando a transação for confirmada, verá o GRT sacado do seu saldo na sua carteira Arbitrum.
@@ -83,7 +83,7 @@ Quando fizeres bridge do GRT, será possível adicioná-lo ao seu saldo de cobra
    - Para sugestões sobre o número de queries que deve usar, veja a nossa página de **Perguntas Frequentes**.
 5. Escolha "Criptomoedas". Atualmente, o GRT é a única criptomoeda aceita na Graph Network.
 6. Selecione o número de meses que deseja pagar antecipadamente.
-   - Pagamentos antecipados não te comprometem a um uso futuro. Você só será cobrado pelo que usa, e pode sacar o seu saldo a qualquer hora.
+   - Pagamentos antecipados não te comprometem a usos futuros. Você só será cobrado pelo que usa, e pode sacar o seu saldo a qualquer hora.
 7. Escolha a rede da qual o seu GRT será depositado. GRT do Arbitrum e do Ethereum são aceitáveis. Clique "Allow GRT Access" (Permitir Acesso ao GRT) e depois especifique a quantidade de GRT que pode ser retirada da sua carteira.
    - Se pagar múltiplos meses antecipadamente, permita o acesso à quantia que corresponde àquela quantidade. Esta interação não custará gas.
 8. Por último, clique em "Add GRT to Billing Balance" (Adicionar GRT ao Saldo de Cobranças). Esta transação precisará de GRT no Arbitrum para cobrir os custos de gas.
@@ -127,7 +127,7 @@ Este é um guia passo a passo para comprar GRT na Binance.
 7. Verifique a sua compra e clique em "Comprar GRT".
 8. Confirme a sua compra, e logo o seu GRT aparecerá na sua Carteira Spot da Binance.
 9. É possível transferir o GRT da sua conta à sua carteira preferida, como o [MetaMask](https://metamask.io/).
-   - [Para sacar](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) o GRT à sua carteira, adicione o endereço da sua carteira à whitelist de saques.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Clique no botão "wallet", clique em "sacar", e selecione GRT.
    - Insira a quantia de GRT que deseja enviar, e o endereço da carteira na whitelist à qual quer enviar.
    - Clique em "Continuar" e confirme a sua transação.
@@ -198,7 +198,7 @@ Saiba mais sobre como adquirir ETH na Binance [aqui](https://www.binance.com/en/
 
 ### De quantas queries precisarei?
 
-Não é necessário saber com antecedência quantos queries serão necessários. Você só será cobrado pelo que usar, e poderá sacar GRT da sua conta a qualquer hora.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 Recomendamos estimar mais queries do que necessário para que não precise encher o seu saldo com frequência. Uma boa estimativa para aplicativos pequenos ou médios é começar com 1 a 2 milhões de queries por mês e monitorar atenciosamente o uso nas primeiras semanas. Para aplicativos maiores, uma boa estimativa consiste em utilizar o número de visitas diárias ao seu site multiplicado ao número de queries que a sua página mais ativa faz ao abrir.
 
@@ -208,6 +208,6 @@ Claro que todos os utilizadores, novatos ou experientes, podem contactar a equip
 
 Sim, sempre é possível sacar GRT que não já foi usado para queries do seu saldo de cobrança. O contrato inteligente só é projetado para bridgear GRT da mainnet Ethereum até a rede Arbitrum. Se quiser transferir o seu GRT do Arbitrum de volta à mainnet Ethereum, precisará usar a [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### O que acontece quando o meu saldo de cobrança se esgota? Receberei um aviso?
+### What happens when my billing balance runs out? Will I get a warning?
 
 Serão enviadas várias notificações de email antes do seu saldo de cobrança ser esvaziado.

From 3329f103809c66a5417df0dcb7f1c5df143b9894 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:16 -0500
Subject: [PATCH 0917/1325] New translations billing.mdx (Russian)

---
 website/pages/ru/billing.mdx | 268 +++++++++++++++++------------------
 1 file changed, 134 insertions(+), 134 deletions(-)

diff --git a/website/pages/ru/billing.mdx b/website/pages/ru/billing.mdx
index cdf92ab49675..b8c58d83de09 100644
--- a/website/pages/ru/billing.mdx
+++ b/website/pages/ru/billing.mdx
@@ -2,174 +2,174 @@
 title: Выставление счетов
 ---
 
-## Subgraph Billing Plans
+## Тарифные планы для субграфов
 
-There are two plans to use when querying subgraphs on The Graph Network.
+Существует два плана для выполнения запросов к субграфам в The Graph Network.
 
-- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling their dapp.
+- **Бесплатный план**: Бесплатный план включает 100,000 бесплатных запросов в месяц с полным доступом к тестовой среде Subgraph Studio. Этот план разработан для любителей, участников хакатонов и тех, у кого есть сторонние проекты, чтобы они могли попробовать The Graph перед масштабированием своего децентрализованного приложения.
 
-- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card. The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+- **План роста**: План роста включает все возможности бесплатного плана, но все запросы, превышающие 100,000 в месяц, требуют оплаты в GRT или кредитной картой. Этот план достаточно гибок, чтобы поддерживать команды, которые уже запустили децентрализованные приложения для различных сценариев использования.
 
 <VideoEmbed youtube="Nn771WagX2I" />
 
-## Query Payments with credit card
+## Оплата запросов с помощью кредитной карты
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
-  1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+- Чтобы настроить оплату с помощью кредитных/дебетовых карт, пользователи должны зайти в Subgraph Studio (https://thegraph.com/studio/)
+  1. Перейдите на[страницу оплаты Subgraph Studio](https://thegraph.com/studio/billing/).
   2. Нажмите на кнопку «Connect Wallet» в правом верхнем углу страницы. Вы будете перенаправлены на страницу выбора кошелька. Выберите свой кошелек и нажмите «Connect».
-  3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
-  4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details.
-- Invoices will be processed at the end of each month and require an active credit card on file for all queries beyond the free plan quota.
+  3. Выберите «Обновление плана», если Вы переходите с бесплатного плана, или «Управление планом», если Вы уже ранее добавили GRT на свой баланс для оплаты. Далее Вы можете оценить количество запросов, чтобы получить примерную стоимость, но это не обязательный шаг.
+  4. Чтобы выбрать оплату кредитной картой, выберите «Credit card» как способ оплаты и заполните информацию о своей карте. Те, кто ранее использовал Stripe, могут воспользоваться функцией Link для автоматического заполнения данных.
+- Счета будут выставляться в конце каждого месяца, и для всех запросов сверх квоты бесплатного плана потребуется активная кредитная карта.
 
-## Query Payments with GRT
+## Оплата запросов с помощью GRT
 
-Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph Network. With GRT, invoices will be processed at the end of each month and require a sufficient balance of GRT to make queries beyond the Free Plan quota of 100,000 monthly queries. You'll be required to pay fees generated from your API keys. Using the billing contract, you'll be able to:
+Пользователи субграфов могут использовать токен The Graph (GRT) для оплаты запросов в The Graph Network. При использовании GRT счета будут выставляться в конце каждого месяца, и потребуется достаточный баланс GRT для выполнения запросов, превышающих квоту бесплатного плана в 100,000 запросов в месяц. Вам нужно будет оплатить комиссии, которые генерируются Вашими API-ключами. С помощью платежного контракта Вы сможете:
 
 - Добавлять и списывать токены GRT с Вашего платежного баланса.
 - Отслеживать баланс своих счетов на основе того, сколько токенов GRT Вы добавили к своему платежному балансу и сколько удалили.
 - Автоматически оплачивать счета на основе сгенерированных комиссий за запросы, если на Вашем платежном балансе достаточно токенов GRT.
 
-### GRT on Arbitrum or Ethereum
+### GRT на Arbitrum или Ethereum
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+Платежная система The Graph принимает GRT на Arbitrum, и пользователям потребуется ETH на Arbitrum для оплаты газа. Хотя протокол The Graph изначально был запущен на основной сети Ethereum, вся активность, включая платежные контракты, теперь проходит на Arbitrum One.
 
-To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Для оплаты запросов Вам потребуется GRT на Arbitrum. Вот несколько способов, как это можно сделать:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Если у Вас уже есть GRT на Ethereum, Вы можете перенести его на Arbitrum. Вы можете сделать это через опцию переноса GRT, доступную в Subgraph Studio, или с помощью одного из следующих мостов:
 
-- [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+- [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
 - [TransferTo](https://transferto.xyz/swap)
 
-- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap.
+- Если у Вас уже есть активы на Arbitrum, Вы можете обменять их на GRT через протокол обмена, такой как Uniswap.
 
-- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange.
+- В качестве альтернативы, Вы можете приобрести GRT напрямую на Arbitrum через децентрализованную биржу.
 
-> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
+> Этот раздел предполагает, что у Вас уже есть GRT в Вашем кошельке, и Вы находитесь в сети Arbitrum. Если у Вас нет GRT, Вы можете узнать, как его получить, [здесь](#getting-grt).
 
-Once you bridge GRT, you can add it to your billing balance.
+После переноса GRT Вы можете добавить его на баланс для оплаты.
 
-### Adding GRT using a wallet
+### Добавление токенов GRT с помощью кошелька
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+1. Перейдите на [страницу оплаты в Subgraph Studio](https://thegraph.com/studio/billing/).
 2. Нажмите на кнопку «Connect Wallet» в правом верхнем углу страницы. Вы будете перенаправлены на страницу выбора кошелька. Выберите свой кошелек и нажмите «Connect».
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable.
-8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-9. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
-
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
-
-### Withdrawing GRT using a wallet
-
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
-4. Enter the amount of GRT you would like to withdraw.
-5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
-6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
+3. Нажмите кнопку «Управление» в правом верхнем углу. Новые пользователи увидят опцию «Обновить до плана Роста», а те, кто пользовался ранее — «Пополнение с кошелька».
+4. Используйте ползунок, чтобы оценить количество запросов, которое Вы планируете выполнять ежемесячно.
+   - Рекомендации по количеству запросов, которые Вы можете использовать, можно найти на нашей странице **Часто задаваемые вопросы**.
+5. Выберите «Криптовалюта». В настоящее время GRT — единственная криптовалюта, принимаемая в The Graph Network.
+6. Выберите количество месяцев, за которые Вы хотели бы внести предоплату.
+   - Предоплата не обязывает Вас к дальнейшему использованию. С Вас будет взиматься плата только за то, что Вы используете, и Вы сможете вывести свой баланс в любое время.
+7. Выберите сеть, из которой Вы вносите свой GRT. Принимаются GRT как на Arbitrum, так и на Ethereum.
+8. Нажмите «Разрешить доступ к GRT», а затем укажите количество GRT, которое может быть списано с Вашего кошелька.
+   - Если Вы вносите предоплату за несколько месяцев, Вам нужно разрешить доступ к сумме, которая соответствует этому количеству. За это действие газ взиматься не будет.
+9. В заключение, нажмите «Добавить GRT в платежный баланс». Эта транзакция потребует ETH на Arbitrum для покрытия затрат на газ.
+
+- Обратите внимание, что GRT, переведенные из Arbitrum, будут обработаны в течение нескольких секунд, в то время как GRT, переведенные из Ethereum, займут около 15-20 минут. Как только транзакция будет подтверждена, Вы увидите GRT на балансе своего аккаунта.
+
+### Вывод токенов GRT с помощью кошелька
+
+1. Перейдите на [страницу для оплаты Subgraph Studio](https://thegraph.com/studio/billing/).
+2. Нажмите на кнопку «Подключить кошелек» в правом верхнем углу страницы. Выберите свой кошелек и нажмите «Подключить».
+3. Нажмите кнопку «Управление» в правом верхнем углу страницы. Выберите «Вывести GRT». Появится боковая панель.
+4. Введите сумму GRT, которую хотите вывести.
+5. Нажмите «Вывести GRT», чтобы вывести токены GRT со своего платежного баланса. Подпишите соответствующую транзакцию в своем кошельке. За это потребуется оплата комиссии сети. Токены GRT будут отправлены на Ваш кошелек Arbitrum.
+6. Как только транзакция будет подтверждена, Вы увидите токены GRT выведенные с Вашего платежного баланса в своем кошельке Arbitrum.
 
 ### Добавление токенов GRT с помощью кошелька с мультиподписью
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas.
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+1. Перейдите на [страницу оплаты Subgraph Studio](https://thegraph.com/studio/billing/).
+2. Кликните «Подключить кошелек» в правом верхнем углу страницы. Выберите свой кошелек и нажмите «Подключить». Если Вы используете [Gnosis-Safe](https://gnosis-safe.io/), Вы сможете подключить как стандартный кошелёк, так и кошелёк с мультиподписью. Затем подпишите соответствующую транзакцию. За это Вам не придётся платить комиссию.
+3. Нажмите кнопку «Управление» в правом верхнем углу. Новые пользователи увидят опцию «Обновить до плана Роста», а те, кто пользовался ранее — «Пополнение с кошелька».
+4. Используйте ползунок, чтобы оценить количество запросов, которое Вы планируете выполнять ежемесячно.
+   - Рекомендации по количеству запросов, которые Вы можете использовать, можно найти на нашей странице **Часто задаваемые вопросы**.
+5. Выберите «Криптовалюта». В настоящее время GRT — единственная криптовалюта, принимаемая в The Graph Network.
+6. Выберите количество месяцев, за которые Вы хотели бы внести предоплату.
+   - Предоплата не обязывает Вас к дальнейшему использованию. С Вас будет взиматься плата только за то, что Вы используете, и Вы сможете вывести свой баланс в любое время.
+7. Выберите сеть, из которой Вы вносите свой GRT. Принимаются GRT как на Arbitrum, так и на Ethereum. 8. Нажмите «Разрешить доступ к GRT», а затем укажите количество GRT, которое может быть списано с Вашего кошелька.
+   - Если Вы вносите предоплату за несколько месяцев, Вам нужно разрешить доступ к сумме, которая соответствует этому количеству. За это действие газ взиматься не будет.
+8. В заключение, нажмите «Добавить GRT в платежный баланс». Эта транзакция потребует ETH на Arbitrum для покрытия затрат на газ.
 
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+- Обратите внимание, что GRT, переведенные из Arbitrum, будут обработаны в течение нескольких секунд, в то время как GRT, переведенные из Ethereum, займут около 15-20 минут. Как только транзакция будет подтверждена, Вы увидите GRT на балансе своего аккаунта.
 
-## Getting GRT
+## Получение GRT
 
-This section will show you how to get GRT to pay for query fees.
+В этом разделе показано, как оплачивать комиссии за запросы с помощью токенов GRT.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing GRT on Coinbase.
+Далее будет представлено пошаговое руководство по приобретению токена GRT на Coinbase.
 
-1. Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page.
-4. Select the currency you want to purchase. Select GRT.
-5. Select the payment method. Select your preferred payment method.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase. Review your purchase and click "Buy GRT".
-8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT.
-9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page.
-   - Click on the "Send" button next to the GRT account.
-   - Enter the amount of GRT you want to send and the wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction. -Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet.
+1. Перейдите на [Coinbase](https://www.coinbase.com/) и создайте учетную запись.
+2. После того как Вы создали учетную запись, Вам нужно будет подтвердить свою личность с помощью процесса, известного как KYC (или Know Your Customer). Это стандартная процедура для всех централизованных или кастодиальных криптобирж.
+3. После того как Вы подтвердили свою личность, Вы можете приобрести токены ETH нажав на кнопку "Купить/Продать" в правом верхнем углу страницы.
+4. Выберите валюту, которую хотите купить. Выберите GRT.
+5. Выберите способ оплаты. Выберите предпочитаемый способ оплаты.
+6. Выберите количество токенов GRT, которое хотите приобрести.
+7. Проверьте все данные о приобретении. Проверьте все данные о приобретении и нажмите «Купить GRT».
+8. Подтвердите покупку. Подтвердите покупку - Вы успешно приобрели токены GRT.
+9. Вы можете перевести токены GRT со своей учетной записи на свой кошелек, например, на [MetaMask](https://metamask.io/).
+   - Чтобы перевести токены GRT на свой кошелек, нажмите кнопку «Учетные записи» в правом верхнем углу страницы.
+   - Нажмите на кнопку «Отправить» рядом с учетной записью GRT.
+   - Введите сумму GRT, которую хотите отправить, и адрес кошелька, на который хотите её отправить.
+   - Нажмите «Продолжить» и подтвердите транзакцию. -Обратите внимание, что при больших суммах покупки Coinbase может потребовать от Вас подождать 7-10 дней, прежде чем переведет полную сумму на кошелек.
 
-You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+Получить больше информации о покупке GRT на Coinbase Вы можете [здесь](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
 
 ### Binance
 
-This will be a step by step guide for purchasing GRT on Binance.
+Далее будет представлено пошаговое руководство по приобретению токена GRT на Binance.
 
-1. Go to [Binance](https://www.binance.com/en) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner.
-4. You will be taken to a page where you can select the currency you want to purchase. Select GRT.
-5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase and click "Buy GRT".
-8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
-9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
-   - Click on the "wallet" button, click withdraw, and select GRT.
-   - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction.
+1. Перейдите на [Binance](https://www.binance.com/en) и создайте учетную запись.
+2. После того как Вы создали учетную запись, Вам нужно будет подтвердить свою личность с помощью процесса, известного как KYC (или Know Your Customer). Это стандартная процедура для всех централизованных или кастодиальных криптобирж.
+3. После того как Вы подтвердили свою личность, Вы можете приобрести токены GRT. Вы можете сделать это, нажав на кнопку «Купить сейчас» на баннере главной страницы.
+4. Вы попадете на страницу, где сможете выбрать валюту, которую хотите приобрести. Выберите GRT.
+5. Выберите предпочитаемый способ оплаты. Вы сможете расплатиться различными фиатными валютами, такими как евро, доллары США и т. д.
+6. Выберите количество токенов GRT, которое хотите приобрести.
+7. Проверьте все данные о приобретении и нажмите «Купить GRT».
+8. Подтвердите покупку, и Вы сможете увидеть GRT в своем кошельке Binance Spot.
+9. Вы можете вывести GRT со своей учетной записи на свой окошелек, например, на [MetaMask](https://metamask.io/).
+   - [Чтобы вывести](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) GRT на свой кошелек, добавьте адрес кошелька в белый список вывода.
+   - Нажмите на кнопку «кошелек», нажмите «вывести» и выберите GRT.
+   - Введите сумму GRT, которую хотите отправить, и адрес кошелька из белого списка, на который Вы хотите её отправить.
+   - Нажмите «Продолжить» и подтвердите транзакцию.
 
-You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+Получить больше информации о покупке GRT на Binance Вы можете [здесь](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
 
 ### Uniswap
 
-This is how you can purchase GRT on Uniswap.
+Так Вы можете приобрести GRT на Uniswap.
 
-1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet.
-2. Select the token you want to swap from. Select ETH.
-3. Select the token you want to swap to. Select GRT.
-   - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
-4. Enter the amount of ETH you want to swap.
-5. Click "Swap".
-6. Confirm the transaction in your wallet and you wait for the transaction to process.
+1. Перейдите на [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) и подключите свой кошелек.
+2. Выберите токен, который хотите обменять. Выберите ETH.
+3. Выберите токен, на который хотите произвести обмен. Выберите GRT.
+   - Убедитесь, что выбираете правильный токен. Адрес смарт-контракта GRT в сети Arbitrum One: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+4. Введите количество ETH, которое хотите обменять.
+5. Нажмите «Обменять».
+6. Подтвердите транзакцию в своем кошельке и дождитесь ее обработки.
 
-You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
+Получить больше информации о покупке GRT на Uniswap Вы можете [здесь](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
 
-## Getting Ether
+## Получение Ether
 
-This section will show you how to get Ether (ETH) to pay for transaction fees or gas costs. ETH is necessary to execute operations on the Ethereum network such as transferring tokens or interacting with contracts.
+В этом разделе показано, как с помощью Ethereum (ETH) оплачивать транзакционные сборы или расходы комиссии сети. ETH необходим для выполнения операций в сети Ethereum, таких, как передача токенов или взаимодействие с контрактами.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing ETH on Coinbase.
-
-1.  Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3.  Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
-8.  Confirm your purchase and you will have successfully purchased ETH.
-9.  You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/).
-    - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page.
-    - Click on the "Send" button next to the ETH account.
-    - Enter the amount of ETH you want to send and the wallet address you want to send it to.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
-    - Click "Continue" and confirm your transaction.
+Далее будет представлено пошаговое руководство по приобретению токена ETH на Coinbase.
+
+1.  Перейдите на [Coinbase](https://www.coinbase.com/) и создайте учетную запись.
+2.  После того как Вы создали учетную запись, Вам нужно будет подтвердить свою личность с помощью процесса, известного как KYC (или Know Your Customer). Это стандартная процедура для всех централизованных или кастодиальных криптобирж.
+3.  После того как Вы подтвердили свою личность, Вы можете приобрести токены ETH нажав на кнопку "Купить/Продать" в правом верхнем углу страницы.
+4.  Выберите валюту, которую хотите купить. Выберите ETH.
+5.  Выберите предпочитаемый способ оплаты.
+6.  Введите количество ETH, которое хотите приобрести.
+7.  Проверьте все данные о приобретении и нажмите «Купить ETH».
+8.  Подтвердите покупку. Вы успешно приобрели токены ETH.
+9.  Вы можете перевести токены ETH со своей учетной записи на свой кошелек, например, на [MetaMask](https://metamask.io/).
+    - Чтобы перевести ETH на свой кошелек, нажмите кнопку «Учетные записи» в правом верхнем углу страницы.
+    - Нажмите на кнопку «Отправить» рядом с учетной записью ETH.
+    - Введите сумму ETH которую хотите отправить, и адрес кошелька, на который хотите её отправить.
+    - Убедитесь, что делаете перевод на адрес своего Ethereum-кошелька в сети Arbitrum One.
+    - Нажмите «Продолжить» и подтвердите транзакцию.
 
 You can learn more about getting ETH on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
 
@@ -177,37 +177,37 @@ You can learn more about getting ETH on Coinbase [here](https://help.coinbase.co
 
 This will be a step by step guide for purchasing ETH on Binance.
 
-1.  Go to [Binance](https://www.binance.com/en) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
+1.  Перейдите на [Binance](https://www.binance.com/en) и создайте учетную запись.
+2.  После того как Вы создали учетную запись, Вам нужно будет подтвердить свою личность с помощью процесса, известного как KYC (или Know Your Customer). Это стандартная процедура для всех централизованных или кастодиальных криптобирж.
 3.  Once you have verified your identity, purchase ETH by clicking on the "Buy Now" button on the homepage banner.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
+4.  Выберите валюту, которую хотите купить. Выберите ETH.
+5.  Выберите предпочитаемый способ оплаты.
+6.  Введите количество ETH, которое хотите приобрести.
+7.  Проверьте все данные о приобретении и нажмите «Купить ETH».
 8.  Confirm your purchase and you will see your ETH in your Binance Spot Wallet.
-9.  You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/).
-    - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist.
+9.  Вы можете вывести ETH со своей учетной записи на свой кошелек, например, на [MetaMask](https://metamask.io/).
+    - Чтобы вывести ETH на свой кошелек, добавьте адрес кошелька в белый список вывода.
     - Click on the "wallet" button, click withdraw, and select ETH.
     - Enter the amount of ETH you want to send and the whitelisted wallet address you want to send it to.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
-    - Click "Continue" and confirm your transaction.
+    - Убедитесь, что делаете перевод на адрес своего Ethereum-кошелька в сети Arbitrum One.
+    - Нажмите «Продолжить» и подтвердите транзакцию.
 
 You can learn more about getting ETH on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
 
-## Billing FAQs
+## Часто задаваемые вопросы по выставлению счетов
 
-### How many queries will I need?
+### Сколько запросов мне понадобится?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+Вам не нужно заранее знать, сколько запросов Вам понадобится. С Вас будет взиматься плата только за фактически использованные запросы, и Вы сможете вывести GRT со своего счета в любое время.
 
-We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
+Мы рекомендуем переоценить количество запросов, чтобы Вам не приходилось часто пополнять баланс. Хорошей оценкой для небольших и средних приложений будет начать с 1–2 млн запросов в месяц и внимательно следить за использованием в первые недели. Для более крупных приложений хорошей оценкой будет использовать количество ежедневных посещений Вашего сайта, умноженное на количество запросов, которые делает Ваша самая активная страница при открытии.
 
-Of course, both new and existing users can reach out to Edge & Node's BD team for a consult to learn more about anticipated usage.
+Разумеется, как новые, так и старые пользователи могут обратиться к команде BD Edge & Node за консультацией, чтобы узнать больше о предполагаемом использовании.
 
-### Can I withdraw GRT from my billing balance?
+### Могу ли я вывести GRT со своего платежного баланса?
 
-Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
+Да, Вы всегда можете вывести GRT, которые еще не были использованы для запросов, с Вашего баланса. Контракт на выставление счетов предназначен только для моста GRT из основной сети Ethereum в сеть Arbitrum. Если Вы хотите перенести свой GRT из Arbitrum обратно в сеть Ethereum, Вам необходимо использовать [Мост Arbitrum](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### Что произойдет, когда мой платежный баланс закончится? Получу ли я предупреждение?
 
-You will receive several email notifications before your billing balance runs out.
+Вы получите несколько уведомлений по электронной почте перед тем, как Ваш платежный баланс обнулится.

From 5c7ca7a2a1dc3b100fbb47aac4d7c2a2feaa8fa7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:17 -0500
Subject: [PATCH 0918/1325] New translations billing.mdx (Swedish)

---
 website/pages/sv/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/sv/billing.mdx b/website/pages/sv/billing.mdx
index 96e596687dea..5c12aa5cd9c1 100644
--- a/website/pages/sv/billing.mdx
+++ b/website/pages/sv/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Klicka på knappen "Anslut plånbok" längst upp till höger på sidan. Du kommer att omdirigeras till sidan för plånboksval. Välj din plånbok och klicka på "Anslut".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ Du kan lära dig mer om att få ETH på Binance [här](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From b933f80bad5761dadfd81088117b876edc944460 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:18 -0500
Subject: [PATCH 0919/1325] New translations billing.mdx (Turkish)

---
 website/pages/tr/billing.mdx | 268 +++++++++++++++++------------------
 1 file changed, 134 insertions(+), 134 deletions(-)

diff --git a/website/pages/tr/billing.mdx b/website/pages/tr/billing.mdx
index b2faf34d0b49..43d51514645f 100644
--- a/website/pages/tr/billing.mdx
+++ b/website/pages/tr/billing.mdx
@@ -2,174 +2,174 @@
 title: Faturalandırma
 ---
 
-## Subgraph Billing Plans
+## Subgraph Faturalama Planları
 
-There are two plans to use when querying subgraphs on The Graph Network.
+The Graph Ağı'nda subgraph'leri sorgulamak için kullanabileceğiniz iki plan bulunmaktadır.
 
-- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling their dapp.
+- **Ücretsiz Plan**: Ücretsiz Plan, Subgraph Studio test ortamına tam erişim ile birlikte aylık 100.000 ücretsiz sorgu içerir. Bu plan, dapp'lerini ölçeklendirmeden önce The Graph'i denemek isteyen hobi meraklıları, hackathon katılımcıları ve yan projeleri olan kişiler için tasarlanmıştır.
 
-- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card. The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+- **Büyüme Planı**: Büyüme Planı, Ücretsiz Plan'daki her özelliği içerir ve aylık 100.000 sorgudan sonraki tüm sorgular için GRT veya kredi kartı ile ödeme gerektirir. Büyüme Planı, çeşitli kullanım senaryolarına sahip dapp'leri ölçeklendirmek isteyen ekipler için yeterli esnekliği sunar.
 
 <VideoEmbed youtube="Nn771WagX2I" />
 
-## Query Payments with credit card
+## Kredi kartı ile sorgu ödemeleri
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
-  1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+- Kredi/banka kartları ile faturalandırmayı ayarlamak için, kullanıcıların Subgraph Studio'ya (https://thegraph.com/studio/) erişmeleri gerekir
+  1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/billing/).
   2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdan seçim sayfasına yönlendirileceksiniz. Cüzdanınızı seçin ve "Bağlan" a tıklayın.
-  3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
-  4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details.
-- Invoices will be processed at the end of each month and require an active credit card on file for all queries beyond the free plan quota.
+  3. Ücretsiz Plan'dan yükseltme yapıyorsanız "Planı Yükselt" seçeneğini, daha önce faturalandırma bakiyenize GRT eklediyseniz "Planı Yönet" seçeneğini seçin. Sonrasında, sorgu sayısını tahmin ederek bir fiyat tahmini alabilirsiniz, ancak bu zorunlu bir adım değildir.
+  4. Kredi kartı ödemesini seçmek için, ödeme yöntemi olarak "Kredi kartı" seçeneğini seçin ve kredi kartı bilgilerinizi doldurun. Daha önce Stripe kullananlar, bilgilerini otomatik doldurmak için Link özelliğini kullanabilirler.
+- Faturalar her ayın sonunda işlenecek ve Ücretsiz Plan kotasını aşan tüm sorgular için sistemde aktif bir kredi kartı bulunması gerekecektir.
 
-## Query Payments with GRT
+## GRT ile Sorgu Ödemeleri
 
-Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph Network. With GRT, invoices will be processed at the end of each month and require a sufficient balance of GRT to make queries beyond the Free Plan quota of 100,000 monthly queries. You'll be required to pay fees generated from your API keys. Using the billing contract, you'll be able to:
+Subgraph kullanıcıları, The Graph Ağında sorgular için ödeme yapmak amacıyla The Graph Token (GRT) kullanabilirler. GRT ile faturalar her ayın sonunda işlenecek ve 100.000 aylık sorgu limiti olan Ücretsiz Plan kotasının ötesindeki sorgular için yeterli GRT bakiyesi bulunması gerekecek. API anahtarlarınızdan kaynaklanan ücretleri ödemeniz gerekecek. Faturalandırma sözleşmesini kullanarak şunları yapabileceksiniz:
 
 - Hesap bakiyenizden GRT ekleyin ve çekin.
 - Hesap bakiyenize ne kadar GRT eklediğiniz, ne kadar çektiğiniz ve faturalarınıza göre bakiyelerinizi takip edin.
 - Hesap bakiyenizde yeterli GRT olduğu sürece, oluşturulan sorgu ücretlerine göre faturaları otomatik olarak ödeyin.
 
-### GRT on Arbitrum or Ethereum
+### Ethereum ya da Arbitrum Ağında GRT
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+The Graph'in faturalandırma sistemi, Arbitrum ağı üzerinde GRT ile ödeme alır. Kullanıcıların gas ücretlerini ödemek için Arbitrum üzerinde ETH'ye ihtiyaçları olacaktır. The Graph protokolü, başlangıçta Ethereum Mainnet üzerinde başlatılmış olsa da, faturalandırma sözleşmeleri de dahil olmak üzere tüm faaliyetler artık Arbitrum One üzerinde gerçekleştirilmektedir.
 
-To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Sorgu ödemelerini yapmak için Arbitrum üzerinde GRT'ye ihtiyacınız var. İşte GRT elde etmenin birkaç farklı yolu:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Ethereum üzerinde zaten GRT'niz varsa, bunu Arbitrum'a köprüleyebilirsiniz. Bunu, Subgraph Studio'da sunulan GRT köprüleme seçeneği aracılığıyla veya aşağıdaki köprülerden birini kullanarak yapabilirsiniz:
 
-- [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+- [Arbitrum Köprüsü](https://bridge.arbitrum.io/?l2ChainId=42161)
 - [TransferTo](https://transferto.xyz/swap)
 
-- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap.
+- Arbitrum üzerinde zaten varlıklarınız varsa, Uniswap gibi bir takas protokolü aracılığıyla bunları GRT ile takas edebilirsiniz.
 
-- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange.
+- Alternatif olarak, GRT'yi doğrudan Arbitrum üzerinde merkeziyetsiz bir borsa aracılığıyla edinebilirsiniz.
 
-> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
+> Bu bölüm, cüzdanınızda zaten GRT bulunduğu ve Arbitrum üzerinde olduğunuz varsayılarak yazılmıştır. Eğer GRT'niz yoksa, nasıl GRT edinebileceğinizi [buradan](#getting-grt) öğrenebilirsiniz.
 
-Once you bridge GRT, you can add it to your billing balance.
+GRT'yi köprüledikten sonra faturalandırma bakiyenize ekleyebilirsiniz.
 
-### Adding GRT using a wallet
+### Bir cüzdan kullanarak GRT ekleme
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/billing/).
 2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdan seçim sayfasına yönlendirileceksiniz. Cüzdanınızı seçin ve "Bağlan" a tıklayın.
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable.
-8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-9. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
-
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
-
-### Withdrawing GRT using a wallet
-
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
-4. Enter the amount of GRT you would like to withdraw.
-5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
-6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
+3. Sağ üst köşedeki 'Yönet' düğmesine tıklayın. İlk kez kullanıyorsanız 'Büyüme Planına Yükselt' seçeneğini göreceksiniz. Daha önce işlem yaptıysanız 'Cüzdandan Yatır' seçeneğine tıklayın.
+4. Kaydırıcıyı kullanarak aylık olarak yapmayı beklediğiniz sorgu sayısını tahmin edin.
+   - Aylık sorgu sayısı hakkında öneriler almak için **Sıkça Sorulan Sorular** sayfamıza göz atın.
+5. "Kriptopara" seçeneğini seçin. Şu anda The Graph Ağı'nda kabul edilen tek kriptopara GRT'dir.
+6. Peşin ödeme yapmak istediğiniz ay sayısını seçin.
+   - Peşin ödeme yapmak, gelecekte kullanım zorunluluğu getirmez. Yalnızca kullandığınız kadar ücretlendirilirsiniz ve bakiyenizi istediğiniz zaman çekebilirsiniz.
+7. GRT yatıracağınız ağı seçin. Arbitrum veya Ethereum üzerindeki GRT kabul edilmektedir.
+8. "Allow GRT Access" düğmesine tıklayın ve ardından cüzdanınızdan çekilebilecek GRT miktarını belirtin.
+   - Eğer birden fazla ay için peşin ödeme yapıyorsanız, o tutara karşılık gelen miktar için erişime izin vermelisiniz. Bu işlem herhangi bir gas ücreti gerektirmez.
+9. Son olarak, "GRT'yi Faturalandırma Bakiyesine Ekle" düğmesine tıklayın. Bu işlem için gas ücretlerini karşılamak üzere Arbitrum üzerinde ETH'ye ihtiyacınız olacak.
+
+- Arbitrum'dan yatırılan GRT'nin işlenmesi birkaç dakika içinde tamamlanırken, Ethereum'dan yatırılan GRT'nin işlenmesi yaklaşık 15-20 dakika sürecektir. İşlem onaylandıktan sonra GRT'nin hesap bakiyenize eklendiğini göreceksiniz.
+
+### Bir cüzdan kullanarak GRT çekme
+
+1. Subgraph Studio Faturalandırma sayfasına gitmek için  [buraya tıklayın](https://thegraph.com/studio/billing/).
+2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdanınızı seçin ve "Bağlan" düğmesine tıklayın.
+3. Sayfanın sağ üst köşesindeki "Yönet" düğmesine tıklayın. "GRT Çek" seçeneğini seçin. Bir yan panel açılacaktır.
+4. Çekmek istediğiniz GRT miktarını girin.
+5. "Çek GRT" düğmesine tıklayarak GRT'yi hesap bakiyenizden çekin. İlgili işlemi cüzdanınızda imzalayın. Bu işlem gas ücreti gerektirecektir. GRT, Arbitrum cüzdanınıza gönderilecektir.
+6. İşlem onaylandıktan sonra, GRT'nin hesap bakiyenizden çekildiğini ve Arbitrum cüzdanınıza aktarıldığını göreceksiniz.
 
 ### Multisig cüzdanı kullanarak GRT ekleme
 
-1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
-2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas.
-3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
-4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
-   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
-5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
-6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
-7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
-   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
-8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+1. Subgraph Studio Faturalandırma sayfasına gitmek için [buraya tıklayın](https://thegraph.com/studio/billing/).
+2. Sayfanın sağ üst köşesindeki "Cüzdanı Bağla" düğmesine tıklayın. Cüzdanınızı seçin ve "Bağlan" düğmesine tıklayın. Eğer [Gnosis-Safe](https://gnosis-safe.io/) kullanıyorsanız, multisig cüzdanınızı ve imza cüzdanınızı da bağlayabileceksiniz. Ardından ilgili mesajı imzalayın. Bu işlem gas ücreti gerektirmeyecektir.
+3. Sağ üst köşedeki 'Yönet' düğmesine tıklayın. İlk kez kullanıyorsanız 'Büyüme Planına Yükselt' seçeneğini göreceksiniz. Daha önce işlem yaptıysanız 'Cüzdandan Yatır' seçeneğine tıklayın.
+4. Kaydırıcıyı kullanarak aylık olarak yapmayı beklediğiniz sorgu sayısını tahmin edin.
+   - Aylık sorgu sayısı hakkında öneriler almak için **Sıkça Sorulan Sorular** sayfamıza göz atın.
+5. "Kriptopara" seçeneğini seçin. Şu anda The Graph Ağı'nda kabul edilen tek kriptopara GRT'dir.
+6. Peşin ödeme yapmak istediğiniz ay sayısını seçin.
+   - Peşin ödeme yapmak, gelecekte kullanım zorunluluğu getirmez. Yalnızca kullandığınız kadar ücretlendirilirsiniz ve bakiyenizi istediğiniz zaman çekebilirsiniz.
+7. GRT yatıracağınız ağı seçin. Arbitrum veya Ethereum üzerindeki GRT kabul edilmektedir. 8. "GRT Erişimine İzin Ver" düğmesine tıklayın ve ardından cüzdanınızdan çekilebilecek GRT miktarını belirtin.
+   - Eğer birden fazla ay için peşin ödeme yapıyorsanız, o tutara karşılık gelen miktar için erişime izin vermelisiniz. Bu işlem herhangi bir gas ücreti gerektirmez.
+8. Son olarak, "GRT'yi Faturalandırma Bakiyesine Ekle" düğmesine tıklayın. Bu işlem için gas ücretlerini karşılamak üzere Arbitrum üzerinde ETH'ye ihtiyacınız olacak.
 
-- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+- Arbitrum'dan yatırılan GRT'nin işlenmesi birkaç dakika içinde tamamlanırken, Ethereum'dan yatırılan GRT'nin işlenmesi yaklaşık 15-20 dakika sürecektir. İşlem onaylandıktan sonra GRT'nin hesap bakiyenize eklendiğini göreceksiniz.
 
-## Getting GRT
+## GRT Edinme
 
-This section will show you how to get GRT to pay for query fees.
+Bu bölüm, sorgu ücretlerini ödemek için nasıl GRT edinebileceğinizi anlatacaktır.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing GRT on Coinbase.
+Bu kılavuz, Coinbase üzerinden GRT satın alma işlemini adım adım açıklayacaktır.
 
-1. Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page.
-4. Select the currency you want to purchase. Select GRT.
-5. Select the payment method. Select your preferred payment method.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase. Review your purchase and click "Buy GRT".
-8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT.
-9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page.
-   - Click on the "Send" button next to the GRT account.
-   - Enter the amount of GRT you want to send and the wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction. -Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet.
+1. [Coinbase](https://www.coinbase.com/)'e gidin ve bir hesap oluşturun.
+2. Bir hesap oluşturduktan sonra, kimliğinizi KYC (Müşterini Tanı) olarak bilinen bir süreçle doğrulamanız gerekecek. KYC, tüm merkezi veya emanetçi kripto borsaları için standart bir prosedürdür.
+3. Kimliğinizi doğruladıktan sonra GRT satın alabilirsiniz. Bunu sayfanın sağ üst köşesindeki "Al/Sat" düğmesine tıklayarak yapabilirsiniz.
+4. Satın almak istediğiniz para birimini seçin. GRT'yi seçin.
+5. Ödeme yöntemini seçin. Tercih ettiğiniz ödeme yöntemini seçin.
+6. Satın almak istediğiniz GRT miktarını seçin.
+7. Satın alımınızı gözden geçirin. Satın alımınızı gözden geçirin ve "GRT Satın Al" düğmesine tıklayın.
+8. Satın alımınızı onaylayın. Satın alımınızı onaylayın, böylece başarılı bir şekilde GRT satın almış olacaksınız.
+9. GRT'yi hesabınızdan [MetaMask](https://metamask.io/) gibi bir cüzdana transfer edebilirsiniz.
+   - GRT'yi cüzdanınıza transfer etmek için, sayfanın sağ üst köşesindeki "Hesaplar" düğmesine tıklayın.
+   - GRT hesabının yanındaki "Gönder" düğmesine tıklayın.
+   - Göndermek istediğiniz GRT miktarını ve göndermek istediğiniz cüzdan adresini girin.
+   - "Devam" düğmesine tıklayın ve işleminizi onaylayın. -Lütfen unutmayın, yüksek tutarda satın alım durumunda Coinbase, tam tutarı bir cüzdana transfer etmeden önce 7-10 gün beklemenizi isteyebilir.
 
-You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+Coinbase üzerinden GRT edinme hakkında daha fazla bilgiye [buradan](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency) ulaşabilirsiniz.
 
 ### Binance
 
-This will be a step by step guide for purchasing GRT on Binance.
+Bu kılavuz, Binance üzerinden GRT satın alma işlemini adım adım açıklayacaktır.
 
-1. Go to [Binance](https://www.binance.com/en) and create an account.
-2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner.
-4. You will be taken to a page where you can select the currency you want to purchase. Select GRT.
-5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more.
-6. Select the amount of GRT you want to purchase.
-7. Review your purchase and click "Buy GRT".
-8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
-9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
-   - Click on the "wallet" button, click withdraw, and select GRT.
-   - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
-   - Click "Continue" and confirm your transaction.
+1. [Binance](https://www.binance.com/en)e gidin ve bir hesap oluşturun.
+2. Bir hesap oluşturduktan sonra, kimliğinizi KYC (Müşterini Tanı) olarak bilinen bir süreçle doğrulamanız gerekecek. KYC, tüm merkezi veya emanetçi kripto borsaları için standart bir prosedürdür.
+3. Kimliğinizi doğruladıktan sonra GRT satın alabilirsiniz. Bunu, ana sayfa banner'ındaki "Şimdi Satın Al" düğmesine tıklayarak yapabilirsiniz.
+4. Satın almak istediğiniz para birimini seçebileceğiniz bir sayfaya yönlendirileceksiniz. GRT'yi seçin.
+5. Tercih ettiğiniz ödeme yöntemini seçin. Euro, ABD Doları ve diğer birçok itibari para birimiyle ödeme yapabileceksiniz.
+6. Satın almak istediğiniz GRT miktarını seçin.
+7. Satın alımınızı gözden geçirin ve "GRT Satın Al" düğmesine tıklayın.
+8. Satın alımınızı onaylayın, ardından GRT'nizi Binance Spot Cüzdanınızda görüntüleyebilirsiniz.
+9. GRT'yi hesabınızdan [MetaMask](https://metamask.io/) gibi bir cüzdana çekebilirsiniz.
+   - GRT'yi cüzdanınıza çekmek için cüzdan adresinizi çekim beyaz listesine ekleyin. Daha fazla bilgi için [buraya tıklayın](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570).
+   - "Cüzdan" düğmesine tıklayın, ardından "Çekim" seçeneğine tıklayın ve GRT'yi seçin.
+   - Göndermek istediğiniz GRT miktarını ve beyaz listeye eklenmiş cüzdan adresini girin.
+   - "Devam" düğmesine tıklayın ve işleminizi onaylayın.
 
-You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+Binance üzerinde GRT edinme hakkında daha fazla bilgiye [buradan](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582) ulaşabilirsiniz.
 
 ### Uniswap
 
-This is how you can purchase GRT on Uniswap.
+Bu kılavuz, Uniswap üzerinden GRT satın alma işlemini adım adım açıklayacaktır.
 
-1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet.
-2. Select the token you want to swap from. Select ETH.
-3. Select the token you want to swap to. Select GRT.
-   - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
-4. Enter the amount of ETH you want to swap.
-5. Click "Swap".
-6. Confirm the transaction in your wallet and you wait for the transaction to process.
+1. [Uniswap](https://app.uniswap.org/swap?chain=arbitrum)'e gidin ve cüzdanınızı bağlayın.
+2. Baz para birimi olarak kullanılacak token'ı seçin. ETH'yi seçin.
+3. Satın almak istediğiniz token'ı seçin. GRT'yi seçin.
+   - Doğru token'a takas ettiğinizden emin olun. Arbitrum One üzerindeki GRT akıllı sözleşme adresi: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+4. Takas etmek istediğiniz ETH miktarını girin.
+5. "Swap" butonuna tıklayın.
+6. İşlemi cüzdanınızda onaylayın ve işlemin tamamlanmasını bekleyin.
 
-You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
+Uniswap üzerinden GRT edinme hakkında daha fazla bilgiye [buradan](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-) ulaşabilirsiniz.
 
-## Getting Ether
+## Ether Edinme
 
-This section will show you how to get Ether (ETH) to pay for transaction fees or gas costs. ETH is necessary to execute operations on the Ethereum network such as transferring tokens or interacting with contracts.
+Bu bölüm, işlem ücretlerini veya gas maliyetlerini ödemek için nasıl Ether (ETH) edinebileceğinizi anlatacaktır. Ethereum ağı üzerinde token transferi yapmak veya akıllı sözleşmelerle etkileşime geçmek gibi işlemleri gerçekleştirmek için ETH gereklidir.
 
 ### Coinbase
 
-This will be a step by step guide for purchasing ETH on Coinbase.
-
-1.  Go to [Coinbase](https://www.coinbase.com/) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
-3.  Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
-8.  Confirm your purchase and you will have successfully purchased ETH.
-9.  You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/).
-    - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page.
-    - Click on the "Send" button next to the ETH account.
-    - Enter the amount of ETH you want to send and the wallet address you want to send it to.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
-    - Click "Continue" and confirm your transaction.
+Bu kılavuz, Coinbase üzerinden ETH satın alma işlemini adım adım açıklayacaktır.
+
+1.  [Coinbase](https://www.coinbase.com/)'e gidin ve bir hesap oluşturun.
+2.  Bir hesap oluşturduktan sonra, kimliğinizi KYC (Müşterini Tanı) olarak bilinen bir süreçle doğrulamanız gerekecek. Bu, tüm merkezi veya emanetçi kripto borsaları için standart bir prosedürdür.
+3.  Kimliğinizi doğruladıktan sonra, sayfanın sağ üst köşesindeki "Al/Sat" düğmesine tıklayarak ETH satın alın.
+4.  Satın almak istediğiniz para birimini seçin. ETH seçin.
+5.  Tercih ettiğiniz ödeme yöntemini seçin.
+6.  Satın almak istediğiniz ETH miktarını girin.
+7.  Satın alımınızı gözden geçirin ve "ETH Satın Al" düğmesine tıklayın.
+8.  Satın alımınızı onaylayın, böylece ETH'yi başarıyla satın almış olacaksınız.
+9.  ETH'yi hesabınızdan [MetaMask](https://metamask.io/) gibi bir cüzdana transfer edebilirsiniz.
+    - ETH'yi cüzdanınıza transfer etmek için, sayfanın sağ üst köşesindeki "Hesaplar" düğmesine tıklayın.
+    - ETH hesabının yanındaki "Gönder" düğmesine tıklayın.
+    - Göndermek istediğiniz ETH miktarını ve göndermek istediğiniz cüzdan adresini girin.
+    - Gönderdiğiniz adresin Arbitrum One üzerindeki Ethereum cüzdan adresiniz olduğundan emin olun.
+    - "Devam" düğmesine tıklayın ve işleminizi onaylayın.
 
 Coinbase'de ETH edinmekle alakalı daha fazla bilgiyi [buradan](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency) öğrenebilirsiniz.
 
@@ -177,37 +177,37 @@ Coinbase'de ETH edinmekle alakalı daha fazla bilgiyi [buradan](https://help.coi
 
 Bu, Binance'de ETH satın almak için adım adım bir rehberdir.
 
-1.  Go to [Binance](https://www.binance.com/en) and create an account.
-2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
+1.  [Binance](https://www.binance.com/en)e gidin ve bir hesap oluşturun.
+2.  Bir hesap oluşturduktan sonra, kimliğinizi KYC (Müşterini Tanı) olarak bilinen bir süreçle doğrulamanız gerekecek. Bu, tüm merkezi veya emanetçi kripto borsaları için standart bir prosedürdür.
 3.  Kimliğinizi doğruladıktan sonra, ana sayfa afişindeki "Şimdi Satın Al" düğmesine tıklayarak ETH satın alın.
-4.  Select the currency you want to purchase. Select ETH.
-5.  Select your preferred payment method.
-6.  Enter the amount of ETH you want to purchase.
-7.  Review your purchase and click "Buy ETH".
+4.  Satın almak istediğiniz para birimini seçin. ETH seçin.
+5.  Tercih ettiğiniz ödeme yöntemini seçin.
+6.  Satın almak istediğiniz ETH miktarını girin.
+7.  Satın alımınızı gözden geçirin ve "ETH Satın Al" düğmesine tıklayın.
 8.  Satın alımınızı onaylayın ve ETH'nizi Binance Spot Cüzdanınızda görüceksiniz.
-9.  You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/).
-    - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist.
+9.  ETH'yi hesabınızdan [MetaMask](https://metamask.io/) gibi bir cüzdana çekebilirsiniz.
+    - ETH'yi cüzdanınıza çekmek için cüzdan adresinizi çekim beyaz listesine ekleyin. Daha fazla bilgi için buraya tıklayın.
     - "Cüzdan" düğmesine tıklayın, para çekme seçeneğine tıklayın ve ETH'yi seçin.
     - Göndermek istediğiniz ETH miktarını ve göndermek istediğiniz güvenilir adresler listesindeki cüzdan adresini girin.
-    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
-    - Click "Continue" and confirm your transaction.
+    - Gönderdiğiniz adresin Arbitrum One üzerindeki Ethereum cüzdan adresiniz olduğundan emin olun.
+    - "Devam" düğmesine tıklayın ve işleminizi onaylayın.
 
 Binance'de ETH edinmekle alakalı daha fazla bilgiyi [buradan](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582) öğrenebilirsiniz.
 
-## Billing FAQs
+## Faturalandırma Hakkında SSS
 
-### How many queries will I need?
+### Kaç sorguya ihtiyacım olacak?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+Kaç sorguya ihtiyacınız olacağını önceden bilmeniz gerekmez. Yalnızca kullandığınız kadar ücretlendirilirsiniz ve istediğiniz zaman hesabınızdan GRT çekebilirsiniz.
 
-We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
+Sorgu sayısını fazla tahmin etmenizi öneririz, böylece bakiyenizi sık sık doldurmak zorunda kalmazsınız. Küçük ve orta ölçekli uygulamalar için iyi bir başlangıç tahmini, aylık 1M-2M sorgu ile başlamak ve ilk haftalarda kullanımı yakından izlemektir. Daha büyük uygulamalar için iyi bir tahmin, sitenizin günlük ziyaret sayısını, en aktif sayfanızın açılışta yaptığı sorgu sayısı ile çarpmaktır.
 
-Of course, both new and existing users can reach out to Edge & Node's BD team for a consult to learn more about anticipated usage.
+Elbette, hem yeni hem de mevcut kullanıcılar, beklenen kullanım hakkında daha fazla bilgi almak için Edge & Node'un İş Geliştirme (BD) ekibiyle iletişime geçebilirler.
 
-### Can I withdraw GRT from my billing balance?
+### Faturalandırma bakiyemden GRT çekebilir miyim?
 
-Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
+Evet, faturalandırma bakiyenizde sorgularda kullanılmamış olan GRT'yi her zaman çekebilirsiniz. Faturalandırma sözleşmesi yalnızca GRT'yi Ethereum ana ağından Arbitrum ağına bağlamak için tasarlanmıştır. GRT'nizi Arbitrum'dan tekrar Ethereum ana ağına aktarmak isterseniz, [Arbitrum Köprüsü](https://bridge.arbitrum.io/?l2ChainId=42161)'nü kullanmanız gerekir.
 
-### What happens when my billing balance runs? Will I get a warning?
+### Faturalandırma bakiyem tükendiğinde ne olur? Bir uyarı alacak mıyım?
 
-You will receive several email notifications before your billing balance runs out.
+Faturalandırma bakiyeniz tükenmeden önce birkaç e-posta bildirimi alacaksınız.

From f393c593472b193827c5689bbb21b6b2589958f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:19 -0500
Subject: [PATCH 0920/1325] New translations billing.mdx (Ukrainian)

---
 website/pages/uk/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/uk/billing.mdx b/website/pages/uk/billing.mdx
index 47467e108558..b6e73127d865 100644
--- a/website/pages/uk/billing.mdx
+++ b/website/pages/uk/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Натисніть на кнопку "Connect Wallet" у правому верхньому куті сторінки. Ви будете перенаправлені на сторінку вибору гаманця. Виберіть той, який вам підходить, і натисніть кнопку "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 38fe9c1724ea190e838e8fccf97193e3a2653576 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:20 -0500
Subject: [PATCH 0921/1325] New translations billing.mdx (Chinese Simplified)

---
 website/pages/zh/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/zh/billing.mdx b/website/pages/zh/billing.mdx
index 894302b4aa9b..8d63ddec5ba1 100644
--- a/website/pages/zh/billing.mdx
+++ b/website/pages/zh/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. 单击页面右上角的“Connect Wallet”（连接钱包）按钮。您将被重定向到钱包选择页面。选择您的钱包，然后单击“Connect”（连接）。
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 5b2371a92024d623af3762adf7e0e9f7dd9dc436 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:21 -0500
Subject: [PATCH 0922/1325] New translations billing.mdx (Urdu (Pakistan))

---
 website/pages/ur/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ur/billing.mdx b/website/pages/ur/billing.mdx
index cc192cfe227b..95164e556c2c 100644
--- a/website/pages/ur/billing.mdx
+++ b/website/pages/ur/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. صفحہ کے اوپری دائیں کونے میں "کنیکٹ والیٹ" بٹن پر کلک کریں۔ آپ کو والیٹ کے انتخاب کے صفحہ پر بھیج دیا جائے گا۔ اپنا والیٹ منتخب کریں اور "کنیکٹ" پر کلک کریں.
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ This will be a step by step guide for purchasing ETH on Coinbase.
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 4f02f670f2cc96b2a87741e72f2c4d17b3010922 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:23 -0500
Subject: [PATCH 0923/1325] New translations billing.mdx (Vietnamese)

---
 website/pages/vi/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/vi/billing.mdx b/website/pages/vi/billing.mdx
index 37f9c840d00b..dec5cfdadc12 100644
--- a/website/pages/vi/billing.mdx
+++ b/website/pages/vi/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From cf317b4bad968b590fc6369ab637a2d179a2ccf6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:24 -0500
Subject: [PATCH 0924/1325] New translations billing.mdx (Marathi)

---
 website/pages/mr/billing.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/mr/billing.mdx b/website/pages/mr/billing.mdx
index 26457c03358f..63430377cc61 100644
--- a/website/pages/mr/billing.mdx
+++ b/website/pages/mr/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. पृष्ठाच्या वरच्या उजव्या कोपर्यात "कनेक्ट वॉलेट" बटणावर क्लिक करा. तुम्हाला वॉलेट निवड पृष्ठावर पुनर्निर्देशित केले जाईल. तुमचे वॉलेट निवडा आणि "कनेक्ट" वर क्लिक करा.
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### What happens when my billing balance runs out? Will I get a warning?
 
 You will receive several email notifications before your billing balance runs out.

From 1bfab1e3f587f202b0c7ec87e8c805f3eff75158 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:25 -0500
Subject: [PATCH 0925/1325] New translations billing.mdx (Hindi)

---
 website/pages/hi/billing.mdx | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/website/pages/hi/billing.mdx b/website/pages/hi/billing.mdx
index d6377dbf57be..d67ec53497ca 100644
--- a/website/pages/hi/billing.mdx
+++ b/website/pages/hi/billing.mdx
@@ -14,7 +14,7 @@ There are two plans to use when querying subgraphs on The Graph Network.
 
 ## Query Payments with credit card
 
-- To set up billing with credit/debit cards, users will access Subgraph Studio (https://thegraph.com/studio/)
+- क्रेडिट/डेबिट कार्ड के साथ बिलिंग सेट करने के लिए, उपयोगकर्ताओं को **Subgraph Studio** (https://thegraph.com/studio/) पर जाना चाहिए।
   1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
   2. पृष्ठ के ऊपरी दाएं कोने पर "कनेक्ट वॉलेट" बटन पर क्लिक करें। आपको बटुआ चयन पृष्ठ पर पुनर्निर्देशित किया जाएगा। अपना बटुआ चुनें और "कनेक्ट" पर क्लिक करें।
   3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
@@ -31,22 +31,22 @@ Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph
 
 ### GRT on Arbitrum or Ethereum
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+The Graph का बिलिंग सिस्टम Arbitrum पर GRT को स्वीकार करता है, और उपयोगकर्ताओं को गैस के भुगतान के लिए Arbitrum  पर ETH की आवश्यकता होगी। जबकि The Graph प्रोटोकॉल Ethereum Mainnet पर शुरू हुआ, सभी गतिविधियाँ, जिसमें बिलिंग कॉन्ट्रैक्ट्स भी शामिल हैं, अब Arbitrum One पर हैं।
 
-To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+क्वेरियों के लिए भुगतान करने के लिए, आपको Arbitrum पर GRT की आवश्यकता है। इसे प्राप्त करने के लिए कुछ विभिन्न तरीके यहां दिए गए हैं:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- यदि आपके पास पहले से  Ethereum पर GRT है, तो आप इसे Arbitrum पर ब्रिज कर सकते हैं। आप यह Subgraph Studio में प्रदान किए गए GRT ब्रिजिंग विकल्प के माध्यम से या निम्नलिखित में से किसी एक ब्रिज का उपयोग करके कर सकते हैं:
 
 - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
 - [TransferTo](https://transferto.xyz/swap)
 
-- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap.
+- यदि आपके पास पहले से Arbitrum पर संपत्तियाँ हैं, तो आप उन्हें Uniswap जैसे स्वैपिंग प्रोटोकॉल के माध्यम से GRT के लिए स्वैप कर सकते हैं।
 
-- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange.
+- वैकल्पिक रूप से, आप एक विकेंद्रीकृत एक्सचेंज के माध्यम से Arbitrum पर सीधे GRT प्राप्त कर सकते हैं।
 
-> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
+> यह अनुभाग इस धारणा के तहत लिखा गया है कि आपके पास पहले से ही अपने वॉलेट में **GRT** है, और आप **Arbitrum** पर हैं। यदि आपके पास **GRT** नहीं है, तो आप **यहाँ** [जान सकते हैं कि GRT कैसे प्राप्त करें](#getting-grt)।
 
-Once you bridge GRT, you can add it to your billing balance.
+एक बार जब आप GRT को ब्रिज करते हैं, तो आप इसे अपने बिलिंग बैलेंस में जोड़ सकते हैं।
 
 ### Adding GRT using a wallet
 
@@ -69,7 +69,7 @@ Once you bridge GRT, you can add it to your billing balance.
 
 1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
 2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
-3. Click the "Manage"" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+3. पृष्ठ के ऊपरी दाएं कोने में "मैनेज" बटन पर क्लिक करें। "GRT निकालें" चुनें। एक साइड पैनल दिखाई देगा।
 4. Enter the amount of GRT you would like to withdraw.
 5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
 6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
@@ -83,7 +83,7 @@ Once you bridge GRT, you can add it to your billing balance.
    - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
 5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
 6. Select the number of months you would like to prepay.
-   - Paying in advance does not committing you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
 7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
    - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
 8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
@@ -127,7 +127,7 @@ This will be a step by step guide for purchasing GRT on Binance.
 7. Review your purchase and click "Buy GRT".
 8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
 9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
-   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawel whitelist.
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) GRT को अपने वॉलेट में, निकासी श्वेतसूची में अपने वॉलेट का पता जोड़ें।
    - Click on the "wallet" button, click withdraw, and select GRT.
    - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
    - Click "Continue" and confirm your transaction.
@@ -198,7 +198,7 @@ You can learn more about getting ETH on Binance [here](https://www.binance.com/e
 
 ### How many queries will I need?
 
-You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdrawal GRT from your account at any time.
+आपको यह पहले से नहीं जानना होगा कि आपको कितनी क्वेरीज़ की आवश्यकता होगी। आपको केवल उसी के लिए चार्ज किया जाएगा जो आप उपयोग करते हैं, और आप कभी भी अपने खाते से GRT निकाल सकते हैं।
 
 We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
 
@@ -208,6 +208,6 @@ Of course, both new and existing users can reach out to Edge & Node's BD team fo
 
 Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
 
-### What happens when my billing balance runs? Will I get a warning?
+### जब मेरा बिलिंग बैलेंस खत्म हो जाता है, तो क्या होगा? क्या मुझे कोई चेतावनी मिलेगी?
 
 You will receive several email notifications before your billing balance runs out.

From 2baed17c378a9632743135093471747ca2531329 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:26 -0500
Subject: [PATCH 0926/1325] New translations billing.mdx (Swahili)

---
 website/pages/sw/billing.mdx | 213 +++++++++++++++++++++++++++++++++++
 1 file changed, 213 insertions(+)
 create mode 100644 website/pages/sw/billing.mdx

diff --git a/website/pages/sw/billing.mdx b/website/pages/sw/billing.mdx
new file mode 100644
index 000000000000..dec5cfdadc12
--- /dev/null
+++ b/website/pages/sw/billing.mdx
@@ -0,0 +1,213 @@
+---
+title: Billing
+---
+
+## Subgraph Billing Plans
+
+There are two plans to use when querying subgraphs on The Graph Network.
+
+- **Free Plan**: The Free Plan includes 100,000 free monthly queries with full access to the Subgraph Studio testing environment. This plan is designed for hobbyists, hackathoners, and those with side projects to try out The Graph before scaling their dapp.
+
+- **Growth Plan**: The Growth Plan includes everything in the Free Plan with all queries after 100,000 monthly queries requiring payments with GRT or credit card. The Growth Plan is flexible enough to cover teams that have established dapps across a variety of use cases.
+
+<VideoEmbed youtube="Nn771WagX2I" />
+
+## Query Payments with credit card
+
+- To set up billing with credit/debit cards, users should access Subgraph Studio (https://thegraph.com/studio/)
+  1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+  2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
+  3. Choose “Upgrade plan” if you are upgrading from the Free Plan or choose “Manage Plan” if you have already added GRT to your billing balance in the past. Next, you can estimate the number of queries to get a pricing estimate, but this is not a required step.
+  4. To choose a credit card payment, choose “Credit card” as the payment method and fill out your credit card information. Those who have used Stripe before can use the Link feature to autofill their details.
+- Invoices will be processed at the end of each month and require an active credit card on file for all queries beyond the free plan quota.
+
+## Query Payments with GRT
+
+Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph Network. With GRT, invoices will be processed at the end of each month and require a sufficient balance of GRT to make queries beyond the Free Plan quota of 100,000 monthly queries. You'll be required to pay fees generated from your API keys. Using the billing contract, you'll be able to:
+
+- Add and withdraw GRT from your account balance.
+- Keep track of your balances based on how much GRT you have added to your account balance, how much you have removed, and your invoices.
+- Automatically pay invoices based on query fees generated, as long as there is enough GRT in your account balance.
+
+### GRT on Arbitrum or Ethereum
+
+The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+
+To pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+
+- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+
+- [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+- [TransferTo](https://transferto.xyz/swap)
+
+- If you already have assets on Arbitrum, you can swap them for GRT via a swapping protocol like Uniswap.
+
+- Alternatively, you acquire GRT directly on Arbitrum through a decentralized exchange.
+
+> This section is written assuming you already have GRT in your wallet, and you're on Arbitrum. If you don't have GRT, you can learn how to get GRT [here](#getting-grt).
+
+Once you bridge GRT, you can add it to your billing balance.
+
+### Adding GRT using a wallet
+
+1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
+3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
+4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
+   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
+5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
+6. Select the number of months you would like to prepay.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable.
+8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
+   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
+9. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+
+- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+
+### Withdrawing GRT using a wallet
+
+1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect".
+3. Click the "Manage" button at the top right corner of the page. Select "Withdraw GRT". A side panel will appear.
+4. Enter the amount of GRT you would like to withdraw.
+5. Click 'Withdraw GRT' to withdraw the GRT from your account balance. Sign the associated transaction in your wallet. This will cost gas. The GRT will be sent to your Arbitrum wallet.
+6. Once the transaction is confirmed, you'll see the GRT withdrawn from your account balance in your Arbitrum wallet.
+
+### Adding GRT using a multisig wallet
+
+1. Go to the [Subgraph Studio Billing page](https://thegraph.com/studio/billing/).
+2. Click on the "Connect Wallet" button on the top right corner of the page. Select your wallet and click on "Connect". If you're using [Gnosis-Safe](https://gnosis-safe.io/), you'll be able to connect your multisig as well as your signing wallet. Then, sign the associated message. This will not cost any gas.
+3. Select the "Manage" button near the top right corner. First time users will see an option to "Upgrade to Growth plan" while returning users will click "Deposit from wallet".
+4. Use the slider to estimate the number of queries you expect to make on a monthly basis.
+   - For suggestions on the number of queries you may use, see our **Frequently Asked Questions** page.
+5. Choose "Cryptocurrency". GRT is currently the only cryptocurrency accepted on The Graph Network.
+6. Select the number of months you would like to prepay.
+   - Paying in advance does not commit you to future usage. You will only be charged for what you use and you can withdraw your balance at any time.
+7. Pick the network from which you are depositing your GRT. GRT on Arbitrum or Ethereum are both acceptable. 8. Click "Allow GRT Access" and then specify the amount of GRT that can be taken from you wallet.
+   - If you are prepaying for multiple months, you must allow access to the amount that corresponds with that amount. This interaction will not cost any gas.
+8. Lastly, click on "Add GRT to Billing Balance". This transaction will require ETH on Arbitrum to cover the gas costs.
+
+- Note that GRT deposited from Arbitrum will process within a few moments while GRT deposited from Ethereum will take approximately 15-20 minutes to process. Once the transaction is confirmed, you'll see the GRT added to your account balance.
+
+## Getting GRT
+
+This section will show you how to get GRT to pay for query fees.
+
+### Coinbase
+
+This will be a step by step guide for purchasing GRT on Coinbase.
+
+1. Go to [Coinbase](https://www.coinbase.com/) and create an account.
+2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
+3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy/Sell" button on the top right of the page.
+4. Select the currency you want to purchase. Select GRT.
+5. Select the payment method. Select your preferred payment method.
+6. Select the amount of GRT you want to purchase.
+7. Review your purchase. Review your purchase and click "Buy GRT".
+8. Confirm your purchase. Confirm your purchase and you will have successfully purchased GRT.
+9. You can transfer the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
+   - To transfer the GRT to your wallet, click on the "Accounts" button on the top right of the page.
+   - Click on the "Send" button next to the GRT account.
+   - Enter the amount of GRT you want to send and the wallet address you want to send it to.
+   - Click "Continue" and confirm your transaction. -Please note that for larger purchase amounts, Coinbase may require you to wait 7-10 days before transferring the full amount to a wallet.
+
+You can learn more about getting GRT on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+
+### Binance
+
+This will be a step by step guide for purchasing GRT on Binance.
+
+1. Go to [Binance](https://www.binance.com/en) and create an account.
+2. Once you have created an account, you will need to verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
+3. Once you have verified your identity, you can purchase GRT. You can do this by clicking on the "Buy Now" button on the homepage banner.
+4. You will be taken to a page where you can select the currency you want to purchase. Select GRT.
+5. Select your preferred payment method. You'll be able to pay with different fiat currencies such as Euros, US Dollars, and more.
+6. Select the amount of GRT you want to purchase.
+7. Review your purchase and click "Buy GRT".
+8. Confirm your purchase and you will be able to see your GRT in your Binance Spot Wallet.
+9. You can withdraw the GRT from your account to your wallet such as [MetaMask](https://metamask.io/).
+   - [To withdraw](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570) the GRT to your wallet, add your wallet's address to the withdrawal whitelist.
+   - Click on the "wallet" button, click withdraw, and select GRT.
+   - Enter the amount of GRT you want to send and the whitelisted wallet address you want to send it to.
+   - Click "Continue" and confirm your transaction.
+
+You can learn more about getting GRT on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+
+### Uniswap
+
+This is how you can purchase GRT on Uniswap.
+
+1. Go to [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) and connect your wallet.
+2. Select the token you want to swap from. Select ETH.
+3. Select the token you want to swap to. Select GRT.
+   - Make sure you're swapping for the correct token. The GRT smart contract address on Arbitrum One is: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
+4. Enter the amount of ETH you want to swap.
+5. Click "Swap".
+6. Confirm the transaction in your wallet and you wait for the transaction to process.
+
+You can learn more about getting GRT on Uniswap [here](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-).
+
+## Getting Ether
+
+This section will show you how to get Ether (ETH) to pay for transaction fees or gas costs. ETH is necessary to execute operations on the Ethereum network such as transferring tokens or interacting with contracts.
+
+### Coinbase
+
+This will be a step by step guide for purchasing ETH on Coinbase.
+
+1.  Go to [Coinbase](https://www.coinbase.com/) and create an account.
+2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
+3.  Once you have verified your identity, purchase ETH by clicking on the "Buy/Sell" button on the top right of the page.
+4.  Select the currency you want to purchase. Select ETH.
+5.  Select your preferred payment method.
+6.  Enter the amount of ETH you want to purchase.
+7.  Review your purchase and click "Buy ETH".
+8.  Confirm your purchase and you will have successfully purchased ETH.
+9.  You can transfer the ETH from your Coinbase account to your wallet such as [MetaMask](https://metamask.io/).
+    - To transfer the ETH to your wallet, click on the "Accounts" button on the top right of the page.
+    - Click on the "Send" button next to the ETH account.
+    - Enter the amount of ETH you want to send and the wallet address you want to send it to.
+    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
+    - Click "Continue" and confirm your transaction.
+
+You can learn more about getting ETH on Coinbase [here](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency).
+
+### Binance
+
+This will be a step by step guide for purchasing ETH on Binance.
+
+1.  Go to [Binance](https://www.binance.com/en) and create an account.
+2.  Once you have created an account, verify your identity through a process known as KYC (or Know Your Customer). This is a standard procedure for all centralized or custodial crypto exchanges.
+3.  Once you have verified your identity, purchase ETH by clicking on the "Buy Now" button on the homepage banner.
+4.  Select the currency you want to purchase. Select ETH.
+5.  Select your preferred payment method.
+6.  Enter the amount of ETH you want to purchase.
+7.  Review your purchase and click "Buy ETH".
+8.  Confirm your purchase and you will see your ETH in your Binance Spot Wallet.
+9.  You can withdraw the ETH from your account to your wallet such as [MetaMask](https://metamask.io/).
+    - To withdraw the ETH to your wallet, add your wallet's address to the withdrawal whitelist.
+    - Click on the "wallet" button, click withdraw, and select ETH.
+    - Enter the amount of ETH you want to send and the whitelisted wallet address you want to send it to.
+    - Ensure that you are sending to your Ethereum wallet address on Arbitrum One.
+    - Click "Continue" and confirm your transaction.
+
+You can learn more about getting ETH on Binance [here](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582).
+
+## Billing FAQs
+
+### How many queries will I need?
+
+You don't need to know how many queries you'll need in advance. You will only be charged for what you use and you can withdraw GRT from your account at any time.
+
+We recommend you overestimate the number of queries you will need so that you don’t have to top up your balance frequently. A good estimate for small to medium sized applications is to start with 1M-2M queries per month and monitor usage closely in the first weeks. For larger apps, a good estimate is to use the number of daily visits your site gets multiplied by the number of queries your most active page makes upon opening.
+
+Of course, both new and existing users can reach out to Edge & Node's BD team for a consult to learn more about anticipated usage.
+
+### Can I withdraw GRT from my billing balance?
+
+Yes, you can always withdraw GRT that has not already been used for queries from your billing balance. The billing contract is only designed to bridge GRT from Ethereum mainnet to the Arbitrum network. If you'd like to transfer your GRT from Arbitrum back to Ethereum mainnet, you'll need to use the [Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161).
+
+### What happens when my billing balance runs out? Will I get a warning?
+
+You will receive several email notifications before your billing balance runs out.

From fdc288f412e4a9bb0af55a4b681d84c377dc8488 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:27 -0500
Subject: [PATCH 0927/1325] New translations grafting.mdx (Romanian)

---
 website/pages/ro/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ro/cookbook/grafting.mdx b/website/pages/ro/cookbook/grafting.mdx
index 6b4f419390d5..6c3b85419af9 100644
--- a/website/pages/ro/cookbook/grafting.mdx
+++ b/website/pages/ro/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 651b0467531c0095a62b6db499891cbc77ef4408 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:28 -0500
Subject: [PATCH 0928/1325] New translations grafting.mdx (Spanish)

---
 website/pages/es/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/es/cookbook/grafting.mdx b/website/pages/es/cookbook/grafting.mdx
index 30df42fca0a1..212250c06428 100644
--- a/website/pages/es/cookbook/grafting.mdx
+++ b/website/pages/es/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ Para más información, puedes consultar:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-En este tutorial vamos a cubrir un caso de uso básico. Reemplazaremos un contrato existente con un contrato idéntico (con una nueva dirección, pero el mismo código). Luego, haremos grafting del subgrafo existente en el subgrafo "base" que rastrea el nuevo contrato.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ En este tutorial vamos a cubrir un caso de uso básico. Reemplazaremos un contra
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - La fuente de datos de `Lock` es el ABI y la dirección del contrato que obtendremos cuando compilemos y realicemos el deploy del contrato
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - La sección de `mapeo` define los disparadores de interés y las funciones que deben ejecutarse en respuesta a esos disparadores. En este caso, estamos escuchando el evento `Withdrawal` y llamando a la función `handleWithdrawal` cuando se emite.
 
 ## Definición del manifiesto de grafting
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Recursos Adicionales
 
-Si quieres tener más experiencia con el grafting, aquí tienes algunos ejemplos de contratos populares:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 2327931bbbf43e5f172202124adeec301a37800b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:29 -0500
Subject: [PATCH 0929/1325] New translations grafting.mdx (Arabic)

---
 website/pages/ar/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ar/cookbook/grafting.mdx b/website/pages/ar/cookbook/grafting.mdx
index 548091ac5b7d..08c347c50a63 100644
--- a/website/pages/ar/cookbook/grafting.mdx
+++ b/website/pages/ar/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [تطعيم(Grafting)](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## مصادر إضافية
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 57952bfa9b464dca1f8aa22f0672235298b566f2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:30 -0500
Subject: [PATCH 0930/1325] New translations grafting.mdx (Czech)

---
 website/pages/cs/cookbook/grafting.mdx | 26 +++++++++++++-------------
 1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/website/pages/cs/cookbook/grafting.mdx b/website/pages/cs/cookbook/grafting.mdx
index b68cbe3707c2..637a85c5774e 100644
--- a/website/pages/cs/cookbook/grafting.mdx
+++ b/website/pages/cs/cookbook/grafting.mdx
@@ -22,15 +22,15 @@ Další informace naleznete na:
 
 - [Roubování](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-V tomto tutoriálu se budeme zabývat základním případem použití. Nahradíme stávající smlouvu identickou smlouvou (s novou adresou, ale stejným kódem). Poté naroubujeme stávající podgraf na "základní" podgraf, který sleduje nový kontrakt.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Důležité upozornění k roubování při aktualizaci na síť
 
-> **Caution**: It is recommended to not use grafting for subgraphs published to The Graph Network
+> **Upozornění**: Doporučujeme nepoužívat roubování pro podgrafy publikované v síti grafů
 
 ### Proč je to důležité?
 
-Štěpování je výkonná funkce, která umožňuje "naroubovat" jeden podgraf na druhý, čímž efektivně přenese historická data ze stávajícího podgrafu do nové verze. Ačkoli se jedná o účinný způsob, jak zachovat data a ušetřit čas při indexování, roubování může přinést složitosti a potenciální problémy při migraci z hostovaného prostředí do decentralizované sítě. Podgraf není možné naroubovat ze sítě The Graph Network zpět do hostované služby nebo do aplikace Subgraph Studio.
+Štěpování je výkonná funkce, která umožňuje "naroubovat" jeden podgraf na druhý, čímž efektivně přenese historická data ze stávajícího podgrafu do nové verze. Podgraf není možné naroubovat ze Sítě grafů zpět do Podgraf Studio.
 
 ### Osvědčené postupy
 
@@ -42,7 +42,7 @@ Dodržováním těchto pokynů minimalizujete rizika a zajistíte hladší průb
 
 ## Vytvoření existujícího podgrafu
 
-Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided:
+Vytváření podgrafů je důležitou součástí Grafu, která je podrobněji popsána [zde](/quick-start/). Aby bylo možné sestavit a nasadit existující podgraf použitý v tomto tutoriálu, je k dispozici následující repozitář:
 
 - [Příklad repo subgrafu](https://github.com/Shiyasmohd/grafting-tutorial)
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - Zdroj dat `Lock` je adresa abi a smlouvy, kterou získáme při kompilaci a nasazení smlouvy
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - Sekce `mapování` definuje spouštěče, které vás zajímají, a funkce, které by měly být spuštěny v reakci na tyto spouštěče. V tomto případě nasloucháme na událost `Výstup` a po jejím vyslání voláme funkci `obsluhovatVýstup`.
 
 ## Definice manifestu roubování
@@ -96,14 +96,14 @@ graft:
   block: 5956000 # block number
 ```
 
-- `features:` is a list of all used [feature names](/developing/creating-a-subgraph/#experimental-features).
+- `funkce:` je seznam všech použitých [jmen funkcí](/developing/creating-a-subgraph/#experimental-features).
 - `graft:` je mapa subgrafu `base` a bloku, na který se má roubovat. `block` je číslo bloku, od kterého začít indexovat. Graph zkopíruje data základního subgrafu až k zadanému bloku včetně, a poté pokračuje v indexaci nového subgrafu od tohoto bloku dále.
 
 Hodnoty `base` a `block` lze nalézt nasazením dvou podgrafů: jednoho pro základní indexování a druhého s roubováním
 
 ## Nasazení základního podgrafu
 
-1. Go to [Subgraph Studio](https://thegraph.com/studio/) and create a subgraph on Sepolia testnet called `graft-example`
+1. Přejděte do [Podgraf Studio](https://thegraph.com/studio/) a vytvořte podgraf v testovací síti Sepolia s názvem `graft-example`
 2. Následujte pokyny v části `AUTH & DEPLOY` na stránce vašeho subgrafu v adresáři `graft-example` ve vašem repozitáři
 3. Po dokončení ověřte, zda se podgraf správně indexuje. Pokud spustíte následující příkaz v The Graph Playground
 
@@ -144,8 +144,8 @@ Jakmile ověříte, že se podgraf správně indexuje, můžete jej rychle aktua
 
 Náhradní podgraf.yaml bude mít novou adresu smlouvy. K tomu může dojít při aktualizaci dapp, novém nasazení kontraktu atd.
 
-1. Go to [Subgraph Studio](https://thegraph.com/studio/) and create a subgraph on Sepolia testnet called `graft-replacement`
-2. Create a new manifest. The `subgraph.yaml` for `graph-replacement` contains a different contract address and new information about how it should graft. These are the `block` of the [last event emitted](https://sepolia.etherscan.io/tx/0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc452) you care about by the old contract and the `base` of the old subgraph. The `base` subgraph ID is the `Deployment ID` of your original `graph-example` subgraph. You can find this in Subgraph Studio.
+1. Přejděte do [Podgraf Studio](https://thegraph.com/studio/) a vytvořte podgraf v testovací síti Sepolia s názvem `graft-replacement`
+2. Vytvořte nový manifest. Soubor `subgraph.yaml` pro `graph-replacement` obsahuje jinou adresu kontraktu a nové informace o tom, jak by měl být podgraf nasazen. Tyto informace zahrnují `block` [poslední emitovanou událost](https://sepolia.etherscan.io/tx/0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc452) od starého kontraktu a `base` starého podgrafu. ID `base` podgrafu je `Deployment ID` vašeho původního `graph-example` subgrafu. To můžete najít v Podgraf Studiu.
 3. Postupujte podle pokynů v části `AUTH & DEPLOY` na stránce podgrafu ve složce `graft-replacement` z repozitáře
 4. Po dokončení ověřte, zda se podgraf správně indexuje. Pokud spustíte následující příkaz v The Graph Playground
 
@@ -185,18 +185,18 @@ Měla by vrátit následující:
 }
 ```
 
-You can see that the `graft-replacement` subgraph is indexing from older `graph-example` data and newer data from the new contract address. The original contract emitted two `Withdrawal` events, [Event 1](https://sepolia.etherscan.io/tx/0xe8323d21c4f104607b10b0fff9fc24b9612b9488795dea8196b2d5f980d3dc1d) and [Event 2](https://sepolia.etherscan.io/tx/0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc452). The new contract emitted one `Withdrawal` after, [Event 3](https://sepolia.etherscan.io/tx/0x2410475f76a44754bae66d293d14eac34f98ec03a3689cbbb56a716d20b209af). The two previously indexed transactions (Event 1 and 2) and the new transaction (Event 3) were combined together in the `graft-replacement` subgraph.
+Vidíte, že podgraf `graft-replacement` indexuje ze starších dat `graph-example` a novějších dat z nové adresy smlouvy. Původní smlouva emitovala dvě události `Odstoupení`, [Událost 1](https://sepolia.etherscan.io/tx/0xe8323d21c4f104607b10b0fff9fc24b9612b9488795dea8196b2d5f980d3dc1d) a [Událost 2](https://sepolia.etherscan.io/tx/0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc452). Nová smlouva emitovala jednu událost `Výběr` poté, [Událost 3](https://sepolia.etherscan.io/tx/0x2410475f76a44754bae66d293d14eac34f98ec03a3689cbbb56a716d20b209af). Dvě dříve indexované transakce (Událost 1 a 2) a nová transakce (Událost 3) byly spojeny dohromady v podgrafu `výměna-odvod`.
 
-Congrats! You have successfully grafted a subgraph onto another subgraph.
+Gratulujeme! Úspěšně jste naroubovali podgraf na jiný podgraf.
 
 ## Další zdroje
 
-Pokud chcete získat více zkušeností s roubováním, zde je několik příkladů oblíbených smluv:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)
 - [Uniswap](https://github.com/messari/subgraphs/blob/master/subgraphs/uniswap-v3-forks/protocols/uniswap-v3/config/templates/uniswapV3Template.yaml),
 
-To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results
+Chcete-li se stát ještě větším odborníkem na graf, zvažte možnost seznámit se s dalšími způsoby zpracování změn v podkladových zdrojích dat. Alternativy jako [Šablony zdroje dat](/developing/creating-a-subgraph/#data-source-templates) mohou dosáhnout podobných výsledků
 
 > Poznámka: Mnoho materiálů z tohoto článku bylo převzato z dříve publikovaného [článku Arweave](/cookbook/arweave/)

From 09bb42e119bfae9ff64bf7bfbb06c8f8a5a36156 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:32 -0500
Subject: [PATCH 0931/1325] New translations grafting.mdx (German)

---
 website/pages/de/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/de/cookbook/grafting.mdx b/website/pages/de/cookbook/grafting.mdx
index d6a88a506760..4e2311f14da2 100644
--- a/website/pages/de/cookbook/grafting.mdx
+++ b/website/pages/de/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 11dc0880d999fd769e529ee2c1b19baf072f3c13 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:33 -0500
Subject: [PATCH 0932/1325] New translations grafting.mdx (Italian)

---
 website/pages/it/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/it/cookbook/grafting.mdx b/website/pages/it/cookbook/grafting.mdx
index 5137472eca06..d6c443a46538 100644
--- a/website/pages/it/cookbook/grafting.mdx
+++ b/website/pages/it/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 2e38eaf751dce2c95b74881958613ddd8d0f1106 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:34 -0500
Subject: [PATCH 0933/1325] New translations grafting.mdx (Japanese)

---
 website/pages/ja/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ja/cookbook/grafting.mdx b/website/pages/ja/cookbook/grafting.mdx
index c0febe43753c..2df8229bce59 100644
--- a/website/pages/ja/cookbook/grafting.mdx
+++ b/website/pages/ja/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: グラフティングでコントラクトを取り替え、履歴を残
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-このチュートリアルでは、基本的なユースケースについて説明します。既存の契約を同一の契約に置き換えます（新しい住所ですが、コードは同じです）。次に、新しいコントラクトを追跡する「ベース」サブグラフに既存のサブグラフを移植します
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## ネットワークにアップグレードする際の移植に関する重要な注意事項
 
@@ -30,7 +30,7 @@ title: グラフティングでコントラクトを取り替え、履歴を残
 
 ### 何でこれが大切ですか？
 
-グラフティングは、既存のサブグラフから新しいバージョンに歴史的なデータを効果的に転送することを可能にする、強力な機能です。これはデータを保存し、インデックス作業に時間を節約する効果的な方法ですが、ホスト環境から分散ネットワークに移行する際に複雑さや潜在的な問題を導入する可能性があります。The Graph NetworkからホストされたサービスやSubgraph Studioにサブグラフを戻すことはできません。
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### ベストプラクティス
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - `Lock`データソースは、コンパイルとデプロイ時に取得するアビとコントラクトのアドレスです。
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - `mapping`セクションでは、関心のあるトリガーと、それらのトリガーに応答して実行されるべき関数を定義しています。この場合、`Withdrawal`イベントをリスニングし、それが発信されたときに`handleWithdrawal`関数を呼び出すことにしています。
 
 ## グラフティングマニフェストの定義
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## その他のリソース
 
-もっとグラフティングを体験したい方に、人気のあるコントラクトの例をご紹介します：
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [曲線](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From d095eb59aca2f9d792f3d0ba603645f50a9a7416 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:35 -0500
Subject: [PATCH 0934/1325] New translations grafting.mdx (Korean)

---
 website/pages/ko/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ko/cookbook/grafting.mdx b/website/pages/ko/cookbook/grafting.mdx
index 6b4f419390d5..6c3b85419af9 100644
--- a/website/pages/ko/cookbook/grafting.mdx
+++ b/website/pages/ko/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 11d0d28e3b5c3c39835507437f0f053da428e725 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:36 -0500
Subject: [PATCH 0935/1325] New translations grafting.mdx (Dutch)

---
 website/pages/nl/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/nl/cookbook/grafting.mdx b/website/pages/nl/cookbook/grafting.mdx
index 6b4f419390d5..6c3b85419af9 100644
--- a/website/pages/nl/cookbook/grafting.mdx
+++ b/website/pages/nl/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From d5fc0576feb8afa89e6c0576d14a643373d933f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:37 -0500
Subject: [PATCH 0936/1325] New translations grafting.mdx (Polish)

---
 website/pages/pl/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/pl/cookbook/grafting.mdx b/website/pages/pl/cookbook/grafting.mdx
index 6b4f419390d5..6c3b85419af9 100644
--- a/website/pages/pl/cookbook/grafting.mdx
+++ b/website/pages/pl/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 4276dc51bd8d8421cda44f4809a89f8105d5b843 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:38 -0500
Subject: [PATCH 0937/1325] New translations grafting.mdx (Portuguese)

---
 website/pages/pt/cookbook/grafting.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/pt/cookbook/grafting.mdx b/website/pages/pt/cookbook/grafting.mdx
index c92b438ecfdd..70bffd53aae8 100644
--- a/website/pages/pt/cookbook/grafting.mdx
+++ b/website/pages/pt/cookbook/grafting.mdx
@@ -30,7 +30,7 @@ Neste tutorial, cobriremos um caso de uso básico. Substituiremos um contrato ex
 
 ### Qual a Importância Disto?
 
-O enxerto é uma ferramenta poderosa que lhe permite "enxertar" um subgraph em outro — a fim de, efetivamente, transferir dados históricos do subgraph existente a uma nova versão. Enquanto isto é uma forma eficaz de preservar dados e poupar tempo de indexação, enxertos podem causar complexidades e possíveis problemas ao migrar de um ambiente hospedado até a rede descentralizada. Não é possível enxertar um subgraph da Graph Network de volta ao serviço hospedado ou ao Subgraph Studio.
+Isto é um recurso poderoso que permite que os programadores "enxertem" um subgraph em outro, o que, efetivamente, transfere dados históricos do subgraph existente até uma versão nova. Não é possível enxertar um subgraph da Graph Network de volta ao Subgraph Studio.
 
 ### Boas práticas
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - A fonte de dados `Lock` é o abi e o endereço do contrato que receberemos ao compilar e lançar o contrato
-- A rede deve corresponder a uma rede indexada a ser consultada em query. Como executamos na testnet Sepolia, a rede é `sepolia`
+- A rede deve corresponder a uma rede indexada que está a ser consultada em query. Como executamos na testnet Sepolia, a rede é `sepolia`
 - A seção `mapping` define os gatilhos de interesse e as funções que devem ser executadas em resposta àqueles gatilhos. Neste caso, esperamos o evento `Withdrawal` e chamaremos a função `handleWithdrawal` quando o evento for emitido.
 
 ## Definição de Manifest de Enxertos

From 9241f671f71d053a951914aa501e4867e0c57fca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:39 -0500
Subject: [PATCH 0938/1325] New translations grafting.mdx (Swedish)

---
 website/pages/sv/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/sv/cookbook/grafting.mdx b/website/pages/sv/cookbook/grafting.mdx
index aa498bdcaaa6..8ddfa857f8da 100644
--- a/website/pages/sv/cookbook/grafting.mdx
+++ b/website/pages/sv/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ För mer information kan du kontrollera:
 
 - [Ympning](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-I den här handledningen kommer vi att täcka ett grundläggande användningsfall. Vi kommer att ersätta ett befintligt kontrakt med ett identiskt kontrakt (med en ny adress, men samma kod). Ympa sedan den befintliga subgrafen på "bas"-subgrafen som spårar det nya kontraktet.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Viktig anmärkning om ympning vid uppgradering till nätverket
 
@@ -30,7 +30,7 @@ I den här handledningen kommer vi att täcka ett grundläggande användningsfal
 
 ### Varför är detta viktigt?
 
-Ympning är en kraftfull funktion som gör det möjligt att "transplantera" en subgraph till en annan, och överföra historisk data från den befintliga subgraphen till en ny version. Även om detta är ett effektivt sätt att bevara data och spara tid på indexering, kan grafting introducera komplexiteter och potentiella problem vid övergången från en hostad miljö till det decentraliserade nätverket. Det är inte möjligt att använda grafting för att föra tillbaka en subgraph från The Graf Nätverk till den hostade tjänsten eller Subgraf Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Bästa praxis
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - `Lock`-datakällan är abi- och kontraktsadressen vi får när vi kompilerar och distribuerar kontraktet
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - Avsnittet `mappning` definierar utlösare av intresse och de funktioner som ska köras som svar på dessa utlösare. I det här fallet lyssnar vi efter händelsen `Withdrawal` och anropar funktionen `handleWithdrawal` när den sänds.
 
 ## Ympnings manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Ytterligare resurser
 
-Om du vill ha mer erfarenhet av ympning, här är några exempel på populära kontrakt:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From ea7b3dfde7d6cd7d1c0e521b531f2d369e987240 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:40 -0500
Subject: [PATCH 0939/1325] New translations grafting.mdx (Turkish)

---
 website/pages/tr/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/tr/cookbook/grafting.mdx b/website/pages/tr/cookbook/grafting.mdx
index b3e1f5a218c0..2857ded9d636 100644
--- a/website/pages/tr/cookbook/grafting.mdx
+++ b/website/pages/tr/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ Daha fazla bilgi için kontrol edebilirsiniz:
 
 - [Graftlama](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-Bu eğitici içerikte, temel bir kullanım örneğini ele alacağız. Mevcut bir sözleşmeyi özdeş bir sözleşme ile değiştireceğiz (yeni bir adresle, ancak aynı kodla). Ardından, mevcut subgraph'ı yeni sözleşmeyi izleyen "base" subgraph'a graftlayacağız.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Ağa Yükseltme Durumunda Graftlamaya İlişkin Önemli Not
 
@@ -30,7 +30,7 @@ Bu eğitici içerikte, temel bir kullanım örneğini ele alacağız. Mevcut bir
 
 ### Bu Neden Önemli?
 
-Graftlama, bir subgraph'ı diğerine "graftlamanıza" ve geçmiş verileri mevcut subgraph'tan yeni bir sürüme etkili bir şekilde transfer etmenize olanak tanıyan güçlü bir özelliktir. Bu, verileri korumak ve indekslemede zaman kazanmak için etkili bir yol olsa da, graftlama, barındırılan bir ortamdan merkeziyersiz ağa taşınırken karmaşıklıklar ve potansiyel sorunlar ortaya çıkarabilir. Bir subgraph'ı Graph Ağı'ndan barındırılan hizmete veya Subgraph Stüdyo'ya geri graftlamak mümkün değildir.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### En İyi Uygulamalar
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - `Lock` veri kaynağı, sözleşmeyi derleyip dağıttığımızda alacağımız abi ve sözleşme adresidir
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - `mapping` bölümü, ilgili tetikleyicileri ve bu tetikleyicilere yanıt olarak çalıştırılması gereken fonksiyonları tanımlar. Bu durumda, `Withdrawal` olayının etkinliklerini gözlemliyoruz ve yayıldığında `handleWithdrawal` fonksiyonunu çağırıyoruz.
 
 ## Graftlama Manifest Tanımı
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Ek Kaynaklar
 
-Graftlama konusunda daha fazla tecrübe edinmek istiyorsanız, işte popüler sözleşmeler için birkaç örnek:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 23c25e849a316967bf1b752664cb23a83c8d50bf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:42 -0500
Subject: [PATCH 0940/1325] New translations grafting.mdx (Ukrainian)

---
 website/pages/uk/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/uk/cookbook/grafting.mdx b/website/pages/uk/cookbook/grafting.mdx
index 46b93c05d891..4e8339df3ee3 100644
--- a/website/pages/uk/cookbook/grafting.mdx
+++ b/website/pages/uk/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: Замініть контракт та збережіть його іст
 
 - [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-У цьому матеріалі ми розглянемо базовий випадок використання. Ми замінимо наявний контракт на ідентичний (з новою адресою, але тим самим кодом).
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Важливе зауваження щодо графтингу при оновленні в мережі
 
@@ -30,7 +30,7 @@ title: Замініть контракт та збережіть його іст
 
 ### Чому це так важливо?
 
-Grafting - це потужна функція, яка дозволяє " накладати" один підграф на інший, ефективно переносячи історичні дані з наявного підграфа в нову версію. Хоча це ефективний спосіб зберегти дані та заощадити час на індексацію, але при перенесенні з хостингу в децентралізовану мережу можуть виникнути складнощі та потенційні проблеми. Неможливо трансплантувати підграф з The Graph Network назад до хостингового сервісу або Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Найкращі практики
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - Джерелом даних `Lock` є адреса abi та адреса контракту, яку ми отримаємо під час компіляції та розгортання контракту
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - Розділ `mapping` визначає тригери, що нас цікавлять, і функції, які мають бути запущені у відповідь на ці тригери. У цьому випадку ми очікуємо на `Withdrawal` і після цього викликаємо функцію `handleWithdrawal` коли вона з'являється.
 
 ## Визначення Grafting Manifest
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Додаткові матеріали
 
-Якщо ви хочете отримати більше досвіду роботи зі процесом графтингу, ось кілька прикладів популярних контрактів:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From e9a70edf7be83e9496b11afca3af2032cea1dce4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:43 -0500
Subject: [PATCH 0941/1325] New translations grafting.mdx (Chinese Simplified)

---
 website/pages/zh/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/zh/cookbook/grafting.mdx b/website/pages/zh/cookbook/grafting.mdx
index c570b3abbd93..c98e74e7d670 100644
--- a/website/pages/zh/cookbook/grafting.mdx
+++ b/website/pages/zh/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: 用嫁接替换合约并保持合约的历史
 
 - [嫁接](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-在本教程中，我们将介绍一个基本用例。我们将用一个相同的合约(用一个新的地址，但相同的代码) 替换现有的合约。然后，将现有的子图移植到跟踪新合约的基本子图上。
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ title: 用嫁接替换合约并保持合约的历史
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - `Lock`数据源是我们在编译和部署合约时获得的abi和合约地址
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - `mapping`部分定义了感兴趣的触发器以及应该响应这些触发器而运行的函数。在这种情况下，我们正在监听`Withdrawl`事件，并在发出该事件时调用`处理Withdrawal`函数。
 
 ## 嫁接清单定义
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## 其他资源
 
-如果你想要更多的嫁接经验，这里有一些流行合约的例子:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 746a2fe5a94aeda215040eee2b7b97b7deac4424 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:44 -0500
Subject: [PATCH 0942/1325] New translations grafting.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ur/cookbook/grafting.mdx b/website/pages/ur/cookbook/grafting.mdx
index 53278d2240ec..c204eee68424 100644
--- a/website/pages/ur/cookbook/grafting.mdx
+++ b/website/pages/ur/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: ایک کنٹریکٹ کو تبدیل کریں اور اس کی تاری
 
 - [گرافٹنگ](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-اس ٹیوٹوریل میں، ہم استعمال کے ایک بنیادی کیس کا احاطہ کریں گے۔ ہم موجودہ معاہدے کو ایک جیسے کنٹریکٹ سے بدل دیں گے (ایک نئے پتہ کے ساتھ، لیکن ایک ہی کوڈ کے ساتھ)۔ اس کے بعد، موجودہ سب گراف کو "بیس" سب گراف پر گرافٹ کریں جو نئے کنٹریکٹ کو ٹریک کرتا ہے.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## نیٹ ورک میں اپ گریڈ کرتے وقت گرافٹنگ پر اہم نوٹ
 
@@ -30,7 +30,7 @@ title: ایک کنٹریکٹ کو تبدیل کریں اور اس کی تاری
 
 ### یہ کیوں اہم ہے؟
 
-گرافٹنگ ایک طاقتور خصوصیت ہے جو آپ کو ایک سب گراف کو دوسرے پر "گرافٹ" کرنے کی اجازت دیتی ہے، مؤثر طریقے سے تاریخی ڈیٹا کو موجودہ سب گراف سے نئے ورژن میں منتقل کرتی ہے۔ اگرچہ یہ ڈیٹا کو محفوظ رکھنے اور انڈیکسنگ پر وقت بچانے کا ایک مؤثر طریقہ ہے، لیکن گرافٹنگ کسی میزبان ماحول سے ڈیسنٹرالا ئزڈ نیٹ ورک کی طرف ہجرت کرتے وقت پیچیدگیوں اور ممکنہ مسائل کو پیش کر سکتی ہے۔ گراف نیٹ ورک سے سب گراف کو ہوسٹڈ سروس یا سب گراف اسٹوڈیو میں واپس کرنا ممکن نہیں ہے.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### بہترین طریقے
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - `Lock` ڈیٹا کا ذریعہ abi اور کنٹریکٹ ایڈریس ہے جب ہم کنٹریکٹ کو مرتب اور تعینات کریں گے
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - `mapping` سیکشن دلچسپی کے محرکات اور ان افعال کی وضاحت کرتا ہے جنہیں ان محرکات کے جواب میں چلایا جانا چاہیے۔ اس صورت میں، ہم `Withdrawal` ایونٹ کو سن رہے ہیں اور جب یہ خارج ہوتا ہے تو `handleWithdrawal` فنکشن کو کال کر رہے ہیں.
 
 ## گرافٹنگ مینی فیسٹ کی تعریف
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## اضافی وسائل
 
-اگر آپ گرافٹنگ کے ساتھ مزید تجربہ چاہتے ہیں، تو یہاں مقبول کنٹریکٹس کے لیے چند مثالیں ہیں:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From ede10aa3f32185ca3201b3a96afcf68095bdab51 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:45 -0500
Subject: [PATCH 0943/1325] New translations grafting.mdx (Vietnamese)

---
 website/pages/vi/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/vi/cookbook/grafting.mdx b/website/pages/vi/cookbook/grafting.mdx
index 3b4f46fe9bd1..c37ae95c28e0 100644
--- a/website/pages/vi/cookbook/grafting.mdx
+++ b/website/pages/vi/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ For more information, you can check:
 
 - [Ghép](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-In this tutorial, we will be covering a basic usecase. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ In this tutorial, we will be covering a basic usecase. We will replace an existi
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
 
 ## Grafting Manifest Definition
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## Additional Resources
 
-If you want more experience with grafting, here's a few examples for popular contracts:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 7f1cbeaac09b73cd66e5a20ede7e731c9a43bf16 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:46 -0500
Subject: [PATCH 0944/1325] New translations grafting.mdx (Marathi)

---
 website/pages/mr/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/mr/cookbook/grafting.mdx b/website/pages/mr/cookbook/grafting.mdx
index 9c46a16ab79d..77d4b0d04899 100644
--- a/website/pages/mr/cookbook/grafting.mdx
+++ b/website/pages/mr/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: करार बदला आणि त्याचा इतिहास
 
 - [कलम करणे](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-या ट्युटोरियलमध्ये, आपण मूलभूत वापराचे केस कव्हर करणार आहोत. आम्‍ही सध्‍याच्‍या कराराची जागा एकसमान कराराने (नवीन पत्‍त्‍यासह, परंतु समान कोडसह) बदलू. त्यानंतर, नवीन कराराचा मागोवा घेणाऱ्या "बेस" सबग्राफवर विद्यमान सबग्राफ कलम करा.
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ title: करार बदला आणि त्याचा इतिहास
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
 - `मॅपिंग` विभाग स्वारस्यांचे ट्रिगर आणि त्या ट्रिगरला प्रतिसाद म्हणून चालवल्या जाणार्‍या कार्ये परिभाषित करतो. या प्रकरणात, आम्ही `Withdrawal` इव्हेंट ऐकत आहोत आणि जेव्हा ते उत्सर्जित होते तेव्हा `handleWithdrawal` फंक्शनला कॉल करत आहोत.
 
 ## Grafting मॅनिफेस्ट व्याख्या
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## अतिरिक्त संसाधने
 
-तुम्हाला ग्राफ्टिंगचा अधिक अनुभव हवा असल्यास, लोकप्रिय करारांसाठी येथे काही उदाहरणे आहेत:
+If you want more experience with grafting, here are a few examples for popular contracts:
 
 - [वक्र](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From babf19cc205757ec9775c950fae1107fdeaa4cca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:47 -0500
Subject: [PATCH 0945/1325] New translations grafting.mdx (Hindi)

---
 website/pages/hi/cookbook/grafting.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/hi/cookbook/grafting.mdx b/website/pages/hi/cookbook/grafting.mdx
index 88c95a19b144..2225f5cacb01 100644
--- a/website/pages/hi/cookbook/grafting.mdx
+++ b/website/pages/hi/cookbook/grafting.mdx
@@ -22,7 +22,7 @@ title: एक कॉन्ट्रैक्ट बदलें और उसक
 
 - [ग्राफ्टिंग](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
 
-इस अनुशिक्षण में हम एक बुनियादी उदहारण देखेंगे| हम एक मौजूदा कॉन्ट्रैक्ट को एक समान कॉन्ट्रैक्ट से बदल देंगे( नए एड्रेस के साथ, मगर सामान कोड). उसके बाद हम एक मौजूदा सब-ग्राफ एक "बेस" सब-ग्राफ में ग्राफ्ट कर देंगे नए कॉन्ट्रैक्ट की निगरानी करेगा|
+इस ट्यूटोरियल में, हम एक बुनियादी उपयोग मामले को कवर करेंगे। हम एक मौजूदा कॉन्ट्रैक्ट को एक समान कॉन्ट्रैक्ट (नए पते के साथ, लेकिन वही कोड) से बदलेंगे। फिर, मौजूदा Subgraph को "बेस" Subgraph पर जोड़ेंगे, जो नए कॉन्ट्रैक्ट को ट्रैक करता है।
 
 ## Important Note on Grafting When Upgrading to the Network
 
@@ -30,7 +30,7 @@ title: एक कॉन्ट्रैक्ट बदलें और उसक
 
 ### Why Is This Important?
 
-Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. While this is an effective way to preserve data and save time on indexing, grafting may introduce complexities and potential issues when migrating from a hosted environment to the decentralized network. It is not possible to graft a subgraph from The Graph Network back to the hosted service or Subgraph Studio.
+Grafting एक शक्तिशाली विशेषता है जो आपको एक सबग्राफ़ को दूसरे पर "graft" करने की अनुमति देती है, जिससे मौजूदा सबग्राफ़ से नए संस्करण में ऐतिहासिक डेटा को प्रभावी ढंग से स्थानांतरित किया जा सके।The Graph Network से सबग्राफ़ को Subgraph Studioमें वापस graft करना संभव नहीं है।
 
 ### Best Practices
 
@@ -80,7 +80,7 @@ dataSources:
 ```
 
 - `Lock` डाटा सोर्स वह ऐ बी आई और कॉन्ट्रैक्ट एड्रेस है जो कि हमे तब मिलेगा जब हम अपना कॉन्ट्रैक्ट संकलित और तैनात करते हैं|
-- The network should correspond to a indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- नेटवर्क को उस इंडेक्स किए गए नेटवर्क के अनुरूप होना चाहिए जिसे क्वेरी किया जा रहा है। चूंकि हम **Sepolia** टेस्टनेट पर काम कर रहे हैं, नेटवर्क `sepolia` है।
 - `mapping` सेक्शन उन ट्रिगर ऑफ़ इंटरेस्ट और उनके जवाब में चलने वाले फंक्शन्स को परिभासित करता है| इस स्थिति में, हम `Withdrawal` फंक्शन को सुनते हैं और `handleWithdrawal` फंक्शन को कॉल करते हैं|
 
 ## ग्राफ्टिंग मैनिफेस्ट की परिभाषा
@@ -191,7 +191,7 @@ Congrats! You have successfully grafted a subgraph onto another subgraph.
 
 ## अतिरिक्त संसाधन
 
-अगर आप ग्राफ्टिंग के साथ और अधिक अनुभव चाहते हैं तोह आपके लिए निम्न कुछ लोकप्रिय कॉन्ट्रैक्ट्स हैं:
+यदि आप grafting के साथ अधिक अनुभव प्राप्त करना चाहते हैं, तो यहां कुछ लोकप्रिय कॉन्ट्रैक्ट्स के उदाहरण दिए गए हैं:
 
 - [कर्व](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
 - [इ आर सी - 721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)

From 6b608ec0bfae9c89ed7bdcaaf10911d4a295e798 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:49:48 -0500
Subject: [PATCH 0946/1325] New translations grafting.mdx (Swahili)

---
 website/pages/sw/cookbook/grafting.mdx | 202 +++++++++++++++++++++++++
 1 file changed, 202 insertions(+)
 create mode 100644 website/pages/sw/cookbook/grafting.mdx

diff --git a/website/pages/sw/cookbook/grafting.mdx b/website/pages/sw/cookbook/grafting.mdx
new file mode 100644
index 000000000000..6c3b85419af9
--- /dev/null
+++ b/website/pages/sw/cookbook/grafting.mdx
@@ -0,0 +1,202 @@
+---
+title: Replace a Contract and Keep its History With Grafting
+---
+
+In this guide, you will learn how to build and deploy new subgraphs by grafting existing subgraphs.
+
+## What is Grafting?
+
+Grafting reuses the data from an existing subgraph and starts indexing it at a later block. This is useful during development to get past simple errors in the mappings quickly or to temporarily get an existing subgraph working again after it has failed. Also, it can be used when adding a feature to a subgraph that takes long to index from scratch.
+
+The grafted subgraph can use a GraphQL schema that is not identical to the one of the base subgraph, but merely compatible with it. It has to be a valid subgraph schema in its own right, but may deviate from the base subgraph's schema in the following ways:
+
+- It adds or removes entity types
+- It removes attributes from entity types
+- It adds nullable attributes to entity types
+- It turns non-nullable attributes into nullable attributes
+- It adds values to enums
+- It adds or removes interfaces
+- It changes for which entity types an interface is implemented
+
+For more information, you can check:
+
+- [Grafting](/developing/creating-a-subgraph#grafting-onto-existing-subgraphs)
+
+In this tutorial, we will be covering a basic use case. We will replace an existing contract with an identical contract (with a new address, but the same code). Then, graft the existing subgraph onto the "base" subgraph that tracks the new contract.
+
+## Important Note on Grafting When Upgrading to the Network
+
+> **Caution**: It is recommended to not use grafting for subgraphs published to The Graph Network
+
+### Why Is This Important?
+
+Grafting is a powerful feature that allows you to "graft" one subgraph onto another, effectively transferring historical data from the existing subgraph to a new version. It is not possible to graft a subgraph from The Graph Network back to Subgraph Studio.
+
+### Best Practices
+
+**Initial Migration**: when you first deploy your subgraph to the decentralized network, do so without grafting. Ensure that the subgraph is stable and functioning as expected.
+
+**Subsequent Updates**: once your subgraph is live and stable on the decentralized network, you may use grafting for future versions to make the transition smoother and to preserve historical data.
+
+By adhering to these guidelines, you minimize risks and ensure a smoother migration process.
+
+## Building an Existing Subgraph
+
+Building subgraphs is an essential part of The Graph, described more in depth [here](/quick-start/). To be able to build and deploy the existing subgraph used in this tutorial, the following repo is provided:
+
+- [Subgraph example repo](https://github.com/Shiyasmohd/grafting-tutorial)
+
+> Note: The contract used in the subgraph was taken from the following [Hackathon Starterkit](https://github.com/schmidsi/hackathon-starterkit).
+
+## Subgraph Manifest Definition
+
+The subgraph manifest `subgraph.yaml` identifies the data sources for the subgraph, the triggers of interest, and the functions that should be run in response to those triggers. See below for an example subgraph manifest that you will use:
+
+```yaml
+specVersion: 0.0.4
+schema:
+  file: ./schema.graphql
+dataSources:
+  - kind: ethereum
+    name: Lock
+    network: sepolia
+    source:
+      address: '0xb3aabe721794b85fe4e72134795c2f93b4eb7e63'
+      abi: Lock
+      startBlock: 5955690
+    mapping:
+      kind: ethereum/events
+      apiVersion: 0.0.6
+      language: wasm/assemblyscript
+      entities:
+        - Withdrawal
+      abis:
+        - name: Lock
+          file: ./abis/Lock.json
+      eventHandlers:
+        - event: Withdrawal(uint256,uint256)
+          handler: handleWithdrawal
+      file: ./src/lock.ts
+```
+
+- The `Lock` data source is the abi and contract address we will get when we compile and deploy the contract
+- The network should correspond to an indexed network being queried. Since we're running on Sepolia testnet, the network is `sepolia`
+- The `mapping` section defines the triggers of interest and the functions that should be run in response to those triggers. In this case, we are listening for the `Withdrawal` event and calling the `handleWithdrawal` function when it is emitted.
+
+## Grafting Manifest Definition
+
+Grafting requires adding two new items to the original subgraph manifest:
+
+```yaml
+---
+features:
+  - grafting # feature name
+graft:
+  base: Qm... # subgraph ID of base subgraph
+  block: 5956000 # block number
+```
+
+- `features:` is a list of all used [feature names](/developing/creating-a-subgraph/#experimental-features).
+- `graft:` is a map of the `base` subgraph and the block to graft on to. The `block` is the block number to start indexing from. The Graph will copy the data of the base subgraph up to and including the given block and then continue indexing the new subgraph from that block on.
+
+The `base` and `block` values can be found by deploying two subgraphs: one for the base indexing and one with grafting
+
+## Deploying the Base Subgraph
+
+1. Go to [Subgraph Studio](https://thegraph.com/studio/) and create a subgraph on Sepolia testnet called `graft-example`
+2. Follow the directions in the `AUTH & DEPLOY` section on your subgraph page in the `graft-example` folder from the repo
+3. Once finished, verify the subgraph is indexing properly. If you run the following command in The Graph Playground
+
+```graphql
+{
+  withdrawals(first: 5) {
+    id
+    amount
+    when
+  }
+}
+```
+
+It returns something like this:
+
+```
+{
+  "data": {
+    "withdrawals": [
+      {
+        "id": "0xe8323d21c4f104607b10b0fff9fc24b9612b9488795dea8196b2d5f980d3dc1d0a000000",
+        "amount": "0",
+        "when": "1716394824"
+      },
+      {
+        "id": "0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc45203000000",
+        "amount": "0",
+        "when": "1716394848"
+      }
+    ]
+  }
+}
+```
+
+Once you have verified the subgraph is indexing properly, you can quickly update the subgraph with grafting.
+
+## Deploying the Grafting Subgraph
+
+The graft replacement subgraph.yaml will have a new contract address. This could happen when you update your dapp, redeploy a contract, etc.
+
+1. Go to [Subgraph Studio](https://thegraph.com/studio/) and create a subgraph on Sepolia testnet called `graft-replacement`
+2. Create a new manifest. The `subgraph.yaml` for `graph-replacement` contains a different contract address and new information about how it should graft. These are the `block` of the [last event emitted](https://sepolia.etherscan.io/tx/0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc452) you care about by the old contract and the `base` of the old subgraph. The `base` subgraph ID is the `Deployment ID` of your original `graph-example` subgraph. You can find this in Subgraph Studio.
+3. Follow the directions in the `AUTH & DEPLOY` section on your subgraph page in the `graft-replacement` folder from the repo
+4. Once finished, verify the subgraph is indexing properly. If you run the following command in The Graph Playground
+
+```graphql
+{
+  withdrawals(first: 5) {
+    id
+    amount
+    when
+  }
+}
+```
+
+It should return the following:
+
+```
+{
+  "data": {
+    "withdrawals": [
+      {
+        "id": "0xe8323d21c4f104607b10b0fff9fc24b9612b9488795dea8196b2d5f980d3dc1d0a000000",
+        "amount": "0",
+        "when": "1716394824"
+      },
+      {
+        "id": "0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc45203000000",
+        "amount": "0",
+        "when": "1716394848"
+      },
+      {
+        "id": "0x2410475f76a44754bae66d293d14eac34f98ec03a3689cbbb56a716d20b209af06000000",
+        "amount": "0",
+        "when": "1716429732"
+      }
+    ]
+  }
+}
+```
+
+You can see that the `graft-replacement` subgraph is indexing from older `graph-example` data and newer data from the new contract address. The original contract emitted two `Withdrawal` events, [Event 1](https://sepolia.etherscan.io/tx/0xe8323d21c4f104607b10b0fff9fc24b9612b9488795dea8196b2d5f980d3dc1d) and [Event 2](https://sepolia.etherscan.io/tx/0xea1cee35036f2cacb72f2a336be3e54ab911f5bebd58f23400ebb8ecc5cfc452). The new contract emitted one `Withdrawal` after, [Event 3](https://sepolia.etherscan.io/tx/0x2410475f76a44754bae66d293d14eac34f98ec03a3689cbbb56a716d20b209af). The two previously indexed transactions (Event 1 and 2) and the new transaction (Event 3) were combined together in the `graft-replacement` subgraph.
+
+Congrats! You have successfully grafted a subgraph onto another subgraph.
+
+## Additional Resources
+
+If you want more experience with grafting, here are a few examples for popular contracts:
+
+- [Curve](https://github.com/messari/subgraphs/blob/master/subgraphs/curve-finance/protocols/curve-finance/config/templates/curve.template.yaml)
+- [ERC-721](https://github.com/messari/subgraphs/blob/master/subgraphs/erc721-metadata/subgraph.yaml)
+- [Uniswap](https://github.com/messari/subgraphs/blob/master/subgraphs/uniswap-v3-forks/protocols/uniswap-v3/config/templates/uniswapV3Template.yaml),
+
+To become even more of a Graph expert, consider learning about other ways to handle changes in underlying datasources. Alternatives like [Data Source Templates](/developing/creating-a-subgraph/#data-source-templates) can achieve similar results
+
+> Note: A lot of material from this article was taken from the previously published [Arweave article](/cookbook/arweave/)

From 125bde876915c46e869df621d221f39879a67ebb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:02 -0500
Subject: [PATCH 0947/1325] New translations firehose.mdx (Swahili)

---
 website/pages/sw/firehose.mdx | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 website/pages/sw/firehose.mdx

diff --git a/website/pages/sw/firehose.mdx b/website/pages/sw/firehose.mdx
new file mode 100644
index 000000000000..0f0fdebbafd0
--- /dev/null
+++ b/website/pages/sw/firehose.mdx
@@ -0,0 +1,24 @@
+---
+title: Firehose
+---
+
+![Firehose Logo](/img/firehose-logo.png)
+
+Firehose is a new technology developed by StreamingFast working with The Graph Foundation. The product provides **previously unseen capabilities and speeds for indexing blockchain data** using a files-based and streaming-first approach.
+
+The Graph merges into Go Ethereum/geth with the adoption of [Live Tracer with v1.14.0 release](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0).
+
+Firehose extracts, transforms and saves blockchain data in a highly performant file-based strategy. Blockchain developers can then access data extracted by Firehose through binary data streams. Firehose is intended to stand as a replacement for The Graph’s original blockchain data extraction layer.
+
+## Firehose Documentation
+
+The Firehose documentation is currently maintained by the StreamingFast team [on the StreamingFast website](https://firehose.streamingfast.io/).
+
+### Getting Started
+
+- Read this [Firehose introduction](https://firehose.streamingfast.io/introduction/firehose-overview) to get an overview of what it is and why it was built.
+- Learn about the [Prerequisites](https://firehose.streamingfast.io/introduction/prerequisites) to install and deploy Firehose.
+
+### Expand Your Knowledge
+
+- Learn about the different [Firehose components](https://firehose.streamingfast.io/architecture/components) available.

From 467bb1a0171ac0ab48e48927c8d10b1b692fe49f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:04 -0500
Subject: [PATCH 0948/1325] New translations substreams.mdx (Romanian)

---
 website/pages/ro/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/ro/substreams.mdx b/website/pages/ro/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/ro/substreams.mdx
+++ b/website/pages/ro/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From a8f7f4abd3d959c04bc0cb3d3488905c6b2d9985 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:05 -0500
Subject: [PATCH 0949/1325] New translations substreams.mdx (French)

---
 website/pages/fr/substreams.mdx | 36 +++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/website/pages/fr/substreams.mdx b/website/pages/fr/substreams.mdx
index 1797d3816bc2..03b653f3025b 100644
--- a/website/pages/fr/substreams.mdx
+++ b/website/pages/fr/substreams.mdx
@@ -4,29 +4,31 @@ title: Substreams
 
 ![Logo Substreams](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## Le fonctionnement de Substreams en 4 étapes
 
-1. **Vous écrivez un programme Rust, qui définit les transformations que vous souhaitez appliquer aux données de la blockchain.** Par exemple, la fonction Rust suivante extrait les informations pertinentes d'un bloc Ethereum (numéro, hachage et hachage parent) .
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **Il suffit d'exécuter une seule commande CLI pour transformer votre programme Rust en un module WASM.**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **Le conteneur WASM est envoyé à un point de terminaison Substreams pour exécution.** Le fournisseur Substreams alimente le conteneur WASM avec les données blockchain et les transformations sont appliquées.
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
 4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Élargissez vos connaissances
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 24057933d493a015e1a38c24fdaca43d847c27f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:06 -0500
Subject: [PATCH 0950/1325] New translations substreams.mdx (Spanish)

---
 website/pages/es/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/es/substreams.mdx b/website/pages/es/substreams.mdx
index 8fcd8349f986..34c7e40e05f0 100644
--- a/website/pages/es/substreams.mdx
+++ b/website/pages/es/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From a8b0b848109d4fb063936747f0317b4088753b80 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:07 -0500
Subject: [PATCH 0951/1325] New translations substreams.mdx (Arabic)

---
 website/pages/ar/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/ar/substreams.mdx b/website/pages/ar/substreams.mdx
index cc4cb7918c45..7b73a6aedb7d 100644
--- a/website/pages/ar/substreams.mdx
+++ b/website/pages/ar/substreams.mdx
@@ -4,25 +4,27 @@ title: سبستريمز
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 3c82c6a65c64c6c017118238d48014e2143cd9fb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:08 -0500
Subject: [PATCH 0952/1325] New translations substreams.mdx (Czech)

---
 website/pages/cs/substreams.mdx | 36 +++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/website/pages/cs/substreams.mdx b/website/pages/cs/substreams.mdx
index 7cc86d6a0f04..03213f73f903 100644
--- a/website/pages/cs/substreams.mdx
+++ b/website/pages/cs/substreams.mdx
@@ -4,29 +4,31 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## Jak funguje Substreams ve 4 krocích
 
-1. **Napíšete program v jazyce Rust, který definuje transformace, jež chcete aplikovat na data blockchainu.** Například následující funkce v jazyce Rust extrahuje relevantní informace z bloku Ethereum (číslo, hash a nadřazený hash).
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **Program Rust zabalíte do modulu WASM pouhým spuštěním jediného příkazu CLI.**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **Kontejner WASM je odeslán na koncový bod Substreams k provedení.** Poskytovatel Substreams dodá kontejneru WASM data blockchainu a jsou aplikovány transformace.
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
 4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Rozšiřte své znalosti
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From d69fdefd33734ce1959264535c728ce6d13492d6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:09 -0500
Subject: [PATCH 0953/1325] New translations substreams.mdx (German)

---
 website/pages/de/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/de/substreams.mdx b/website/pages/de/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/de/substreams.mdx
+++ b/website/pages/de/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From dbc400bc3e7922948dd6db4451efdfe9bdb861cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:10 -0500
Subject: [PATCH 0954/1325] New translations substreams.mdx (Italian)

---
 website/pages/it/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/it/substreams.mdx b/website/pages/it/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/it/substreams.mdx
+++ b/website/pages/it/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From e964120622f7137d6928632c2e95c052c3f42ba3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:11 -0500
Subject: [PATCH 0955/1325] New translations substreams.mdx (Japanese)

---
 website/pages/ja/substreams.mdx | 36 +++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/website/pages/ja/substreams.mdx b/website/pages/ja/substreams.mdx
index 4983c635cf7d..77a415fd9511 100644
--- a/website/pages/ja/substreams.mdx
+++ b/website/pages/ja/substreams.mdx
@@ -4,29 +4,31 @@ title: サブストリーム
 
 ![Substreams ロゴ](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## サブストリームの4つのステップ
 
-1. **ブロックチェーンのデータに適用したい変換を定義したRustプログラムを記述します。**例えば、以下のRust関数はイーサリアムのブロックから関連情報（番号、ハッシュ、親ハッシュ）を抽出します。
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **CLIコマンドを1つ実行するだけで、RustプログラムをWASMモジュールにまとめることができます。**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **WASMコンテナは実行のためにSubstreamsエンドポイントに送られます。** SubstreamsプロバイダはWASMコンテナにブロックチェーンデータを送り、変換が適用されます。
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
 4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### 知識を広げよう
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 907abab35257c2c18ea931650abd182ef6e573ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:13 -0500
Subject: [PATCH 0956/1325] New translations substreams.mdx (Korean)

---
 website/pages/ko/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/ko/substreams.mdx b/website/pages/ko/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/ko/substreams.mdx
+++ b/website/pages/ko/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 65019f31f6fdaa9a624fae2ae470319f3e7ba295 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:14 -0500
Subject: [PATCH 0957/1325] New translations substreams.mdx (Dutch)

---
 website/pages/nl/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/nl/substreams.mdx b/website/pages/nl/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/nl/substreams.mdx
+++ b/website/pages/nl/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 7332eae1dd0b998c69cb797dd401265a5683c52a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:15 -0500
Subject: [PATCH 0958/1325] New translations substreams.mdx (Polish)

---
 website/pages/pl/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/pl/substreams.mdx b/website/pages/pl/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/pl/substreams.mdx
+++ b/website/pages/pl/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 7976dec757677da77f506ef9c194cd08faf2c20e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:16 -0500
Subject: [PATCH 0959/1325] New translations substreams.mdx (Portuguese)

---
 website/pages/pt/substreams.mdx | 40 +++++++++++++++++++--------------
 1 file changed, 23 insertions(+), 17 deletions(-)

diff --git a/website/pages/pt/substreams.mdx b/website/pages/pt/substreams.mdx
index 45893eeb079d..de7a8bb99cd5 100644
--- a/website/pages/pt/substreams.mdx
+++ b/website/pages/pt/substreams.mdx
@@ -4,37 +4,39 @@ title: Substreams
 
 ![Logo do Substreams](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## Como o Substreams funciona em 4 passos
 
-1. **Primeiro escreva um programa em Rust, que define as transformações que queres aplicar aos dados em blockchain.** Por exemplo, a seguinte função em Rust extrai informações relevantes de um bloco no Ethereum (número, hash, e hash parente).
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **Embrulhe o seu programa Rust num módulo WASM com a execução de um único comando numa CLI.**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **O container WASM é enviado a um endpoint do Substreams para execução.** O provedor do Substreams alimenta o container WASM com os dados da blockchain e as transformações são aplicadas.
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
-4. **Selecione um [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), um lugar para enviar os dados transformados** (um banco de dados Postgres ou um Subgraph, por exemplo).
+4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
 ## Documentação do Substreams
 
 A documentação oficial do Substreams é mantida atualmente pela equipa do StreamingFast no [site oficial do StreamingFast](https://substreams.streamingfast.io/).
 
-To learn about the latest version of Substreams CLI, which enables developers to bootstrap a Substreams project without any code, please check [Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6).
+Para aprender mais sobre a última versão da CLI do Substreams, que permite que programadores inicializem um projeto de Substreams sem código, confira o [Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6).
 
 ### Como Começar
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expanda o Seu Conhecimento
 
 - Confira o [Tutorial de Explorador de Ethereum](https://substreams.streamingfast.io/tutorials/evm) para aprender as transformações básicas que poderá criar com o Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 2841f7b3404e6b54e3f028a8c352a3621095c5cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:17 -0500
Subject: [PATCH 0960/1325] New translations substreams.mdx (Russian)

---
 website/pages/ru/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/ru/substreams.mdx b/website/pages/ru/substreams.mdx
index a6878e2dc49e..934024fc548a 100644
--- a/website/pages/ru/substreams.mdx
+++ b/website/pages/ru/substreams.mdx
@@ -4,25 +4,27 @@ title: Подпотоки
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 9d9df76712325bbab6a59b41dbb865f69f450dc7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:18 -0500
Subject: [PATCH 0961/1325] New translations substreams.mdx (Swedish)

---
 website/pages/sv/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/sv/substreams.mdx b/website/pages/sv/substreams.mdx
index 9e605493cfc7..bb26b65e3a2c 100644
--- a/website/pages/sv/substreams.mdx
+++ b/website/pages/sv/substreams.mdx
@@ -4,25 +4,27 @@ title: Underströmmar
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 33e0f80147b5fc7bf2ff86a7b115eb165b9a2163 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:19 -0500
Subject: [PATCH 0962/1325] New translations substreams.mdx (Turkish)

---
 website/pages/tr/substreams.mdx | 36 +++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/website/pages/tr/substreams.mdx b/website/pages/tr/substreams.mdx
index aa52656677c6..fbdfd3761b54 100644
--- a/website/pages/tr/substreams.mdx
+++ b/website/pages/tr/substreams.mdx
@@ -4,29 +4,31 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## Substreams Nasıl Çalışır - 4 Adımda
 
-1. **Blok zinciri verilerine uygulamak istediğiniz dönüşümleri tanımlayan bir Rust programı yazarsınız.** Örneğin, aşağıdaki Rust fonksiyonu bir Ethereum bloğundan ilgili bilgileri çıkarır (numara, hash ve üst hash).
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **Sadece tek bir CLI komutu çalıştırarak Rust programınızı bir WASM modülüne çevirirsiniz.**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **WASM konteyneri, yürütme için bir Substreams uç noktasına gönderilir.** Substreams sağlayıcısı, WASM konteynerini blok zincir verileriyle besler ve dönüşümler uygulanır.
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
 4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Bilgi Dağarcığınızı Genişletin
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From e521abf82e217e08752b135398408d0e167ab2b4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:20 -0500
Subject: [PATCH 0963/1325] New translations substreams.mdx (Ukrainian)

---
 website/pages/uk/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/uk/substreams.mdx b/website/pages/uk/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/uk/substreams.mdx
+++ b/website/pages/uk/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 52a73bbdd95ddaeafe776c9e18da38fd598ab5c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:21 -0500
Subject: [PATCH 0964/1325] New translations substreams.mdx (Chinese
 Simplified)

---
 website/pages/zh/substreams.mdx | 36 +++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/website/pages/zh/substreams.mdx b/website/pages/zh/substreams.mdx
index 359a610c10a2..9c09b399c810 100644
--- a/website/pages/zh/substreams.mdx
+++ b/website/pages/zh/substreams.mdx
@@ -4,29 +4,31 @@ title: 子流
 
 ![子流Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## 子流的工作原理分为四个步骤
 
-1. **您编写了一个Rust程序，定义了要应用于区块链数据的转换操作。**例如，以下的Rust函数从以太坊区块中提取相关信息（区块号、哈希和父哈希）。
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **您只需运行一个命令行命令，就可以将您的Rust程序打包成一个WASM模块。**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **WASM容器被发送到Substreams端点执行。** Substreams提供商将区块链数据传送给WASM容器，然后执行转换操作。
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
 4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### 知识拓展
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 9d7c77d4a88c3927604b19223506aacc5b967b72 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:22 -0500
Subject: [PATCH 0965/1325] New translations substreams.mdx (Urdu (Pakistan))

---
 website/pages/ur/substreams.mdx | 36 +++++++++++++++++++--------------
 1 file changed, 21 insertions(+), 15 deletions(-)

diff --git a/website/pages/ur/substreams.mdx b/website/pages/ur/substreams.mdx
index 060d72a059d0..2373b3c71e34 100644
--- a/website/pages/ur/substreams.mdx
+++ b/website/pages/ur/substreams.mdx
@@ -4,29 +4,31 @@ title: سب سٹریمز
 
 ![سب سٹریمز لوگو](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## سب سٹریمز 4 مراحل میں کیسے کام کرتا ہے۔
 
-1. **آپ ایک رسٹ پروگرام لکھتے ہیں، جو ان تبدیلیوں کی وضاحت کرتا ہے جو آپ بلاکچین ڈیٹا پر لاگو کرنا چاہتے ہیں۔** مثال کے طور پر، درج ذیل رسٹ فنکشن ایتھیریم بلاک (نمبر ، ہیش، اور پیرنٹ ہیش)۔
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
-2. **آپ صرف ایک CLI کمانڈ چلا کر اپنے رسٹ پروگرام کو WASM ماڈیول میں سمیٹتے ہیں۔**
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
-3. **WASM کنٹینر کو چلانے کے لیے سب سٹریم اینڈ پوائنٹ پر بھیجا جاتا ہے۔** سب سٹریم فراہم کنندہ WASM کنٹینر کو بلاکچین ڈیٹا کے ساتھ فیڈ کرتا ہے اور تبدیلیاں لاگو ہوتی ہیں۔
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
 
 4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### اپنے علم کو وسعت دیں
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 94a17d0ca0b889d7f04d63b16b1ee72b12456693 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:23 -0500
Subject: [PATCH 0966/1325] New translations substreams.mdx (Vietnamese)

---
 website/pages/vi/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/vi/substreams.mdx b/website/pages/vi/substreams.mdx
index 710e110012cc..6385439f89f0 100644
--- a/website/pages/vi/substreams.mdx
+++ b/website/pages/vi/substreams.mdx
@@ -4,25 +4,27 @@ title: Substreams
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From 8c789f4243f72f9c9862cab3bc3e96dd3b055682 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:24 -0500
Subject: [PATCH 0967/1325] New translations substreams.mdx (Marathi)

---
 website/pages/mr/substreams.mdx | 30 ++++++++++++++++++------------
 1 file changed, 18 insertions(+), 12 deletions(-)

diff --git a/website/pages/mr/substreams.mdx b/website/pages/mr/substreams.mdx
index a0f162be9963..174e1b32d083 100644
--- a/website/pages/mr/substreams.mdx
+++ b/website/pages/mr/substreams.mdx
@@ -4,25 +4,27 @@ title: उपप्रवाह
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
 
 ## How Substreams Works in 4 Steps
 
 1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From fcbd6e73939d7f316bbc782eb55ff24ed6547bd7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:25 -0500
Subject: [PATCH 0968/1325] New translations substreams.mdx (Hindi)

---
 website/pages/hi/substreams.mdx | 34 +++++++++++++++++++--------------
 1 file changed, 20 insertions(+), 14 deletions(-)

diff --git a/website/pages/hi/substreams.mdx b/website/pages/hi/substreams.mdx
index e88c7d5a3a93..b1ab6cedc259 100644
--- a/website/pages/hi/substreams.mdx
+++ b/website/pages/hi/substreams.mdx
@@ -4,25 +4,27 @@ title: सबस्ट्रीम
 
 ![Substreams Logo](/img/substreams-logo.png)
 
-Substreams is a powerful blockchain indexing technology developed for The Graph Network. It enables developers to write Rust modules, compose data streams alongside the community, and provide extremely high-performance indexing due to parallelization in a streaming-first approach.
+Substreams एक शक्तिशाली ब्लॉकचेन indexing तकनीक है जो The Graph Network में प्रदर्शन और स्केलेबिलिटी को बढ़ाने के लिए डिज़ाइन की गई है। यह निम्नलिखित सुविधाएँ प्रदान करती है:
 
-With Substreams, developers can quickly extract data from different blockchains (Ethereum, BNB, Solana, ect.) and send it to various locations of their choice, such as a Postgres database, a Mongo database, or a Subgraph. Additionally, Substreams packages enable developers to specify which data they want to extract from the blockchain.
+- **त्वरित इंडेक्सिंग**: Substreams एक पैरेललाइज्ड इंजन के कारण Subgraph indexing समय को कम करते हैं, जिससे डेटा पुनर्प्राप्ति और प्रोसेसिंग तेजी से होती है।
+- **बहु-श्रृंखला समर्थन**: Substreams EVM-आधारित श्रृंखलाओं के परे इंडेक्सिंग क्षमताओं को विस्तारित करते हैं, जो Solana, Injective, Starknet, and Vara जैसे पारिस्थितिकी तंत्र का समर्थन करते हैं।
+- ** बहु-सींक समर्थन: ** सबग्राफ़, Postgres डेटाबेस, Clickhouse , Mongo डेटाबेस।
 
 ## How Substreams Works in 4 Steps
 
-1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
+1. **आप एक Rust प्रोग्राम लिखते हैं, जो उन ट्रांसफॉर्मेशन्स को परिभाषित करता है जिन्हें आप ब्लॉकचेन डेटा पर लागू करना चाहते हैं।** उदाहरण के लिए, निम्नलिखित Rust फ़ंक्शन एक Ethereum ब्लॉक से प्रासंगिक जानकारी निकालता है (नंबर, हैश, और पेरेंट हैश)।
 
-```rust
-fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
-    let header = blk.header.as_ref().unwrap();
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
 
-    Ok(MyBlock {
-        number: blk.number,
-        hash: Hex::encode(&blk.hash),
-        parent_hash: Hex::encode(&header.parent_hash),
-    })
-}
-```
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
 
 2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
 
@@ -34,7 +36,7 @@ fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
 
 The official Substreams documentation is currently maintained by the StreamingFast team [on the StreamingFast website](https://substreams.streamingfast.io/).
 
-To learn about the latest version of Substreams CLI, which enables developers to bootstrap a Substreams project without any code, please check [Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6).
+Substreams CLI के नवीनतम संस्करण के बारे में जानने के लिए, जो डेवलपर्स को बिना किसी कोड के Substreams प्रोजेक्ट को बूटस्ट्रैप करने में सक्षम बनाता है, कृपया [Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) को चेक करें।
 
 ### शुरू करना
 
@@ -44,3 +46,7 @@ To learn about the latest version of Substreams CLI, which enables developers to
 ### Expand Your Knowledge
 
 - Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams रजिस्ट्र्री
+
+एक Substreams पैकेज एक पूर्व-कंपाइल किया हुआ बाइनरी फ़ाइल है जो उस विशेष डेटा को परिभाषित करता है जिसे आप ब्लॉकचेन से निकालना चाहते हैं, पारंपरिक subgraphs में `mapping.ts` फ़ाइल के समान। विभिन्न ब्लॉकचेन नेटवर्क पर उपयोग के लिए तैयार Substreams पैकेजों के बढ़ते संग्रह की खोज के लिए [substreams.dev](https://substreams.dev/) पर जाएं।

From 64eff8fb30c9f98388f5546efb74d5091d7ca67a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:27 -0500
Subject: [PATCH 0969/1325] New translations substreams.mdx (Swahili)

---
 website/pages/sw/substreams.mdx | 52 +++++++++++++++++++++++++++++++++
 1 file changed, 52 insertions(+)
 create mode 100644 website/pages/sw/substreams.mdx

diff --git a/website/pages/sw/substreams.mdx b/website/pages/sw/substreams.mdx
new file mode 100644
index 000000000000..6385439f89f0
--- /dev/null
+++ b/website/pages/sw/substreams.mdx
@@ -0,0 +1,52 @@
+---
+title: Substreams
+---
+
+![Substreams Logo](/img/substreams-logo.png)
+
+Substreams is a powerful blockchain indexing technology designed to enhance performance and scalability within The Graph Network. It offers the following features:
+
+- **Accelerated Indexing**: Substreams reduce subgraph indexing time thanks to a parallelized engine, enabling faster data retrieval and processing.
+- **Multi-Chain Support**: Substreams expand indexing capabilities beyond EVM-based chains, supporting ecosystems like Solana, Injective, Starknet, and Vara.
+- **Multi-Sink Support:** Subgraph, Postgres database, Clickhouse, Mongo database
+
+## How Substreams Works in 4 Steps
+
+1. **You write a Rust program, which defines the transformations that you want to apply to the blockchain data.** For example, the following Rust function extracts relevant information from an Ethereum block (number, hash, and parent hash).
+
+   ```rust
+   fn get_my_block(blk: Block) -> Result<MyBlock, substreams::errors::Error> {
+       let header = blk.header.as_ref().unwrap();
+
+       Ok(MyBlock {
+           number: blk.number,
+           hash: Hex::encode(&blk.hash),
+           parent_hash: Hex::encode(&header.parent_hash),
+       })
+   }
+   ```
+
+2. **You wrap up your Rust program into a WASM module just by running a single CLI command.**
+
+3. **The WASM container is sent to a Substreams endpoint for execution.** The Substreams provider feeds the WASM container with the blockchain data and the transformations are applied.
+
+4. **You select a [sink](https://substreams.streamingfast.io/documentation/consume/other-sinks), a place where you want to send the transformed data** (a Postgres database or a Subgraph, for example).
+
+## Substreams Documentation
+
+The official Substreams documentation is currently maintained by the StreamingFast team [on the StreamingFast website](https://substreams.streamingfast.io/).
+
+To learn about the latest version of Substreams CLI, which enables developers to bootstrap a Substreams project without any code, please check [Substreams Codegen](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6).
+
+### Getting Started
+
+- In order to develop and deploy a Substreams, [you must install the Substreams CLI](https://substreams.streamingfast.io/documentation/consume/installing-the-cli).
+- Then, run your first Substreams by following the [Quickstart Tutorial](https://substreams.streamingfast.io/documentation/develop/init-project).
+
+### Expand Your Knowledge
+
+- Take a look at the [Ethereum Explorer Tutorial](https://substreams.streamingfast.io/tutorials/evm) to learn about the basic transformations you can create with Substreams.
+
+### Substreams Registry
+
+A Substreams package is a precompiled binary file that defines the specific data you want to extract from the blockchain, similar to the `mapping.ts` file in traditional subgraphs. Visit [substreams.dev](https://substreams.dev/) to explore a growing collection of ready-to-use Substreams packages across various blockchain networks.

From dad8ec709beb4cd5f22c7516b2186b0a31b53957 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:28 -0500
Subject: [PATCH 0970/1325] New translations operating-graph-node.mdx
 (Romanian)

---
 website/pages/ro/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ro/operating-graph-node.mdx b/website/pages/ro/operating-graph-node.mdx
index dbbfcd5fc545..fb3d538f952a 100644
--- a/website/pages/ro/operating-graph-node.mdx
+++ b/website/pages/ro/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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.
 

From 5ac21289e66ee2a93c6675724b390ff42d054a3a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:29 -0500
Subject: [PATCH 0971/1325] New translations operating-graph-node.mdx (French)

---
 website/pages/fr/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/fr/operating-graph-node.mdx b/website/pages/fr/operating-graph-node.mdx
index 252894e113a0..329f1ac72adf 100644
--- a/website/pages/fr/operating-graph-node.mdx
+++ b/website/pages/fr/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Un exemple complet de configuration de Kubernetes est disponible dans le [dépô
 
 Lorsqu'il est en cours d'exécution, Graph Node expose les ports suivants :
 
-| Port | Objectif | Routes | Argument CLI | Variable d'environnement |
-| --- | --- | --- | --- | --- |
-| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(pour gérer les déploiements) | / | --admin-port | - |
-| 8030 | API de statut d'indexation des subgraphs | /graphq | --index-node-port | - |
-| 8040 | Métriques Prometheus | /metrics | --metrics-port | - |
+| Port | Objectif                                                         | Routes                                               | Argument CLI      | Variable d'environnement |
+| ---- | ---------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------------ |
+| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                        |
+| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                        |
+| 8020 | JSON-RPC<br />(pour gérer les déploiements)                | /                                                    | --admin-port      | -                        |
+| 8030 | API de statut d'indexation des subgraphs                         | /graphq                                              | --index-node-port | -                        |
+| 8040 | Métriques Prometheus                                             | /metrics                                             | --metrics-port    | -                        |
 
 > **Important** : Soyez prudent lorsque vous exposez les ports publiquement : les **ports d'administration** doivent rester verrouillés. Cela inclut le point de terminaison Graph Node JSON-RPC.
 

From f678004eded7ef91f495091510daeb50eedc04d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:30 -0500
Subject: [PATCH 0972/1325] New translations operating-graph-node.mdx (Spanish)

---
 website/pages/es/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/es/operating-graph-node.mdx b/website/pages/es/operating-graph-node.mdx
index 2dc80685b400..99e966da590a 100644
--- a/website/pages/es/operating-graph-node.mdx
+++ b/website/pages/es/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Puedes encontrar un ejemplo completo de configuración de Kubernetes en el [Inde
 
 Cuando está funcionando, Graph Node muestra los siguientes puertos:
 
-| Puerto | Objeto | Rutas | Argumento CLI | Variable de Entorno |
-| --- | --- | --- | --- | --- |
-| 8000 | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(para suscripciones a subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(para administrar implementaciones) | / | --admin-port | - |
-| 8030 | API de estado de indexación de subgrafos | /graphql | --index-node-port | - |
-| 8040 | Métricas de Prometheus | /metrics | --metrics-port | - |
+| Puerto | Objeto                                                         | Rutas                                                | Argumento CLI     | Variable de Entorno |
+| ------ | -------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------- |
+| 8000   | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                   |
+| 8001   | GraphQL WS<br />(para suscripciones a subgrafos)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                   |
+| 8020   | JSON-RPC<br />(para administrar implementaciones)        | /                                                    | --admin-port      | -                   |
+| 8030   | API de estado de indexación de subgrafos                       | /graphql                                             | --index-node-port | -                   |
+| 8040   | Métricas de Prometheus                                         | /metrics                                             | --metrics-port    | -                   |
 
 > **Importante**: Ten cuidado con exponer puertos públicamente - los **puertos de administración** deben mantenerse bloqueados. Esto incluye el punto final JSON-RPC de Graph Node.
 

From 47c05db5e9f1baf03f825170cfc4666eaa879d4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:31 -0500
Subject: [PATCH 0973/1325] New translations operating-graph-node.mdx (Arabic)

---
 website/pages/ar/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ar/operating-graph-node.mdx b/website/pages/ar/operating-graph-node.mdx
index ec9595ef8404..ac2816215c96 100644
--- a/website/pages/ar/operating-graph-node.mdx
+++ b/website/pages/ar/operating-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:
 
-| المنفذ | الغرض | المسار | CLI Argument | متغيرات البيئة |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port-- | - |
-| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port-- | - |
-| 8020 | JSON-RPC <br /> (for managing deployments) | / | admin-port-- | - |
-| 8030 | Subgraph indexing status API | /graphql | index-node-port-- | - |
-| 8040 | Prometheus metrics | /metrics | metrics-port-- | - |
+| المنفذ | الغرض                                                   | المسار                                                              | CLI Argument      | متغيرات البيئة |
+| ------ | ------------------------------------------------------- | ------------------------------------------------------------------- | ----------------- | -------------- |
+| 8000   | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port--       | -              |
+| 8001   | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port--         | -              |
+| 8020   | JSON-RPC <br /> (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.
 

From 3ed3a6c8f0eb4f59facc42c9431429de8085ba8d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:32 -0500
Subject: [PATCH 0974/1325] New translations operating-graph-node.mdx (Czech)

---
 website/pages/cs/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/cs/operating-graph-node.mdx b/website/pages/cs/operating-graph-node.mdx
index b6067883a47a..9a720348c8c5 100644
--- a/website/pages/cs/operating-graph-node.mdx
+++ b/website/pages/cs/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Kompletní příklad konfigurace Kubernetes naleznete v úložišti [indexer](ht
 
 Když je Graf Uzel spuštěn, zpřístupňuje následující ports:
 
-| Port | Účel | Trasy | CLI Argument | Proměnná prostředí |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(pro odběry podgrafů) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(pro správu nasazení) | / | --admin-port | - |
-| 8030 | Stav indexování podgrafů API | /graphql | --index-node-port | - |
-| 8040 | Metriky Prometheus | /metrics | --metrics-port | - |
+| Port | Účel                                                 | Trasy                                                | CLI Argument      | Proměnná prostředí |
+| ---- | ---------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
+| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
+| 8001 | GraphQL WS<br />(pro odběry podgrafů)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
+| 8020 | JSON-RPC<br />(pro správu nasazení)            | /                                                    | --admin-port      | -                  |
+| 8030 | Stav indexování podgrafů API                         | /graphql                                             | --index-node-port | -                  |
+| 8040 | Metriky Prometheus                                   | /metrics                                             | --metrics-port    | -                  |
 
 > **Důležité**: Dávejte pozor na veřejné vystavování portů - **administrační porty** by měly být uzamčeny. To se týká i koncového bodu JSON-RPC uzlu Graf.
 

From 6e4b508cd926feed4d76f612a19c723c72a9a3f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:33 -0500
Subject: [PATCH 0975/1325] New translations operating-graph-node.mdx (German)

---
 website/pages/de/operating-graph-node.mdx | 86 +++++++++++------------
 1 file changed, 43 insertions(+), 43 deletions(-)

diff --git a/website/pages/de/operating-graph-node.mdx b/website/pages/de/operating-graph-node.mdx
index 1db929271a01..571f332cd774 100644
--- a/website/pages/de/operating-graph-node.mdx
+++ b/website/pages/de/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Eine vollständige Kubernetes-Beispielkonfiguration finden Sie im [Indexer-Repos
 
 Wenn es ausgeführt wird, stellt Graph Node die folgenden Ports zur Verfügung:
 
-| Port | Zweck | Routen | CLI-Argument | Umgebungsvariable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(für Subgraf-Abonnements) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(zum Verwalten von Deployments) | / | --admin-port | - |
-| 8030 | Subgraf-Indizierungsstatus-API | /graphql | --index-node-port | - |
-| 8040 | Prometheus-Metriken | /metrics | --metrics-port | - |
+| Port | Zweck                                                 | Routen                                               | CLI-Argument      | Umgebungsvariable |
+| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | ----------------- |
+| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                 |
+| 8001 | GraphQL WS<br />(für Subgraf-Abonnements)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                 |
+| 8020 | JSON-RPC<br />(zum Verwalten von Deployments)   | /                                                    | --admin-port      | -                 |
+| 8030 | Subgraf-Indizierungsstatus-API                        | /graphql                                             | --index-node-port | -                 |
+| 8040 | Prometheus-Metriken                                   | /metrics                                             | --metrics-port    | -                 |
 
 > **Wichtig**: Seien Sie vorsichtig, wenn Sie Ports öffentlich zugänglich machen - **Administrationsports** sollten gesperrt bleiben. Dies schließt den JSON-RPC-Endpunkt des Graph-Knotens ein.
 
@@ -97,9 +97,9 @@ Dieses Setup kann horizontal skaliert werden, indem mehrere Graph-Knoten und meh
 
 Eine [TOML](https://toml.io/en/)-Konfigurationsdatei kann verwendet werden, um komplexere Konfigurationen als die in der CLI bereitgestellten festzulegen. Der Speicherort der Datei wird mit dem Befehlszeilenschalter --config übergeben.
 
-> When using a configuration file, it is not possible to use the options --postgres-url, --postgres-secondary-hosts, and --postgres-host-weights.
+> Bei Verwendung einer Konfigurationsdatei ist es nicht möglich, die Optionen --postgres-url, --postgres-secondary-hosts und --postgres-host-weights zu verwenden.
 
-A minimal `config.toml` file can be provided; the following file is equivalent to using the --postgres-url command line option:
+Eine minimale `config.toml`-Datei kann bereitgestellt werden; Die folgende Datei entspricht der Verwendung der Befehlszeilenoption --postgres-url:
 
 ```toml
 [store]
@@ -110,19 +110,19 @@ connection="<.. postgres-url argument ..>"
 indexers = [ "<.. list of all indexing nodes ..>" ]
 ```
 
-Full documentation of `config.toml` can be found in the [Graph Node docs](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md).
+Die vollständige Dokumentation von `config.toml` finden Sie in den [Graph Node Dokumenten](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md).
 
-#### Multiple Graph Nodes
+#### Mehrere Graph-Knoten
 
 Graph Node indexing can scale horizontally, running multiple instances of Graph Node to split indexing and querying across different nodes. This can be done simply by running Graph Nodes configured with a different `node_id` on startup (e.g. in the Docker Compose file), which can then be used in the `config.toml` file to specify [dedicated query nodes](#dedicated-query-nodes), [block ingestors](#dedicated-block-ingestion), and splitting subgraphs across nodes with [deployment rules](#deployment-rules).
 
-> Note that multiple Graph Nodes can all be configured to use the same database, which itself can be horizontally scaled via sharding.
+> Beachten Sie darauf, dass mehrere Graph-Knoten so konfiguriert werden können, dass sie dieselbe Datenbank verwenden, die ihrerseits durch Sharding horizontal skaliert werden kann.
 
-#### Deployment rules
+#### Bereitstellungsregeln
 
 Given multiple Graph Nodes, it is necessary to manage deployment of new subgraphs so that the same subgraph isn't being indexed by two different nodes, which would lead to collisions. This can be done by using deployment rules, which can also specify which `shard` a subgraph's data should be stored in, if database sharding is being used. Deployment rules can match on the subgraph name and the network that the deployment is indexing in order to make a decision.
 
-Example deployment rule configuration:
+Beispielkonfiguration für Bereitstellungsregeln:
 
 ```toml
 [deployment]
@@ -150,49 +150,49 @@ indexers = [
   ]
 ```
 
-Read more about deployment rules [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#controlling-deployment).
+Weitere Informationen zu Bereitstellungsregeln finden Sie [hier](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#controlling-deployment).
 
-#### Dedicated query nodes
+#### Dedizierte Abfrageknoten
 
-Nodes can be configured to explicitly be query nodes by including the following in the configuration file:
+Knoten können explizit als Abfrageknoten konfiguriert werden, indem Sie Folgendes in die Konfigurationsdatei aufnehmen:
 
 ```toml
 [general]
 query = "<regular expression>"
 ```
 
-Any node whose --node-id matches the regular expression will be set up to only respond to queries.
+Jeder Knoten, dessen --node-id mit dem regulären Ausdruck übereinstimmt, wird so eingerichtet, dass er nur auf Abfragen antwortet.
 
-#### Database scaling via sharding
+#### Datenbankskalierung durch Sharding
 
-For most use cases, a single Postgres database is sufficient to support a graph-node instance. When a graph-node instance outgrows a single Postgres database, it is possible to split the storage of graph-node's data across multiple Postgres databases. All databases together form the store of the graph-node instance. Each individual database is called a shard.
+Für die meisten Anwendungsfälle reicht eine einzelne Postgres-Datenbank aus, um eine Graph-Node-Instanz zu unterstützen. Wenn eine Graph-Node-Instanz aus einer einzelnen Postgres-Datenbank herauswächst, ist es möglich, die Speicherung der Daten des Graph-Nodes auf mehrere Postgres-Datenbanken aufzuteilen. Alle Datenbanken zusammen bilden den Speicher der Graph-Node-Instanz. Jede einzelne Datenbank wird als Shard bezeichnet.
 
 Shards can be used to split subgraph deployments across multiple databases, and can also be used to use replicas to spread query load across databases. This includes configuring the number of available database connections each `graph-node` should keep in its connection pool for each database, which becomes increasingly important as more subgraphs are being indexed.
 
-Sharding becomes useful when your existing database can't keep up with the load that Graph Node puts on it, and when it's not possible to increase the database size anymore.
+Sharding wird nützlich, wenn Ihre vorhandene Datenbank nicht mit der Last Schritt halten kann, die Graph Node ihr auferlegt, und wenn es nicht mehr möglich ist, die Datenbankgröße zu erhöhen.
 
 > It is generally better make a single database as big as possible, before starting with shards. One exception is where query traffic is split very unevenly between subgraphs; in those situations it can help dramatically if the high-volume subgraphs are kept in one shard and everything else in another because that setup makes it more likely that the data for the high-volume subgraphs stays in the db-internal cache and doesn't get replaced by data that's not needed as much from low-volume subgraphs.
 
-In terms of configuring connections, start with max_connections in postgresql.conf set to 400 (or maybe even 200) and look at the store_connection_wait_time_ms and store_connection_checkout_count Prometheus metrics. Noticeable wait times (anything above 5ms) is an indication that there are too few connections available; high wait times there will also be caused by the database being very busy (like high CPU load). However if the database seems otherwise stable, high wait times indicate a need to increase the number of connections. In the configuration, how many connections each graph-node instance can use is an upper limit, and Graph Node will not keep connections open if it doesn't need them.
+Was das Konfigurieren von Verbindungen betrifft, beginnen Sie mit max_connections in postgresql.conf, das auf 400 (oder vielleicht sogar 200) eingestellt ist, und sehen Sie sich die Prometheus-Metriken store_connection_wait_time_ms und store_connection_checkout_count an. Spürbare Wartezeiten (alles über 5 ms) sind ein Hinweis darauf, dass zu wenige Verbindungen verfügbar sind; hohe Wartezeiten werden auch dadurch verursacht, dass die Datenbank sehr ausgelastet ist (z. B. hohe CPU-Last). Wenn die Datenbank jedoch ansonsten stabil erscheint, weisen hohe Wartezeiten darauf hin, dass die Anzahl der Verbindungen erhöht werden muss. In der Konfiguration ist die Anzahl der Verbindungen, die jede Graph-Knoten-Instanz verwenden kann, eine Obergrenze, und der Graph-Knoten hält Verbindungen nicht offen, wenn er sie nicht benötigt.
 
-Read more about store configuration [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-multiple-databases).
+Weitere Informationen zur Speicherkonfiguration finden Sie [hier](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-multiple-databases).
 
-#### Dedicated block ingestion
+#### Dedizierte Blockaufnahme
 
-If there are multiple nodes configured, it will be necessary to specify one node which is responsible for ingestion of new blocks, so that all configured index nodes aren't polling the chain head. This is done as part of the `chains` namespace, specifying the `node_id` to be used for block ingestion:
+Wenn mehrere Knoten konfiguriert sind, muss ein Knoten angegeben werden, der für die Aufnahme neuer Blöcke verantwortlich ist, damit nicht alle konfigurierten Indexknoten den Kettenkopf abfragen. Dies geschieht als Teil des `chains`-Namespace, der die `node_id` angibt, die für die Blockaufnahme verwendet werden soll:
 
 ```toml
 [chains]
 ingestor = "block_ingestor_node"
 ```
 
-#### Supporting multiple networks
+#### Unterstützung mehrerer Netzwerke
 
-The Graph Protocol is increasing the number of networks supported for indexing rewards, and there exist many subgraphs indexing unsupported networks which an indexer would like to process. The `config.toml` file allows for expressive and flexible configuration of:
+Das Graph-Protokoll erhöht die Anzahl der Netzwerke, die für die Indizierung von Belohnungen unterstützt werden, und es gibt viele Subgraphen, die nicht unterstützte Netzwerke indizieren, die ein Indexer verarbeiten möchte. Die Datei `config.toml` ermöglicht eine ausdrucksstarke und flexible Konfiguration von:
 
-- Multiple networks
-- Multiple providers per network (this can allow splitting of load across providers, and can also allow for configuration of full nodes as well as archive nodes, with Graph Node preferring cheaper providers if a given workload allows).
-- Additional provider details, such as features, authentication and the type of provider (for experimental Firehose support)
+- Mehrere Netzwerke
+- Mehrere Anbieter pro Netzwerk (dies kann eine Aufteilung der Last auf Anbieter ermöglichen und kann auch die Konfiguration von vollständigen Knoten sowie Archivknoten ermöglichen, wobei Graph Node günstigere Anbieter bevorzugt, wenn eine bestimmte Arbeitslast dies zulässt).
+- Zusätzliche Anbieterdetails, wie Funktionen, Authentifizierung und Anbietertyp (für experimentelle Firehose-Unterstützung)
 
 The `[chains]` section controls the ethereum providers that graph-node connects to, and where blocks and other metadata for each chain are stored. The following example configures two chains, mainnet and kovan, where blocks for mainnet are stored in the vip shard and blocks for kovan are stored in the primary shard. The mainnet chain can use two different providers, whereas kovan only has one provider.
 
@@ -210,17 +210,17 @@ shard = "primary"
 provider = [ { label = "kovan", url = "http://..", features = [] } ]
 ```
 
-Read more about provider configuration [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-ethereum-providers).
+Weitere Informationen zur Anbieterkonfiguration finden Sie [hier](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-ethereum-providers).
 
-### Environment variables
+### Umgebungsvariablen
 
-Graph Node supports a range of environment variables which can enable features, or change Graph Node behaviour. These are documented [here](https://github.com/graphprotocol/graph-node/blob/master/docs/environment-variables.md).
+Graph Node unterstützt eine Reihe von Umgebungsvariablen, die Funktionen aktivieren oder das Verhalten von Graph Node ändern können. Diese sind [hier](https://github.com/graphprotocol/graph-node/blob/master/docs/environment-variables.md) dokumentiert.
 
-### Continuous deployment
+### Kontinuierlicher Einsatz
 
-Users who are operating a scaled indexing setup with advanced configuration may benefit from managing their Graph Nodes with Kubernetes.
+Benutzer, die ein skaliertes Indizierungs-Setup mit erweiterter Konfiguration betreiben, können von der Verwaltung ihrer Graph-Knoten mit Kubernetes profitieren.
 
-- The indexer repository has an [example Kubernetes reference](https://github.com/graphprotocol/indexer/tree/main/k8s)
+- Das Indexer-Repository enthält eine [Beispielreferenz für Kubernetes](https://github.com/graphprotocol/indexer/tree/main/k8s)
 - [Launchpad](https://docs.graphops.xyz/launchpad/intro) is a toolkit for running a Graph Protocol Indexer on Kubernetes maintained by GraphOps. It provides a set of Helm charts and a CLI to manage a Graph Node deployment.
 
 ### Managing Graph Node
@@ -231,25 +231,25 @@ Given a running Graph Node (or Graph Nodes!), the challenge is then to manage de
 
 Graph Node's logs can provide useful information for debugging and optimisation of Graph Node and specific subgraphs. Graph Node supports different log levels via the `GRAPH_LOG` environment variable, with the following levels: error, warn, info, debug or trace.
 
-In addition setting `GRAPH_LOG_QUERY_TIMING` to `gql` provides more details about how GraphQL queries are running (though this will generate a large volume of logs).
+Außerdem bietet das Festlegen von `GRAPH_LOG_QUERY_TIMING` auf `gql` weitere Details darüber, wie GraphQL-Abfragen ausgeführt werden (obwohl dies eine große Menge an Protokollen generieren wird).
 
-#### Monitoring & alerting
+#### Überwachung & Warnungen
 
-Graph Node provides the metrics via Prometheus endpoint on 8040 port by default. Grafana can then be used to visualise these metrics.
+Graph Node stellt die Metriken standardmäßig durch den Prometheus-Endpunkt am Port 8040 bereit. Grafana kann dann zur Visualisierung dieser Metriken verwendet werden.
 
-The indexer repository provides an [example Grafana configuration](https://github.com/graphprotocol/indexer/blob/main/k8s/base/grafana.yaml).
+Das Indexer-Repository bietet eine [Beispielkonfiguration für Grafana](https://github.com/graphprotocol/indexer/blob/main/k8s/base/grafana.yaml).
 
 #### Graphman
 
-`graphman` is a maintenance tool for Graph Node, helping with diagnosis and resolution of different day-to-day and exceptional tasks.
+`graphman` ist ein Wartungstool für Graph Node, das bei der Diagnose und Lösung verschiedener alltäglicher und außergewöhnlicher Aufgaben hilft.
 
 The graphman command is included in the official containers, and you can docker exec into your graph-node container to run it. It requires a `config.toml` file.
 
-Full documentation of `graphman` commands is available in the Graph Node repository. See \[/docs/graphman.md\] (https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md) in the Graph Node `/docs`
+Eine vollständige Dokumentation der `graphman`-Befehle ist im Graph Node-Repository verfügbar. Siehe \[/docs/graphman.md\] (https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md) im Graph Node `/docs`
 
 ### Working with subgraphs
 
-#### Indexing status API
+#### Indizierungsstatus-API
 
 Available on port 8030/graphql by default, the indexing status API exposes a range of methods for checking indexing status for different subgraphs, checking proofs of indexing, inspecting subgraph features and more.
 

From a58a417cb58f5bf0cb26ee8c0be422a337e009ee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:35 -0500
Subject: [PATCH 0976/1325] New translations operating-graph-node.mdx (Italian)

---
 website/pages/it/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/it/operating-graph-node.mdx b/website/pages/it/operating-graph-node.mdx
index b3b3ca24e204..276c3022ec6c 100644
--- a/website/pages/it/operating-graph-node.mdx
+++ b/website/pages/it/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Un esempio completo di configurazione Kubernetes si trova nel [repository indexe
 
 Quando è in funzione, Graph Node espone le seguenti porte:
 
-| Porta | Obiettivo | Routes | Argomento CLI | Variabile d'ambiente |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(per la gestione dei deployment) | / | --admin-port | - |
-| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
-| 8040 | Metriche di Prometheus | /metrics | --metrics-port | - |
+| Porta | Obiettivo                                                 | Routes                                               | Argomento CLI     | Variabile d'ambiente |
+| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000  | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001  | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020  | JSON-RPC<br />(per la gestione dei deployment)      | /                                                    | --admin-port      | -                    |
+| 8030  | Subgraph indexing status API                              | /graphql                                             | --index-node-port | -                    |
+| 8040  | Metriche di Prometheus                                    | /metrics                                             | --metrics-port    | -                    |
 
 > **Importante**: fare attenzione a esporre le porte pubblicamente - le porte di **amministrazione** devono essere tenute sotto chiave. Questo include l'endpoint JSON-RPC del Graph Node.
 

From 76a4726c9d7e14ce104c9132980a26622a45e2a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:36 -0500
Subject: [PATCH 0977/1325] New translations operating-graph-node.mdx
 (Japanese)

---
 website/pages/ja/operating-graph-node.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/ja/operating-graph-node.mdx b/website/pages/ja/operating-graph-node.mdx
index cb9e4f14e8f3..71da764773e6 100644
--- a/website/pages/ja/operating-graph-node.mdx
+++ b/website/pages/ja/operating-graph-node.mdx
@@ -26,7 +26,7 @@ title: オペレーティンググラフノード
 
 ### IPFSノード
 
-IPFS ノード（バージョン 未満） - サブグラフのデプロイメタデータは IPFS ネットワーク上に保存されます。 グラフノードは、サブグラフのデプロイ時に主に IPFS ノードにアクセスし、サブグラフマニフェストと全てのリンクファイルを取得します。 ネットワーク・インデクサーは独自の IPFS ノードをホストする必要はありません。 ネットワーク用の IPFS ノードは、https://ipfs.network.thegraph.com でホストされています。
+IPFS ノード（バージョン  未満） - サブグラフのデプロイメタデータは IPFS ネットワーク上に保存されます。 グラフノードは、サブグラフのデプロイ時に主に IPFS ノードにアクセスし、サブグラフマニフェストと全てのリンクファイルを取得します。 ネットワーク・インデクサーは独自の IPFS ノードをホストする必要はありません。 ネットワーク用の IPFS ノードは、https://ipfs.network.thegraph.com でホストされています。
 
 ### Prometheus メトリクスサーバー
 
@@ -77,13 +77,13 @@ Kubernetesの完全な設定例は、[indexerリポジトリ](https://github.com
 
 グラフノードは起動時に以下のポートを公開します。
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC <br /> (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 <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC <br /> (for managing deployments)        | /                                                      | --admin-port      | -                    |
+| 8030 | Subgraph indexing status API                            | /graphql                                               | --index-node-port | -                    |
+| 8040 | Prometheus metrics                                      | /metrics                                               | --metrics-port    | -                    |
 
 > **重要**: ポートを公に公開する場合は注意してください。**管理ポート**はロックしておく必要があります。ノードの JSON-RPC エンドポイント
 

From 434d14739ea61db5ad2c29f3aa9f91ed0e0cacdd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:37 -0500
Subject: [PATCH 0978/1325] New translations operating-graph-node.mdx (Korean)

---
 website/pages/ko/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ko/operating-graph-node.mdx b/website/pages/ko/operating-graph-node.mdx
index dbbfcd5fc545..fb3d538f952a 100644
--- a/website/pages/ko/operating-graph-node.mdx
+++ b/website/pages/ko/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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.
 

From 6f7cb0e0aaf2d4e287ec8b7452b1c89be8395345 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:38 -0500
Subject: [PATCH 0979/1325] New translations operating-graph-node.mdx (Dutch)

---
 website/pages/nl/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/nl/operating-graph-node.mdx b/website/pages/nl/operating-graph-node.mdx
index d2117bcf07d5..7524b17721c9 100644
--- a/website/pages/nl/operating-graph-node.mdx
+++ b/website/pages/nl/operating-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:
 
-| Poort | Doel | Routes | CLI-Argument | Omgevingsvariabele |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(voor subgraph query's) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(voor subgraph abonnementen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(voor het beheren van implementaties) | / | --admin-port | - |
-| 8030 | Subgraph indexeerstatus API | /graphql | --index-node-port | - |
-| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
+| Poort | Doel                                                      | Routes                                               | CLI-Argument      | Omgevingsvariabele |
+| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
+| 8000  | GraphQL HTTP server<br />(voor subgraph query's)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
+| 8001  | GraphQL WS<br />(voor subgraph abonnementen)        | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
+| 8020  | JSON-RPC<br />(voor het beheren van implementaties) | /                                                    | --admin-port      | -                  |
+| 8030  | Subgraph indexeerstatus 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.
 

From 7783460a394004140028b4225e36e5251f4940be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:39 -0500
Subject: [PATCH 0980/1325] New translations operating-graph-node.mdx (Polish)

---
 website/pages/pl/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/pl/operating-graph-node.mdx b/website/pages/pl/operating-graph-node.mdx
index dbbfcd5fc545..fb3d538f952a 100644
--- a/website/pages/pl/operating-graph-node.mdx
+++ b/website/pages/pl/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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.
 

From 3d8a8429f4c0c78e2d4215160a3098086858b9f5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:40 -0500
Subject: [PATCH 0981/1325] New translations operating-graph-node.mdx
 (Portuguese)

---
 website/pages/pt/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/pt/operating-graph-node.mdx b/website/pages/pt/operating-graph-node.mdx
index 38202b73da9c..5eb6c795dcd5 100644
--- a/website/pages/pt/operating-graph-node.mdx
+++ b/website/pages/pt/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Veja uma configuração de exemplo completa do Kubernetes no [repositório de in
 
 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<br />(para queries de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | WS GraphQL<br />(para inscrições a subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(para gerir lançamentos) | / | --admin-port | - |
-| 8030 | API de status de indexamento 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<br />(para queries de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001  | WS GraphQL<br />(para inscrições a subgraphs)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020  | JSON-RPC<br />(para gerir lançamentos)                | /                                                    | --admin-port      | -                    |
+| 8030  | API de status de indexamento do subgraph                    | /graphql                                             | --index-node-port | -                    |
+| 8040  | Métricas Prometheus                                         | /metrics                                             | --metrics-port    | -                    |
 
 > **Importante:** Cuidado ao expor portas publicamente; as **portas de administração** devem ser trancadas a sete chaves. Isto inclui o endpoint JSON-RPC do Graph Node.
 

From 9588d38fd9cd9bbdf09020a5e6afa033bf50b92f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:41 -0500
Subject: [PATCH 0982/1325] New translations operating-graph-node.mdx (Russian)

---
 website/pages/ru/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ru/operating-graph-node.mdx b/website/pages/ru/operating-graph-node.mdx
index dad9f543237a..d4ac6c51a05d 100644
--- a/website/pages/ru/operating-graph-node.mdx
+++ b/website/pages/ru/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 Во время работы Graph Node предоставляет следующие порты:
 
-| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
-| --- | --- | --- | --- | --- |
-| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(для подписок на подграфы) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(для управления процессом развертывания) | / | --admin-port | - |
-| 8030 | API для определения статуса индексирования подграфов | /graphql | --index-node-port | - |
-| 8040 | Показатели Prometheus | /metrics | --metrics-port | - |
+| Порт | Назначение                                                   | Расположение                                         | CLI-аргумент      | Переменная среды |
+| ---- | ------------------------------------------------------------ | ---------------------------------------------------- | ----------------- | ---------------- |
+| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                |
+| 8001 | GraphQL WS<br />(для подписок на подграфы)             | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                |
+| 8020 | JSON-RPC<br />(для управления процессом развертывания) | /                                                    | --admin-port      | -                |
+| 8030 | API для определения статуса индексирования подграфов         | /graphql                                             | --index-node-port | -                |
+| 8040 | Показатели Prometheus                                        | /metrics                                             | --metrics-port    | -                |
 
 > **Важно**. Будьте осторожны, открывая порты для общего доступа — **порты администрирования** должны быть заблокированы. Это касается конечных точек Graph Node JSON-RPC.
 

From 0165ff37167779cdd8b55c956795471f9d428fac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:42 -0500
Subject: [PATCH 0983/1325] New translations operating-graph-node.mdx (Swedish)

---
 website/pages/sv/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/sv/operating-graph-node.mdx b/website/pages/sv/operating-graph-node.mdx
index 65b506e574dd..83c59421c17b 100644
--- a/website/pages/sv/operating-graph-node.mdx
+++ b/website/pages/sv/operating-graph-node.mdx
@@ -77,13 +77,13 @@ En komplett exempelkonfiguration för Kubernetes finns i [indexer repository](ht
 
 När Graph Node är igång exponerar den följande portar:
 
-| Port | Syfte | Rutter | Argument för CLI | Miljö Variabel |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP-server<br />(för frågor om undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(för prenumerationer på undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(för hantering av distributioner) | / | --admin-port | - |
-| 8030 | Status för indexering av undergrafer API | /graphql | --index-node-port | - |
-| 8040 | Prometheus mätvärden | /metrics | --metrics-port | - |
+| Port | Syfte                                                      | Rutter                                               | Argument för CLI  | Miljö Variabel |
+| ---- | ---------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------- |
+| 8000 | GraphQL HTTP-server<br />(för frågor om undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -              |
+| 8001 | GraphQL WS<br />(för prenumerationer på undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -              |
+| 8020 | JSON-RPC<br />(för hantering av distributioner)      | /                                                    | --admin-port      | -              |
+| 8030 | Status för indexering av undergrafer API                   | /graphql                                             | --index-node-port | -              |
+| 8040 | Prometheus mätvärden                                       | /metrics                                             | --metrics-port    | -              |
 
 > **Viktigt**: Var försiktig med att exponera portar offentligt - **administrationsportar** bör hållas säkra. Detta inkluderar JSON-RPC-slutpunkten för Graph Node.
 

From e5abf0440e7303cfcd205b50eaf9133e89f2a4aa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:44 -0500
Subject: [PATCH 0984/1325] New translations operating-graph-node.mdx (Turkish)

---
 website/pages/tr/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/tr/operating-graph-node.mdx b/website/pages/tr/operating-graph-node.mdx
index 7a9039808b81..7112df5b91c5 100644
--- a/website/pages/tr/operating-graph-node.mdx
+++ b/website/pages/tr/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Tam Kubernetes örnek yapılandırması [indeksleyici Github deposunda](https://
 
 Graph Düğümü çalışırken aşağıdaki portları açar:
 
-| Port | Amaç | Rotalar | CLI Argümanı | Ortam Değişkeni |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />( subgraph abonelikleri için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(dağıtımları yönetmek için) | / | --admin-port | - |
-| 8030 | Subgraph indeksleme durum API'si | /graphql | --index-node-port | - |
-| 8040 | Prometheus metrikleri | /metrics | --metrics-port | - |
+| Port | Amaç                                                        | Rotalar                                              | CLI Argümanı      | Ortam Değişkeni |
+| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
+| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
+| 8001 | GraphQL WS<br />( subgraph abonelikleri için)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
+| 8020 | JSON-RPC<br />(dağıtımları yönetmek için)             | /                                                    | --admin-port      | -               |
+| 8030 | Subgraph indeksleme durum API'si                            | /graphql                                             | --index-node-port | -               |
+| 8040 | Prometheus metrikleri                                       | /metrics                                             | --metrics-port    | -               |
 
 > **Önemli**: Bağlantı noktalarını herkese açık olarak açarken dikkatli olun - **yönetim portları** kilitli tutulmalıdır. Bu, Graph Düğümü JSON-RPC uç noktasını içerir.
 

From c92ecea70e62f52567dd5aca6fb0123d85bf4901 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:45 -0500
Subject: [PATCH 0985/1325] New translations operating-graph-node.mdx
 (Ukrainian)

---
 website/pages/uk/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/uk/operating-graph-node.mdx b/website/pages/uk/operating-graph-node.mdx
index 30a9ee532653..cd8118b275b7 100644
--- a/website/pages/uk/operating-graph-node.mdx
+++ b/website/pages/uk/operating-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:
 
-| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
-| --- | --- | --- | --- | --- |
-| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт | - |
-| 8001 | GraphQL WS<br />(для підписок на підграфи) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(для керування розгортаннями) | / | --admin-port | - |
-| 8030 | API стану індексації підграфів | /graphql | --index-node-port | - |
-| 8040 | Метрики Prometheus | /metrics | --metrics-port | - |
+| Порт | Призначення                                               | Розташування                                         | Аргумент CLI      | Перемінна оточення |
+| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
+| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт       | -                  |
+| 8001 | GraphQL WS<br />(для підписок на підграфи)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
+| 8020 | JSON-RPC<br />(для керування розгортаннями)         | /                                                    | --admin-port      | -                  |
+| 8030 | API стану індексації підграфів                            | /graphql                                             | --index-node-port | -                  |
+| 8040 | Метрики Prometheus                                        | /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.
 

From 9a258fa4adbb4c5026eda0842fea26e6346a4b9c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:46 -0500
Subject: [PATCH 0986/1325] New translations operating-graph-node.mdx (Chinese
 Simplified)

---
 website/pages/zh/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/zh/operating-graph-node.mdx b/website/pages/zh/operating-graph-node.mdx
index 0847fd1c03c6..ecda26fa9061 100644
--- a/website/pages/zh/operating-graph-node.mdx
+++ b/website/pages/zh/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 当运行Graph Node时，会暴露以下端口：
 
-| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS <br />（用于子图订阅） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC <br />（用于管理部署） | / | --admin-port | - |
-| 8030 | 子图索引状态 API | /graphql | --index-node-port | - |
-| 8040 | Prometheus 指标 | /metrics | --metrics-port | - |
+| 端口   | 用途                                   | 路径                                                                  | CLI 参数            | 环境 变量 |
+| ---- | ------------------------------------ | ------------------------------------------------------------------- | ----------------- | ----- |
+| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port       | -     |
+| 8001 | GraphQL WS <br />（用于子图订阅）      | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --ws-port         | -     |
+| 8020 | JSON-RPC <br />（用于管理部署）        | /                                                                   | --admin-port      | -     |
+| 8030 | 子图索引状态 API                           | /graphql                                                            | --index-node-port | -     |
+| 8040 | Prometheus 指标                        | /metrics                                                            | --metrics-port    | -     |
 
 > **重要**: 公开暴露端口时要小心 - **管理端口** 应保持锁定。 这包括下面详述的 Graph 节点 JSON-RPC 和索引人管理端点。
 

From c1c2ed2be0bc9c3b8d6d18ab8b6ff83333ae1aab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:47 -0500
Subject: [PATCH 0987/1325] New translations operating-graph-node.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ur/operating-graph-node.mdx b/website/pages/ur/operating-graph-node.mdx
index 53ed532c07f8..1591a45dd2d0 100644
--- a/website/pages/ur/operating-graph-node.mdx
+++ b/website/pages/ur/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 جب یہ چل رہا ہوتا ہے گراف نوڈ مندرجہ ذیل پورٹس کو بے نقاب کرتا ہے:
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے) | / | --admin-port | - |
-| 8030 | سب گراف انڈیکسنگ اسٹیٹس API | /graphql | --index-node-port | - |
-| 8040 | Prometheus میٹرکس | /metrics | --metrics-port | - |
+| Port | Purpose                                                   | Routes                                               | CLI Argument      | Environment Variable |
+| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے)          | /                                                    | --admin-port      | -                    |
+| 8030 | سب گراف انڈیکسنگ اسٹیٹس API                               | /graphql                                             | --index-node-port | -                    |
+| 8040 | Prometheus میٹرکس                                         | /metrics                                             | --metrics-port    | -                    |
 
 > **اہم**: پورٹس کو عوامی طور پر ظاہر کرنے میں محتاط رہیں - **انتظامی پورٹس** کو بند رکھا جانا چاہیے. اس میں گراف نوڈ کا JSON-RPC اینڈ پوائنٹ شامل ہے.
 

From 662983fd7f88f986ed88fc63ff9b3d52ec4d5bda Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:48 -0500
Subject: [PATCH 0988/1325] New translations operating-graph-node.mdx
 (Vietnamese)

---
 website/pages/vi/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/vi/operating-graph-node.mdx b/website/pages/vi/operating-graph-node.mdx
index 82cebd402554..9185043e72a4 100644
--- a/website/pages/vi/operating-graph-node.mdx
+++ b/website/pages/vi/operating-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:
 
-| Cổng | Mục đích | Tuyến | Đối số CLI | Biến môi trường |
-| --- | --- | --- | --- | --- |
-| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(cho các đăng ký subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(để quản lý triển khai) | / | --admin-port | - |
-| 8030 | API trạng thái lập chỉ mục Subgraph | /graphql | --index-node-port | - |
-| 8040 | Số liệu Prometheus | /metrics | --metrics-port | - |
+| Cổng | Mục đích                                                    | Tuyến                                                | Đối số CLI        | Biến môi trường |
+| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
+| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
+| 8001 | GraphQL WS<br />(cho các đăng ký subgraph)            | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
+| 8020 | JSON-RPC<br />(để quản lý triển khai)                 | /                                                    | --admin-port      | -               |
+| 8030 | API trạng thái lập chỉ mục Subgraph                         | /graphql                                             | --index-node-port | -               |
+| 8040 | Số liệu Prometheus                                          | /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.
 

From 069f80414368c23f4670517cf46f05420930e9cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:50 -0500
Subject: [PATCH 0989/1325] New translations operating-graph-node.mdx (Marathi)

---
 website/pages/mr/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/mr/operating-graph-node.mdx b/website/pages/mr/operating-graph-node.mdx
index 907114f75be5..84d5fb6d4d9b 100644
--- a/website/pages/mr/operating-graph-node.mdx
+++ b/website/pages/mr/operating-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:
 
-| बंदर | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(for managing deployments) | / | --admin-port | - |
-| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
-| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
+| बंदर | Purpose                                               | Routes                                               | CLI Argument      | Environment Variable |
+| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(for managing deployments)        | /                                                    | --admin-port      | -                    |
+| 8030 | Subgraph indexing status API                          | /graphql                                             | --index-node-port | -                    |
+| 8040 | Prometheus metrics                                    | /metrics                                             | --metrics-port    | -                    |
 
 > **महत्त्वाचे**: पोर्ट सार्वजनिकपणे उघड करण्याबाबत सावधगिरी बाळगा - **प्रशासन पोर्ट** लॉक डाउन ठेवले पाहिजेत. यामध्ये ग्राफ नोड JSON-RPC एंडपॉइंटचा समावेश आहे.
 

From 4018aef1c47603c311b779aa6d1e275a5f58d469 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:51 -0500
Subject: [PATCH 0990/1325] New translations operating-graph-node.mdx (Hindi)

---
 website/pages/hi/operating-graph-node.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/hi/operating-graph-node.mdx b/website/pages/hi/operating-graph-node.mdx
index d8707dae894c..706cfcb7f112 100644
--- a/website/pages/hi/operating-graph-node.mdx
+++ b/website/pages/hi/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 जब यह चल रहा होता है तो ग्राफ़ नोड निम्नलिखित पोर्ट को उजागर करता है:
 
-| Port | Purpose | Routes | CLI Argument | Environment Variable |
-| --- | --- | --- | --- | --- |
-| 8000 | GraphQL HTTP server<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
-| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
-| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए) | / | --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<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए)           | /                                                    | --admin-port      | -                    |
+| 8030 | Subgraph indexing status API                             | /graphql                                             | --index-node-port | -                    |
+| 8040 | Prometheus metrics                                       | /metrics                                             | --metrics-port    | -                    |
 
 > **महत्वपूर्ण**: बंदरगाहों को सार्वजनिक रूप से उजागर करने के बारे में सावधान रहें - **प्रशासन बंदरगाहों** को बंद रखा जाना चाहिए। इसमें ग्राफ़ नोड JSON-RPC समापन बिंदु शामिल है।
 

From 1e72254769a1e234c6a0b48aa39659d5c35b0bc9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:52 -0500
Subject: [PATCH 0991/1325] New translations operating-graph-node.mdx (Swahili)

---
 website/pages/sw/operating-graph-node.mdx | 345 ++++++++++++++++++++++
 1 file changed, 345 insertions(+)
 create mode 100644 website/pages/sw/operating-graph-node.mdx

diff --git a/website/pages/sw/operating-graph-node.mdx b/website/pages/sw/operating-graph-node.mdx
new file mode 100644
index 000000000000..fb3d538f952a
--- /dev/null
+++ b/website/pages/sw/operating-graph-node.mdx
@@ -0,0 +1,345 @@
+---
+title: Operating Graph Node
+---
+
+Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+
+This provides a contextual overview of Graph Node, and some of the more advanced options available to indexers. Detailed documentation and instructions can be found in the [Graph Node repository](https://github.com/graphprotocol/graph-node).
+
+## Graph Node
+
+[Graph Node](https://github.com/graphprotocol/graph-node) is the reference implementation for indexing Subgraphs on The Graph Network, connecting to blockchain clients, indexing subgraphs and making indexed data available to query.
+
+Graph Node (and the whole indexer stack) can be run on bare metal, or in a cloud environment. This flexibility of the central indexing component is crucial to the robustness of The Graph Protocol. Similarly, Graph Node can be [built from source](https://github.com/graphprotocol/graph-node), or indexers can use one of the [provided Docker Images](https://hub.docker.com/r/graphprotocol/graph-node).
+
+### PostgreSQL database
+
+The main store for the Graph Node, this is where subgraph data is stored, as well as metadata about subgraphs, and subgraph-agnostic network data such as the block cache, and eth_call cache.
+
+### Network clients
+
+In order to index a network, Graph Node needs access to a network client via an EVM-compatible JSON-RPC API. This RPC may connect to a single client or it could be a more complex setup that load balances across multiple.
+
+While some subgraphs may just require a full node, some may have indexing features which require additional RPC functionality. Specifically subgraphs which make `eth_calls` as part of indexing will require an archive node which supports [EIP-1898](https://eips.ethereum.org/EIPS/eip-1898), and subgraphs with `callHandlers`, or `blockHandlers` with a `call` filter, require `trace_filter` support ([see trace module documentation here](https://openethereum.github.io/JSONRPC-trace-module)).
+
+**Network Firehoses** - a Firehose is a gRPC service providing an ordered, yet fork-aware, stream of blocks, developed by The Graph's core developers to better support performant indexing at scale. This is not currently an Indexer requirement, but Indexers are encouraged to familiarise themselves with the technology, ahead of full network support. Learn more about the Firehose [here](https://firehose.streamingfast.io/).
+
+### IPFS Nodes
+
+Subgraph deployment metadata is stored on the IPFS network. The Graph Node primarily accesses the IPFS node during subgraph deployment to fetch the subgraph manifest and all linked files. Network indexers do not need to host their own IPFS node. An IPFS node for the network is hosted at https://ipfs.network.thegraph.com.
+
+### Prometheus metrics server
+
+To enable monitoring and reporting, Graph Node can optionally log metrics to a Prometheus metrics server.
+
+### Getting started from source
+
+#### Install prerequisites
+
+- **Rust**
+
+- **PostgreSQL**
+
+- **IPFS**
+
+- **Additional Requirements for Ubuntu users** - To run a Graph Node on Ubuntu a few additional packages may be needed.
+
+```sh
+sudo apt-get install -y clang libpq-dev libssl-dev pkg-config
+```
+
+#### Setup
+
+1. Start a PostgreSQL database server
+
+```sh
+initdb -D .postgres
+pg_ctl -D .postgres -l logfile start
+createdb graph-node
+```
+
+2. Clone [Graph Node](https://github.com/graphprotocol/graph-node) repo and build the source by running `cargo build`
+
+3. Now that all the dependencies are setup, start the Graph Node:
+
+```sh
+cargo run -p graph-node --release -- \
+  --postgres-url postgresql://[USERNAME]:[PASSWORD]@localhost:5432/graph-node \
+  --ethereum-rpc [NETWORK_NAME]:[URL] \
+  --ipfs https://ipfs.network.thegraph.com
+```
+
+### Getting started with Kubernetes
+
+A complete Kubernetes example configuration can be found in the [indexer repository](https://github.com/graphprotocol/indexer/tree/main/k8s).
+
+### Ports
+
+When it is running Graph Node exposes the following ports:
+
+| Port | Purpose                                               | Routes                                               | CLI Argument      | Environment Variable |
+| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
+| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
+| 8020 | JSON-RPC<br />(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.
+
+## Advanced Graph Node configuration
+
+At its simplest, Graph Node can be operated with a single instance of Graph Node, a single PostgreSQL database, an IPFS node, and the network clients as required by the subgraphs to be indexed.
+
+This setup can be scaled horizontally, by adding multiple Graph Nodes, and multiple databases to support those Graph Nodes. Advanced users may want to take advantage of some of the horizontal scaling capabilities of Graph Node, as well as some of the more advanced configuration options, via the `config.toml` file and Graph Node's environment variables.
+
+### `config.toml`
+
+A [TOML](https://toml.io/en/) configuration file can be used to set more complex configurations than those exposed in the CLI. The location of the file is passed with the --config command line switch.
+
+> When using a configuration file, it is not possible to use the options --postgres-url, --postgres-secondary-hosts, and --postgres-host-weights.
+
+A minimal `config.toml` file can be provided; the following file is equivalent to using the --postgres-url command line option:
+
+```toml
+[store]
+[store.primary]
+connection="<.. postgres-url argument ..>"
+[deployment]
+[[deployment.rule]]
+indexers = [ "<.. list of all indexing nodes ..>" ]
+```
+
+Full documentation of `config.toml` can be found in the [Graph Node docs](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md).
+
+#### Multiple Graph Nodes
+
+Graph Node indexing can scale horizontally, running multiple instances of Graph Node to split indexing and querying across different nodes. This can be done simply by running Graph Nodes configured with a different `node_id` on startup (e.g. in the Docker Compose file), which can then be used in the `config.toml` file to specify [dedicated query nodes](#dedicated-query-nodes), [block ingestors](#dedicated-block-ingestion), and splitting subgraphs across nodes with [deployment rules](#deployment-rules).
+
+> Note that multiple Graph Nodes can all be configured to use the same database, which itself can be horizontally scaled via sharding.
+
+#### Deployment rules
+
+Given multiple Graph Nodes, it is necessary to manage deployment of new subgraphs so that the same subgraph isn't being indexed by two different nodes, which would lead to collisions. This can be done by using deployment rules, which can also specify which `shard` a subgraph's data should be stored in, if database sharding is being used. Deployment rules can match on the subgraph name and the network that the deployment is indexing in order to make a decision.
+
+Example deployment rule configuration:
+
+```toml
+[deployment]
+[[deployment.rule]]
+match = { name = "(vip|important)/.*" }
+shard = "vip"
+indexers = [ "index_node_vip_0", "index_node_vip_1" ]
+[[deployment.rule]]
+match = { network = "kovan" }
+# No shard, so we use the default shard called 'primary'
+indexers = [ "index_node_kovan_0" ]
+[[deployment.rule]]
+match = { network = [ "xdai", "poa-core" ] }
+indexers = [ "index_node_other_0" ]
+[[deployment.rule]]
+# There's no 'match', so any subgraph matches
+shards = [ "sharda", "shardb" ]
+indexers = [
+    "index_node_community_0",
+    "index_node_community_1",
+    "index_node_community_2",
+    "index_node_community_3",
+    "index_node_community_4",
+    "index_node_community_5"
+  ]
+```
+
+Read more about deployment rules [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#controlling-deployment).
+
+#### Dedicated query nodes
+
+Nodes can be configured to explicitly be query nodes by including the following in the configuration file:
+
+```toml
+[general]
+query = "<regular expression>"
+```
+
+Any node whose --node-id matches the regular expression will be set up to only respond to queries.
+
+#### Database scaling via sharding
+
+For most use cases, a single Postgres database is sufficient to support a graph-node instance. When a graph-node instance outgrows a single Postgres database, it is possible to split the storage of graph-node's data across multiple Postgres databases. All databases together form the store of the graph-node instance. Each individual database is called a shard.
+
+Shards can be used to split subgraph deployments across multiple databases, and can also be used to use replicas to spread query load across databases. This includes configuring the number of available database connections each `graph-node` should keep in its connection pool for each database, which becomes increasingly important as more subgraphs are being indexed.
+
+Sharding becomes useful when your existing database can't keep up with the load that Graph Node puts on it, and when it's not possible to increase the database size anymore.
+
+> It is generally better make a single database as big as possible, before starting with shards. One exception is where query traffic is split very unevenly between subgraphs; in those situations it can help dramatically if the high-volume subgraphs are kept in one shard and everything else in another because that setup makes it more likely that the data for the high-volume subgraphs stays in the db-internal cache and doesn't get replaced by data that's not needed as much from low-volume subgraphs.
+
+In terms of configuring connections, start with max_connections in postgresql.conf set to 400 (or maybe even 200) and look at the store_connection_wait_time_ms and store_connection_checkout_count Prometheus metrics. Noticeable wait times (anything above 5ms) is an indication that there are too few connections available; high wait times there will also be caused by the database being very busy (like high CPU load). However if the database seems otherwise stable, high wait times indicate a need to increase the number of connections. In the configuration, how many connections each graph-node instance can use is an upper limit, and Graph Node will not keep connections open if it doesn't need them.
+
+Read more about store configuration [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-multiple-databases).
+
+#### Dedicated block ingestion
+
+If there are multiple nodes configured, it will be necessary to specify one node which is responsible for ingestion of new blocks, so that all configured index nodes aren't polling the chain head. This is done as part of the `chains` namespace, specifying the `node_id` to be used for block ingestion:
+
+```toml
+[chains]
+ingestor = "block_ingestor_node"
+```
+
+#### Supporting multiple networks
+
+The Graph Protocol is increasing the number of networks supported for indexing rewards, and there exist many subgraphs indexing unsupported networks which an indexer would like to process. The `config.toml` file allows for expressive and flexible configuration of:
+
+- Multiple networks
+- Multiple providers per network (this can allow splitting of load across providers, and can also allow for configuration of full nodes as well as archive nodes, with Graph Node preferring cheaper providers if a given workload allows).
+- Additional provider details, such as features, authentication and the type of provider (for experimental Firehose support)
+
+The `[chains]` section controls the ethereum providers that graph-node connects to, and where blocks and other metadata for each chain are stored. The following example configures two chains, mainnet and kovan, where blocks for mainnet are stored in the vip shard and blocks for kovan are stored in the primary shard. The mainnet chain can use two different providers, whereas kovan only has one provider.
+
+```toml
+[chains]
+ingestor = "block_ingestor_node"
+[chains.mainnet]
+shard = "vip"
+provider = [
+  { label = "mainnet1", url = "http://..", features = [], headers = { Authorization = "Bearer foo" } },
+  { label = "mainnet2", url = "http://..", features = [ "archive", "traces" ] }
+]
+[chains.kovan]
+shard = "primary"
+provider = [ { label = "kovan", url = "http://..", features = [] } ]
+```
+
+Read more about provider configuration [here](https://github.com/graphprotocol/graph-node/blob/master/docs/config.md#configuring-ethereum-providers).
+
+### Environment variables
+
+Graph Node supports a range of environment variables which can enable features, or change Graph Node behaviour. These are documented [here](https://github.com/graphprotocol/graph-node/blob/master/docs/environment-variables.md).
+
+### Continuous deployment
+
+Users who are operating a scaled indexing setup with advanced configuration may benefit from managing their Graph Nodes with Kubernetes.
+
+- The indexer repository has an [example Kubernetes reference](https://github.com/graphprotocol/indexer/tree/main/k8s)
+- [Launchpad](https://docs.graphops.xyz/launchpad/intro) is a toolkit for running a Graph Protocol Indexer on Kubernetes maintained by GraphOps. It provides a set of Helm charts and a CLI to manage a Graph Node deployment.
+
+### Managing Graph Node
+
+Given a running Graph Node (or Graph Nodes!), the challenge is then to manage deployed subgraphs across those nodes. Graph Node surfaces a range of tools to help with managing subgraphs.
+
+#### Logging
+
+Graph Node's logs can provide useful information for debugging and optimisation of Graph Node and specific subgraphs. Graph Node supports different log levels via the `GRAPH_LOG` environment variable, with the following levels: error, warn, info, debug or trace.
+
+In addition setting `GRAPH_LOG_QUERY_TIMING` to `gql` provides more details about how GraphQL queries are running (though this will generate a large volume of logs).
+
+#### Monitoring & alerting
+
+Graph Node provides the metrics via Prometheus endpoint on 8040 port by default. Grafana can then be used to visualise these metrics.
+
+The indexer repository provides an [example Grafana configuration](https://github.com/graphprotocol/indexer/blob/main/k8s/base/grafana.yaml).
+
+#### Graphman
+
+`graphman` is a maintenance tool for Graph Node, helping with diagnosis and resolution of different day-to-day and exceptional tasks.
+
+The graphman command is included in the official containers, and you can docker exec into your graph-node container to run it. It requires a `config.toml` file.
+
+Full documentation of `graphman` commands is available in the Graph Node repository. See \[/docs/graphman.md\] (https://github.com/graphprotocol/graph-node/blob/master/docs/graphman.md) in the Graph Node `/docs`
+
+### Working with subgraphs
+
+#### Indexing status API
+
+Available on port 8030/graphql by default, the indexing status API exposes a range of methods for checking indexing status for different subgraphs, checking proofs of indexing, inspecting subgraph features and more.
+
+The full schema is available [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql).
+
+#### Indexing performance
+
+There are three separate parts of the indexing process:
+
+- Fetching events of interest from the provider
+- Processing events in order with the appropriate handlers (this can involve calling the chain for state, and fetching data from the store)
+- Writing the resulting data to the store
+
+These stages are pipelined (i.e. they can be executed in parallel), but they are dependent on one another. Where subgraphs are slow to index, the underlying cause will depend on the specific subgraph.
+
+Common causes of indexing slowness:
+
+- Time taken to find relevant events from the chain (call handlers in particular can be slow, given the reliance on `trace_filter`)
+- Making large numbers of `eth_calls` as part of handlers
+- A large amount of store interaction during execution
+- A large amount of data to save to the store
+- A large number of events to process
+- Slow database connection time, for crowded nodes
+- The provider itself falling behind the chain head
+- Slowness in fetching new receipts at the chain head from the provider
+
+Subgraph indexing metrics can help diagnose the root cause of indexing slowness. In some cases, the problem lies with the subgraph itself, but in others, improved network providers, reduced database contention and other configuration improvements can markedly improve indexing performance.
+
+#### Failed subgraphs
+
+During indexing subgraphs might fail, if they encounter data that is unexpected, some component not working as expected, or if there is some bug in the event handlers or configuration. There are two general types of failure:
+
+- Deterministic failures: these are failures which will not be resolved with retries
+- Non-deterministic failures: these might be down to issues with the provider, or some unexpected Graph Node error. When a non-deterministic failure occurs, Graph Node will retry the failing handlers, backing off over time.
+
+In some cases a failure might be resolvable by the indexer (for example if the error is a result of not having the right kind of provider, adding the required provider will allow indexing to continue). However in others, a change in the subgraph code is required.
+
+> Deterministic failures are considered "final", with a Proof of Indexing generated for the failing block, while non-determinstic failures are not, as the subgraph may manage to "unfail" and continue indexing. In some cases, the non-deterministic label is incorrect, and the subgraph will never overcome the error; such failures should be reported as issues on the Graph Node repository.
+
+#### Block and call cache
+
+Graph Node caches certain data in the store in order to save refetching from the provider. Blocks are cached, as are the results of `eth_calls` (the latter being cached as of a specific block). This caching can dramatically increase indexing speed during "resyncing" of a slightly altered subgraph.
+
+However, in some instances, if an Ethereum node has provided incorrect data for some period, that can make its way into the cache, leading to incorrect data or failed subgraphs. In this case indexers can use `graphman` to clear the poisoned cache, and then rewind the affected subgraphs, which will then fetch fresh data from the (hopefully) healthy provider.
+
+If a block cache inconsistency is suspected, such as a tx receipt missing event:
+
+1. `graphman chain list` to find the chain name.
+2. `graphman chain check-blocks <CHAIN> by-number <NUMBER>` will check if the cached block matches the provider, and deletes the block from the cache if it doesn’t.
+   1. If there is a difference, it may be safer to truncate the whole cache with `graphman chain truncate <CHAIN>`.
+   2. If the block matches the provider, then the issue can be debugged directly against the provider.
+
+#### Querying issues and errors
+
+Once a subgraph has been indexed, indexers can expect to serve queries via the subgraph's dedicated query endpoint. If the indexer is hoping to serve significant query volume, a dedicated query node is recommended, and in case of very high query volumes, indexers may want to configure replica shards so that queries don't impact the indexing process.
+
+However, even with a dedicated query node and replicas, certain queries can take a long time to execute, and in some cases increase memory usage and negatively impact the query time for other users.
+
+There is not one "silver bullet", but a range of tools for preventing, diagnosing and dealing with slow queries.
+
+##### Query caching
+
+Graph Node caches GraphQL queries by default, which can significantly reduce database load. This can be further configured with the `GRAPH_QUERY_CACHE_BLOCKS` and `GRAPH_QUERY_CACHE_MAX_MEM` settings - read more [here](https://github.com/graphprotocol/graph-node/blob/master/docs/environment-variables.md#graphql-caching).
+
+##### Analysing queries
+
+Problematic queries most often surface in one of two ways. In some cases, users themselves report that a given query is slow. In that case the challenge is to diagnose the reason for the slowness - whether it is a general issue, or specific to that subgraph or query. And then of course to resolve it, if possible.
+
+In other cases, the trigger might be high memory usage on a query node, in which case the challenge is first to identify the query causing the issue.
+
+Indexers can use [qlog](https://github.com/graphprotocol/qlog/) to process and summarize Graph Node's query logs. `GRAPH_LOG_QUERY_TIMING` can also be enabled to help identify and debug slow queries.
+
+Given a slow query, indexers have a few options. Of course they can alter their cost model, to significantly increase the cost of sending the problematic query. This may result in a reduction in the frequency of that query. However this often doesn't resolve the root cause of the issue.
+
+##### Account-like optimisation
+
+Database tables that store entities seem to generally come in two varieties: 'transaction-like', where entities, once created, are never updated, i.e., they store something akin to a list of financial transactions, and 'account-like' where entities are updated very often, i.e., they store something like financial accounts that get modified every time a transaction is recorded. Account-like tables are characterized by the fact that they contain a large number of entity versions, but relatively few distinct entities. Often, in such tables the number of distinct entities is 1% of the total number of rows (entity versions)
+
+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 <sgdNNNN`> 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 <sgdNNN> <table>` 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.
+
+Once a table has been determined to be account-like, running `graphman stats account-like <sgdNNN>.<table>` will turn on the account-like optimization for queries against that table. The optimization can be turned off again with `graphman stats account-like --clear <sgdNNN>.<table>` It takes up to 5 minutes for query nodes to notice that the optimization has been turned on or off. After turning the optimization on, it is necessary to verify that the change does not in fact make queries slower for that table. If you have configured Grafana to monitor Postgres, slow queries would show up in `pg_stat_activity`in large numbers, taking several seconds. In that case, the optimization needs to be turned off again.
+
+For Uniswap-like subgraphs, the `pair` and `token` tables are prime candidates for this optimization, and can have a dramatic effect on database load.
+
+#### 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 d84d54931d63927b5954c67036f50ac6ec0686ac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:54 -0500
Subject: [PATCH 0992/1325] New translations glossary.mdx (Romanian)

---
 website/pages/ro/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/ro/glossary.mdx b/website/pages/ro/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/ro/glossary.mdx
+++ b/website/pages/ro/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 0517e2a5a65c7cca641b139502029fe4aed5821f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:55 -0500
Subject: [PATCH 0993/1325] New translations glossary.mdx (French)

---
 website/pages/fr/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/fr/glossary.mdx b/website/pages/fr/glossary.mdx
index e709ff578441..ebe5e6e88668 100644
--- a/website/pages/fr/glossary.mdx
+++ b/website/pages/fr/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossaire
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexeurs** : participants au réseau qui exécutent des nœuds d'indexation pour indexer les données des blockchains et servir des requêtes GraphQL.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Flux de revenus des indexeurs** : Les indexeurs sont récompensés en GRT avec deux composantes : les remises sur les frais de requête et les récompenses d'indexation.
 
@@ -22,19 +20,19 @@ title: Glossaire
 
   2. **Récompenses d'indexation** : les récompenses que les indexeurs reçoivent pour l'indexation des subgraphs. Les récompenses d'indexation sont générées par l'émission annuelle de 3 % de GRT.
 
-- **Participation personnelle de l'indexeur** : le montant de GRT que les indexeurs mettent en jeu pour participer au réseau décentralisé. Le minimum est de 100 000 GRT et il n’y a pas de limite supérieure.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Mise à niveau de l'indexeur** : un indexeur temporaire conçu pour servir de solution de secours pour les requêtes de subgraphs non prises en charge par d'autres indexeurs du réseau. Il garantit une transition transparente pour la mise à niveau des subgraphs à partir du service hébergé en répondant facilement à leurs requêtes dès leur publication. L'indexeur de mise à niveau n'est pas compétitif par rapport aux autres indexeurs et prend en charge les chaînes qui étaient auparavant exclusives au service hébergé.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Taxe de délégation** : Une taxe de 0,5 % payée par les délégués lorsqu'ils délèguent des GRT aux indexeurs. Les GRT utilisés pour payer la taxe sont brûlés.
 
-- **Curateurs** : participants au réseau qui identifient des subgraphs de haute qualité et les « organisent » (c'est-à-dire signalent GRT sur eux) en échange de partages de curation. Lorsque les indexeurs réclament des frais de requête sur un subgraph, 10 % sont distribués aux conservateurs de ce subgraph. Les indexeurs gagnent des récompenses d'indexation proportionnelles au signal sur un subgraph. Nous voyons une corrélation entre la quantité de GRT signalée et le nombre d'indexeurs indexant un subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Taxe de curation** : Une taxe de 1% payée par les curateurs lorsqu'ils signalent des GRT sur des subgraphs. Le GRT utilisé pour payer la taxe est brûlé.
 
-- **Consommateur de subgraphs** : Toute application ou utilisateur qui interroge un subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Développeur de subgraphs** : un développeur qui crée et déploie un subgraph sur le réseau décentralisé de The Graph.
 
@@ -46,15 +44,15 @@ title: Glossaire
 
   1. **Actif** : Une allocation est considérée comme active lorsqu'elle est créée sur la chaîne. Cela s'appelle ouvrir une allocation, et indique au réseau que l'indexeur indexe et sert activement les requêtes pour un subgraph particulier. Les allocations actives accumulent des récompenses d'indexation proportionnelles au signal sur le subgraph et à la quantité de GRT allouée.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio** : une application puissante pour créer, déployer et publier des subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Récompenses d'indexation** : les récompenses que les indexeurs reçoivent pour l'indexation des subgraphs. Les récompenses d'indexation sont distribuées en GRT.
 
@@ -62,11 +60,11 @@ title: Glossaire
 
 - .**GRT** : le jeton d'utilité du travail de The Graph, le GRT offre des incitations économiques aux participants du réseau pour leur contribution au réseau.
 
-- **POI ou preuve d'indexation** : lorsqu'un indexeur clôture son allocation et souhaite réclamer ses récompenses d'indexation accumulées sur un subgraph donné, il doit fournir une preuve d'indexation valide et récente ( POI). Les pêcheurs peuvent contester le POI fourni par un indexeur. Un différend résolu en faveur du pêcheur entraînera la suppression de l'indexeur.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node** : Graph Node est le composant qui indexe les subgraphs et rend les données résultantes disponibles pour interrogation via une API GraphQL. En tant que tel, il est au cœur de la pile de l’indexeur, et le bon fonctionnement de Graph Node est crucial pour exécuter un indexeur réussi.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Agent de l'indexeur** : l'agent de l'indexeur fait partie de la pile de l'indexeur. Il facilite les interactions de l'indexeur sur la chaîne, notamment l'enregistrement sur le réseau, la gestion des déploiements de subgraphs vers son ou son(ses) noed(s) de graph et la gestion des allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client** : une bibliothèque pour créer des dapps basées sur GraphQL de manière décentralisée.
 
@@ -76,12 +74,8 @@ title: Glossaire
 
 - **Période de récupération** : le temps restant jusqu'à ce qu'un indexeur qui a modifié ses paramètres de délégation puisse le faire à nouveau.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Mise à niveau_ d'un subgraph vers The Graph Network** : processus de déplacement d'un subgraph du service hébergé vers The Graph Network .
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Mise à jour_ d'un subgraph** : processus de publication d'une nouvelle version de subgraph avec des mises à jour du manifeste, du schéma ou du subgraph. cartographies.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 40c1b02059055bbbb995786b8c4534b420645e83 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:56 -0500
Subject: [PATCH 0994/1325] New translations glossary.mdx (Spanish)

---
 website/pages/es/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/es/glossary.mdx b/website/pages/es/glossary.mdx
index adabc2b4b467..b2b41524b887 100644
--- a/website/pages/es/glossary.mdx
+++ b/website/pages/es/glossary.mdx
@@ -10,11 +10,9 @@ title: Glosario
 
 - **Endpoint**: Una URL que se puede utilizar para consultar un subgrafo. El endpoint de prueba para Subgraph Studio es `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` y el endpoint de Graph Explorer es `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. El endpoint de Graph Explorer se utiliza para consultar subgrafos en la red descentralizada de The Graph.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexadores (Indexers)**: Participantes de la red que ejecutan nodos de indexación para indexar datos de la blockchain y servir consultas GraphQL.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Flujos de ingresos de los indexadores (Indexer Revenue Streams)**: Los Indexadores son recompensados en GRT con dos componentes: reembolsos de tarifas de consulta y recompensas de indexación.
 
@@ -22,19 +20,19 @@ title: Glosario
 
   2. **Recompensas de Indexación (Indexing Rewards)**: Las recompensas que reciben los Indexadores por indexar subgrafos. Las recompensas de indexación se generan mediante una nueva emisión anual del 3% de GRT.
 
-- **Stake propio del Indexador (Indexer's Self Stake)**: La cantidad de GRT que los Indexadores depositan en stake para participar en la red descentralizada. El mínimo es de 100.000 GRT, y no hay límite superior.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegadores (Delegators)**: Participantes de la red que poseen GRT y delegan su GRT en Indexadores. Esto permite a los Indexadores aumentar su stake en los subgrafos de la red. A cambio, los Delegadores reciben una parte de las recompensas de indexación que reciben los Indexadores por procesar los subgrafos.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Impuesto a la Delegación (Delegation Tax)**: Una tasa del 0,5% que pagan los Delegadores cuando delegan GRT en los Indexadores. El GRT utilizado para pagar la tasa se quema.
 
-- **Curadores (Curators)**: Participantes de la red que identifican subgrafos de alta calidad y los "curan" (es decir, señalan GRT sobre ellos) a cambio de cuotas de curación. Cuando los Indexadores reclaman tarifas de consulta sobre un subgrafo, el 10% se distribuye entre los Curadores de ese subgrafo. Los Indexadores obtienen recompensas de indexación proporcionales a la señal en un subgrafo. Vemos una correlación entre la cantidad de GRT señalada y el número de Indexadores que indexan un subgrafo.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Impuesto a la Curación (Curation Tax)**: Una tasa del 1% pagada por los Curadores cuando señalan GRT en los subgrafos. El GRT utilizado para pagar la tasa se quema.
 
-- **Consumidor de Subgrafos (Subgraph Consumer)**: Cualquier aplicación o usuario que consulte un subgrafo.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Developer de subgrafos (Subgraph developer)**: Developer que construye y realiza el deploy de un subgrafo en la red descentralizada de The Graph.
 
@@ -46,15 +44,15 @@ title: Glosario
 
   1. **Activa (Active)**: Una allocation se considera activa cuando se crea on-chain. Esto se llama abrir una allocation, e indica a la red que el Indexador está indexando activamente y sirviendo consultas para un subgrafo en particular. Las allocations activas acumulan recompensas de indexación proporcionales a la señal del subgrafo y a la cantidad de GRT asignada.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: Una potente aplicación para crear, deployar y publicar subgrafos.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Recompensas de Indexación (Indexing Rewards)**: Las recompensas que reciben los Indexadores por indexar subgrafos. Las recompensas de indexación se distribuyen en GRT.
 
@@ -62,11 +60,11 @@ title: Glosario
 
 - **GRT**: El token de utilidad de trabajo de The Graph. GRT ofrece incentivos económicos a los participantes en la red por contribuir a ella.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node es el componente que indexa los subgrafos, y hace que los datos resultantes estén disponibles para su consulta a través de una API GraphQL. Como tal, es fundamental para el stack del Indexador, y el correcto funcionamiento de Graph Node es crucial para ejecutar un Indexador con éxito.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Agente indexador (Indexer Agent)**: El agente del Indexador forma parte del stack del Indexador. Facilita las interacciones on-chain del Indexador, incluido el registro en la red, la gestión de deploys de subgrafos en su(s) Graph Node y la gestión de allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **Cliente The Graph (The Graph Client)**: Una biblioteca para construir dapps basadas en GraphQL de forma descentralizada.
 
@@ -76,12 +74,8 @@ title: Glosario
 
 - **Período de enfriamiento (Cooldown Period)**: El tiempo restante hasta que un Indexador que cambió sus parámetros de delegación pueda volver a hacerlo.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 7e7d51c22dc9d546d99a123af6f1805940949ffc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:57 -0500
Subject: [PATCH 0995/1325] New translations glossary.mdx (Arabic)

---
 website/pages/ar/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/ar/glossary.mdx b/website/pages/ar/glossary.mdx
index a94cb5d4be55..6e4fbeab2e85 100644
--- a/website/pages/ar/glossary.mdx
+++ b/website/pages/ar/glossary.mdx
@@ -10,11 +10,9 @@ title: قائمة المصطلحات
 
 - **نقطة النهاية (Endpoint)**: عنوان URL يمكن استخدامه للاستعلام عن سبغراف. نقطة الاختبار لـ سبغراف استوديو هي: `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` ونقطة نهاية مستكشف الغراف هي: `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>` تُستخدم نقطة نهاية مستكشف الغراف للاستعلام عن سبغرافات على شبكة الغراف اللامركزية.
 
-- **غراف فرعي (Subgraph)**: واجهة برمجة تطبيقات مفتوحة تستخلص البيانات من سلسلة الكتل، ومعالجتها، وتخزينها ليكون من السهل الاستعلام عنها من خلال لغة استعلام GraphQL. يمكن للمطورين بناء ونشر الغرافات الفرعية على شبكة الغراف اللامركزية. بعد ذلك، يمكن للمفهرسين البدء في فهرسة الغرافات الفرعية لتكون متاحة للاستعلام من قبل أي كان.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **الخدمة المستضافة (Hosted Service)**: هي خدمة مؤقتة تعمل كبنية تحتية لبناء واستعلام الغرافات الفرعية، حيث تقوم شبكة الغراف اللامركزية بتحسين تكاليف الخدمة وجودة الخدمة وتجربة المطور.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: قائمة المصطلحات
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **مستهلك الغراف الفرعي**: أي تطبيق أو مستخدم يستعلم عن غراف فرعي معين.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **مطور السوبغراف**: هو المطور الذي يقوم ببناء ونشر السوبغراف على شبكة الغراف اللامركزية.
 
@@ -46,15 +44,15 @@ title: قائمة المصطلحات
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: قائمة المصطلحات
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: قائمة المصطلحات
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 08c51ffebd49a5bd7137b3228a45a311a8c6a2c0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:58 -0500
Subject: [PATCH 0996/1325] New translations glossary.mdx (Czech)

---
 website/pages/cs/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/cs/glossary.mdx b/website/pages/cs/glossary.mdx
index b1e74d28b440..5e3859945744 100644
--- a/website/pages/cs/glossary.mdx
+++ b/website/pages/cs/glossary.mdx
@@ -10,11 +10,9 @@ title: Glosář
 
 - **Koncový bod**: URL, které lze použít k dotazu na podgraf. Testovací koncový bod pro Podgraf Studio je `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` a koncový bod Graf Exploreru je `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. Koncový bod Graf Explorer se používá k dotazování podgrafů v decentralizované síti Graf.
 
-- **Podgraf**: Otevřené API, které získává data z blockchainu, zpracovává je a ukládá tak, aby bylo možné se na ně snadno dotazovat prostřednictvím GraphQL. Vývojáři mohou vytvářet, nasazovat a publikovat podgrafy v síti Graf Poté mohou indexátoři začít indexovat podgrafy, aby je kdokoli mohl vyhledávat.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hostovaná služba**: Dočasná lešenářská služba pro vytváření a dotazování podgrafů v době, kdy decentralizovaná síť Graf dozrává v oblasti nákladů na služby, kvality služeb a zkušeností vývojářů.
-
-- **Indexery**: Účastníci sítě, kteří provozují indexovací uzly pro indexování dat z blockchainů a obsluhu dotazů GraphQL.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Příjmy indexátorů**: Indexátoři jsou v GRT odměňováni dvěma složkami: slevami z poplatků za dotazy a odměnami za indexování.
 
@@ -22,19 +20,19 @@ title: Glosář
 
   2. **Odměny za indexování**: Odměny, které indexátory obdrží za indexování podgrafů. Odměny za indexování jsou generovány prostřednictvím nové emise 3% GRT ročně.
 
-- **Vlastní vklad indexátora**: Částka GRT, kterou indexátoři vkládají, aby se mohli účastnit decentralizované sítě. Minimum je 100,000 GRT a horní hranice není stanovena.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade indexeru**: Dočasný indexer určený jako záložní pro dotazy na podgrafy, které nejsou obsluhovány jinými indexery v síti. Zajišťuje bezproblémový přechod pro podgrafy, které se upgradují z hostované služby na Síť Graf. Upgrade Indexer není konkurenční vůči ostatním Indexerům. Podporuje řadu blokových řetězců, které byly dříve dostupné pouze v hostované službě.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegátoři**: Účastníci sítě, kteří vlastní GRT a delegují své GRT na indexátory. To umožňuje Indexerům zvýšit svůj podíl v podgrafech v síti. Delegáti na oplátku dostávají část odměn za indexování, které indexátoři dostávají za zpracování podgrafů.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegační daň**: 0.5% poplatek, který platí delegáti, když delegují GRT na indexátory. GRT použitý k úhradě poplatku se spálí.
 
-- **Kurátoři**: Účastníci sítě, kteří identifikují vysoce kvalitní podgrafy a "kurátorují" je (tj. signalizují na nich GRT) výměnou za kurátorské podíly. Když indexátoři požadují poplatky za dotaz na podgraf, 10% se rozdělí kurátorům tohoto podgrafu. Indexátoři získávají indexační odměny úměrné signálu na podgrafu. Vidíme korelaci mezi množstvím signalizovaných GRT a počtem indexátorů indexujících podgraf.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: Kurátoři platí 1% poplatek, když signalizují GRT na podgraf GRT použitý k zaplacení poplatku se spálí.
 
-- **Podgraf Spotřebitel**: Jakákoli aplikace nebo uživatel, který se dotazuje na podgraf.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Vývojář podgrafů**: Vývojář, který vytváří a nasazuje subgraf do decentralizované sítě Grafu.
 
@@ -46,15 +44,15 @@ title: Glosář
 
   1. **Aktivní**: Alokace je považována za aktivní, když je vytvořena v řetězci. Tomu se říká otevření alokace a signalizuje síti, že indexátor aktivně indexuje a obsluhuje dotazy pro daný podgraf. Aktivní alokace získávají odměny za indexování úměrné signálu na podgrafu a množství alokovaného GRT.
 
-  2. **Zavřeno**: Indexátor si může nárokovat odměny za indexaci daného podgrafu předložením aktuálního a platného dokladu o indexaci (POI). Tomuto postupu se říká uzavření přídělu. Alokace musí být otevřena minimálně jednu epochu, aby mohla být uzavřena. Maximální doba přidělení je 28 epoch. Pokud indexátor ponechá alokaci otevřenou déle než 28 epoch, je tato alokace označována jako zastaralá. Když je alokace ve stavu **uzavřeno**, může rybář stále otevřít spor a napadnout indexátor za podávání falešných dat.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Podgraf Studio**: Výkonná aplikace pro vytváření, nasazování a publikování podgrafů.
 
-- **Rybáři**: Úloha v rámci sítě Grafu, kterou zastávají účastníci, kteří sledují přesnost a integritu dat poskytovaných indexátory. Pokud Rybář identifikuje odpověď na dotaz nebo POI, o které se domnívá, že je nesprávná, může iniciovat spor s Indexátorem. Pokud spor rozhodne ve prospěch Rybáře, je Indexátor vyřazen. Konkrétně indexátor přijde o 2.5 % svého vlastního podílu na GRT. Z této částky je 50% přiznáno Rybáři jako odměna za jeho bdělost a zbývajících 50% je staženo z oběhu (spáleno). Tento mechanismus je navržen tak, aby Rybáře motivoval k tomu, aby pomáhali udržovat spolehlivost sítě tím, že zajistí, aby Indexátoři nesli odpovědnost za data, která poskytují.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Rozhodčí**: Rozhodci jsou účastníci sítě jmenovaní v rámci procesu řízení. Úkolem arbitra je rozhodovat o výsledku sporů týkajících se indexace a dotazů. Jejich cílem je maximalizovat užitečnost a spolehlivost sítě Graf.
 
-- **Slashing**: Indexerům může být snížen jejich vlastní GRT za poskytnutí nesprávného POI nebo za poskytnutí nepřesných dat. Procento slashingu je parametr protokolu, který je v současné době nastaven na 2.5% vlastního podílu indexátora. 5% z kráceného GRT připadne rybáři, který nepřesná data nebo nesprávné POI zpochybnil. Zbývajících 50% se spálí.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Odměny za indexování**: Odměny, které indexátory obdrží za indexování podgrafů. Odměny za indexování se rozdělují v GRT.
 
@@ -62,11 +60,11 @@ title: Glosář
 
 - **GRT**: Token pracovního nástroje Grafu. GRT poskytuje účastníkům sítě ekonomické pobídky za přispívání do sítě.
 
-- **POI nebo Doklad o indexování**: Když indexátor uzavře svůj příděl a chce si nárokovat své naběhlé odměny za indexování na daném podgrafu, musí předložit platný a aktuální doklad o indexování (POI). Rybáři mohou POI poskytnuté indexátorem zpochybnit. Spor vyřešený ve prospěch lovce bude mít za následek snížení indexátoru.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Uzel grafu**: Uzel grafu je komponenta, která indexuje podgrafy a zpřístupňuje výsledná data pro dotazování prostřednictvím rozhraní GraphQL API. Jako takový je ústředním prvkem zásobníku indexátoru a správná činnost Uzel grafu je pro úspěšný provoz indexátoru klíčová.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Agent indexátoru**: Agent indexeru je součástí zásobníku indexeru. Usnadňuje interakce indexeru v řetězci, včetně registrace v síti, správy rozmístění podgrafů do jeho grafových uzlů a správy alokací.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **Klient grafu**: Knihovna pro decentralizované vytváření dapps na bázi GraphQL.
 
@@ -76,12 +74,8 @@ title: Glosář
 
 - **Období vychladnutí**: Doba, která zbývá do doby, než indexátor, který změnil své parametry delegování, může tuto změnu provést znovu.
 
-- **Nástroje pro přenos L2**: Chytré smlouvy a UI, které umožňují účastníkům sítě převádět aktiva související se sítí z mainnetu Ethereum do Arbitrum One. Účastníci sítě mohou převádět delegované GRT, podgrafy, kurátorské podíly a vlastní podíl Indexera.
-
-- **_Vylepšit_ podgrafu do Sítě grafů**: Proces přesunu podgrafu z hostované služby do Sítě grafů.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Aktualizace_ podgrafu**: Proces vydání nové verze podgrafu s aktualizacemi manifestu, schématu nebo mapování podgrafu.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrace**: Proces sdílení kurátorů, při kterém se přechází ze staré verze podgrafu na novou verzi podgrafu (např. při aktualizaci verze v0.0.1 na verzi v0.0.2).
-
-- **Okno aktualizace**: Odpočet, kdy mohou uživatelé hostovaných služeb aktualizovat své podgrafy na síť The Graph Network, začíná 11, dubna a končí 12, června 2024.

From 32f970795fcb7076b8b19180cd4641dcd44dd4f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:50:59 -0500
Subject: [PATCH 0997/1325] New translations glossary.mdx (German)

---
 website/pages/de/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/de/glossary.mdx b/website/pages/de/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/de/glossary.mdx
+++ b/website/pages/de/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 8ec5bc8f158b42600879b2053f9504f45fa3fe55 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:00 -0500
Subject: [PATCH 0998/1325] New translations glossary.mdx (Italian)

---
 website/pages/it/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/it/glossary.mdx b/website/pages/it/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/it/glossary.mdx
+++ b/website/pages/it/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 6cc2a9d65aa53ea5fc87fff1992bcf7a78107744 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:01 -0500
Subject: [PATCH 0999/1325] New translations glossary.mdx (Japanese)

---
 website/pages/ja/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/ja/glossary.mdx b/website/pages/ja/glossary.mdx
index 8b41d244d3e7..ced046d1391e 100644
--- a/website/pages/ja/glossary.mdx
+++ b/website/pages/ja/glossary.mdx
@@ -10,11 +10,9 @@ title: 用語集
 
 - **エンドポイント**: サブグラフのクエリに使用できる URL。 Subgraph Studio のテスト エンドポイントは `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` であり、Graph Explorer エンドポイントは `https: //gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. Graph Explorer エンドポイントは、The Graph の分散型ネットワーク上のサブグラフをクエリするために使用されます。
 
-- **サブグラフ**： ブロックチェーンからデータを抽出し、処理し、GraphQLで簡単にクエリできるように保存するオープンAPIです。開発者はサブグラフを構築し、デプロイし、グラフネットワークに公開することができます。その後、インデクサーはサブグラフのインデックス作成を開始して、誰でもクエリできるようにします。
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **ホスティングサービス**： The Graphの分散型ネットワークが、サービスコスト、サービス品質、開発者エクスペリエンスを成熟させつつある中、サブグラフの構築とクエリのための一時的な足場となるサービスです。
-
-- **インデクサー**：ブロックチェーンからデータをインデックスし、GraphQLクエリを提供するためにインデックスノードを実行するネットワーク参加者です。
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **インデクサー報酬**：GRTでは、インデクサー報酬は、クエリ料金のリベートとインデックスの報酬の2つの要素で成り立っています。
 
@@ -22,19 +20,19 @@ title: 用語集
 
   2. **インデックス作成報酬**：インデクサーが、サブグラフのインデックス作成に対して受け取る報酬です。インデックス報酬は、毎年3%のGRTを新規に発行することで発生します。
 
-- **インデクサーのセルフステーク**：インデクサーが分散型ネットワークに参加するためにステークするGRTの金額です。最低額は100,000GRTで、上限はありません。
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **デリゲーター**：GRTを所有し、そのGRTをインデクサーに委任するネットワーク参加者です。これにより、インデクサーはネットワーク上のサブグラフへの出資比率を高めることができます。デリゲーターは、インデクサーがサブグラフを処理する際に受け取るインデクサー報酬の一部を受け取ります。
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **デリゲーション・タックス**。デリゲーターがインデクサーにGRTを委任する際に支払う0.5%の手数料です。手数料の支払いに使われたGRTはバーンされます。
 
-- **キュレーター**：質の高いサブグラフを特定し、キュレーションシェアと引き換えにそれらを「キュレーション」する（つまり、その上でGRTをシグナルする）ネットワーク参加者。インデクサーがサブグラフのクエリ料を請求すると、10%がそのサブグラフのCuratorに分配されます。インデクサーは、サブグラフ上のシグナルに比例してインデックス作成報酬を得ます。GRTのシグナル量と、サブグラフのインデックスを作成するインデクサーの数には相関関係があります。
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **キュレーション税**。キュレーターがサブグラフにGRTのシグナルを送る際に支払う1%の手数料。手数料を支払うために使用されるGRTはバーンされます。
 
-- **サブグラフ・コンシューマー**。消費者。サブグラフにクエリをするアプリケーションやユーザーが主となります。
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **サブグラフ・デベロッパー**：The Graphの分散型ネットワークにサブグラフを構築し、デプロイする開発者のことです。
 
@@ -46,15 +44,15 @@ title: 用語集
 
   1. **アクティブ**：アロケーションは、オンチェーンで作成されたときにアクティブとみなされます。これはアロケーションを開くと呼ばれ、インデクサーが特定のサブグラフのために積極的にインデックスを作成し、クエリを提供していることをネットワークに示しています。アクティブなアロケーションは、サブグラフ上のシグナルと割り当てられたGRTの量に比例してインデックス作成報酬を発生させます。
 
-  2. **クローズ**： インデックス作成者は、最近の有効なインデックス証明(POI) を提出することで、 与えられたサブグラフに発生したインデックス報酬を要求することができる。これは割り当てを終了することとして知られている。割り当てを閉じるには、最低1エポック開いていなければなりません。最大割当期間は28エポックです。もしインデクサが28エポックを超えて割り当てを開いたままにしておくと、その割り当ては古くなった割り当てとして知られています。割り当てが**クローズ**状態にあるときでも、 フィッシャーマンは、虚偽のデータを提供したとして、 インデクサーに異議を申し立てるために紛争を開くことができます。
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**：サブグラフの構築、デプロイ、公開のための強力なDAPです。
 
-- **フィッシャーマン**： The Graph Networkの中で、Indexersが提供するデータの正確性と完全性を監視する参加者が持つ役割。フィッシャーマンは、不正確であると思われるクエリ応答やPOIを特定した場合、インデクサに対して論争を開始することができる。もし紛争がフィッシャーマンに有利な裁定を下した場合、 インデックサーは切り捨てられます。具体的には、インデクサーのGRTの2.5%を失う。この額のうち、50％は警戒に対する報奨金としてフィッシャーマンに与えられ、残りの50％は流通から外される（燃やされる）。この仕組みは、インデクサーの提供するデータに対する責任を保証することで、ネットワークの信頼性維持に貢献するようフィッシャーマンを奨励するためのものです。
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **アービトレーター（仲裁人）**： 仲裁人は、ガバナンスプロセスを通じて任命されるネットワーク参加者です。仲裁人の役割は、インデックス作成とクエリの論争の結果を決定することです。その目的は、グラフネットワークの実用性と信頼性を最大化することです。
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **インデックス作成報酬**：インデクサーがサブグラフのインデックス作成に対して受け取る報酬です。インデックス作成報酬はGRTで分配されます。
 
@@ -62,11 +60,11 @@ title: 用語集
 
 - **GRT**: Graphのワークユーティリティトークン。GRTは、ネットワーク参加者にネットワークへの貢献に対する経済的インセンティブを提供します。
 
-- **POIまたはインデックス証明**： インデクサーが割り当てを終了し、与えられたサブグラフについて発生したインデックス報酬を要求する場合、有効で最近のインデックスの証明（POI）を提出しなければなりません。フィッシャーマンは、インデクサーの提示した POI に異議を唱えることができます。フィッシャーマンに有利に解決された論争は、そのインデクサーのスラッシュに繋がります。
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **グラフノード**：Graph Nodeは、サブグラフにインデックスを付け、その結果得られたデータをGraphQL APIを介してクエリに利用できるようにするコンポーネントです。そのため、インデクサースタックの中心であり、グラフノードの正しい動作は、成功するインデクサを実行するために重要です。
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **インデクサエージェント**：インデクサエージェントは、インデクサスタックの一部です。ネットワークへの登録、グラフノードへのサブグラフの展開の管理、割り当ての管理など、チェーン上でのインデクサーのインタラクションを促進します。
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **グラフクライアント**：GraphQLベースのDappsを分散的に構築するためのライブラリです。
 
@@ -76,12 +74,8 @@ title: 用語集
 
 - **クールダウン期間**：デリゲーションパラメータを変更したインデクサが再度デリゲーションできるようになるまでの残り時間。
 
-- **L2転送ツール**：ネットワーク参加者がイーサリアムメインネットからArbitrum Oneにネットワーク関連資産を転送できるようにするスマートコントラクトとUIです。ネットワーク参加者は、委任されたGRT、サブグラフ、キュレーションシェア、およびインデクサーのセルフステークを転送できます。
-
-- サブグラフを Graph Network に***アップグレード*する**: サブグラフをホストされたサービスから Graph Network に移動するプロセス。
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- サブグラフ**の*更新***: サブグラフのマニフェスト、スキーマ、または更新を含む新しいサブグラフ バージョンをリリースするプロセス。マッピング。
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **移行**：サブグラフの古いバージョンから新しいバージョンに移行するキュレーション共有のプロセスです（例えば、v0.0.1がv0.0.2に更新される場合）。
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 10f23005c6b0433a1d92ca2892734a07ee5ce79b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:02 -0500
Subject: [PATCH 1000/1325] New translations glossary.mdx (Korean)

---
 website/pages/ko/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/ko/glossary.mdx b/website/pages/ko/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/ko/glossary.mdx
+++ b/website/pages/ko/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From ce550a49fef573ed5b28a178f77e15c66ad3316f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:03 -0500
Subject: [PATCH 1001/1325] New translations glossary.mdx (Dutch)

---
 website/pages/nl/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/nl/glossary.mdx b/website/pages/nl/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/nl/glossary.mdx
+++ b/website/pages/nl/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 88b2894b7fde57262959ba91d3bcc250aed8a9c7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:04 -0500
Subject: [PATCH 1002/1325] New translations glossary.mdx (Polish)

---
 website/pages/pl/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/pl/glossary.mdx b/website/pages/pl/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/pl/glossary.mdx
+++ b/website/pages/pl/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 8c785c45628e67fa83df528b83b153d09b487bee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:06 -0500
Subject: [PATCH 1003/1325] New translations glossary.mdx (Portuguese)

---
 website/pages/pt/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/pt/glossary.mdx b/website/pages/pt/glossary.mdx
index 75cc00cb710e..e7442f46ccba 100644
--- a/website/pages/pt/glossary.mdx
+++ b/website/pages/pt/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossário
 
 - **Endpoint** (ponto final): Um URL para consultar um subgraph. O endpoint de testes para o Subgraph Studio é `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` e o endpoint do Graph Explorer é `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. O endpoint do Graph Explorer é utilizado para consultar subgraphs na rede descentralizada do The Graph.
 
-- **Subgraph**: Uma API aberta que extrai dados de uma blockchain, os processa e os armazena para que possem ser consultados com facilidade via GraphQL. Programadores podem construir e editar subgraphs à Graph Network. Depois, os Indexadores podem começar a indexar subgraphs para disponibilizá-los para queries por qualquer pessoa.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Serviço hospedado**: Um suporte temporário para construir e consultar subgraphs, enquanto a rede descentralizada do The Graph amadurece o seu custo e qualidade de serviço e experiência de programação.
-
-- **Indexadores**: Participantes da rede que executam nodes de indexação para indexar dados de blockchains e servir consultas em GraphQL.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Fontes de Renda de Indexadores**: Os indexadores são recompensados em GRT com dois componentes: rebates de taxa de query e recompensas de indexação.
 
@@ -22,19 +20,19 @@ title: Glossário
 
   2. **Recompensas de Indexação**: As recompensas que os Indexadores recebem por indexar subgraphs. Estas são geradas por novas emissões de 3% GRT ao ano.
 
-- **Auto-Stake (Stake Próprio) do Indexador**: A quantia de GRT que os Indexadores usam para participar na rede descentralizada. A quantia mínima é 100.000 GRT, e não há limite máximo.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Indexador de Atualizações**: Um Indexador temporário feito para agir como uma reserva para queries de subgraphs não servidos por outros Indexadores na rede. Ele garante uma transição suave para subgraphs que atualizam do serviço hospedado à Graph Network. O Indexador de atualização não é competitivo com outros Indexadores. Ele apoia várias blockchains que antes estavam disponíveis apenas no serviço hospedado.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegantes**: Participantes na rede que são titulares de GRT, e delegam o seu GRT aos Indexadores. Isto permite aos Indexadores aumentar o seu stake nos subgraphs da rede. Em troca, os Delegantes recebem uma porção das Recompensas de Indexação que os Indexadores recebem por processar subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Taxa de Delegação**: Uma taxa de 0.5% paga pelos Delegantes ao delegar GRT aos Indexadores. O GRT usado para pagar a taxa é queimado.
 
-- **Curadores**: Participantes na rede que identificam subgraphs de alta qualidade, e os "curam" (por ex., sinalizam GRT neles) em troca de ações de curadoria. Quando Indexadores reivindicam taxas de query em um subgraph, 10% delas é distribuído aos Curadores daquele subgraph. Os Indexadores ganham recompensas de indexação proporcionais ao sinal em um subgraph. Perceba uma correlação entre a quantia de GRT sinalizada e o número de Indexadores que indexam um subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Taxa de Curadoria**: Uma taxa de 1% paga pelos Curadores quando sinalizam GRT em subgraphs. O GRT usado para pagar a taxa é queimado.
 
-- **Consumidor de Subgraph**: Qualquer aplicativo ou utilizador que consulta um subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Programador de Subgraph**: Um programador que constrói e lança um subgraph à rede descentralizada do The Graph.
 
@@ -46,15 +44,15 @@ title: Glossário
 
   1. **Ativa**: Uma alocação é considerada ativa quando é criada on-chain. Isto se chama abrir de uma alocação, e indica à rede que o Indexador está a indexar e servir consultas ativamente para um subgraph particular. Alocações ativas acumulam recompensas de indexação proporcionais ao sinal no subgraph, e à quantidade de GRT alocada.
 
-  2. **Fechada**: Um Indexador pode resgatar as recompensas acumuladas em um subgraph selecionado ao enviar uma Prova de Indexação (POI) recente e válida. Isto se chama "fechar uma alocação". Uma alocação deve ter ficado aberta por, no mínimo, um epoch antes que possa ser fechada. O período máximo de alocação é de 28 epochs; se um indexador deixar uma alocação aberta por mais que isso, ela se torna uma alocação obsoleta. Quando uma alocação está **Fechada**, um Pescador ainda pode abrir uma disputa contra um Indexador por servir dados falsos.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: um dApp poderoso para a construção, lançamento e edição de subgraphs.
 
-- **Pescadores**: Um papel na Graph Network cumprido por participantes que monitoram a precisão e integridade dos dados servidos pelos Indexadores. Quando um Pescador identifica uma resposta de query ou uma POI que acreditam ser incorreta, ele pode iniciar uma disputa contra o Indexador. Se a disputa der um veredito a favor do Pescador, o Indexador é cortado, ou seja, perderá 2.5% do seu auto-stake de GRT. Desta quantidade, 50% é dado ao Pescador como recompensa pela sua vigilância, e os 50% restantes são retirados da circulação (queimados). Este mecanismo é desenhado para encorajar Pescadores a ajudar a manter a confiança na rede ao garantir que Indexadores sejam responsabilizados pelos dados que providenciam.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Árbitros**: Participantes da rede apontados por um processo de governança. O papel do Árbitro é decidir o resultado de disputas de indexação e consultas, e a sua meta é maximizar a utilidade e confiança da Graph Network.
 
-- **Corte**: Os Indexadores podem tomar cortes em seu GRT em self-stake por fornecer uma prova de indexação (POI) incorreta ou servir dados imprecisos. A porcentagem de corte é um parâmetro do protocolo, atualmente configurado em 2.5% do auto-stake de um Indexador. 50% do GRT cortado vai ao Pescador que disputou os dados ou POI incorretos. Os outros 50% são queimados.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Recompensas de Indexação**: As recompensas que os Indexadores recebem por indexar subgraphs, distribuídas em GRT.
 
@@ -62,11 +60,11 @@ title: Glossário
 
 - **GRT**: O token de utilidade do The Graph, que oferece incentivos económicos a participantes da rede por contribuir.
 
-- **POI ou Prova de Indexação**: Quando um Indexador fecha a sua alocação e quer reivindicar as suas recompensas de indexação acumuladas em um certo subgraph, ele deve providenciar uma Prova de Indexação (POI) válida e recente. Os Pescadores podem disputar a POI providenciada por um Indexador; disputas resolvidas a favor do Pescador causam um corte para o Indexador.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: O componente que indexa subgraphs e disponibiliza os dados resultantes abertos a queries através de uma API GraphQL. Assim ele é essencial ao stack de indexadores, e operações corretas de um Graph Node são cruciais para executar um indexador com êxito.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Agente de Indexador**: Parte do stack do indexador. Ele facilita as interações do Indexer on-chain, inclusive registos na rede, gestão de lançamentos de Subgraph ao(s) seu(s) Graph Node(s), e gestão de alocações.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: Uma biblioteca para construir dApps baseados em GraphQL de maneira descentralizada.
 
@@ -76,12 +74,8 @@ title: Glossário
 
 - **Período de Tempo de Recarga**: O tempo restante até que um Indexador que mudou os seus parâmetros de delegação possa fazê-lo novamente.
 
-- **Ferramentas de Transferência para L2**: Contratos inteligentes e interfaces que permitem que os participantes na rede transfiram ativos relacionados à rede da mainnet da Ethereum ao Arbitrum One. Os participantes podem transferir GRT delegado, subgraphs, ações de curadoria, e o autostake do Indexador.
-
-- **_Atualização_ de um subgraph à Graph Network**: O processo de migrar um subgraph do serviço hospedado à Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Atualização_ de um subgraph**: O processo de lançar uma nova versão de subgraph com atualizações ao manifest, schema e mapeamentos do subgraph.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migração**: O processo de movimentar ações de curadoria da versão antiga de um subgraph a uma versão nova de um subgraph (por ex., quando a v.0.0.1 é atualizada à v.0.0.2).
-
-- **Janela de Atualização**: O período para que utilizadores do serviço hospedado atualizem o(s) seu(s) subgraph(s) à Graph Network começa em 11 de abril e termina em 12 de junho de 2024.

From 56194180f71453e6e448826a3098c6a4be319c4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:07 -0500
Subject: [PATCH 1004/1325] New translations glossary.mdx (Russian)

---
 website/pages/ru/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/ru/glossary.mdx b/website/pages/ru/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/ru/glossary.mdx
+++ b/website/pages/ru/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 7f780c0ea5f30f8fda40ff04cae3ad6d73b5b7db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:08 -0500
Subject: [PATCH 1005/1325] New translations glossary.mdx (Swedish)

---
 website/pages/sv/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/sv/glossary.mdx b/website/pages/sv/glossary.mdx
index 5623c1c1b9fc..fffe4b8e1ef7 100644
--- a/website/pages/sv/glossary.mdx
+++ b/website/pages/sv/glossary.mdx
@@ -10,11 +10,9 @@ title: Ordlista
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Ordlista
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegationsavgift **: En avgift på 0,5% som betalas av Delegatorer när de delegerar GRT till Indexers. Det GRT som används för att betala avgiften bränns.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Ordlista
 
   1. **Aktiv**: En allokering anses vara aktiv när den skapas på kedjan. Detta kallas att öppna en allokering och indikerar för nätverket att Indexer aktivt indexerar och betjänar frågor för en särskild subgraf. Aktiva allokeringar ackumulerar indexbelöningar proportionellt mot signalen på subgrafen och mängden GRT som allokerats.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **SubGraf Studio**: En kraftfull dapp för att bygga, distribuera och publicera subgrafer.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexbelöningar**: De belöningar som Indexers får för att indexera subgrafer. Indexbelöningar distribueras i GRT.
 
@@ -62,11 +60,11 @@ title: Ordlista
 
 - **GRT**: The Graph's arbetsnytto-token. GRT tillhandahåller ekonomiska incitament för nätverksdeltagare att bidra till nätverket.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Grafnod**: Graph Node är komponenten som indexerar subgrafer och gör den resulterande datan tillgänglig för frågor via ett GraphQL API. Som sådan är den central för indexeringsstacken och korrekt drift av Graph Node är avgörande för att köra en framgångsrik Indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer-agent**: Indexer-agenten är en del av indexeringsstacken. Den underlättar Indexers interaktioner på kedjan, inklusive registrering på nätverket, hantering av subgrafers distributioner till dess Graph Node(s), och hantering av allokeringar.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Klient**: Ett bibliotek för att bygga decentraliserade dappar baserade på GraphQL.
 
@@ -76,12 +74,8 @@ title: Ordlista
 
 - **Cooldown-period**: Den återstående tiden tills en Indexer som ändrade sina delegationsparametrar kan göra det igen.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Uppgradering_ av en subgraf till The Graf Nätverk**: Processen att flytta en subgraf från hosted service till The Graph Nätverk.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Uppdatering_ av en subgraf**: Processen att släppa en ny subgrafversion med uppdateringar av subgrafens manifest, schema eller avbildning.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 46630de7c0ee1720e43d759cced451daf1dbfb49 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:09 -0500
Subject: [PATCH 1006/1325] New translations glossary.mdx (Turkish)

---
 website/pages/tr/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/tr/glossary.mdx b/website/pages/tr/glossary.mdx
index 23b85c69e0c1..9c7b1781c257 100644
--- a/website/pages/tr/glossary.mdx
+++ b/website/pages/tr/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Uç Nokta**: Bir subgraph'ı sorgulamak için kullanılabilecek bir URL'dir. Subgraph Stüdyo için test uç noktası `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` ve Graph Gezgini uç noktası `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>` şeklindedir. Graph Gezgini uç noktası, Graph'ın merkeziyetsiz ağındaki subgraphları sorgulamak için kullanılır.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **İndeksleme Ödülleri**: İndeksleyicilerin subgraph'leri indeksleme karşılığında aldığı ödüller. İndeksleme ödülleri, yıllık %3 GRT'nin yeni ihracı yoluyla oluşturulur.
 
-- **İndeksleyicinin Kendi Stake'i**: İndeksleyicilerin merkeziyetsiz ağa katılmak için stake ettikleri GRT miktarıdır. Minimum 100.000 GRT'dir ve üst sınır yoktur.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegatörler**: GRT'ye sahip olan ve GRT'lerini indeksleyicilere stake eden ağ katılımcıları. Bu, indeksleyicilerin ağdaki subgraph'lerde mevcut paylarını artırmalarına olanak tanır. Buna karşılık, delegatörler, indeksleyicilerin subgraph'leri işlemek için aldıkları indeksleme ödüllerinin bir kısmını alırlar.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegasyon Vergisi**: GRT'yi indeksleyicilere stake ettiklerinde delegatörler tarafından ödenen %0,5'lik bir ücret. Ücreti ödemek için kullanılan GRT yakılır.
 
-- **Küratörler**: Yüksek kaliteli subgraph'leri belirleyen ve bunları küratörlük paylaşımları karşılığında "düzenleyen" (yani üzerlerinde GRT sinyali veren) ağ katılımcılarıdır. İndeksleyiciler bir subgraph'te sorgulama ücreti talep ettiğinde, o subgraph'in küratörlerine %10 dağıtılır. İndeksleyiciler, bir subgraph'teki sinyalle orantılı indeksleme ödülleri kazanır. Sinyal verilen GRT miktarı ile bir subgraph'i indeksleyen indeksleyicilerin sayısı arasında bir korelasyon görüyoruz.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Kurasyon Vergisi**: Küratörler tarafından subgraph'lerde GRT sinyali verildiğinde ödenen %1'lik bir ücrettir. Ücreti ödemek için kullanılan GRT yakılır.
 
-- **Subgraph Tüketicisi**: Bir subgraph'ği sorgulayan herhangi bir uygulama veya kullanıcı.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Geliştiricisi**: Graph'in merkeziyetsiz ağına bir subgraph inşa eden ve dağıtan bir geliştirici.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Aktif**: Bir tahsis, zincir üzerinde oluşturulduğunda aktif kabul edilir. Buna tahsis açma denir ve ağa, indeksleyicinin belirli bir subgraph için sorguları aktif olarak indekslediğini ve sunduğunu gösterir. Aktif tahsisler, subgraph'teki sinyal ve tahsis edilen GRT miktarı ile orantılı olarak indeksleme ödülleri tahakkuk ettirir.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Stüdyo**: Subgraph'ler oluşturmak, deploy etmek ve yayınlamak için güçlü bir merkeziyetsiz uygulamadır.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **İndeksleme Ödülleri**: İndeksleyicilerin subgraph'leri indeksleme karşılığında aldığı ödüllerdir. İndeksleme ödülleri GRT şeklinde dağıtılır.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: Graph'in çalışma yardımcı programı belirtecidir. GRT, ağ katılımcılarına ağa katkıda bulunmaları için ekonomik teşvikler sağlar.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node, subgraph'leri indeksleyen ve elde edilen verileri bir GraphQL API aracılığıyla sorgulanabilir hale getiren bileşendir. Bu nedenle, indeksleyici yığınının merkezinde yer alır ve Graph node'unun doğru çalışması, başarılı bir indeksleyici olabilmek için çok önemlidir.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **İndeksleyici Aracı**: İndeksleyici aracı, indeksleyici yığının bir parçasıdır. Ağa kaydolma, Graph node'larına subgraph deploy sürecini ve tahsisleri yönetme dahil olmak üzere indeksleyicinin zincir üzerindeki etkileşimlerini kolaylaştırır.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **Graph Tüketicileri**: Merkeziyetsiz bir şekilde GraphQL tabanlı merkeziyetsiz uygulamalar inşa etmeye yönelik bir kitaplık.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Soğuma Süresi**: Yetki parametrelerini değiştiren indeksleyicinin bunu tekrar yapabilmesi için kalan süre.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **Bir subgraph'ı Graph Ağı'na _yükseltme_**: Bir subgraph'ı barındırılan hizmetten Graph Ağı'na taşıma işlemi.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **Bir subgraph'ın _güncellenmesi_**: Subgraph manifestosunda, şemasında veya eşleştirmelerinde yapılan güncellemelerle yeni bir subgraph sürümü yayınlama işlemi.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From e23bce92cd30b7784816632d02e02dd0eeb758a8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:10 -0500
Subject: [PATCH 1007/1325] New translations glossary.mdx (Ukrainian)

---
 website/pages/uk/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/uk/glossary.mdx b/website/pages/uk/glossary.mdx
index 392cc6b55f27..162a88d424e0 100644
--- a/website/pages/uk/glossary.mdx
+++ b/website/pages/uk/glossary.mdx
@@ -10,11 +10,9 @@ title: Глосарій
 
 - **Кінцева точка**: URL-адреса, яку можна використовувати для запиту підграфа. Кінцевою точкою тестування для Subgraph Studio є `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>`, а кінцевою точкою для Graph Explorer є `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. Кінцева точка Graph Explorer використовується для запиту підграфів у децентралізованій мережі The Graph.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Індексатори**: Користувачі мережі, які запускають ноди індексації для індексування даних з блокчейнів та обслуговування запитів до GraphQL.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Винагорода індексаторам в GRT складається з двох компонентів: певна комісія за запити (query fee rebates) та винагорода за індексацію (indexing rewards).
 
@@ -22,19 +20,19 @@ title: Глосарій
 
   2. **Indexing Rewards**: Винагорода, яку отримують індексатори за індексування підграфів. Винагорода за індексацію формується шляхом випуску нової емісії 3% GRT щорічно.
 
-- **Indexer's Self Stake**: Сума токенів GRT, яку Індексатори стейкають, щоб брати участь у децентралізації мережі. Мінімальна сума становить 100 000 GRT, без верхнього ліміту.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Делегати**: Користувачі мережі, які володіють токеном GRT та делегують його Індексаторам. Це дозволяє індексаторам збільшити кількість застейканих токенів на власних підграфах всередині мережі. Натомість делегати отримують частину винагороди за індексування, яку індексатори отримують за свою роботу.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: Комісія у розмірі 0.5% сплачується делегатами, коли вони делегують власні GRT індексаторам. GRT, який використовувався для сплати цієї комісії, спалюється.
 
-- **Куратори**: Користувачі мережі, які ідентифікують якісні підграфи та "курують" їх (тобто подають на них сигнал за допомогою власних GRT токенів) в обмін на винагороди за кураторство. Коли індексатори отримують плату за запит до підграфа, 10% розподіляється між Кураторами цього підграфа. Індексатори отримують винагороду за індексацію пропорційно кількості сигналів на підграфі. Ми бачимо кореляцію між кількістю GRT, які були подані в якості сигналу та кількістю індексаторів, що індексують підграф.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: Комісія у розмірі 1%, яку сплачують куратори, коли подають сигнал в токенах GRT на підграфи. Відповідно GRT, що використовується для сплати цієї комісії, спалюється.
 
-- **Користувач підграфа**: Будь-яка програма або користувач, який робить запит до підграфа.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Розробник підграфа**: Розробник, який створює та розгортає підграф у децентралізованій мережі The Graph.
 
@@ -46,15 +44,15 @@ title: Глосарій
 
   1. **Активний**: Розподіл вважається активним, коли він створюється всередині мережі. Це називається відкриттям розподілу і вказує мережі на те, що індексатор активно індексує та обслуговує запити для конкретного підграфа. При активному розподілі нараховується винагорода за індексацію пропорційно до кількості сигналів на підграфі та суми розподілених GRT токенів.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: Потужний додаток для створення, розгортання та публікації підграфів.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Нагороди за індексацію**: Винагорода, яку отримують Індексатори за індексування підграфів. Винагороди за індексацію розподіляються в токенах GRT.
 
@@ -62,11 +60,11 @@ title: Глосарій
 
 - **GRT**: Функціональний токен екосистеми The Graph. GRT надає економічні заохочення учасникам мережі за їх внесок у її розвиток.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node - це компонент, який індексує підграфи та робить отримані дані доступними для запитів через GraphQL API. Загалом, він є центральним елементом стека індексатора, і правильна робота Graph Node має вирішальне значення для успішної роботи індексатора.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Агент індексації**: Агент індексації (Indexer agent) є частиною стека індексаторів. Він полегшує взаємодію Індексатора всередині мережі, включаючи реєстрацію, управління розгортанням підграфів у Graph Node та управління розподілом.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **Клієнт The Graph**: Бібліотека для децентралізованого створення додатків на основі GraphQL.
 
@@ -76,12 +74,8 @@ title: Глосарій
 
 - **Період очікування**: Час, що залишився до того моменту, як індексатор, який змінив параметри делегування, зможе зробити це знову.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From b60263c9952ada7df0fd16b25646201eb4796d11 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:11 -0500
Subject: [PATCH 1008/1325] New translations glossary.mdx (Chinese Simplified)

---
 website/pages/zh/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/zh/glossary.mdx b/website/pages/zh/glossary.mdx
index dea556fafe08..99305cea1b15 100644
--- a/website/pages/zh/glossary.mdx
+++ b/website/pages/zh/glossary.mdx
@@ -10,11 +10,9 @@ title: 术语汇编
 
 - **Endpoint**: 可以用来查询子图的URL。Subgraph Studio的测试端点是`https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>`，Graph浏览器端点`为https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`。Graph浏览器端点用于查询Graph的去中心化网络上的子图。
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted Service**: 作为 The Graph 分布式网络成熟的一个临时支架服务，用于构建和查询子图，以提高服务成本、服务质量和开发者体验。
-
-- **Indexers**：网络参与者运行索引节点，从区块链索引数据并提供 GraphQL 查询。
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**：索引人在 GRT 中获得两个组成部分: 查询费用回扣和索引奖励。
 
@@ -22,19 +20,19 @@ title: 术语汇编
 
   2. **Indexing Rewards**: 索引人因为索引子图而获得的奖励。索引奖励是通过每年发行3% 的 GRT 来产生的。
 
-- **Indexer's Self Stake**: 索引人参与去中心化网络的 GRT 金额。最低为100000 GRT，并且没有上限。
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: 拥有 GRT 并将其 GRT 委托给索引人的网络参与者。这使得索引人可以增加它们在网络子图中的份额。作为回报，委托方将获得索引方为处理子图而获得的索引奖励的一部分。
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: 委托人将 GRT 委托给索引人时支付的0.5% 的费用。用于支付费用的 GRT 将被消耗。
 
-- **Curators**: 网络参与者，识别高质量的子图，并“策展”他们(即，对他们发GRT信号) ，以换取策展份额。当索引人索赔子图上的查询费用时，10% 将分配给该子图的策展人。索引认获得与子图上的信号成比例的索引奖励。我们可以看到发出信号的 GRT 数量与索引子图的索引人数量之间的相关性。
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: 当策展人在子图上显示 GRT 时，他们要支付1% 的费用。用于支付费用的 GRT 将被消耗。
 
-- **Subgraph Consumer**: 查询子图的任何应用程序或用户。
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: 构建并部署子图到 Graph 去中心化网络的开发人员。
 
@@ -46,15 +44,15 @@ title: 术语汇编
 
   1. **Active**: 分配在链上创建时被认为是活动的。这称为打开一个分配，并向网络表明索引人正在为特定子图建立索引并提供查询服务。主动分配的增值索引奖励与子图上的信号以及分配的 GRT 的数量成比例。
 
-  2. **Closed**: 索引人可以通过提交最近的、有效的索引证明（POI）来领取在给定子图上累积的索引奖励。这被称为关闭分配。在关闭之前，分配必须至少开放一个纪元。最大分配期为 28 个纪元。如果索引人在 28 个纪元之后仍然保持分配开放状态，则被称为过时分配。当分配处于 **Closed** 状态时，渔夫仍然可以提出异议，挑战索引人提供虚假数据。
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: 用于构建、部署和发布子图的强大 dapp。
 
-- **Fishermen**: The Graph Network 中的一个角色，由监视索引人提供的数据的准确性和完整性的参与者担任。当渔夫发现他们认为是不正确的查询响应或 POI 时，他们可以对索引人提起争议。如果争议裁定有利于渔夫，索引人将被削减。具体而言，索引人将失去他们的 GRT 自有股份的 2.5%。其中，50%作为对渔夫的奖励，以表彰他们的警惕性，剩下的50%将被从流通中移除（销毁）。这个机制旨在鼓励渔夫通过确保索引人对他们提供的数据负责来帮助维护网络的可靠性。
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: 仲裁员是通过治理设置的网络参与者。仲裁员的作用是决定索引和查询争议的结果。他们的目标是最大限度地提高Graph网络的效用和可靠性。
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: 索引人因为索引子图而获得的奖励。索引奖励是通过GRT 来分配的。
 
@@ -62,11 +60,11 @@ title: 术语汇编
 
 - **GRT**: Graph的工作效用代币。 GRT 为网络参与者提供经济激励，鼓励他们为网络做出贡献。
 
-- **POI or Proof of Indexing**: 当一个索引人关闭他们的分配，并希望要求他们的累积索引人奖励在一个给定的子图，他们必须提供一个有效的和最近的索引证明(POI)。Fishermen可以对索引人提供的 POI 提出异议。Fisherman胜出的争端将导致索引人被惩罚。
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph节点是索引子图的组件，并使生成的数据可通过GraphQL API进行查询。因此，它是索引人堆栈的中心，Graph节点的正确操作对于运行成功的索引人至关重要。
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: 索引人代理是索引人堆栈的一部分。它促进了索引人在链上的交互，包括在网络上注册、管理到其 Graph节点的子图部署以及分配管理。
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: 用于以去中心化方式构建基于 GraphQL 的 dapps 的库。
 
@@ -76,12 +74,8 @@ title: 术语汇编
 
 - **Cooldown Period**: 直到更改其委托参数的索引人可以再次进行此操作之前的剩余时间。
 
-- **L2 Transfer Tools**: 智能合约和UI，使网络参与者能够从以太坊主网转移到Arbitrum One。网络参与者可以转移委托的GRT、子图、策展股份和索引者自己的股份。
-
-- **_升级_ 子图到 Graph网络中**: 将子图从托管服务移动到Graph网络的过程.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_更新_ 子图**: 发布新子图版本的过程，其中包含对子图的清单、模式或映射的更新。
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: 策展份额从子图的旧版本移动到子图的新版本的过程（例如，从 v0.0.1 更新到 v0.0.2）。
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 225dcc77e5ec603a41e588c2676009b320327a19 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:12 -0500
Subject: [PATCH 1009/1325] New translations glossary.mdx (Urdu (Pakistan))

---
 website/pages/ur/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/ur/glossary.mdx b/website/pages/ur/glossary.mdx
index 637afbec2617..1b58dd720662 100644
--- a/website/pages/ur/glossary.mdx
+++ b/website/pages/ur/glossary.mdx
@@ -10,11 +10,9 @@ title: لغت
 
 - **اینڈ پوائنٹ**: ایک URL جسے سب گراف سے کیوری کرنے کے لیے استعمال کیا جا سکتا ہے۔ سب گراف سٹوڈیو کے لیے ٹیسٹنگ اینڈ پوائنٹ ہے `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` اور گراف ایکسپلورر اینڈ پوائنٹ ہے `https: //gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`۔ گراف ایکسپلورر اینڈ پوائنٹ کا استعمال گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر سب گراف کے بارے میں کیوری کرنے کے لیے کیا جاتا ہے.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **انڈیکسرز**: نیٹ ورک کے شرکاء جو بلاکچینز سے ڈیٹا کو انڈیکس کرنے کے لیے انڈیکسنگ نوڈس چلاتے ہیں اور GraphQL کی کیوریز پیش کرتے ہیں.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **انڈیکسر کے آمدنی کے سلسلے** انڈیکسرز کو GRT میں دو اجزاء کے ساتھ انعام دیا جاتا ہے: کیوری کی فیس میں چھوٹ اور انڈیکسنگ کے انعامات.
 
@@ -22,19 +20,19 @@ title: لغت
 
   2. **انڈیکسنگ انعامات**: وہ انعامات جو انڈیکسرز کو انڈیکس کرنے والے سب گراف کے لیے موصول ہوتے ہیں۔انڈیکسنگ کے انعامات سالانہ 3% GRT کے نئے اجراء کے ذریعے بنائے جاتے ہیں.
 
-- **انڈیکسر سیلف سٹیک**: GRT کی وہ مقدار جو انڈیکسرز ڈیسینٹرالائزڈ نیٹ ورک میں حصہ لینے کے لیے لگاتے ہیں۔ کم از کم 100,000 GRT ہے، اور کوئی اوپری حد نہیں ہے.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **ڈیلیگیٹرز**: نیٹ ورک کے شرکاء جو GRT کے مالک ہیں اور اپنی GRT انڈیکسرز کو تفویض کرتے ہیں۔ یہ انڈیکسرز کو نیٹ ورک پر سب گراف میں اپنا حصہ بڑھانے کی اجازت دیتا ہے۔ بدلے میں، ڈیلیگیٹرز کو انڈیکسنگ کے انعامات کا ایک حصہ ملتا ہے جو انڈیکسرز سب گراف پر کارروائی کرنے کے لیے وصول کرتے ہیں.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **ڈیلیگیشن ٹیکس**: ڈیلیگیٹرز کی طرف سے 0.5% فیس ادا کی جاتی ہے جب وہ انڈیکسرز کو GRT تفویض کرتے ہیں۔ فیس کی ادائیگی کے لیے استعمال ہونے والی GRT کو جلا دیا جاتا ہے.
 
-- **کیوریٹرز**: نیٹ ورک کے شرکاء جو اعلیٰ معیار کے سب گراف کی شناخت کرتے ہیں، اور کیوریشن شیئرز کے بدلے انہیں "کیوریٹ" کرتے ہیں (یعنی ان پر GRT کا اشارہ دیتے ہیں)۔ جب انڈیکسرز کسی سب گراف پر کیوری کی فیس کا دعویٰ کرتے ہیں، تو 10% اس سب گراف کے کیوریٹرز میں تقسیم کیا جاتا ہے۔ انڈیکسرز سب گراف پر سگنل کے متناسب انڈیکسنگ کے انعامات حاصل کرتے ہیں۔ ہم GRT سگنل کی مقدار اور سب گراف کو ترتیب دینے والے انڈیکسرز کی تعداد کے درمیان باہمی تعلق دیکھتے ہیں.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **کیوریشن ٹیکس**: کیوریٹرز کے ذریعہ 1% فیس ادا کی جاتی ہے جب وہ سب گرافس پر GRT کا اشارہ دیتے ہیں۔ فیس کی ادائیگی کے لیے استعمال ہونے والی GRT کو جلا دیا جاتا ہے.
 
-- **سب گراف کنزیومر**: کوئی بھی ایپلیکیشن یا صارف جو سب گراف سے کیوری کرتا ہے.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **سب گراف ڈویلپر**: ایک ڈویلپر جو گراف کے ڈیسینٹرالائزڈ نیٹ ورک پر سب گراف بناتا اور تعینات کرتا ہے.
 
@@ -46,15 +44,15 @@ title: لغت
 
   1. **فعال**: ایک مختص کو فعال سمجھا جاتا ہے جب اسے آن چین بنایا جاتا ہے۔ اسے ایلوکیشن کھولنا کہا جاتا ہے، اور یہ نیٹ ورک کی طرف اشارہ کرتا ہے کہ انڈیکسر کسی خاص سب گراف کے لیے فعال طور پر انڈیکس کر رہا ہے اور کیوریز پیش کر رہا ہے۔ فعال مختصات سب گراف پر سگنل کے متناسب انڈیکسنگ انعامات اور مختص کردہ GRT کی رقم جمع کرتی ہیں.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **سب گراف اسٹوڈیو**: سب گراف کی تعمیر، تعیناتی اور اشاعت کے لیے ایک طاقتور ڈیپ.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **انڈیکسنگ انعامات**: وہ انعامات جو انڈیکسرز کو انڈیکس کرنے والے سب گراف کے لیے موصول ہوتے ہیں۔ انڈیکسنگ کے انعامات GRT میں تقسیم کیے جاتے ہیں.
 
@@ -62,11 +60,11 @@ title: لغت
 
 - **GRT**: گراف کے کام کا یوٹیلیٹی ٹوکن۔ GRT نیٹ ورک میں حصہ ڈالنے کے لیے نیٹ ورک کے شرکاء کو اقتصادی مراعات فراہم کرتا ہے.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **گراف نوڈ**: گراف نوڈ وہ جزو ہے جو سب گراف کو انڈیکس کرتا ہے، اور نتیجے میں ڈیٹا کو GraphQL API کے ذریعے کیوری کے لیے دستیاب کرتا ہے۔ اس طرح یہ انڈیکسر اسٹیک میں مرکزی حیثیت رکھتا ہے، اور ایک کامیاب انڈیکسر چلانے کے لیے گراف نوڈ کا درست آپریشن بہت ضروری ہے.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **انڈیکسر ایجنٹ**: انڈیکسر ایجنٹ انڈیکسر اسٹیک کا حصہ ہے۔ یہ انڈیکسر کے آن چین تعاملات کو سہولت فراہم کرتا ہے، بشمول نیٹ ورک پر رجسٹر کرنا، اس کے گراف نوڈز پر سب گراف کی تعیناتیوں کا انتظام کرنا، اور مختص کا انتظام کرنا.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **گراف کلائنٹ**: ڈیسینٹرالائزڈ طریقے سے GraphQL پر مبنی ڈیپ بنانے کے لیے ایک لائبریری.
 
@@ -76,12 +74,8 @@ title: لغت
 
 - **کولڈاؤن کا دورانیہ**: ایک انڈیکسر جس نے اپنے ڈیلیگیشن پیرامیٹرز کو تبدیل کیا ہے اس وقت تک باقی وقت دوبارہ ایسا کر سکتا ہے.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **گراف نیٹ ورک پر سب گراف کو _اپ گریڈ_ کرنا**: ہوسٹڈ سروس سے گراف نیٹ ورک پر سب گراف منتقل کرنے کا عمل۔
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **سب گراف کو _اپ ڈیٹ_ کرنا**: سب گراف کے مینی فیسٹ، سکیما، یا میپنگز میں اپ ڈیٹس کے ساتھ ایک نیا سب گراف ورزن جاری کرنے کا عمل۔
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 0d1268df01c43fc1b1ba73ebf98ae1680c2ae27d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:14 -0500
Subject: [PATCH 1010/1325] New translations glossary.mdx (Vietnamese)

---
 website/pages/vi/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/vi/glossary.mdx b/website/pages/vi/glossary.mdx
index cd24a22fd4d5..bdeff7281023 100644
--- a/website/pages/vi/glossary.mdx
+++ b/website/pages/vi/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **Indexers**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
 
-- **Indexer's Self Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **Delegators**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
 
-- **Curators**: Network participants that identify high-quality subgraphs, and “curate” them (i.e., signal GRT on them) in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. Indexers earn indexing rewards proportional to the signal on a subgraph. We see a correlation between the amount of GRT signalled and the number of Indexers indexing a subgraph.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
 
-- **Subgraph Consumer**: Any application or user that queries a subgraph.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **Graph Node**: Graph Node is the component which indexes subgraphs, and makes the resulting data available to query via a GraphQL API. As such it is central to the indexer stack, and correct operation of Graph Node is crucial to running a successful indexer.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **Indexer agent**: The Indexer agent is part of the indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 10bf737ec489cf41048873e033ee9e6c21fd2fb8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:15 -0500
Subject: [PATCH 1011/1325] New translations glossary.mdx (Marathi)

---
 website/pages/mr/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/mr/glossary.mdx b/website/pages/mr/glossary.mdx
index 3b293eb5489a..71fd8619af45 100644
--- a/website/pages/mr/glossary.mdx
+++ b/website/pages/mr/glossary.mdx
@@ -10,11 +10,9 @@ title: Glossary
 
 - **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **इंडेक्सर्स**: नेटवर्क सहभागी जे ब्लॉकचेनमधील डेटा इंडेक्स करण्यासाठी इंडेक्सिंग नोड्स चालवतात आणि GraphQL क्वेरी सर्व्ह करतात.
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
 
 - **इंडेक्सर रेव्हेन्यू स्ट्रीम्स**: GRT मध्ये इंडेक्सर्सना दोन घटकांसह पुरस्कृत केले जाते: क्वेरी फी रिबेट्स आणि इंडेक्सिंग रिवॉर्ड्स.
 
@@ -22,19 +20,19 @@ title: Glossary
 
   2. **इंडेक्सिंग रिवॉर्ड्स**: इंडेक्सर्सना अनुक्रमणिका सबग्राफसाठी प्राप्त होणारे पुरस्कार. इंडेक्सिंग रिवॉर्ड्स वार्षिक 3% GRT च्या नवीन जारी करून व्युत्पन्न केले जातात.
 
-- **इंडेक्सरचा सेल्फ स्टेक**: विकेंद्रीकृत नेटवर्कमध्ये भाग घेण्यासाठी इंडेक्सर्सची जीआरटीची रक्कम. किमान 100,000 GRT आहे आणि कोणतीही उच्च मर्यादा नाही.
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
 
-- **प्रतिनिधी**: नेटवर्क सहभागी जे GRT चे मालक आहेत आणि त्यांचे GRT इंडेक्सर्सना सोपवतात. हे इंडेक्सर्सना नेटवर्कवरील सबग्राफमध्ये त्यांची भागीदारी वाढविण्यास अनुमती देते. त्या बदल्यात, प्रतिनिधींना अनुक्रमणिका बक्षिसेचा एक भाग प्राप्त होतो जो इंडेक्सर्सना सबग्राफवर प्रक्रिया करण्यासाठी प्राप्त होतो.
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
 
 - **प्रतिनिधी कर**: प्रतिनिधींनी इंडेक्सर्सना GRT सोपवल्यावर 0.5% शुल्क. फी भरण्यासाठी वापरण्यात आलेला जीआरटी जळाला आहे.
 
-- **क्युरेटर**: नेटवर्क सहभागी जे उच्च-गुणवत्तेचे सबग्राफ ओळखतात आणि क्युरेशन शेअर्सच्या बदल्यात त्यांना “क्युरेट” करतात (म्हणजे त्यांच्यावर GRT सिग्नल करतात). जेव्हा इंडेक्सर्स सबग्राफवर क्वेरी फीचा दावा करतात, तेव्हा 10% त्या सबग्राफच्या क्युरेटर्सना वितरित केले जातात. इंडेक्सर्स सबग्राफवरील सिग्नलच्या प्रमाणात अनुक्रमणिका बक्षिसे मिळवतात. आम्ही GRT सिग्नलची रक्कम आणि सबग्राफ इंडेक्स करणार्‍या इंडेक्सर्सची संख्या यांच्यातील परस्परसंबंध पाहतो.
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
 
 - **क्युरेशन टॅक्स**: क्युरेटर्सने सबग्राफवर GRT सिग्नल केल्यावर 1% फी भरली जाते. फी भरण्यासाठी वापरण्यात आलेला जीआरटी जळाला आहे.
 
-- **सबग्राफ कंझ्युमर**: सबग्राफसाठी प्रश्न विचारणारा कोणताही अनुप्रयोग किंवा वापरकर्ता.
+- **Data Consumer**: Any application or user that queries a subgraph.
 
 - **सबग्राफ डेव्हलपर**: एक विकासक जो ग्राफच्या विकेंद्रीकृत नेटवर्कवर सबग्राफ तयार करतो आणि तैनात करतो.
 
@@ -46,15 +44,15 @@ title: Glossary
 
   1. **सक्रिय**: ऑन-चेन तयार केल्यावर वाटप सक्रिय मानले जाते. याला वाटप उघडणे म्हणतात, आणि नेटवर्कला सूचित करते की इंडेक्सर सक्रियपणे अनुक्रमित करत आहे आणि विशिष्ट सबग्राफसाठी क्वेरी सर्व्ह करत आहे. सक्रिय वाटप सबग्राफवरील सिग्नल आणि वाटप केलेल्या GRT रकमेच्या प्रमाणात अनुक्रमणिका बक्षिसे जमा करतात.
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
 
 - **सबग्राफ स्टुडिओ**: सबग्राफ तयार करणे, उपयोजित करणे आणि प्रकाशित करणे यासाठी एक शक्तिशाली डॅप.
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
 
 - **इंडेक्सिंग रिवॉर्ड्स**: इंडेक्सर्सना अनुक्रमणिका सबग्राफसाठी प्राप्त होणारे पुरस्कार. इंडेक्सिंग रिवॉर्ड्स GRT मध्ये वितरीत केले जातात.
 
@@ -62,11 +60,11 @@ title: Glossary
 
 - **GRT**: आलेखाचे कार्य उपयुक्तता टोकन. GRT नेटवर्क सहभागींना नेटवर्कमध्ये योगदान देण्यासाठी आर्थिक प्रोत्साहन देते.
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
 
-- **ग्राफ नोड**: ग्राफ नोड हा घटक आहे जो सबग्राफ अनुक्रमित करतो आणि परिणामी डेटा GraphQL API द्वारे क्वेरीसाठी उपलब्ध करतो. हे इंडेक्सर स्टॅकसाठी मध्यवर्ती आहे आणि यशस्वी इंडेक्सर चालवण्यासाठी ग्राफ नोडचे योग्य ऑपरेशन महत्वाचे आहे.
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
 
-- **इंडेक्सर एजंट**: इंडेक्सर एजंट इंडेक्सर स्टॅकचा भाग आहे. नेटवर्कवर नोंदणी करणे, त्याच्या ग्राफ नोड्सवर सबग्राफ उपयोजन व्यवस्थापित करणे आणि वाटप व्यवस्थापित करणे यासह इंडेक्सरच्या साखळीतील परस्परसंवाद सुलभ करते.
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
 
 - **द ग्राफ क्लायंट**: GraphQL-आधारित dapps विकेंद्रित पद्धतीने तयार करण्यासाठी लायब्ररी.
 
@@ -76,12 +74,8 @@ title: Glossary
 
 - **कूलडाउन कालावधी**: इंडेक्सर ज्याने त्यांचे प्रतिनिधीत्व पॅरामीटर्स बदलले आहेत तोपर्यंत तो पुन्हा करू शकतो.
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From 3b4344cd8c7726e2106beda85cb592d698e868ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:16 -0500
Subject: [PATCH 1012/1325] New translations glossary.mdx (Hindi)

---
 website/pages/hi/glossary.mdx | 36 +++++++++++++++--------------------
 1 file changed, 15 insertions(+), 21 deletions(-)

diff --git a/website/pages/hi/glossary.mdx b/website/pages/hi/glossary.mdx
index aa9f07691bff..244ef6f95cdd 100644
--- a/website/pages/hi/glossary.mdx
+++ b/website/pages/hi/glossary.mdx
@@ -10,11 +10,9 @@ title: शब्दकोष
 
 - **समाप्ति बिंदु**: एक URL जिसका उपयोग किसी सबग्राफ को क्वेरी करने के लिए किया जा सकता है। सबग्राफ स्टूडियो के लिए टेस्टिंग एंडपॉइंट `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` है और ग्राफ एक्सप्लोरर एंडपॉइंट `https है: //gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`। ग्राफ़ एक्सप्लोरर समापन बिंदु का उपयोग ग्राफ़ के विकेन्द्रीकृत नेटवर्क पर उप-अनुच्छेदों को क्वेरी करने के लिए किया जाता है।
 
-- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Then, Indexers can begin indexing subgraphs to make them available to be queried by anyone.
+- **Subgraph**: एक ओपन एपीआई जो ब्लॉकचेन से डेटा निकालती है, उसे प्रोसेस करती है, और इसे इस तरह से स्टोर करती है कि इसे GraphQL के माध्यम से आसानी से क्वेरी किया जा सके। डेवलपर्स subgraphs बना, तैनात और The Graph Network पर प्रकाशित कर सकते हैं। एक बार इंडेक्स होने के बाद, subgraph को कोई भी क्वेरी कर सकता है।
 
-- **Hosted service**: A temporary scaffold service for building and querying subgraphs as The Graph's decentralized network is maturing its cost of service, quality of service, and developer experience.
-
-- **इंडेक्सर्स**: नेटवर्क प्रतिभागी जो ब्लॉकचेन से डेटा को इंडेक्स करने के लिए इंडेक्सिंग नोड्स चलाते हैं और ग्राफक्यूएल क्वेरीज सर्व करते हैं।
+- **Indexer**: नेटवर्क प्रतिभागी जो इंडेक्सिंग नोड्स चलाते हैं ताकि ब्लॉकचेन से डेटा को इंडेक्स करें और GraphQL क्वेरीज़ को सर्व करें।
 
 - **इंडेक्सर रेवेन्यू स्ट्रीम**: इंडेक्सर्स को जीआरटी में दो घटकों के साथ पुरस्कृत किया जाता है: क्वेरी शुल्क छूट और इंडेक्सिंग पुरस्कार।
 
@@ -22,19 +20,19 @@ title: शब्दकोष
 
   2. **इंडेक्सिंग रिवार्ड्स**: वे पुरस्कार जो इंडेक्सर्स को सबग्राफ इंडेक्स करने के लिए मिलते हैं। इंडेक्सिंग पुरस्कार सालाना 3% जीआरटी के नए जारी करने के माध्यम से उत्पन्न होते हैं।
 
-- **इंडेक्सर का सेल्फ स्टेक**: GRT की वह राशि जो इंडेक्सर्स विकेंद्रीकृत नेटवर्क में भाग लेने के लिए दांव पर लगाते हैं। न्यूनतम 100,000 जीआरटी है, और कोई ऊपरी सीमा नहीं है।
+- **Indexer का Self-Stake**: वह मात्रा GRT जो Indexers विकेंद्रीकृत नेटवर्क में भाग लेने के लिए स्टेक करते हैं। न्यूनतम 100,000 GRT है, और कोई ऊपरी सीमा नहीं है।
 
-- **Upgrade Indexer**: A temporary Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. It ensures a seamless transition for subgraphs upgrading from the hosted service to The Graph Network. The upgrade Indexer is not competitive with other Indexers. It supports numerous blockchains that were previously only available on the hosted service.
+- **Upgrade Indexer**: एक Indexer जिसे नेटवर्क पर अन्य Indexers द्वारा सेवा प्रदान नहीं किए जाने वाले subgraph प्रश्नों के लिए एक बैकअप के रूप में कार्य करने के लिए डिज़ाइन किया गया है। Upgrade Indexer अन्य Indexers के साथ प्रतिस्पर्धात्मक नहीं है।
 
-- **डेलीगेटर्स**: नेटवर्क प्रतिभागी जो GRT के मालिक हैं और अपने GRT को इंडेक्सर्स को सौंपते हैं। यह इंडेक्सर्स को नेटवर्क पर सबग्राफ में अपनी हिस्सेदारी बढ़ाने की अनुमति देता है। बदले में, डेलिगेटर्स को इंडेक्सिंग रिवॉर्ड्स का एक हिस्सा मिलता है जो इंडेक्सर्स को सबग्राफ प्रोसेसिंग के लिए मिलता है।
+- **Delegator**: नेटवर्क प्रतिभागी जो GRT के मालिक होते हैं और अपने GRT को Indexers को डेलीगेट करते हैं। इससे Indexers को नेटवर्क पर subgraphs में अपनी हिस्सेदारी बढ़ाने की अनुमति मिलती है। इसके बदले, Delegators को उन Indexing Rewards का एक हिस्सा मिलता है जो Indexers को subgraphs को प्रोसेस करने के लिए मिलते हैं।
 
 - **प्रत्यायोजन कर**: प्रतिनिधि द्वारा 0.5% शुल्क का भुगतान किया जाता है, जब वे अनुक्रमणकों को GRT प्रत्यायोजित करते हैं. शुल्क का भुगतान करने के लिए प्रयुक्त GRT जल गया है।
 
-- **क्यूरेटर**: नेटवर्क प्रतिभागी जो उच्च-गुणवत्ता वाले सबग्राफ की पहचान करते हैं, और क्यूरेशन शेयरों के बदले उन्हें "क्यूरेट" करते हैं (यानी, उन पर जीआरटी का संकेत देते हैं)। जब इंडेक्सर्स एक सबग्राफ पर क्वेरी फीस का दावा करते हैं, तो उस सबग्राफ के क्यूरेटर को 10% वितरित किया जाता है। इंडेक्सर्स एक सबग्राफ पर संकेत के अनुपात में इंडेक्सिंग पुरस्कार अर्जित करते हैं। हम संकेतित GRT की मात्रा और किसी सबग्राफ को अनुक्रमणित करने वाले अनुक्रमणकों की संख्या के बीच सहसंबंध देखते हैं।
+- **Curator**: नेटवर्क प्रतिभागी जो उच्च गुणवत्ता वाले subgraphs की पहचान करते हैं, और उनके लिए सिग्नल GRT प्राप्त करते हैं, जिसके बदले में उन्हें क्यूरेशन शेयर मिलते हैं। जब Indexers किसी subgraph पर क्वेरी शुल्क लेते हैं, तो उसका 10% उस subgraph के Curators को वितरित किया जाता है। GRT के सिग्नल की मात्रा और एक subgraph को इंडेक्सिंग करने वाले Indexers की संख्या के बीच एक सकारात्मक संबंध होता है।
 
 - **क्यूरेशन टैक्स**: क्यूरेटर द्वारा सबग्राफ पर GRT का संकेत देने पर 1% शुल्क का भुगतान किया जाता है। शुल्क का भुगतान करने के लिए प्रयुक्त GRT जल गया है।
 
-- **सबग्राफ उपभोक्ता**: कोई भी एप्लिकेशन या उपयोगकर्ता जो सबग्राफ पर सवाल उठाता है।
+- **डेटा उपभोक्ता**: कोई भी एप्लिकेशन या उपयोगकर्ता जो एक subgraph का क्वेरी करता है।
 
 - **सबग्राफ डेवलपर**: एक डेवलपर जो ग्राफ़ के विकेंद्रीकृत नेटवर्क के लिए एक सबग्राफ़ बनाता और तैनात करता है।
 
@@ -46,15 +44,15 @@ title: शब्दकोष
 
   1. **सक्रिय**: एक आवंटन को तब सक्रिय माना जाता है जब इसे ऑन-चेन बनाया जाता है। इसे ओपनिंग आबंटन कहा जाता है, और यह नेटवर्क को इंगित करता है कि इंडेक्सर सक्रिय रूप से अनुक्रमण कर रहा है और किसी विशेष सबग्राफ के लिए प्रश्नों की सेवा कर रहा है। सक्रिय आबंटन उप-अनुच्छेद पर संकेत के अनुपात में अनुक्रमित पुरस्कार अर्जित करते हैं, और आवंटित जीआरटी की राशि।
 
-  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+  2. **बंद**: एक Indexer एक दिए गए Subgraph पर अर्जित indexing पुरस्कारों का दावा कर सकता है, जब वह हाल का और वैध **Proof of Indexing (POI)** प्रस्तुत करता है। इसे आवंटन बंद करना कहा जाता है। एक आवंटन को बंद करने से पहले न्यूनतम एक युग के लिए खुला होना चाहिए। अधिकतम आवंटन अवधि 28 युग होती है। यदि एक Indexer 28 युगों के बाद भी आवंटन को खुला रखता है, तो इसे बासी आवंटन कहा जाता है। जब एक आवंटन **बंद** स्थिति में होता है, तो एक फिशरमैन अभी भी Indexer को झूठे डेटा की सेवा करने के लिए चुनौती देने के लिए एक विवाद खोल सकता है।
 
 - **सबग्राफ स्टूडियो**: सबग्राफ बनाने, लगाने और प्रकाशित करने के लिए एक शक्तिशाली डैप।
 
-- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed. Specifically, the Indexer will lose 2.5% of their self-stake of GRT. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+- **Fishermen**: The Graph Network में एक भूमिका, जिसे भागीदारों द्वारा निभाया जाता है, जो Indexers द्वारा प्रदान किए गए डेटा की सटीकता और अखंडता की निगरानी करते हैं। जब एक मछुआरा किसी क्वेरी प्रतिक्रिया या POI की पहचान करता है जिसे वह गलत मानता है, तो वह Indexer के खिलाफ एक विवाद शुरू कर सकता है। यदि विवाद का निर्णय मछुआरे के पक्ष में होता है, तो Indexer को 2.5% अपने स्वयं के स्टेक के नुकसान के रूप में दंडित किया जाता है। इस राशि का 50% मछुआरे को उनकी सतर्कता के लिए इनाम के रूप में दिया जाता है, और शेष 50% को परिसंचरण से हटा दिया जाता है (जलाया जाता है)। यह तंत्र मछुआरों को नेटवर्क की विश्वसनीयता बनाए रखने में मदद करने के लिए प्रोत्साहित करने के लिए डिज़ाइन किया गया है, यह सुनिश्चित करते हुए कि Indexers द्वारा प्रदान किए गए डेटा के लिए उन्हें जवाबदेह ठहराया जाए।
 
 - **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
 
-- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+- **Slashing**: Indexers अपनी स्वयं-स्टेक की GRT को गलत POI प्रदान करने या गलत डेटा सेवा देने के लिए स्लैश किया जा सकता है। स्लैशिंग प्रतिशत एक प्रोटोकॉल पैरामीटर है जिसे वर्तमान में एक Indexer's की स्वयं-स्टेक का 2.5% पर सेट किया गया है। स्लैश की गई GRT का 50% उस Fisherman को जाता है जिसने गलत डेटा या गलत POI का विवाद किया। बाकी 50% जलाया जाता है।
 
 - **इंडेक्सिंग रिवार्ड्स**: वे पुरस्कार जो इंडेक्सर्स को सबग्राफ इंडेक्स करने के लिए मिलते हैं। इंडेक्सिंग पुरस्कार जीआरटी में वितरित किए जाते हैं।
 
@@ -62,11 +60,11 @@ title: शब्दकोष
 
 - **GRT**: ग्राफ़ का कार्य उपयोगिता टोकन। जीआरटी नेटवर्क प्रतिभागियों को नेटवर्क में योगदान करने के लिए आर्थिक प्रोत्साहन प्रदान करता है।
 
-- **POI or Proof of Indexing**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent Proof of Indexing (POI). Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+- ** Proof of Indexing (POI)**: जब एक इंडेक्सर अपनी आवंटन को बंद करता है और किसी दिए गए सबग्राफ़ पर अर्जित इंडेक्सिंग पुरस्कारों का दावा करना चाहता है, तो उसे एक मान्य और हाल का POI प्रदान करना होगा। मछुआरे द्वारा इंडेक्सर द्वारा प्रदान किए गए POI का विवाद किया जा सकता है। यदि विवाद मछुआरे के पक्ष में हल होता है, तो इसका परिणाम इंडेक्सर के लिए दंडस्वरूप होगा।
 
-- **ग्राफ़ नोड**: ग्राफ़ नोड वह घटक है जो सबग्राफ़ को अनुक्रमित करता है, और परिणामी डेटा को ग्राफ़क्यूएल एपीआई के माध्यम से क्वेरी के लिए उपलब्ध कराता है। इस तरह यह इंडेक्सर स्टैक के लिए केंद्रीय है, और एक सफल इंडेक्सर चलाने के लिए ग्राफ नोड का सही संचालन महत्वपूर्ण है।
+- **ग्राफ़ नोड**: ग्राफ़ नोड वह घटक है जो सबग्राफ़ को इंडेक्स करता है और परिणामस्वरूप डेटा को GraphQL APIके माध्यम से क्वेरी के लिए उपलब्ध कराता है। इसलिए, यह Indexer स्टैक का केंद्रीय हिस्सा है, और ग्राफ़ नोड का सही संचालन एक सफल इंडेक्सर चलाने के लिए महत्वपूर्ण है।
 
-- **इंडेक्सर एजेंट**: इंडेक्सर एजेंट इंडेक्सर स्टैक का हिस्सा है। यह श्रृंखला पर अनुक्रमणिका के अन्योन्यक्रियाओं की सुविधा प्रदान करता है, जिसमें नेटवर्क पर पंजीकरण, इसके ग्राफ़ नोड(ओं) में सबग्राफ परिनियोजन प्रबंधित करना और आवंटन प्रबंधित करना शामिल है।
+- **Indexer एजेंट**: इंडेक्सर एजेंट इंडेक्सर स्टैक का हिस्सा है। यह नेटवर्क पर इंडेक्सर की इंटरैक्शन को सुगम बनाता है, जिसमें नेटवर्क पर पंजीकरण, अपने Graph Node(s) पर सबग्राफ़ तैनातियों का प्रबंधन, और आवंटनों का प्रबंधन शामिल है।
 
 - **द ग्राफ़ क्लाइंट**: विकेंद्रीकृत तरीके से ग्राफ़कॉल-आधारित डैप बनाने के लिए एक लाइब्रेरी।
 
@@ -76,12 +74,8 @@ title: शब्दकोष
 
 - **कूलडाउन अवधि**: वह समय जब तक कोई अनुक्रमणिका अपने प्रतिनिधिमंडल पैरामीटर को बदल नहीं सकता, तब तक वह फिर से ऐसा कर सकता है।
 
-- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self stake.
-
-- **_Upgrading_ a subgraph to The Graph Network**: The process of moving a subgraph from the hosted service to The Graph Network.
+- **L2 ट्रांसफर टूल्स**: स्मार्ट कॉन्ट्रैक्ट और UI जो नेटवर्क प्रतिभागियों को Ethereum मेननेट से Arbitrum One में नेटवर्क से संबंधित संपत्तियों को स्थानांतरित करने में सक्षम बनाते हैं। नेटवर्क प्रतिभागी डेलिगेटेड GRT, subgraphs, क्यूरेशन शेयर और Indexer's self-stake को ट्रांसफर कर सकते हैं।
 
-- **_Updating_ a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+- **Subgraph को अपडेट करना**: Subgraph के मैनिफेस्ट, स्कीमा, या मैपिंग्स में अपडेट के साथ एक नए subgraph's manifest को जारी करने की प्रक्रिया।
 
 - **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).
-
-- **Upgrade Window**: The countdown for hosted service users to upgrade their subgraph(s) to The Graph Network beginning on April 11th, and ending on June 12th 2024.

From cff3b7fd84444d0ccfc79efb2babdb4fcd49ce32 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:17 -0500
Subject: [PATCH 1013/1325] New translations glossary.mdx (Swahili)

---
 website/pages/sw/glossary.mdx | 81 +++++++++++++++++++++++++++++++++++
 1 file changed, 81 insertions(+)
 create mode 100644 website/pages/sw/glossary.mdx

diff --git a/website/pages/sw/glossary.mdx b/website/pages/sw/glossary.mdx
new file mode 100644
index 000000000000..bdeff7281023
--- /dev/null
+++ b/website/pages/sw/glossary.mdx
@@ -0,0 +1,81 @@
+---
+title: Glossary
+---
+
+- **The Graph**: A decentralized protocol for indexing and querying data.
+
+- **Query**: A request for data. In the case of The Graph, a query is a request for data from a subgraph that will be answered by an Indexer.
+
+- **GraphQL**: A query language for APIs and a runtime for fulfilling those queries with your existing data. The Graph uses GraphQL to query subgraphs.
+
+- **Endpoint**: A URL that can be used to query a subgraph. The testing endpoint for Subgraph Studio is `https://api.studio.thegraph.com/query/<ID>/<SUBGRAPH_NAME>/<VERSION>` and the Graph Explorer endpoint is `https://gateway.thegraph.com/api/<API_KEY>/subgraphs/id/<SUBGRAPH_ID>`. The Graph Explorer endpoint is used to query subgraphs on The Graph's decentralized network.
+
+- **Subgraph**: An open API that extracts data from a blockchain, processes it, and stores it so that it can be easily queried via GraphQL. Developers can build, deploy, and publish subgraphs to The Graph Network. Once it is indexed, the subgraph can be queried by anyone.
+
+- **Indexer**: Network participants that run indexing nodes to index data from blockchains and serve GraphQL queries.
+
+- **Indexer Revenue Streams**: Indexers are rewarded in GRT with two components: query fee rebates and indexing rewards.
+
+  1. **Query Fee Rebates**: Payments from subgraph consumers for serving queries on the network.
+
+  2. **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are generated via new issuance of 3% GRT annually.
+
+- **Indexer's Self-Stake**: The amount of GRT that Indexers stake to participate in the decentralized network. The minimum is 100,000 GRT, and there is no upper limit.
+
+- **Upgrade Indexer**: An Indexer designed to act as a fallback for subgraph queries not serviced by other Indexers on the network. The upgrade Indexer is not competitive with other Indexers.
+
+- **Delegator**: Network participants who own GRT and delegate their GRT to Indexers. This allows Indexers to increase their stake in subgraphs on the network. In return, Delegators receive a portion of the Indexing Rewards that Indexers receive for processing subgraphs.
+
+- **Delegation Tax**: A 0.5% fee paid by Delegators when they delegate GRT to Indexers. The GRT used to pay the fee is burned.
+
+- **Curator**: Network participants that identify high-quality subgraphs, and signal GRT on them in exchange for curation shares. When Indexers claim query fees on a subgraph, 10% is distributed to the Curators of that subgraph. There is a positive correlation between the amount of GRT signaled and the number of Indexers indexing a subgraph.
+
+- **Curation Tax**: A 1% fee paid by Curators when they signal GRT on subgraphs. The GRT used to pay the fee is burned.
+
+- **Data Consumer**: Any application or user that queries a subgraph.
+
+- **Subgraph Developer**: A developer who builds and deploys a subgraph to The Graph's decentralized network.
+
+- **Subgraph Manifest**: A YAML file that describes the subgraph's GraphQL schema, data sources, and other metadata. [Here](https://github.com/graphprotocol/example-subgraph/blob/master/subgraph.yaml) is an example.
+
+- **Epoch**: A unit of time within the network. Currently, one epoch is 6,646 blocks or approximately 1 day.
+
+- **Allocation**: An Indexer can allocate their total GRT stake (including Delegators' stake) towards subgraphs that have been published on The Graph's decentralized network. Allocations can have different statuses:
+
+  1. **Active**: An allocation is considered active when it is created on-chain. This is called opening an allocation, and indicates to the network that the Indexer is actively indexing and serving queries for a particular subgraph. Active allocations accrue indexing rewards proportional to the signal on the subgraph, and the amount of GRT allocated.
+
+  2. **Closed**: An Indexer may claim the accrued indexing rewards on a given subgraph by submitting a recent, and valid, Proof of Indexing (POI). This is known as closing an allocation. An allocation must have been open for a minimum of one epoch before it can be closed. The maximum allocation period is 28 epochs. If an Indexer leaves an allocation open beyond 28 epochs, it is known as a stale allocation. When an allocation is in the **Closed** state, a Fisherman can still open a dispute to challenge an Indexer for serving false data.
+
+- **Subgraph Studio**: A powerful dapp for building, deploying, and publishing subgraphs.
+
+- **Fishermen**: A role within The Graph Network held by participants who monitor the accuracy and integrity of data served by Indexers. When a Fisherman identifies a query response or a POI they believe to be incorrect, they can initiate a dispute against the Indexer. If the dispute rules in favor of the Fisherman, the Indexer is slashed by losing 2.5% of their self-stake. Of this amount, 50% is awarded to the Fisherman as a bounty for their vigilance, and the remaining 50% is removed from circulation (burned). This mechanism is designed to encourage Fishermen to help maintain the reliability of the network by ensuring that Indexers are held accountable for the data they provide.
+
+- **Arbitrators**: Arbitrators are network participants appointed through a governance process. The role of the Arbitrator is to decide the outcome of indexing and query disputes. Their goal is to maximize the utility and reliability of The Graph Network.
+
+- **Slashing**: Indexers can have their self-staked GRT slashed for providing an incorrect POI or for serving inaccurate data. The slashing percentage is a protocol parameter currently set to 2.5% of an Indexer's self-stake. 50% of the slashed GRT goes to the Fisherman that disputed the inaccurate data or incorrect POI. The other 50% is burned.
+
+- **Indexing Rewards**: The rewards that Indexers receive for indexing subgraphs. Indexing rewards are distributed in GRT.
+
+- **Delegation Rewards**: The rewards that Delegators receive for delegating GRT to Indexers. Delegation rewards are distributed in GRT.
+
+- **GRT**: The Graph's work utility token. GRT provides economic incentives to network participants for contributing to the network.
+
+- **Proof of Indexing (POI)**: When an Indexer closes their allocation and wants to claim their accrued indexing rewards on a given subgraph, they must provide a valid and recent POI. Fishermen may dispute the POI provided by an Indexer. A dispute resolved in the Fisherman's favor will result in slashing of the Indexer.
+
+- **Graph Node**: Graph Node is the component that indexes subgraphs and makes the resulting data available to query via a GraphQL API. As such it is central to the Indexer stack, and correct operation of Graph Node is crucial to running a successful Indexer.
+
+- **Indexer agent**: The Indexer agent is part of the Indexer stack. It facilitates the Indexer's interactions on-chain, including registering on the network, managing subgraph deployments to its Graph Node(s), and managing allocations.
+
+- **The Graph Client**: A library for building GraphQL-based dapps in a decentralized way.
+
+- **Graph Explorer**: A dapp designed for network participants to explore subgraphs and interact with the protocol.
+
+- **Graph CLI**: A command line interface tool for building and deploying to The Graph.
+
+- **Cooldown Period**: The time remaining until an Indexer who changed their delegation parameters can do so again.
+
+- **L2 Transfer Tools**: Smart contracts and UI that enable network participants to transfer network related assets from Ethereum mainnet to Arbitrum One. Network participants can transfer delegated GRT, subgraphs, curation shares, and Indexer's self-stake.
+
+- **Updating a subgraph**: The process of releasing a new subgraph version with updates to the subgraph's manifest, schema, or mappings.
+
+- **Migrating**: The process of curation shares moving from an old version of a subgraph to a new version of a subgraph (e.g. when v0.0.1 is updated to v0.0.2).

From c2d03495c0db92f38b2d1fa7af3c9a62960032b3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:18 -0500
Subject: [PATCH 1014/1325] New translations subgraph-uncrashable.mdx
 (Romanian)

---
 website/pages/ro/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ro/cookbook/subgraph-uncrashable.mdx b/website/pages/ro/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/ro/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/ro/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From 159f29957ba29ccf08738eab2a2e3833cc7388e9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:19 -0500
Subject: [PATCH 1015/1325] New translations subgraph-uncrashable.mdx (Spanish)

---
 website/pages/es/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/es/cookbook/subgraph-uncrashable.mdx b/website/pages/es/cookbook/subgraph-uncrashable.mdx
index d6ab2b8a0878..d7a39a67df81 100644
--- a/website/pages/es/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/es/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Generador de código de subgrafo seguro
 
 - El marco también incluye una forma (a través del archivo de configuración) para crear funciones de establecimiento personalizadas, pero seguras, para grupos de variables de entidad. De esta forma, es imposible que el usuario cargue/utilice una entidad gráfica obsoleta y también es imposible olvidarse de guardar o configurar una variable requerida por la función.
 
-- Los registros de advertencia se registran como registros que indican donde hay una infracción de la lógica del subgrafo para ayudar a solucionar el problema y garantizar la precisión de los datos. Estos registros se pueden ver en el servicio alojado de The Graph en la sección 'Registros'.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable se puede ejecutar como un indicador opcional mediante el comando codegen Graph CLI.
 

From ed6b11a6f85137af42a0f674a21da7a5af5b1615 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:20 -0500
Subject: [PATCH 1016/1325] New translations subgraph-uncrashable.mdx (Arabic)

---
 website/pages/ar/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ar/cookbook/subgraph-uncrashable.mdx b/website/pages/ar/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/ar/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/ar/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From 1a40377efab6818d951fd73027888ad653b89507 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:21 -0500
Subject: [PATCH 1017/1325] New translations subgraph-uncrashable.mdx (Czech)

---
 website/pages/cs/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/cs/cookbook/subgraph-uncrashable.mdx b/website/pages/cs/cookbook/subgraph-uncrashable.mdx
index 1c2b3d9e4dad..13c979d18853 100644
--- a/website/pages/cs/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/cs/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Generátor kódu bezpečného podgrafu
 
 - Framework také obsahuje způsob (prostřednictvím konfiguračního souboru), jak vytvořit vlastní, ale bezpečné funkce setteru pro skupiny proměnných entit. Tímto způsobem není možné, aby uživatel načetl/použil zastaralou entitu grafu, a také není možné zapomenout uložit nebo nastavit proměnnou, kterou funkce vyžaduje.
 
-- Varovné protokoly se zaznamenávají jako protokoly označující místa, kde došlo k porušení logiky podgrafu, aby bylo možné problém opravit a zajistit přesnost dat. Tyto protokoly lze zobrazit v hostované službě The Graph v části 'Logs' sekce.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Podgraf Uncrashable lze spustit jako volitelný příznak pomocí příkazu Graph CLI codegen.
 

From 94d7bb9d9a9f1f2829b9f8a6b6e86801d475aa38 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:22 -0500
Subject: [PATCH 1018/1325] New translations subgraph-uncrashable.mdx (German)

---
 website/pages/de/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/de/cookbook/subgraph-uncrashable.mdx b/website/pages/de/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/de/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/de/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From d5645730215a325a336b1be7369cbb5001d2a55e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:23 -0500
Subject: [PATCH 1019/1325] New translations subgraph-uncrashable.mdx (Italian)

---
 website/pages/it/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/it/cookbook/subgraph-uncrashable.mdx b/website/pages/it/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/it/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/it/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From d543afa4ece257565410f4581cbad9ffd28c1d37 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:24 -0500
Subject: [PATCH 1020/1325] New translations subgraph-uncrashable.mdx
 (Japanese)

---
 website/pages/ja/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ja/cookbook/subgraph-uncrashable.mdx b/website/pages/ja/cookbook/subgraph-uncrashable.mdx
index f50944b02a9c..97d6d7fb8fe4 100644
--- a/website/pages/ja/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/ja/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: 安全なサブグラフのコード生成
 
 - また、このフレームワークには、エンティティ変数のグループに対して、カスタムだが安全なセッター関数を作成する方法が（設定ファイルを通じて）含まれています。この方法では、ユーザーが古いグラフ・エンティティをロード/使用することは不可能であり、また、関数が必要とする変数の保存や設定を忘れることも不可能です。
 
-- 警告ログは、サブグラフのロジックに違反がある場所を示すログとして記録され、データの正確性を確保するための問題の修正に役立ちます。これらのログは、The Graphのホスティングサービスの「Logs」セクションで確認することができます。
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashableは、Graph CLI codegenコマンドでオプションのフラグとして実行することができます。
 

From b09312a12daa8c978e31b3728f080e7dd58dfb96 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:25 -0500
Subject: [PATCH 1021/1325] New translations subgraph-uncrashable.mdx (Korean)

---
 website/pages/ko/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ko/cookbook/subgraph-uncrashable.mdx b/website/pages/ko/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/ko/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/ko/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From f69afa8426e26d5ea638a6b72674d5f476866915 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:26 -0500
Subject: [PATCH 1022/1325] New translations subgraph-uncrashable.mdx (Dutch)

---
 website/pages/nl/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/nl/cookbook/subgraph-uncrashable.mdx b/website/pages/nl/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/nl/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/nl/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From 9bf8d8f12730f951c6054187d223266ce9cbf19d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:27 -0500
Subject: [PATCH 1023/1325] New translations subgraph-uncrashable.mdx (Polish)

---
 website/pages/pl/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pl/cookbook/subgraph-uncrashable.mdx b/website/pages/pl/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/pl/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/pl/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From a0e7b3f045e5d33dc7145531656b393507929061 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:28 -0500
Subject: [PATCH 1024/1325] New translations subgraph-uncrashable.mdx
 (Portuguese)

---
 website/pages/pt/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pt/cookbook/subgraph-uncrashable.mdx b/website/pages/pt/cookbook/subgraph-uncrashable.mdx
index 4ffce19ebc87..19defed68524 100644
--- a/website/pages/pt/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/pt/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ O [Subgraph Uncrashable](https://float-capital.github.io/float-subgraph-uncrasha
 
 - A estrutura também inclui uma maneira (através do arquivo de configuração) de criar funções personalizadas, mas seguras, para configurar grupos de variáveis de entidade. Desta maneira, é impossível que o utilizador carregue/use uma entidade de graph obsoleta, e também é impossível esquecer de salvar ou determinar uma variável exigida pela função.
 
-- Logs de aviso são gravados como logs que indicam onde há uma brecha na lógica do subgraph para ajudar a solucionar o problema e garantir a precisão dos dados. Estes logs podem ser visualizados no serviço hospedado do The Graph, na seção 'Logs'.
+- Logs de aviso são registrados como logs que indicam onde há uma quebra de lógica no subgraph, para ajudar a consertar o problema e garantir a segurança dos dados.
 
 A Subgraph Uncrashable pode ser executada como flag opcional usando o comando codegen no Graph CLI.
 

From d7d5a6893fc473aacbfc3cb18ac55eb0e68407f4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:29 -0500
Subject: [PATCH 1025/1325] New translations subgraph-uncrashable.mdx (Swedish)

---
 website/pages/sv/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/sv/cookbook/subgraph-uncrashable.mdx b/website/pages/sv/cookbook/subgraph-uncrashable.mdx
index e6ef7ed8cc76..c77c02c2bee6 100644
--- a/website/pages/sv/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/sv/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Säker subgraf kodgenerator
 
 - Ramverket innehåller också ett sätt (via konfigurationsfilen) att skapa anpassade, men säkra, sätterfunktioner för grupper av entitetsvariabler. På så sätt är det omöjligt för användaren att ladda/använda en inaktuell grafenhet och det är också omöjligt att glömma att spara eller ställa in en variabel som krävs av funktionen.
 
-- Varningsloggar registreras som loggar som indikerar var det finns ett brott mot subgraf logik för att hjälpa till att korrigera problemet för att säkerställa datanoggrannhet. Dessa loggar kan ses i The Graphs värdtjänst under avsnittet "Loggar".
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable kan köras som en valfri flagga med kommandot Graph CLI codegen.
 

From 7264daecbd340df0e955a50e754cdacb757a951a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:31 -0500
Subject: [PATCH 1026/1325] New translations subgraph-uncrashable.mdx (Turkish)

---
 website/pages/tr/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/tr/cookbook/subgraph-uncrashable.mdx b/website/pages/tr/cookbook/subgraph-uncrashable.mdx
index 015a2720bb6a..fedae7827357 100644
--- a/website/pages/tr/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/tr/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Güvenli Subgraph Kod Oluşturucu
 
 - Framework ayrıca unsur değişkenleri grupları için özel, ancak güvenli ayarlayıcı fonksiyonları oluşturmanın bir yolunu (yapılandırma dosyası aracılığıyla) içerir. Bu sayede, kullanıcının eski bir graph unsurunu yüklemesi/kullanması ve ayrıca fonksiyonun gerektirdiği bir değişkeni kaydetmeyi veya ayarlamayı unutması imkansız hale gelir.
 
-- Uyarı kayıtları, subgraph mantığında bir ihlal olduğunda veri doğruluğunu sağlamak amacıyla sorunu düzeltmek için kullanılabilecek kayıtlar olarak kaydedilir. Bu kayıtlar, Graph'ın barındırılan hizmetinde 'Kayıtlar' bölümünde görüntülenebilir.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable, Graph CLI codegen komutu kullanılarak isteğe bağlı bir bayrak olarak çalıştırılabilir.
 

From 1f87ae44b284876eb17dccd3469dd0e9d1d31923 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:32 -0500
Subject: [PATCH 1027/1325] New translations subgraph-uncrashable.mdx
 (Ukrainian)

---
 website/pages/uk/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/uk/cookbook/subgraph-uncrashable.mdx b/website/pages/uk/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/uk/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/uk/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From f278fc72533ba92e6dba71e3f4799e0aa7aab320 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:33 -0500
Subject: [PATCH 1028/1325] New translations subgraph-uncrashable.mdx (Chinese
 Simplified)

---
 website/pages/zh/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/cookbook/subgraph-uncrashable.mdx b/website/pages/zh/cookbook/subgraph-uncrashable.mdx
index b0c1d6607410..5726f6409b80 100644
--- a/website/pages/zh/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/zh/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: 安全子图代码生成器
 
 - 该框架还包括一种方法(通过配置文件) 为实体变量组创建自定义但安全的 setter 函数。这样，用户就不可能加载/使用过时的图形实体，也不可能忘记保存或设置函数所需的变量。
 
-- 警告日志被记录为日志，指示哪里存在子图逻辑中断以帮助修补问题，从而确保数据的准确性。这些日志可以在 Graph 的托管服务中的“ Logs”部分中查看。
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 使用 Graph CLI codegen 命令，Subgraph Uncrashable 可以作为一个可选标志运行。
 

From f48abe98e6f813521c4ba07abdc725b6412cd1b9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:34 -0500
Subject: [PATCH 1029/1325] New translations subgraph-uncrashable.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ur/cookbook/subgraph-uncrashable.mdx b/website/pages/ur/cookbook/subgraph-uncrashable.mdx
index 0de9d6fa3a55..3bea4e892699 100644
--- a/website/pages/ur/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/ur/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: محفوظ سب گراف کوڈ جنریٹر
 
 - فریم ورک میں ہستی متغیرات کے گروپس کے لیے حسب ضرورت، لیکن محفوظ، سیٹر فنکشنز بنانے کا ایک طریقہ (کنفگ فائل کے ذریعے) بھی شامل ہے۔ اس طرح صارف کے لیے کسی باسی گراف ہستی کو لوڈ/استعمال کرنا ناممکن ہے اور فنکشن کے لیے مطلوبہ متغیر کو محفوظ کرنا یا سیٹ کرنا بھولنا بھی ناممکن ہے.
 
-- انتباہی لاگز کو لاگز کے طور پر ریکارڈ کیا جاتا ہے جو اس بات کی نشاندہی کرتے ہیں کہ ڈیٹا کی درستگی کو یقینی بنانے کے لیے مسئلے کو پیچ کرنے میں مدد کے لیے سب گراف کی منطق کی خلاف ورزی کہاں ہے۔ یہ لاگز 'لاگز' سیکشن کے تحت گراف کی میزبانی کی ہوسٹڈ میں دیکھے جا سکتے ہیں.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 گراف CLI کوڈجن کمانڈ کا استعمال کرتے ہوئے سب گراف ان کریش ایبل کو اختیاری پرچم کے طور پر چلایا جا سکتا ہے.
 

From 6bdbe0ca8fbc17791cd88a156cbee7810da54dd2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:35 -0500
Subject: [PATCH 1030/1325] New translations subgraph-uncrashable.mdx
 (Vietnamese)

---
 website/pages/vi/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/vi/cookbook/subgraph-uncrashable.mdx b/website/pages/vi/cookbook/subgraph-uncrashable.mdx
index 989310a3f9a0..0cc91a0fa2c3 100644
--- a/website/pages/vi/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/vi/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: Safe Subgraph Code Generator
 
 - The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
 
-- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy. These logs can be viewed in the The Graph's hosted service under the 'Logs' section.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
 

From a8b80b0c69ce7e4bbab4b65114ebd9130a10557d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:36 -0500
Subject: [PATCH 1031/1325] New translations subgraph-uncrashable.mdx (Marathi)

---
 website/pages/mr/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/mr/cookbook/subgraph-uncrashable.mdx b/website/pages/mr/cookbook/subgraph-uncrashable.mdx
index ed44a80b316f..1b8e106d4b03 100644
--- a/website/pages/mr/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/mr/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: सुरक्षित सबग्राफ कोड जनरेट
 
 - फ्रेमवर्कमध्ये एंटिटी व्हेरिएबल्सच्या गटांसाठी सानुकूल, परंतु सुरक्षित, सेटर फंक्शन्स तयार करण्याचा मार्ग (कॉन्फिग फाइलद्वारे) देखील समाविष्ट आहे. अशा प्रकारे वापरकर्त्याला जुना आलेख घटक लोड करणे/वापरणे अशक्य आहे आणि फंक्शनसाठी आवश्यक असलेले व्हेरिएबल सेव्ह करणे किंवा सेट करणे विसरणे देखील अशक्य आहे.
 
-- डेटा अचूकता सुनिश्चित करण्यासाठी समस्या पॅच करण्यात मदत करण्यासाठी सबग्राफ लॉजिकचे उल्लंघन कोठे आहे हे दर्शविणारे लॉग म्हणून चेतावणी लॉग रेकॉर्ड केले जातात. हे लॉग 'लॉग' विभागांतर्गत ग्राफच्या होस्ट केलेल्या सेवेमध्ये पाहिले जाऊ शकतात.
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
 
 ग्राफ CLI codegen कमांड वापरून Subgraph Uncrashable हा पर्यायी ध्वज म्हणून चालवला जाऊ शकतो.
 

From 364c1f9a610adc735a8bbec34bda73955ba21332 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:37 -0500
Subject: [PATCH 1032/1325] New translations subgraph-uncrashable.mdx (Hindi)

---
 website/pages/hi/cookbook/subgraph-uncrashable.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/cookbook/subgraph-uncrashable.mdx b/website/pages/hi/cookbook/subgraph-uncrashable.mdx
index 7038a99ce5ce..5c28f6161087 100644
--- a/website/pages/hi/cookbook/subgraph-uncrashable.mdx
+++ b/website/pages/hi/cookbook/subgraph-uncrashable.mdx
@@ -18,7 +18,7 @@ title: सुरक्षित सबग्राफ कोड जेनरे
 
 - फ्रेमवर्क में इकाई वैरिएबल के समूहों के लिए कस्टम, लेकिन सुरक्षित, सेटर फ़ंक्शन बनाने का एक तरीका (कॉन्फिग फ़ाइल के माध्यम से) भी शामिल है। इस तरह उपयोगकर्ता के लिए एक पुरानी ग्राफ़ इकाई को लोड/उपयोग करना असंभव है और फ़ंक्शन द्वारा आवश्यक वैरिएबल को सहेजना या सेट करना भूलना भी असंभव है।
 
-- चेतावनी लॉग्स लॉग्स के रूप में रिकॉर्ड किए जाते हैं जो इंगित करते हैं कि डेटा सटीकता सुनिश्चित करने के लिए समस्या को ठीक करने में मदद करने के लिए सबग्राफ लॉजिक का उल्लंघन कहां हुआ है। इन लॉग्स को 'लॉग्स' सेक्शन के तहत द ग्राफ की होस्टेड सेवा में देखा जा सकता है।
+- चेतावनी लॉग को लॉग के रूप में रिकॉर्ड किया जाता है, जो यह इंगित करता है कि Subgraph लॉजिक में कहां उल्लंघन हो रहा है, ताकि समस्या को ठीक किया जा सके और डेटा की सटीकता सुनिश्चित हो सके।
 
 सबग्राफ अनक्रैशेबल को ग्राफ़ CLI codegen कमांड का उपयोग करके एक वैकल्पिक फ़्लैग के रूप में चलाया जा सकता है।
 

From da2f3c3fb8dcca16268b654a20c83973e15189ba Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:38 -0500
Subject: [PATCH 1033/1325] New translations subgraph-uncrashable.mdx (Swahili)

---
 .../sw/cookbook/subgraph-uncrashable.mdx      | 29 +++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 website/pages/sw/cookbook/subgraph-uncrashable.mdx

diff --git a/website/pages/sw/cookbook/subgraph-uncrashable.mdx b/website/pages/sw/cookbook/subgraph-uncrashable.mdx
new file mode 100644
index 000000000000..0cc91a0fa2c3
--- /dev/null
+++ b/website/pages/sw/cookbook/subgraph-uncrashable.mdx
@@ -0,0 +1,29 @@
+---
+title: Safe Subgraph Code Generator
+---
+
+[Subgraph Uncrashable](https://float-capital.github.io/float-subgraph-uncrashable/) is a code generation tool that generates a set of helper functions from the graphql schema of a project. It ensures that all interactions with entities in your subgraph are completely safe and consistent.
+
+## Why integrate with Subgraph Uncrashable?
+
+- **Continuous Uptime**. Mishandled entities may cause subgraphs to crash, which can be disruptive for projects that are dependent on The Graph. Set up helper functions to make your subgraphs “uncrashable” and ensure business continuity.
+
+- **Completely Safe**. Common problems seen in subgraph development are issues of loading undefined entities, not setting or initializing all values of entities, and race conditions on loading and saving entities. Ensure all interactions with entities are completely atomic.
+
+- **User Configurable** Set default values and configure the level of security checks that suits your individual project's needs. Warning logs are recorded indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
+
+**Key Features**
+
+- The code generation tool accommodates **all** subgraph types and is configurable for users to set sane defaults on values. The code generation will use this config to generate helper functions that are to the users specification.
+
+- The framework also includes a way (via the config file) to create custom, but safe, setter functions for groups of entity variables. This way it is impossible for the user to load/use a stale graph entity and it is also impossible to forget to save or set a variable that is required by the function.
+
+- Warning logs are recorded as logs indicating where there is a breach of subgraph logic to help patch the issue to ensure data accuracy.
+
+Subgraph Uncrashable can be run as an optional flag using the Graph CLI codegen command.
+
+```sh
+graph codegen -u [options] [<subgraph-manifest>]
+```
+
+Visit the [subgraph uncrashable documentation](https://float-capital.github.io/float-subgraph-uncrashable/docs/) or watch this [video tutorial](https://float-capital.github.io/float-subgraph-uncrashable/docs/tutorial) to learn more and to get started with developing safer subgraphs.

From dc7285e7860b4b4739abc1ac6f8ffb2bd3bd8f40 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:49 -0500
Subject: [PATCH 1034/1325] New translations graphcast.mdx (Swahili)

---
 website/pages/sw/graphcast.mdx | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)
 create mode 100644 website/pages/sw/graphcast.mdx

diff --git a/website/pages/sw/graphcast.mdx b/website/pages/sw/graphcast.mdx
new file mode 100644
index 000000000000..4072877a1257
--- /dev/null
+++ b/website/pages/sw/graphcast.mdx
@@ -0,0 +1,21 @@
+---
+title: Graphcast
+---
+
+## Introduction
+
+Is there something you'd like to learn from or share with your fellow Indexers in an automated manner, but it's too much hassle or costs too much gas?
+
+Currently, the cost to broadcast information to other network participants is determined by gas fees on the Ethereum blockchain. Graphcast solves this problem by acting as an optional decentralized, distributed peer-to-peer (P2P) communication tool that allows Indexers across the network to exchange information in real time. The cost of exchanging P2P messages is near zero, with the tradeoff of no data integrity guarantees. Nevertheless, Graphcast aims to provide message validity guarantees (i.e. that the message is valid and signed by a known protocol participant) with an open design space of reputation models.
+
+The Graphcast SDK (Software Development Kit) allows developers to build Radios, which are gossip-powered applications that Indexers can run to serve a given purpose. We also intend to create a few Radios (or provide support to other developers/teams that wish to build Radios) for the following use cases:
+
+- Real-time cross-checking of subgraph data integrity ([Subgraph Radio](https://docs.graphops.xyz/graphcast/radios/subgraph-radio/intro)).
+- Conducting auctions and coordination for warp syncing subgraphs, substreams, and Firehose data from other Indexers.
+- Self-reporting on active query analytics, including subgraph request volumes, fee volumes, etc.
+- Self-reporting on indexing analytics, including subgraph indexing time, handler gas costs, indexing errors encountered, etc.
+- Self-reporting on stack information including graph-node version, Postgres version, Ethereum client version, etc.
+
+### Learn More
+
+If you would like to learn more about Graphcast, [check out the documentation here.](https://docs.graphops.xyz/graphcast/intro)

From c7cba0a8291f3d17665696e2655e8a84841172c8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:51 -0500
Subject: [PATCH 1035/1325] New translations
 graphql-validations-migration-guide.mdx (French)

---
 .../release-notes/graphql-validations-migration-guide.mdx   | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx b/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx
index 62e5435c0fc3..567231e0bedf 100644
--- a/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx
@@ -103,7 +103,7 @@ query myData {
 }
 
 query myData2 {
-  # renommer la deuxième requête
+   # renommer la deuxième requête
   name
 }
 ```
@@ -158,7 +158,7 @@ _Solution:_
 
 ```graphql
 query myData($id: String) {
-  # conserver la variable pertinente (ici : `$id: String`)
+   # conserver la variable pertinente (ici : `$id: String`)
   id
   ...MyFields
 }
@@ -259,7 +259,7 @@ query {
 
 ```graphql
 # Différents arguments peuvent conduire à des données différentes,
-# donc nous ne pouvons pas supposer que les champs seront les mêmes.
+# donc nous ne pouvons pas supposer que les champs seront les mêmes. 
 query {
   dogs {
     doesKnowCommand(dogCommand: SIT)

From 4ed9194c22a87008717378edcb1e912eddd78257 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:52 -0500
Subject: [PATCH 1036/1325] New translations
 graphql-validations-migration-guide.mdx (Spanish)

---
 .../es/release-notes/graphql-validations-migration-guide.mdx     | 1 +
 1 file changed, 1 insertion(+)

diff --git a/website/pages/es/release-notes/graphql-validations-migration-guide.mdx b/website/pages/es/release-notes/graphql-validations-migration-guide.mdx
index 55801738ddca..292c60a70cf9 100644
--- a/website/pages/es/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/es/release-notes/graphql-validations-migration-guide.mdx
@@ -406,6 +406,7 @@ query {
   user {
     id
     image # 'image' requiere un conjunto de selección para subcampos!
+
   }
 }
 ```

From 9c90f1b63868a8d02973579a88e3670361b37645 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:55 -0500
Subject: [PATCH 1037/1325] New translations
 graphql-validations-migration-guide.mdx (Japanese)

---
 .../ja/release-notes/graphql-validations-migration-guide.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx
index b004e14d9f98..9a8bcf34625f 100644
--- a/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx
@@ -521,7 +521,7 @@ query {
 }
 ```
 
-\_注: `@stream`、`@live`、`@defer` はサポートされていません。
+_注: `@stream`、`@live`、`@defer` はサポートされていません。
 
 **ディレクティブは、この場所で 1 回だけ使用できます (#UniqueDirectivesPerLocationRule)**
 

From bcc24ccd8dab872690397094d693d1cbc1faf26e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:58 -0500
Subject: [PATCH 1038/1325] New translations
 graphql-validations-migration-guide.mdx (Portuguese)

---
 .../graphql-validations-migration-guide.mdx         | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx b/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx
index 7b94db58a11d..75c8799b9286 100644
--- a/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx
@@ -256,7 +256,8 @@ query {
 }
 ```
 
-**Conflicting fields with arguments (#OverlappingFieldsCanBeMergedRule)** (Campos em conflito com argumentos)
+**Conflicting fields with arguments (#OverlappingFieldsCanBeMergedRule)**
+(Campos em conflito com argumentos)
 
 ```graphql
 # Argumentos diferentes podem levar a dados diferentes,
@@ -465,10 +466,10 @@ Estas referências desconhecidas devem ser consertadas:
 - caso contrário, remova
 
 ### Fragment: invalid spread or definition
-
 (Fragment: espalhamento ou definição inválidos)
 
-**Invalid Fragment spread (#PossibleFragmentSpreadsRule)** (Espalhamento de fragment inválido)
+**Invalid Fragment spread (#PossibleFragmentSpreadsRule)**
+(Espalhamento de fragment inválido)
 
 Um Fragment não pode ser espalhado em um tipo não aplicável.
 
@@ -508,7 +509,8 @@ fragment inlineFragOnScalar on Dog {
 
 ### Uso de Diretivas
 
-**Directive cannot be used at this location (#KnownDirectivesRule)** (A diretiva não pode ser usada neste local)
+**Directive cannot be used at this location (#KnownDirectivesRule)**
+(A diretiva não pode ser usada neste local)
 
 Apenas diretivas GraphQL (`@...`) apoiadas pela API do The Graph podem ser usadas.
 
@@ -525,7 +527,8 @@ query {
 
 _Nota: `@stream`, `@live`, e `@defer` não têm apoio._
 
-**Directive can only be used once at this location (#UniqueDirectivesPerLocationRule)** (A diretiva só pode ser usada neste local uma vez)
+**Directive can only be used once at this location (#UniqueDirectivesPerLocationRule)**
+(A diretiva só pode ser usada neste local uma vez)
 
 As diretivas apoiadas pelo The Graph só podem ser usadas uma vez por local.
 

From a3856fff5c10d8728f3bb0e321198965571d2470 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:51:59 -0500
Subject: [PATCH 1039/1325] New translations
 graphql-validations-migration-guide.mdx (Russian)

---
 .../graphql-validations-migration-guide.mdx            | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx
index b7cb792259b3..25238b858a50 100644
--- a/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx
@@ -284,8 +284,8 @@ query {
 
 ```graphql
 query {
-  # В конце концов, у нас есть два определения "x", указывающие
-  # на разные поля!
+ # В конце концов, у нас есть два определения "x", указывающие
+ # на разные поля!
   ...A
   ...B
 }
@@ -437,7 +437,7 @@ query {
 ```graphql
 query purposes {
   # Если в схеме "name" определено как "String",
-  # этот запрос не пройдёт валидацию.
+   # этот запрос не пройдёт валидацию.
   purpose(name: 1) {
     id
   }
@@ -447,8 +447,8 @@ query purposes {
 
 query purposes($name: Int!) {
   # Если "name" определено в схеме как `String`,
-  # этот запрос не пройдёт валидацию, потому что
-  # используемая переменная имеет тип `Int`
+   # этот запрос не пройдёт валидацию, потому что
+   # используемая переменная имеет тип `Int`
   purpose(name: $name) {
     id
   }

From 38746656f6a708945a3e9625834fd5603eeee21c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:02 -0500
Subject: [PATCH 1040/1325] New translations
 graphql-validations-migration-guide.mdx (Chinese Simplified)

---
 .../zh/release-notes/graphql-validations-migration-guide.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx b/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx
index bdd11ecfbb29..6316302a7142 100644
--- a/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx
@@ -62,7 +62,7 @@ npx@graphql验证/cli-shttps://api-npx @graphql-validate/cli -s https://api-next
 
 或者
 
-- `https://api-next.thegraph.com/subgraphs/name`\<GITHUB_USER>/\<SUBGRAPH_NAME>
+- `https://api-next.thegraph.com/subgraphs/name`<GITHUB_USER>/<SUBGRAPH_NAME>
 
 要处理标记为存在验证错误的查询，可以使用您最喜欢的GraphQL查询工具，如Altair或[GraphiQL](https://cloud.hasura.io/public/graphiql)，然后尝试您的查询。这些工具还会在用户界面中标记这些错误，甚至在您运行之前。
 

From 347eef8e352825a7f9c9b32097c696afa83d9b65 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:03 -0500
Subject: [PATCH 1041/1325] New translations
 graphql-validations-migration-guide.mdx (Urdu (Pakistan))

---
 .../ur/release-notes/graphql-validations-migration-guide.mdx   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx
index fba78a067915..3d1289e29dd2 100644
--- a/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx
@@ -4,7 +4,8 @@ title: GraphQL کی توثیق کی منتقلی گائیڈ
 
 جلد ہی `گراف نوڈ` [GraphQL توثیق کی تفصیلات](https://spec.graphql.org/June2018/#sec-Validation) کی 100% کوریج کو سپورٹ کرے گا.
 
-`گراف نوڈ` کے پچھلے ورژن تمام توثیقوں کی حمایت نہیں کرتے تھے اور زیادہ خوبصورت جوابات فراہم کرتے تھے - لہذا، ابہام کی صورت میں، `گراف نوڈ` غلط گراف کیو ایل آپریشن کے اجزاء کو نظر انداز کر رہا تھا.
+`گراف نوڈ` کے پچھلے ورژن تمام توثیقوں کی حمایت نہیں کرتے تھے اور زیادہ خوبصورت جوابات فراہم کرتے تھے - لہذا، ابہام کی صورت میں، `گراف نوڈ` غلط گراف کیو ایل
+ آپریشن کے اجزاء کو نظر انداز کر رہا تھا.
 
 GraphQL ویلیڈیشن سپورٹ آنے والی نئی خصوصیات اور گراف نیٹ ورک کے پیمانے پر کارکردگی کا ایک ستون ہے.
 

From ad9d11beea109df59ce1919476669b8eb3982e07 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:06 -0500
Subject: [PATCH 1042/1325] New translations
 graphql-validations-migration-guide.mdx (Swahili)

---
 .../graphql-validations-migration-guide.mdx   | 538 ++++++++++++++++++
 1 file changed, 538 insertions(+)
 create mode 100644 website/pages/sw/release-notes/graphql-validations-migration-guide.mdx

diff --git a/website/pages/sw/release-notes/graphql-validations-migration-guide.mdx b/website/pages/sw/release-notes/graphql-validations-migration-guide.mdx
new file mode 100644
index 000000000000..4d909e8970a8
--- /dev/null
+++ b/website/pages/sw/release-notes/graphql-validations-migration-guide.mdx
@@ -0,0 +1,538 @@
+---
+title: GraphQL Validations migration guide
+---
+
+Soon `graph-node` will support 100% coverage of the [GraphQL Validations specification](https://spec.graphql.org/June2018/#sec-Validation).
+
+Previous versions of `graph-node` did not support all validations and provided more graceful responses - so, in cases of ambiguity, `graph-node` was ignoring invalid GraphQL operations components.
+
+GraphQL Validations support is the pillar for the upcoming new features and the performance at scale of The Graph Network.
+
+It will also ensure determinism of query responses, a key requirement on The Graph Network.
+
+**Enabling the GraphQL Validations will break some existing queries** sent to The Graph API.
+
+To be compliant with those validations, please follow the migration guide.
+
+> ⚠️ If you do not migrate your queries before the validations are rolled out, they will return errors and possibly break your frontends/clients.
+
+## Migration guide
+
+You can use the CLI migration tool to find any issues in your GraphQL operations and fix them. Alternatively you can update the endpoint of your GraphQL client to use the `https://api-next.thegraph.com/subgraphs/name/$GITHUB_USER/$SUBGRAPH_NAME` endpoint. Testing your queries against this endpoint will help you find the issues in your queries.
+
+> Not all subgraphs will need to be migrated, if you are using [GraphQL ESlint](https://the-guild.dev/graphql/eslint/docs) or [GraphQL Code Generator](https://the-guild.dev/graphql/codegen), they already ensure that your queries are valid.
+
+## Migration CLI tool
+
+**Most of the GraphQL operations errors can be found in your codebase ahead of time.**
+
+For this reason, we provide a smooth experience for validating your GraphQL operations during development or in CI.
+
+[`@graphql-validate/cli`](https://github.com/saihaj/graphql-validate) is a simple CLI tool that helps validate GraphQL operations against a given schema.
+
+### **Getting started**
+
+You can run the tool as follows:
+
+```bash
+npx @graphql-validate/cli -s https://api-next.thegraph.com/subgraphs/name/$GITHUB_USER/$SUBGRAPH_NAME -o *.graphql
+```
+
+**Notes:**
+
+- Set or replace $GITHUB_USER, $SUBGRAPH_NAME with the appropriate values. Like: [`artblocks/art-blocks`](https://api.thegraph.com/subgraphs/name/artblocks/art-blocks)
+- The preview schema URL (https://api-next.thegraph.com/) provided is heavily rate-limited and will be sunset once all users have migrated to the new version. **Do not use it in production.**
+- Operations are identified in files with the following extensions [`.graphql`,](https://www.graphql-tools.com/docs/schema-loading#graphql-file-loader)[`.ts`, `.tsx`, `.js`, `jsx`](https://www.graphql-tools.com/docs/schema-loading#code-file-loader) (`-o` option).
+
+### CLI output
+
+The `[@graphql-validate/cli](https://github.com/saihaj/graphql-validate)` CLI tool will output any GraphQL operations errors as follows:
+
+![Error output from CLI](https://i.imgur.com/x1cBdhq.png)
+
+For each error, you will find a description, file path and position, and a link to a solution example (see the following section).
+
+## Run your local queries against the preview schema
+
+We provide an endpoint `https://api-next.thegraph.com/` that runs a `graph-node` version that has validations turned on.
+
+You can try out queries by sending them to:
+
+- `https://api-next.thegraph.com/subgraphs/id/<Qm...>`
+
+or
+
+- `https://api-next.thegraph.com/subgraphs/name/<GITHUB_USER>/<SUBGRAPH_NAME>`
+
+To work on queries that have been flagged as having validation errors, you can use your favorite GraphQL query tool, like Altair or [GraphiQL](https://cloud.hasura.io/public/graphiql), and try your query out. Those tools will also mark those errors in their UI, even before you run it.
+
+## How to solve issues
+
+Below, you will find all the GraphQL validations errors that could occur on your existing GraphQL operations.
+
+### GraphQL variables, operations, fragments, or arguments must be unique
+
+We applied rules for ensuring that an operation includes a unique set of GraphQL variables, operations, fragments, and arguments.
+
+A GraphQL operation is only valid if it does not contain any ambiguity.
+
+To achieve that, we need to ensure that some components in your GraphQL operation must be unique.
+
+Here's an example of a few invalid operations that violates these rules:
+
+**Duplicate Query name (#UniqueOperationNamesRule)**
+
+```graphql
+# The following operation violated the UniqueOperationName
+# rule, since we have a single operation with 2 queries
+# with the same name
+query myData {
+  id
+}
+
+query myData {
+  name
+}
+```
+
+_Solution:_
+
+```graphql
+query myData {
+  id
+}
+
+query myData2 {
+  # rename the second query
+  name
+}
+```
+
+**Duplicate Fragment name (#UniqueFragmentNamesRule)**
+
+```graphql
+# The following operation violated the UniqueFragmentName
+# rule.
+query myData {
+  id
+  ...MyFields
+}
+
+fragment MyFields {
+  metadata
+}
+
+fragment MyFields {
+  name
+}
+```
+
+_Solution:_
+
+```graphql
+query myData {
+  id
+  ...MyFieldsName
+  ...MyFieldsMetadata
+}
+
+fragment MyFieldsMetadata { # assign a unique name to fragment
+  metadata
+}
+
+fragment MyFieldsName { # assign a unique name to fragment
+  name
+}
+```
+
+**Duplicate variable name (#UniqueVariableNamesRule)**
+
+```graphql
+# The following operation violates the UniqueVariables
+query myData($id: String, $id: Int) {
+  id
+  ...MyFields
+}
+```
+
+_Solution:_
+
+```graphql
+query myData($id: String) {
+  # keep the relevant variable (here: `$id: String`)
+  id
+  ...MyFields
+}
+```
+
+**Duplicate argument name (#UniqueArgument)**
+
+```graphql
+# The following operation violated the UniqueArguments
+query myData($id: ID!) {
+  userById(id: $id, id: "1") {
+    id
+  }
+}
+```
+
+_Solution:_
+
+```graphql
+query myData($id: ID!) {
+  userById(id: $id) {
+    id
+  }
+}
+```
+
+**Duplicate anonymous query (#LoneAnonymousOperationRule)**
+
+Also, using two anonymous operations will violate the `LoneAnonymousOperation` rule due to conflict in the response structure:
+
+```graphql
+# This will fail if executed together in
+# a single operation with the following two queries:
+query {
+  someField
+}
+
+query {
+  otherField
+}
+```
+
+_Solution:_
+
+```graphql
+query {
+  someField
+  otherField
+}
+```
+
+Or name the two queries:
+
+```graphql
+query FirstQuery {
+  someField
+}
+
+query SecondQuery {
+  otherField
+}
+```
+
+### Overlapping Fields
+
+A GraphQL selection set is considered valid only if it correctly resolves the eventual result set.
+
+If a specific selection set, or a field, creates ambiguity either by the selected field or by the arguments used, the GraphQL service will fail to validate the operation.
+
+Here are a few examples of invalid operations that violate this rule:
+
+**Conflicting fields aliases (#OverlappingFieldsCanBeMergedRule)**
+
+```graphql
+# Aliasing fields might cause conflicts, either with
+# other aliases or other fields that exist on the
+# GraphQL schema.
+query {
+  dogs {
+    name: nickname
+    name
+  }
+}
+```
+
+_Solution:_
+
+```graphql
+query {
+  dogs {
+    name: nickname
+    originalName: name # alias the original `name` field
+  }
+}
+```
+
+**Conflicting fields with arguments (#OverlappingFieldsCanBeMergedRule)**
+
+```graphql
+# Different arguments might lead to different data,
+# so we can't assume the fields will be the same.
+query {
+  dogs {
+    doesKnowCommand(dogCommand: SIT)
+    doesKnowCommand(dogCommand: HEEL)
+  }
+}
+```
+
+_Solution:_
+
+```graphql
+query {
+  dogs {
+    knowsHowToSit: doesKnowCommand(dogCommand: SIT)
+    knowsHowToHeel: doesKnowCommand(dogCommand: HEEL)
+  }
+}
+```
+
+Also, in more complex use-cases, you might violate this rule by using two fragments that might cause a conflict in the eventually expected set:
+
+```graphql
+query {
+  # Eventually, we have two "x" definitions, pointing
+  # to different fields!
+  ...A
+  ...B
+}
+
+fragment A on Type {
+  x: a
+}
+
+fragment B on Type {
+  x: b
+}
+```
+
+In addition to that, client-side GraphQL directives like `@skip` and `@include` might lead to ambiguity, for example:
+
+```graphql
+fragment mergeSameFieldsWithSameDirectives on Dog {
+  name @include(if: true)
+  name @include(if: false)
+}
+```
+
+[You can read more about the algorithm here.](https://spec.graphql.org/June2018/#sec-Field-Selection-Merging)
+
+### Unused Variables or Fragments
+
+A GraphQL operation is also considered valid only if all operation-defined components (variables, fragments) are used.
+
+Here are a few examples for GraphQL operations that violates these rules:
+
+**Unused variable** (#NoUnusedVariablesRule)
+
+```graphql
+# Invalid, because $someVar is never used.
+query something($someVar: String) {
+  someData
+}
+```
+
+_Solution:_
+
+```graphql
+query something {
+  someData
+}
+```
+
+**Unused Fragment** (#NoUnusedFragmentsRule)
+
+```graphql
+# Invalid, because fragment AllFields is never used.
+query something {
+  someData
+}
+
+fragment AllFields { # unused :(
+  name
+  age
+}
+```
+
+_Solution:_
+
+```graphql
+# Invalid, because fragment AllFields is never used.
+query something {
+  someData
+}
+
+# remove the `AllFields` fragment
+```
+
+### Invalid or missing Selection-Set (#ScalarLeafsRule)
+
+Also, a GraphQL field selection is only valid if the following is validated:
+
+- An object field must-have selection set specified.
+- An edge field (scalar, enum) must not have a selection set specified.
+
+Here are a few examples of violations of these rules with the following Schema:
+
+```graphql
+type Image {
+  url: String!
+}
+
+type User {
+  id: ID!
+  avatar: Image!
+}
+
+type Query {
+  user: User!
+}
+```
+
+**Invalid Selection-Set**
+
+```graphql
+query {
+  user {
+    id { # Invalid, because "id" is of type ID and does not have sub-fields
+
+    }
+  }
+}
+```
+
+_Solution:_
+
+```graphql
+query {
+  user {
+    id
+  }
+}
+```
+
+**Missing Selection-Set**
+
+```graphql
+query {
+  user {
+    id
+    image # `image` requires a Selection-Set for sub-fields!
+  }
+}
+```
+
+_Solution:_
+
+```graphql
+query {
+  user {
+    id
+    image {
+      src
+    }
+  }
+}
+```
+
+### Incorrect Arguments values (#VariablesInAllowedPositionRule)
+
+GraphQL operations that pass hard-coded values to arguments must be valid, based on the value defined in the schema.
+
+Here are a few examples of invalid operations that violate these rules:
+
+```graphql
+query purposes {
+  # If "name" is defined as "String" in the schema,
+  # this query will fail during validation.
+  purpose(name: 1) {
+    id
+  }
+}
+
+# This might also happen when an incorrect variable is defined:
+
+query purposes($name: Int!) {
+  # If "name" is defined as `String` in the schema,
+  # this query will fail during validation, because the
+  # variable used is of type `Int`
+  purpose(name: $name) {
+    id
+  }
+}
+```
+
+### Unknown Type, Variable, Fragment, or Directive (#UnknownX)
+
+The GraphQL API will raise an error if any unknown type, variable, fragment, or directive is used.
+
+Those unknown references must be fixed:
+
+- rename if it was a typo
+- otherwise, remove
+
+### Fragment: invalid spread or definition
+
+**Invalid Fragment spread (#PossibleFragmentSpreadsRule)**
+
+A Fragment cannot be spread on a non-applicable type.
+
+Example, we cannot apply a `Cat` fragment to the `Dog` type:
+
+```graphql
+query {
+	dog {
+		...CatSimple
+  }
+}
+
+fragment CatSimple on Cat {
+  # ...
+}
+```
+
+**Invalid Fragment definition (#FragmentsOnCompositeTypesRule)**
+
+All Fragment must be defined upon (using `on ...`) a composite type, in short: object, interface, or union.
+
+The following examples are invalid, since defining fragments on scalars is invalid.
+
+```graphql
+fragment fragOnScalar on Int {
+  # we cannot define a fragment upon a scalar (`Int`)
+  something
+}
+
+fragment inlineFragOnScalar on Dog {
+  ... on Boolean {
+    # `Boolean` is not a subtype of `Dog`
+    somethingElse
+  }
+}
+```
+
+### Directives usage
+
+**Directive cannot be used at this location (#KnownDirectivesRule)**
+
+Only GraphQL directives (`@...`) supported by The Graph API can be used.
+
+Here is an example with The GraphQL supported directives:
+
+```graphql
+query {
+  dog {
+    name @include(true)
+    age @skip(true)
+  }
+}
+```
+
+_Note: `@stream`, `@live`, `@defer` are not supported._
+
+**Directive can only be used once at this location (#UniqueDirectivesPerLocationRule)**
+
+The directives supported by The Graph can only be used once per location.
+
+The following is invalid (and redundant):
+
+```graphql
+query {
+  dog {
+    name @include(true) @include(true)
+  }
+}
+```

From bec4d8555882c90d2b13fea5aa4ba4dc59c9b358 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:07 -0500
Subject: [PATCH 1043/1325] New translations arbitrum-faq.mdx (Romanian)

---
 website/pages/ro/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/ro/arbitrum/arbitrum-faq.mdx b/website/pages/ro/arbitrum/arbitrum-faq.mdx
index a36b0103772f..9c12c8816259 100644
--- a/website/pages/ro/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/ro/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## Why is The Graph implementing an L2 Solution?
+## Why did The Graph implement an L2 Solution?
 
-By scaling The Graph on L2, network participants can expect:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ By scaling The Graph on L2, network participants can expect:
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle
 
 ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-As of April 10th, 2023, 5% of all indexing rewards are being minted on Arbitrum. As network participation increases, and as the Council approves it, indexing rewards will gradually shift from Ethereum to Arbitrum, eventually moving entirely to Arbitrum.
-
-## If I would like to participate in the network on L2, what should I do?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Are there any risks associated with scaling the network to L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Will existing subgraphs on Ethereum continue to work?
+## Are existing subgraphs on Ethereum working?
 
-Yes, The Graph Network contracts will operate in parallel on both Ethereum and Arbitrum until moving fully to Arbitrum at a later date.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Will GRT have a new smart contract deployed on Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From b7bf76e4d7c719f386d6c768b59378bcdfa0d81e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:08 -0500
Subject: [PATCH 1044/1325] New translations arbitrum-faq.mdx (French)

---
 website/pages/fr/arbitrum/arbitrum-faq.mdx | 42 ++++++++++------------
 1 file changed, 18 insertions(+), 24 deletions(-)

diff --git a/website/pages/fr/arbitrum/arbitrum-faq.mdx b/website/pages/fr/arbitrum/arbitrum-faq.mdx
index 85632d92168b..23faf8dab29b 100644
--- a/website/pages/fr/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/fr/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: FAQ d'Arbitrum
 
 Cliquez [ici] (#billing-on-arbitrum-faqs) si vous souhaitez passer à la FAQ sur la facturation Arbitrum.
 
-## Pourquoi The Graph met-il en place une solution L2 ?
+## Pourquoi The Graph a-t-il mis en place une solution L2 ?
 
-En faisant passer The Graph à l'échelle L2, les participants au réseau peuvent espérer :
+Grâce à la mise à l'échelle de The Graph sur la L2, les participants du réseau peuvent désormais bénéficier de ce qui suit :
 
 - Jusqu'à 26 fois plus d'économies sur les frais de gaz
 
@@ -14,26 +14,26 @@ En faisant passer The Graph à l'échelle L2, les participants au réseau peuven
 
 - La sécurité héritée d'Ethereum
 
-La mise à l'échelle des contrats intelligents du protocole sur L2 permet aux participants au réseau d'interagir plus fréquemment pour un coût réduit en termes de frais de gaz. Par exemple, les indexeurs peuvent ouvrir et fermer des allocations pour indexer un plus grand nombre de subgraphs avec une plus grande fréquence, les développeurs peuvent déployer et mettre à jour des subgraphs plus facilement, les délégués peuvent déléguer des GRT avec une fréquence accrue, et les curateurs peuvent ajouter ou supprimer des signaux à un plus grand nombre de subgraphs - des actions auparavant considérées comme trop coûteuses pour être effectuées fréquemment en raison des frais de gaz.
+La mise à l'échelle des contrats intelligents du protocole sur la L2 permet aux participants du réseau d'interagir plus fréquemment pour un coût réduit en termes de frais de gaz. Par exemple, les Indexeurs peuvent ouvrir et fermer des allocations plus fréquemment pour indexer un plus grand nombre de subgraphs. Les développeurs peuvent déployer et mettre à jour des subgraphs plus facilement, et les Déléguateurs peuvent déléguer des GRT plus fréquemment. Les Curateurs peuvent ajouter ou supprimer des signaux dans un plus grand nombre de subgraphs - des actions auparavant considérées comme trop coûteuses pour être effectuées fréquemment en raison des frais de gaz.
 
 La communauté Graph a décidé d'avancer avec Arbitrum l'année dernière après le résultat de la discussion [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
 ## Que dois-je faire pour utiliser The Graph en L2 ?
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+Le système de facturation de The Graph accepte le GRT sur Arbitrum, et les utilisateurs auront besoin d'ETH sur Arbitrum pour payer leurs frais de gaz. Bien que le protocole The Graph ait commencé sur Ethereum Mainnet, toute l'activité, y compris les contrats de facturation, est maintenant sur Arbitrum One.
 
-Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Par conséquent, pour payer les requêtes, vous avez besoin de GRT sur Arbitrum. Voici quelques façons d'y parvenir :
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Si vous avez déjà des GRT sur Ethereum, vous pouvez les bridge vers Arbitrum. Vous pouvez le faire via l'option de bridge de GRT fournie dans Subgraph Studio ou en utilisant l'un des bridges suivants :
 
-  - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+  - [Le Bridge Arbitrum](https://bridge.arbitrum.io/?l2ChainId=42161)
   - [TransferTo](https://transferto.xyz/swap)
 
-- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap.
+- Si vous avez d'autres actifs sur Arbitrum, vous pouvez les échanger contre du GRT via un protocole de swap comme Uniswap.
 
-- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange.
+- Alternativement, vous pouvez obtenir des GRT directement sur Arbitrum via un échangeur décentralisé.
 
-Once you have GRT on Arbitrum, you can add it to your billing balance.
+Une fois que vous avez des GRT sur Arbitrum, vous pouvez l'ajouter à votre solde de facturation.
 
 Pour tirer parti de l'utilisation de The Graph sur L2, utilisez ce sélecteur déroulant pour passer d'une chaîne à l'autre.
 
@@ -41,27 +41,21 @@ Pour tirer parti de l'utilisation de The Graph sur L2, utilisez ce sélecteur d
 
 ## En tant que développeur de subgraphs, consommateur de données, indexeur, curateur ou délégateur, que dois-je faire maintenant ?
 
-Aucune action immédiate n'est requise, cependant, les participants au réseau sont encouragés à commencer à migrer vers Arbitrum pour profiter des avantages de L2.
+Les participants du réseau doivent passer à Arbitrum pour continuer à participer à The Graph Network. Veuillez consulter le [Guide de l'outil de transfert L2](/arbitrum/l2-transfer-tools-guide/) pour une assistance supplémentaire.
 
-Les équipes de développeurs de base travaillent à la création d'outils de transfert L2 qui faciliteront considérablement le transfert de la délégation, de la curation et des subgraphes vers Arbitrum. Les participants au réseau peuvent s'attendre à ce que les outils de transfert L2 soient disponibles d'ici l'été 2023.
+Toutes les récompenses d'indexation sont désormais entièrement sur Arbitrum.
 
-À partir du 10 avril 2023, 5 % de toutes les récompenses d'indexation sont frappées sur Arbitrum. Au fur et à mesure que la participation au réseau augmentera et que le Conseil l'approuvera, les récompenses d'indexation passeront progressivement de l'Ethereum à l'Arbitrum, pour finalement passer entièrement à l'Arbitrum.
+## Y avait-il des risques associés à la mise à l'échelle du réseau vers la L2 ?
 
-## Que dois-je faire si je souhaite participer au réseau L2 ?
-
-Veuillez aider à [tester le réseau](https://testnet.thegraph.com/explorer) sur L2 et signaler vos commentaires sur votre expérience dans [Discord](https://discord.gg/graphprotocol).
-
-## Existe-t-il des risques associés à la mise à l’échelle du réseau vers L2 ?
-
-All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
+Tous les contrats intelligents ont été soigneusement [vérifiés](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-aud.pdf).
 
 Tout a été testé minutieusement et un plan d’urgence est en place pour assurer une transition sûre et fluide. Les détails peuvent être trouvés [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and- considérations de sécurité-20).
 
-## Les subgraphs existants sur Ethereum continueront-ils à fonctionner ?
+## Les subgraphs existants sur Ethereum fonctionnent  t-ils?
 
-Oui, les contrats The Graph Network fonctionneront en parallèle sur Ethereum et Arbitrum jusqu'à leur passage complet à Arbitrum à une date ultérieure.
+Tous les subgraphs sont désormais sur Arbitrum. Veuillez consulter le [Guide de l'outil de transfert L2](/arbitrum/l2-transfer-tools-guide/) pour vous assurer que vos subgraphs fonctionnent sans problème.
 
-## GRT disposera-t-il d'un nouveau contrat intelligent déployé sur Arbitrum ?
+## GRT a-t-il un nouveau contrat intelligent déployé sur Arbitrum ?
 
 Oui, GRT dispose d'un [contrat intelligent sur Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) supplémentaire. Cependant, le réseau principal Ethereum [contrat GRT](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) restera opérationnel.
 
@@ -83,4 +77,4 @@ Le pont a été [fortement audité](https://code4rena.com/contests/2022-10-the-g
 
 L'ajout de GRT à votre solde de facturation Arbitrum peut être effectué en un seul clic dans [Subgraph Studio](https://thegraph.com/studio/). Vous pourrez facilement relier votre GRT à Arbitrum et remplir vos clés API en une seule transaction.
 
-Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT.
+Visitez la [page de Facturation](/facturation/) pour obtenir des instructions plus détaillées sur l'ajout, le retrait ou l'acquisition de GRT.

From 6fa61f7d91a00e183c34c73f7ac5bbda4cce7e61 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:09 -0500
Subject: [PATCH 1045/1325] New translations arbitrum-faq.mdx (Spanish)

---
 website/pages/es/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/es/arbitrum/arbitrum-faq.mdx b/website/pages/es/arbitrum/arbitrum-faq.mdx
index 2b8812590990..b418ae4af15c 100644
--- a/website/pages/es/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/es/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Preguntas frecuentes sobre Arbitrum
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## ¿Por qué The Graph está implementando una solución L2?
+## Why did The Graph implement an L2 Solution?
 
-Al escalar The Graph en L2, los participantes de la red pueden esperar:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ Al escalar The Graph en L2, los participantes de la red pueden esperar:
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ Para aprovechar el uso de The Graph en L2, usa este conmutador desplegable para
 
 ## Como developer de subgrafos, consumidor de datos, Indexador, Curador o Delegador, ¿qué debo hacer ahora?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-A partir del 10 de abril de 2023, el 5% de todas las recompensas de indexación se están generando en Arbitrum. A medida que aumenta la participación en la red, y según lo apruebe el Council, las recompensas de indexación se desplazarán gradualmente de Ethereum a Arbitrum, moviéndose eventualmente por completo a Arbitrum.
-
-## Si me gustaría participar en la red en L2, ¿qué debo hacer?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## ¿Existe algún riesgo asociado con escalar la red a L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## ¿Seguirán funcionando los subgrafos existentes en Ethereum?
+## Are existing subgraphs on Ethereum working?
 
-Sí, los contratos de The Graph Network operarán en paralelo tanto en Ethereum como en Arbitrum hasta que pasen completamente a Arbitrum en una fecha posterior.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## ¿GRT tendrá un nuevo contrato inteligente implementado en Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From d8c251f184d0f41dcfcc017697ad78017f0ecedd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:10 -0500
Subject: [PATCH 1046/1325] New translations arbitrum-faq.mdx (Arabic)

---
 website/pages/ar/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/ar/arbitrum/arbitrum-faq.mdx b/website/pages/ar/arbitrum/arbitrum-faq.mdx
index 98346d82a41d..2cf8402a7718 100644
--- a/website/pages/ar/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/ar/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: الأسئلة الشائعة حول Arbitrum
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## لماذا يقوم The Graph بتطبيق حل L2؟
+## Why did The Graph implement an L2 Solution?
 
-By scaling The Graph on L2, network participants can expect:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ By scaling The Graph on L2, network participants can expect:
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
 
 ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-اعتبارًا من 10 أبريل 2023 ، تم سك 5٪ من جميع مكافآت الفهرسة على Arbitrum. مع زيادة المشاركة في الشبكة ، وموافقة المجلس عليها ، ستتحول مكافآت الفهرسة تدريجياً من Ethereum إلى Arbitrum ، وستنتقل في النهاية بالكامل إلى Arbitrum.
-
-## إذا كنت أرغب في المشاركة في اشبكة L2 ، فماذا أفعل؟
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## هل توجد أي مخاطر مرتبطة بتوسيع الشبكة إلى L2؟
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## هل ستستمر ال subgraphs الموجودة على Ethereum في العمل؟
+## Are existing subgraphs on Ethereum working?
 
-نعم ، ستعمل عقود شبكة The Graph بالتوازي على كل من Ethereum و Arbitrum حتى الانتقال بشكل كامل إلى Arbitrum في وقت لاحق.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## هل سيكون لدى GRT عقد ذكي جديد يتم نشره على Arbitrum؟
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From ea6db4536c63e15f6f4b32aec359efa0b5f0ad3b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:11 -0500
Subject: [PATCH 1047/1325] New translations arbitrum-faq.mdx (Czech)

---
 website/pages/cs/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/cs/arbitrum/arbitrum-faq.mdx b/website/pages/cs/arbitrum/arbitrum-faq.mdx
index 4f9d8f545b6a..486e371b527d 100644
--- a/website/pages/cs/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/cs/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Pokud chcete přejít na často ptal dotazy k účtování Arbitrum, klikněte na [here](#billing-on-arbitrum-faqs).
 
-## Proč The Graph implementuje řešení L2?
+## Why did The Graph implement an L2 Solution?
 
-Škálováním The Graph na L2, sítě účastníci mohou očekávat:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Až 26x úspora na poplatcích za plyn
 
@@ -14,7 +14,7 @@ Pokud chcete přejít na často ptal dotazy k účtování Arbitrum, klikněte n
 
 - Zabezpečení zděděné po Ethereum
 
-Škálování chytrých smluv protokolu na L2 umožňuje účastníkům sítě interakci častěji při snížených nákladech na plyn. Například, indexéry by mohly otevírat a zavírat alokace pro indexování většího počtu podgrafů s větší frekvencí, vývojáři mohli snadněji zavádět a aktualizovat podgrafy s větší lehkostí, Delegátor by mohli častěji delegovat GRT, Kurátoři by mohli přidávat nebo odebírat signály do většího počtu podgrafů–akcí dříve považovány za příliš nákladné dělat často kvůli nákladům.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 Komunita Graf se v loňském roce rozhodla pokračovat v Arbitrum po výsledku diskuze [GIP-0031] (https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
@@ -41,27 +41,21 @@ Pro využití výhod používání a Graf na L2 použijte rozevírací přepína
 
 ## Jako vývojář podgrafů, Spotřebitel dat, indexer, kurátor, nebo delegátor, co mám nyní udělat?
 
-Není třeba přijímat žádná okamžitá opatření, nicméně vyzýváme účastníky sítě, aby začali přecházet na Arbitrum a využívali výhod L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Týmy hlavních vývojářů pracují na vytvoření nástrojů pro přenos L2, které usnadní přesun delegování, kurátorství a podgrafů do služby Arbitrum. Účastníci sítě mohou očekávat, že nástroje pro přenos L2 budou k dispozici do léta 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-Od 10. dubna 2023 se na Arbitrum razí 5 % všech indexačních odměn. S rostoucí účastí v síti a se souhlasem Rady, odměny za indexování se postupně přesunou z Etherea na Arbitrum a nakonec zcela na Arbitrum.
-
-## Co mám udělat, pokud se chci zapojit do sítě L2?
-
-Pomozte prosím [otestovat síť](https://testnet.thegraph.com/explorer) na L2 a nahlaste své zkušenosti na [Discord](https://discord.gg/graphprotocol).
-
-## Existují nějaká rizika spojená s rozšiřováním sítě na L2?
+## Were there any risks associated with scaling the network to L2?
 
 Všechny chytré smlouvy byly důkladně [auditovány](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Vše bylo důkladně otestováno, a je připraven pohotovostní plán, který zajistí bezpečný a bezproblémový přechod. Podrobnosti naleznete [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Budou stávající subgrafy na Ethereum fungovat i nadále?
+## Are existing subgraphs on Ethereum working?
 
-Ano, smlouvy Graf síť budou fungovat paralelně na platformě Ethereum i Arbitrum, dokud se později plně nepřesunou na Arbitrum.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Bude mít GRT na Arbitrum nasazen nový chytrý kontrakt?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Ano, GRT má další [smart contract na Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Mainnetový [kontrakt GRT](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) na Ethereum však zůstane v provozu.
 

From 2ce2f9f7ceb71e1f78fe4f3d95e9a1baecd0b0da Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:12 -0500
Subject: [PATCH 1048/1325] New translations arbitrum-faq.mdx (German)

---
 website/pages/de/arbitrum/arbitrum-faq.mdx | 42 ++++++++++------------
 1 file changed, 18 insertions(+), 24 deletions(-)

diff --git a/website/pages/de/arbitrum/arbitrum-faq.mdx b/website/pages/de/arbitrum/arbitrum-faq.mdx
index 67fffeeb677c..7e48874081e2 100644
--- a/website/pages/de/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/de/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum-FAQ
 
 Klicken Sie [hier](#billing-on-arbitrum-faqs), wenn Sie zu den Arbitrum Billing FAQs springen möchten.
 
-## Warum implementiert The Graph eine L2-Lösung?
+## Warum hat The Graph eine L2-Lösung eingeführt?
 
-Durch die Skalierung von The Graph auf L2 können die Netzwerkteilnehmer erwarten:
+Durch die Skalierung von The Graph auf L2 können die Netzwerkteilnehmer nun von folgenden Vorteilen profitieren:
 
 - Bis zu 26-fache Einsparungen bei den Gebühren für Gas
 
@@ -14,26 +14,26 @@ Durch die Skalierung von The Graph auf L2 können die Netzwerkteilnehmer erwarte
 
 - Von Ethereum übernommene Sicherheit
 
-Die Skalierung der Smart Contracts des Protokolls auf L2 ermöglicht den Netzwerkteilnehmern eine häufigere Interaktion zu geringeren Kosten in Form von Gasgebühren. Zum Beispiel könnten Indexer Zuweisungen öffnen und schließen, um eine größere Anzahl von Subgraphen mit größerer Häufigkeit zu indexieren, Entwickler könnten Subgraphen mit größerer Leichtigkeit bereitstellen und aktualisieren, Delegatoren könnten GRT mit größerer Häufigkeit delegieren und Kuratoren könnten Signale zu einer größeren Anzahl von Subgraphen hinzufügen oder entfernen - Aktionen, die zuvor als zu kostenintensiv angesehen wurden, um sie häufig auszuführen.
+Die Skalierung der Smart Contracts des Protokolls auf L2 ermöglicht den Netzwerkteilnehmern eine häufigere Interaktion zu geringeren Kosten in Form von Gasgebühren. So können Indexer beispielsweise häufiger Zuweisungen öffnen und schließen, um eine größere Anzahl von Subgraphen zu indexieren. Entwickler können Subgraphen leichter bereitstellen und aktualisieren, und Delegatoren können GRT häufiger delegieren. Kuratoren können einer größeren Anzahl von Subgraphen Signale hinzufügen oder entfernen - Aktionen, die bisher aufgrund der Kosten zu kostspielig waren, um sie häufig durchzuführen.
 
-DieThe Graph-Community beschloss letztes Jahr nach dem Ergebnis der [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305)-Diskussion, mit Arbitrum weiterzumachen.
+Die The Graph-Community beschloss letztes Jahr nach dem Ergebnis der [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305)-Diskussion, mit Arbitrum weiterzumachen.
 
 ## Was muss ich tun, um The Graph auf L2 zu nutzen?
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+Das Abrechnungssystem von The Graph akzeptiert GRT auf Arbitrum, und die Nutzer benötigen ETH auf Arbitrum, um ihr Gas zu bezahlen. Während das The Graph-Protokoll auf dem Ethereum Mainnet begann, finden alle Aktivitäten, einschließlich der Abrechnungsverträge, nun auf Arbitrum One statt.
 
-Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Um Abfragen zu bezahlen brauchen Sie also GRT auf Arbitrum. Hier sind ein paar Möglichkeiten, dies zu erreichen:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Wenn Sie bereits GRT auf Ethereum haben, können Sie es zu Arbitrum überbrücken. Sie können dieses über GRT-Bridging-Option in Subgraph Studio tun oder eine der folgenden Bridges verwenden:
 
-  - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+  - [Die Arbitrum-Brücke] (https://bridge.arbitrum.io/?l2ChainId=42161)
   - [TransferTo](https://transferto.xyz/swap)
 
-- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap.
+- Wenn du andere Vermögenswerte auf Arbitrum hast, kannst du sie über ein Swapping-Protokoll wie Uniswap in GRT tauschen.
 
-- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange.
+- Alternativ können Sie GRT auch direkt auf Arbitrum über einen dezentralen Handelsplatz erwerben.
 
-Once you have GRT on Arbitrum, you can add it to your billing balance.
+Sobald Sie GRT auf Arbitrum haben, können Sie es zu Ihrem Guthaben hinzufügen.
 
 Um die Vorteile von The Graph auf L2 zu nutzen, verwenden Sie diesen Dropdown-Schalter, um zwischen den Ketten umzuschalten.
 
@@ -41,27 +41,21 @@ Um die Vorteile von The Graph auf L2 zu nutzen, verwenden Sie diesen Dropdown-Sc
 
 ## Was muss ich als Entwickler von Subgraphen, Datenkonsument, Indexer, Kurator oder Delegator jetzt tun?
 
-Es besteht kein unmittelbarer Handlungsbedarf, jedoch werden die Netzwerkteilnehmer ermutigt, mit der Umstellung auf Arbitrum zu beginnen, um von den Vorteilen von L2 zu profitieren.
+Die Netzwerkteilnehmer müssen zu Arbitrum wechseln, um weiterhin am The Graph Netzwerk teilzunehmen. Bitte lesen Sie den [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) für zusätzliche Unterstützung.
 
-Kernentwicklerteams arbeiten an der Erstellung von L2-Transfer-Tools, die die Übertragung von Delegation, Kuration und Subgraphen auf Arbitrum erheblich erleichtern werden. Netzwerkteilnehmer können davon ausgehen, dass L2-Transfer-Tools bis zum Sommer 2023 verfügbar sein werden.
-
-Ab dem 10. April 2023 werden 5% aller Indexierungs-Rewards auf Arbitrum geprägt. Mit zunehmender Beteiligung des Netzwerks und der Zustimmung des Rates werden die Indexierungsprämien schrittweise von Ethereum auf Arbitrum und schließlich vollständig auf Arbitrum umgestellt.
-
-## Was muss ich tun, wenn ich am L2-Netz teilnehmen möchte?
-
-Bitte helfen Sie [test the network](https://testnet.thegraph.com/explorer) auf L2 und berichten Sie über Ihre Erfahrungen in [Discord](https://discord.gg/graphprotocol).
+Alle Indexierungsprämien sind jetzt vollständig auf Arbitrum.
 
 ## Sind mit der Skalierung des Netzes auf L2 irgendwelche Risiken verbunden?
 
-All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
+Alle Smart Contracts wurden gründlich [audited] (https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Alles wurde gründlich getestet, und es gibt einen Notfallplan, um einen sicheren und nahtlosen Übergang zu gewährleisten. Einzelheiten finden Sie [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Werden die bestehenden Subgraphen auf Ethereum weiterhin funktionieren?
+## Funktionieren die vorhandenen Subgraphen auf Ethereum?
 
-Ja, die The Graph Netzwerk-Verträge werden parallel sowohl auf Ethereum als auch auf Arbitrum laufen, bis sie zu einem späteren Zeitpunkt vollständig auf Arbitrum umgestellt werden.
+Alle Subgraphen sind jetzt auf Arbitrum. Bitte lesen Sie den [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/), um sicherzustellen, dass Ihre Subgraphen reibungslos funktionieren.
 
-## Wird GRT einen neuen Smart Contract auf Arbitrum bereitstellen?
+## Verfügt GRT über einen neuen Smart Contract, der auf Arbitrum eingesetzt wird?
 
 Ja, GRT hat einen zusätzlichen [Smart Contract auf Arbitrum] (https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Der Ethereum-Hauptnetz-[GRT-Vertrag](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) wird jedoch weiterhin funktionieren.
 
@@ -83,4 +77,4 @@ Die Brücke wurde [umfangreich geprüft] (https://code4rena.com/contests/2022-10
 
 Das Hinzufügen von GRT zu Ihrem Arbitrum-Abrechnungssaldo kann mit nur einem Klick in [Subgraph Studio] (https://thegraph.com/studio/) erfolgen. Sie können Ihr GRT ganz einfach mit Arbitrum verbinden und Ihre API-Schlüssel in einer einzigen Transaktion füllen.
 
-Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT.
+Besuchen Sie die [Abrechnungsseite] (/) für detaillierte Anweisungen zum Hinzufügen, Abheben oder Erwerben von GRT.

From 511731efdca0901f34babc462e26f3fa355422ab Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:13 -0500
Subject: [PATCH 1049/1325] New translations arbitrum-faq.mdx (Italian)

---
 website/pages/it/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/it/arbitrum/arbitrum-faq.mdx b/website/pages/it/arbitrum/arbitrum-faq.mdx
index bff15519f682..220dbe4480c8 100644
--- a/website/pages/it/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/it/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Clicca [qui](#billing-on-arbitrum-faqs) se desideri saltare alle domande frequenti sulla fatturazione su Arbitrum.
 
-## Perché The Graph sta implementando una soluzione L2?
+## Why did The Graph implement an L2 Solution?
 
-Scalando su L2, i partecipanti alla rete The Graph possono aspettarsi:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Risparmi fino a 26 volte sulle commissioni di gas
 
@@ -14,7 +14,7 @@ Scalando su L2, i partecipanti alla rete The Graph possono aspettarsi:
 
 - Sicurezza ereditata da Ethereum
 
-La scalabilità degli smart contract del protocollo su L2 consente ai partecipanti della rete di interagire più frequentemente a un costo ridotto delle commissioni di gas. Ad esempio, gli Indexer potrebbero aprire e chiudere allocazioni per indicizzare un maggior numero di subgraph con maggiore frequenza, gli sviluppatori potrebbero distribuire e aggiornare i subgraph con maggiore facilità, i Delegator potrebbero delegare GRT con maggiore frequenza e i Curator potrebbero aggiungere o rimuovere segnali a un maggior numero di subgraph - azioni che in passato erano considerate troppo costose da eseguire frequentemente a causa delle commissioni di gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 La comunità di The Graph ha deciso di procedere con Arbitrum l'anno scorso dopo l'esito della discussione [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
@@ -41,27 +41,21 @@ Per sfruttare l'utilizzo di The Graph su L2, utilizza il selettore a discesa per
 
 ## In quanto sviluppatore di subgraph, consumatore di dati, Indexer, Curator o Delegator, cosa devo fare ora?
 
-Non è richiesta alcuna azione immediata, tuttavia si incoraggiano i partecipanti della rete a iniziare a passare ad Arbitrum per beneficiare dei vantaggi di L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-I team di sviluppatori principali stanno lavorando per creare strumenti di trasferimento a L2 che faciliteranno notevolmente il passaggio di deleghe, cure e subgraph su Arbitrum. Ci si aspetta che gli strumenti di trasferimento a L2 siano disponibili entro l'estate del 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-I principali team di sviluppo stanno lavorando per creare strumenti di trasferimento a L2 che faciliteranno notevolmente il passaggio dei GRT delegati, curati, e dei subgraph su Arbitrum. Ci si aspetta che gli strumenti di trasferimento a L2 siano disponibili entro l'estate del 2023.
-
-## Se desiderassi partecipare alla rete su L2, cosa devo fare?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Ci sono rischi associati alla scalabilità della rete su L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Tutto è stato testato accuratamente e un piano di contingenza è in atto per garantire una transizione sicura e senza intoppi. I dettagli possono essere trovati [qui](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## I subgraph esistenti su Ethereum continueranno a funzionare?
+## Are existing subgraphs on Ethereum working?
 
-Sì, gli smart contract di The Graph Network opereranno parallelamente su entrambe le reti Ethereum e Arbitrum fino a quando non si sposteranno completamente su Arbitrum in una data successiva.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Verrà implementato un nuovo smart contract per i GRT su Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Sì, GRT avrà un nuovo [smart contract su Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Tuttavia, il contratto principale [GRT](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) su Ethereum continuerà a essere operativo.
 

From 3cd851091717a3e45353974caa4f0205e257ac47 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:14 -0500
Subject: [PATCH 1050/1325] New translations arbitrum-faq.mdx (Japanese)

---
 website/pages/ja/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/ja/arbitrum/arbitrum-faq.mdx b/website/pages/ja/arbitrum/arbitrum-faq.mdx
index 0cc4f7829ce1..8b416bd7cfe2 100644
--- a/website/pages/ja/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/ja/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Arbitrum Billing FAQ にスキップしたい場合は[here](#billing-on-arbitrum-faqs) をクリックしてください。
 
-## The GraphがL2ソリューションを導入する理由は？
+## Why did The Graph implement an L2 Solution?
 
-The GraphをL2でスケールさせることで、ネットワーク参加者は以下を期待できます：
+By scaling The Graph on L2, network participants can now benefit from:
 
 - ガス料金を 26 倍以上節約
 
@@ -14,7 +14,7 @@ The GraphをL2でスケールさせることで、ネットワーク参加者は
 
 - イーサリアムから継承したセキュリティ
 
-プロトコル スマート コントラクトを L2 に拡張すると、ネットワーク参加者はガス料金を削減しながら、より頻繁に対話できるようになります。たとえば、インデクサーは割り当てを開いたり閉じたりして、より多くのサブグラフにインデックスをより頻繁に付けることができ、開発者はサブグラフのデプロイと更新をより簡単に行うことができ、委任者はより高い頻度で GRT を委任でき、キュレーターはより多くのサブグラフにシグナルを追加または削除できます。サブグラフ – 以前は、ガスのために頻繁に実行するにはコストが高すぎると考えられていたアクション。
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 Graph コミュニティは、[GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) の議論の結果を受けて、昨年 Arbitrum を進めることを決定しました。
 
@@ -41,27 +41,21 @@ L2でのThe Graphの活用には、このドロップダウンスイッチャー
 
 ## サブグラフ開発者、データ消費者、インデクサー、キュレーター、デリゲーターは何をする必要がありますか？
 
-直ちに対応する必要はありませんが、ネットワーク参加者は L2 の利点を活用するために Arbitrum への移行を開始することをお勧めします。
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-コア開発者チームは、委任、キュレーション、およびサブグラフを Arbitrum に移行するのを大幅に容易にする L2 転送ツールの作成に取り組んでいます。ネットワーク参加者は、2023 年の夏までに L2 転送ツールが利用可能になることを期待できます。
+All indexing rewards are now entirely on Arbitrum.
 
-2023 年 4 月 10 日の時点で、すべてのインデックス作成報酬の 5% が Arbitrum で鋳造されています。ネットワークへの参加が増加し、評議会がそれを承認すると、インデックス作成の報酬はイーサリアムからアービトラムに徐々に移行し、最終的には完全にアービトラムに移行します。
-
-## L2でのネットワークに参加したい場合は、どうすればいいのでしょうか？
-
-L2 の [test the network](https://testnet.thegraph.com/explorer) にご協力いただき、[Discord](https://discord.gg/graphprotocol) でのエクスペリエンスに関するフィードバックを報告してください。
-
-## L2へのネットワーク拡張に伴うリスクはありますか？
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 すべてが徹底的にテストされており、安全かつシームレスな移行を保証するための緊急時対応計画が整備されています。詳細は[here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20)をご覧ください。
 
-## イーサリアムの既存のサブグラフは引き続き使えるのでしょうか？
+## Are existing subgraphs on Ethereum working?
 
-はい、グラフネットワークのコントラクトは、後日Arbitrumに完全に移行するまでは、EthereumとArbitrumの両方で並行して運用される予定です。
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## GRTはArbitrumに新しいスマートコントラクトをデプロイするのでしょうか？
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 はい、GRT には追加の [Arbitrum 上のスマート コントラクト](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) があります。ただし、イーサリアムのメインネット [GRT 契約](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) は引き続き運用されます。
 

From 3b66d53fa27e9e6a68cd14b9dcf456a9bb395559 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:15 -0500
Subject: [PATCH 1051/1325] New translations arbitrum-faq.mdx (Korean)

---
 website/pages/ko/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/ko/arbitrum/arbitrum-faq.mdx b/website/pages/ko/arbitrum/arbitrum-faq.mdx
index a36b0103772f..9c12c8816259 100644
--- a/website/pages/ko/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/ko/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## Why is The Graph implementing an L2 Solution?
+## Why did The Graph implement an L2 Solution?
 
-By scaling The Graph on L2, network participants can expect:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ By scaling The Graph on L2, network participants can expect:
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle
 
 ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-As of April 10th, 2023, 5% of all indexing rewards are being minted on Arbitrum. As network participation increases, and as the Council approves it, indexing rewards will gradually shift from Ethereum to Arbitrum, eventually moving entirely to Arbitrum.
-
-## If I would like to participate in the network on L2, what should I do?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Are there any risks associated with scaling the network to L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Will existing subgraphs on Ethereum continue to work?
+## Are existing subgraphs on Ethereum working?
 
-Yes, The Graph Network contracts will operate in parallel on both Ethereum and Arbitrum until moving fully to Arbitrum at a later date.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Will GRT have a new smart contract deployed on Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From 572bbd1decbfb538343925717a2754a19fa827e1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:16 -0500
Subject: [PATCH 1052/1325] New translations arbitrum-faq.mdx (Dutch)

---
 website/pages/nl/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/nl/arbitrum/arbitrum-faq.mdx b/website/pages/nl/arbitrum/arbitrum-faq.mdx
index 34580766c5ef..46baaad9d1e0 100644
--- a/website/pages/nl/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/nl/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Klik [hier] (#billing-on-arbitrum-faqs) als je de Arbitrum facturering FAQ wilt overslaan.
 
-## Waarom is The Graph een L2 oplossing aan het implementeren?
+## Why did The Graph implement an L2 Solution?
 
-Door het schalen van The Graph op L2, netwerk deelnemers kunnen het volgende verwachten:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Meer dan 26x besparen op gas fees
 
@@ -14,7 +14,7 @@ Door het schalen van The Graph op L2, netwerk deelnemers kunnen het volgende ver
 
 - Veiligheid overgenomen van Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph gemeenschap heeft vorig jaar besloten om door te gaan met Arbitrum na de uitkomst van [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussie.
 
@@ -41,27 +41,21 @@ Om gebruik te maken van The Graph op L2, gebruik deze keuzeschakelaar om te wiss
 
 ## Als een subgraph ontwikkelaar, data consument, Indexer, Curator, of Delegator, wat moet ik nu doen?
 
-Er is geen directe handeling vereisd, echter, netwerk deelnemers worden wel aangemoedigd om te beginnen met overstappen naar Arbitrum om te profiteren van de voordelen van L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Kern-ontwikkelingsteams werken eraan om L2 overdrachtstools te creëren die het aanzienlijk makkelijker zullen maken om delegatie, curatie en subgraphs naar Arbitrum te verplaatsen. Netwerkdeelnemers kunnen verwachten dat L2 overdrachtstools beschikbaar zullen zijn tegen de zomer van 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-Vanaf 10 april 2023 wordt 5% van alle indexing beloningen gemint op Arbitrum. Naarmate de netwerkparticipatie toeneemt en de Raad het goedkeurt, zullen de indexing rewards geleidelijk verschuiven van Ethereum naar Arbitrum en uiteindelijk volledig overgaan naar Arbitrum.
-
-## If I would like to participate in the network on L2, what should I do?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Zijn er risico's verbonden met het schalen van het netwerk naar L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Alles is grondig getest, en een eventualiteiten plan is gemaakt en klaargezet voor een veilige en naadloze transitie. Details kunnen [hier](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20) gevonden worden.
 
-## Zullen bestaande subgraphs op Etherium blijven werken?
+## Are existing subgraphs on Ethereum working?
 
-Ja, The Graph Netwerk contracts zullen op zowel Ethereum als Arbitrum parallel opereren tot het volledig overgaan op Arbitrum op een latere datum.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Zal GRT nieuwe smart contract implementeren op Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Ja, GRT heeft een extra [smart contract op Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Echter, het Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) zal operationeel blijven.
 

From 964844d9ee669d1a6c7d56a31eba8e38500865a7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:17 -0500
Subject: [PATCH 1053/1325] New translations arbitrum-faq.mdx (Polish)

---
 website/pages/pl/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/pl/arbitrum/arbitrum-faq.mdx b/website/pages/pl/arbitrum/arbitrum-faq.mdx
index 575b56c610f0..85aa42a5b6f1 100644
--- a/website/pages/pl/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/pl/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum - najczęściej zadawane pytania
 
 Kliknij [tutaj](#billing-on-Arbitrum-faqs), jeśli chcesz przejść do najczęściej zadawanych pytań dotyczących rozliczeń w sieci Arbitrum.
 
-## Dlaczego The Graph implementuje rozwiązanie L2 (ang. Layer 2)?
+## Why did The Graph implement an L2 Solution?
 
-Dzięki procesowi skalowania protokołu The Graph na L2, uczestnicy ekosystemu mogą liczyć na:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Ponad 26-krotną oszczędność na opłatach za gaz
 
@@ -14,7 +14,7 @@ Dzięki procesowi skalowania protokołu The Graph na L2, uczestnicy ekosystemu m
 
 - Bezpieczeństwo jako spuścizna sieci Ethereum
 
-Skalowanie smart kontraktów protokołu na L2 pozwala uczestnikom sieci na częstsze interakcje przy niższych opłatach za gaz. Na przykład, Indekserzy mogą otwierać i zamykać alokacje w celu indeksowania większej liczby subgrafów z większą częstotliwością, Deweloperzy mogą wdrażać i aktualizować subgrafy z większą łatwością, delegatorzy mogą delegować GRT ze zwiększoną częstotliwością, a kuratorzy mogą dodawać lub usuwać sygnał do większej liczby subgrafów - działania wcześniej uważane za zbyt kosztowne do częstego wykonywania ze względu na gaz.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 W zeszłym roku społeczność The Graph postanowiła pójść o krok do przodu z Arbitrum po wynikach dyskusji [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
@@ -41,27 +41,21 @@ By w pełni wykorzystać wszystkie zalety używania protokołu The Graph na L2 w
 
 ## Co powinien wiedzieć na ten temat subgraf developer, konsument danych, indekser, kurator lub delegator?
 
-Nie jest wymagane natychmiastowe podjęcie działań, jednak uczestnicy sieci są zachęcani do rozpoczęcia przenoszenia się do sieci Arbitrum, aby skorzystać z zalet L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Główne zespoły programistów pracują nad stworzeniem narzędzi do transferu L2, które znacznie ułatwią przeniesienie delegowania, kuratorowania i subgrafów do Arbitrum. Uczestnicy sieci mogą liczyć na dostęp do narzędzi transferu L2 do lata 2023 roku.
+All indexing rewards are now entirely on Arbitrum.
 
-Od 10 kwietnia 2023 roku 5% wszystkich nagród za indeksowanie jest emitowane w sieci Arbitrum. W miarę wzrostu udziału w sieci i zatwierdzenia przez Radę Fundacji The Graph, nagrody za indeksowanie stopniowo będą przenoszone z sieci Ethereum (L1) do sieci Arbitrum (L2), a ostatecznie całkowicie przeniosą się na Arbitrum.
-
-## Co trzeba zrobić by zacząć uczestniczyć w sieci Arbitrum (L2)?
-
-Prosimy o pomoc w [testowaniu sieci](https://testnet.thegraph.com/explorer) na L2 i zgłaszanie opinii na temat swoich doświadczeń na platformie [Discord](https://discord.gg/graphprotocol).
-
-## Czy w związku ze skalowaniem sieci do L2 wiąże się jakieś ryzyko?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Wszystko zostało dokładnie przetestowane i przygotowano plan awaryjny, aby zapewnić bezpieczne i płynne przeniesienie. Szczegóły można znaleźć [tutaj](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Czy subgrafy funkcjonujące już w sieci Ethereum, będą dalej działać?
+## Are existing subgraphs on Ethereum working?
 
-Tak. kontrakty z The Graph Network będą funkcjonować równolegle w sieciach Ethereum i Arbitrum dopóki nie nastąpi całkowite przeniesienie do sieci Arbitrum na późniejszym etapie.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Czy dla tokenu GRT zostanie wdrożony nowy smart kontrakt w sieci Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Tak, GRT ma dodatkowy [smart kontrakt na Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Jednak główna sieć Ethereum [kontrakt GRT](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) będzie nadal funkcjonować.
 

From 11583d8e8bcfac6ff456673b0a1f439f040cb8a6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:18 -0500
Subject: [PATCH 1054/1325] New translations arbitrum-faq.mdx (Portuguese)

---
 website/pages/pt/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/pt/arbitrum/arbitrum-faq.mdx b/website/pages/pt/arbitrum/arbitrum-faq.mdx
index 42fa0be68967..873be7d055ef 100644
--- a/website/pages/pt/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/pt/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Perguntas Frequentes do Arbitrum
 
 Clique [aqui](#billing-on-arbitrum-faqs) para pular até as Perguntas Frequentes de Cobranças no Arbitrum.
 
-## Por que o The Graph está a implementar uma Solução L2?
+## Why did The Graph implement an L2 Solution?
 
-Ao escalar o The Graph na L2, os participantes da rede podem:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Poupar até 26x em taxas de gas
 
@@ -14,7 +14,7 @@ Ao escalar o The Graph na L2, os participantes da rede podem:
 
 - Herdar segurança do Ethereum
 
-A escala dos contratos inteligentes do protocolo à L2 permite que os participantes da rede interajam com mais frequência por menos custos em taxas de gás. Por exemplo, os Indexadores podem abrir e fechar alocações para indexar um número maior de subgraphs com mais frequência; os programadores podem lançar e atualizar subgraphs com mais facilidade; os Delegadores podem delegar GRT com mais frequência; e os Curadores podem adicionar ou retirar sinais de um número maior de subgraphs–ações que, antigamente, eram consideradas caras demais para realizar com frequência devido ao gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 A comunidade do The Graph prosseguiu com o Arbitrum no ano passado, após o resultado da discussão [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
@@ -41,27 +41,21 @@ Para aproveitar o The Graph na L2, use este switcher de dropdown para alternar e
 
 ## Como um programador, consumidor de dados, Indexador, Curador ou Delegante, o que devo fazer agora?
 
-Não é necessário fazer nada imediatamente, mas participantes na rede são bem-vindos para começar a mudança ao Arbitrum para aproveitar os benefícios da L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-As equipas centrais de programação estão a trabalhar para criar ferramentas de transferência para L2, que facilitarão muito o movimento de delegação, curadoria e subgraphs ao Arbitrum. Os participantes da rede podem esperar que ferramentas de transferência estejam disponíveis até o fim de 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-Até 10 de abril de 2023, 5% de todas as recompensas de indexação eram mintadas no Arbitrum. À medida que a participação na rede aumenta, e que o Conselho a aprova, as recompensas de indexação serão movidas lentamente do Ethereum até o Arbitrum, até finalizar por completo a mudança ao Arbitrum.
-
-## Se eu quiser participar na rede na L2, o que devo fazer?
-
-Por favor, ajude a [testar a rede](https://testnet.thegraph.com/explorer) na L2 e informe-nos sobre a sua experiência no [Discord](https://discord.gg/graphprotocol).
-
-## Há algum risco associado ao escalamento da rede à L2?
+## Were there any risks associated with scaling the network to L2?
 
 Todos os contratos inteligentes já foram devidamente [auditados](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Tudo foi testado exaustivamente, e já está pronto um plano de contingência para garantir uma transição segura e suave. Mais detalhes [aqui](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Os subgraphs existentes no Ethereum continuarão a funcionar?
+## Are existing subgraphs on Ethereum working?
 
-Sim. Os contratos na Graph Network operarão em paralelo, tanto no Ethereum quanto no Arbitrum, até a migração completa ao Arbitrum numa data futura.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## O GRT terá um novo contrato inteligente lançado no Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Sim, o GRT tem um [contrato inteligente adicional no Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Porém, o [contrato do GRT](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) na mainnet do Ethereum continuará em operação.
 

From 905cde9c0211375e093f62ed811a7ad8f66fcef7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:19 -0500
Subject: [PATCH 1055/1325] New translations arbitrum-faq.mdx (Russian)

---
 website/pages/ru/arbitrum/arbitrum-faq.mdx | 34 +++++++++-------------
 1 file changed, 14 insertions(+), 20 deletions(-)

diff --git a/website/pages/ru/arbitrum/arbitrum-faq.mdx b/website/pages/ru/arbitrum/arbitrum-faq.mdx
index adfa3e6d5565..72bc0949212c 100644
--- a/website/pages/ru/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/ru/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Часто задаваемые вопросы об Arbitrum
 
 Нажмите [here](#billing-on-arbitrum-faqs), если хотите перейти к часто задаваемым вопросам о выставлении счетов Arbitrum.
 
-## Почему The Graph внедряет решение L2?
+## Почему The Graph внедрил решение L2?
 
-Масштабируя The Graph на L2, участники сети могут рассчитывать на:
+Масштабируя The Graph на L2, участники сети теперь могут получить следующие преимущества:
 
 - Экономию более чем в 26 раз на оплате газа
 
@@ -14,26 +14,26 @@ title: Часто задаваемые вопросы об Arbitrum
 
 - Безопасность, унаследованную от Ethereum
 
-Масштабирование смарт-контрактов протокола на L2 позволяет участникам сети взаимодействовать с сетью чаще при снижении затрат на оплату комиссии сети. Например, индексаторы могут открывать и закрывать выделения для индексации большего количества субграфов с большей частотой, разработчики могут с большей легкостью разворачивать и обновлять субграфы, делегаторы могут делегировать GRT с большей частотой, а кураторы могут добавлять или удалять сигнал для большего количества субграфов — действия, которые ранее считались слишком дорогостоящими для частого выполнения из-за высокой комиссии сети.
+Масштабирование смарт-контрактов протокола на L2 позволяет участникам сети взаимодействовать чаще и с меньшими затратами на комиссии за газ. Например, Индексаторы могут чаще открывать и закрывать аллокации, чтобы индексировать большее количество субграфов. Разработчики могут с большей легкостью разворачивать и обновлять субграфы, а Делегаторы — чаще делегировать GRT. Кураторы могут добавлять или удалять сигнал для большего количества субграфов — действия, которые ранее считались слишком затратными для частого выполнения из-за стоимости газа.
 
 Решение о продолжении сотрудничества с Arbitrum было принято в прошлом году по итогам обсуждения сообществом The Graph [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
 ## Что мне нужно сделать, чтобы использовать The Graph на L2?
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+Платежная система The Graph принимает GRT на Arbitrum, и пользователям потребуется ETH на Arbitrum для оплаты газа. Хотя протокол The Graph изначально был запущен на основной сети Ethereum, вся активность, включая платежные контракты, теперь проходит на Arbitrum One.
 
-Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Поэтому для оплаты запросов Вам потребуется GRT на Arbitrum. Вот несколько способов, как это можно сделать:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Если у Вас уже есть GRT на Ethereum, Вы можете перенести его на Arbitrum. Вы можете сделать это через опцию переноса GRT, доступную в Subgraph Studio, или с помощью одного из следующих мостов:
 
   - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
   - [TransferTo](https://transferto.xyz/swap)
 
-- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap.
+- Если у Вас есть другие активы на Arbitrum, Вы можете обменять их на GRT с помощью протокола обмена, такого как Uniswap.
 
-- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange.
+- В качестве альтернативы, Вы можете приобрести GRT напрямую на Arbitrum через децентрализованную биржу.
 
-Once you have GRT on Arbitrum, you can add it to your billing balance.
+Как только у Вас появится GRT на Arbitrum, Вы сможете добавить его к своему платежному балансу.
 
 Чтобы воспользоваться преимуществами использования The Graph на L2, используйте этот выпадающий список для переключения между сетями.
 
@@ -41,15 +41,9 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
 
 ## Что мне нужно делать сейчас как разработчику субграфа, потребителю данных, индексатору, куратору или делегатору?
 
-Немедленных действий не требуется, однако участникам сети рекомендуется начать переход на Arbitrum, чтобы воспользоваться преимуществами L2.
+Участники сети должны перейти на Arbitrum, чтобы продолжить участие в The Graph Network. Пожалуйста, обратитесь к [Руководству по инструменту переноса на L2](/arbitrum/l2-transfer-tools-guide/) для получения дополнительной помощи.
 
-Разработчики ядра работают над созданием инструментов для переноса на L2, что значительно упростит передачу делегирования, курирования и субграфов на Arbitrum. Участники сети могут рассчитывать на то, что инструменты переноса на L2 будут доступны к лету 2023 года.
-
-По состоянию на 10 апреля 2023 года 5% всех вознаграждений за индексацию чеканятся на Arbitrum. По мере увеличения участия в сети и одобрения Советом вознаграждения за индексацию будут постепенно переходить с Ethereum на Arbitrum и, в конечном итоге, полностью перейдут на Arbitrum.
-
-## Если я хочу принять участие в работе сети на L2, что мне следует сделать?
-
-Пожалуйста, помогите [протестировать сеть](https://testnet.thegraph.com/explorer) на L2 и оставьте отзыв о Вашем опыте в [Discord](https://discord.gg/graphprotocol).
+Все вознаграждения за индексацию теперь полностью находятся на Arbitrum.
 
 ## Существуют ли какие-либо риски, связанные с масштабированием сети до L2?
 
@@ -57,11 +51,11 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
 
 Все было тщательно протестировано, и разработан план действий на случай непредвиденных обстоятельств, чтобы обеспечить безопасный и непрерывный переход. Подробности можно найти [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Будут ли продолжать работать существующие субграфы в Ethereum?
+## Работают ли существующие субграфы на Ethereum?
 
-Да, контракты в сети The Graph Network будут работать параллельно как на Ethereum, так и на Arbitrum, пока в последствии полностью не перейдут на Arbitrum.
+Все субграфы теперь находятся на Arbitrum. Пожалуйста, обратитесь к [Руководству по инструменту переноса на L2](/arbitum/l2-transfer-tools-guide/), чтобы убедиться в бесперебойной работе своих субграфов.
 
-## Будет ли у GRT новый смарт-контракт, развернутый на Arbitrum?
+## Есть ли у GRT новый смарт-контракт, развернутый на Arbitrum?
 
 Да, у GRT есть дополнительный смарт-контракт [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Тем не менее, [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) в основной сети Ethereum останется в рабочем состоянии.
 

From 9c89f27e3b9bef2bfd62018b1ce898d3947350d0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:20 -0500
Subject: [PATCH 1056/1325] New translations arbitrum-faq.mdx (Swedish)

---
 website/pages/sv/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/sv/arbitrum/arbitrum-faq.mdx b/website/pages/sv/arbitrum/arbitrum-faq.mdx
index f454a4d1e420..2afe8b430db2 100644
--- a/website/pages/sv/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/sv/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum Vanliga frågor
 
 Klicka [here](#billing-on-arbitrum-faqs) om du vill hoppa till Arbitrum Billing Vanliga frågor.
 
-## Varför implementerar The Graf en L2 lösning?
+## Why did The Graph implement an L2 Solution?
 
-Genom att skala The Graf på L2 kan nätverksdeltagare förvänta sig:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Uppemot 26x besparingar på gasavgifter
 
@@ -14,7 +14,7 @@ Genom att skala The Graf på L2 kan nätverksdeltagare förvänta sig:
 
 - Säkerhet ärvt från Ethereum
 
-Genom att skala protokollets smarta kontrakt till L2 kan nätverksdeltagare interagera oftare till en reducerad kostnad i gasavgifter. Till exempel kan indexerare öppna och stänga allokeringar för att indexera ett större antal subgrafer med högre frekvens, utvecklare kan distribuera och uppdatera subgrafer med större lätthet, delegatorer kan delegera GRT med ökad frekvens och curatorer kan lägga till eller ta bort signaler till ett större antal subgrafer – åtgärder som tidigare ansågs vara för kostsamma för att utföra ofta på grund av gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 Graph gemenskapen beslutade att gå vidare med Arbitrum förra året efter resultatet av diskussionen [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305).
 
@@ -41,27 +41,21 @@ För att dra fördel av att använda The Graph på L2, använd den här rullgard
 
 ## Som subgrafutvecklare, datakonsument, indexerare, curator eller delegator, vad behöver jag göra nu?
 
-Det krävs inga omedelbara åtgärder, men nätverksdeltagare uppmuntras att börja flytta till Arbitrum för att dra nytta av fördelarna med L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Kärnutvecklarteam arbetar med att skapa L2 överföringsverktyg som kommer att göra det betydligt lättare att flytta delegering, kurering och subgrafer till Arbitrum. Nätverksdeltagare kan förvänta sig att L2 överföringsverktyg ska vara tillgängliga till sommaren 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-Från och med den 10 april 2023 präglas 5 % av alla indexeringsbelöningar på Arbitrum. När nätverksdeltagandet ökar, och när rådet godkänner det, kommer indexeringsbelöningar gradvis att flyttas från Ethereum till Arbitrum, och så småningom flyttas helt till Arbitrum.
-
-## Om jag skulle vilja delta i nätverket på L2, vad ska jag göra?
-
-Vänligen hjälp [testa nätverket](https://testnet.thegraph.com/explorer) på L2 och rapportera feedback om din upplevelse av [Discord](https://discord.gg/graphprotocol).
-
-## Finns det några risker med att skala nätverket till L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Allt har testats noggrant och en beredskapsplan finns på plats för att säkerställa en säker och sömlös övergång. Detaljer finns [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Kommer befintliga subgrafer på Ethereum att fortsätta att fungera?
+## Are existing subgraphs on Ethereum working?
 
-Ja, The Graph Nätverk kontrakt kommer att fungera parallellt på både Ethereum och Arbitrum tills de flyttas helt till Arbitrum vid ett senare tillfälle.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Kommer GRT att ha ett nytt smart kontrakt utplacerat på Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Ja, GRT har ytterligare ett [smart kontrakt på Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). Ethereums huvudnät [GRT-kontrakt](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) kommer dock att fortsätta att fungera.
 

From 57a97971b42d26638970a27eecb47ddea4f6ac9c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:21 -0500
Subject: [PATCH 1057/1325] New translations arbitrum-faq.mdx (Turkish)

---
 website/pages/tr/arbitrum/arbitrum-faq.mdx | 58 ++++++++++------------
 1 file changed, 26 insertions(+), 32 deletions(-)

diff --git a/website/pages/tr/arbitrum/arbitrum-faq.mdx b/website/pages/tr/arbitrum/arbitrum-faq.mdx
index b839c3a0d1f3..65ea8a73cdb7 100644
--- a/website/pages/tr/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/tr/arbitrum/arbitrum-faq.mdx
@@ -1,86 +1,80 @@
 ---
-title: Arbitrum FAQ
+title: Arbitrum Hakkında SSS
 ---
 
 Arbitrum Faturalama SSS bölümüne geçmek istiyorsanız [buraya](#billing-on-arbitrum-faqs) tıklayın.
 
-## Graph neden bir Katman2 Çözümü uyguluyor?
+## The Graph neden Katman 2 (L2) çözümü kullanıyor?
 
-Katman2'de Graph'ı ölçeklendirerek, ağ katılımcıları şunları bekleyebilir:
+Ağ katılımcıları, The Graph'i L2 üzerinde ölçeklendirerek şunlardan faydalanabilir:
 
 - Gas ücretlerinde 26 kata kadar tasarruf
 
-- Faster transaction speed
+- Daha hızlı işlemler
 
 - Ethereum'dan aktarılmış güvenlik
 
-Protokol akıllı sözleşmelerinin Katman2'ye ölçeklendirilmesi, ağ katılımcılarının gas ücretlerinde daha düşük bir maliyetle daha sık etkileşime girmesine olanak tanır. Örneğin, İndeksleyiciler daha fazla sayıda subgraph'ı daha sık indekslemek için tahsisleri açıp kapatabilir, geliştiriciler subgraphları daha kolay bir şekilde dağıtabilir ve güncelleyebilir, Delegatörler GRT'yi daha sık bir şekilde delege edebilir ve Küratörler daha önce gas nedeniyle sık sık gerçekleştirilemeyecek kadar maliyetli olduğu düşünülen, daha fazla sayıda subgraph'a sinyal ekleyebilir veya çıkarabilir.
+Protokol akıllı sözleşmelerini L2’ye ölçeklendirmek, ağ katılımcılarının daha düşük gas ücretleriyle daha sık etkileşimde bulunmasına olanak tanır. Örneğin, Endeksleyiciler daha fazla subgraph endekslemek için tahsisleri daha sık açıp kapatabilir. Geliştiriciler, subgraph’leri daha kolay bir şekilde dağıtabilir ve güncelleyebilir. Delegatörler, GRT’yi daha sık bir şekilde delege edebilir. Küratörler, daha fazla sayıda subgraph’e sinyal ekleyebilir veya kaldırabilir. Böylece önceden gas maliyetleri nedeniyle sık yapılması ekonomik olmayan işlemler artık mümkün hale gelir.
 
 Graph topluluğu, geçen yıl [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) tartışmasının sonucuna göre Arbitrum ile çalışmaya karar verdi.
 
 ## Graph'ı Katman2'de kullanmak için ne yapmam gerekiyor?
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+The Graph'in faturalandırma sistemi, Arbitrum ağı üzerinde GRT ile ödeme alır. Kullanıcıların gaz ücretlerini ödemek için Arbitrum üzerinde ETH'ye ihtiyaçları olacaktır. The Graph protokolü, başlangıçta Ethereum Mainnet üzerinde başlatılmış olsa da, faturalandırma sözleşmeleri de dahil olmak üzere tüm faaliyetler artık Arbitrum One üzerinde gerçekleştirilmektedir.
 
-Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+Dolayısıyla, sorgu ödemelerini yapmak için Arbitrum üzerinde GRT'ye ihtiyacınız var. İşte GRT elde etmenin birkaç farklı yolu:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- Ethereum üzerinde halihazırda GRT'leriniz varsa, bunları Arbitrum'a köprüleyebilirsiniz. Bu işlemi Subgraph Studio'da sunulan GRT köprüleme seçeneği aracılığıyla veya aşağıdaki köprülerden birini kullanarak yapabilirsiniz:
 
-  - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+  - [Arbitrum Köprüsü](https://bridge.arbitrum.io/?l2ChainId=42161)
   - [TransferTo](https://transferto.xyz/swap)
 
-- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap.
+- Arbitrum üzerinde başka varlıklarınız varsa, Uniswap gibi bir takas protokolü aracılığıyla varlıklarınızı GRT ile takas edebilirsiniz.
 
-- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange.
+- Alternatif olarak, GRT'yi doğrudan Arbitrum üzerinde merkeziyetsiz bir borsa aracılığıyla edinebilirsiniz.
 
-Once you have GRT on Arbitrum, you can add it to your billing balance.
+GRT tutarınız Arbitrum'a ulaşınca faturalandırma bakiyenize ekleyebilirsiniz.
 
 Graph'ı Katman2'de kullanmanın avantajlarından yararlanmak için, zincirler arasında geçiş yapma noktasında bu açılır anahtarı kullanın.
 
 ![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png)
 
-## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
+## Bir subgraph geliştirici, veri tüketicisi, Endeksleyici, Küratör veya Delegatör olarak şimdi ne yapmalıyım?
 
-Hemen yapılması gereken bir eylem yok, ancak ağ katılımcılarına Katman2'nin faydalarından yararlanmaları için Arbitrum'a geçmeye başlamaları önerilir.
+Ağ katılımcıları, The Graph Ağı'nda katılım göstermeye devam edebilmek için Arbitrum'a geçmek zorundadır. Ek destek için [L2 Transfer Aracı Kılavuzu](/arbitrum/l2-transfer-tools-guide/) sayfasına bakınız.
 
-Çekirdek geliştirici ekipleri, delegasyon, kürasyon ve subgraphları Arbitrum'a taşımayı önemli ölçüde kolaylaştıracak Katman2 transfer araçları oluşturmak için çalışıyor. Ağ katılımcıları, Katman2 aktarım araçlarının 2023 yazına kadar kullanıma sunulmasını bekleyebilirler.
+Tüm endeksleme ödülleri artık tamamen Arbitrum üzerindedir.
 
-10 Nisan 2023 itibarıyla, tüm endeksleme ödüllerinin %5'i Arbitrum'da üretilmektedir. Ağ katılımı arttıkça ve Konsey onayladıkça, endeksleme ödülleri Ethereum'dan Arbitrum'a doğru yavaşça kayacaktır ve nihayetinde tamamen Arbitrum'a geçecektir.
+## Ağı Katman 2'ye ölçeklendirmekle ilgili herhangi bir risk var mı?
 
-## Katman2'deki ağa katılmak istersem ne yapmalıyım?
-
-Lütfen Katman2'deki [ağı test etmeye](https://testnet.thegraph.com/explorer) yardımcı olun ve deneyiminizle ilgili [Discord](https://discord.gg/graphprotocol)'da geri bildirimde bulunun.
-
-## Ağı Katman2'ye ölçeklendirmekle ilgili herhangi bir risk var mı?
-
-All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
+Tüm akıllı sözleşmeler kapsamlı bir şekilde [denetlenmiştir](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Güvenli ve sorunsuz bir geçiş sağlamak için her şey kapsamlı bir şekilde test edilmiş ve bir acil durum planı hazırlanmıştır. Ayrıntıları [burada](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20) bulabilirsiniz.
 
-## Ethereum'daki mevcut subgraph'lar çalışmaya devam edecek mi?
+## Ethereum üzerindeki mevcut subgraph'ler çalışıyor mu?
 
-Evet, The Graph Ağı sözleşmeleri, daha sonraki bir tarihte tamamen Arbitrum'a taşınana kadar hem Ethereum hem de Arbitrum üzerinde paralel olarak çalışacaktır.
+Tüm subgraph'ler artık Arbitrum üzerindedir. Subgraph'lerinizin sorunsuz bir şekilde çalıştığından emin olmak için [L2 Transfer Aracı Kılavuzu](/arbitrum/l2-transfer-tools-guide/) sayfasını inceleyin.
 
-## GRT'nin Arbitrum'da dağıtılan yeni bir akıllı sözleşmesi olacak mı?
+## GRT'nin Arbitrum'da yeni bir akıllı sözleşmesi mi var?
 
 Evet, GRT'nin Arbitrum üzerinde ek bir [akıllı sözleşmesi](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7) bulunmaktadır. Ancak, Ethereum ana ağında bulunan [GRT sözleşmesi](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) çalışmaya devam edecektir.
 
 ## Arbitrum'da Faturalandırma SSS'leri
 
-## What do I need to do about the GRT in my billing balance?
+## Faturalandırma bakiyemdeki GRT için ne yapmam gerekiyor?
 
-Nothing! Your GRT has been securely migrated to Arbitrum and is being used to pay for queries as you read this.
+Hiçbir şey! GRT'niz güvenli bir şekilde Arbitrum'a taşındı ve bu satırları okuduğunuz sırada sorgular için kullanılmaktadır.
 
-## How do I know my funds have migrated securely to Arbitrum?
+## Fonlarımın güvenli bir şekilde Arbitrum'a taşındığını nasıl anlarım?
 
 Tüm GRT faturalandırma bakiyeleri Arbitrum'a başarıyla taşınmıştır. Arbitrum'daki faturalandırma sözleşmesini [buradan](https://arbiscan.io/address/0x1B07D3344188908Fb6DEcEac381f3eE63C48477a) görüntüleyebilirsiniz.
 
-## How do I know the Arbitrum bridge is secure?
+## Arbitrum köprüsünün güvenli olduğunu nasıl anlarım?
 
 Köprü, tüm kullanıcılar için emniyet ve güvenliği sağlamak amacıyla [kapsamlı bir şekilde denetlenmiştir](https://code4rena.com/contests/2022-10-the-graph-l2-bridge-contest).
 
-## What do I need to do if I'm adding fresh GRT from my Ethereum mainnet wallet?
+## Ethereum ana ağ cüzdanımdan yeni GRT ekliyorsam ne yapmam gerekiyor?
 
 GRT'yi Arbitrum faturalandırma bakiyenize eklemek [Subgraph Stüdyo'da](https://thegraph.com/studio/) tek bir tık ile yapılabilir. GRT'nizi Arbitrum'a kolayca köprüleyebilecek ve API anahtarlarınızı tek bir işlemle doldurabileceksiniz.
 
-Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT.
+GRT ekleme, çekme veya satın alma hakkında daha ayrıntılı talimatlar için [Faturalandırma sayfasını](/billing/) ziyaret edin.

From 754ff85c176ed3ebbe7e3f66580c9580532ee5d1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:22 -0500
Subject: [PATCH 1058/1325] New translations arbitrum-faq.mdx (Ukrainian)

---
 website/pages/uk/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/uk/arbitrum/arbitrum-faq.mdx b/website/pages/uk/arbitrum/arbitrum-faq.mdx
index 16104f2abf6b..560d2bf46563 100644
--- a/website/pages/uk/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/uk/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Найбільш поширені запитання по Arbitrum
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## Чому The Graph використовує рішення на L2?
+## Why did The Graph implement an L2 Solution?
 
-Внаслідок переходу The Graph на L2, користувачі мережі можуть очікувати:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitru
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
 
 ## Якщо я розробник підграфів, споживач даних, Індексатор, Куратор або Делегат, що мені потрібно робити зараз?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-As of April 10th, 2023, 5% of all indexing rewards are being minted on Arbitrum. As network participation increases, and as the Council approves it, indexing rewards will gradually shift from Ethereum to Arbitrum, eventually moving entirely to Arbitrum.
-
-## Якщо я хочу взяти участь у мережі на L2, що мені потрібно зробити?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Чи є якісь ризики, пов'язані з переходом мережі на L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Чи продовжать працювати вже наявні підграфи на Ethrereum?
+## Are existing subgraphs on Ethereum working?
 
-Так, звичайно, контракти в мережі The Graph будуть працювати одночасно на Ethereum та Arbitrum до моменту повного переходу на Arbitrum, який заплановано пізніше.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Чи розгорнутий на Arbitrum новий смартконтракт для GRT?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From 94d7783ed135b0a337385b7fa3323909b0400398 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:23 -0500
Subject: [PATCH 1059/1325] New translations arbitrum-faq.mdx (Chinese
 Simplified)

---
 website/pages/zh/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/zh/arbitrum/arbitrum-faq.mdx b/website/pages/zh/arbitrum/arbitrum-faq.mdx
index afdba606c23e..6ae6a6ccd818 100644
--- a/website/pages/zh/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/zh/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum网络常见问题解答
 
 如果您想跳到Arbitrum计费常见问题解答，请单击[here](#billing-on-arbitrum-faqs)。
 
-## 为什么Graph实施L2解决方案？
+## Why did The Graph implement an L2 Solution?
 
-通过缩放L2上的Graph，网络参与者可以预期：
+By scaling The Graph on L2, network participants can now benefit from:
 
 - 燃气费节省26倍以上
 
@@ -14,7 +14,7 @@ title: Arbitrum网络常见问题解答
 
 - 从以太坊继承的安全性
 
-将协议智能合约扩展到L2允许网络参与者更频繁地交互，同时降低了gas费用成本。例如，索引人可以打开和关闭已有分工，以更高的频率索引更多的子图，开发人员可以更轻松地部署和升级子图，委托人可以更频繁委托GRT，策展人可以添加或删除大量子图的信号，这些操作以前被认为成本太高，无法频繁执行。
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 去年，The Graph社区在[GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) 讨论的结果之后，决定推进Arbitrum。
 
@@ -41,27 +41,21 @@ Once you have GRT on Arbitrum, you can add it to your billing balance.
 
 ## 作为子图开发人员、数据消费者、索引人、策展人或授权者，我现在需要做什么？
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-核心开发团队正在努力创建迁移工具，这将大大简化将委托、策展和子图移动到Arbitrum的过程。网络参与者预计2023年4月将提供迁移工具。
+All indexing rewards are now entirely on Arbitrum.
 
-截至2023年4月10日，所有索引奖励的5%都在Arbitrum上铸造。随着网络参与度的增加，以及理事会的批准，索引奖励将逐渐从以太坊转移到Arbitrum，最终完全转移到Arbitrum。
-
-## 如果我想参加L2上的Graph网络，该怎么办？
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## 将网络扩展到L2是否存在任何风险？
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 所有事项已经经过了彻底测试，并制定了应急计划，以确保安全和无缝过渡。详细信息可以在这里 [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20)找到。
 
-## 以太坊上现有的子图会继续工作吗？
+## Are existing subgraphs on Ethereum working?
 
-是的，Graph网络合约将在以太坊和Arbitrum上并行运行，直到稍后完全迁移到Arbitrum。
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## GRT会在Arbitrum上部署新的智能合约吗？
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 是的，GRT在Arbitrum上有一个额外的智能合约[smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)。然而，以太坊主网上的GRT合约 [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7)将继续保持运营。
 

From a742cb00d0b18a0c949b5fcc9605d172927b9cdb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:24 -0500
Subject: [PATCH 1060/1325] New translations arbitrum-faq.mdx (Urdu (Pakistan))

---
 website/pages/ur/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/ur/arbitrum/arbitrum-faq.mdx b/website/pages/ur/arbitrum/arbitrum-faq.mdx
index 4e46325061e3..7e3277e62140 100644
--- a/website/pages/ur/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/ur/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: آربٹرم اکثر پوچھے گئے سوالات
 
 [یہاں](#billing-on-arbitrum-faqs) کلک کریں اگر آپ Arbitrum بلنگ FAQs پر جانا چاہتے ہیں۔
 
-## گراف ایک L2 حل کیوں نافذ کر رہا ہے؟
+## Why did The Graph implement an L2 Solution?
 
-L2 پر گراف کو سکیل کرنے سے، نیٹ ورک کے شرکاء توقع کر سکتے ہیں:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - گیس فیس پر 26 گنا زیادہ کی بچت
 
@@ -14,7 +14,7 @@ L2 پر گراف کو سکیل کرنے سے، نیٹ ورک کے شرکاء ت
 
 - سیکیورٹی ایتھیریم سے وراثت میں ملی
 
-پروٹوکول نیٹ ورک کے شرکاء کو گیس فیس میں کم قیمت پر زیادہ کثرت سے بات چیت کرنے کی اجازت دیتا ہے۔ یہ انڈیکسرز کو زیادہ تعداد میں سب گرافس کو انڈیکس کرنے کے قابل بناتا ہے، ڈویلپرز کو سب گرافس کو زیادہ آسانی کے ساتھ تعینات کرنے اور اپ ڈیٹ کرنے کی اجازت دیتا ہے، ڈیلیگیٹرز کو زیادہ سے زیادہ تعداد کے ساتھ GRT کو ڈیلیگیٹ کرنے کے قابل بناتا ہے، اور کیوریٹرز کو سب گراف کی ایک بڑی تعداد میں سگنل شامل کرنے کی صلاحیت فراہم کرتا ہے.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 گراف کمیونٹی نے [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) بحث کے نتائج کے بعد گزشتہ سال Arbitrum کے ساتھ آگے بڑھنے کا فیصلہ کیا۔
 
@@ -41,27 +41,21 @@ L2 پر گراف استعمال کرنے کا فائدہ اٹھانے کے لی
 
 ## بطور سب گراف ڈویلپر، ڈیٹا کنزیومر، انڈیکسر، کیوریٹر، یا ڈیلیگیٹر، مجھے اب کیا کرنے کی ضرورت ہے؟
 
-فوری طور پر کسی کارروائی کی ضرورت نہیں ہے، نیٹ ورک کے شرکاء کی حوصلہ افزائی کی جاتی ہے کہ وہ L2 کے فوائد سے فائدہ اٹھانے کے لیے Arbitrum میں جانا شروع کریں۔
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-کور ڈویلپر ٹیمیں مائیگریشن مددگار بنانے کے لیے کام کر رہی ہیں جو ڈیلیگیشن، کیوریشن، اور سب گراف کو Arbitrum میں منتقل کرنے میں نمایاں طور پر آسان بنائے گی۔ نیٹ ورک کے شرکاء اپریل 2023 میں مائیگریشن کے مددگاروں کے دستیاب ہونے کی توقع کر سکتے ہیں.
+All indexing rewards are now entirely on Arbitrum.
 
-10 اپریل 2023 تک، تمام انڈیکسنگ کے انعامات کا 5% آربٹرم پر دیا جا رہا ہے۔ جیسے جیسے نیٹ ورک کی شرکت میں اضافہ ہوتا ہے، اور جیسے ہی کونسل اسے منظور کرتی ہے، انڈیکسنگ کے انعامات آہستہ آہستہ ایتھریم سے آربٹرم میں منتقل ہوتے جائیں گے، بالآخر مکمل طور پر آربٹرم میں منتقل ہو جائیں گے.
-
-## اگر میں L2 پر نیٹ ورک میں حصہ لینا چاہتا ہوں تو مجھے کیا کرنا چاہیے؟
-
-براہ کرم L2 پر [نیٹ ورک](https://testnet.thegraph.com/explorer) کی جانچ کرنے میں مدد کریں اور [Discord](https://discord.gg/graphprotocol) میں اپنے تجربے کے بارے میں تاثرات کی اطلاع دیں.
-
-## کیا نیٹ ورک کو L2 کرنے سے متعلق کوئی خطرہ ہے؟
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 ہر چیز کی اچھی طرح جانچ کی گئی ہے، اور ایک محفوظ اور ہموار منتقلی کو یقینی بنانے کے لیے ایک ہنگامی منصوبہ تیار کیا گیا ہے۔ تفصیلات دیکھی جا سکتی ہیں [یہاں](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## کیا ایتھیریم پر موجودہ سب گراف کام کرتے رہیں گے؟
+## Are existing subgraphs on Ethereum working?
 
-جی ہاں، گراف نیٹ ورک کے کنٹریکٹس ایتھریم اور آربٹرم دونوں پر متوازی طور پر کام کریں گے جب تک کہ بعد کی تاریخ میں مکمل طور پر آربٹرم میں منتقل نہ ہو جائیں.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## کیا GRT کے پاس آربٹرم پر ایک نیا سمارٹ کنٹریکٹ تعینات ہوگا؟
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 ہاں، GRT کے پاس ایک اضافی [Arbitrum پر سمارٹ کنٹریکٹ] (https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)۔ تاہم، ایتھیریم مین نیٹ [GRT کنٹریکٹ] (https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) کا کام جاری رہے گا۔
 

From f54f9123061b24066d33967862d836fc001675e6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:25 -0500
Subject: [PATCH 1061/1325] New translations arbitrum-faq.mdx (Vietnamese)

---
 website/pages/vi/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/vi/arbitrum/arbitrum-faq.mdx b/website/pages/vi/arbitrum/arbitrum-faq.mdx
index a36b0103772f..9c12c8816259 100644
--- a/website/pages/vi/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/vi/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## Why is The Graph implementing an L2 Solution?
+## Why did The Graph implement an L2 Solution?
 
-By scaling The Graph on L2, network participants can expect:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ By scaling The Graph on L2, network participants can expect:
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle
 
 ## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-As of April 10th, 2023, 5% of all indexing rewards are being minted on Arbitrum. As network participation increases, and as the Council approves it, indexing rewards will gradually shift from Ethereum to Arbitrum, eventually moving entirely to Arbitrum.
-
-## If I would like to participate in the network on L2, what should I do?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Are there any risks associated with scaling the network to L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Will existing subgraphs on Ethereum continue to work?
+## Are existing subgraphs on Ethereum working?
 
-Yes, The Graph Network contracts will operate in parallel on both Ethereum and Arbitrum until moving fully to Arbitrum at a later date.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Will GRT have a new smart contract deployed on Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From c6782fd6b2743477301a815ef995b1b3d9bdca70 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:26 -0500
Subject: [PATCH 1062/1325] New translations arbitrum-faq.mdx (Marathi)

---
 website/pages/mr/arbitrum/arbitrum-faq.mdx | 24 ++++++++--------------
 1 file changed, 9 insertions(+), 15 deletions(-)

diff --git a/website/pages/mr/arbitrum/arbitrum-faq.mdx b/website/pages/mr/arbitrum/arbitrum-faq.mdx
index b72ce63a04ea..6a6ac6739ee8 100644
--- a/website/pages/mr/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/mr/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## Why is The Graph implementing an L2 Solution?
+## Why did The Graph implement an L2 Solution?
 
-By scaling The Graph on L2, network participants can expect:
+By scaling The Graph on L2, network participants can now benefit from:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,7 +14,7 @@ By scaling The Graph on L2, network participants can expect:
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
@@ -41,27 +41,21 @@ To take advantage of using The Graph on L2, use this dropdown switcher to toggle
 
 ## सबग्राफ डेव्हलपर, डेटा कंझ्युमर, इंडेक्सर, क्युरेटर किंवा डेलिगेटर म्हणून, मला आता काय करावे लागेल?
 
-There is no immediate action required, however, network participants are encouraged to begin moving to Arbitrum to take advantage of the benefits of L2.
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
 
-Core developer teams are working to create L2 transfer tools that will make it significantly easier to move delegation, curation, and subgraphs to Arbitrum. Network participants can expect L2 transfer tools to be available by summer of 2023.
+All indexing rewards are now entirely on Arbitrum.
 
-10 एप्रिल 2023 पर्यंत, सर्व इंडेक्सिंग रिवॉर्ड्सपैकी 5% आर्बिट्रमवर टाकले जात आहेत. जसजसा नेटवर्क सहभाग वाढतो, आणि काउन्सिलने त्याला मान्यता दिली तसतसे, अनुक्रमणिका बक्षिसे हळूहळू इथरियममधून आर्बिट्रममध्ये बदलली जातील, अखेरीस संपूर्णपणे आर्बिट्रमकडे जातील.
-
-## If I would like to participate in the network on L2, what should I do?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## Are there any risks associated with scaling the network to L2?
+## Were there any risks associated with scaling the network to L2?
 
 All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
 
-## Will existing subgraphs on Ethereum continue to work?
+## Are existing subgraphs on Ethereum working?
 
-होय, ग्राफ नेटवर्क कॉन्ट्रॅक्ट्स नंतरच्या तारखेला पूर्णपणे आर्बिट्रममध्ये जाईपर्यंत इथरियम आणि आर्बिट्रम दोन्हीवर समांतरपणे कार्य करतील.
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
 
-## Will GRT have a new smart contract deployed on Arbitrum?
+## Does GRT have a new smart contract deployed on Arbitrum?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 

From 7be029a1f31d86a6aaae52d194a2bb3bd78332ff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:27 -0500
Subject: [PATCH 1063/1325] New translations arbitrum-faq.mdx (Hindi)

---
 website/pages/hi/arbitrum/arbitrum-faq.mdx | 45 ++++++++++------------
 1 file changed, 20 insertions(+), 25 deletions(-)

diff --git a/website/pages/hi/arbitrum/arbitrum-faq.mdx b/website/pages/hi/arbitrum/arbitrum-faq.mdx
index a64a009e8616..b694353d661e 100644
--- a/website/pages/hi/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/hi/arbitrum/arbitrum-faq.mdx
@@ -4,9 +4,9 @@ title: Arbitrum FAQ
 
 Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
 
-## The Graph L2 Solution क्यों लागू कर रहा है?
+## The Graph ने L2 समाधान को लागू करने का कारण क्या था?
 
-L2 पर Graph को scale करके, network participants उम्मीद कर सकते हैं:
+ L2 पर The Graph को स्केल करके, नेटवर्क के प्रतिभागी अब निम्नलिखित लाभ उठा सकते हैं:
 
 - Upwards of 26x savings on gas fees
 
@@ -14,58 +14,53 @@ L2 पर Graph को scale करके, network participants उम्मी
 
 - Security inherited from Ethereum
 
-Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers could open and close allocations to index a greater number of subgraphs with greater frequency, developers could deploy and update subgraphs with greater ease, Delegators could delegate GRT with increased frequency, and Curators could add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+L2 पर प्रोटोकॉल स्मार्ट कॉन्ट्रैक्ट्स को स्केल करने से नेटवर्क के प्रतिभागियों को गैस शुल्क में कमी के साथ अधिक बार इंटरैक्ट करने की अनुमति मिलती है। उदाहरण के लिए, Indexer अधिक बार आवंटन खोल और बंद कर सकते हैं ताकि अधिक सबग्राफ़ को इंडेक्स किया जा सके। डेवलपर्स सबग्राफ़ को अधिक आसानी से तैनात और अपडेट कर सकते हैं, और डेलीगेटर्स अधिक बार GRT को डेलीगेट कर सकते हैं। क्यूरेटर अधिक सबग्राफ़ में सिग्नल जोड़ या हटा सकते हैं—ऐसे कार्य जो पहले गैस की उच्च लागत के कारण अक्सर करना बहुत महंगा माना जाता था।
 
 The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
 
 ## L2 पर ग्राफ़ का उपयोग करने के लिए मुझे क्या करना होगा?
 
-The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+The Graph का बिलिंग सिस्टम Arbitrum पर GRT स्वीकार करता है, और उपयोगकर्ताओं को गैस के लिए Arbitrum पर ETHकी आवश्यकता होगी। जबकि The Graph प्रोटोकॉल Ethereum Mainnet पर शुरू हुआ था, अब सभी गतिविधियाँ, जिसमें बिलिंग कॉन्ट्रैक्ट्स शामिल हैं, Arbitrum One पर हैं।
 
-Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+अत: क्वेरीज़ के लिए भुगतान करने के लिए, आपको Arbitrum पर GRT की आवश्यकता है। इसे प्राप्त करने के कुछ विभिन्न तरीके यहाँ दिए गए हैं:
 
-- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+- यदि आपके पास पहले से Ethereum पर GRT है, तो आप इसे Arbitrum पर ब्रिज कर सकते हैं। आप इसे Subgraph Studio में उपलब्ध GRT ब्रिजिंग विकल्प के माध्यम से या निम्नलिखित में से किसी एक ब्रिज का उपयोग करके कर सकते हैं:
 
   - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
   - [TransferTo](https://transferto.xyz/swap)
 
-- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap.
+- यदि आपके पास Arbitrum पर अन्य संपत्तियाँ हैं, तो आप उन्हें Uniswap जैसे स्वैपिंग प्रोटोकॉल के माध्यम से GRT में स्वैप कर सकते हैं।
 
-- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange.
+- वैकल्पिक रूप से, आप Arbitrum पर सीधे एक विकेन्द्रीकृत एक्सचेंज के माध्यम से GRT प्राप्त कर सकते हैं।
 
-Once you have GRT on Arbitrum, you can add it to your billing balance.
+एक बार जब आपके पास Arbitrum पर GRT हो, तो आप इसे अपनी बिलिंग बैलेंस में जोड़ सकते हैं।
 
 L2 पर द ग्राफ़ का उपयोग करने का लाभ उठाने के लिए, इस ड्रॉपडाउन स्विचर का उपयोग जंजीरों के बीच टॉगल करने के लिए करें।
 
 ![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png)
 
-## सबग्राफ डेवलपर, डेटा उपभोक्ता, इंडेक्सर, क्यूरेटर, या डेलिगेटर के रूप में, अब मुझे क्या करने की आवश्यकता है?
+## Subgraph developer, data consumer, Indexer, Curator, or Delegator, के रूप में, मुझे अब क्या करने की आवश्यकता है?
 
-तत्काल कार्रवाई की आवश्यकता नहीं है, हालांकि, नेटवर्क प्रतिभागियों को एल2 के लाभों का लाभ उठाने के लिए आर्बिट्रम में जाना शुरू करने के लिए प्रोत्साहित किया जाता है।
+नेटवर्क प्रतिभागियों को The Graph Network में भाग लेना जारी रखने के लिए Arbitrum पर स्थानांतरित होना होगा। अतिरिक्त सहायता के लिए कृपया [L2 ट्रांसफर टूल गाइड](/arbitrum/l2-transfer-tools-guide/) देखें।
 
-कोर डेवलपर टीमें एल2 ट्रांसफर टूल बनाने के लिए काम कर रही हैं, जिससे डेलिगेशन, क्यूरेशन और सबग्राफ को आर्बिट्रम में स्थानांतरित करना काफी आसान हो जाएगा। नेटवर्क प्रतिभागी उम्मीद कर सकते हैं कि 2023 की गर्मियों तक एल2 ट्रांसफर टूल उपलब्ध हो जाएंगे।
+अब सभी इंडेक्सिंग पुरस्कार पूरी तरह से Arbitrum पर हैं।
 
-10 अप्रैल, 2023 तक, सभी इंडेक्सिंग पुरस्कारों का 5% आर्बिट्रम पर खनन किया जा रहा है। जैसे-जैसे नेटवर्क की भागीदारी बढ़ती है, और जैसे ही परिषद इसे मंजूरी देती है, अनुक्रमण पुरस्कार धीरे-धीरे एथेरियम से आर्बिट्रम में स्थानांतरित हो जाएंगे, अंततः पूरी तरह से आर्बिट्रम में चले जाएंगे।
+## क्या नेटवर्क को L2 पर स्केल करने से संबंधित कोई जोखिम थे?
 
-## यदि मैं L2 पर नेटवर्क में भाग लेना चाहता हूँ, तो मुझे क्या करना चाहिए?
-
-Please help [test the network](https://testnet.thegraph.com/explorer) on L2 and report feedback about your experience in [Discord](https://discord.gg/graphprotocol).
-
-## क्या नेटवर्क को L2 तक स्केल करने से जुड़े कोई जोखिम हैं?
-
-All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
+सभी स्मार्ट कॉन्ट्रैक्ट्स का पूरी तरह से परीक्षित किया गया है।
+(https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 हर चीज़ का पूरी तरह से परीक्षण किया गया है, और एक सुरक्षित और निर्बाध संक्रमण सुनिश्चित करने के लिए एक आकस्मिक योजना बनाई गई है। विवरण यहां पाया जा सकता है [here] (https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and- सुरक्षा-विचार-20).
 
-## क्या एथेरियम पर मौजूदा सबग्राफ काम करना जारी रखेंगे?
+## क्या Ethereum पर मौजूद सबग्राफ़ काम कर रहे हैं?
 
-हां, द ग्राफ नेटवर्क कॉन्ट्रैक्ट बाद की तारीख में पूरी तरह से आर्बिट्रम में जाने तक एथेरियम और आर्बिट्रम दोनों पर समानांतर रूप से काम करेगा।
+अब सभी सबग्राफ़ Arbitrum पर हैं। सुनिश्चित करें कि आपके सबग्राफ़ सुचारू रूप से कार्य करते हैं, कृपया [L2 ट्रांसफर टूल गाइड](/arbitrum/l2-transfer-tools-guide/) देखें।
 
-## क्या जीआरटी के पास आर्बिट्रम पर एक नया स्मार्ट अनुबंध होगा?
+## क्या GRT का एक नया स्मार्ट कॉन्ट्रैक्ट Arbitrum पर तैनात किया गया है?
 
 Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
 
-## आर्बिट्रम एफएक्यू पर बिलिंग
+## Arbitrum पर बिलिंग FAQs
 
 ## मुझे अपने बिलिंग बैलेंस में GRT के बारे में क्या करना होगा?
 
@@ -83,4 +78,4 @@ The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the
 
 आपके आर्बिट्रम बिलिंग बैलेंस में जीआरटी जोड़ना [सबग्राफ स्टूडियो] (https://thegraph.com/studio/) में एक-क्लिक अनुभव के साथ किया जा सकता है। आप आसानी से अपने जीआरटी को आर्बिट्रम से जोड़ सकेंगे और एक लेनदेन में अपनी एपीआई कुंजी भर सकेंगे।
 
-Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT.
+कृपया अधिक विस्तृत निर्देशों के लिए [Billing page](/billing/) पर जाएं, जहाँ GRT जोड़ने, निकालने या प्राप्त करने के तरीके बताए गए हैं।

From 045a2689b8be90ac10c5833d1c6904ae5943d5fc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:28 -0500
Subject: [PATCH 1064/1325] New translations arbitrum-faq.mdx (Swahili)

---
 website/pages/sw/arbitrum/arbitrum-faq.mdx | 80 ++++++++++++++++++++++
 1 file changed, 80 insertions(+)
 create mode 100644 website/pages/sw/arbitrum/arbitrum-faq.mdx

diff --git a/website/pages/sw/arbitrum/arbitrum-faq.mdx b/website/pages/sw/arbitrum/arbitrum-faq.mdx
new file mode 100644
index 000000000000..9c12c8816259
--- /dev/null
+++ b/website/pages/sw/arbitrum/arbitrum-faq.mdx
@@ -0,0 +1,80 @@
+---
+title: Arbitrum FAQ
+---
+
+Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitrum Billing FAQs.
+
+## Why did The Graph implement an L2 Solution?
+
+By scaling The Graph on L2, network participants can now benefit from:
+
+- Upwards of 26x savings on gas fees
+
+- Faster transaction speed
+
+- Security inherited from Ethereum
+
+Scaling the protocol smart contracts onto L2 allows network participants to interact more frequently at a reduced cost in gas fees. For example, Indexers can open and close allocations more frequently to index a greater number of subgraphs. Developers can deploy and update subgraphs more easily, and Delegators can delegate GRT more frequently. Curators can add or remove signal to a larger number of subgraphs–actions previously considered too cost-prohibitive to perform frequently due to gas.
+
+The Graph community decided to move forward with Arbitrum last year after the outcome of the [GIP-0031](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) discussion.
+
+## What do I need to do to use The Graph on L2?
+
+The Graph’s billing system accepts GRT on Arbitrum, and users will need ETH on Arbitrum to pay their gas. While The Graph protocol started on Ethereum Mainnet, all activity, including the billing contracts, is now on Arbitrum One.
+
+Consequently, to pay for queries, you need GRT on Arbitrum. Here are a few different ways to achieve this:
+
+- If you already have GRT on Ethereum, you can bridge it to Arbitrum. You can do this via the GRT bridging option provided in Subgraph Studio or by using one of the following bridges:
+
+  - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
+  - [TransferTo](https://transferto.xyz/swap)
+
+- If you have other assets on Arbitrum, you can swap them for GRT through a swapping protocol like Uniswap.
+
+- Alternatively, you can acquire GRT directly on Arbitrum through a decentralized exchange.
+
+Once you have GRT on Arbitrum, you can add it to your billing balance.
+
+To take advantage of using The Graph on L2, use this dropdown switcher to toggle between chains.
+
+![Dropdown switcher to toggle Arbitrum](/img/arbitrum-screenshot-toggle.png)
+
+## As a subgraph developer, data consumer, Indexer, Curator, or Delegator, what do I need to do now?
+
+Network participants must move to Arbitrum to continue participating in The Graph Network. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) for additional support.
+
+All indexing rewards are now entirely on Arbitrum.
+
+## Were there any risks associated with scaling the network to L2?
+
+All smart contracts have been thoroughly [audited](https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
+
+Everything has been tested thoroughly, and a contingency plan is in place to ensure a safe and seamless transition. Details can be found [here](https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and-security-considerations-20).
+
+## Are existing subgraphs on Ethereum working?
+
+All subgraphs are now on Arbitrum. Please refer to [L2 Transfer Tool Guide](/arbitrum/l2-transfer-tools-guide/) to ensure your subgraphs operate seamlessly.
+
+## Does GRT have a new smart contract deployed on Arbitrum?
+
+Yes, GRT has an additional [smart contract on Arbitrum](https://arbiscan.io/address/0x9623063377ad1b27544c965ccd7342f7ea7e88c7). However, the Ethereum mainnet [GRT contract](https://etherscan.io/token/0xc944e90c64b2c07662a292be6244bdf05cda44a7) will remain operational.
+
+## Billing on Arbitrum FAQs
+
+## What do I need to do about the GRT in my billing balance?
+
+Nothing! Your GRT has been securely migrated to Arbitrum and is being used to pay for queries as you read this.
+
+## How do I know my funds have migrated securely to Arbitrum?
+
+All GRT billing balances have already been successfully migrated to Arbitrum. You can view the billing contract on Arbitrum [here](https://arbiscan.io/address/0x1B07D3344188908Fb6DEcEac381f3eE63C48477a).
+
+## How do I know the Arbitrum bridge is secure?
+
+The bridge has been [heavily audited](https://code4rena.com/contests/2022-10-the-graph-l2-bridge-contest) to ensure safety and security for all users.
+
+## What do I need to do if I'm adding fresh GRT from my Ethereum mainnet wallet?
+
+Adding GRT to your Arbitrum billing balance can be done with a one-click experience in [Subgraph Studio](https://thegraph.com/studio/). You'll be able to easily bridge your GRT to Arbitrum and fill your API keys in one transaction.
+
+Visit the [Billing page](/billing/) for more detailed instructions on adding, withdrawing, or acquiring GRT.

From 7c9c17f3490cd979cab8bc453aa52bc41c5790bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:30 -0500
Subject: [PATCH 1065/1325] New translations l2-transfer-tools-faq.mdx (French)

---
 website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx
index 45ec79e9d4f9..d43463682da5 100644
--- a/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx
@@ -336,11 +336,13 @@ Si vous n’avez transféré aucun solde de contrat de vesting à L2 et que votr
 
 ### J’utilise mon contrat de vesting pour investir dans mainnet. Puis-je transférer ma participation à Arbitrum?
 
-Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat d’acquisition L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat d’acquisition dans Explorer. Si votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
+Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat d’acquisition L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat d’acquisition dans Explorer. Si
+votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
 
 ### J’utilise mon contrat de vesting pour déléguer sur mainnet. Puis-je transférer mes délégations à Arbitrum?
 
-Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat de vesting L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat de vesting dans Explorer. Si votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
+Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat de vesting L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat de vesting dans Explorer. Si
+votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
 
 ### Puis-je spécifier un bénéficiaire différent pour mon contrat de vesting sur L2?
 

From 1871c4e0b1fb9e8597c50ba05e55ae4ddfd02b4c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:32 -0500
Subject: [PATCH 1066/1325] New translations l2-transfer-tools-faq.mdx (Arabic)

---
 website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx
index 22b4d7efd398..250f550bcacd 100644
--- a/website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/ar/arbitrum/l2-transfer-tools-faq.mdx
@@ -46,7 +46,7 @@ If you have the L1 transaction hash (which you can find by looking at the recent
 
 2. انتظر 20 دقيقة للتأكيد
 
-3. قم بتأكيد نقل الـ subgraph على Arbitrum \\ \*
+3. قم بتأكيد نقل الـ subgraph على Arbitrum \ \*
 
 4. قم بإنهاء نشر الـ subgraph على Arbitrum
 
@@ -200,11 +200,11 @@ The tokens that are being undelegated are "locked" and therefore cannot be trans
 
 1. ابدأ نقل الإشارة على شبكة Ethereum mainnet
 
-2. حدد عنوان L2 للمنسق \\ \*
+2. حدد عنوان L2 للمنسق \ \*
 
 3. انتظر 20 دقيقة للتأكيد
 
-\\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
+\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
 
 ### كيف سأعرف ما إذا كان الرسم البياني الفرعي الذي قمت بعمل إشارة تنسيق عليه قد انتقل إلى L2؟
 
@@ -250,7 +250,7 @@ The tokens that are being undelegated are "locked" and therefore cannot be trans
 
 ### كم من الوقت لدي لتأكيد تحويل حصتي إلى Arbitrum؟
 
-\\ _ \\ _ \\ \* يجب تأكيد معاملتك لإتمام تحويل الحصة على Arbitrum. يجب إكمال هذه الخطوة في غضون 7 أيام وإلا فقد يتم فقدان الحصة.
+\ _ \ _ \ \* يجب تأكيد معاملتك لإتمام تحويل الحصة على Arbitrum. يجب إكمال هذه الخطوة في غضون 7 أيام وإلا فقد يتم فقدان الحصة.
 
 ### ماذا لو كان لدي تخصيصات مفتوحة؟
 
@@ -366,13 +366,13 @@ Yes! The process is a bit different, because vesting contracts can't forward the
 
 3. امنح البروتوكول حق الوصول إلى عقد الاستحقاق (سيسمح لعقدك بالتفاعل مع أداة التحويل)
 
-4. حدد عنوان المستفيد على L2 \\ \* وابدأ في تحويل الرصيد على Ethereum mainnet
+4. حدد عنوان المستفيد على L2 \ \* وابدأ في تحويل الرصيد على Ethereum mainnet
 
 5. انتظر 20 دقيقة للتأكيد
 
 6. قم بتأكيد تحويل الرصيد على L2
 
-\\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
+\ \* إذا لزم الأمر -أنت تستخدم عنوان عقد.
 
 \*\*\*\*You must confirm your transaction to complete the balance transfer on Arbitrum. This step must be completed within 7 days or the balance could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).
 

From 96d06ab93c0909f6f33b6e01c5022958ec8089a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:33 -0500
Subject: [PATCH 1067/1325] New translations l2-transfer-tools-faq.mdx (German)

---
 .../pages/de/arbitrum/l2-transfer-tools-faq.mdx  | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx
index eb4fda3fc003..48944eebbfbb 100644
--- a/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx
@@ -2,23 +2,23 @@
 title: L2-Übertragungs-Tools FAQ
 ---
 
-## General
+## Allgemein
 
 ### Was sind L2-Transfer-Tools?
 
-The Graph has made it 26x cheaper for contributors to participate in the network by deploying the protocol to Arbitrum One. The L2 Transfer Tools were created by core devs to make it easy to move to L2.
+The Graph hat die Teilnahme am Netzwerk für Mitwirkende um das 26-fache kostengünstiger gemacht, indem das Protokoll auf Arbitrum One bereitgestellt wurde. Die L2-Transfer-Tools wurden von den Kernentwicklern entwickelt, um den Wechsel zu L2 zu erleichtern.
 
-For each network participant, a set of L2 Transfer Tools are available to make the experience seamless when moving to L2, avoiding thawing periods or having to manually withdraw and bridge GRT.
+Für jeden Netzwerkteilnehmer stehen eine Reihe von L2-Transfer-Tools zur Verfügung, die einen nahtlosen Übergang zu L2 ermöglichen, ohne dass Auftauzeiten entstehen oder GRT manuell entnommen und überbrückt werden müssen.
 
-These tools will require you to follow a specific set of steps depending on what your role is within The Graph and what you are transferring to L2.
+Für diese Tools müssen Sie eine Reihe von Schritten befolgen, je nachdem, welche Rolle Sie bei The Graph spielen und was Sie auf L2 übertragen.
 
 ### Kann ich dieselbe Wallet verwenden, die ich im Ethereum Mainnet benutze?
 
 Wenn Sie eine [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) Wallet verwenden, können Sie dieselbe Adresse verwenden. Wenn Ihr Ethereum Mainnet Wallet ein Kontrakt ist (z.B. ein Multisig), dann müssen Sie eine [Arbitrum Wallet Adresse](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) angeben, an die Ihr Transfer gesendet wird. Bitte überprüfen Sie die Adresse sorgfältig, da Überweisungen an eine falsche Adresse zu einem dauerhaften Verlust führen können. Wenn Sie einen Multisig auf L2 verwenden möchten, stellen Sie sicher, dass Sie einen Multisig-Vertrag auf Arbitrum One einsetzen.
 
-Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else.
+Wallets auf EVM-Blockchains wie Ethereum und Arbitrum bestehen aus einem Paar von Schlüsseln (öffentlich und privat), die Sie erstellen, ohne mit der Blockchain interagieren zu müssen. Jede Wallet, die für Ethereum erstellt wurde, funktioniert also auch auf Arbitrum, ohne dass Sie etwas anderes tun müssen.
 
-The exception is with smart contract wallets like multisigs: these are smart contracts that are deployed separately on each chain, and get their address when they are deployed. If a multisig was deployed to Ethereum, it won't exist with the same address on Arbitrum. A new multisig must be created first on Arbitrum, and may get a different address.
+Die Ausnahme sind Smart-Contract-Wallets wie Multisigs: Das sind Smart Contracts, die auf jeder Kette separat eingesetzt werden und ihre Adresse erhalten, wenn sie eingesetzt werden. Wenn ein Multisig auf Ethereum bereitgestellt wurde, wird er nicht mit der gleichen Adresse auf Arbitrum existieren. Ein neuer Multisig muss zuerst auf Arbitrum erstellt werden und kann eine andere Adresse erhalten.
 
 ### Was passiert, wenn ich meinen Transfer nicht innerhalb von 7 Tagen abschließe?
 
@@ -28,7 +28,7 @@ Wenn Sie Ihre Vermögenswerte (Subgraph, Anteil, Delegation oder Kuration) an L2
 
 Dies ist der so genannte "Bestätigungsschritt" in allen Übertragungswerkzeugen - er wird in den meisten Fällen automatisch ausgeführt, da die automatische Ausführung meist erfolgreich ist, aber es ist wichtig, dass Sie sich vergewissern, dass die Übertragung erfolgreich war. Wenn dies nicht gelingt und es innerhalb von 7 Tagen keine erfolgreichen Wiederholungsversuche gibt, verwirft die Arbitrum-Brücke das Ticket, und Ihre Assets (Subgraph, Pfahl, Delegation oder Kuration) gehen verloren und können nicht wiederhergestellt werden. Die Entwickler des Graph-Kerns haben ein Überwachungssystem eingerichtet, um diese Situationen zu erkennen und zu versuchen, die Tickets einzulösen, bevor es zu spät ist, aber es liegt letztendlich in Ihrer Verantwortung, sicherzustellen, dass Ihr Transfer rechtzeitig abgeschlossen wird. Wenn Sie Probleme mit der Bestätigung Ihrer Transaktion haben, wenden Sie sich bitte an [dieses Formular] (https://noteforms.com/forms/notionform-l2-transfer-tooling-issues-0ogqfu?notionforms=1&utm_source=notionforms) und die Entwickler des Kerns werden Ihnen helfen.
 
-### I started my delegation/stake/curation transfer and I'm not sure if it made it through to L2, how can I confirm that it was transferred correctly?
+### Ich habe mit der Übertragung meiner Delegation/des Einsatzes/der Kuration begonnen und bin mir nicht sicher, ob sie an L2 weitergeleitet wurde. Wie kann ich bestätigen, dass sie korrekt übertragen wurde?
 
 If you don't see a banner on your profile asking you to finish the transfer, then it's likely the transaction made it safely to L2 and no more action is needed. If in doubt, you can check if Explorer shows your delegation, stake or curation on Arbitrum One.
 
@@ -64,7 +64,7 @@ Die Übertragungszeit beträgt etwa 20 Minuten. Die Arbitrum-Brücke arbeitet im
 
 ### Wird mein Subgraph noch auffindbar sein, nachdem ich ihn auf L2 übertragen habe?
 
-Ihr Subgraph ist nur in dem Netzwerk auffindbar, in dem er veröffentlicht ist. Wenn Ihr Subgraph zum Beispiel auf Arbitrum One ist, können Sie ihn nur im Explorer auf Arbitrum One finden und nicht auf Ethereum. Bitte vergewissern Sie sich, dass Sie Arbitrum One in der Netzwerkumschaltung oben auf der Seite ausgewählt haben, um sicherzustellen, dass Sie sich im richtigen Netzwerk befinden. Nach der Übertragung wird der L1-Subgraph als veraltet angezeigt.
+Ihr Subgraph ist nur in dem Netzwerk auffindbar, in dem er veröffentlicht ist. Wenn Ihr Subgraph zum Beispiel auf Arbitrum One ist, können Sie ihn nur im Explorer auf Arbitrum One finden und nicht auf Ethereum. Bitte vergewissern Sie sich, dass Sie Arbitrum One in der Netzwerkumschaltung oben auf der Seite ausgewählt haben, um sicherzustellen, dass Sie sich im richtigen Netzwerk befinden.  Nach der Übertragung wird der L1-Subgraph als veraltet angezeigt.
 
 ### Muss mein Subgraph ( Teilgraph ) veröffentlicht werden, um ihn zu übertragen?
 

From 36e2ddcbd46126400122f10cb38849a3d47752cc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:35 -0500
Subject: [PATCH 1068/1325] New translations l2-transfer-tools-faq.mdx
 (Japanese)

---
 website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx
index 06814d41c7c3..9885a24b3c6c 100644
--- a/website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/ja/arbitrum/l2-transfer-tools-faq.mdx
@@ -52,7 +52,7 @@ L1トランザクションのハッシュを持っている場合（これはウ
 
 5. クエリ URL を更新 (推奨)
 
-\*注意：7日以内に転送を確認する必要があります。それ以外の場合、サブグラフが失われる可能性があります。ほとんどの場合、このステップは自動的に実行されますが、Arbitrumでガス価格が急上昇した場合には手動で確認する必要があるかもしれません。このプロセス中に問題が発生した場合、サポートを受けるためのリソースが用意されています：support@thegraph.com に連絡するか、[Discord](https://discord.gg/graphprotocol)でお問い合わせください\\。
+\*注意：7日以内に転送を確認する必要があります。それ以外の場合、サブグラフが失われる可能性があります。ほとんどの場合、このステップは自動的に実行されますが、Arbitrumでガス価格が急上昇した場合には手動で確認する必要があるかもしれません。このプロセス中に問題が発生した場合、サポートを受けるためのリソースが用意されています：support@thegraph.com に連絡するか、[Discord](https://discord.gg/graphprotocol)でお問い合わせください\。
 
 ### どこから転送を開始すればよいですか?
 

From 3762ce72a38f81c07e02a479b416a62525ff5136 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:36 -0500
Subject: [PATCH 1069/1325] New translations l2-transfer-tools-faq.mdx (Korean)

---
 website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx
index de12152a1f00..602b2a2c3aa2 100644
--- a/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx
@@ -22,7 +22,8 @@ The exception is with smart contract wallets like multisigs: these are smart con
 
 ### 만약 7일 안에 이체를 완료하지 못하면 어떻게 되나요?
 
-L2 전송 도구는 Arbitrum의 기본 메커니즘을 사용하여 L1에서 L2로 메시지를 보냅니다. 이 메커니즘은 "재시도 가능한 티켓"이라고 하며 Arbitrum GRT 브리지를 포함한 모든 네이티브 토큰 브리지를 사용하여 사용됩니다. 재시도 가능한 티켓에 대해 자세히 읽을 수 있습니다 [Arbitrum 문서] (https://docs.arbitrum.io/arbos/l1-to-l2-messaging).
+L2 전송 도구는 Arbitrum의 기본 메커니즘을 사용하여 L1에서 L2로 메시지를 보냅니다. 이 메커니즘은 "재시도 가능한 티켓"이라고 하며 Arbitrum GRT 브리지를 포함한 모든 네이티브 토큰 브리지를 사용하여 사용됩니다. 재시도 가능한 티켓에 대해 자세히 읽을 수 있습니다 [Arbitrum 문서] 
+(https://docs.arbitrum.io/arbos/l1-to-l2-messaging).
 
 자산(하위 그래프, 스테이크, 위임 또는 큐레이션) 을 L2로 이전하면 L2에서 재시도 가능한 티켓을 생성하는 Arbitrum GRT 브리지를 통해 메시지가 전송됩니다. 전송 도구에는 거래에 일부 ETH 값이 포함되어 있으며, 이는 1) 티켓 생성 비용을 지불하고 2) L2에서 티켓을 실행하기 위해 가스 비용을 지불하는 데 사용됩니다. 그러나 티켓이 L2에서 실행될 준비가 될 때까지 가스 가격이 시간에 따라 달라질 수 있으므로 이 자동 실행 시도가 실패할 수 있습니다. 그런 일이 발생하면 Arbitrum 브릿지는 재시도 가능한 티켓을 최대 7일 동안 유지하며 누구나 티켓 "사용"을 재시도할 수 있습니다(Arbitrum에 브릿지된 일부 ETH가 있는 지갑이 필요함).
 
@@ -40,6 +41,8 @@ If you have the L1 transaction hash (which you can find by looking at the recent
 
 <VideoEmbed youtube="R8_vz4lx2Co" />
 
+
+
 1. 이더리움 메인넷에서 전송 시작
 
 2. 확인을 위해 20분 정도 기다리세요

From 2173c07516edeeea8b9e18dff06fd21a68f1e814 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:38 -0500
Subject: [PATCH 1070/1325] New translations l2-transfer-tools-faq.mdx (Polish)

---
 website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx
index e74cfdb59413..7ce69aeab929 100644
--- a/website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/pl/arbitrum/l2-transfer-tools-faq.mdx
@@ -118,9 +118,9 @@ Aby przesłać delegację, należy wykonać następujące kroki:
 
 If the Indexer to whom you're delegating is still operating on L1, when you transfer to Arbitrum you will forfeit any delegation rewards from open allocations on Ethereum mainnet. This means that you will lose the rewards from, at most, the last 28-day period. If you time the transfer right after the Indexer has closed allocations you can make sure this is the least amount possible. If you have a communication channel with your Indexer(s), consider discussing with them to find the best time to do your transfer.
 
-### Co się stanie, jeśli indeksator, do którego obecnie deleguję, nie jest dostępny w Arbitrum One?
+### What happens if the Indexer I currently delegate to isn't on Arbitrum One?
 
-Narzędzie przesyłania L2 aktywuje się tylko wtedy, gdy delegowany przez Ciebie indeksator prześle swój stake do Arbitrum.
+The L2 transfer tool will only be enabled if the Indexer you have delegated to has transferred their own stake to Arbitrum.
 
 ### Czy Delegaci mają możliwość delegowania do innego Indeksera?
 

From 06802de3cc27785330a3e8932eb85ac526991d4a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:45 -0500
Subject: [PATCH 1071/1325] New translations l2-transfer-tools-faq.mdx
 (Swahili)

---
 .../sw/arbitrum/l2-transfer-tools-faq.mdx     | 411 ++++++++++++++++++
 1 file changed, 411 insertions(+)
 create mode 100644 website/pages/sw/arbitrum/l2-transfer-tools-faq.mdx

diff --git a/website/pages/sw/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/sw/arbitrum/l2-transfer-tools-faq.mdx
new file mode 100644
index 000000000000..b075b7548fb8
--- /dev/null
+++ b/website/pages/sw/arbitrum/l2-transfer-tools-faq.mdx
@@ -0,0 +1,411 @@
+---
+title: L2 Transfer Tools FAQ
+---
+
+## General
+
+### What are L2 Transfer Tools?
+
+The Graph has made it 26x cheaper for contributors to participate in the network by deploying the protocol to Arbitrum One. The L2 Transfer Tools were created by core devs to make it easy to move to L2.
+
+For each network participant, a set of L2 Transfer Tools are available to make the experience seamless when moving to L2, avoiding thawing periods or having to manually withdraw and bridge GRT.
+
+These tools will require you to follow a specific set of steps depending on what your role is within The Graph and what you are transferring to L2.
+
+### Can I use the same wallet I use on Ethereum mainnet?
+
+If you are using an [EOA](https://ethereum.org/en/developers/docs/accounts/#types-of-account) wallet you can use the same address. If your Ethereum mainnet wallet is a contract (e.g. a multisig) then you must specify an [Arbitrum wallet address](/arbitrum/arbitrum-faq/#what-do-i-need-to-do-to-use-the-graph-on-l2) where your transfer will be sent. Please check the address carefully as any transfers to an incorrect address can result in permanent loss. If you'd like to use a multisig on L2, make sure you deploy a multisig contract on Arbitrum One.
+
+Wallets on EVM blockchains like Ethereum and Arbitrum are a pair of keys (public and private), that you create without any need to interact with the blockchain. So any wallet that was created for Ethereum will also work on Arbitrum without having to do anything else.
+
+The exception is with smart contract wallets like multisigs: these are smart contracts that are deployed separately on each chain, and get their address when they are deployed. If a multisig was deployed to Ethereum, it won't exist with the same address on Arbitrum. A new multisig must be created first on Arbitrum, and may get a different address.
+
+### What happens if I don’t finish my transfer in 7 days?
+
+The L2 Transfer Tools use Arbitrum’s native mechanism to send messages from L1 to L2. This mechanism is called a “retryable ticket” and is used by all native token bridges, including the Arbitrum GRT bridge. You can read more about retryable tickets in the [Arbitrum docs](https://docs.arbitrum.io/arbos/l1-to-l2-messaging).
+
+When you transfer your assets (subgraph, stake, delegation or curation) to L2, a message is sent through the Arbitrum GRT bridge which creates a retryable ticket in L2. The transfer tool includes some ETH value in the transaction, that is used to 1) pay to create the ticket and 2) pay for the gas to execute the ticket in L2. However, because gas prices might vary in the time until the ticket is ready to execute in L2, it is possible that this auto-execution attempt fails. When that happens, the Arbitrum bridge will keep the retryable ticket alive for up to 7 days, and anyone can retry “redeeming” the ticket (which requires a wallet with some ETH bridged to Arbitrum).
+
+This is what we call the “Confirm” step in all the transfer tools - it will run automatically in most cases, as the auto-execution is most often successful, but it is important that you check back to make sure it went through. If it doesn’t succeed and there are no successful retries in 7 days, the Arbitrum bridge will discard the ticket, and your assets (subgraph, stake, delegation or curation) will be lost and can’t be recovered. The Graph core devs have a monitoring system in place to detect these situations and try to redeem the tickets before it’s too late, but it is ultimately your responsibility to ensure your transfer is completed in time. If you’re having trouble confirming your transaction, please reach out using [this form](https://noteforms.com/forms/notionform-l2-transfer-tooling-issues-0ogqfu?notionforms=1&utm_source=notionforms) and core devs will be there help you.
+
+### I started my delegation/stake/curation transfer and I'm not sure if it made it through to L2, how can I confirm that it was transferred correctly?
+
+If you don't see a banner on your profile asking you to finish the transfer, then it's likely the transaction made it safely to L2 and no more action is needed. If in doubt, you can check if Explorer shows your delegation, stake or curation on Arbitrum One.
+
+If you have the L1 transaction hash (which you can find by looking at the recent transactions in your wallet), you can also confirm if the "retryable ticket" that carried the message to L2 was redeemed here: https://retryable-dashboard.arbitrum.io/ - if the auto-redeem failed, you can also connect your wallet there and redeem it. Rest assured that core devs are also monitoring for messages that get stuck, and will attempt to redeem them before they expire.
+
+## Subgraph Transfer
+
+### How do I transfer my subgraph?
+
+<VideoEmbed youtube="R8_vz4lx2Co" />
+
+To transfer your subgraph, you will need to complete the following steps:
+
+1. Initiate the transfer on Ethereum mainnet
+
+2. Wait 20 minutes for confirmation
+
+3. Confirm subgraph transfer on Arbitrum\*
+
+4. Finish publishing subgraph on Arbitrum
+
+5. Update Query URL (recommended)
+
+\*Note that you must confirm the transfer within 7 days otherwise your subgraph may be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).
+
+### Where should I initiate my transfer from?
+
+You can initiate your transfer from the [Subgraph Studio](https://thegraph.com/studio/), [Explorer,](https://thegraph.com/explorer) or any subgraph details page. Click the "Transfer Subgraph" button in the subgraph details page to start the transfer.
+
+### How long do I need to wait until my subgraph is transferred
+
+The transfer time takes approximately 20 minutes. The Arbitrum bridge is working in the background to complete the bridge transfer automatically. In some cases, gas costs may spike and you will need to confirm the transaction again.
+
+### Will my subgraph still be discoverable after I transfer it to L2?
+
+Your subgraph will only be discoverable on the network it is published to. For example, if your subgraph is on Arbitrum One, then you can only find it in Explorer on Arbitrum One and will not be able to find it on Ethereum. Please ensure that you have Arbitrum One selected in the network switcher at the top of the page to ensure you are on the correct network.  After the transfer, the L1 subgraph will appear as deprecated.
+
+### Does my subgraph need to be published to transfer it?
+
+To take advantage of the subgraph transfer tool, your subgraph must be already published to Ethereum mainnet and must have some curation signal owned by the wallet that owns the subgraph. If your subgraph is not published, it is recommended you simply publish directly on Arbitrum One - the associated gas fees will be considerably lower. If you want to transfer a published subgraph but the owner account hasn't curated any signal on it, you can signal a small amount (e.g. 1 GRT) from that account; make sure to choose "auto-migrating" signal.
+
+### What happens to the Ethereum mainnet version of my subgraph after I transfer to Arbitrum?
+
+After transferring your subgraph to Arbitrum, the Ethereum mainnet version will be deprecated. We recommend you update your query URL within 48 hours. However, there is a grace period in place that keeps your mainnet URL functioning so that any third-party dapp support can be updated.
+
+### After I transfer, do I also need to re-publish on Arbitrum?
+
+After the 20 minute transfer window, you will need to confirm the transfer with a transaction in the UI to finish the transfer, but the transfer tool will guide you through this. Your L1 endpoint will continue to be supported during the transfer window and a grace period after. It is encouraged that you update your endpoint when convenient for you.
+
+### Will my endpoint experience downtime while re-publishing?
+
+It is unlikely, but possible to experience a brief downtime depending on which Indexers are supporting the subgraph on L1 and whether they keep indexing it until the subgraph is fully supported on L2.
+
+### Is publishing and versioning the same on L2 as Ethereum Ethereum mainnet?
+
+Yes. Select Arbitrum One as your published network when publishing in Subgraph Studio. In the Studio, the latest endpoint will be available which points to the latest updated version of the subgraph.
+
+### Will my subgraph's curation move with my subgraph?
+
+If you've chosen auto-migrating signal, 100% of your own curation will move with your subgraph to Arbitrum One. All of the subgraph's curation signal will be converted to GRT at the time of the transfer, and the GRT corresponding to your curation signal will be used to mint signal on the L2 subgraph.
+
+Other Curators can choose whether to withdraw their fraction of GRT, or also transfer it to L2 to mint signal on the same subgraph.
+
+### Can I move my subgraph back to Ethereum mainnet after I transfer?
+
+Once transferred, your Ethereum mainnet version of this subgraph will be deprecated. If you would like to move back to mainnet, you will need to redeploy and publish back to mainnet. However, transferring back to Ethereum mainnet is strongly discouraged as indexing rewards will eventually be distributed entirely on Arbitrum One.
+
+### Why do I need bridged ETH to complete my transfer?
+
+Gas fees on Arbitrum One are paid using bridged ETH (i.e. ETH that has been bridged to Arbitrum One). However, the gas fees are significantly lower when compared to Ethereum mainnet.
+
+## Delegation
+
+### How do I transfer my delegation?
+
+<VideoEmbed youtube="CAAQCKw5eV4" />
+
+To transfer your delegation, you will need to complete the following steps:
+
+1. Initiate delegation transfer on Ethereum mainnet
+2. Wait 20 minutes for confirmation
+3. Confirm delegation transfer on Arbitrum
+
+\*\*\*\*You must confirm the transaction to complete the delegation transfer on Arbitrum. This step must be completed within 7 days or the delegation could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).
+
+### What happens to my rewards if I initiate a transfer with an open allocation on Ethereum mainnet?
+
+If the Indexer to whom you're delegating is still operating on L1, when you transfer to Arbitrum you will forfeit any delegation rewards from open allocations on Ethereum mainnet. This means that you will lose the rewards from, at most, the last 28-day period. If you time the transfer right after the Indexer has closed allocations you can make sure this is the least amount possible. If you have a communication channel with your Indexer(s), consider discussing with them to find the best time to do your transfer.
+
+### What happens if the Indexer I currently delegate to isn't on Arbitrum One?
+
+The L2 transfer tool will only be enabled if the Indexer you have delegated to has transferred their own stake to Arbitrum.
+
+### Do Delegators have the option to delegate to another Indexer?
+
+If you wish to delegate to another Indexer, you can transfer to the same Indexer on Arbitrum, then undelegate and wait for the thawing period. After this, you can select another active Indexer to delegate to.
+
+### What if I can't find the Indexer I'm delegating to on L2?
+
+The L2 transfer tool will automatically detect the Indexer you previously delegated to.
+
+### Will I be able to mix and match or 'spread' my delegation across new or several Indexers instead of the prior Indexer?
+
+The L2 transfer tool will always move your delegation to the same Indexer you delegated to previously. Once you have moved to L2, you can undelegate, wait for the thawing period, and decide if you'd like to split up your delegation.
+
+### Am I subject to the cooldown period or can I withdraw immediately after using the L2 delegation transfer tool?
+
+The transfer tool allows you to immediately move to L2. If you would like to undelegate you will have to wait for the thawing period. However, if an Indexer has transferred all of their stake to L2, you can withdraw on Ethereum mainnet immediately.
+
+### Can my rewards be negatively impacted if I do not transfer my delegation?
+
+It is anticipated that all network participation will move to Arbitrum One in the future.
+
+### How long does it take to complete the transfer of my delegation to L2?
+
+A 20-minute confirmation is required for delegation transfer. Please note that after the 20-minute period, you must come back and complete step 3 of the transfer process within 7 days. If you fail to do this, then your delegation may be lost. Note that in most cases the transfer tool will complete this step for you automatically. In case of a failed auto-attempt, you will need to complete it manually. If any issues arise during this process, don't worry, we'll be here to help: contact us at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).
+
+### Can I transfer my delegation if I'm using a GRT vesting contract/token lock wallet?
+
+Yes! The process is a bit different because vesting contracts can't forward the ETH needed to pay for the L2 gas, so you need to deposit it beforehand. If your vesting contract is not fully vested, you will also have to first initialize a counterpart vesting contract on L2 and will only be able to transfer the delegation to this L2 vesting contract. The UI on Explorer can guide you through this process when you've connected to Explorer using the vesting lock wallet.
+
+### Does my Arbitrum vesting contract allow releasing GRT just like on mainnet?
+
+No, the vesting contract that is created on Arbitrum will not allow releasing any GRT until the end of the vesting timeline, i.e. until your contract is fully vested. This is to prevent double spending, as otherwise it would be possible to release the same amounts on both layers.
+
+If you'd like to release GRT from the vesting contract, you can transfer them back to the L1 vesting contract using Explorer: in your Arbitrum One profile, you will see a banner saying you can transfer GRT back to the mainnet vesting contract. This requires a transaction on Arbitrum One, waiting 7 days, and a final transaction on mainnet, as it uses the same native bridging mechanism from the GRT bridge.
+
+### Is there any delegation tax?
+
+No. Received tokens on L2 are delegated to the specified Indexer on behalf of the specified Delegator without charging a delegation tax.
+
+### Will my unrealized rewards be transferred when I transfer my delegation?
+
+​Yes! The only rewards that can't be transferred are the ones for open allocations, as those won't exist until the Indexer closes the allocations (usually every 28 days). If you've been delegating for a while, this is likely only a small fraction of rewards.
+
+At the smart contract level, unrealized rewards are already part of your delegation balance, so they will be transferred when you transfer your delegation to L2. ​
+
+### Is moving delegations to L2 mandatory? Is there a deadline?
+
+​Moving delegation to L2 is not mandatory, but indexing rewards are increasing on L2 following the timeline described in [GIP-0052](https://forum.thegraph.com/t/gip-0052-timeline-and-requirements-to-increase-rewards-in-l2/4193). Eventually, if the Council keeps approving the increases, all rewards will be distributed in L2 and there will be no indexing rewards for Indexers and Delegators on L1. ​
+
+### If I am delegating to an Indexer that has already transferred stake to L2, do I stop receiving rewards on L1?
+
+​Many Indexers are transferring stake gradually so Indexers on L1 will still be earning rewards and fees on L1, which are then shared with Delegators. Once an Indexer has transferred all of their stake, then they will stop operating on L1, so Delegators will not receive any more rewards unless they transfer to L2.
+
+Eventually, if the Council keeps approving the indexing rewards increases in L2, all rewards will be distributed on L2 and there will be no indexing rewards for Indexers and Delegators on L1. ​
+
+### I don't see a button to transfer my delegation. Why is that?
+
+​Your Indexer has probably not used the L2 transfer tools to transfer stake yet.
+
+If you can contact the Indexer, you can encourage them to use the L2 Transfer Tools so that Delegators can transfer delegations to their L2 Indexer address. ​
+
+### My Indexer is also on Arbitrum, but I don't see a button to transfer the delegation in my profile. Why is that?
+
+​It is possible that the Indexer has set up operations on L2, but hasn't used the L2 transfer tools to transfer stake. The L1 smart contracts will therefore not know about the Indexer's L2 address. If you can contact the Indexer, you can encourage them to use the transfer tool so that Delegators can transfer delegations to their L2 Indexer address. ​
+
+### Can I transfer my delegation to L2 if I have started the undelegating process and haven't withdrawn it yet?
+
+​No. If your delegation is thawing, you have to wait the 28 days and withdraw it.
+
+The tokens that are being undelegated are "locked" and therefore cannot be transferred to L2.
+
+## Curation Signal
+
+### How do I transfer my curation?
+
+To transfer your curation, you will need to complete the following steps:
+
+1. Initiate signal transfer on Ethereum mainnet
+
+2. Specify an L2 Curator address\*
+
+3. Wait 20 minutes for confirmation
+
+\*If necessary - i.e. you are using a contract address.
+
+### How will I know if the subgraph I curated has moved to L2?
+
+When viewing the subgraph details page, a banner will notify you that this subgraph has been transferred. You can follow the prompt to transfer your curation. You can also find this information on the subgraph details page of any subgraph that has moved.
+
+### What if I do not wish to move my curation to L2?
+
+When a subgraph is deprecated you have the option to withdraw your signal. Similarly, if a subgraph has moved to L2, you can choose to withdraw your signal in Ethereum mainnet or send the signal to L2.
+
+### How do I know my curation successfully transferred?
+
+Signal details will be accessible via Explorer approximately 20 minutes after the L2 transfer tool is initiated.
+
+### Can I transfer my curation on more than one subgraph at a time?
+
+There is no bulk transfer option at this time.
+
+## Indexer Stake
+
+### How do I transfer my stake to Arbitrum?
+
+> Disclaimer: If you are currently unstaking any portion of your GRT on your Indexer, you will not be able to use L2 Transfer Tools.
+
+<VideoEmbed youtube="5lTq_V4YbWc" />
+
+To transfer your stake, you will need to complete the following steps:
+
+1. Initiate stake transfer on Ethereum mainnet
+
+2. Wait 20 minutes for confirmation
+
+3. Confirm stake transfer on Arbitrum
+
+\*Note that you must confirm the transfer within 7 days otherwise your stake may be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).
+
+### Will all of my stake transfer?
+
+You can choose how much of your stake to transfer. If you choose to transfer all of your stake at once, you will need to close any open allocations first.
+
+If you plan on transferring parts of your stake over multiple transactions, you must always specify the same beneficiary address.
+
+Note: You must meet the minimum stake requirements on L2 the first time you use the transfer tool. Indexers must send the minimum 100k GRT (when calling this function the first time). If leaving a portion of stake on L1, it must also be over the 100k GRT minimum and be sufficient (together with your delegations) to cover your open allocations.
+
+### How much time do I have to confirm my stake transfer to Arbitrum?
+
+\*\*\* You must confirm your transaction to complete the stake transfer on Arbitrum. This step must be completed within 7 days or stake could be lost.
+
+### What if I have open allocations?
+
+If you are not sending all of your stake, the L2 transfer tool will validate that at least the minimum 100k GRT remains in Ethereum mainnet and your remaining stake and delegation is enough to cover any open allocations. You may need to close open allocations if your GRT balance does not cover the minimums + open allocations.
+
+### Using the transfer tools, is it necessary to wait 28 days to unstake on Ethereum mainnet before transferring?
+
+No, you can transfer your stake to L2 immediately, there's no need to unstake and wait before using the transfer tool. The 28-day wait only applies if you'd like to withdraw the stake back to your wallet, on Ethereum mainnet or L2.
+
+### How long will it take to transfer my stake?
+
+It will take approximately 20 minutes for the L2 transfer tool to complete transferring your stake.
+
+### Do I have to index on Arbitrum before I transfer my stake?
+
+You can effectively transfer your stake first before setting up indexing, but you will not be able to claim any rewards on L2 until you allocate to subgraphs on L2, index them, and present POIs.
+
+### Can Delegators move their delegation before I move my indexing stake?
+
+No, in order for Delegators to transfer their delegated GRT to Arbitrum, the Indexer they are delegating to must be active on L2.
+
+### Can I transfer my stake if I'm using a GRT vesting contract / token lock wallet?
+
+Yes! The process is a bit different, because vesting contracts can't forward the ETH needed to pay for the L2 gas, so you need to deposit it beforehand. If your vesting contract is not fully vested, you will also have to first initialize a counterpart vesting contract on L2 and will only be able to transfer the stake to this L2 vesting contract. The UI on Explorer can guide you through this process when you've connected to Explorer using the vesting lock wallet.
+
+### I already have stake on L2. Do I still need to send 100k GRT when I use the transfer tools the first time?
+
+​Yes. The L1 smart contracts will not be aware of your L2 stake, so they will require you to transfer at least 100k GRT when you transfer for the first time. ​
+
+### Can I transfer my stake to L2 if I am in the process of unstaking GRT?
+
+​No. If any fraction of your stake is thawing, you have to wait the 28 days and withdraw it before you can transfer stake. The tokens that are being staked are "locked" and will prevent any transfers or stake to L2.
+
+## Vesting Contract Transfer
+
+### How do I transfer my vesting contract?
+
+To transfer your vesting, you will need to complete the following steps:
+
+1. Initiate the vesting transfer on Ethereum mainnet
+
+2. Wait 20 minutes for confirmation
+
+3. Confirm vesting transfer on Arbitrum
+
+### How do I transfer my vesting contract if I am only partially vested?
+
+<VideoEmbed youtube="URPOb2c6o2Y" />
+
+1. Deposit some ETH into the transfer tool contract (UI can help estimate a reasonable amount)
+
+2. Send some locked GRT through the transfer tool contract, to L2 to initialize the L2 vesting lock. This will also set their L2 beneficiary address.
+
+3. Send their stake/delegation to L2 through the "locked" transfer tool functions in the L1Staking contract.
+
+4. Withdraw any remaining ETH from the transfer tool contract
+
+### How do I transfer my vesting contract if I am fully vested?
+
+<VideoEmbed youtube="DuZNYPNe1S0" />
+
+For those that are fully vested, the process is similar:
+
+1. Deposit some ETH into the transfer tool contract (UI can help estimate a reasonable amount)
+
+2. Set your L2 address with a call to the transfer tool contract
+
+3. Send your stake/delegation to L2 through the "locked" transfer tool functions in the L1 Staking contract.
+
+4. Withdraw any remaining ETH from the transfer tool contract
+
+### Can I transfer my vesting contract to Arbitrum?
+
+You can transfer your vesting contract's GRT balance to a vesting contract in L2. This is a prerequisite for transferring stake or delegation from your vesting contract to L2. The vesting contract must hold a nonzero amount of GRT (you can transfer a small amount like 1 GRT to it if needed).
+
+When you transfer GRT from your L1 vesting contract to L2, you can choose the amount to send and you can do this as many times as you like. The L2 vesting contract will be initialized the first time you transfer GRT.
+
+The transfers are done using a Transfer Tool that will be visible on your Explorer profile when you connect with the vesting contract account.
+
+Please note that you will not be able to release/withdraw GRT from the L2 vesting contract until the end of your vesting timeline when your contract is fully vested. If you need to release GRT before then, you can transfer the GRT back to the L1 vesting contract using another transfer tool that is available for that purpose.
+
+If you haven't transferred any vesting contract balance to L2, and your vesting contract is fully vested, you should not transfer your vesting contract to L2. Instead, you can use the transfer tools to set an L2 wallet address, and directly transfer your stake or delegation to this regular wallet on L2.
+
+### I'm using my vesting contract to stake on mainnet. Can I transfer my stake to Arbitrum?
+
+Yes, but if your contract is still vesting, you can only transfer the stake so that it is owned by your L2 vesting contract. You must first initialize this L2 contract by transferring some GRT balance using the vesting contract transfer tool on Explorer. If your contract is fully vested, you can transfer your stake to any address in L2, but you must set it beforehand and deposit some ETH for the L2 transfer tool to pay for L2 gas.
+
+### I'm using my vesting contract to delegate on mainnet. Can I transfer my delegations to Arbitrum?
+
+Yes, but if your contract is still vesting, you can only transfer the delegation so that it is owned by your L2 vesting contract. You must first initialize this L2 contract by transferring some GRT balance using the vesting contract transfer tool on Explorer. If your contract is fully vested, you can transfer your delegation to any address in L2, but you must set it beforehand and deposit some ETH for the L2 transfer tool to pay for L2 gas.
+
+### Can I specify a different beneficiary for my vesting contract on L2?
+
+Yes, the first time you transfer a balance and set up your L2 vesting contract, you can specify an L2 beneficiary. Make sure this beneficiary is a wallet that can perform transactions on Arbitrum One, i.e. it must be an EOA or a multisig deployed to Arbitrum One.
+
+If your contract is fully vested, you will not set up a vesting contract on L2; instead, you will set an L2 wallet address and this will be the receiving wallet for your stake or delegation on Arbitrum.
+
+### My contract is fully vested. Can I transfer my stake or delegation to another address that is not an L2 vesting contract?
+
+Yes. If you haven't transferred any vesting contract balance to L2, and your vesting contract is fully vested, you should not transfer your vesting contract to L2. Instead, you can use the transfer tools to set an L2 wallet address, and directly transfer your stake or delegation to this regular wallet on L2.
+
+This allows you to transfer your stake or delegation to any L2 address.
+
+### My vesting contract is still vesting. How do I transfer my vesting contract balance to L2?
+
+These steps only apply if your contract is still vesting, or if you've used this process before when your contract was still vesting.
+
+To transfer your vesting contract to L2, you will send any GRT balance to L2 using the transfer tools, which will initialize your L2 vesting contract:
+
+1. Deposit some ETH into the transfer tool contract (this will be used to pay for L2 gas)
+
+2. Revoke protocol access to the vesting contract (needed for the next step)
+
+3. Give protocol access to the vesting contract (will allow your contract to interact with the transfer tool)
+
+4. Specify an L2 beneficiary address\* and initiate the balance transfer on Ethereum mainnet
+
+5. Wait 20 minutes for confirmation
+
+6. Confirm the balance transfer on L2
+
+\*If necessary - i.e. you are using a contract address.
+
+\*\*\*\*You must confirm your transaction to complete the balance transfer on Arbitrum. This step must be completed within 7 days or the balance could be lost. In most cases, this step will run automatically, but a manual confirmation may be needed if there is a gas price spike on Arbitrum. If there are any issues during this process, there will be resources to help: contact support at support@thegraph.com or on [Discord](https://discord.gg/graphprotocol).
+
+### My vesting contract shows 0 GRT so I cannot transfer it, why is this and how do I fix it?
+
+​To initialize your L2 vesting contract, you need to transfer a nonzero amount of GRT to L2. This is required by the Arbitrum GRT bridge that is used by the L2 Transfer Tools. The GRT must come from the vesting contract's balance, so it does not include staked or delegated GRT.
+
+If you've staked or delegated all your GRT from the vesting contract, you can manually send a small amount like 1 GRT to the vesting contract address from anywhere else (e.g. from another wallet, or an exchange). ​
+
+### I am using a vesting contract to stake or delegate, but I don't see a button to transfer my stake or delegation to L2, what do I do?
+
+​If your vesting contract hasn't finished vesting, you need to first create an L2 vesting contract that will receive your stake or delegation on L2. This vesting contract will not allow releasing tokens in L2 until the end of the vesting timeline, but will allow you to transfer GRT back to the L1 vesting contract to be released there.
+
+When connected with the vesting contract on Explorer, you should see a button to initialize your L2 vesting contract. Follow that process first, and you will then see the buttons to transfer your stake or delegation in your profile. ​
+
+### If I initialize my L2 vesting contract, will this also transfer my delegation to L2 automatically?
+
+​No, initializing your L2 vesting contract is a prerequisite for transferring stake or delegation from the vesting contract, but you still need to transfer these separately.
+
+You will see a banner on your profile prompting you to transfer your stake or delegation after you have initialized your L2 vesting contract.
+
+### Can I move my vesting contract back to L1?
+
+There is no need to do so because your vesting contract is still in L1. When you use the transfer tools, you just create a new contract in L2 that is connected with your L1 vesting contract, and you can send GRT back and forth between the two.
+
+### Why do I need to move my vesting contract to begin with?
+
+You need to set up an L2 vesting contract so that this account can own your stake or delegation on L2. Otherwise, there'd be no way for you to transfer the stake/delegation to L2 without "escaping" the vesting contract.
+
+### What happens if I try to cash out my contract when it is only partially vested? Is this possible?
+
+This is not a possibility. You can move funds back to L1 and withdraw them there.
+
+### What if I don't want to move my vesting contract to L2?
+
+You can keep staking/delegating on L1. Over time, you may want to consider moving to L2 to enable rewards there as the protocol scales on Arbitrum. Note that these transfer tools are for vesting contracts that are allowed to stake and delegate in the protocol. If your contract does not allow staking or delegating, or is revocable, then there is no transfer tool available. You will still be able to withdraw your GRT from L1 when available.

From ed0ae64d9f24cd9395a99837b4aa114852242a15 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:47 -0500
Subject: [PATCH 1072/1325] New translations l2-transfer-tools-guide.mdx
 (French)

---
 website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx
index 81df458a44b1..a0a6f17b4265 100644
--- a/website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx
+++ b/website/pages/fr/arbitrum/l2-transfer-tools-guide.mdx
@@ -68,7 +68,7 @@ Après avoir ouvert l'outil de transfert, vous pourrez saisir l'adresse du porte
 
 Si vous exécutez cette étape, **assurez-vous de continuer jusqu'à terminer l'étape 3 en moins de 7 jours, sinon le subgraph et votre signal GRT seront perdus.** Cela est dû au fonctionnement de la messagerie L1-L2 sur Arbitrum : les messages qui sont envoyés via le pont sont des « tickets réessayables » qui doivent être exécutés dans les 7 jours, et l'exécution initiale peut nécessiter une nouvelle tentative s'il y a des pics dans le prix du gaz sur Arbitrum.
 
-![Start the transfer to L2](/img/startTransferL2.png)
+![Démarrer le transfert vers la L2](/img/startTransferL2.png)
 
 ## Étape 2 : Attendre que le subgraphe atteigne L2
 

From 3ed807da9462897d1fbe86aa8e6607c1348ff5df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:53 -0500
Subject: [PATCH 1073/1325] New translations l2-transfer-tools-guide.mdx
 (Russian)

---
 website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx
index 160b61ce54e7..f77c7f686ac9 100644
--- a/website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx
+++ b/website/pages/ru/arbitrum/l2-transfer-tools-guide.mdx
@@ -68,7 +68,7 @@ The Graph упростил переход на L2 в Arbitrum One. Для каж
 
 Если Вы выполните этот шаг, ** убедитесь в том, что Вы завершили шаг 3 менее чем за 7 дней, иначе субграф и Ваш сигнал GRT будут утеряны.** Это связано с тем, как в Arbitrum работает обмен сообщениями L1-L2: сообщения, которые отправляются через мост, представляют собой «билеты с возможностью повторной попытки», которые должны быть выполнены в течение 7 дней, и для первоначального исполнения может потребоваться повторная попытка, если в Arbitrum будут скачки цен комиссии сети.
 
-![Start the transfer to L2](/img/startTransferL2.png)
+![Запустите перенос на L2](/img/startTransferL2.png)
 
 ## Шаг 2: Ожидание перехода субграфа в L2
 

From 666a9406bff7951ac9854444ab6d74cfef96022f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:55 -0500
Subject: [PATCH 1074/1325] New translations l2-transfer-tools-guide.mdx
 (Turkish)

---
 website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx
index 59e27fcfdc3a..c2df6e4ed5cb 100644
--- a/website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx
+++ b/website/pages/tr/arbitrum/l2-transfer-tools-guide.mdx
@@ -68,7 +68,7 @@ Transfer Aracını açtıktan sonra, Katman2 cüzdan adresini "Alıcı cüzdan a
 
 Bu adımı uygularsanız, **3. adımı tamamlamak için yedi günden daha kısa bir sürede ilerlediğinizden mutlaka emin olmalısınız; aksi halde subgraph ve sinyal GRT'nizi kaybedeceksiniz.** Bunun nedeni Arbitrum'da Katman1-Katman2 mesajlaşmasının çalışma şeklidir: köprü üzerinden gönderilen mesajlar 7 gün içinde yürütülmesi gereken "yeniden denenebilir biletler"dir ve Arbitrum'da gas fiyatında ani artışlar olması durumunda ilk yürütmenin yeniden denenmesi gerekebilir.
 
-![Start the transfer to L2](/img/startTransferL2.png)
+![L2’ye transferi başlatın](/img/startTransferL2.png)
 
 ## Adım 2: Subgraph'ın Katman2'ye ulaşmasını bekleme
 

From f697b268f4ebbc6f222f6c655575a7ac1dfddea1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:52:56 -0500
Subject: [PATCH 1075/1325] New translations l2-transfer-tools-guide.mdx
 (Chinese Simplified)

---
 website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx
index bfdbc9013821..71601a39c69d 100644
--- a/website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx
+++ b/website/pages/zh/arbitrum/l2-transfer-tools-guide.mdx
@@ -2,7 +2,7 @@
 title: L2转移工具指南
 ---
 
-The Graph 使迁移到 Arbitrum One(L2) 上变得非常容易。对于每个协议参与者，都有一组 L2 转账工具，使所有网络参与者无缝地迁移到 L2。根据你要转移的内容，这些工具会要求你按照特定的步骤操作。
+The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring.
 
 关于这些工具的一些常见问题在 L2 Transfer Tools FAQ(/arbitrum/l2-transfer-tools-faq) 中有详细解答。FAQ 中深入解释了如何使用这些工具、它们的工作原理以及在使用过程中需要注意的事项。
 

From 1296037441d0c9ddf69b41c742ededbbc6e89054 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:00 -0500
Subject: [PATCH 1076/1325] New translations l2-transfer-tools-guide.mdx
 (Swahili)

---
 .../sw/arbitrum/l2-transfer-tools-guide.mdx   | 165 ++++++++++++++++++
 1 file changed, 165 insertions(+)
 create mode 100644 website/pages/sw/arbitrum/l2-transfer-tools-guide.mdx

diff --git a/website/pages/sw/arbitrum/l2-transfer-tools-guide.mdx b/website/pages/sw/arbitrum/l2-transfer-tools-guide.mdx
new file mode 100644
index 000000000000..5ba89020402c
--- /dev/null
+++ b/website/pages/sw/arbitrum/l2-transfer-tools-guide.mdx
@@ -0,0 +1,165 @@
+---
+title: L2 Transfer Tools Guide
+---
+
+The Graph has made it easy to move to L2 on Arbitrum One. For each protocol participant, there are a set of L2 Transfer Tools to make transferring to L2 seamless for all network participants. These tools will require you to follow a specific set of steps depending on what you are transferring.
+
+Some frequent questions about these tools are answered in the [L2 Transfer Tools FAQ](/arbitrum/l2-transfer-tools-faq). The FAQs contain in-depth explanations of how to use the tools, how they work, and things to keep in mind when using them.
+
+## How to transfer your subgraph to Arbitrum (L2)
+
+<VideoEmbed youtube="R8_vz4lx2Co" />
+
+## Benefits of transferring your subgraphs
+
+The Graph's community and core devs have [been preparing](https://forum.thegraph.com/t/gip-0031-arbitrum-grt-bridge/3305) to move to Arbitrum over the past year. Arbitrum, a layer 2 or "L2" blockchain, inherits the security from Ethereum but provides drastically lower gas fees.
+
+When you publish or upgrade your subgraph to The Graph Network, you're interacting with smart contracts on the protocol and this requires paying for gas using ETH. By moving your subgraphs to Arbitrum, any future updates to your subgraph will require much lower gas fees. The lower fees, and the fact that curation bonding curves on L2 are flat, also make it easier for other Curators to curate on your subgraph, increasing the rewards for Indexers on your subgraph. This lower-cost environment also makes it cheaper for Indexers to index and serve your subgraph. Indexing rewards will be increasing on Arbitrum and decreasing on Ethereum mainnet over the coming months, so more and more Indexers will be transferring their stake and setting up their operations on L2.
+
+## Understanding what happens with signal, your L1 subgraph and query URLs
+
+Transferring a subgraph to Arbitrum uses the Arbitrum GRT bridge, which in turn uses the native Arbitrum bridge, to send the subgraph to L2. The "transfer" will deprecate the subgraph on mainnet and send the information to re-create the subgraph on L2 using the bridge. It will also include the subgraph owner's signaled GRT, which must be more than zero for the bridge to accept the transfer.
+
+When you choose to transfer the subgraph, this will convert all of the subgraph's curation signal to GRT. This is equivalent to "deprecating" the subgraph on mainnet. The GRT corresponding to your curation will be sent to L2 together with the subgraph, where they will be used to mint signal on your behalf.
+
+Other Curators can choose whether to withdraw their fraction of GRT, or also transfer it to L2 to mint signal on the same subgraph. If a subgraph owner does not transfer their subgraph to L2 and manually deprecates it via a contract call, then Curators will be notified and will be able to withdraw their curation.
+
+As soon as the subgraph is transferred, since all curation is converted to GRT, Indexers will no longer receive rewards for indexing the subgraph. However, there will be Indexers that will 1) keep serving transferred subgraphs for 24 hours, and 2) immediately start indexing the subgraph on L2. Since these Indexers already have the subgraph indexed, there should be no need to wait for the subgraph to sync, and it will be possible to query the L2 subgraph almost immediately.
+
+Queries to the L2 subgraph will need to be done to a different URL (on `arbitrum-gateway.thegraph.com`), but the L1 URL will continue working for at least 48 hours. After that, the L1 gateway will forward queries to the L2 gateway (for some time), but this will add latency so it is recommended to switch all your queries to the new URL as soon as possible.
+
+## Choosing your L2 wallet
+
+When you published your subgraph on mainnet, you used a connected wallet to create the subgraph, and this wallet owns the NFT that represents this subgraph and allows you to publish updates.
+
+When transferring the subgraph to Arbitrum, you can choose a different wallet that will own this subgraph NFT on L2.
+
+If you're using a "regular" wallet like MetaMask (an Externally Owned Account or EOA, i.e. a wallet that is not a smart contract), then this is optional and it is recommended to keep the same owner address as in L1.
+
+If you're using a smart contract wallet, like a multisig (e.g. a Safe), then choosing a different L2 wallet address is mandatory, as it is most likely that this account only exists on mainnet and you will not be able to make transactions on Arbitrum using this wallet. If you want to keep using a smart contract wallet or multisig, create a new wallet on Arbitrum and use its address as the L2 owner of your subgraph.
+
+**It is very important to use a wallet address that you control, and that can make transactions on Arbitrum. Otherwise, the subgraph will be lost and cannot be recovered.**
+
+## Preparing for the transfer: bridging some ETH
+
+Transferring the subgraph involves sending a transaction through the bridge, and then executing another transaction on Arbitrum. The first transaction uses ETH on mainnet, and includes some ETH to pay for gas when the message is received on L2. However, if this gas is insufficient, you will have to retry the transaction and pay for the gas directly on L2 (this is "Step 3: Confirming the transfer" below). This step **must be executed within 7 days of starting the transfer**. Moreover, the second transaction ("Step 4: Finishing the transfer on L2") will be done directly on Arbitrum. For these reasons, you will need some ETH on an Arbitrum wallet. If you're using a multisig or smart contract account, the ETH will need to be in the regular (EOA) wallet that you are using to execute the transactions, not on the multisig wallet itself.
+
+You can buy ETH on some exchanges and withdraw it directly to Arbitrum, or you can use the Arbitrum bridge to send ETH from a mainnet wallet to L2: [bridge.arbitrum.io](http://bridge.arbitrum.io). Since gas fees on Arbitrum are lower, you should only need a small amount. It is recommended that you start at a low threshold (0.e.g. 01 ETH) for your transaction to be approved.
+
+## Finding the subgraph Transfer Tool
+
+You can find the L2 Transfer Tool when you're looking at your subgraph's page on Subgraph Studio:
+
+![transfer tool](/img/L2-transfer-tool1.png)
+
+It is also available on Explorer if you're connected with the wallet that owns a subgraph and on that subgraph's page on Explorer:
+
+![Transferring to L2](/img/transferToL2.png)
+
+Clicking on the Transfer to L2 button will open the transfer tool where you can start the transfer process.
+
+## Step 1: Starting the transfer
+
+Before starting the transfer, you must decide which address will own the subgraph on L2 (see "Choosing your L2 wallet" above), and it is strongly recommend having some ETH for gas already bridged on Arbitrum (see "Preparing for the transfer: bridging some ETH" above).
+
+Also please note transferring the subgraph requires having a nonzero amount of signal on the subgraph with the same account that owns the subgraph; if you haven't signaled on the subgraph you will have to add a bit of curation (adding a small amount like 1 GRT would suffice).
+
+After opening the Transfer Tool, you will be able to input the L2 wallet address into the "Receiving wallet address" field - **make sure you've entered the correct address here**. Clicking on Transfer Subgraph will prompt you to execute the transaction on your wallet (note some ETH value is included to pay for L2 gas); this will initiate the transfer and deprecate your L1 subgraph (see "Understanding what happens with signal, your L1 subgraph and query URLs" above for more details on what goes on behind the scenes).
+
+If you execute this step, **make sure you proceed until completing step 3 in less than 7 days, or the subgraph and your signal GRT will be lost.** This is due to how L1-L2 messaging works on Arbitrum: messages that are sent through the bridge are "retry-able tickets" that must be executed within 7 days, and the initial execution might need a retry if there are spikes in the gas price on Arbitrum.
+
+![Start the transfer to L2](/img/startTransferL2.png)
+
+## Step 2: Waiting for the subgraph to get to L2
+
+After you start the transfer, the message that sends your L1 subgraph to L2 must propagate through the Arbitrum bridge. This takes approximately 20 minutes (the bridge waits for the mainnet block containing the transaction to be "safe" from potential chain reorgs).
+
+Once this wait time is over, Arbitrum will attempt to auto-execute the transfer on the L2 contracts.
+
+![Wait screen](/img/screenshotOfWaitScreenL2.png)
+
+## Step 3: Confirming the transfer
+
+In most cases, this step will auto-execute as the L2 gas included in step 1 should be sufficient to execute the transaction that receives the subgraph on the Arbitrum contracts. In some cases, however, it is possible that a spike in gas prices on Arbitrum causes this auto-execution to fail. In this case, the "ticket" that sends your subgraph to L2 will be pending and require a retry within 7 days.
+
+If this is the case, you will need to connect using an L2 wallet that has some ETH on Arbitrum, switch your wallet network to Arbitrum, and click on "Confirm Transfer" to retry the transaction.
+
+![Confirm the transfer to L2](/img/confirmTransferToL2.png)
+
+## Step 4: Finishing the transfer on L2
+
+At this point, your subgraph and GRT have been received on Arbitrum, but the subgraph is not published yet. You will need to connect using the L2 wallet that you chose as the receiving wallet, switch your wallet network to Arbitrum, and click "Publish Subgraph."
+
+![Publish the subgraph](/img/publishSubgraphL2TransferTools.png)
+
+![Wait for the subgraph to be published](/img/waitForSubgraphToPublishL2TransferTools.png)
+
+This will publish the subgraph so that Indexers that are operating on Arbitrum can start serving it. It will also mint curation signal using the GRT that were transferred from L1.
+
+## Step 5: Updating the query URL
+
+Your subgraph has been successfully transferred to Arbitrum! To query the subgraph, the new URL will be :
+
+`https://arbitrum-gateway.thegraph.com/api/[api-key]/subgraphs/id/[l2-subgraph-id]`
+
+Note that the subgraph ID on Arbitrum will be a different than the one you had on mainnet, but you can always find it on Explorer or Studio. As mentioned above (see "Understanding what happens with signal, your L1 subgraph and query URLs") the old L1 URL will be supported for a short while, but you should switch your queries to the new address as soon as the subgraph has been synced on L2.
+
+## How to transfer your curation to Arbitrum (L2)
+
+## Understanding what happens to curation on subgraph transfers to L2
+
+When the owner of a subgraph transfers a subgraph to Arbitrum, all of the subgraph's signal is converted to GRT at the same time. This applies to "auto-migrated" signal, i.e. signal that is not specific to a subgraph version or deployment but that follows the latest version of a subgraph.
+
+This conversion from signal to GRT is the same as what would happen if the subgraph owner deprecated the subgraph in L1. When the subgraph is deprecated or transferred, all curation signal is "burned" simultaneously (using the curation bonding curve) and the resulting GRT is held by the GNS smart contract (that is the contract that handles subgraph upgrades and auto-migrated signal). Each Curator on that subgraph therefore has a claim to that GRT proportional to the amount of shares they had for the subgraph.
+
+A fraction of these GRT corresponding to the subgraph owner is sent to L2 together with the subgraph.
+
+At this point, the curated GRT will not accrue any more query fees, so Curators can choose to withdraw their GRT or transfer it to the same subgraph on L2, where it can be used to mint new curation signal. There is no rush to do this as the GRT can be help indefinitely and everybody gets an amount proportional to their shares, irrespective of when they do it.
+
+## Choosing your L2 wallet
+
+If you decide to transfer your curated GRT to L2, you can choose a different wallet that will own the curation signal on L2.
+
+If you're using a "regular" wallet like Metamask (an Externally Owned Account or EOA, i.e. a wallet that is not a smart contract), then this is optional and it is recommended to keep the same Curator address as in L1.
+
+If you're using a smart contract wallet, like a multisig (e.g. a Safe), then choosing a different L2 wallet address is mandatory, as it is most likely that this account only exists on mainnet and you will not be able to make transactions on Arbitrum using this wallet. If you want to keep using a smart contract wallet or multisig, create a new wallet on Arbitrum and use its address as the L2 receiving wallet address.
+
+**It is very important to use a wallet address that you control, and that can make transactions on Arbitrum, as otherwise the curation will be lost and cannot be recovered.**
+
+## Sending curation to L2: Step 1
+
+Before starting the transfer, you must decide which address will own the curation on L2 (see "Choosing your L2 wallet" above), and it is recommended having some ETH for gas already bridged on Arbitrum in case you need to retry the execution of the message on L2. You can buy ETH on some exchanges and withdraw it directly to Arbitrum, or you can use the Arbitrum bridge to send ETH from a mainnet wallet to L2: [bridge.arbitrum.io](http://bridge.arbitrum.io) - since gas fees on Arbitrum are so low, you should only need a small amount, e.g. 0.01 ETH will probably be more than enough.
+
+If a subgraph that you curate to has been transferred to L2, you will see a message on Explorer telling you that you're curating to a transferred subgraph.
+
+When looking at the subgraph page, you can choose to withdraw or transfer the curation. Clicking on "Transfer Signal to Arbitrum" will open the transfer tool.
+
+![Transfer signal](/img/transferSignalL2TransferTools.png)
+
+After opening the Transfer Tool, you may be prompted to add some ETH to your wallet if you don't have any. Then you will be able to input the L2 wallet address into the "Receiving wallet address" field - **make sure you've entered the correct address here**. Clicking on Transfer Signal will prompt you to execute the transaction on your wallet (note some ETH value is included to pay for L2 gas); this will initiate the transfer.
+
+If you execute this step, **make sure you proceed until completing step 3 in less than 7 days, or your signal GRT will be lost.** This is due to how L1-L2 messaging works on Arbitrum: messages that are sent through the bridge are "retryable tickets" that must be executed within 7 days, and the initial execution might need a retry if there are spikes in the gas price on Arbitrum.
+
+## Sending curation to L2: step 2
+
+Starting the transfer:
+
+![Send signal to L2](/img/sendingCurationToL2Step2First.png)
+
+After you start the transfer, the message that sends your L1 curation to L2 must propagate through the Arbitrum bridge. This takes approximately 20 minutes (the bridge waits for the mainnet block containing the transaction to be "safe" from potential chain reorgs).
+
+Once this wait time is over, Arbitrum will attempt to auto-execute the transfer on the L2 contracts.
+
+![Sending curation signal to L2](/img/sendingCurationToL2Step2Second.png)
+
+## Sending curation to L2: step 3
+
+In most cases, this step will auto-execute as the L2 gas included in step 1 should be sufficient to execute the transaction that receives the curation on the Arbitrum contracts. In some cases, however, it is possible that a spike in gas prices on Arbitrum causes this auto-execution to fail. In this case, the "ticket" that sends your curation to L2 will be pending and require a retry within 7 days.
+
+If this is the case, you will need to connect using an L2 wallet that has some ETH on Arbitrum, switch your wallet network to Arbitrum, and click on "Confirm Transfer" to retry the transaction.
+
+![Send signal to L2](/img/L2TransferToolsFinalCurationImage.png)
+
+## Withdrawing your curation on L1
+
+If you prefer not to send your GRT to L2, or you'd rather bridge the GRT manually, you can withdraw your curated GRT on L1. On the banner on the subgraph page, choose "Withdraw Signal" and confirm the transaction; the GRT will be sent to your Curator address.

From 43ce348081495e5f054a81d8dbf3b225c5174ca8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:04 -0500
Subject: [PATCH 1077/1325] New translations substreams-powered-subgraphs.mdx
 (Japanese)

---
 website/pages/ja/cookbook/substreams-powered-subgraphs.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ja/cookbook/substreams-powered-subgraphs.mdx b/website/pages/ja/cookbook/substreams-powered-subgraphs.mdx
index d77a11f670b9..d37080612f41 100644
--- a/website/pages/ja/cookbook/substreams-powered-subgraphs.mdx
+++ b/website/pages/ja/cookbook/substreams-powered-subgraphs.mdx
@@ -68,7 +68,7 @@ fn map_contract(block: eth::v2::Block) -> Result<Contracts, substreams::errors::
 
 Substreams パッケージは、互換性のあるエンティティの変更を出力するモジュールを持っている限り、サブグラフで使用できます。サンプルの Substreams パッケージには、「lib.rs」内に追加の「graph_out」モジュールがあり、グラフ ノードで処理できる「substreams_entity_change::pb::entity::EntityChanges」出力を返します。
 
-> 「substreams_entity_change」クレートには、エンティティの変更を単純に生成するための専用の「Tables」関数もあります (\[[documentation](https://docs.rs/substreams-entity-change/1.2.2/substreams_entity_change/tables/index.html))。生成されたエンティティ変更は、対応するサブグラフの `subgraph.graphql` で定義された `schema.graphql` エンティティと互換性がある必要があります。
+> 「substreams_entity_change」クレートには、エンティティの変更を単純に生成するための専用の「Tables」関数もあります ([[documentation](https://docs.rs/substreams-entity-change/1.2.2/substreams_entity_change/tables/index.html))。生成されたエンティティ変更は、対応するサブグラフの `subgraph.graphql` で定義された `schema.graphql` エンティティと互換性がある必要があります。
 
 ```rust
 #[substreams::handlers::map]

From 6821da3c0a59f3d84350c5712990294145e47896 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:12 -0500
Subject: [PATCH 1078/1325] New translations substreams-powered-subgraphs.mdx
 (Swahili)

---
 .../cookbook/substreams-powered-subgraphs.mdx | 226 ++++++++++++++++++
 1 file changed, 226 insertions(+)
 create mode 100644 website/pages/sw/cookbook/substreams-powered-subgraphs.mdx

diff --git a/website/pages/sw/cookbook/substreams-powered-subgraphs.mdx b/website/pages/sw/cookbook/substreams-powered-subgraphs.mdx
new file mode 100644
index 000000000000..8a7998c325f8
--- /dev/null
+++ b/website/pages/sw/cookbook/substreams-powered-subgraphs.mdx
@@ -0,0 +1,226 @@
+---
+title: Substreams-powered subgraphs
+---
+
+[Substreams](/substreams) is a new framework for processing blockchain data, developed by StreamingFast for The Graph Network. A substreams modules can output entity changes, which are compatible with Subgraph entities. A subgraph can use such a Substreams module as a data source, bringing the indexing speed and additional data of Substreams to subgraph developers.
+
+## Requirements
+
+This cookbook requires [yarn](https://yarnpkg.com/), [the dependencies necessary for local Substreams development](https://substreams.streamingfast.io/documentation/consume/installing-the-cli), and the latest version of Graph CLI (>=0.52.0):
+
+```
+npm install -g @graphprotocol/graph-cli
+```
+
+## Get the cookbook
+
+> This cookbook uses this [Substreams-powered subgraph as a reference](https://github.com/graphprotocol/graph-tooling/tree/main/examples/substreams-powered-subgraph).
+
+```
+graph init --from-example substreams-powered-subgraph
+```
+
+## Defining a Substreams package
+
+A Substreams package is composed of types (defined as [Protocol Buffers](https://protobuf.dev/)), modules (written in Rust), and a `substreams.yaml` file which references the types, and specifies how modules are triggered. [Visit the Substreams documentation to learn more about Substreams development](/substreams), and check out [awesome-substreams](https://github.com/pinax-network/awesome-substreams) and the [Substreams cookbook](https://github.com/pinax-network/substreams-cookbook) for more examples.
+
+The Substreams package in question detects contract deployments on Mainnet Ethereum, tracking the creation block and timestamp for all newly deployed contracts. To do this, there is a dedicated `Contract` type in `/proto/example.proto` ([learn more about defining Protocol Buffers](https://protobuf.dev/programming-guides/proto3/#simple)):
+
+```proto
+syntax = "proto3";
+
+package example;
+
+message Contracts {
+  repeated Contract contracts = 1;
+}
+
+message Contract {
+    string address = 1;
+    uint64 blockNumber = 2;
+    string timestamp = 3;
+    uint64 ordinal = 4;
+}
+```
+
+The core logic of the Substreams package is a `map_contract` module in `lib.rs`, which processes every block, filtering for Create calls which did not revert, returning `Contracts`:
+
+```rust
+#[substreams::handlers::map]
+fn map_contract(block: eth::v2::Block) -> Result<Contracts, substreams::errors::Error> {
+    let contracts = block
+        .transactions()
+        .flat_map(|tx| {
+            tx.calls
+                .iter()
+                .filter(|call| !call.state_reverted)
+                .filter(|call| call.call_type == eth::v2::CallType::Create as i32)
+                .map(|call| Contract {
+                    address: format!("0x{}", Hex(&call.address)),
+                    block_number: block.number,
+                    timestamp: block.timestamp_seconds().to_string(),
+                    ordinal: tx.begin_ordinal,
+                })
+        })
+        .collect();
+    Ok(Contracts { contracts })
+}
+```
+
+A Substreams package can be used by a subgraph as long as it has a module which outputs compatible entity changes. The example Substreams package has an additional `graph_out` module in `lib.rs` which returns a `substreams_entity_change::pb::entity::EntityChanges` output, which can be processed by Graph Node.
+
+> The `substreams_entity_change` crate also has a dedicated `Tables` function for simply generating entity changes ([documentation](https://docs.rs/substreams-entity-change/1.2.2/substreams_entity_change/tables/index.html)). The Entity Changes generated must be compatible with the `schema.graphql` entities defined in the `subgraph.graphql` of the corresponding subgraph.
+
+```rust
+#[substreams::handlers::map]
+pub fn graph_out(contracts: Contracts) -> Result<EntityChanges, substreams::errors::Error> {
+    // hash map of name to a table
+    let mut tables = Tables::new();
+
+    for contract in contracts.contracts.into_iter() {
+        tables
+            .create_row("Contract", contract.address)
+            .set("timestamp", contract.timestamp)
+            .set("blockNumber", contract.block_number);
+    }
+
+    Ok(tables.to_entity_changes())
+}
+```
+
+These types and modules are pulled together in `substreams.yaml`:
+
+```yaml
+specVersion: v0.1.0
+package:
+  name: 'substreams_test' # the name to be used in the .spkg
+  version: v1.0.1 # the version to use when creating the .spkg
+
+imports: # dependencies
+  entity: https://github.com/streamingfast/substreams-entity-change/releases/download/v0.2.1/substreams-entity-change-v0.2.1.spkg
+
+protobuf: # specifies custom types for use by Substreams modules
+  files:
+    - example.proto
+  importPaths:
+    - ./proto
+
+binaries:
+  default:
+    type: wasm/rust-v1
+    file: ./target/wasm32-unknown-unknown/release/substreams.wasm
+
+modules: # specify modules with their inputs and outputs.
+  - name: map_contract
+    kind: map
+    inputs:
+      - source: sf.ethereum.type.v2.Block
+    output:
+      type: proto:test.Contracts
+
+  - name: graph_out
+    kind: map
+    inputs:
+      - map: map_contract
+    output:
+      type: proto:substreams.entity.v1.EntityChanges # this type can be consumed by Graph Node
+```
+
+You can check the overall "flow" from a Block, to `map_contract` to `graph_out` by running `substreams graph`:
+
+```mermaid
+graph TD;
+  map_contract[map: map_contract];
+  sf.ethereum.type.v2.Block[source: sf.ethereum.type.v2.Block] --> map_contract;
+  graph_out[map: graph_out];
+  map_contract --> graph_out;
+```
+
+To prepare this Substreams package for consumption by a subgraph, you must run the following commands:
+
+```bash
+yarn substreams:protogen # generates types in /src/pb
+yarn substreams:build # builds the substreams
+yarn substreams:package # packages the substreams in a .spkg file
+
+# alternatively, yarn substreams:prepare calls all of the above commands
+```
+
+> These scripts are defined in the `package.json` file if you want to understand the underlying substreams commands
+
+This generates a `spkg` file based on the package name and version from `substreams.yaml`. The `spkg` file has all the information which Graph Node needs to ingest this Substreams package.
+
+> If you update the Substreams package, depending on the changes you make, you may need to run some or all of the above commands so that the `spkg` is up to date.
+
+## Defining a Substreams-powered subgraph
+
+Substreams-powered subgraphs introduce a new `kind` of data source, "substreams". Such subgraphs can only have one data source.
+
+This data source must specify the indexed network, the Substreams package (`spkg`) as a relative file location, and the module within that Substreams package which produces subgraph-compatible entity changes (in this case `map_entity_changes`, from the Substreams package above). The mapping is specified, but simply identifies the mapping kind ("substreams/graph-entities") and the apiVersion.
+
+> Currently, Subgraph Studio and The Graph Network support Substreams-powered subgraphs which index `mainnet` (Mainnet Ethereum).
+
+```yaml
+specVersion: 0.0.4
+description: Ethereum Contract Tracking Subgraph (powered by Substreams)
+repository: https://github.com/graphprotocol/graph-tooling
+schema:
+  file: schema.graphql
+dataSources:
+  - kind: substreams
+    name: substream_test
+    network: mainnet
+    source:
+      package:
+        moduleName: graph_out
+        file: substreams-test-v1.0.1.spkg
+    mapping:
+      kind: substreams/graph-entities
+      apiVersion: 0.0.5
+```
+
+The `subgraph.yaml` also references a schema file. The requirements for this file are unchanged, but the entities specified must be compatible with the entity changes produced by the Substreams module referenced in the `subgraph.yaml`.
+
+```graphql
+type Contract @entity {
+  id: ID!
+
+  "The timestamp when the contract was deployed"
+  timestamp: String!
+
+  "The block number of the contract deployment"
+  blockNumber: BigInt!
+}
+```
+
+Given the above, subgraph developers can use Graph CLI to deploy this Substreams-powered subgraph.
+
+> Substreams-powered subgraphs indexing mainnet Ethereum can be deployed to the [Subgraph Studio](https://thegraph.com/studio/).
+
+```bash
+yarn install # install graph-cli
+yarn subgraph:build # build the subgraph
+yarn subgraph:deploy # deploy the subgraph
+```
+
+That's it! You have built and deployed a Substreams-powered subgraph.
+
+## Serving Substreams-powered subgraphs
+
+In order to serve Substreams-powered subgraphs, Graph Node must be configured with a Substreams provider for the relevant network, as well as a Firehose or RPC to track the chain head. These providers can be configured via a `config.toml` file:
+
+```toml
+[chains.mainnet]
+shard = "main"
+protocol = "ethereum"
+provider = [
+  { label = "substreams-provider-mainnet",
+    details = { type = "substreams",
+    url = "https://mainnet-substreams-url.grpc.substreams.io/",
+    token = "exampletokenhere" }},
+  { label = "firehose-provider-mainnet",
+    details = { type = "firehose",
+    url = "https://mainnet-firehose-url.grpc.firehose.io/",
+    token = "exampletokenhere" }},
+]
+```

From 3a00c5d9d6eea6a700aa5bee84882d9477d5db92 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:13 -0500
Subject: [PATCH 1079/1325] New translations
 substreams-powered-subgraphs-faq.mdx (French)

---
 .../fr/developing/substreams-powered-subgraphs-faq.mdx    | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/fr/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/fr/developing/substreams-powered-subgraphs-faq.mdx
index 67ef80c54b92..b5510cf7441c 100644
--- a/website/pages/fr/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/fr/developing/substreams-powered-subgraphs-faq.mdx
@@ -4,7 +4,7 @@ title: FAQ sur les subgraphs alimentés par les sous-flux
 
 ## Que sont les sous-flux ?
 
-Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere.
+Développé par [StreamingFast](https://www.streamingfast.io/), Substreams est un moteur de traitement extrêmement puissant capable de consommer des flux riches de données blockchain. Substreams vous permet de raffiner et de structurer les données blockchain pour une digestion rapide et fluide par les applications des utilisateurs finaux. Plus précisément, Substreams est un moteur agnostique à la blockchain, parallélisé et axé sur le streaming, servant de couche de transformation des données blockchain. Propulsé par [Firehose](https://firehose.streamingfast.io/), il permet aux développeurs d'écrire des modules Rust, de s'appuyer sur des modules communautaires, de fournir une indexation très performante, et de [diriger(sink)](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) leurs données vers n'importe quelle destination.
 
 Rendez-vous sur le site [Substreams Documentation](/substreams) pour en savoir plus sur Substreams.
 
@@ -22,7 +22,7 @@ En revanche, les subgraphs alimentés par des flux secondaires disposent d'une s
 
 ## Quels sont les avantages de l'utilisation de subgraphs alimentés par des courants descendants ?
 
-Substreams-powered subgraphs combine all the benefits of Substreams with the queryability of subgraphs. They bring greater composability and high-performance indexing to The Graph. They also enable new data use cases; for example, once you've built your Substreams-powered Subgraph, you can reuse your [Substreams modules](https://substreams.streamingfast.io/documentation/develop/manifest-modules) to output to different [sinks](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) such as PostgreSQL, MongoDB, and Kafka.
+Les subgraphs alimentés par Substreams combinent tous les avantages de Substreams avec la capacité d'intérrogation des subgraphs. Ils apportent une plus grande composabilité (la capacité des composants d'un système à être modifié et recombiné en une autre structure afin de répondre à des besoins précis.) et une indexation haute performance à The Graph. Ils permettent également de nouveaux cas d'utilisation de données; par exemple, une fois que vous avez construit votre subgraph alimenté par Substreams, vous pouvez réutiliser vos [modules Substreams](https://substreams.streamingfast.io/documentation/develop/manifest-modules) pour produire des sorties vers différents [sinks](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) tels que PostgreSQL, MongoDB et Kafka.
 
 ## Quels sont les avantages de Substreams ?
 
@@ -66,13 +66,13 @@ La [documentation Substreams](/substreams) vous apprendra à construire des modu
 
 La [documentation sur les subgraphs alimentés par des flux partiels] (/cookbook/substreams-powered-subgraphs/) vous montrera comment les emballer pour les déployer sur The Graph.
 
-The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code.
+Le [dernier outil Substreams Codegen ](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) vous permettra de lancer un projet Substreams sans aucun code.
 
 ## Quel est le rôle des modules Rust dans Substreams ?
 
 Les modules Rust sont l'équivalent des mappeurs AssemblyScript dans les subgraphs. Ils sont compilés dans WASM de la même manière, mais le modèle de programmation permet une exécution parallèle. Ils définissent le type de transformations et d'agrégations que vous souhaitez appliquer aux données brutes de la blockchain.
 
-See [modules documentation](https://substreams.streamingfast.io/documentation/develop/manifest-modules) for details.
+Consultez [ documentation des modules](https://substreams.streamingfast.io/documentation/develop/manifest-modules) pour plus de détails.
 
 ## Qu'est-ce qui rend Substreams composable ?
 

From ffb440755e69d20b31923be397d874e543f96556 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:19 -0500
Subject: [PATCH 1080/1325] New translations
 substreams-powered-subgraphs-faq.mdx (Portuguese)

---
 .../pages/pt/developing/substreams-powered-subgraphs-faq.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pt/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/pt/developing/substreams-powered-subgraphs-faq.mdx
index 45792250dc05..5fc4b8f0c2f6 100644
--- a/website/pages/pt/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/pt/developing/substreams-powered-subgraphs-faq.mdx
@@ -66,7 +66,7 @@ A [documentação do Substreams](/substreams) lhe ensinará como construir módu
 
 A [documentação de subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs/) lhe ensinará como empacotá-los para a publicação no The Graph.
 
-The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code.
+A [ferramenta de Codegen no Substreams mais recente](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) permitirá ao programador inicializar um projeto no Substreams sem a necessidade de código.
 
 ## Qual é o papel de módulos em Rust no Substreams?
 

From 4b87e5e73aa13ff9d175cc482e1e3b3c6827310c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:21 -0500
Subject: [PATCH 1081/1325] New translations
 substreams-powered-subgraphs-faq.mdx (Urdu (Pakistan))

---
 .../pages/ur/developing/substreams-powered-subgraphs-faq.mdx   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx
index d00028321854..ff87c267315c 100644
--- a/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx
@@ -44,7 +44,8 @@ Substreams-powered subgraphs combine all the benefits of Substreams with the que
 
 [StreamingFast](https://www.streamingfast.io/) کے ذریعے تیار کردہ، Firehose ایک بلاکچین ڈیٹا نکالنے کی پرت ہے جسے شروع سے بلاکچینز کی مکمل تاریخ کو اس رفتار سے پروسیس کرنے کے لیے ڈیزائن کیا گیا ہے جو پہلے نظر نہیں آتی تھیں۔ فائلوں پر مبنی اور سٹریمنگ فرسٹ اپروچ فراہم کرنا، یہ سٹریمنگ فاسٹ کے اوپن سورس ٹیکنالوجیز کے سوٹ کا بنیادی جزو اور سب اسٹریمز کی بنیاد ہے.
 
-Firehose کے بارے میں مزید جاننے کے لیے[documentation] (https://firehose.streamingfast.io/) پر جائیں.
+Firehose کے بارے میں مزید جاننے کے لیے[documentation]
+(https://firehose.streamingfast.io/) پر جائیں.
 
 ## Firehose کے کیا فوائد ہیں؟
 

From 427bf01944b49f1284838ddb0b7f3bb49dae1b7d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:23 -0500
Subject: [PATCH 1082/1325] New translations
 substreams-powered-subgraphs-faq.mdx (Hindi)

---
 .../pages/hi/developing/substreams-powered-subgraphs-faq.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/hi/developing/substreams-powered-subgraphs-faq.mdx
index 92c6a8313a5f..4ac776772148 100644
--- a/website/pages/hi/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/hi/developing/substreams-powered-subgraphs-faq.mdx
@@ -66,7 +66,7 @@ The [Substreams documentation](/substreams) will teach you how to build Substrea
 
 The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph.
 
-The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code.
+[नवीनतम Substreams Codegen टूल](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) आपको बिना किसी कोड के एक Substreams प्रोजेक्ट शुरू करने की अनुमति देगा।
 
 ## What is the role of Rust modules in Substreams?
 

From 241c190072540002f85cced8f9171d0e25a29081 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:24 -0500
Subject: [PATCH 1083/1325] New translations
 substreams-powered-subgraphs-faq.mdx (Swahili)

---
 .../substreams-powered-subgraphs-faq.mdx      | 93 +++++++++++++++++++
 1 file changed, 93 insertions(+)
 create mode 100644 website/pages/sw/developing/substreams-powered-subgraphs-faq.mdx

diff --git a/website/pages/sw/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/sw/developing/substreams-powered-subgraphs-faq.mdx
new file mode 100644
index 000000000000..92c6a8313a5f
--- /dev/null
+++ b/website/pages/sw/developing/substreams-powered-subgraphs-faq.mdx
@@ -0,0 +1,93 @@
+---
+title: Substreams-powered subgraphs FAQ
+---
+
+## What are Substreams?
+
+Developed by [StreamingFast](https://www.streamingfast.io/), Substreams is an exceptionally powerful processing engine capable of consuming rich streams of blockchain data. Substreams allow you to refine and shape blockchain data for fast and seamless digestion by end-user applications. More specifically, Substreams is a blockchain-agnostic, parallelized, and streaming-first engine, serving as a blockchain data transformation layer. Powered by the [Firehose](https://firehose.streamingfast.io/), it ​​enables developers to write Rust modules, build upon community modules, provide extremely high-performance indexing, and [sink](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) their data anywhere.
+
+Go to the [Substreams Documentation](/substreams) to learn more about Substreams.
+
+## What are Substreams-powered subgraphs?
+
+[Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs/) combine the power of Substreams with the queryability of subgraphs. When publishing a Substreams-powered Subgraph, the data produced by the Substreams transformations, can [output entity changes](https://github.com/streamingfast/substreams-sink-entity-changes/blob/develop/substreams-entity-change/src/tables.rs), which are compatible with subgraph entities.
+
+If you are already familiar with subgraph development, then note that Substreams-powered subgraphs can then be queried, just as if it had been produced by the AssemblyScript transformation layer, with all the Subgraph benefits, like providing a dynamic and flexible GraphQL API.
+
+## How are Substreams-powered subgraphs different from subgraphs?
+
+Subgraphs are made up of datasources which specify on-chain events, and how those events should be transformed via handlers written in Assemblyscript. These events are processed sequentially, based on the order in which events happen on-chain.
+
+By contrast, substreams-powered subgraphs have a single datasource which references a substreams package, which is processed by the Graph Node. Substreams have access to additional granular on-chain data compared to conventional subgraphs, and can also benefit from massively parallelised processing, which can mean much faster processing times.
+
+## What are the benefits of using Substreams-powered subgraphs?
+
+Substreams-powered subgraphs combine all the benefits of Substreams with the queryability of subgraphs. They bring greater composability and high-performance indexing to The Graph. They also enable new data use cases; for example, once you've built your Substreams-powered Subgraph, you can reuse your [Substreams modules](https://substreams.streamingfast.io/documentation/develop/manifest-modules) to output to different [sinks](https://substreams.streamingfast.io/reference-and-specs/manifests#sink) such as PostgreSQL, MongoDB, and Kafka.
+
+## What are the benefits of Substreams?
+
+There are many benefits to using Substreams, including:
+
+- Composable: You can stack Substreams modules like LEGO blocks, and build upon community modules, further refining public data.
+
+- High-performance indexing: Orders of magnitude faster indexing through large-scale clusters of parallel operations (think BigQuery).
+
+- Sink anywhere: Sink your data to anywhere you want: PostgreSQL, MongoDB, Kafka, subgraphs, flat files, Google Sheets.
+
+- Programmable: Use code to customize extraction, do transformation-time aggregations, and model your output for multiple sinks.
+
+- Access to additional data which is not available as part of the JSON RPC
+
+- All the benefits of the Firehose.
+
+## What is the Firehose?
+
+Developed by [StreamingFast](https://www.streamingfast.io/), the Firehose is a blockchain data extraction layer designed from scratch to process the full history of blockchains at speeds that were previously unseen. Providing a files-based and streaming-first approach, it is a core component of StreamingFast's suite of open-source technologies and the foundation for Substreams.
+
+Go to the [documentation](https://firehose.streamingfast.io/) to learn more about the Firehose.
+
+## What are the benefits of the Firehose?
+
+There are many benefits to using Firehose, including:
+
+- Lowest latency & no polling: In a streaming-first fashion, the Firehose nodes are designed to race to push out the block data first.
+
+- Prevents downtimes: Designed from the ground up for High Availability.
+
+- Never miss a beat: The Firehose stream cursor is designed to handle forks and to continue where you left off in any condition.
+
+- Richest data model:  Best data model that includes the balance changes, the full call tree, internal transactions, logs, storage changes, gas costs, and more.
+
+- Leverages flat files: Blockchain data is extracted into flat files, the cheapest and most optimized computing resource available.
+
+## Where can developers access more information about Substreams-powered subgraphs and Substreams?
+
+The [Substreams documentation](/substreams) will teach you how to build Substreams modules.
+
+The [Substreams-powered subgraphs documentation](/cookbook/substreams-powered-subgraphs/) will show you how to package them for deployment on The Graph.
+
+The [latest Substreams Codegen tool](https://streamingfastio.medium.com/substreams-codegen-no-code-tool-to-bootstrap-your-project-a11efe0378c6) will allow you to bootstrap a Substreams project without any code.
+
+## What is the role of Rust modules in Substreams?
+
+Rust modules are the equivalent of the AssemblyScript mappers in subgraphs. They are compiled to WASM in a similar way, but the programming model allows for parallel execution. They define the sort of transformations and aggregations you want to apply to the raw blockchain data.
+
+See [modules documentation](https://substreams.streamingfast.io/documentation/develop/manifest-modules) for details.
+
+## What makes Substreams composable?
+
+When using Substreams, the composition happens at the transformation layer enabling cached modules to be re-used.
+
+As an example, Alice can build a DEX price module, Bob can use it to build a volume aggregator for some tokens of his interest, and Lisa can combine four individual DEX price modules to create a price oracle. A single Substreams request will package all of these individual's modules, link them together, to offer a much more refined stream of data. That stream can then be used to populate a subgraph, and be queried by consumers.
+
+## How can you build and deploy a Substreams-powered Subgraph?
+
+After [defining](/cookbook/substreams-powered-subgraphs/) a Substreams-powered Subgraph, you can use the Graph CLI to deploy it in [Subgraph Studio](https://thegraph.com/studio/).
+
+## Where can I find examples of Substreams and Substreams-powered subgraphs?
+
+You can visit [this Github repo](https://github.com/pinax-network/awesome-substreams) to find examples of Substreams and Substreams-powered subgraphs.
+
+## What do Substreams and Substreams-powered subgraphs mean for The Graph Network?
+
+The integration promises many benefits, including extremely high-performance indexing and greater composability by leveraging community modules and building on them.

From e9a0a6bf8650d988f35e4fc97a0ee7ec4fd6499f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:25 -0500
Subject: [PATCH 1084/1325] New translations new-chain-integration.mdx
 (Romanian)

---
 website/pages/ro/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/ro/new-chain-integration.mdx b/website/pages/ro/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/ro/new-chain-integration.mdx
+++ b/website/pages/ro/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From ceb67f31b89debf7624cd5affa0607ccdd6de98a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:26 -0500
Subject: [PATCH 1085/1325] New translations new-chain-integration.mdx (French)

---
 website/pages/fr/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/fr/new-chain-integration.mdx b/website/pages/fr/new-chain-integration.mdx
index ec6a7423d079..398e4770837e 100644
--- a/website/pages/fr/new-chain-integration.mdx
+++ b/website/pages/fr/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Intégration de nouveaux réseaux
+title: New Chain Integration
 ---
 
-Graph Node peut actuellement indexer les données des types de chaînes suivants :
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-Si l'une de ces chaînes vous intéresse, l'intégration est une question de configuration et de test de Graph Node.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-Si la blockchain est équivalente à EVM et que le client/nœud expose l'API EVM JSON-RPC standard, Graph Node devrait pouvoir indexer la nouvelle chaîne. Pour plus d'informations, reportez-vous à [Test d'un EVM JSON-RPC] (new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Tester un EVM JSON-RPC
 
-Pour les chaînes non basées sur EVM, Graph Node doit ingérer des données de blockchain via gRPC et des définitions de type connues. Cela peut être fait via [Firehose](firehose/), une nouvelle technologie développée par [StreamingFast](https://www.streamingfast.io/) qui fournit une solution de blockchain d'indexation hautement évolutive utilisant un système de streaming et de fichiers basé sur des fichiers. première approche. Contactez l'[équipe StreamingFast](mailto:integrations@streamingfast.io/) si vous avez besoin d'aide pour le développement de Firehose.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Différence entre EVM JSON-RPC et Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-Bien que les deux conviennent aux subgraphs, un Firehose est toujours requis pour les développeurs souhaitant construire avec [Substreams](substreams/), comme la construction de [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). De plus, Firehose permet des vitesses d'indexation améliorées par rapport à JSON-RPC.
+### 2. Firehose Integration
 
-Les nouveaux intégrateurs de chaîne EVM peuvent également envisager l'approche basée sur Firehose, compte tenu des avantages des sous-flux et de ses capacités d'indexation parallélisées massives. La prise en charge des deux permet aux développeurs de choisir entre la création de sous-flux ou de subgraphs pour la nouvelle chaîne.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **REMARQUE** : Une intégration basée sur Firehose pour les chaînes EVM nécessitera toujours que les indexeurs exécutent le nœud RPC d'archive de la chaîne pour indexer correctement les subgraph. Cela est dû à l'incapacité de Firehose à fournir un état de contrat intelligent généralement accessible par la méthode RPC `eth_call`. (Il convient de rappeler que les eth_calls ne sont [pas une bonne pratique pour les développeurs](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Tester un EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-Pour que Graph Node puisse ingérer des données à partir d'une chaîne EVM, le nœud RPC doit exposer les méthodes EVM JSON RPC suivantes :
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Configuration Graph Node
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Commencez par préparer votre environnement local**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Configuration Graph Node
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modifiez [cette ligne](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) pour inclure le nouveau nom de réseau et l'URL compatible avec le RPC JSON EVM
-   > Ne modifiez pas le nom de la variable d'environnement lui-même. Il doit rester « Ethereum » même si le nom du réseau est différent.
-3. Exécutez un nœud IPFS ou utilisez celui utilisé par The Graph : https://api.thegraph.com/ipfs/
 
-**Testez l'intégration en déployant localement un subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Créez un exemple de subgraph simple. Certaines options sont ci-dessous :
-   1. Le contrat intelligent et le subgraph pré-emballés [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) sont un bon point de départ
-   2. Amorcez un subgraph local à partir de n'importe quel contrat intelligent ou environnement de développement Solidity existant [en utilisant Hardhat avec un plugin Graph](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Créez votre subgraph dans Graph Node : `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publiez votre subgraph sur Graph Node : `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node devrait synchroniser le subgraph déployé s'il n'y a pas d'erreurs. Laissez-lui le temps de se synchroniser, puis envoyez des requêtes GraphQL au point de terminaison de l'API indiqué dans les journaux.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Intégration d'une nouvelle chaîne Firehose
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Créez un exemple de subgraph simple. Certaines options sont ci-dessous :
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node devrait synchroniser le subgraph déployé s'il n'y a pas d'erreurs. Laissez-lui le temps de se synchroniser, puis envoyez des requêtes GraphQL au point de terminaison de l'API indiqué dans les journaux.
 
-L'intégration d'une nouvelle chaîne est également possible en utilisant l'approche Firehose. Il s'agit actuellement de la meilleure option pour les chaînes non-EVM et d'une exigence pour la prise en charge des substreams. La documentation supplémentaire se concentre sur le fonctionnement de Firehose, l'ajout de la prise en charge de Firehose pour une nouvelle chaîne et son intégration avec Graph Node. Documentation recommandée aux intégrateurs :
+## Substreams-powered Subgraphs
 
-1. [Documentation générale sur Firehose](firehose/)
-2. [Ajout du support Firehose pour une nouvelle chaîne](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Intégration de Graph Node avec une nouvelle chaîne via Firehose] (https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 83f6d9376e59ff089f35f0959f7a5a90accd12af Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:27 -0500
Subject: [PATCH 1086/1325] New translations new-chain-integration.mdx
 (Spanish)

---
 website/pages/es/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/es/new-chain-integration.mdx b/website/pages/es/new-chain-integration.mdx
index 652d1a26d51a..ea501d78d47a 100644
--- a/website/pages/es/new-chain-integration.mdx
+++ b/website/pages/es/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integración de nuevas redes
+title: New Chain Integration
 ---
 
-El Graph Node actualmente puede indexar datos de los siguientes tipos de cadena:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, a través de EVM JSON-RPC y [Ethereum Firehose] (https://github.com/streamingfast/firehose-ethereum)
-- NEAR, a través de [NEAR Firehose] (https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, a través de [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, a través de [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-Si estás interesado en alguna de esas cadenas, la integración es una cuestión de configuración y prueba de Graph Node.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-Si la cadena de bloques es equivalente a EVM y el cliente/nodo expone la EVM JSON-RPC API estándar, Graph Node debería poder indexar la nueva cadena. Para obtener más información, consulte [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Probando un EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Diferencia entre EVM JSON-RPC y Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, en una solicitud por lotes JSON-RPC
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-Si bien los dos son adecuados para subgrafos, siempre se requiere un Firehose para los desarrolladores que quieran compilar con [Substreams](substreams/), como crear [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). Además, Firehose permite velocidades de indexación mejoradas en comparación con JSON-RPC.
+### 2. Firehose Integration
 
-Los nuevos integradores de cadenas EVM también pueden considerar el enfoque basado en Firehose, dados los beneficios de los substreams y sus enormes capacidades de indexación en paralelo. El soporte de ambos permite a los desarrolladores elegir entre crear substreams o subgrafos para la nueva cadena.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTA**: Una integración basada en Firehose para cadenas EVM aún requerirá que los indexadores ejecuten el nodo RPC de archivo de la cadena para indexar correctamente los subgrafos. Esto se debe a la incapacidad de Firehose para proporcionar un estado de contrato inteligente al que normalmente se puede acceder mediante el método RPC `eth_call`. (Vale la pena recordar que eth_calls [no es una buena práctica para desarrolladores] (https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Probando un EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-Para que Graph Node pueda ingerir datos de una cadena EVM, el nodo RPC debe exponer los siguientes métodos EVM JSON RPC:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(para bloques históricos, con EIP-1898 - requiere nodo de archivo):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, en una solicitud por lotes JSON-RPC
-- _`trace_filter`_ _(opcionalmente necesario para que Graph Node admita call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Configuración del Graph Node
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Empiece por preparar su entorno local**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Configuración del Graph Node
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modifique [esta línea](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) para incluir el nuevo nombre de la red y la URL compatible con EVM JSON RPC
-   > No cambie el nombre de la var env. Debe seguir siendo "ethereum" incluso si el nombre de la red es diferente.
-3. Ejecute un nodo IPFS o use el utilizado por The Graph: https://api.thegraph.com/ipfs/
 
-**Prueba la integración implementando localmente un subgrafo**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Crea un subgrafo simple de prueba. Algunas opciones están a continuación:
-   1. El contrato inteligente y el subgrafo [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) preempaquetados son un buen comienzo
-   2. Arranca un subgrafo local desde cualquier contrato inteligente existente o entorno de desarrollo de solidity [usando Hardhat con un plugin Graph] (https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Crea tu subgrafo en Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publica tu subgrafo en Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node debería sincronizar el subgrafo implementado si no hay errores. Dale tiempo para que se sincronice y luego envíe algunas queries GraphQL al punto final de la API impreso en los registros.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integración de una nueva cadena habilitada para Firehose
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Crea un subgrafo simple de prueba. Algunas opciones están a continuación:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node debería sincronizar el subgrafo implementado si no hay errores. Dale tiempo para que se sincronice y luego envíe algunas queries GraphQL al punto final de la API impreso en los registros.
 
-También es posible integrar una nueva cadena utilizando el enfoque Firehose. Actualmente, esta es la mejor opción para cadenas que no son EVM y un requisito para el soporte de substreams. La documentación adicional se centra en cómo funciona Firehose, agregando soporte de Firehose para una nueva cadena e integrándola con Graph Node. Documentos recomendados para integradores:
+## Substreams-powered Subgraphs
 
-1. [Documentos generales sobre Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integración de Graph Node con una nueva cadena a través de Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 258d4d5ce2f6e3fee466fe2f239ebc488d0b3a5a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:28 -0500
Subject: [PATCH 1087/1325] New translations new-chain-integration.mdx (Arabic)

---
 website/pages/ar/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/ar/new-chain-integration.mdx b/website/pages/ar/new-chain-integration.mdx
index 5b4925685de2..ec987dfa5b55 100644
--- a/website/pages/ar/new-chain-integration.mdx
+++ b/website/pages/ar/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: تكامل الشبكات الجديدة
+title: New Chain Integration
 ---
 
-عقدة الغراف يمكنه حاليًا فهرسة البيانات من أنواع الشبكات التالية:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- إيثيريوم، من خلال استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية ( EVM JSON-RPC) و [فايرهوز إيثيريوم](https://github.com/streamingfast/firehose-ethereum)
-- نير، عبر [نير فايرهوز](https://github.com/streamingfast/near-firehose-indexer)
-- كوسموس، عبر [كوسموس فايرهوز](https://github.com/graphprotocol/firehose-cosmos)
-- أرويف، عبر [أرويف فايرهوز](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-إذا كنت مهتمًا بأي من تلك السلاسل، فإن التكامل يتطلب ضبط واختبار عقدة الغراف.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-إذا كنت مهتمًا بنوع سلسلة مختلفة، فيجب بناء تكامل جديد مع عقدة الغراف. الطريقة الموصى بها هي تطوير فايرهوز جديد للسلسلة المعنية، ثم دمج ذلك الفايرهوز مع عقدة الغراف. المزيد من المعلومات أدناه.
+## Integration Strategies
 
-**1. استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية**
+### 1. EVM JSON-RPC
 
-إذا كانت سلسلة الكتل متوافقة مع آلة الإيثريوم الافتراضية وإذا كان العميل/العقدة يوفر واجهة برمجة التطبيقات القياسية لاستدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية، ، فإنه يمكن لعقدة الغراف فهرسة هذه السلسلة الجديدة. لمزيد من المعلومات، يرجى الاطلاع على [اختبار استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية] (تكامل*سلسة*جديدة #اختبار*استدعاء*إجراء*عن*بُعد*باستخدام*تمثيل*كائنات*جافا*سكريبت*لآلة*التشغيل*الافتراضية_لإثريوم).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. فايرهوز**
+#### اختبار استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية (EVM JSON-RPC)
 
-بالنسبة لسلاسل الكتل الغير المبنية على آلة الإيثيريوم الافتراضية، يجب على عقدة الغراف استيعاب بيانات سلسلة الكتل عبر استدعاء الإجراءات عن بُعد من جوجل(gRPC) وتعريفات الأنواع المعروفة. يمكن القيام بذلك باستخدام [فايرهوز](فايرهوز/)، وهي تقنية جديدة تم تطويرها بواسطة [ستريمنج فاست](https://www.streamingfast.io/)، وتوفر حلاً لفهرسة سلسلة الكتل والقابلة للتوسع باستخدام نهج قائم على الملفات والتدفق المباشر. يمكنكم التواصل مع [فريق ستريمنج فاست](mailto:integrations@streamingfast.io/) إذا كنتم بحاجة إلى مساعدة في تطوير فايرهوز.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## الفرق بين استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية والفايرهوز
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`، ضمن طلب دفعة استدعاء الإجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-في حين أن الاثنين مناسبان للغرافات الفرعية، فإن فايرهوز مطلوب دائمًا للمطورين الراغبين في البناء باستخدام [سبستريمز](سبستريمز/)، مثل بناء [غرافات فرعية مدعومة بسبستريمز](cookbook/substreams-powered-subgraphs/). بالإضافة إلى ذلك، يسمح فايرهوز بتحسين سرعات الفهرسة مقارنةً باستدعاء الإجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت.
+### 2. Firehose Integration
 
-قد يفكر المطورون الجدد لسلاسل آلة الإيثيريوم الافتراضة أيضًا في الاستفادة من نهج فايرهوز بناءً على فوائد سبستريمز وقدرات الفهرسة المتوازية الضخمة. إن دعم كليهما يسمح للمطورين بالاختيار بين بناء سبستريمز أو غرافات فرعية للسلسلة الجديدة.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> ملاحظة: أن التكامل القائم على فايرهوز لسلاسل الآلة الإيثيريوم الافتراضية يتطلب من المفهرسين تشغيل عقدة نداء الإجراء عن بعد للأرشيف الخاص بالشبكة لفهرسة الغرافات الفرعية بشكل صحيح. يرجع ذلك إلى عدم قدرة فايرهوز على توفير حالة العقد الذكية التي يمكن الوصول إليها عادةً بطريقةنداء الإجراء عن بعد `eth_call`. (من الجدير بالذكر أن استخدام eth_calls [ليست ممارسة جيدة للمطورين](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## اختبار استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية (EVM JSON-RPC)
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-لكي تتمكن عقدة الغراف من جمع البيانات من سلسلة EVM، يجب أن يوفر العقد RPC طرق EVM JSON RPC التالية:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(للكتل التاريخية، باستخدام EIP-1898 - يتطلب نقطة أرشيف):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`، ضمن طلب دفعة استدعاء الإجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت
-- _`trace_filter`_ _(مطلوبة اختياريًا لعقدة الغراف لدعم معالجات الاستدعاء)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### تكوين عقدة الغراف
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**ابدأ بإعداد بيئتك المحلية**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## تكوين عقدة الغراف
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [استنسخ عقدة الغراف](https://github.com/graphprotocol/graph-node)
-2. قم بتعديل [هذا السطر](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) لتضمين اسم الشبكة الجديدة والعنوان المتوافق مع استدعاء إجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت لآلة الإيثريوم الافتراضية
-   > لا تقم بتعديل اسم المتغير البيئي نفسه. يجب أن يظل اسمه `ethereum` حتى لو كان اسم الشبكة مختلفًا.
-3. قم بتشغيل عقدة نظام الملفات بين الكواكب (IPFS) أو استخدم العقدة التي يستخدمها الغراف: https://api.thegraph.com/ipfs/
 
-**اختبر التكامل من خلال نشر الغراف الفرعي محليًا.**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. قم بإنشاء مثالًا بسيطًا للغراف الفرعي. بعض الخيارات المتاحة هي كالتالي:
-   1. يُعتبر [غرافيتار](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) المُعد مسبقًا مثالًا جيدًا لعقد ذكي وغراف فرعي كنقطة انطلاقة جيدة
-   2. قم بإعداد غراف فرعي محلي من أي عقد ذكي موجود أو بيئة تطوير صلبة [باستخدام هاردهات وملحق الغراف](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. أنشئ غرافك الفرعي في عقدة الغراف: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. انشر غرافك الفرعي إلى عقدة الغراف: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-إذا لم تكن هناك أخطاء يجب أن يقوم عقدة الغراف بمزامنة الغراف الفرعي المنشور. قم بمنحه بعض الوقت لإتمام عملية المزامنة، ثم قم بإرسال بعض استعلامات لغة الإستعلام للغراف (GraphQL) إلى نقطة نهاية واجهة برمجة التطبيقات الموجودة في السجلات.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## تكامل سلسلة جديدة تدعم فايرهوز
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. قم بإنشاء مثالًا بسيطًا للغراف الفرعي. بعض الخيارات المتاحة هي كالتالي:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+إذا لم تكن هناك أخطاء يجب أن يقوم عقدة الغراف بمزامنة الغراف الفرعي المنشور. قم بمنحه بعض الوقت لإتمام عملية المزامنة، ثم قم بإرسال بعض استعلامات لغة الإستعلام للغراف (GraphQL) إلى نقطة نهاية واجهة برمجة التطبيقات الموجودة في السجلات.
 
-يتيح فايرهوز أيضًا إمكانية دمج سلسلة جديدة. يُعتبر هذا حاليًا الخيار الأفضل للسلاسل الغير معتمدة على آلة الإيثريوم الافتراضية ويعتبر متطلبًا لدعم سبستريمز. الوثائق الإضافية تركز على كيفية عمل فايرهوز وإضافة دعم فايرهوز لسلسلة جديدة ودمجها مع عقدة الغراف. يُوصى بالوثائق التالية للمطورين الذين يقومون بذلك:
+## Substreams-powered Subgraphs
 
-1. [وثائق عامة عن فايرهوز] (firehose/)
-2. [إضافة دعم فايرهوز لسلسلة جديدة](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [دمج غراف نود مع سلسلة جديدة عبر فايرهوز](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 5ea4b7d33c30c86b3ca1fef7e45208214ed32fbc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:29 -0500
Subject: [PATCH 1088/1325] New translations new-chain-integration.mdx (Czech)

---
 website/pages/cs/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/cs/new-chain-integration.mdx b/website/pages/cs/new-chain-integration.mdx
index 1c5466566491..6fd34e39cbac 100644
--- a/website/pages/cs/new-chain-integration.mdx
+++ b/website/pages/cs/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrace nových sítí
+title: New Chain Integration
 ---
 
-Uzel grafu může v současné době indexovat data z následujících typů řetězců:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, prostřednictvím [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, prostřednictvím [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, prostřednictvím [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-Pokud máte zájem o některý z těchto řetězců, je integrace otázkou konfigurace a testování uzlu Graf.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-Pokud máte zájem o jiný typ řetězce, je třeba vytvořit novou integraci s Uzel Graf. Naším doporučeným přístupem je vytvoření nového Firehose pro daný řetězec a následná integrace tohoto Firehose s Uzel Graf. Více informací naleznete níže.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-Pokud je blockchain ekvivalentní EVM a klient/uzel vystavuje standardní EVM JSON-RPC API, měl by být Uzel Grafu schopen indexovat nový řetězec. Další informace naleznete v části [Testování EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testování EVM JSON-RPC
 
-U řetězců, které nejsou založeny na EvM, musí Uzel Graf přijímat data blockchainu prostřednictvím gRPC a známých definic typů. To lze provést prostřednictvím [Firehose](firehose/), nové technologie vyvinuté společností [StreamingFast](https://www.streamingfast.io/), která poskytuje vysoce škálovatelné řešení indexování blockchainu pomocí přístupu založeného na souborech a streamování. Pokud potřebujete s vývojem Firehose pomoci, obraťte se na tým [StreamingFast](mailto:integrations@streamingfast.io/).
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Rozdíl mezi EVM JSON-RPC a Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-Zatímco pro podgrafy jsou tyto dva typy vhodné, pro vývojáře, kteří chtějí vytvářet pomocí [Substreams](substreams/), jako je vytváření [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/), je vždy vyžadován Firehose. Firehose navíc umožňuje vyšší rychlost indexování ve srovnání s JSON-RPC.
+### 2. Firehose Integration
 
-Noví integrátoři řetězců EVM mohou také zvážit přístup založený na technologii Firehose vzhledem k výhodám substreamů a jejím masivním možnostem paralelizovaného indexování. Podpora obojího umožňuje vývojářům zvolit si mezi vytvářením substreamů nebo podgrafů pro nový řetězec.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **POZNÁMKA**: Integrace založená na Firehose pro řetězce EVM bude stále vyžadovat, aby indexátory spustily archivační uzel RPC řetězce, aby správně indexovaly podgrafy. Důvodem je neschopnost Firehose poskytovat stav inteligentních kontraktů typicky přístupný metodou `eth_call` RPC. (Stojí za to připomenout, že eth_call je [pro vývojáře není dobrou praxí](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testování EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-Aby mohl uzel Grafu přijímat data z řetězce EVM, musí uzel RPC zpřístupnit následující metody EVM JSON RPC:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(volitelně vyžadováno pro Uzel Graf, aby podporoval obsluhu volání)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Config uzlu grafu
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Začněte přípravou místního prostředí**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Config uzlu grafu
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Upravte [tento řádek](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) tak, aby obsahoval nový název sítě a URL adresu EVM kompatibilní s JSON RPC
-   > Samotný název env var neměňte. Musí zůstat `ethereum`, i když je název sítě jiný.
-3. Spusťte uzel IPFS nebo použijte ten, který používá Graf: https://api.thegraph.com/ipfs/
 
-**Testování integrace lokálním nasazením podgrafu**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Vytvořte jednoduchý příklad podgrafu. Některé možnosti jsou uvedeny níže:
-   1. Předpřipravený chytrá smlouva [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) a podgraf je dobrým výchozím bodem
-   2. Zavedení lokálního podgrafu z jakéhokoli existujícího chytrého kontraktu nebo vývojového prostředí Solidity [pomocí Hardhat s plugin Graph](https://github.com/graphprotocol/hardhat-graph)
-3. Upravte výsledný soubor `subgraph.yaml` změnou názvu `dataSources.network` na stejný, který byl dříve předán uzlu Graf.
-4. Vytvořte podgraf v uzlu Graf: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Zveřejněte svůj podgraf v uzlu Graf: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Pokud nedošlo k chybám, měl by uzel Graf synchronizovat nasazený podgraf. Dejte mu čas na synchronizaci a poté odešlete několik dotazů GraphQL na koncový bod API vypsaný v protokolech.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrace nového řetězce s podporou služby Firehose
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Vytvořte jednoduchý příklad podgrafu. Některé možnosti jsou uvedeny níže:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Pokud nedošlo k chybám, měl by uzel Graf synchronizovat nasazený podgraf. Dejte mu čas na synchronizaci a poté odešlete několik dotazů GraphQL na koncový bod API vypsaný v protokolech.
 
-Integrace nového řetězce je možná také pomocí přístupu Firehose. To je v současné době nejlepší možnost pro řetězce, které nejsou součástí EVM, a požadavek na podporu substreamů. Další dokumentace se zaměřuje na to, jak Firehose funguje, přidání podpory Firehose pro nový řetězec a jeho integraci s Uzel Graf. Doporučená dokumentace pro integrátory:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Přidání podpory Firehose pro nový řetězec](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrace graf uzlu s novým řetězcem přes Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From b612861d3f5dc56463305a48b99e92afc5ef73ee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:30 -0500
Subject: [PATCH 1089/1325] New translations new-chain-integration.mdx (German)

---
 website/pages/de/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/de/new-chain-integration.mdx b/website/pages/de/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/de/new-chain-integration.mdx
+++ b/website/pages/de/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 7404394c0f78961d94c8e690e136e426df56a05b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:31 -0500
Subject: [PATCH 1090/1325] New translations new-chain-integration.mdx
 (Italian)

---
 website/pages/it/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/it/new-chain-integration.mdx b/website/pages/it/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/it/new-chain-integration.mdx
+++ b/website/pages/it/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 2599e4ee14e89173037fe80a6d7344a114f27a81 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:32 -0500
Subject: [PATCH 1091/1325] New translations new-chain-integration.mdx
 (Japanese)

---
 website/pages/ja/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/ja/new-chain-integration.mdx b/website/pages/ja/new-chain-integration.mdx
index d4d71e358463..76d085dc6ea8 100644
--- a/website/pages/ja/new-chain-integration.mdx
+++ b/website/pages/ja/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: 新しいネットワークの統合
+title: New Chain Integration
 ---
 
-Graph Nodeは現在、以下のチェーンタイプからデータをインデックス化できます：
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-もしご興味があるチェーンがあれば、統合はGraph Nodeの設定とテストの問題です。
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-異なるチェーンタイプに興味がある場合、Graph Nodeとの新しい統合を構築する必要があります。私たちの推奨するアプローチは、問題のチェーン用に新しい Firehose を開発し、その Firehose を Graph Node と統合することです。詳細は下記をご覧ください。
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-ブロックチェーンが EVM と同等であり、クライアント/ノードが標準の EVM JSON-RPC API を公開している場合、グラフ ノードは新しいチェーンのインデックスを作成できるはずです。 詳細については、「EVM JSON-RPC のテスト」(new-chain-integration#testing-an-evm-json-rpc) を参照してください。
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### EVM JSON-RPC のテスト
 
-EVMベースでないチェーンの場合、Graph NodeはgRPCと既知の型定義を介してブロックチェーンデータを取り込む必要があります。これは[StreamingFast](https://www.streamingfast.io/)によって開発された新技術である[Firehose](firehose/)を介して行うことができ、ファイルベースとストリーミングファーストアプローチを使用して高度にスケーラブルなインデックス化ブロックチェーンソリューションを提供します。Firehoseの開発でサポートが必要な場合は、[StreamingFastチーム](mailto:integrations@streamingfast.io/)までご連絡ください。
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## EVM JSON-RPC と Firehose の違い
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-これらの2つの方法は、サブグラフに適していますが、[Substreams](substreams/), を使用して開発者がビルドする場合、常にFirehoseが必要です。これには、[Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/) のようなサブストリームを活用したサブグラフの構築が含まれます。さらに、FirehoseはJSON-RPCと比較して、改善されたインデックス化速度を提供します。
+### 2. Firehose Integration
 
-新しいEVMチェーンの統合者は、サブストリームの利点とその大規模な並列化されたインデックス化能力を考慮して、Firehoseベースのアプローチも検討することができます。両方をサポートすることで、開発者は新しいチェーンに対してサブストリームまたはサブグラフのどちらを構築するかを選択できるようになります。
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **注意**: EVM チェーンの Firehose ベースの統合では、インデクサーがチェーンのアーカイブ RPC ノードを実行してサブグラフに適切にインデックスを付ける必要があります。 これは、通常「eth_call」RPC メソッドによってアクセスできるスマート コントラクト状態を Firehose が提供できないためです。 (eth_calls は [開発者にとって良い習慣ではない](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/) であることを思い出してください)
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## EVM JSON-RPC のテスト
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-Graph NodeがEVMチェーンからデータを取り込むためには、RPCノードは以下のEVM JSON RPCメソッドを公開する必要があります。
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node の設定
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**ローカル環境を準備することから始めます**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node の設定
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. [この行](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) を変更して、新しいネットワーク名と EVM JSON RPC 準拠の URL を含めます。
-   > 環境変数名自体は変更しないでください。ネットワーク名が異なる場合でも、「ethereum」という名前のままである必要があります。
-3. IPFSノードを実行するか、The Graphが使用するものを使用してください: https://api.thegraph.com/ipfs/
 
-**サブグラフをローカルにデプロイして統合をテストします。**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. 簡単なサブグラフの例を作成します。 いくつかのオプションを以下に示します。
-   1. 事前にパックされた [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) スマート コントラクトとサブグラフは良い出発点です。
-   2. 既存のスマート コントラクトまたは Solidity 開発環境からローカル サブグラフをブートストラップする [グラフ プラグインで Hardhat を使用](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. グラフ ノードでサブグラフを作成します: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. サブグラフをGraph Nodeに公開するには、次のコマンドを使用します：graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Nodeはエラーがない場合、デプロイされたサブグラフを同期するはずです。同期が完了するのを待ってから、ログに表示されたAPIエンドポイントに対していくつかのGraphQLクエリを送信してください。
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## 新しい Firehose 対応チェーンの統合
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. 簡単なサブグラフの例を作成します。 いくつかのオプションを以下に示します。
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Nodeはエラーがない場合、デプロイされたサブグラフを同期するはずです。同期が完了するのを待ってから、ログに表示されたAPIエンドポイントに対していくつかのGraphQLクエリを送信してください。
 
-新しいチェーンを統合することは、Firehoseアプローチを使用しても可能です。これは、非EVMチェーン向けの現在の最良のオプションであり、サブストリームサポートの要件でもあります。追加のドキュメントでは、Firehoseの動作方法、新しいチェーンへのFirehoseサポートの追加、およびGraph Nodeとの統合に焦点を当てています。統合者に推奨されるドキュメント:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [新チェーンのFirehoseサポート追加](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From cfed17f94555f8160d67f6db69534eb574762aec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:33 -0500
Subject: [PATCH 1092/1325] New translations new-chain-integration.mdx (Korean)

---
 website/pages/ko/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/ko/new-chain-integration.mdx b/website/pages/ko/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/ko/new-chain-integration.mdx
+++ b/website/pages/ko/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 2580cea520de7d05f5783f28ed27619581d11fc1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:34 -0500
Subject: [PATCH 1093/1325] New translations new-chain-integration.mdx (Dutch)

---
 website/pages/nl/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/nl/new-chain-integration.mdx b/website/pages/nl/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/nl/new-chain-integration.mdx
+++ b/website/pages/nl/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 6b82ba6c4ae5e2598b7ed856987dd0fdd4534c02 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:35 -0500
Subject: [PATCH 1094/1325] New translations new-chain-integration.mdx (Polish)

---
 website/pages/pl/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/pl/new-chain-integration.mdx b/website/pages/pl/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/pl/new-chain-integration.mdx
+++ b/website/pages/pl/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From ef98478b55fe8247f2f43f57b5e272221d4e6247 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:36 -0500
Subject: [PATCH 1095/1325] New translations new-chain-integration.mdx
 (Portuguese)

---
 website/pages/pt/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/pt/new-chain-integration.mdx b/website/pages/pt/new-chain-integration.mdx
index 02844784397e..9c4f0e35d292 100644
--- a/website/pages/pt/new-chain-integration.mdx
+++ b/website/pages/pt/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integração de Novas Redes
+title: Integração de Chains Novas
 ---
 
-Atualmente, Graph Nodes podem indexar dados dos seguintes tipos de chain:
+Chains podem trazer apoio a subgraphs para os seus ecossistemas ao iniciar uma nova integração de `graph-node`. Subgraphs são ferramentas poderosas de indexação que abrem infinitas possibilidades a programadores. O Graph Node já indexa dados das chains listadas aqui. Caso tenha interesse numa nova integração, há 2 estratégias para ela:
 
-- Ethereum, através de EVM JSON-RPC e [Firehose Ethereum](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, através de um [Firehose NEAR](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, através de um [Firehose Cosmos](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, através de um [Firehose Arweave](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: Todas as soluções de integração do Firehose incluem Substreams, um motor de transmissão de grande escala com base no Firehose com apoio nativo ao `graph-node`, o que permite transformações paralelizadas.
 
-Se tiver interesse em qualquer destas chains, a integração será uma questão de configuração e testes do Graph Node.
+> Note que enquanto a abordagem recomendada é o desenvolvimento de um novo Firehose para todas as chains novas, ele só é requerido para chains que não sejam EVMs.
 
-Caso tenha interesse num tipo diferente de chain, será necessária a criação de uma integração nova com o Graph Node. Recomendamos programar um novo Firehose para a chain em questão e então a integração daquele Firehose com o Graph Node. Mais informações abaixo.
+## Estratégias de Integração
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-Se a blockchain for equivalente à EVM, e o cliente/node expor a API EVM JSON-RPC, o Graph Node deve ser capaz de indexar a nova chain. Para mais informações, confira [Como testar uma EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+Se a blockchain for equivalente a EVM e o cliente/node expor a API padrão de JSON-RPC, o Graph Node deve poder indexar a nova chain.
 
-**2. Firehose**
+#### Como testar uma EVM JSON-RPC
 
-Para chains que não são baseadas em EVM, o Graph Node deverá ingerir dados de blockchain através da gRPC e definições de tipos conhecidas. Isto pode ser feito através do [Firehose](firehose/), uma nova tecnologia desenvolvida pelo [StreamingFast](https://www.streamingfast.io/) que providencia uma solução de indexação de blockchain altamente escalável com o uso de uma abordagem baseada em arquivos e que prioriza a transmissão de dados. Contacte a [equipe do StreamingFast](mailto:integrations@streamingfast.io/) caso precise de ajuda com a programação do Firehose.
+Para que o Graph Node possa ingerir dados de uma chain EVM, o node RPC deve expor os seguintes métodos em EVM JSON-RPC:
 
-## Diferenças entre EVM JSON-RPC e Firehose
+- `eth_getLogs`
+- `eth_call` (para blocos históricos, com EIP-1898 - requer node de arquivo)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, em um pedido conjunto em JSON-RPC
+- `trace_filter` (opcional, para que o Graph Node tenha apoio a handlers de chamada)\*
 
-Enquanto os dois são aptos para subgraphs, um Firehose é sempre exigido para programadores que querem construir com [Substreams](substreams/), como a construção de [subgraphs movidos a Substreams](cookbook/substreams-powered-subgraphs/). Além disso, o Firehose gera velocidades de indexação mais rápidas em comparação ao JSON-RPC.
+### 2. Integração do Firehose
 
-Novos integradores de chain EVM também podem considerar a abordagem com base no Firehose, com consideração aos benefícios do substreams e as suas imensas capacidades paralelas de indexação. Apoiar ambos permite que programadores escolham entre a construção de substreams ou subgraphs para a nova chain.
+O [Firehose](https://firehose.streamingfast.io/firehose-setup/overview) é uma camada de extração de última geração, que coleta históricos em streams e arquivos planos em tempo real. A tecnologia do Firehose substitui estas chamadas de API com um fluxo de dados que utilizam um modelo de empurrão que envia dados ao node de indexação mais rapidamente. Isto ajuda a aumentar a velocidade da sincronização e da indexação.
 
-> **NOTA**: Uma integração baseada no Firehose para chains EVM ainda exigirá que Indexadores executem o node RPC de arquivo da chain para indexar subgraphs corretamente. Isto se deve à inabilidade do Firehose para providenciar estados de contratos inteligentes que são tipicamente acessíveis pelo método RPC `eth_call`. (Vale lembrar que eth_calls [não são uma boa prática para programadores](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+O método principal de integrar o Firehose a chains é uma estratégia de polling de RPC. O nosso algoritmo de polling preverá quando um bloco novo irá chegar, e aumentará o ritmo em que ele verifica por um novo bloco quando se aproximar daquela hora, o que o faz uma solução de baixa latência muito eficiente. Para ajuda com a integração e a manutenção do Firehose, contacte a [equipa do StreamingFast](https://www.streamingfast.io/firehose-integration-program). Novas chains e os seus integrantes apreciarão a [consciência de fork](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) e as capacidades imensas de indexação paralelizada que o Firehose e os Substreams trazem ao seu ecossistema.
 
----
+> NOTA: Todas as integrações feitas pela equipa da StreamingFast incluem manutenção para o protocolo de réplica do Firehose no banco de código da chain. O StreamingFast rastreia todas as mudanças e lança binários quando o código é mudado, pelo programador ou pela StreamingFast. Isto inclui o lançamento de binários do Firehose/Substreams para o protocolo, a manutenção dos módulos de Substreams para o modelo de bloco da chain, e o lançamento de binários para o node da blockchain com a instrumentação, caso necessária.
 
-## Como testar uma EVM JSON-RPC
+#### Instrumentação Específica do Firehose para chains EVM (`geth`)
 
-Para que o Graph Node possa ingerir dados de uma chain EVM, o node RPC deve expor os seguintes métodos em EVM JSON-RPC:
+Para chains EVM, há um nível mais profundo de dados que podem ser alcançados através do [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0) `geth`, uma colaboração entre a Go-Ethereum e a StreamingFast, na construção de um sistema de traços rico e de alto throughput. O Live Tracer é a solução mais compreensiva, o que resulta em detalhes de blocos [Estendidos](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425). Isto permite novos paradigmas de indexação, como correspondência de padrões de eventos com base em mudanças no estado, chamadas, árvores de chamadas de parentes, ou o acionamento de eventos com base nas mudanças nas próprias variáveis em um contrato inteligente.
 
-- `eth_getLogs`
-- `eth_call` \_(para blocos históricos, com EIP-1898 - requer node de arquivo):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, em um pedido conjunto em JSON-RPC
-- _`trace_filter`_ _(opcional, para que o Graph Node tenha apoio a call handlers)_
+![Bloco base x bloco Estendido](/img/extended-vs-base-substreams-blocks.png)
+
+> NOTA: Esta melhoria no Firehose requer que chains usem o motor de EVM na `versão geth 1.13.0` adiante.
+
+## Considerações de EVM - Diferença entre JSON-RPC e Firehose
+
+Enquanto ambos o JSON-RPC e o Firehose são próprios para subgraphs, um Firehose é sempre necessário para programadores que querem construir com [Substreams](https://substreams.streamingfast.io). Apoiar os Substreams permite que programadores construam [subgraphs movidos a Substreams](/cookbook/substreams-powered-subgraphs) para a nova chain, e tem o potencial de melhorar o desempenho dos seus subgraphs. Além disto, o Firehose — como um substituto pronto para a camada de extração JSON-RPC do `graph-node` — reduz em 90% o número de chamadas RPC exigidas para indexação geral.
+
+- Todas essas chamadas `getLogs` e roundtrips são substituídas por um único fluxo que chega no coração do `graph-node`, um modelo de bloco único para todos os subgraphs que processa.
 
-### Configuração do Graph Node
+> NOTA: Uma integração baseada no Firehose para chains EVM ainda exigirá que os Indexadores executem o node RPC de arquivo da chain para indexar subgraphs corretamente. Isto é porque o Firehose não pode fornecer estados de contratos inteligentes que são tipicamente acessíveis pelo método RPC  `eth_call` . (Vale lembrar que eth_calls não são uma boa prática para programadores)
 
-**Primeiro, prepare o seu ambiente local**
+## Como Configurar um Graph Node
+
+Configurar um Graph Node é tão fácil quanto preparar o seu ambiente local. Quando o seu ambiente local estiver pronto, será possível testar a integração com a edição local de um subgraph.
 
 1. [Clone o Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modifique [esta linha](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) para ela incluir o nome da nova rede e a URL do EVM JSON-RPC
-   > Não mude o nome do env var. Ele deve permanecer como `ethereum` mesmo se o nome da rede for diferente.
-3. Execute um node IPFS ou use aquele usado pelo The Graph: https://api.thegraph.com/ipfs/
 
-**Teste a integração com o lançamento local de um subgraph**
+2. Modifique [esta linha](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) para ela incluir o nome da nova rede e a URL do EVM JSON-RPC
 
-1. Instale o [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Crie um subgraph de exemplo simples. Aqui estão algumas opções:
-   1. O contrato inteligente e o subgraph [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) pré-inclusos são bons para começar
-   2. Inicie um subgraph local de qualquer contrato inteligente existente ou de um ambiente de programação em solidity [com o uso do Hardhat com um plugin do Graph](https://github.com/graphprotocol/hardhat-graph)
-3. Adapte o `subgraph.yaml` resultante com a mudança do `dataSources.network` para o mesmo nome passado anteriormente ao Graph Node.
-4. Crie o seu subgraph no Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publique o seu subgraph no Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Não mude o nome do env var. Ele deve permanecer como `ethereum` mesmo se o nome da rede for diferente.
 
-O Graph Node deve então sincronizar o subgraph lançado caso não haja erros. Dê um tempo para que ele sincronize, e depois envie alguns queries em GraphQL ao endpoint da API produzido pelos logs.
+3. Execute um node IPFS ou use aquele usado pelo The Graph: https://api.thegraph.com/ipfs/
 
----
+### Como testar um JSON-RPC com a edição local de um subgraph
+
+1. Instale a [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Crie um subgraph de exemplo simples. Aqui estão algumas opções:
+   1. O contrato inteligente e o subgraph [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) pré-inclusos são bons pontos de partida
+   2. Inicie um subgraph local a partir de qualquer contrato inteligente existente ou de um ambiente de programação em solidity [com o uso do Hardhat com um plugin do Graph](https://github.com/graphprotocol/hardhat-graph)
+3. Adapte o `subgraph.yaml` resultante com a mudança do  `dataSources.network` para o mesmo nome passado anteriormente ao Graph Node.
+4. Crie o seu subgraph no Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Edite o seu subgraph no Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
 
-## Integração de uma nova chain com o Firehose
+O Graph Node deve então sincronizar o subgraph lançado caso não haja erros. Deixe-o sincronizar por um tempo, e depois envie alguns queries em GraphQL ao endpoint da API produzido pelos logs.
 
-Integrar uma nova chain também é possível com a abordagem do Firehose. Esta é, atualmente, a melhor opção para chains não-EVM, e necessária para o apoio do substreams. Há mais documentações sobre como o Firehose funciona, como adicionar apoio ao Firehose para uma nova chain, e como integrá-la com o Graph Node. Documentos recomendados para integradores:
+## Subgraphs movidos por Substreams
 
-1. [Documentos gerais sobre o Firehose](firehose/)
-2. [Como adicionar apoio do Firehose a uma nova chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integração do Graph Node com uma nova chain através do Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 804089b01ec7e5edc99e192bb6c7f42a16d8ae8f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:37 -0500
Subject: [PATCH 1096/1325] New translations new-chain-integration.mdx
 (Russian)

---
 website/pages/ru/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/ru/new-chain-integration.mdx b/website/pages/ru/new-chain-integration.mdx
index a394134ffc62..534d6701efdb 100644
--- a/website/pages/ru/new-chain-integration.mdx
+++ b/website/pages/ru/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-\*_Протестируйте интеграцию, локально развернув субграф_
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 8e8ae8e414646ada1d2da7b2b86da6a11eabca0d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:38 -0500
Subject: [PATCH 1097/1325] New translations new-chain-integration.mdx
 (Swedish)

---
 website/pages/sv/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/sv/new-chain-integration.mdx b/website/pages/sv/new-chain-integration.mdx
index 8ebd913a3766..7902ed6f31b2 100644
--- a/website/pages/sv/new-chain-integration.mdx
+++ b/website/pages/sv/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrering av Nya Nätverk
+title: New Chain Integration
 ---
 
-Graf Node kan för närvarande indexera data från följande typer av blockkedjor:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC och [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via en [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via en [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via en [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-Om du är intresserad av någon av dessa blockkedjor är integrering en fråga om konfiguration och testning av Graf Node.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-Om blockkedjan är EVM-ekvivalent och klienten/noden exponerar den standardiserade EVM JSON-RPC API:n, bör Graf Node kunna indexera den nya blockkedjan. För mer information, se [Testa en EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testa en EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Skillnad mellan EVM JSON-RPC och Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, i en JSON-RPC batch-begäran
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-Medan båda alternativen är lämpliga för subgrafer krävs en Firehose alltid för utvecklare som vill bygga med [Substreams](substreams/), som att bygga [Substreams-drivna subgrafer](cookbook/substreams-powered-subgraphs/). Dessutom möjliggör Firehose förbättrade indexeringstider jämfört med JSON-RPC.
+### 2. Firehose Integration
 
-Nya EVM-blockkedjeintegratörer kan också överväga den Firehose-baserade metoden med tanke på fördelarna med substreams och dess massivt parallella indexeringsegenskaper. Att stödja båda alternativen ger utvecklare möjlighet att välja mellan att bygga substreams eller subgrafer för den nya blockkedjan.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **OBS**: En Firehose-baserad integration för EVM-blockkedjor kommer fortfarande att kräva att Indexers kör blockkedjans arkiv-RPC-nod för att korrekt indexera subgrafer. Detta beror på att Firehosen inte kan tillhandahålla den smarta kontraktsstatus som normalt är åtkomlig via `eth_call` RPC-metoden. (Det är värt att påminna om att eth_calls inte är [en bra praxis för utvecklare](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testa en EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-För att Graf Node ska kunna ta emot data från en EVM-blockkedja måste RPC-noden exponera följande EVM JSON-RPC-metoder:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(för historiska block, med EIP-1898 - kräver arkivnod):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, i en JSON-RPC batch-begäran
-- _`trace_filter`_ _(valfritt krav för att Graf Node ska stödja anropshanterare)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graf Node-konfiguration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Börja med att förbereda din lokala miljö**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graf Node-konfiguration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Klona Graf Node](https://github.com/graphprotocol/graph-node)
-2. Ändra [den här raden](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) för att inkludera det nya nätverksnamnet och den EVM JSON-RPC-kompatibla URL:n
-   > Byt inte namnet på env-var självt. Det måste förbli `ethereum` även om nätverksnamnet är annorlunda.
-3. Kör en IPFS-nod eller använd den som används av The Graf: https://api.thegraph.com/ipfs/
 
-**Testa integrationen genom att lokalt distribuera en subgraf**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Skapa en enkel exempelsubgraf. Några alternativ är nedan:
-   1. Den förpackade [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323)-smartkontrakt och subgraf är en bra startpunkt
-   2. Starta en lokal subgraf från ett befintligt smart kontrakt eller en Solidity-utvecklingsmiljö [med hjälp av Hardhat med ett Graf-plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Skapa din subgraf i Graf Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publicera din subgraf till Graf Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graf Node bör synkronisera den distribuerade subgrafen om det inte finns några fel. Ge det tid att synkronisera, och skicka sedan några GraphQL-begäranden till API-slutpunkten som skrivs ut i loggarna.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrera en ny Firehose-aktiverad blockkedja
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Skapa en enkel exempelsubgraf. Några alternativ är nedan:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graf Node bör synkronisera den distribuerade subgrafen om det inte finns några fel. Ge det tid att synkronisera, och skicka sedan några GraphQL-begäranden till API-slutpunkten som skrivs ut i loggarna.
 
-Det är också möjligt att integrera en ny blockkedja med Firehose-metoden. Detta är för närvarande det bästa alternativet för icke-EVM-blockkedjor och ett krav för stöd för delströmmar. Ytterligare dokumentation fokuserar på hur Firehose fungerar, hur du lägger till Firehose-stöd för en ny blockkedja och integrerar den med Graf Node. Rekommenderade dokument för integratörer:
+## Substreams-powered Subgraphs
 
-1. [Allmänna dokument om Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrera Graf Node med en ny blockkedja via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 0ee03597d03cb686bd886bde33d62ed060486b2f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:39 -0500
Subject: [PATCH 1098/1325] New translations new-chain-integration.mdx
 (Turkish)

---
 website/pages/tr/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/tr/new-chain-integration.mdx b/website/pages/tr/new-chain-integration.mdx
index f9e7086bc07f..9f2bc45f75cd 100644
--- a/website/pages/tr/new-chain-integration.mdx
+++ b/website/pages/tr/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Yeni Ağların Entegrasyonu
+title: New Chain Integration
 ---
 
-Graph Düğümü şu anda aşağıdaki zincir türlerinden verileri indeksleyebilir:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, EVM JSON-RPC ve [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum) aracılığıyla
-- NEAR, [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer) aracılığıyla
-- Cosmos, [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos) aracılığıyla
-- Arweave, [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave) aracılığıyla
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-Bu zincirlerden herhangi biriyle ilgileniyorsanız, entegrasyon Graph Düğümü yapılandırması ve testinden ibarettir.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-Blok zinciri EVM eşdeğeri ise ve istemci/düğüm standart EVM JSON-RPC API'sini sunuyorsa, Graph Düğümü yeni zinciri indeksleyebilmelidir. Daha fazla bilgi için [EVM JSON-RPC'yi test etme](new-chain-integration#testing-an-evm-json-rpc) bölümüne bakın.
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### EVM JSON-RPC'yi test etme
 
-EVM tabanlı olmayan zincirler için, Graph Düğümü blok zinciri verilerini gRPC ve bilinen tip tanımları aracılığıyla alması zorunludur. Bu, [StreamingFast] (https://www.streamingfast.io/) tarafından geliştirilen ve dosya tabanlı ve akış öncelikli bir yaklaşım kullanarak yüksek ölçeklenebilir bir indeksleme blok zinciri çözümü sağlayan yeni bir teknoloji olan [Firehose](firehose/) aracılığıyla yapılabilir. [StreamingFast team](mailto:integrations@streamingfast.io/) geliştirme konusunda yardıma ihtiyacınız varsa StreamingFast ekibine ulaşın.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## EVM JSON-RPC ve Firehose arasındaki fark
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, bir JSON-RPC toplu talebinde
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-Her ikisi de subgraphlar için uygun olsa da, [Substreams destekli subgraphlar](cookbook/substreams-powered-subgraphs/) oluşturmak gibi [Substreams](substreams/) ile oluşturmak isteyen geliştiriciler için her zaman bir Firehose gereklidir. Ayrıca Firehose, JSON-RPC ile karşılaştırıldığında daha iyi indeksleme hızları sağlar.
+### 2. Firehose Integration
 
-Yeni EVM zinciri entegre edicileri, substreams faydaları ve devasa paralelleştirilmiş indeksleme kabiliyetleri göz önüne alındığında Firehose tabanlı yaklaşımı da düşünebilirler. Her ikisinin de desteklenmesi, geliştiricilerin yeni zincir için substreams veya subgraphlar oluşturma arasında seçim yapmasına olanak tanır.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOT**: EVM zincirleri için Firehose tabanlı bir entegrasyon, subgraphları düzgün bir şekilde indekslemek için İndeksleyicilerin zincirin arşiv RPC düğümünü çalıştırmasını gerektirecektir. Bunun nedeni, Firehose'un \`eth_call' RPC metodu tarafından erişilebilen akıllı sözleşme durumunu sağlayamamasıdır. (eth_calls'ların [geliştiriciler için iyi bir uygulama olmadığını](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/) hatırlatmakta fayda var)
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## EVM JSON-RPC'yi test etme
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-Graph Düğümü'nün bir EVM zincirinden veri alabilmesi için RPC düğümünün aşağıdaki EVM JSON RPC yöntemlerini sunması gerekir:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(geçmiş bloklar için EIP-1898 ile - arşiv düğümü gerektirir):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, bir JSON-RPC toplu talebinde
-- _`trace_filter`_ _(Graph Düğümü'nün çağrı işleyicilerini desteklemesi için opsiyonel olarak gereklidir)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Yerel ortamınızı hazırlayarak başlayın**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Graph Düğümü'nü Klonlayın](https://github.com/graphprotocol/graph-node)
-2. [Bu satırı](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) yeni ağ adını ve EVM JSON RPC uyumlu URL'yi içerecek şekilde değiştirin
-   > env var adının kendisini değiştirmeyin. Ağ adı farklı olsa bile `ethereum` olarak kalmalıdır.
-3. Bir IPFS düğümü çalıştırın veya Graph tarafından kullanılanı kullanın: https://api.thegraph.com/ipfs/
 
-**Bir subgraph'ı yerel olarak dağıtarak entegrasyonu test edin**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Basit bir örnek subgraph oluşturun. Bazı seçenekler aşağıdadır:
-   1. Önceden paketlenmiş [Gravitar] (https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) akıllı sözleşmesi ve subgraph'ı iyi bir başlangıç noktasıdır
-   2. [Bir Graph eklentisi ile Hardhat kullanarak](https://github.com/graphprotocol/hardhat-graph) mevcut herhangi bir akıllı sözleşmeden veya solidity geliştirme ortamından yerel bir subgraph'ı önyükleyin
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Graph Düğümü'nde subgraph'ınızı oluşturun: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Subgraph'ınızı Graph Düğümü'nde yayınlayın: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Herhangi bir hata olmadığı takdirde Graph Düğü'mü dağıtılan subgraph'ı senkronize ediyor olmalıdır. Senkronizasyon için zaman tanıyın, ardından kayıtlarla yazdırılan API uç noktasına bazı GraphQL sorguları gönderin.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Firehose özellikli yeni bir zincirin entegrasyonu
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Basit bir örnek subgraph oluşturun. Bazı seçenekler aşağıdadır:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Herhangi bir hata olmadığı takdirde Graph Düğü'mü dağıtılan subgraph'ı senkronize ediyor olmalıdır. Senkronizasyon için zaman tanıyın, ardından kayıtlarla yazdırılan API uç noktasına bazı GraphQL sorguları gönderin.
 
-Yeni bir zincirin entegrasyonu, Firehose yaklaşımını kullanarak da mümkündür. Bu, şu anda EVM dışı zincirler için en iyi seçenektir ve substreams desteği için bir gerekliliktir. Ek dokümantasyon, Firehose'un nasıl çalıştığına, yeni bir zincir için Firehose desteği eklemeyi ve onun Graph Düğümü ile entegrasyonunu içerir. Entegre ediciler için önerilen dokümanlar:
+## Substreams-powered Subgraphs
 
-1. [Firehose ile ilgili genel dokümanlar](firehose/)
-2. [Yeni bir zincir için Firehose desteği ekleme](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Firehose aracılığıyla Graph Düğümü'nün yeni bir zincirle entegrasyonu](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 465c94ad535a737d80ccdf8045603f42bea107ef Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:40 -0500
Subject: [PATCH 1099/1325] New translations new-chain-integration.mdx
 (Ukrainian)

---
 website/pages/uk/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/uk/new-chain-integration.mdx b/website/pages/uk/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/uk/new-chain-integration.mdx
+++ b/website/pages/uk/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From dbd8cab5c464a3bf02002f326902d2b7673cc877 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:41 -0500
Subject: [PATCH 1100/1325] New translations new-chain-integration.mdx (Chinese
 Simplified)

---
 website/pages/zh/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/zh/new-chain-integration.mdx b/website/pages/zh/new-chain-integration.mdx
index 99a5e5bdb30a..a3074f0c8223 100644
--- a/website/pages/zh/new-chain-integration.mdx
+++ b/website/pages/zh/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: 集成新网络
+title: New Chain Integration
 ---
 
-Graph Node目前可以从以下链类型中索引数据：
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- 通过EVM JSON-RPC和Ethereum Firehose(https://github.com/streamingfast/firehose-ethereum)进行以太坊的索引
-- 通过NEAR Firehose(https://github.com/streamingfast/near-firehose-indexer)进行NEAR的索引
-- 通过Cosmos Firehose(https://github.com/graphprotocol/firehose-cosmos)进行Cosmos的索引
-- 通过Arweave Firehose(https://github.com/graphprotocol/firehose-arweave)进行Arweave的索引
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-如果您对其中任何一种链感兴趣，集成是Graph Node配置和测试的事情。
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-如果区块链与EVM等效，并且客户端/节点公开标准的EVM JSON-RPC API，Graph Node应该能够索引新的链。有关更多信息，请参阅EVM JSON-RPC测试(new-chain-integration#testing-an-evm-json-rpc)。
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-2. Firehose
+#### 测试EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## EVM JSON-RPC和Firehose之间的区别
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, 在JSON-RPC批量请求中
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-虽然这两者都适用于子图（Subgraph），但是对于想要构建[Substreams](substreams/) 的开发人员，始终需要一个Firehose，比如构建Substreams-powered子图(cookbook/substreams-powered-subgraphs/)。此外，与JSON-RPC相比，Firehose可以实现更快的索引速度。
+### 2. Firehose Integration
 
-新的EVM链集成者也可以考虑基于Firehose的方法，考虑到substreams的好处和其大规模并行化的索引能力。支持这两种方法允许开发人员在新链上选择构建substreams或子图。
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> 注意：基于Firehose的EVM链集成仍需要索引器运行链的归档RPC节点，以正确索引子图。这是因为Firehose无法提供通常通过eth_call RPC方法访问的智能合约状态。 (值得提醒的是，eth_calls对于开发人员来说不是一个好的实践(https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## 测试EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-为了使Graph Node能够从EVM链中获取数据，RPC节点必须公开以下EVM JSON RPC方法：
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \\（对于历史块，使用EIP-1898 - 需要归档节点）：
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, 在JSON-RPC批量请求中
-- _`trace_filter`_ \_（可选择支持Graph Node的调用处理程序）
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node配置
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-首先准备您的本地环境
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node配置
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. 修改此行(https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22)，包括新网络名称和符合EVM JSON RPC的URL
-   > 不要更改环境变量名称本身。它必须保持为ethereum，即使网络名称不同也是如此。
-3. 运行IPFS节点，或使用The Graph使用的IPFS节点：https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. 创建一个简单的示例子图。以下是一些选项：
-   1. 预打包的[Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323)智能合约和子图是一个很好的起点
-   2. 使用任何现有的智能合约或solidity开发环境使用Hardhat和Graph插件引导本地子图(https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. 在Graph Node中创建子图：graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT
-5. 将子图发布到Graph Node：graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-如果没有错误，Graph Node应该正在同步部署的子图。给它一些时间来同步，然后向API端点发送一些GraphQL查询。
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## 集成一个新的Firehose启用链
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. 创建一个简单的示例子图。以下是一些选项：
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+如果没有错误，Graph Node应该正在同步部署的子图。给它一些时间来同步，然后向API端点发送一些GraphQL查询。
 
-使用Firehose方法也可以集成新的链。这是目前非EVM链的最佳选择，也是支持substreams的要求。有关如何使用Firehose，为新链添加Firehose支持以及如何将其与Graph Node集成的其他文档。集成者的推荐文档：
+## Substreams-powered Subgraphs
 
-1. Firehose的通用文档(firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. 通过Firehose将Graph Node与新链集成(https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From fea1182126135e34dec66c7659e629c6f1eb9865 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:42 -0500
Subject: [PATCH 1101/1325] New translations new-chain-integration.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/ur/new-chain-integration.mdx b/website/pages/ur/new-chain-integration.mdx
index cc4e1f532644..8a348a4970ea 100644
--- a/website/pages/ur/new-chain-integration.mdx
+++ b/website/pages/ur/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: نئے نیٹ ورکس کو انٹیگریٹ کرنا
+title: New Chain Integration
 ---
 
-گراف نوڈ فی الحال ذیل میں دی گئ چین کی اقسام سے ڈیٹا انڈیکس کر سکتا ہے:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- ایتھیریم, بذریعہ EVM JSON-RPC اور [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR، بذریعہ [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos، بذریعہ [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave، ایک [Arweave Firehose] کے ذریعے (https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-اگر آپ ان میں سے کسی بھی چین میں دلچسپی رکھتے ہیں تو، انٹیگریشن گراف نوڈ کی کنفگریشن اور جانچ کا معاملہ ہے۔
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-اگر آپ مختلف قسم کی چین میں دلچسپی رکھتے ہیں تو، گراف نوڈ کے ساتھ ایک نئی انٹیگریشن ضرور بنایا جانا چاہیے۔ ہمارا تجویز کردہ نقطہ نظر زیر بحث چین کے لیے ایک نیا فائر ہوز تیار کر رہا ہے اور پھر اس فائر ہوز کا گراف نوڈ کے ساتھ انٹیگریشن۔ ذیل میں مزید معلومات ہیں۔
+## Integration Strategies
 
-**1۔ EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-اگر بلاکچین EVM کے برابر ہے اور کلائنٹ/نوڈ معیاری EVM JSON-RPC API کو ظاہر کرتا ہے، تو گراف نوڈ کو نئی چین کی انڈیکس کرنے کے قابل ہونا چاہیے۔ مزید معلومات کے لیے، [EVM JSON-RPC کی ٹیسٹنگ کرنا](new-chain-integration#testing-an-evm-json-rpc) سے رجوع کریں۔
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. فائر ہوز**
+#### EVM JSON-RPC کی ٹیسٹ کرنا
 
-غیر EVM پر مبنی چینز کے لیے، گراف نوڈ کو gRPC اور معروف قسم کی تعریفوں کے ذریعے بلاکچین ڈیٹا کو ہضم کرنا چاہیے۔ یہ [فائر ہوز](فائر ہوز/) کے ذریعے کیا جا سکتا ہے، جو کہ [سٹریمنگ فاسٹ](https://www.streamingfast.io/) کی تیار کردہ ایک نئی ٹیکنالوجی ہے جو فائلوں پر مبنی اور سٹریمنگ کا استعمال کرتے ہوئے ایک انتہائی قابل توسیع انڈیکسنگ بلاکچین حل فراہم کرتی ہے۔ پہلا نقطہ نظر. اگر آپ کو فائر ہوز ڈیولپمنٹ میں مدد کی ضرورت ہو تو [سٹریمنگ فاسٹ ٹیم](میل کریں:integrations@streamingfast.io/) سے رابطہ کریں۔
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## EVM JSON-RPC اور Firehose کے درمیان فرق
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-جب کہ دونوں سب گرافس کے لیے موزوں ہیں، فائر ہوز ہمیشہ ڈویلپرز کے لیے درکار ہوتا ہے جو [سب سٹریمز](سب سٹریمز/) کے ساتھ تعمیر کرنا چاہتے ہیں، جیسا کہ [سب سٹریمز سے چلنے والے سب گرافس](cookbook/substreams-powered-subgraphs/)۔ اس کے علاوہ، فائر ہوز JSON-RPC کے مقابلے میں بہتر انڈیکسنگ کی رفتار کی اجازت دیتا ہے۔
+### 2. Firehose Integration
 
-نئے EVM چین انٹیگریٹرز سب سٹریمز کے فوائد اور اس کے بڑے پیمانے پر متوازی انڈیکسنگ کی صلاحیتوں کو دیکھتے ہوئے، Firehose پر مبنی نقطہ نظر پر بھی غور کر سکتے ہیں۔ دونوں کو سپورٹ کرنے سے ڈویلپرز کو نئی چین کے لیے سب سٹریمز کی تعمیر یا سب گراف کے درمیان انتخاب کرنے کی اجازت ملتی ہے۔
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **نوٹ**: EVM چینز کے لیے فائر ہوز پر مبنی انٹیگریشن کے لیے اب بھی انڈیکسرز کو چین کے آرکائیو RPC نوڈ کو صحیح طریقے سے سب گرافس کو انڈیکس کرنے کے لیے چلانے کی ضرورت ہوگی۔ یہ فائر ہوز کی سمارٹ کنٹریکٹ سٹیٹ فراہم کرنے میں ناکامی کی وجہ سے ہے جو عام طور پر `eth_call` RPC طریقہ سے قابل رسائی ہے۔ (یہ یاد دلانے کے قابل ہے کہ ایتھ_کالز [ڈویلپرز کے لیے اچھا عمل نہیں ہے](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## EVM JSON-RPC کی ٹیسٹ کرنا
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-گراف نوڈ کے لیے EVM چین سے ڈیٹا ہضم کرنے کے لیے، RPC نوڈ کو درج ذیل EVM JSON RPC طریقوں کو بے نقاب کرنا چاہیے:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(تاریخی بلاکس کے لیے, EIP-1898 کے ساتھ - آرکائیو نوڈ کی ضرورت ہے):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(کال ہینڈلرز کو سپورٹ کرنے کے لیے گراف نوڈ کے لیے اختیاری طور پر درکار ہے)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### گراف نوڈ کنفگریشن
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**اپنے مقامی ماحول کو تیار کرکے شروع کریں**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## گراف نوڈ کنفگریشن
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [گراف نوڈ کی نقل بنائیں](https://github.com/graphprotocol/graph-node)
-2. نئے نیٹ ورک کا نام اور EVM JSON RPC کے مطابق URL کو شامل کرنے کے لیے [اس لائن](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) میں ترمیم کریں۔
-   > env var نام ہی تبدیل نہ کریں۔ نیٹ ورک کا نام مختلف ہونے کے باوجود اسے 'ایتھیریم' ہی رہنا چاہیے۔
-3. IPFS نوڈ چلائیں یا گراف کے ذریعہ استعمال کردہ استعمال کریں: https://api.thegraph.com/ipfs/
 
-**مقامی طور پر سب گراف کو تعینات کر کے انٹیگریشن کی جانچ کریں**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. ایک سادہ مثالی سب گراف بنائیں۔ کچھ آپشنز ذیل میں ہیں:
-   1. پہلے سے پیک [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) سمارٹ کنٹریکٹ اور سب گراف ایک اچھا نقطہ آغاز ہے
-   2. کسی بھی موجودہ سمارٹ کنٹریکٹ یا سولیٹی ڈویلپر ماحول سے مقامی سب گراف کو بوٹسٹریپ کریں [گراف پلگ ان کے ساتھ Hardhat کا استعمال کرتے ہوئے](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. اپنا سب گراف گراف نوڈ میں بنائیں: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. اپنا سب گراف گراف نوڈ پر شائع کریں: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-اگر کوئی خرابی نہیں ہے تو گراف نوڈ کو تعینات سب گراف کو ہم آہنگ کرنا چاہیے۔ اسے مطابقت پذیری کے لیے وقت دیں، پھر لاگز میں پرنٹ کردہ API اینڈ پوائنٹ پر کچھ GraphQL کیوریز بھیجیں۔
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## فائر ہوز سے چلنے والی ایک نئی چین کو انٹیگریٹ کرنا
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. ایک سادہ مثالی سب گراف بنائیں۔ کچھ آپشنز ذیل میں ہیں:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+اگر کوئی خرابی نہیں ہے تو گراف نوڈ کو تعینات سب گراف کو ہم آہنگ کرنا چاہیے۔ اسے مطابقت پذیری کے لیے وقت دیں، پھر لاگز میں پرنٹ کردہ API اینڈ پوائنٹ پر کچھ GraphQL کیوریز بھیجیں۔
 
-فائر ہوز اپروچ کا استعمال کرتے ہوئے ایک نئی چین کو انٹیگریٹ کرنا بھی ممکن ہے۔ یہ فی الحال غیر EVM چینز کے لیے بہترین آپشن ہے اور سب سٹریمز سپورٹ کی ضرورت ہے۔ مزید دستاویزات اس بات پر مرکوز ہیں کہ فائر ہوز کیسے کام کرتا ہے، ایک نئی چین کے لیے فائر ہوز سپورٹ شامل کرنا اور اسے گراف نوڈ کے ساتھ انٹیگریٹ کرنا۔ انٹیگریٹز کے لیے تجویز کردہ دستاویزات:
+## Substreams-powered Subgraphs
 
-1. [فائر ہوز پر عمومی دستاویزات](فائر ہوز/)
-2. [ایک نئی چین کے لیے فائر ہوز سپورٹ شامل کرنا](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [فائر ہوز کے ذریعے ایک نئی چین کے ساتھ گراف نوڈ کو انٹیگریٹ کرنا](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 1fcecfc7e3d9a7c4780b81625b46f0c192ed18dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:43 -0500
Subject: [PATCH 1102/1325] New translations new-chain-integration.mdx
 (Vietnamese)

---
 website/pages/vi/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/vi/new-chain-integration.mdx b/website/pages/vi/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/vi/new-chain-integration.mdx
+++ b/website/pages/vi/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 4ba0270d01ce15798bf9f71150a8661181a7fca7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:44 -0500
Subject: [PATCH 1103/1325] New translations new-chain-integration.mdx
 (Marathi)

---
 website/pages/mr/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/mr/new-chain-integration.mdx b/website/pages/mr/new-chain-integration.mdx
index 35b2bc7c8b4a..534d6701efdb 100644
--- a/website/pages/mr/new-chain-integration.mdx
+++ b/website/pages/mr/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: New Chain Integration
 ---
 
-Graph Node can currently index data from the following chain types:
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## Integration Strategies
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose Integration
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
 
----
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
 
-## Testing an EVM JSON-RPC
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
 
-**Start by preparing your local environment**
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
----
+### Testing an EVM JSON-RPC by locally deploying a subgraph
 
-## Integrating a new Firehose-enabled chain
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## Substreams-powered Subgraphs
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From c760e309014f6a736ff22221aa8fb034ad099bf4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:45 -0500
Subject: [PATCH 1104/1325] New translations new-chain-integration.mdx (Hindi)

---
 website/pages/hi/new-chain-integration.mdx | 97 ++++++++++++----------
 1 file changed, 51 insertions(+), 46 deletions(-)

diff --git a/website/pages/hi/new-chain-integration.mdx b/website/pages/hi/new-chain-integration.mdx
index 35b2bc7c8b4a..e2bd36ba8ad3 100644
--- a/website/pages/hi/new-chain-integration.mdx
+++ b/website/pages/hi/new-chain-integration.mdx
@@ -1,75 +1,80 @@
 ---
-title: Integrating New Networks
+title: नई श्रृंखला एकीकरण
 ---
 
-Graph Node can currently index data from the following chain types:
+चेन अपने पारिस्थितिकी तंत्र में सबग्राफ़ समर्थन लाने के लिए एक नया `graph-node` एकीकरण शुरू कर सकती हैं। सबग्राफ़ एक शक्तिशाली इंडेक्सिंग उपकरण हैं, जो डेवलपर्स के लिए संभावनाओं की एक नई दुनिया खोलते हैं। ग्राफ़ नोड पहले से ही यहाँ सूचीबद्ध चेन से डेटा को इंडेक्स करता है। यदि आप नए एकीकरण में रुचि रखते हैं, तो दो एकीकरण रणनीतियाँ हैं:
 
-- Ethereum, via EVM JSON-RPC and [Ethereum Firehose](https://github.com/streamingfast/firehose-ethereum)
-- NEAR, via a [NEAR Firehose](https://github.com/streamingfast/near-firehose-indexer)
-- Cosmos, via a [Cosmos Firehose](https://github.com/graphprotocol/firehose-cosmos)
-- Arweave, via an [Arweave Firehose](https://github.com/graphprotocol/firehose-arweave)
+1. EVM JSON-RPC
+2. Firehose: सभी Firehose एकीकरण समाधान में Substreams शामिल हैं, जो Firehose पर आधारित एक बड़े पैमाने पर स्ट्रीमिंग इंजन है, जिसमें स्वदेशी `graph-node` समर्थन है, जो समानांतर रूपांतरण की अनुमति देता है।
 
-If you are interested in any of those chains, integration is a matter of Graph Node configuration and testing.
+> ध्यान दें कि जबकि अनुशंसित तरीका सभी नए चेन के लिए एक नया Firehose विकसित करना है, यह केवल गैर-EVM चेन के लिए आवश्यक है।
 
-If you are interested in a different chain type, a new integration with Graph Node must be built. Our recommended approach is developing a new Firehose for the chain in question and then the integration of that Firehose with Graph Node. More info below.
+## एकीकरण रणनीतियाँ
 
-**1. EVM JSON-RPC**
+### 1. EVM JSON-RPC
 
-If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain. For more information, refer to [Testing an EVM JSON-RPC](new-chain-integration#testing-an-evm-json-rpc).
+यदि ब्लॉकचेन EVM समान है और क्लाइंट/नोड मानक EVM JSON-RPC API को एक्सपोज़ करता है, तो Graph Node को नए चेन को इंडेक्स करने में सक्षम होना चाहिए।
 
-**2. Firehose**
+#### Testing an EVM JSON-RPC
 
-For non-EVM-based chains, Graph Node must ingest blockchain data via gRPC and known type definitions. This can be done via [Firehose](firehose/), a new technology developed by [StreamingFast](https://www.streamingfast.io/) that provides a highly-scalable indexing blockchain solution using a files-based and streaming-first approach. Reach out to the [StreamingFast team](mailto:integrations@streamingfast.io/) if you need help with Firehose development.
+Graph Node को EVM चेन से डेटा इन्गेस्ट करने के लिए, RPC नोड को निम्नलिखित EVM JSON-RPC विधियों को एक्सपोज़ करना होगा:
 
-## Difference between EVM JSON-RPC & Firehose
+- `eth_getLogs`
+- eth_call (ऐतिहासिक ब्लॉक्स के लिए, EIP-1898 के साथ - आर्काइव नोड की आवश्यकता)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- trace_filter (वैकल्पिक रूप से Graph Node को कॉल हैंडलर्स का समर्थन करने के लिए आवश्यक)
 
-While the two are suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](substreams/), like building [Substreams-powered subgraphs](cookbook/substreams-powered-subgraphs/). In addition, Firehose allows for improved indexing speeds when compared to JSON-RPC.
+### 2. Firehose एकीकरण
 
-New EVM chain integrators may also consider the Firehose-based approach, given the benefits of substreams and its massive parallelized indexing capabilities. Supporting both allows developers to choose between building substreams or subgraphs for the new chain.
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) एक अगली पीढ़ी की निष्कर्षण परत है। यह फ्लैट फ़ाइलों में इतिहास एकत्र करता है और वास्तविक समय में स्ट्रीम करता है। Firehose तकनीक उन पॉलिंग API कॉल्स को एक डेटा स्ट्रीम से बदल देती है, जो एक पुश मॉडल का उपयोग करती है, जिससे डेटा को इंडेक्सिंग नोड तक तेजी से भेजा जा सके। यह सिंकिंग और इंडेक्सिंग की गति बढ़ाने में मदद करता है।
 
-> **NOTE**: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that eth_calls are [not a good practice for developers](https://thegraph.com/blog/improve-subgraph-performance-reduce-eth-calls/))
+फायरहोज़ को चेन में एकीकृत करने का प्राथमिक तरीका RPC पॉलिंग रणनीति का उपयोग करना है। हमारी पॉलिंग एल्गोरिदम नए ब्लॉक के आने का पूर्वानुमान लगाएगी और उस समय के करीब नए ब्लॉक के लिए जाँच करने की दर बढ़ा देगी, जिससे यह एक बहुत कम लेटेंसी और प्रभावी समाधान बन जाता है। फायरहोज़ के एकीकरण और रखरखाव में मदद के लिए, [स्ट्रीमिंगफास्ट टीम](https://www.streamingfast.io/firehose-integration-program) से संपर्क करें। नए चेन और उनके एकीकृतकर्ताओं को फायरहोज़ और सबस्ट्रीम द्वारा उनके पारिस्थितिकी तंत्र में लाए गए [फोर्क जागरूकता](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) और विशाल समानांतर इंडेक्सिंग क्षमताओं की सराहना होगी।
 
----
+> नोट: StreamingFast टीम द्वारा की गई सभी एकीकरणों में श्रृंखला के कोडबेस में Firehose प्रतिकृति प्रोटोकॉल के लिए रखरखाव शामिल है।StreamingFast किसी भी परिवर्तन को ट्रैक करता है और जब आप कोड बदलते हैं और जब StreamingFastकोड बदलता है, तो बाइनरी जारी करता है। इसमें प्रोटोकॉल के लिए Firehose/Substreamsबाइनरी जारी करना, श्रृंखला के ब्लॉक मॉडल के लिए Substreamsमॉड्यूल को बनाए रखना, और आवश्यकता होने पर ब्लॉकचेन नोड के लिए इंस्ट्रुमेंटेशन के साथ बाइनरी जारी करना शामिल है।
 
-## Testing an EVM JSON-RPC
+#### ईवीएम (`geth`) चेन के लिए विशिष्ट फायरहोज़ इंस्ट्रूमेंटेशन
 
-For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON RPC methods:
+EVM चेन के लिए, एक गहरे स्तर के डेटा को प्राप्त करने के लिए `geth` [लाइव-ट्रेसर](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0) का उपयोग किया जाता है, जो गो-एथेरियम और स्ट्रीमिंगफास्ट के बीच सहयोग है, जो उच्च थ्रूपुट और समृद्ध लेनदेन ट्रेसिंग प्रणाली बनाने के लिए है। लाइव ट्रेसर सबसे व्यापक समाधान है, जो [विस्तारित](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) ब्लॉक विवरण का परिणाम है। यह नए इंडेक्सिंग पैरेडाइम्स की अनुमति देता है, जैसे राज्य परिवर्तनों, कॉल्स, पैरेंट कॉल ट्रीज़ के आधार पर घटनाओं का पैटर्न मिलाना, या स्मार्ट कॉन्ट्रैक्ट में वास्तविक वेरिएबल्स में बदलाव के आधार पर घटनाओं को ट्रिगर करना।
 
-- `eth_getLogs`
-- `eth_call` \_(for historical blocks, with EIP-1898 - requires archive node):
-- `eth_getBlockByNumber`
-- `eth_getBlockByHash`
-- `net_version`
-- `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- _`trace_filter`_ _(optionally required for Graph Node to support call handlers)_
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
 
-### Graph Node Configuration
+> नोट: Firehose में यह सुधार तब आवश्यक है जब चेन EVM इंजन `geth संस्करण 1.13.0` और उससे ऊपर का उपयोग करें।
 
-**Start by preparing your local environment**
+## EVM विचार - JSON-RPC और Firehose के बीच का अंतर
+
+जबकि JSON-RPC और Firehose दोनों सबग्राफ़ के लिए उपयुक्त हैं, Firehose हमेशा उन डेवलपर्स के लिए आवश्यक है जो [Substreams](https://substreams.streamingfast.io) के साथ निर्माण करना चाहते हैं। Substreams का समर्थन करने से डेवलपर्स को नए चेन के लिए [Substreams-समर्थित सबग्राफ़](https://cookbook/substreams-powered-subgraphs) बनाने की अनुमति मिलती है, और इससे आपके सबग्राफ़ के प्रदर्शन में सुधार करने की क्षमता होती है। इसके अतिरिक्त, Firehose — `graph-node` के JSON-RPC निष्कर्षण स्तर के लिए एक ड्रॉप-इन प्रतिस्थापन के रूप में — सामान्य अनुक्रमण के लिए आवश्यक RPC कॉल की संख्या को 90% तक कम करता है।
+
+- सभी `getLogs` कॉल्स और राउंडट्रिप्स को एकल स्ट्रीम द्वारा प्रतिस्थापित किया जाता है, जो सीधे `graph-node` के केंद्र में पहुंचती है; यह एकल ब्लॉक मॉडल सभी सबग्राफ्स के लिए काम करता है जिन्हें यह प्रोसेस करता है।
+
+> **NOTE**: EVM chains के लिए Firehose-based integration के लिए अभी भी Indexers को chain के संग्रह RPC node को subgraph को ठीक से index करने के लिए चलाने की आवश्यकता होगी। यह `eth_call` RPC विधि द्वारा आम तौर पर पहुंच योग्य smart contract स्थिति प्रदान करने में Firehosesकी असमर्थता के कारण है। (It's worth reminding that eth_calls are [not a good practice for developers](/))
+
+## Graph Node Configuration
+
+ग्राफ नोड को कॉन्फ़िगर करना आपके स्थानीय वातावरण को तैयार करने के समान आसान है। एक बार जब आपका स्थानीय वातावरण सेट हो जाता है, तो आप एक उपग्राफ को स्थानीय रूप से डिप्लॉय करके एकीकरण का परीक्षण कर सकते हैं।
 
 1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
-2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON RPC compliant URL
-   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
-3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
 
-**Test the integration by locally deploying a subgraph**
+2. नए network नाम और EVM JSON RPC अनुरूप URL को शामिल करने के लिए [this line] (https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) को संशोधित करें
 
-1. Install [graph-cli](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)
-2. Create a simple example subgraph. Some options are below:
-   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
-   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
-3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
-4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
-5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+   > कृपया पर्यावरण चर ethereum को खुद नाम में बदलें नहीं। यही रहना चाहिए, चाहे network का नाम भिन्न हो।
 
-Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+3. एक IPFS node चलाएं या उसे The Graph द्वारा उपयोग किया जाने वाले node का उपयोग करें: https://api.thegraph.com/ipfs/
 
----
+### EVM JSON-RPC का परीक्षण करने के लिए स्थानीय रूप से एक Subgraph तैनात करना
 
-## Integrating a new Firehose-enabled chain
+1. [graph-cli] स्थापित करें(https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. Pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract और subgraph एक अच्छा शुरुआती बिंदु है
+   2. किसी भी मौजूदा smart contract या solidity dev वातावरण से एक local subgraph को Bootstrap करें [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. परिणामी `subgraph.yaml` को [`dataSources.network`](http://dataSources.network) को उसी नाम में बदलकर अनुकूलित करें जो पहले Graph Node पर दिया गया था।
+4. अपने subgraph को Graph Node में बनाएँ: graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT
+5. अपने 'subgraph' को Graph Node पर प्रकाशित करें: graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
 
-Integrating a new chain is also possible using the Firehose approach. This is currently the best option for non-EVM chains and a requirement for substreams support. Additional documentation focuses on how Firehose works, adding Firehose support for a new chain and integrating it with Graph Node. Recommended docs for integrators:
+## सबस्ट्रीम-संचालित सबग्राफ की सेवा
 
-1. [General docs on Firehose](firehose/)
-2. [Adding Firehose support for a new chain](https://firehose.streamingfast.io/integrate-new-chains/integration-overview)
-3. [Integrating Graph Node with a new chain via Firehose](https://github.com/graphprotocol/graph-node/blob/master/docs/implementation/add-chain.md)
+StreamingFast-के नेतृत्व वाले Firehose/Substreams इंटीग्रेशन के लिए, मूलभूत Substreams मॉड्यूल (जैसे कि डिकोडेड लेनदेन, लॉग और स्मार्ट-कॉन्ट्रैक्ट इवेंट) और Substreams कोडजन टूल्स के लिए बुनियादी समर्थन शामिल है। ये टूल [Substreams-समर्थित सबग्राफ़](https://sps.introduction) सक्षम करने की क्षमता प्रदान करते हैं। [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) का पालन करें और `substreams codegen subgraph` चलाएं ताकि आप कोडजन टूल्स का अनुभव कर सकें।

From 69e3149771b75b80138e7f7d14435f23eeb6f7f3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:46 -0500
Subject: [PATCH 1105/1325] New translations new-chain-integration.mdx
 (Swahili)

---
 website/pages/sw/new-chain-integration.mdx | 80 ++++++++++++++++++++++
 1 file changed, 80 insertions(+)
 create mode 100644 website/pages/sw/new-chain-integration.mdx

diff --git a/website/pages/sw/new-chain-integration.mdx b/website/pages/sw/new-chain-integration.mdx
new file mode 100644
index 000000000000..534d6701efdb
--- /dev/null
+++ b/website/pages/sw/new-chain-integration.mdx
@@ -0,0 +1,80 @@
+---
+title: New Chain Integration
+---
+
+Chains can bring subgraph support to their ecosystem by starting a new `graph-node` integration. Subgraphs are a powerful indexing tool opening a world of possibilities for developers. Graph Node already indexes data from the chains listed here. If you are interested in a new integration, there are 2 integration strategies:
+
+1. **EVM JSON-RPC**
+2. **Firehose**: All Firehose integration solutions include Substreams, a large-scale streaming engine based off Firehose with native `graph-node` support, allowing for parallelized transforms.
+
+> Note that while the recommended approach is to develop a new Firehose for all new chains, it is only required for non-EVM chains.
+
+## Integration Strategies
+
+### 1. EVM JSON-RPC
+
+If the blockchain is EVM equivalent and the client/node exposes the standard EVM JSON-RPC API, Graph Node should be able to index the new chain.
+
+#### Testing an EVM JSON-RPC
+
+For Graph Node to be able to ingest data from an EVM chain, the RPC node must expose the following EVM JSON-RPC methods:
+
+- `eth_getLogs`
+- `eth_call` (for historical blocks, with EIP-1898 - requires archive node)
+- `eth_getBlockByNumber`
+- `eth_getBlockByHash`
+- `net_version`
+- `eth_getTransactionReceipt`, in a JSON-RPC batch request
+- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+
+### 2. Firehose Integration
+
+[Firehose](https://firehose.streamingfast.io/firehose-setup/overview) is a next-generation extraction layer. It collects history in flat files and streams in real time. Firehose technology replaces those polling API calls with a stream of data utilizing a push model that sends data to the indexing node faster. This helps increase the speed of syncing and indexing.
+
+The primary method to integrate the Firehose into chains is to use an RPC polling strategy. Our polling algorithm will predict when a new block will arrive and increase the rate at which it checks for a new block near that time, making it a very low-latency and efficient solution. For help with the integration and maintenance of the Firehose, contact the [StreamingFast team](https://www.streamingfast.io/firehose-integration-program). New chains and their integrators will appreciate the [fork awareness](https://substreams.streamingfast.io/documentation/consume/reliability-guarantees) and massive parallelized indexing capabilities that Firehose and Substreams bring to their ecosystem.
+
+> NOTE: All integrations done by the StreamingFast team include maintenance for the Firehose replication protocol into the chain's codebase. StreamingFast tracks any changes and releases binaries when you change code and when StreamingFast changes code. This includes releasing Firehose/Substreams binaries for the protocol, maintaining Substreams modules for the block model of the chain, and releasing binaries for the blockchain node with instrumentation if need be.
+
+#### Specific Firehose Instrumentation for EVM (`geth`) chains
+
+For EVM chains, there exists a deeper level of data that can be achieved through the `geth` [live-tracer](https://github.com/ethereum/go-ethereum/releases/tag/v1.14.0), a collaboration between Go-Ethereum and StreamingFast, in building a high-throughput and rich transaction tracing system. The Live Tracer is the most comprehensive solution, resulting in [Extended](https://streamingfastio.medium.com/new-block-model-to-accelerate-chain-integration-9f65126e5425) block details. This enables new indexing paradigms, like pattern matching of events based on state changes, calls, parent call trees, or triggering of events based on changes to the actual variables in a smart contract.
+
+![Base block vs Extended block](/img/extended-vs-base-substreams-blocks.png)
+
+> NOTE: This improvement upon the Firehose requires chains make use of the EVM engine `geth version 1.13.0` and up.
+
+## EVM considerations - Difference between JSON-RPC & Firehose
+
+While the JSON-RPC and Firehose are both suitable for subgraphs, a Firehose is always required for developers wanting to build with [Substreams](https://substreams.streamingfast.io). Supporting Substreams allows developers to build [Substreams-powered subgraphs](/cookbook/substreams-powered-subgraphs) for the new chain, and has the potential to improve the performance of your subgraphs. Additionally, Firehose — as a drop-in replacement for the JSON-RPC extraction layer of `graph-node` — reduces by 90% the number of RPC calls required for general indexing.
+
+- All those `getLogs` calls and roundtrips get replaced by a single stream arriving into the heart of `graph-node`; a single block model for all subgraphs it processes.
+
+> NOTE: A Firehose-based integration for EVM chains will still require Indexers to run the chain's archive RPC node to properly index subgraphs. This is due to the Firehose's inability to provide smart contract state typically accessible by the `eth_call` RPC method. (It's worth reminding that `eth_calls` are not a good practice for developers)
+
+## Graph Node Configuration
+
+Configuring Graph Node is as easy as preparing your local environment. Once your local environment is set, you can test the integration by locally deploying a subgraph.
+
+1. [Clone Graph Node](https://github.com/graphprotocol/graph-node)
+
+2. Modify [this line](https://github.com/graphprotocol/graph-node/blob/master/docker/docker-compose.yml#L22) to include the new network name and the EVM JSON-RPC compliant URL
+
+   > Do not change the env var name itself. It must remain `ethereum` even if the network name is different.
+
+3. Run an IPFS node or use the one used by The Graph: https://api.thegraph.com/ipfs/
+
+### Testing an EVM JSON-RPC by locally deploying a subgraph
+
+1. Install [graph-cli](https://github.com/graphprotocol/graph-cli)
+2. Create a simple example subgraph. Some options are below:
+   1. The pre-packed [Gravitar](https://github.com/graphprotocol/example-subgraph/tree/f89bdd4628efa4badae7367d4919b3f648083323) smart contract and subgraph is a good starting point
+   2. Bootstrap a local subgraph from any existing smart contract or solidity dev environment [using Hardhat with a Graph plugin](https://github.com/graphprotocol/hardhat-graph)
+3. Adapt the resulting `subgraph.yaml` by changing `dataSources.network` to the same name previously passed on to Graph Node.
+4. Create your subgraph in Graph Node: `graph create $SUBGRAPH_NAME --node $GRAPH_NODE_ENDPOINT`
+5. Publish your subgraph to Graph Node: `graph deploy $SUBGRAPH_NAME --ipfs $IPFS_ENDPOINT --node $GRAPH_NODE_ENDPOINT`
+
+Graph Node should be syncing the deployed subgraph if there are no errors. Give it time to sync, then send some GraphQL queries to the API endpoint printed in the logs.
+
+## Substreams-powered Subgraphs
+
+For StreamingFast-led Firehose/Substreams integrations, basic support for foundational Substreams modules (e.g. decoded transactions, logs and smart-contract events) and Substreams codegen tools are included. These tools enable the ability to enable [Substreams-powered subgraphs](/sps/introduction). Follow the [How-To Guide](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application) and run `substreams codegen subgraph` to experience the codegen tools for yourself.

From 6176f40b2598e6e2e147f7313d051dfab75bd225 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:47 -0500
Subject: [PATCH 1106/1325] New translations chain-integration-overview.mdx
 (Romanian)

---
 website/pages/ro/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ro/chain-integration-overview.mdx b/website/pages/ro/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/ro/chain-integration-overview.mdx
+++ b/website/pages/ro/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From d89d5f592ca71454b5e8d1279a042b5bafa300bd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:48 -0500
Subject: [PATCH 1107/1325] New translations chain-integration-overview.mdx
 (French)

---
 website/pages/fr/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/fr/chain-integration-overview.mdx b/website/pages/fr/chain-integration-overview.mdx
index 9310317d84ca..8e3cc18a00bd 100644
--- a/website/pages/fr/chain-integration-overview.mdx
+++ b/website/pages/fr/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ Un processus d'intégration transparent et basé sur la gouvernance a été con
 
 ## Étape 1. Intégration technique
 
-- Les équipes travaillent sur une intégration de Graph Node et Firehose pour les chaînes non basées sur EVM. [Voici comment](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Les équipes lancent le processus d'intégration du protocole en créant un fil de discussion sur le forum [ici](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (sous-catégorie Nouvelles sources de données sous Gouvernance et GIPs ). L'utilisation du modèle de forum par défaut est obligatoire.
 
 ## Étape 2. Validation de l'intégration
 
-- Les équipes collaborent avec les développeurs principaux, Graph Foundation et les opérateurs d'interfaces graphiques et de passerelles réseau, tels que [Subgraph Studio](https://thegraph.com/studio/), pour garantir un processus d'intégration fluide. Cela implique de fournir l'infrastructure backend nécessaire, telle que les points de terminaison JSON RPC ou Firehose de la chaîne d'intégration. Les équipes souhaitant éviter d'auto-héberger une telle infrastructure peuvent s'appuyer sur la communauté d'opérateurs de nœuds (indexeurs) de The Graph, ce que la Fondation peut aider à faire.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Les Graph Indexeurs testent l'intégration sur le réseau de testnet du graph.
 - Les développeurs principaux et les indexeurs surveillent la stabilité, les performances et le déterminisme des données.
 
@@ -38,7 +38,7 @@ Ce processus est lié au service de données Subgraph, applicable uniquement aux
 
 Cela n’aurait un impact que sur la prise en charge du protocole pour l’indexation des récompenses sur les subgraphs alimentés par Substreams. La nouvelle implémentation de Firehose nécessiterait des tests sur testnet, en suivant la méthodologie décrite pour l'étape 2 de ce GIP. De même, en supposant que l'implémentation soit performante et fiable, un PR sur la [Matrice de support des fonctionnalités](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) serait requis ( Fonctionnalité de sous-graphe « Sous-flux de sources de données »), ainsi qu'un nouveau GIP pour la prise en charge du protocole pour l'indexation des récompenses. N'importe qui peut créer le PR et le GIP ; la Fondation aiderait à obtenir l'approbation du Conseil.
 
-### 3. Combien de temps ce processus prendra-t-il ?
+### 3. How much time will the process of reaching full protocol support take?
 
 Le temps nécessaire à la mise en réseau principal devrait être de plusieurs semaines, variant en fonction du temps de développement de l'intégration, de la nécessité ou non de recherches supplémentaires, de tests et de corrections de bugs et, comme toujours, du calendrier du processus de gouvernance qui nécessite les commentaires de la communauté.
 
@@ -46,4 +46,4 @@ La prise en charge du protocole pour l'indexation des récompenses dépend de la
 
 ### 4. Comment les priorités seront-elles gérées ?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From ccfb5c961cdef6b47994e5aa475c7f43d138fb99 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:49 -0500
Subject: [PATCH 1108/1325] New translations chain-integration-overview.mdx
 (Spanish)

---
 website/pages/es/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/es/chain-integration-overview.mdx b/website/pages/es/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/es/chain-integration-overview.mdx
+++ b/website/pages/es/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 6ab9ba7e3bf0082b5d5605ef93980f37297c4058 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:50 -0500
Subject: [PATCH 1109/1325] New translations chain-integration-overview.mdx
 (Arabic)

---
 website/pages/ar/chain-integration-overview.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/ar/chain-integration-overview.mdx b/website/pages/ar/chain-integration-overview.mdx
index 501143bfb88d..b8e41513fa9d 100644
--- a/website/pages/ar/chain-integration-overview.mdx
+++ b/website/pages/ar/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ title: نظرة عامة حول عملية التكامل مع الشبكة
 
 ## المرحلة الأولى: التكامل التقني
 
-- تعمل الفرق على تكامل نقطة الغراف وفايرهوز بالنسبة للسلاسل الغير مبنية على آلة الإيثيريوم الإفتراضية. إليك الطريقة(https://thegraph. com/docs/en/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - تستهل الفرق عملية التكامل مع البروتوكول من خلال إنشاء موضوع في المنتدى هنا(https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (الفئة الفرعية "مصادر البيانات الجديدة" تحت قسم "الحوكمة واقتراحات تحسين الغراف"). استخدام قالب المنتدى الافتراضي إلزامي.
 
 ## المرحلة الثانية: التحقق من صحة التكامل
 
-- تتعاون الفرق مع المطورين الأساسيين، ومؤسسة الغراف، ومشغلي واجهات المستخدم الرسومية وبوابات الشبكة مثل سبغراف استوديو(https://thegraph.com/studio/) لضمان عملية تكامل سلسة. يتضمن ذلك توفير بنية تحتية للواجهة الخلفية، مثل إجراء الإستدعاء عن بعد -للترميز الكائني لجافاسكريبت- الخاص بالسلسلة المتكاملة أو نقاط نهاية فايرهوز. الفرق الراغبة في تجنب الإستضافة الذاتية مثل هذه البنية التحتية يمكنهم الإستفادة من مشغلي النقاط (المفهرسين) في مجتمع الغراف للقيام بذلك، والذي يمكن للمؤسسة المساعدة من خلاله.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - مفهرسو الغراف يختبرون التكامل على شبكة إختبار الغراف.
 - يقوم المطورون الأساسيون والمفهرسون بمراقبة استقرار، وأداء، وحتمية البيانات.
 
@@ -38,12 +38,12 @@ Ready to shape the future of The Graph Network? [Start your proposal](https://gi
 
 هذا سيؤثر فقط على دعم البروتوكول لمكافآت الفهرسة على الغرافات الفرعية المدعومة من سبستريمز. تنفيذ الفايرهوز الجديد سيحتاج إلى الفحص على شبكة الاختبار، وفقًا للمنهجية الموضحة للمرحلة الثانية في هذا المقترح لتحسين الغراف. وعلى نحو مماثل، وعلى افتراض أن التنفيذ فعال وموثوق به، سيتتطالب إنشاء طلب سحب على [مصفوفة دعم الميزات] (https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) ("مصادر بيانات سبستريمز" ميزة للغراف الفرعي)، بالإضافة إلى مقترح جديد لتحسين الغراف، لدعم البروتوكول لمكافآت الفهرسة. يمكن لأي شخص إنشاء طلب السحب ومقترح تحسين الغراف؛ وسوف تساعد المؤسسة في الحصول على موافقة المجلس.
 
-### 3. كم من الوقت ستستغرق هذه العملية؟
+### 3. How much time will the process of reaching full protocol support take?
 
 يُتوقع أن يستغرق الوصول إلى الشبكة الرئيسية عدة أسابيع، وذلك يعتمد على وقت تطوير التكامل، وما إذا كانت هناك حاجة إلى بحوث إضافية، واختبارات وإصلاحات الأخطاء، وكذلك توقيت عملية الحوكمة التي تتطلب ملاحظات المجتمع كما هو الحال دائمًا.
 
-يعتمد دعم البروتوكول لمكافآت الفهرسة على قدرة أصحاب الحصص في المضي قدماً في عمليات الفحص وجمع الملاحظات ومعالجة المساهمات في قاعدة الكود الأساسية، إذا كان ذلك قابلاً للتطبيق. هذا مرتبط مباشرة بنضج عملية التكامل ومدى استجابة فريق التكامل (والذي قد يكون أو قد لا يكون نفس الفريق المسؤول عن تنفيذ إجراء الإستدعاء عن بعد\\الفايرهوز). المؤسسة هنا لمساعدة الدعم خلال العملية بأكملها.
+يعتمد دعم البروتوكول لمكافآت الفهرسة على قدرة أصحاب الحصص في المضي قدماً في عمليات الفحص وجمع الملاحظات ومعالجة المساهمات في قاعدة الكود الأساسية، إذا كان ذلك قابلاً للتطبيق. هذا مرتبط مباشرة بنضج عملية التكامل ومدى استجابة فريق التكامل (والذي قد يكون أو قد لا يكون نفس الفريق المسؤول عن تنفيذ إجراء الإستدعاء عن بعد\الفايرهوز). المؤسسة هنا لمساعدة الدعم خلال العملية بأكملها.
 
 ### 4. كيف سيتم التعامل مع الأولويات؟
 
-كما في السؤال الثالث، سيتوقف ذلك على الجهوزية بشكل عام وعلى قدرات أصحاب الحصص المشاركين. على سبيل المثال، قد تستغرق سلسلة جديدة مع تطبيق فايرهوز جديد تمامًا وقتاً أطول من عمليات التكامل التي تم فحصها بالفعل أو التي قطعت شوطاً أطول في عملية الحوكمة. وينطبق هذا بشكل خاص على السلاسل المدعومة مسبقاً على الخدمة المستضافة (https://thegraph.com/hosted-service) أو تلك التي تعتمد على تقنيات تم اختبارها بالفعل.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From ad9b2b1708630ffe4df4b9fdc41a65ec3c6053c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:51 -0500
Subject: [PATCH 1110/1325] New translations chain-integration-overview.mdx
 (Czech)

---
 website/pages/cs/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/cs/chain-integration-overview.mdx b/website/pages/cs/chain-integration-overview.mdx
index a54cf6823bf1..673d312e81e1 100644
--- a/website/pages/cs/chain-integration-overview.mdx
+++ b/website/pages/cs/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ Pro blockchainové týmy, které usilují o [integraci s protokolem The Graph](h
 
 ## Fáze 1. Technická integrace
 
-- Týmy pracují na integraci Uzel grafu a Firehose pro řetězce nezaložené na EvM. [Zde je návod](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Týmy zahájí proces integrace protokolu vytvořením vlákna na fóru [zde](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (podkategorie Nové zdroje dat v části Správa a GIP). Použití výchozí šablony Fóra je povinné.
 
 ## Fáze 2. Ověřování integrace
 
-- Týmy spolupracují s hlavními vývojáři, Graph Foundation a provozovateli GUIs a síťových bran, jako je [Subgraph Studio](https://thegraph.com/studio/), aby byl zajištěn hladký proces integrace. To zahrnuje poskytnutí nezbytné backendové infrastruktury, jako jsou koncové body JSON RPC nebo Firehose integračního řetězce. Týmy, které se chtějí vyhnout vlastnímu hostování takové infrastruktury, mohou k tomu využít komunitu provozovatelů uzlů (Indexers) Grafu, s čímž jim může pomoci nadace.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graf Indexers testují integraci na testovací síti Grafu.
 - Vývojáři jádra a indexátoři sledují stabilitu, výkon a determinismus dat.
 
@@ -38,7 +38,7 @@ Tento proces souvisí se službou Datová služba podgrafů a vztahuje se pouze
 
 To by mělo vliv pouze na podporu protokolu pro indexování odměn na podgrafech s podsílou. Novou implementaci Firehose by bylo třeba testovat v testnetu podle metodiky popsané pro fázi 2 v tomto GIP. Podobně, za předpokladu, že implementace bude výkonná a spolehlivá, by bylo nutné provést PR na [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) (`Substreams data sources` Subgraph Feature) a také nový GIP pro podporu protokolu pro indexování odměn. PR a GIP může vytvořit kdokoli; nadace by pomohla se schválením Radou.
 
-### 3. Kolik času zabere tento proces?
+### 3. How much time will the process of reaching full protocol support take?
 
 Očekává se, že doba do uvedení do mainnetu bude trvat několik týdnů a bude se lišit v závislosti na době vývoje integrace, na tom, zda bude zapotřebí další výzkum, testování a opravy chyb, a jako vždy na načasování procesu řízení, který vyžaduje zpětnou vazbu od komunity.
 
@@ -46,4 +46,4 @@ Podpora protokolu pro odměny za indexování závisí na šířce pásma zúča
 
 ### 4. Jak budou řešeny priority?
 
-Podobně jako u bodu č. 3 bude záležet na celkové připravenosti a šířce pásma zúčastněných stran. Například nový řetězec se zcela novou implementací Firehose může trvat déle než integrace, které již byly testovány v praxi nebo jsou v procesu správy dále. To platí zejména pro řetězce, které byly dříve podporovány na [hostované službě](https://thegraph.com/hosted-service) nebo které se spoléhají na již otestované stacky.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 3a2c53caf73d1872a475bd46cc6772382b95ef52 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:52 -0500
Subject: [PATCH 1111/1325] New translations chain-integration-overview.mdx
 (German)

---
 website/pages/de/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/de/chain-integration-overview.mdx b/website/pages/de/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/de/chain-integration-overview.mdx
+++ b/website/pages/de/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 69818f5bc56edc1b02a325221046e0e2584e9373 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:53 -0500
Subject: [PATCH 1112/1325] New translations chain-integration-overview.mdx
 (Italian)

---
 website/pages/it/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/it/chain-integration-overview.mdx b/website/pages/it/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/it/chain-integration-overview.mdx
+++ b/website/pages/it/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 9e6c105e4e11367dcff7b7319df49e4f0d641f1a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:54 -0500
Subject: [PATCH 1113/1325] New translations chain-integration-overview.mdx
 (Japanese)

---
 website/pages/ja/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ja/chain-integration-overview.mdx b/website/pages/ja/chain-integration-overview.mdx
index 7d37bf9c9393..2a72e99283a4 100644
--- a/website/pages/ja/chain-integration-overview.mdx
+++ b/website/pages/ja/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ title: チェーン統合プロセスの概要
 
 ## ステージ 1. 技術的統合
 
-- チームは、非 EVM ベースのチェーン用の Graph Node 統合と Firehose に取り組んでいます。 [Here's how](/new-chain-integration/)。
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - チームは、プロトコルの統合プロセスを開始するために、[here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)のフォーラムスレッドを作成します（Governance & GIPsの下にあるNew Data Sourcesのサブカテゴリ内）。デフォルトのフォーラムテンプレートの使用が必須です。
 
 ## ステージ 2. 統合の検証
 
-- チームは、コア開発者、Graph Foundation、および [Subgraph Studio](https://thegraph.com/studio/) のようなGUIやネットワークゲートウェイのオペレーターと協力して、スムーズな統合プロセスを確保しています。これには、統合するチェーンのJSON RPCやFirehoseエンドポイントなどの必要なバックエンドインフラストラクチャを提供することが含まれます。このようなインフラストラクチャをセルフホスティングしたくないチームは、The Graphのノードオペレーター（インデクサー）のコミュニティを活用して、それを行うことができます。これに関しては、Foundationがサポートを提供できます。
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexer は、The Graph のテストネットで統合をテストします。
 - コア開発者とインデクサーは、安定性、パフォーマンス、およびデータの決定性を監視します。
 
@@ -38,7 +38,7 @@ The Graph Network の未来を形作る準備はできていますか? [Start yo
 
 これは、サブストリームで動作するサブグラフに対するインデックスリワードのプロトコルサポートに影響を与えるものです。新しいFirehoseの実装は、このGIPのステージ2に概説されている方法論に従って、テストネットでテストされる必要があります。同様に、実装がパフォーマンスが良く信頼性があると仮定して、[Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md)へのPR（「Substreamsデータソース」サブグラフ機能）が必要です。また、インデックスリワードのプロトコルサポートに関する新しいGIPも必要です。誰でもPRとGIPを作成できますが、Foundationは評議会の承認をサポートします。
 
-### 3. このプロセスにはどのくらい時間がかかりますか?
+### 3. How much time will the process of reaching full protocol support take?
 
 メインネットへの移行にかかる時間は、統合開発の進捗によるもの、追加の調査が必要かどうか、テストとバグ修正、そして常にコミュニティのフィードバックを必要とするガバナンスプロセスのタイミングに応じて異なりますが、数週間を予想しています。
 
@@ -46,4 +46,4 @@ The Graph Network の未来を形作る準備はできていますか? [Start yo
 
 ### 4. 優先順位はどのように扱われますか?
 
-3.と同様、全体的な準備状況や関係者の帯域幅によります。例えば、Firehoseを導入したばかりの新しいチェーンは、すでにテスト済みの統合や、ガバナンスプロセスが進んでいる統合よりも時間がかかるかもしれません。これは特に、以前[ホスティングサービス](https://thegraph.com/hosted-service)でサポートされていたチェーンや、すでにテスト済みのスタックに依存しているチェーンに当てはまります。
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From af92d07c5ced7c4526cfae576e92061cd1c9f453 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:55 -0500
Subject: [PATCH 1114/1325] New translations chain-integration-overview.mdx
 (Korean)

---
 website/pages/ko/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ko/chain-integration-overview.mdx b/website/pages/ko/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/ko/chain-integration-overview.mdx
+++ b/website/pages/ko/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 04d96f280cea416136525395039675b875a92768 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:55 -0500
Subject: [PATCH 1115/1325] New translations chain-integration-overview.mdx
 (Dutch)

---
 website/pages/nl/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/nl/chain-integration-overview.mdx b/website/pages/nl/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/nl/chain-integration-overview.mdx
+++ b/website/pages/nl/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 0823613287cc4c63363cdb3715d8fb3654c522da Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:56 -0500
Subject: [PATCH 1116/1325] New translations chain-integration-overview.mdx
 (Polish)

---
 website/pages/pl/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/pl/chain-integration-overview.mdx b/website/pages/pl/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/pl/chain-integration-overview.mdx
+++ b/website/pages/pl/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 40362e8790968ccdd1d84fb6c4528161141c924d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:57 -0500
Subject: [PATCH 1117/1325] New translations chain-integration-overview.mdx
 (Portuguese)

---
 website/pages/pt/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/pt/chain-integration-overview.mdx b/website/pages/pt/chain-integration-overview.mdx
index 98fd802e80bf..6b239622281f 100644
--- a/website/pages/pt/chain-integration-overview.mdx
+++ b/website/pages/pt/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ Um processo de integração transparente e baseado em governança foi desenhado
 
 ## Fase 1. Integração Técnica
 
-- Equipas constroem uma integração com o Graph Node e com o Firehose para chains sem base em EVM. [Aqui está](/new-chain-integration/).
+- Por favor, visite a página de [Integração de Novas Chains](/new-chain-integration) para informações sobre o apoio do `graph-node` para chains novas.
 - Equipas iniciam o processo de integração de protocolo com a criação de um tópico de Fórum [aqui](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Nova subcategoria de Fontes de Dados sob Governança e GIPs). O uso do modelo padrão do Fórum é obrigatório.
 
 ## Fase 2. Validação de Integração
 
-- Equipas colaboram com o núcleo de programadores, com a Graph Foundation, e com operadores de interfaces gráficas e gateways de redes, como o [Subgraph Studio](https://thegraph.com/studio/), para garantir um processo de integração suave. Isto envolve a providência da infraestrutura de backend necessária, como o JSON RPC da chain a ser integrada ou os endpoints do Firehose. Equipas que querem evitar a autohospedagem de tal infraestrutura podem usar a comunidade de operadores de nodes do The Graph (Indexadores) para fazê-lo, com qual a Foundation pode oferecer ajuda.
+- Equipas colaboram com o núcleo de programadores, com a Graph Foundation, e com operadores de interfaces gráficas e gateways de redes, como o [Subgraph Studio](https://thegraph.com/studio/), para garantir um processo de integração suave. Isto envolve a providência da infraestrutura de backend necessária, como o JSON RPC da chain a ser integrada, Firehose ou os endpoints de Substreams. Equipas que querem evitar a autohospedagem de tal infraestrutura podem usar a comunidade de operadores de nodes do The Graph (Indexadores) para fazê-lo, com qual a Foundation pode oferecer ajuda.
 - Indexadores do Graph testam a integração na testnet do The Graph.
 - O núcleo de programadores e os Indexadores monitoram a estabilidade, a performance e o determinismo dos dados.
 
@@ -38,7 +38,7 @@ Este processo é relacionado ao Serviço de Dados de Subgraph, no momento aplic
 
 Isto só impactaria o apoio do protocolo a recompensas de indexação em subgraphs movidos a Substreams. A nova implementação do Firehose precisaria de testes na testnet, seguindo a metodologia sublinhada na Fase 2 deste GIP. De maneira parecida, ao assumir que a implementação seja confiável e de bom desempenho, um PR no [Matrix de Apoio de Funções](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) seria requerido (A função de Subgraph `Substreams data sources`), assim como um novo GIP para apoio do protocolo a recompensas de indexação. Qualquer pessoa pode criar o PR e a GIP; a Foundation ajudaria com o apoio do Conselho.
 
-### 3. Quanto tempo este processo levará?
+### 3. Quando tempo demora a conclusão do processo de alcance ao apoio total a protocolos?
 
 Espera-se que leve várias semanas, com variação a depender do tempo da programação da integração, da necessidade de pesquisas adicionais, testes e bugfixes, e como sempre, o timing do processo de governança que exige deliberações da comunidade.
 
@@ -46,4 +46,4 @@ O apoio do protocolo às recompensas de indexação depende da banda dos acionis
 
 ### 4. Como as prioridades serão administradas?
 
-Similar ao #3, dependará do preparo geral e da banda dos acionistas envolvidos. Por exemplo, uma nova chain, com uma implementação nova do Firehose, pode demorar mais que as integrações que já foram testadas ou estão mais adiantadas no processo de governança. Isto vale especialmente para chains antes apoiadas no [serviço hospedado](https://thegraph.com/hosted-service) ou daquelas que dependem de stacks já testados.
+Assim como no passo #3, dependerá do preparo geral e da banda dos acionistas envolvidos. Por exemplo, uma nova chain, com uma implementação nova do Firehose, pode demorar mais que as integrações que já foram testadas ou estão mais adiantadas no processo de governança.

From 33a28b2f34978fbf124e84469d2d8050e8c0211f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:58 -0500
Subject: [PATCH 1118/1325] New translations chain-integration-overview.mdx
 (Russian)

---
 website/pages/ru/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/ru/chain-integration-overview.mdx b/website/pages/ru/chain-integration-overview.mdx
index 5bffe3e6c4d7..8f95b3db17f2 100644
--- a/website/pages/ru/chain-integration-overview.mdx
+++ b/website/pages/ru/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ title: Chain Integration Process Overview
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 2fba9bb6b44c8b7f22d6cd37f0dce90486514d46 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:53:59 -0500
Subject: [PATCH 1119/1325] New translations chain-integration-overview.mdx
 (Swedish)

---
 website/pages/sv/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/sv/chain-integration-overview.mdx b/website/pages/sv/chain-integration-overview.mdx
index 3511f1e5a650..5a81ed695be7 100644
--- a/website/pages/sv/chain-integration-overview.mdx
+++ b/website/pages/sv/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ En transparent och styrbaserad integrationsprocess utformades för blockchain-te
 
 ## Fas 1. Teknisk Integration
 
-- Team arbetar med en Graph Node-integration och Firehose för icke-EVM-baserade kedjor. [Här är hur](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Team startar protokollintegrationsprocessen genom att skapa en Forumtråd [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Ny Datakällor underkategori under Governance & GIPs). Att använda standardforummallen är obligatoriskt.
 
 ## Fas 2. Integrationsvalidering
 
-- Team samarbetar med kärnutvecklare, Graph Foundation och operatörer av GUI:er och nätverksportar, såsom [Subgraf Studio](https://thegraph.com/studio/), för att säkerställa en smidig integrationsprocess. Detta innebär att tillhandahålla nödvändig backend-infrastruktur, såsom den integrerande kedjans JSON RPC eller Firehose-endpoints. Team som vill undvika självhostning av sådan infrastruktur kan dra nytta av The Graphs gemenskap av nodoperatörer (Indexers) för att göra det, vilket Stiftelsen kan hjälpa till med.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graf Indexers testar integrationen på The Graphs testnät.
 - Kärnutvecklare och Indexers övervakar stabilitet, prestanda och datadeterminism.
 
@@ -38,7 +38,7 @@ Denna process är relaterad till Subgraf Data Service och gäller endast nya Sub
 
 Detta skulle endast påverka protokollstödet för indexbelöningar på Substreams-drivna subgrafer. Den nya Firehose-implementeringen skulle behöva testas på testnätet, enligt den metodik som beskrivs för Fas 2 i detta GIP. På liknande sätt, förutsatt att implementationen är prestanda- och tillförlitlig, skulle en PR på [Funktionsstödsmatrisen](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) krävas (`Substreams data sources` Subgraf Feature), liksom en ny GIP för protokollstöd för indexbelöningar. Vem som helst kan skapa PR och GIP; Stiftelsen skulle hjälpa till med Rådets godkännande.
 
-### 3. Hur lång tid tar denna process?
+### 3. How much time will the process of reaching full protocol support take?
 
 Tiden till mainnet förväntas vara flera veckor, varierande baserat på tidpunkten för integrationsutveckling, om ytterligare forskning krävs, testning och buggfixar, och, som alltid, timingen av styrdighetsprocessen som kräver gemenskapens återkoppling.
 
@@ -46,4 +46,4 @@ Protokollstöd för indexbelöningar beror på intressenternas bandbredd att for
 
 ### 4. Hur kommer prioriteringar att hanteras?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 75c21a0105967eb154c22a1a758e8dbabde2516c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:00 -0500
Subject: [PATCH 1120/1325] New translations chain-integration-overview.mdx
 (Turkish)

---
 website/pages/tr/chain-integration-overview.mdx | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/website/pages/tr/chain-integration-overview.mdx b/website/pages/tr/chain-integration-overview.mdx
index ea08112b11fc..33a1cdb8a18c 100644
--- a/website/pages/tr/chain-integration-overview.mdx
+++ b/website/pages/tr/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ Blok zinciri ekiplerinin [Graph protokolüyle entegrasyon](https://forum.thegrap
 
 ## Aşama 1. Teknik Entegrasyon
 
-- Ekipler, EVM tabanlı olmayan zincirler için Graph Düğüm entegrasyonu ve Firehose üzerinde çalışıyorr. [İşte nasıl olduğu](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Ekipler, protokol entegrasyon sürecini bir Forum başlığı oluşturarak başlatır [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (Yönetişim ve GIP'ler altındaki Yeni Veri Kaynakları alt kategorisi). Varsayılan Forum şablonunun kullanılması zorunludur.
 
 ## Aşama 2. Entegrasyon Doğrulaması
 
-- Ekipler, entegrasyon sürecinin sorunsuz bir şekilde ilerlemesini sağlamak için çekirdek geliştiricilerle, Graph Vakfı ve [Subgraph Stüdyo](https://thegraph.com/studio/) gibi GUI'ler ve ağ geçidi operatörleri ile işbirliği yapmaktadır. Bu, entegre edilen zincirin JSON RPC veya Firehose uç noktaları gibi gerekli altyapının sağlanmasını içerir. Bu tür bir altyapıyı kendi kendine barındırmaktan kaçınmak isteyen ekipler, bunu yapmak için Graph'ın düğüm operatörleri (İndeksleyiciler) topluluğundan yararlanabilir ve Vakıf bu konuda yardımcı olabilir.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph İndeksleyicileri, entegrasyonu Graph'ın test ağında test eder.
 - Çekirdek geliştiriciler ve İndeksleyiciler kararlılığı, performansı ve veri belirleyiciliğini izler.
 
@@ -30,7 +30,7 @@ Graph Ağı'nın geleceğini şekillendirmeye hazır mısınız? Şimdi [Teklifi
 
 ## Sıkça Sorulan Sorular
 
-### 1. Bunun [World of Data Services teklifi (crwd)lbracketdwrcGIP] (https://forum.thegraph.com/t/gip-0042-a-world-of-data-services/3761) ile ilişkisi nedir?
+### 1. Bunun [World of Data Services teklifi (GIP)] (https://forum.thegraph.com/t/gip-0042-a-world-of-data-services/3761) ile ilişkisi nedir?
 
 Bu süreç Subgraph Veri Hizmeti ile ilgilidir ve yalnızca yeni Subgraph `Veri Kaynakları` için geçerlidir.
 
@@ -38,7 +38,7 @@ Bu süreç Subgraph Veri Hizmeti ile ilgilidir ve yalnızca yeni Subgraph `Veri
 
 Bu, yalnızca Substreams destekli subgraphlar'da ödüllerin indekslenmesi için protokol desteğini etkileyecektir. Yeni Firehose uygulamasının, bu GIP'de Aşama 2 için özetlenen metodolojiyi izleyerek testnet üzerinde test edilmesi gerekecektir. Benzer şekilde, uygulamanın performanslı ve güvenilir olduğu varsayıldığı takdirde, [Özellik Destek Matrisi] (https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) üzerinde bir PR (`Substreams veri kaynakları` Subgraph Özelliği) ve ödüllerin indekslenmesi amacıyla protokol desteği için yeni bir GIP gerekecektir. PR ve GIP'yi herkes oluşturabilir; Vakıf, Konsey onayı konusunda yardımcı olacaktır.
 
-### 3. Bu süreç ne kadar zaman alır?
+### 3. How much time will the process of reaching full protocol support take?
 
 Ana ağa geçiş süresinin entegrasyon geliştirme süresine, ek araştırma gerekip gerekmediğine, test ve hata düzeltmelerine ve her zaman olduğu gibi topluluk geri bildirimi gerektiren yönetişim sürecinin zamanlamasına bağlı olarak değişmek kaydıyla birkaç hafta olması beklenmektedir.
 
@@ -46,4 +46,4 @@ Ana ağa geçiş süresinin entegrasyon geliştirme süresine, ek araştırma ge
 
 ### 4. Öncelikler nasıl ele alınacak?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 9106d3265c6d69dee12a416a4b510de1805ef37e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:01 -0500
Subject: [PATCH 1121/1325] New translations chain-integration-overview.mdx
 (Ukrainian)

---
 website/pages/uk/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/uk/chain-integration-overview.mdx b/website/pages/uk/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/uk/chain-integration-overview.mdx
+++ b/website/pages/uk/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 8eca7c5084c5fdd41fdcd76acd710f73f8e7a334 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:02 -0500
Subject: [PATCH 1122/1325] New translations chain-integration-overview.mdx
 (Chinese Simplified)

---
 website/pages/zh/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/zh/chain-integration-overview.mdx b/website/pages/zh/chain-integration-overview.mdx
index d468efc7653f..e8ee7d47ad02 100644
--- a/website/pages/zh/chain-integration-overview.mdx
+++ b/website/pages/zh/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ title: 链集成过程概述
 
 ## 阶段1：技术集成
 
-- 团队致力于进行Graph Node和非EVM基础链的Firehose技术集成。[详细信息请参阅此处](/new-chain-integration/)。
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - 团队通过在[here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)（治理与GIPs下的新数据源子类别）创建一个论坛帖子来启动协议集成过程。强制使用默认的论坛模板。
 
 ## 阶段2：集成验证
 
-- 团队与核心开发者、Graph Foundation以及GUI和网络网关的运营者合作，例如[Subgraph Studio](https://thegraph.com/studio/)，以确保顺利的集成过程。这包括提供必要的后端基础设施，如集成链的JSON RPC或Firehose端点。希望避免自行托管这种基础设施的团队可以利用The Graph节点运营者（Indexers）社区来实现，而Foundation可以提供帮助。
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph索引人在The Graph的测试网上测试集成。
 - 核心开发者和索引人监控稳定性、性能和数据确定性。
 
@@ -38,7 +38,7 @@ title: 链集成过程概述
 
 这只会影响 Substreams 驱动的子图上的索引奖励的协议支持。新的 Firehose 实现需要在测试网上进行测试，遵循了本 GIP 中第二阶段所概述的方法论。同样地，假设实现是高性能且可靠的，那么需要在 [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) 上提出 PR（`Substreams 数据源` 子图特性），以及一个新的 GIP 来支持索引奖励的协议。任何人都可以创建这个 PR 和 GIP；基金会将协助获得理事会的批准。
 
-### 3. 这个过程需要多长时间？
+### 3. How much time will the process of reaching full protocol support take?
 
 主网上线预计还有数周时间，具体取决于集成开发的时间、是否需要额外的研究、测试和漏洞修复，以及始终如一地需要社区反馈的治理过程的时间。
 
@@ -46,4 +46,4 @@ title: 链集成过程概述
 
 ### 4. 如何处理优先事项？
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 9688e820a967e4d62bcc2f7040f8f721e91e47dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:03 -0500
Subject: [PATCH 1123/1325] New translations chain-integration-overview.mdx
 (Urdu (Pakistan))

---
 website/pages/ur/chain-integration-overview.mdx | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/website/pages/ur/chain-integration-overview.mdx b/website/pages/ur/chain-integration-overview.mdx
index f09de51959b9..43b53094048a 100644
--- a/website/pages/ur/chain-integration-overview.mdx
+++ b/website/pages/ur/chain-integration-overview.mdx
@@ -6,12 +6,13 @@ title: چین انٹیگریشن کے عمل کا جائزہ
 
 ## مرحلہ 1. تکنیکی انٹیگریشن
 
-- ٹیمیں غیر ای وی ایم پر مبنی چینز کے لیے گراف نوڈ انٹیگریشن اور فائر ہوز پر کام کرتی ہیں۔ [یہ طریقہ ہے](/new-chain-integration/).
-- ٹیمیں فورم تھریڈ بنا کر پروٹوکول انٹیگریشن کا عمل شروع کرتی ہیں [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)(گورننس اور GIPs کے تحت نئے ڈیٹا ذرائع ذیلی زمرہ) ۔ پہلے سے طے شدہ فورم ٹیمپلیٹ کا استعمال لازمی ہے.
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
+- ٹیمیں فورم تھریڈ بنا کر پروٹوکول انٹیگریشن کا عمل شروع کرتی ہیں [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)(گورننس اور GIPs کے تحت نئے ڈیٹا ذرائع ذیلی زمرہ)
+  ۔ پہلے سے طے شدہ فورم ٹیمپلیٹ کا استعمال لازمی ہے.
 
 ## مرحلہ 2۔ انٹیگریشن کی توثیق
 
-- ٹیمیں ہموار انٹیگریشن کے عمل کو یقینی بنانے کے لیے بنیادی ڈویلپرز، گراف فاؤنڈیشن اور GUIs اور نیٹ ورک گیٹ ویز کے آپریٹرز، جیسے کہ [Subgraph Studio](https://thegraph.com/studio/) کے ساتھ تعاون کرتی ہیں۔ اس میں ضروری بیک اینڈ انفراسٹرکچر فراہم کرنا شامل ہے، جیسے انٹیگریٹنگ چین کے JSON RPC یا فائر ہوز اینڈ پوائنٹس۔ ایسی ٹیمیں جو اس طرح کے بنیادی ڈھانچے کی خود میزبانی سے گریز کرنا چاہتی ہیں وہ ایسا کرنے کے لیے گراف کی کمیونٹی آف نوڈ آپریٹرز (انڈیکسرز) سے فائدہ اٹھا سکتی ہیں، جس میں فاؤنڈیشن مدد کر سکتی ہے.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - گراف انڈیکسرز گراف کے ٹیسٹ نیٹ پر انٹیگریشن کی جانچ کرتے ہیں.
 - کور ڈویلپرز اور انڈیکسرز استحکام، کارکردگی، اور ڈیٹا کے تعین کی نگرانی کرتے ہیں.
 
@@ -38,7 +39,7 @@ title: چین انٹیگریشن کے عمل کا جائزہ
 
 یہ صرف سب سٹریمزسے چلنے والے سب گرافس پر انڈیکسنگ کے انعامات کے لیے پروٹوکول سپورٹ کو متاثر کرے گا۔ اس GIP میں اسٹیج 2 کے لیے بیان کردہ طریقہ کار کے بعد، نئے فائر ہوز کے نفاذ کو ٹیسٹ نیٹ پر جانچ کی ضرورت ہوگی۔ اسی طرح، یہ فرض کرتے ہوئے کہ نفاذ پرفارمنس اور قابل اعتماد ہے، [فیچر سپورٹ میٹرکس](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) پر ایک PR کی ضرورت ہوگی ( 'سب سٹریمز ڈیٹا سورسز' سب گراف فیچر)، نیز انڈیکسنگ انعامات کے لیے پروٹوکول سپورٹ کے لیے ایک نیا GIP۔ کوئی بھی PR اور GIP بنا سکتا ہے۔ فاؤنڈیشن کونسل کی منظوری میں مدد کرے گی.
 
-### 3. اس عمل میں کتنا وقت لگے گا؟
+### 3. How much time will the process of reaching full protocol support take?
 
 مین نیٹ کرنے کا وقت کئی ہفتوں کا متوقع ہے، انٹیگریشن کی ترقی کے وقت کی بنیاد پر مختلف ہوتا ہے، چاہے اضافی تحقیق کی ضرورت ہو، جانچ اور بگ فکسز، اور ہمیشہ کی طرح، گورننس کے عمل کا وقت جس کے لیے کمیونٹی فیڈ بیک کی ضرورت ہوتی ہے.
 
@@ -46,4 +47,4 @@ title: چین انٹیگریشن کے عمل کا جائزہ
 
 ### 4. ترجیحات کو کس طرح سنبھالا جائے گا؟
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 9fd0feefcf22cf709278e283d344c129a46ba00f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:04 -0500
Subject: [PATCH 1124/1325] New translations chain-integration-overview.mdx
 (Vietnamese)

---
 website/pages/vi/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/vi/chain-integration-overview.mdx b/website/pages/vi/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/vi/chain-integration-overview.mdx
+++ b/website/pages/vi/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 8ed68233b658ebe02aa5e933395d2e4490942795 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:05 -0500
Subject: [PATCH 1125/1325] New translations chain-integration-overview.mdx
 (Marathi)

---
 website/pages/mr/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/mr/chain-integration-overview.mdx b/website/pages/mr/chain-integration-overview.mdx
index 2fe6c2580909..a142f3f817f9 100644
--- a/website/pages/mr/chain-integration-overview.mdx
+++ b/website/pages/mr/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. How much time will the process of reaching full protocol support take?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From ceb35cc95c554c426fac160e0c266489df1e1697 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:06 -0500
Subject: [PATCH 1126/1325] New translations chain-integration-overview.mdx
 (Hindi)

---
 website/pages/hi/chain-integration-overview.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/hi/chain-integration-overview.mdx b/website/pages/hi/chain-integration-overview.mdx
index 2fe6c2580909..575d0b186105 100644
--- a/website/pages/hi/chain-integration-overview.mdx
+++ b/website/pages/hi/chain-integration-overview.mdx
@@ -6,12 +6,12 @@ A transparent and governance-based integration process was designed for blockcha
 
 ## Stage 1. Technical Integration
 
-- Teams work on a Graph Node integration and Firehose for non-EVM based chains. [Here's how](/new-chain-integration/).
+- कृपया [New Chain Integration](/new-chain-integration) पर जाएं नई chains के लिए `graph-node` समर्थन के बारे में जानकारी के लिए.
 - Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
 
 ## Stage 2. Integration Validation
 
-- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON RPC or Firehose endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- टीमें ग्राफ फाउंडेशन और ग्राफिकल यूजर इंटरफेस (GUIs) और नेटवर्क गेटवे के संचालकों के साथ सहयोग करती हैं, जैसे कि [Subgraph Studio](https://thegraph.com/studio/)। इसमें आवश्यक बैकएंड इंफ्रास्ट्रक्चर प्रदान करने शामिल है, जैसे कि एकीकृत चेन के JSON RPC या Firehose एंडपॉइंट्स। ऐसे टीमें जो ऐसी इंफ्रास्ट्रक्चर का स्वयं होस्टिंग नहीं करना चाहती हैं, वे ग्राफ की नोड ऑपरेटर (Indexer) की समुदाय का उपयोग कर सकती हैं, जिसमें फाउंडेशन मदद कर सकता है।
 - Graph Indexers test the integration on The Graph's testnet.
 - Core developers and Indexers monitor stability, performance, and data determinism.
 
@@ -38,7 +38,7 @@ This process is related to the Subgraph Data Service, applicable only to new Sub
 
 This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
 
-### 3. How much time will this process take?
+### 3. पूर्ण प्रोटोकॉल समर्थन तक पहुंचने की प्रक्रिया में कितना समय लगेगा?
 
 The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
 
@@ -46,4 +46,4 @@ Protocol support for indexing rewards depends on the stakeholders' bandwidth to
 
 ### 4. How will priorities be handled?
 
-Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process. This is especially true for chains previously supported on the [hosted service](https://thegraph.com/hosted-service) or those relying on already tested stacks.
+\#3 के समान, यह समग्र तत्परता और शामिल हितधारकों की क्षमता पर निर्भर करेगा। उदाहरण के लिए, एक नए चेन के साथ एक नई Firehose कार्यान्वयन को उन एकीकरणों की तुलना में अधिक समय लग सकता है जो पहले से ही परीक्षण किए जा चुके हैं या जो शासन प्रक्रिया में आगे बढ़ चुके हैं।

From 4457cdb315fbdc7d73c2d08fd2a1580e60a8b81b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:07 -0500
Subject: [PATCH 1127/1325] New translations chain-integration-overview.mdx
 (Swahili)

---
 .../pages/sw/chain-integration-overview.mdx   | 49 +++++++++++++++++++
 1 file changed, 49 insertions(+)
 create mode 100644 website/pages/sw/chain-integration-overview.mdx

diff --git a/website/pages/sw/chain-integration-overview.mdx b/website/pages/sw/chain-integration-overview.mdx
new file mode 100644
index 000000000000..a142f3f817f9
--- /dev/null
+++ b/website/pages/sw/chain-integration-overview.mdx
@@ -0,0 +1,49 @@
+---
+title: Chain Integration Process Overview
+---
+
+A transparent and governance-based integration process was designed for blockchain teams seeking [integration with The Graph protocol](https://forum.thegraph.com/t/gip-0057-chain-integration-process/4468). It is a 3-phase process, as summarised below.
+
+## Stage 1. Technical Integration
+
+- Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
+- Teams initiate the protocol integration process by creating a Forum thread [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71) (New Data Sources sub-category under Governance & GIPs). Using the default Forum template is mandatory.
+
+## Stage 2. Integration Validation
+
+- Teams collaborate with core developers, Graph Foundation and operators of GUIs and network gateways, such as [Subgraph Studio](https://thegraph.com/studio/), to ensure a smooth integration process. This involves providing the necessary backend infrastructure, such as the integrating chain's JSON-RPC, Firehose or Substreams endpoints. Teams wanting to avoid self-hosting such infrastructure can leverage The Graph's community of node operators (Indexers) to do so, which the Foundation can help with.
+- Graph Indexers test the integration on The Graph's testnet.
+- Core developers and Indexers monitor stability, performance, and data determinism.
+
+## Stage 3. Mainnet Integration
+
+- Teams propose mainnet integration by submitting a Graph Improvement Proposal (GIP) and initiating a pull request (PR) on the [feature support matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) (more details on the link).
+- The Graph Council reviews the request and approves mainnet support, providing a successful Stage 2 and positive community feedback.
+
+---
+
+If the process looks daunting, don't worry! The Graph Foundation is committed to supporting integrators by fostering collaboration, offering essential information, and guiding them through various stages, including navigating governance processes such as Graph Improvement Proposals (GIPs) and pull requests. If you have questions, please reach out to [info@thegraph.foundation](mailto:info@thegraph.foundation) or through Discord (either Pedro, The Graph Foundation member, IndexerDAO, or other core developers).
+
+Ready to shape the future of The Graph Network? [Start your proposal](https://github.com/graphprotocol/graph-improvement-proposals/blob/main/gips/0057-chain-integration-process.md) now and be a part of the web3 revolution!
+
+---
+
+## Frequently Asked Questions
+
+### 1. How does this relate to the [World of Data Services GIP](https://forum.thegraph.com/t/gip-0042-a-world-of-data-services/3761)?
+
+This process is related to the Subgraph Data Service, applicable only to new Subgraph `Data Sources`.
+
+### 2. What happens if Firehose & Substreams support comes after the network is supported on mainnet?
+
+This would only impact protocol support for indexing rewards on Substreams-powered subgraphs. The new Firehose implementation would need testing on testnet, following the methodology outlined for Stage 2 in this GIP. Similarly, assuming the implementation is performant and reliable, a PR on the [Feature Support Matrix](https://github.com/graphprotocol/indexer/blob/main/docs/feature-support-matrix.md) would be required (`Substreams data sources` Subgraph Feature), as well as a new GIP for protocol support for indexing rewards. Anyone can create the PR and GIP; the Foundation would help with Council approval.
+
+### 3. How much time will the process of reaching full protocol support take?
+
+The time to mainnet is expected to be several weeks, varying based on the time of integration development, whether additional research is required, testing and bug fixes, and, as always, the timing of the governance process that requires community feedback.
+
+Protocol support for indexing rewards depends on the stakeholders' bandwidth to proceed with testing, feedback gathering, and handling contributions to the core codebase, if applicable. This is directly tied to the integration's maturity and how responsive the integration team is (who may or may not be the team behind the RPC/Firehose implementation). The Foundation is here to help support throughout the whole process.
+
+### 4. How will priorities be handled?
+
+Similar to #3, it will depend on overall readiness and involved stakeholders' bandwidth. For example, a new chain with a brand new Firehose implementation may take longer than integrations that have already been battle-tested or are farther along in the governance process.

From 1ddc88877e793a74d17de0f9b196d9277bf5065e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:08 -0500
Subject: [PATCH 1128/1325] New translations sunrise.mdx (Romanian)

---
 website/pages/ro/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/ro/sunrise.mdx b/website/pages/ro/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/ro/sunrise.mdx
+++ b/website/pages/ro/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 61b59898491825021591e32fbb7abfec80ac5b6f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:09 -0500
Subject: [PATCH 1129/1325] New translations sunrise.mdx (French)

---
 website/pages/fr/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/fr/sunrise.mdx b/website/pages/fr/sunrise.mdx
index 92fd7447ac3f..20f23e1a01f1 100644
--- a/website/pages/fr/sunrise.mdx
+++ b/website/pages/fr/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## Quel est l'essor des données décentralisées ?
+## What was the Sunrise of Decentralized Data?
 
-Le lever du soleil sur les données décentralisées est une initiative lancée par Edge & Node. L'objectif est de permettre aux développeurs de subgraphs de passer en toute transparence au réseau décentralisé de The Graph.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-Ce plan s'appuie sur de nombreux développements antérieurs de l'écosystème The Graph, y compris un indexeur de mise à niveau pour servir des requêtes sur les subgraphs nouvellement publiés, et la capacité d'intégrer de nouveaux réseaux de blockchain à The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Mise à jour des subgraphs dans le réseau The Graph
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### Quand les subgraphs du service hébergé ne seront-ils plus disponibles ?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Mon subgraph de service hébergé sera-t-il pris en charge sur le réseau The Graph ?
-
-Oui, l'indexeur de mise à niveau prendra automatiquement en charge tous les subgraphs de services hébergés publiés sur le réseau The Graph pour une expérience de mise à niveau transparente.
-
-### Comment mettre à jour mon subgraph de services hébergés ?
-
-> Note : La mise à niveau d'un subgraph vers le réseau The Graph ne peut pas être annulée.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Sélectionnez le(s) subgraph(s) que vous souhaitez mettre à niveau.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Cliquez sur le bouton "Mise à niveau".
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### Comment puis-je obtenir de l'aide pour le processus de mise à niveau ?
-
-La communauté Graph est là pour aider les développeurs à passer au réseau Graph. Rejoignez le [serveur Discord] de The Graph (https://discord.gg/vtvv7FP) et demandez de l'aide dans le #canal mise à niveau-du réseau-décentralisé.
-
-### Comment puis-je garantir une haute qualité de service et une redondance pour les subgraphs sur le réseau The Graph ?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Les membres de ces communautés blockchain sont encouragés à intégrer leur chaîne via le [Processus d'intégration de la chaîne](/chain-integration-overview/).
-
-### Comment publier les nouvelles versions sur le réseau ?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Mettez à niveau vers la dernière version de [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Mettez à jour votre commande de déploiement
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> La publication nécessite Arbitrum ETH - la mise à niveau de votre subgraph permet également de déposer une petite quantité pour faciliter vos premières interactions avec le protocole 🧑‍🚀
-
-### J'utilise un subgraph développé par quelqu'un d'autre, comment puis-je m'assurer que mon service n'est pas interrompu ?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### Que se passe-t-il si je ne mets pas à jour mon subgraph ?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### Comment puis-je commencer à interroger des subgraphs sur The Graph Network ?
-
-Vous pouvez explorer les subgraphs disponibles sur [Graph Explorer](https://thegraph.com/explorer). [En savoir plus sur l'interrogation des subgraphs sur The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## À propos de l'indexeur de mise à niveau
 
-### Qu'est-ce que l'indexeur de mise à niveau ?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### Quelles chaînes l’indexeur de mise à niveau prend-il en charge ?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-L'indexeur de mise à niveau prend en charge les chaînes qui n'étaient auparavant disponibles que sur le service hébergé.
+### What does the upgrade Indexer do?
 
-Vous trouverez une liste complète des chaînes soutenues [ici] (/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Pourquoi Edge & Node exécutent-ils l'indexeur de mise à niveau ?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### Que signifie la mise à niveau de l'indexeur pour les indexeurs existants ?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-L'indexeur de mise à niveau fournit également à la communauté des indexeurs des informations sur la demande potentielle de subgraphs et de nouvelles chaînes sur le réseau de graphs.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-L'indexeur de mise à niveau offre une opportunité puissante pour les délégués. Au fur et à mesure que de nouveaux subgraphs sont transférés du service hébergé vers le réseau The Graph, les délégués devraient bénéficier de l'activité accrue du réseau.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### L'indexeur mis à niveau sera-t-il en concurrence avec les indexeurs existants pour l'obtention de récompenses ?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-Non, l'indexeur de mise à niveau allouera uniquement le montant minimum par subgraph et ne collectera pas de récompenses d'indexation.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### Comment cela affectera-t-il les développeurs de subgraphs ?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 L'indexeur de mise à niveau active les chaînes sur le réseau qui n'étaient auparavant prises en charge que sur le service hébergé. Par conséquent, il élargit la portée et la disponibilité des données pouvant être interrogées sur le réseau.
 
-### Quel sera le prix des requêtes de l'indexeur de mise à niveau ?
-
-L'indexeur de mise à niveau fixera le prix des requêtes au taux du marché afin de ne pas influencer le marché des frais de requête.
-
-### Quels sont les critères pour que l'indexeur de mise à niveau cesse de prendre en charge un subgraph ?
-
-L'indexeur de mise à niveau servira un subgraph jusqu'à ce qu'il soit suffisamment et correctement servi avec des requêtes cohérentes servies par au moins 3 autres indexeurs.
-
-En outre, l'indexeur de mise à niveau cessera de prendre en charge un subgraph s'il n'a pas été intégré au cours des 30 derniers jours.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## À propos du réseau Graph
-
-### Dois-je gérer ma propre infrastructure ?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Une fois que votre subgraph a atteint un signal de curation adéquat et que d'autres indexeurs commencent à le soutenir, l'indexeur de mise à niveau se retire progressivement, ce qui permet aux autres indexeurs de percevoir des récompenses d'indexation et des frais d'interrogation.
-
-### Dois-je héberger ma propre infrastructure d'indexation ?
-
-L'exploitation d'une infrastructure pour votre propre projet est [nettement plus gourmande en ressources] (/network/benefits/) par rapport à l'utilisation du réseau Graph.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-Cela dit, si vous êtes toujours intéressé par l'exploitation d'un [nœud de graphe] (https://github.com/graphprotocol/graph-node), envisagez de rejoindre The Graph Network [en tant qu'indexeur] (https://thegraph.com/blog/how-to-become-indexer/) pour gagner des récompenses d'indexation et des frais de requête en servant des données sur votre subgraph et d'autres.
-
-### Dois-je utiliser un fournisseur d’indexation centralisé ?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Voici une description détaillée des avantages de The Graph par rapport à l'hébergement centralisé :
+### How does the upgrade Indexer price queries?
 
-- **Résilience et redondance** : Les systèmes décentralisés sont intrinsèquement plus robustes et résilients en raison de leur nature distribuée. Les données ne sont pas stockées sur un seul serveur ou emplacement. Au lieu de cela, elles sont servies par des centaines d'indexeurs indépendants répartis dans le monde entier. Cela réduit le risque de perte de données ou d'interruption de service en cas de défaillance d'un nœud, ce qui se traduit par un temps de disponibilité exceptionnel (99,99 %).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Qualité de service** : En plus d'un temps de disponibilité impressionnant, The Graph Network se caractérise par une vitesse médiane d'interrogation (latence) d'environ 106 ms et par des taux de réussite des requêtes plus élevés que ceux des autres solutions hébergées. Pour en savoir plus, consultez [ce blog] (https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Tout comme vous avez choisi votre réseau blockchain pour sa nature décentralisée, sa sécurité et sa transparence, opter pour The Graph Network est une extension de ces mêmes principes. En alignant votre infrastructure de données sur ces valeurs, vous garantissez un environnement de développement cohésif, résilient et axé sur la confiance.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 05001a60f89afdb3f9a19204d74ac75b5bbd1c56 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:10 -0500
Subject: [PATCH 1130/1325] New translations sunrise.mdx (Spanish)

---
 website/pages/es/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/es/sunrise.mdx b/website/pages/es/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/es/sunrise.mdx
+++ b/website/pages/es/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From ac27fc03e48b485b99c783116a365186b696d2c4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:11 -0500
Subject: [PATCH 1131/1325] New translations sunrise.mdx (Arabic)

---
 website/pages/ar/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/ar/sunrise.mdx b/website/pages/ar/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/ar/sunrise.mdx
+++ b/website/pages/ar/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 349f92fa4f09a047071af0c0f020f536dce4201d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:12 -0500
Subject: [PATCH 1132/1325] New translations sunrise.mdx (Czech)

---
 website/pages/cs/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/cs/sunrise.mdx b/website/pages/cs/sunrise.mdx
index 157bab9d09e9..75076fb51020 100644
--- a/website/pages/cs/sunrise.mdx
+++ b/website/pages/cs/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Časté dotazy po východu slunce + aktualizace na síť Graf
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Poznámka: Východ slunce decentralizovaných dat skončil 12. června 2024.
 
-## Jaký je východ slunce decentralizovaných dat?
+## Jaký byl úsvit decentralizovaných dat?
 
-Východ slunce decentralizovaných dat je iniciativa, za kterou stojí společnost Edge & Node. Jejím cílem je umožnit vývojářům podgrafů bezproblémový přechod na decentralizovanou síť Graf.
+Úsvit decentralizovaných dat byla iniciativa, kterou vedla společnost Edge & Node. Tato iniciativa umožnila vývojářům podgrafů bezproblémově přejít na decentralizovanou síť Graf.
 
-Tento plán vychází z mnoha předchozích změn v ekosystému Graf, včetně vylepšeného indexeru pro obsluhu dotazů na nově publikované podgrafy a možnosti integrovat do Graf nové blockchainové sítě.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### Jaké jsou fáze východu Slunce?
+### Co se stalo s hostovanou službou?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+Koncové body dotazů hostované služby již nejsou k dispozici a vývojáři nemohou v hostované službě nasadit nové podgrafy.
 
-## Aktualizace podgrafů do sítě grafů
+Během procesu aktualizace mohli vlastníci podgrafů hostovaných služeb aktualizovat své podgrafy na síť Graf. Vývojáři navíc mohli nárokovat automatickou aktualizaci podgrafů.
 
-### Kdy přestanou být podgrafy hostovaných služeb k dispozici?
+### Měla tato aktualizace vliv na Podgraf Studio?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+Ne, na Podgraf Studio neměl Sunrise vliv. Podgrafy byly okamžitě k dispozici pro dotazování, a to díky aktualizačnímu indexeru, který využívá stejnou infrastrukturu jako hostovaná služba.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Proč byly podgrafy zveřejněny na Arbitrum, začalo indexovat jinou síť?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Bude můj podgraf hostované služby podporován v síti Graf?
-
-Ano, nástroj Indexer pro upgrade bude automaticky podporovat všechny podgrafy hostovaných služeb publikované v síti Graf pro bezproblémový upgrade.
-
-### Jak mohu aktualizovat podgraf hostované služby?
-
-> Poznámka: Upgrade podgrafu na síť grafů nelze vrátit zpět.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-Chcete-li aktualizovat podgraf hostované služby, můžete navštívit ovládací panel podgrafu na adrese [hostovaná služba](https://thegraph.com/hosted-service).
-
-1. Vyberte podgraf nebo podgrafy, které chcete aktualizovat.
-2. Vyberte přijímající peněženku (peněženku, která se stane vlastníkem podgrafu).
-3. Klikněte na tlačítko "Upgrade".
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### Jak mohu získat podporu pro proces aktualizace?
-
-Komunita Graf je zde, aby podporovala vývojáře při přechodu na síť Graf. Připojte se k [serveru Discord](https://discord.gg/vtvv7FP) společnosti The Graph a požádejte o pomoc v kanálu #upgrade-decentralized-network.
-
-### Jak lze zajistit vysokou kvalitu služeb a redundanci podgrafů v síti Graf?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Členové těchto blockchainových komunit jsou vyzýváni k integraci svého řetězce prostřednictvím [procesu integrace řetězce](/chain-integration-overview/).
-
-### Jak mohu publikovat nové verze do sítě?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade na nejnovější verzi [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Aktualizace příkazu deploy
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publikování vyžaduje Arbitrum ETH - při upgradu vašeho subgrafu se také uvolní malá částka, která vám usnadní první interakce s protokolem 🧑‍🚀
-
-### Používám podgraf vytvořený někým jiným, jak mohu zajistit, aby nedošlo k přerušení mé služby?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### Co se stane, když svůj podgraf neaktualizuji?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### Jak se mohu začít dotazovat na podgrafy v síti grafů?
-
-Dostupné podgrafy můžete prozkoumat na stránce [Graph Explorer](https://thegraph.com/explorer). [Více informací o dotazování na podgrafy na Graf](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## O Upgrade Indexer
 
-### Co je to upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> Aktualizace Indexer je v současné době aktivní.
 
-### Jaké řetězce podporuje upgrade Indexer?
+Upgrade Indexer byl implementován za účelem zlepšení zkušeností s upgradem podgrafů z hostované služby do sit' Graf a podpory nových verzí stávajících podgrafů, které dosud nebyly indexovány.
 
-Upgrade Indexeru podporuje řetězce, které byly dříve dostupné pouze v hostované službě.
+### Co dělá upgrade Indexer?
 
-Úplný seznam podporovaných řetěz najdete [zde](/developing/supported-networks/).
+- Zavádí řetězce, které ještě nezískaly odměnu za indexaci v síti Graf, a zajišťuje, aby byl po zveřejnění podgrafu co nejrychleji k dispozici indexátor pro obsluhu dotazů.
+- Podporuje řetězce, které byly dříve dostupné pouze v hostované službě. Úplný seznam podporovaných řetězců najdete [zde](/developing/supported-networks/).
+- Indexátoři, kteří provozují upgrade indexátoru, tak činí jako veřejnou službu pro podporu nových podgrafů a dalších řetězců, kterým chybí indexační odměny, než je Rada grafů schválí.
 
 ### Proč Edge & Node spouští aktualizaci Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historicky udržovaly hostovanou službu, a proto již mají synchronizovaná data pro podgrafy hostované služby.
 
 ### Co znamená upgrade indexeru pro stávající indexery?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Řetězce, které byly dříve podporovány pouze v hostované službě, byly vývojářům zpřístupněny v síti Graf nejprve bez odměn za indexování.
+
+Tato akce však uvolnila poplatky za dotazy pro všechny zájemce o indexování a zvýšila počet podgrafů zveřejněných v síti Graf. V důsledku toho mají indexátoři více příležitostí indexovat a obsluhovat tyto podgrafy výměnou za poplatky za dotazy, a to ještě předtím, než jsou odměny za indexování pro řetězec povoleny.
 
-Upgrade Indexer také poskytuje komunitě Indexer informace o potenciální poptávce po podgraf nových řetězcích v síti grafů.
+Upgrade Indexer také poskytuje komunitě Indexer informace o potenciální poptávce po podgrafech a nových řetězcích v síti grafů.
 
 ### Co to znamená pro delegáti?
 
-Upgrade Indexer nabízí delegátům velkou příležitost. Jakmile bude více podgrafů upgradováno z hostované služby do sítě Graf, budou mít delegáti prospěch ze zvýšené aktivity v síti.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Bude upgrade Indexeru soutěžit o odměny se stávajícími Indexery?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-Ne, indexátor aktualizace přidělí pouze minimální částku na podgraf a nebude vybírat odměny za indexování.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### Jak to ovlivní vývojáře podgrafů?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### Jaký to má přínos pro spotřebitele dat?
+### How does the upgrade Indexer benefit data consumers?
 
 Aktualizace Indexeru umožňuje podporu blockchainů v síti, které byly dříve dostupné pouze v rámci hostované služby. Tímto se rozšiřuje rozsah a dostupnost dat, která lze v síti dotazovat.
 
-### Jak bude aktualizace Indexer oceňovat dotazy?
-
-Upgrade Indexer stanoví cenu dotazů podle tržní sazby, aby neovlivňoval trh s poplatky za dotazy.
-
-### Jaká jsou kritéria pro to, aby nástroj Indexer přestal podporovat podgraf?
-
-Aktualizační indexátor bude obsluhovat podgraf, dokud nebude dostatečně a úspěšně obsloužen konzistentními dotazy obsluhovanými alespoň třemi dalšími indexátory.
-
-Kromě toho indexátor aktualizace přestane podgraf podporovat, pokud se na něj v posledních 30 dnech nikdo nezeptal.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## O síti grafů
-
-### Musím provozovat vlastní infrastrukturu?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Jakmile váš podgraf dosáhne dostatečného kurátorského signálu a ostatní indexátory jej začnou podporovat, upgrade indexátoru se postupně sníží a umožní ostatním indexátorům vybírat odměny za indexování a poplatky za dotazy.
-
-### Měl bych hostovat vlastní indexovací infrastrukturu?
-
-Provozování infrastruktury pro vlastní projekt je [výrazně náročnější na zdroje](/network/benefits/) ve srovnání s používáním sit' Graf.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-Pokud přesto máte zájem o provozování [Graph Node](https://github.com/graphprotocol/graph-node), zvažte možnost připojit se k síti The Graph Network [jako indexátor](https://thegraph.com/blog/how-to-become-indexer/) a získávat odměny za indexování a poplatky za dotazy tím, že budete poskytovat data na svém podgrafu a dalších.
-
-### Měl bych používat centralizovaného poskytovatele indexování?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Zde je podrobný přehled výhod Graf oproti centralizovanému hosting:
+### How does the upgrade Indexer price queries?
 
-- **Odolnost a redundance**: Decentralizované systémy jsou díky své distribuované povaze ze své podstaty robustnější a odolnější. Data nejsou uložena na jediném serveru nebo místě. Místo toho je obsluhují stovky nezávislých indexérů po celém světě. Tím se snižuje riziko ztráty dat nebo přerušení služby v případě selhání jednoho uzlu, což vede k výjimečné provozuschopnosti (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Kvalita služeb**: Kromě působivé doby provozu se Sit' Graf vyznačuje průměrnou rychlostí dotazů (latence) ~106 ms a vyšší úspěšností dotazů ve srovnání s hostovanými alternativami. Více informací naleznete v [tomto blogu](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Stejně jako jste si vybrali blockchainovou síť kvůli její decentralizované povaze, bezpečnosti a transparentnosti, je volba sit' Graf rozšířením stejných principů. Sladěním své datové infrastruktury s těmito hodnotami zajistíte soudržné, odolné a důvěryhodné vývojové prostředí.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 2bdbe7f8f1de91159a807fcc8291008d3b38a4c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:13 -0500
Subject: [PATCH 1133/1325] New translations sunrise.mdx (German)

---
 website/pages/de/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/de/sunrise.mdx b/website/pages/de/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/de/sunrise.mdx
+++ b/website/pages/de/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 7fb7490d798f36185b02743a87908c147de83ce8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:14 -0500
Subject: [PATCH 1134/1325] New translations sunrise.mdx (Italian)

---
 website/pages/it/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/it/sunrise.mdx b/website/pages/it/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/it/sunrise.mdx
+++ b/website/pages/it/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 750b2965434f285f82cd22d667bba3ebb176e650 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:15 -0500
Subject: [PATCH 1135/1325] New translations sunrise.mdx (Japanese)

---
 website/pages/ja/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/ja/sunrise.mdx b/website/pages/ja/sunrise.mdx
index cbc91c2445a7..5955cec07911 100644
--- a/website/pages/ja/sunrise.mdx
+++ b/website/pages/ja/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-この計画は、新しく公開されたサブグラフに対するクエリを提供するためのアップグレードされたIndexerや、新しいブロックチェーンネットワークをThe Graphに統合する機能など、The Graphエコシステムのこれまでの多くの開発を利用しています。
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## The Graph Networkへのサブグラフのアップグレード
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-サポートされているチェーンの包括的なリストは[こちら](/developing/supported-networks/)。
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### なぜEdge & Nodeはアップグレード・インデクサーを実行しているのか？
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-アップグレード・インデクサーはまた、グラフ・ネットワーク上のサブグラフや新しいチェーンの潜在的な需要に関する情報を、インデクサー・コミュニティに提供します。
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### これはデリゲーターにとって何を意味するのか？
 
-アップグレード・インデクサーは、デリゲータに強力な機会を提供します。より多くのサブグラフがホスティングされたサービスからグラフネットワークにアップグレードされると、デリゲータはネットワーク活動の増加から利益を得ることができます。
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### アップグレード・インデクサーは、既存のインデクサーと報酬を奪い合うのでしょうか？
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-いいえ、アップグレード・インデクサーは、サブグラフごとに最小量しか割り当てず、インデックス作成報酬は受け取りません。
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### これはサブグラフ開発者にどのような影響を与えるのでしょうか？
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### これはデータ消費者にとってどのようなメリットがあるのでしょうか？
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### アップグレード・インデクサーは、クエリにどのような価格をつけるのでしょうか？
-
-アップグレード・インデクサーは、クエリ料金市場に影響を与えないよう、クエリ料金を市場価格で設定すします。
-
-### アップグレード・インデクサーがサブグラフのサポートを停止する基準は何ですか？
-
-アップグレード・インデクサーは、少なくとも3つの他のインデクサーによって提供された一貫性のあるクエリで、サブグラフが十分かつ正常に提供されるまで、サブグラフを提供します。
-
-さらに、アップグレード・インデクサーは、そのサブグラフが過去30日間にクエリされなかった場合、そのサブグラフのサポートを停止します。
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### インフラは自分で用意する必要がありますか？
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-サブグラフが十分なキュレーションシグナルに達し、他のIndexerがそれをサポートし始めると、アップグレード・インデクサーは徐々に先細りになり、他のインデクサーがインデックス作成報酬とクエリ手数料を徴収できるようになります。
-
-### 独自のインデックス作成インフラをホストすべきか？
-
-自身のプロジェクトのためにインフラストラクチャを実行することは、グラフネットワークを使用する場合と比較して、[著しくリソースを消費します](/network/benefits/)。
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-とはいえ、もしまだ[グラフ・ノード](https://github.com/graphprotocol/graph-node)を運営することに興味があるのであれば、グラフ・ネットワーク[インデクサーとして](https://thegraph.com/blog/how-to-become-indexer/)に参加し、自分のサブグラフや他のサブグラフのデータを提供することで、インデクシング報酬やクエリ報酬を得ることを検討しましょう。
-
-### 集中型インデクシング・プロバイダを使うべきでしょうか？
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-集中型ホスティングに対するThe Graphの利点について詳しく説明します：
+### How does the upgrade Indexer price queries?
 
-- **レジリエンスと冗長性**： 分散型システムは、その分散された性質により、本質的により堅牢で回復力があります。データは単一のサーバーや場所に保存されるわけではありません。その代わり、世界中にある何百もの独立したIndexerがデータを提供します。これにより、1つのノードに障害が発生した場合のデータ損失やサービス中断のリスクを低減し、卓越したアップタイム（99.99%）を実現します。
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **サービスの質**： 印象的なアップタイムに加え、The Graph Networkはクエリ速度（レイテンシー）の中央値が106msであり、他のホスティングサービスと比較して高いクエリー成功率を誇ります。詳しくは[このブログ](https://thegraph.com/blog/qos-the-graph-network/)をご覧ください。
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-非中央集権的な性質、セキュリティ、透明性のためにブロックチェーン・ネットワークを選択したように、The Graph Networkを選択することも同じ原則の延長線上にあります。データインフラストラクチャをこれらの価値観に合わせることで、結束力があり、弾力性があり、信頼に基づいた開発環境を確保することができます。
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From d2d22a80841f648ed91bd67fcc8d30c2169790dc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:16 -0500
Subject: [PATCH 1136/1325] New translations sunrise.mdx (Korean)

---
 website/pages/ko/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/ko/sunrise.mdx b/website/pages/ko/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/ko/sunrise.mdx
+++ b/website/pages/ko/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From c0165ec48f470f68e12b74bb28b64ec4c3559c22 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:17 -0500
Subject: [PATCH 1137/1325] New translations sunrise.mdx (Dutch)

---
 website/pages/nl/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/nl/sunrise.mdx b/website/pages/nl/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/nl/sunrise.mdx
+++ b/website/pages/nl/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 0865e595bd2efdf98e47881e508ee5c3d964eb1b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:18 -0500
Subject: [PATCH 1138/1325] New translations sunrise.mdx (Polish)

---
 website/pages/pl/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/pl/sunrise.mdx b/website/pages/pl/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/pl/sunrise.mdx
+++ b/website/pages/pl/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 820cc894d8a7f26204f1343e53ba94a60b14ccb5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:19 -0500
Subject: [PATCH 1139/1325] New translations sunrise.mdx (Portuguese)

---
 website/pages/pt/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/pt/sunrise.mdx b/website/pages/pt/sunrise.mdx
index 44cb3a669f14..7511fb469647 100644
--- a/website/pages/pt/sunrise.mdx
+++ b/website/pages/pt/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Perguntas Frequentes sobre o Nascer do Sol + Atualizações da Graph Network
+title: Perguntas Frequentes sobre o Pós-Nascer do Sol + Atualizações para a Graph Network
 ---
 
-> Nota: Este documento é atualizado constantemente para garantir o repasse das informações mais úteis e precisas. Se não encontrar a informação que procura, ou se precisar de ajuda imediata, [fale no Discord](https://discord.gg/graphprotocol). Se precisar de informações sobre cobranças, consulte a página sobre [cobranças](/billing/).
+> Nota: O Nascer do Sol dos Dados Descentralizados foi encerrado em 12 de junho de 2024.
 
-## O Que É o Nascer do Sol dos Dados Descentralizados?
+## O Que Foi o Nascer do Sol dos Dados Descentralizados?
 
-O Nascer do Sol dos Dados Descentralizados é uma iniciativa liderada pela Edge & Node. A meta é garantir que os programadores de subgraphs façam uma atualização suave para a rede descentralizada do The Graph.
+O Nascer do Sol dos Dados Descentralizados foi uma iniciativa liderada pela Edge & Node, com a meta de garantir que os programadores de subgraphs fizessem uma atualização suave para a rede descentralizada do The Graph.
 
-Este plano usa vários desenvolvimentos prévios do ecossistema do The Graph, inclusive um Indexador de atualização para servir queries em subgraphs recém-publicados, e a habilidade de integrar novas redes de blockchain ao The Graph.
+Este plano teve base em desenvolvimentos anteriores do ecossistema do The Graph, e incluiu um Indexador de atualização para servir queries em subgraphs recém-editados.
 
-### Quais as fases do Nascer do Sol?
+### O que aconteceu com o serviço hospedado?
 
-**Raio de Sol**: Ativa apoio a chains no serviço hospedado, introduz um fluxo de atualizações suaves, oferece um plano grátis na Graph Network e fornece opções simples de pagamento.\
-**Luz do Sol**: O período que programadores de subgraphs têm para atualizar os seus subgraphs do serviço hospedado à Graph Network. Esta janela será fechada às 10 da manhã, horário Pacífico, em 12 de junho de 2024.\
-**Nascer do Sol**: Endpoints do serviço hospedado não estarão mais disponíveis após as 10 da manhã, horário Pacífico, 12 de junho de 2024.
+Os endpoints de query do serviço hospedado não estão mais disponíveis, e programadores não podem mais editar subgraphs novos no serviço hospedado.
 
-## Como migrar subgraphs à Graph Network
+Durante o processo de atualização, donos de subgraphs no serviço hospedado puderam atualizar os seus subgraphs até a Graph Network. Além disto, programadores podiam resgatar subgraphs atualizados automaticamente.
 
-### Quando os subgraphs do serviço hospedado serão desativados?
+### O Subgraph Studio foi atingido por esta atualização?
 
-Os endpoints de query do serviço hospedado permanecerão ativos até as 10 da manhã, horário Pacífico, em 12 de junho de 2024. Após este horário, os endpoints de query serão desativados e programadores não poderão mais lançar versões novas de subgraphs no serviço hospedado.
+Não, o Subgraph Studio não foi impactado pelo Nascer do Sol. Os subgraphs estavam disponíveis imediatamente para queries, movidos pelo Indexador de atualização, que usa a mesma infraestrutura do serviço hospedado.
 
-### Eu não atualizei o meu subgraph antes de 12 de junho. O que devo fazer se ainda quiser utilizá-lo?
+### Por que subgraphs eram publicados ao Arbitrum, eles começaram a indexar uma rede diferente?
 
-A página inicial do serviço hospedado ainda está disponível e pode ser usada para buscar subgraphs antigos do serviço hospedado. Se o seu subgraph do serviço hospedado já foi atualizado automaticamente, é possível resgatar o seu equivalente da rede como o dono original. Se o seu subgraph não foi [atualizado automaticamente](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), ainda é possível atualizar e editá-lo.
-
-Atualizações levam, em média, menos de cinco minutos. Quando o seu subgraph estiver ao vivo, basta configurar uma chave API no Subgraph Studio, atualizar o seu endpoint de query na API e começar as queries!
-
-### O meu subgraph do serviço hospedado será apoiado na Graph Network?
-
-Sim, o Indexador de atualização terá suporte automático a todos os subgraphs do serviço hospedado editados à Graph Network para garantir uma experiência de atualização suave.
-
-### Como atualizo o meu subgraph do serviço hospedado?
-
-> Nota: A atualização de um subgraph à Graph Network não pode ser desfeita.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-Para atualizar um subgraph do serviço hospedado, é possível visitar o painel do subgraph no [serviço hospedado](https://thegraph.com/hosted-service).
-
-1. Selecione o(s) subgraph(s) que queres atualizar.
-2. Selecione a carteira destinatária (a carteira que tornará-se a dona do subgraph).
-3. Clique no botão "Upgrade".
-
-Com o subgraph editado, o [Indexador de atualização](#what-is-the-upgrade-indexer) começará a servir queries nele. Após gerar uma chave API, será possível começar a fazer queries imediatamente. [Aprenda mais](/cookbook/upgrading-a-subgraph/#what-next).
-
-### Como posso conseguir suporte no processo de atualização?
-
-A comunidade do The Graph está aqui para apoiar programadores enquanto eles migram à Graph Network. Entre no [Discord do The Graph](https://discord.gg/vtvv7FP) e peça ajuda no canal #upgrade-decentralized-network.
-
-### Como posso garantir redundância e uma qualidade alta de serviço para subgraphs na Graph Network?
-
-Todos os subgraphs serão apoiados pelo Indexador de atualização. Para aumentar a qualidade do serviço e a robustez da redundância, é possível adicionar um sinal de curadoria a subgraphs com direito a recompensas de indexação. Recomendamos curar o seu subgraph com, no mínimo, 3.000 GRT (por subgraph) para atrair cerca de 3 Indexadores. [Aprenda mais sobre adicionar sinais ao seu subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Por favor, note que este incentivo de indexação não se esvazia ao longo do tempo; ele não tem ritmo de esgotamento e pode ser sacado imediatamente a qualquer hora. Se quiser adicionar 3000 GRT em sinal, será necessário sinalizar 3.030 GRT (já que 1% seria queimado). Note que uma taxa de 0,5% também é deduzida do sinal do subgraph sempre que uma versão nova é editada.
-
-Subgraphs sem direito a recompensas de indexação podem sofrer ao tentar atrair mais Indexadores. Por exemplo, recompensas de indexação podem não ser disponibilizadas para subgraphs em chains específicas (confira o apoio [aqui](/developing/supported-networks)).
-
-Membros destas comunidades de blockchain são bem-vindos para integrar as suas chains via o [Processo de Integração de Chain](/chain-integration-overview/).
-
-### Como edito novas versões na rede?
-
-É possível lançar novas versões do seu subgraph diretamente ao Subgraph Studio, que providencia um ambiente de testes, antes de editar à rede para uso em produção. O Subgraph Studio tem um comando de lançamento diferente e requer um `version-label` para cada novo lançamento.
-
-1. Atualize à versão mais recente da [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Atualize o seu comando de lançamento
-
-```sh
-# Autorize com o Subgraph Studio, disponível na página do seu subgraph
-## Alternatival passe isto para o comando de lançamento como --access-token (veja abaixo)
-graph auth --studio <deploy-key>
-
-# Lance ao Subgraph Studio
-## Ao contrário do serviço hospedado, o nome consiste apenas do nome do subgraph (sem id do github)
-## Se usar o `--node` diretamente, é possível passá-lo no https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-Esta nova versão será então sincronizada no Subgraph Studio, um ambiente de testes. Quando estiver pronto para mover uma versão mais nova à produção, será possível [editar a versão do subgraph](/publishing/publishing-a-subgraph).
-
-> Editar exige ETH no Arbitrum - atualizar o seu subgraph também envia uma quantia pequena para facilitar as suas primeiras interações no protocolo 🧑‍🚀
-
-### Tenho um subgraph programado por outra pessoa. Como garantir que o meu serviço não será interrompido?
-
-Quando o dono atualizar o seu subgraph, será possível ir facilmente da página do subgraph no serviço hospedado ao subgraph correspondente na Graph Network, e atualizar o seu aplicativo a usar no URL de query do subgraph novo. [Saiba mais](/querying/querying-the-graph).
-
-No começo de junho, a Edge & Node atualizará automaticamente subgraphs com queries ativas. Isto dará a quaisquer consumidores de dados de terceiros uma oportunidade para migrar endpoints de subgraph à Graph Network antes das 10 da manhã, horário Pacífico, em 12 de junho. Os donos dos subgraphs ainda poderão resgatar estes subgraphs na rede com o fluxo de atualização do serviço hospedado.
-
-### O meu subgraph foi atualizado automaticamente, o que isto significa?
-
-Subgraphs no serviço hospedado são APIs abertas, e muitos subgraphs são dependentes de programadores de terceiros para construir os seus aplicativos. Para dar a estes programadores tempo suficiente para migrar à Graph Network, a Edge & Node atualizará automaticamente subgraphs com uso pesado. Um link ao subgraph atualizado automaticamente será visível na página do subgraph original no serviço hospedado.
-
-Donos de subgraphs atualizados automaticamente podem resgatar os seus subgraphs atualizados com o mesmo [fluxo de atualização](/cookbook/upgrading-a-subgraph) - tais subgraphs podem ser identificados pela sua marcação de "auto-upgraded" (atualizado automaticamente). A titularidade do subgraph na Graph Network será transferida à carteira do dono.
-
-### O meu subgraph foi atualizado automaticamente, mas preciso lançar uma versão nova
-
-É possível utilizar o [fluxo de atualização](/cookbook/upgrading-a-subgraph) para reivindicar o subgraph atualizao automaticamente, e depois será possível lançar uma versão nova no Subgraph Studio, com a mesma infraestrutura que move o serviço hospedado.
-
-Se precisar de uma solução urgente, favor contactar o suporte.
-
-### O que acontece se eu não atualizar o meu subgraph?
-
-Os Subgraphs receberão queries no serviço hospedado até as 10 da manhã, horário Pacífico, em 12 de junho. Após esta data, a página inicial do serviço hospedado continuará acessível, mas endpoints de queries serão desativados. Os donos de subgraphs no serviço hospedado ainda poderão atualizar os seus subgraphs à Graph Network após 12 de junho, mas atualizações anteriores serão elegíveis a [ganhar recompensas](https://thegraph.com/sunrise-upgrade-program/). Programadores também poderão reivindicar [subgraphs atualizados automaticamente](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### O que devo fazer com os meus subgraphs no serviço hospedado? Eles pararão de funcionar? Devo apagá-los?
-
-Não é possível apagar subgraphs. Os endpoints de queries permanecerão ativos até as 10 da manhã, horário Pacífico, em 12 de junho, independente de terem sido atualizados ou não.
-
-### O Subgraph Studio será atingido por esta atualização?
-
-Não, o Subgraph Studio não será impactado pelo Nascer do Sol.
-
-### O que acontecerá com o serviço hospedado?
-
-Após as 10 da manhã, horário Pacífico, 12 de junho, endpoints de queries serão desativados e titulares não poderão lançar no serviço hospedado ou consultá-lo. Porém, a interface do serviço hospedado continuará a mostrar páginas de subgraphs, e donos de subgraphs poderão atualizar os seus subgraphs caso já não tenham o feito. A interface do serviço hospedado será aposentada em uma data futura.
-
-### Subgraphs precisarão ser reindexados?
-
-Não, tenha tranquilidade em saber que o seu subgraph não precisará ser reindexado ao ser atualizado à Graph Network. Os subgraphs serão disponibilizados imediatamente para queries, movidos pelo Indexador de atualização, que usa a mesma infraestrutura que o serviço hospedado. Se o se subgraph indexar uma rede elegível a recompensas de indexação, será possível adicionar sinais a ele para atrair Indexadores. [Saiba mais sobre adicionar sinais ao seu subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### Estou com problemas ao indexar. O que devo fazer?
-
-Tenha tranquilidade em saber que Indexadores de rede estão preparados para prover apoio durante esta atualização. Se tiver problemas com qualquer das suas queries no seu subgraph, entre em contacto em support@thegraph.zendesk.com
-
-### Por que o meu subgraph é publicado ao Arbitrum, ele está a indexar uma rede diferente?
-
-A Graph Network foi lançada originalmente à mainnet do Ethereum, mas migrou ao Arbitrum One apra reduzir custos de gas para todos os utilizadores. Assim, todos os subgraphs novos são publicados à Graph Network para que possam ser apoiados por Indexadores. O Arbitrum é a rede em qual os subgraphs são publicados, mas subgraphs podem indexar quaisquer das [redes apoiadas](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### Como posso começar a consultar subgraphs na Graph Network?
-
-É possível explorar subgraphs disponíveis no [Graph Explorer](https://thegraph.com/explorer). [Aprenda mais sobre consultar subgraphs no The Graph](/querying/querying-the-graph).
+A Graph Network foi lançada inicialmente à mainnet do Ethereum, mas migrou ao Arbitrum One apra reduzir custos de gas para todos os utilizadores. Assim, todos os subgraphs novos são publicados à Graph Network no Arbitrum para que possam ser apoiados por Indexadores. O Arbitrum é a rede em qual os subgraphs são publicados, mas subgraphs podem indexar quaisquer das [redes apoiadas](/developing/supported-networks/)
 
 ## Sobre o Indexador de Atualização
 
-### O que é o Indexador de atualização?
-
-O Indexador de atualização é construído para melhorar a experiência de atualizar subgraphs do serviço hospedado à Graph Network e apoiar novas versões de subgraphs existentes que ainda não foram indexados.
-
-O Indexador de atualização mira inicializar chains que ainda não tenham recompensas de indexação na Graph Network, além de uma reserva para novas versões de subgraph. A meta é garantir que um Indexador esteja disponível para servir queries o mais rápido possível após a publicação de um subgraph.
+> O Indexador de Atualização está atualmente ativo.
 
-### Quais chains são apoiadas pelo Indexador de atualização?
+O Indexador de atualização foi construído para melhorar a experiência de atualizar subgraphs do serviço hospedado à Graph Network e apoiar novas versões de subgraphs existentes que ainda não foram indexados.
 
-O Indexador de atualização apoia chains que eram antes disponíveis apenas no serviço hospedado.
+### O que o Indexador de atualização faz?
 
-Encontre uma lista compreensiva de chains apoiadas [aqui](/developing/supported-networks/).
+- Ele inicializa chains que ainda não tenham recompensas de indexação na Graph Network, e garante que um Indexador esteja disponível para servir queries o mais rápido possível após a publicação de um subgraph.
+- Ele apoia chains que antigamente só estavam disponíveis no serviço hospedado. Veja uma lista compreensiva de chains apoiadas [aqui](/developing/supported-networks/).
+- Indexadores que operam um Indexador de atualização o fazem como um serviço público, para apoiar novos subgraphs e chains adicionais que não tenham recompensas de indexação antes da aprovação do Graph Council.
 
 ### Porque a Edge & Node executa o Indexador de atualização?
 
-A Edge & Node historicamente operou o serviço hospedado, e como resultado, já sincronizou os dados de subgraphs do serviço hospedado.
-
-Todos e quaisquer Indexadores são bem-vindos a tornar-se também Indexadores de atualização. Porém, a operação de um Indexador de atualização tende a ser fornecida como um serviço público para apoiar subgraphs novos e chains adicionais que não tem recompensas de indexação antes de serem aprovados pelo Graph Council.
+A Edge & Node operou historicamente o serviço hospedado, e como resultado, já sincronizou os dados de subgraphs do serviço hospedado.
 
 ### O que o Indexador de atualização significa para Indexadores existentes?
 
-Chains que antigamente tinham apoio apenas no serviço hospedado agora estarão disponíveis para programadores na Graph Network sem recompensas de indexação inicialmente, mas isto ativará taxas de query para qualquer Indexador interessado. Espera-se que isto cause um aumento no número de subgraphs editados na rede, o que proverá mais oportunidades para os Indexadores indexarem e servirem estes subgraphs em troca de taxas de query, antes mesmo da ativação de recompensas de indexação para uma chain.
+Chains que antes só eram apoiadas no serviço hospedado foram disponibilizadas para programadores na Graph Network, inicialmente, sem recompensas de indexação.
+
+Porém, esta ação liberou taxas de query para qualquer Indexador interessado e aumentou o número de subgraphs publicados na Graph Network. Como resultado, Indexadores têm mais oportunidades para indexar e servir estes subgraphs em troca de taxas de query, antes mesmo da ativação de recompensas de indexação para uma chain.
 
-O Indexador de atualização também fornece à comunidade de Indexadores informações sobre demanda em potencial para subgraphs e novas chains na Graph Network.
+O Indexador de atualização também fornece à comunidade de Indexadores informações sobre a demanda em potencial para subgraphs e novas chains na Graph Network.
 
 ### O que isto significa para Delegantes?
 
-O Indexador de atualização oferece uma forte oportunidade para Delegantes. À medida que mais subgraphs são atualizados do serviço hospedado até a Graph Network, os Delegantes podem se beneficiar do aumento na atividade da rede.
+O Indexador de atualização oferece uma forte oportunidade para Delegantes. Como ele permitiu que mais subgraphs fossem atualizados do serviço hospedado até a Graph Network, os Delegantes podem se beneficiar do aumento na atividade da rede.
 
-### O Indexador de atualização concorrerá com Indexadores existentes para recompensas?
+### O Indexador de atualização concorreu com Indexadores existentes para recompensas?
 
-Não, o Indexador de atualização só alocará a quantidade mínima por subgraph e não coletará recompensas de indexação.
+Não, o Indexador de atualização só aloca a quantidade mínima por subgraph e não coleta recompensas de indexação.
 
-Ele opera numa base de "necessidade" e serve como uma reserva até que uma cota de qualidade de serviço seja alcançada por, no mínimo, 3 outros Indexadores na rede para chains e subgraphs respetivos.
+Ele opera numa base de "necessidade" e serve como uma reserva até que uma cota de qualidade de serviço seja alcançada por, no mínimo, três outros Indexadores na rede para chains e subgraphs respetivos.
 
-### Como isto afetará os programadores de subgraph?
+### Como isto afeta os programadores de subgraph?
 
-Estes poderão enviar queries para os seus subgraphs na Graph Network logo após migrar do serviço hospedado ou publicá-los do Subgraph Studio, já que não será necessário tempo de espera para a indexação.
+Progmadores de subgraph poderão enviar queries para os seus subgraphs na Graph Network quase imediatamente após migrar do serviço hospedado ou [publicá-los do Subgraph Studio](/publishing/publishing-a-subgraph/), já que não será necessário tempo de espera para a indexação. Note que a [criação de subgraphs](/developing/creating-a-subgraph) não foi impactada por esta atualização.
 
-### Como isto beneficiará os consumidores de dados?
+### Como o Indexador de atualizações beneficia consumidores de dados?
 
 O Indexador de atualização ativa, na rede, chains que antes só tinham apoio no serviço hospedado. Assim, ele aumenta o alcance e a disponibilidade de dados que podem ser consultados na rede.
 
-### Como o Indexador de atualização precificará queries?
-
-O Indexador de atualização precificará queries no preço do mercado, para não influenciar o mercado de taxas de queries.
-
-### Quais são os critérios para que o Indexador de atualização pare de apoiar um subgraph?
-
-O Indexador de atualização servirá um subgraph até ele for servido suficientemente e com êxito, com queries consistentes servidos por, no mínimo, 3 outros Indexadores.
-
-Além disto, o Indexador de atualização parará de apoiar um subgraph se ele não tiver sido consultado nos últimos 30 dias.
-
-Outros Indexadores são incentivados a apoiar subgraphs com o volume de query atual. O volume de query ao Indexador de atualização tende a aproximar zero, já que ele terá um tamanho de alocação pequeno e outros Indexadores serão escolhidos por queries antes do Indexador de atualização.
-
-## Sobre a Graph Network
-
-### Eu tenho que executar a minha própria infraestrutura?
-
-Não. Toda a infraestrutura é operada por Indexadores independentes na Graph Network, o que inclui o Indexador de atualizações ([leia mais abaixo](#what-is-the-upgrade-indexer)).
-
-É possível usar o [Subgraph Studio](https://thegraph.com/studio/) para criar, testar e editar o seu subgraph. Todos os utilizadores do serviço hospedado devem migrar o seu subgraph à Graph Network antes das 10 da manhã, horário Pacífico, em 12 de junho de 2024.
-
-O [Indexador de Atualização do Nascer do Sol](/sunrise/#what-is-the-upgrade-indexer) garante a indexação de todos os subgraphs. No entanto, sinalizar GRT em um subgraph em particular atrairá mais Indexadores a ele. Este incentivo de Indexadores adicionais via curadoria visa melhorar a qualidade do serviço de queries ao reduzir a latência e melhorar a disponibilidade da rede.
-
-Ao sinalizar, os Curadores podem decidir entre sinalizar numa versão específica do subgraph ou sinalizar com a automigração. Caso sinalizem com a automigração, as ações de um curador sempre serão atualizadas à versão mais recente publicada pelo programador. Se decidirem sinalizar numa versão específica, as ações sempre permanecerão naquela versão específica.
-
-Para ajudar equipas que transitam subgraphs do serviço hospedado à Graph Network, abrimos o suporte para curadoria. Se precisar de ajuda com curadoria para melhorar a qualidade do serviço, contacte a equipa da Edge & Node em support@thegraph.zendesk.com e especifique os subgraphs com os quais precisa de ajuda.
-
-Quando o seu subgraph alcançar um sinal de curadoria adequado e outros Indexadores começarem a apoiá-lo, o Indexador de atualização se estabilizará gradualmente, de modo a permitir que outros Indexadores coletem recompensas de indexação e taxas de query.
-
-### Devo hospedar a minha própria infraestrutura de indexação?
-
-A execução de infraestrutura para o seu próprio projeto [requer muito mais recursos](/network/benefits/) em comparação ao uso da Graph Network.
-
-Além disto, a Graph Network é muito mais robusta, confiável, com um custo-benefício muito melhor comparado a qualquer coisa fornecida por uma única organização ou equipa. Centenas de Indexadores independentes ao redor do mundo operam a Graph Network para garantir segurança e redundância.
-
-Dito isto, se ainda tiver interesse em executar um [Graph Node](https://github.com/graphprotocol/graph-node), considere entrar na Graph Network [como Indexador](https://thegraph.com/blog/how-to-become-indexer/) para ganhar recompensas de indexação e taxas de query ao servir dados no seu subgraph e em outros.
-
-### Devo usar um provedor de indexação centralizado?
-
-Se construir na web3, a partir do momento que usa um provedor de indexação centralizado, você dá-os controle do seu dApp e dos seus dados. A rede descentralizada do The Graph oferece [uma qualidade melhor de serviço](https://thegraph.com/blog/qos-the-graph-network/), confiança com atividade imbatível graças à redundância de nodes, além de [custos muito menores](/network/benefits/); e você não será feito de refém na camada de dados.
-
-Com a Graph Network, o seu subgraph é público e qualquer pessoa pode enviar queries a ele abertamente, o que aumenta o uso e os efeitos na rede do seu dApp.
-
-Além disto, o Subgraph Studio fornece 100 mil queries mensais gratuitas no Plano Grátis antes da necessidade de pagar para mais uso.
-
-Aqui está um resumo detalhado dos benefícios do The Graph em comparação à hospedagem centralizada:
+### Como o Indexador de atualização precifica queries?
 
-- **Resiliência e Redundância**: Sistemas descentralizados, por natureza, são mais robustos e resilientes devido à sua natureza distribuída. Os dados não são guardados num único servidor ou local, mas sim, servidos por centenas de Indexadores independentes ao redor do mundo. Isto reduz o risco de perda de dados ou interrupções do serviço se um node falhar, o que leva a um tempo de atividade excepcional (99,99%).
+O Indexador de atualização precifica queries no preço do mercado, para não influenciar o mercado de taxas de queries.
 
-- **Qualidade de Serviço**: Além do tempo de atividade impressionante, a Graph Network tem uma velocidade de query mediana (latência) de cerca de 106ms, e índices maiores de sucesso de query em comparação a alternativas hospedadas. Leia mais [neste blog](https://thegraph.com/blog/qos-the-graph-network/).
+### Quando o Indexador de atualização parará de apoiar um subgraph?
 
-- **Resistência a Censura**: Sistemas centralizados são alvos fáceis para censura, seja por pressão regulatória ou ataques à rede. As arquiteturas dispersadas de sistemas descentralizados os faz muito mais difíceis de censurar, o que garante a disponibilidade contínua dos dados.
+O Indexador de atualização apoia um subgraph até que, no mínimo, 3 outros indexadores sirvam queries feitas nele com êxito e consistência.
 
-- **Transparência e Confiança**: Sistemas descentralizados operam de forma aberta, o que permite que qualquer pessoa verifique os dados de forma independente. Esta transparência constrói confiança entre participantes da rede, já que podem verificar a integridade do sistema sem depender de uma autoridade central.
+Além disto, o Indexador de atualização para de apoiar um subgraph se ele não tiver sido consultado nos últimos 30 dias.
 
-Assim como você escolheu a sua rede de blockchain pela natureza descentralizada, segurança e transparência, optar pela Graph Network é uma extensão destes mesmos princípios. Ao alinhar a sua infraestrutura de dados com estes valores, você garante um ambiente de programação coeso, resiliente e cheio de confiança.
+Outros Indexadores são incentivados a apoiar subgraphs com o volume de query atual. O volume de query ao Indexador de atualização deve se aproximar de zero, já que ele tem um tamanho de alocação pequeno e outros Indexadores devem ser escolhidos por queries antes disso.

From 08fb8f59d2e86e652273eb2823a55ec15f34dd44 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:20 -0500
Subject: [PATCH 1140/1325] New translations sunrise.mdx (Russian)

---
 website/pages/ru/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/ru/sunrise.mdx b/website/pages/ru/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/ru/sunrise.mdx
+++ b/website/pages/ru/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From ea71b426a386f2cebbece940073f058b989b6315 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:21 -0500
Subject: [PATCH 1141/1325] New translations sunrise.mdx (Swedish)

---
 website/pages/sv/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/sv/sunrise.mdx b/website/pages/sv/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/sv/sunrise.mdx
+++ b/website/pages/sv/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From c226af5d0d75b030715a7925edbbf2294ada4a58 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:22 -0500
Subject: [PATCH 1142/1325] New translations sunrise.mdx (Turkish)

---
 website/pages/tr/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/tr/sunrise.mdx b/website/pages/tr/sunrise.mdx
index 1e128fe103a0..e40c0b6f7914 100644
--- a/website/pages/tr/sunrise.mdx
+++ b/website/pages/tr/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-Bu plan, yeni yayınlanan subgraphlar üzerinde sorgular sunmak için bir yükseltme İndeksleyicisi ve yeni blok zinciri ağlarını Graph'a entegre etme yeteneği de dahil olmak üzere Graph ekosistemindeki önceki birçok önceki gelişmeyi içermektedir.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Desteklenen zincirlerin kapsamlı bir listesini inceleyin [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Yükseltme İndeksleyicisini neden Edge & Node çalıştırıyor?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-Yükseltme İndeksleyicisi ayrıca İndeksleyici topluluğuna Graph Ağı'ndaki subgraphlar ve yeni zincirler konusunda potansiyel talep hakkında bilgi sunmaktadır.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### Bu Delegatörler için ne anlama gelmektedir?
 
-Yükseltme İndeksleyicisi, Delegatörler için büyük bir fırsat sunmaktadır. Daha fazla subgraph barındırılan hizmetten Graph Ağı'na yükseltildikçe, Delegatörler artan ağ etkinliğinden faydalanmaya devam edecektir.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Yükseltme İndeksleyicisi, mevcut İndeksleyicilerle ödüller için rekabet edecek mi?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-Hayır, yükseltme İndeksleyicisi yalnızca subgraph başına minimum miktarı tahsis edecek ve indeksleme ödüllerini toplamayacaktır.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### Bu durum subgraph geliştiricilerini nasıl etkileyecek?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### Bu, veri tüketicilerine nasıl fayda sağlar?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### Yükseltme İndeksleyicisi sorguları nasıl fiyatlandıracak?
-
-Yükseltme İndeksleyicisi, sorgu ücreti pazarını etkilememek adına sorguları piyasa fiyatına göre fiyatlandıracaktır.
-
-### Yükseltme İndeksleyicisi'nin bir subgraph'ı desteklemeyi durdurması için kriterler nelerdir?
-
-Yükseltme İndeksleyicisi, bir subgraph'a, en az 3 diğer İndeksleyici tarafından sağlanan tutarlı sorgularla yeterli ve başarılı bir şekilde hizmet verilene kadar hizmet verecektir.
-
-Ayrıca, yükseltme İndeksleyicisi, bir subhraph son 30 günde sorgulanmamış ise desteğini durduracaktır.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Kendi altyapımı çalıştırmam gerekiyor mu?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Subgraph'ınız yeterli kürasyon sinyaline ulaştığında ve diğer İndeksleyiciler tarafından desteklemeye başladığında, yükseltme İndeksleyicisi kademeli olarak azalacak ve diğer İndeksleyicilerin indeksleme ödüllerini ve sorgu ücretlerini toplama fırsatı tanıyacaktır.
-
-### Kendi indeksleme altyapımı barındırmalı mıyım?
-
-Kendi projeniz için altyapıyı çalıştırmak, Graph Ağı'nı kullanmaya kıyasla [önemli ölçüde daha fazla kaynak](/network/benefits/) gerektirir.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-Bununla birlikte, hala bir [Graph Düğümü](https://github.com/graphprotocol/graph-node) çalıştırmakla ilgileniyorsanız, subgraph'ınızda ve diğerlerinde veri sunarak indeksleme ödülleri ve sorgu ücretleri kazanmak için Graph Ağı'na [İndeksleyici olarak](https://thegraph.com/blog/how-to-become-indexer/) katılmayı düşünün.
-
-### Merkezi bir indeksleme sağlayıcısı kullanmalı mıyım?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-İşte Graph'ın merkezi barındırmaya göre avantajlarının ayrıntılı bir açıklaması:
+### How does the upgrade Indexer price queries?
 
-- **Dayanıklılık ve Yedeklilik**: Merkeziyetsiz sistemler, dağıtık yapıları nedeniyle doğal olarak daha dayanıklı ve esnektir. Veriler tek bir sunucuda veya konumda depolanmaz. Bunun yerine, dünyanın dört bir yanındaki yüzlerce bağımsız İndeksleyici tarafından sunulur. Bu, bir düğümün arızalanması durumunda veri kaybı veya hizmet kesintisi riskini azaltır ve olağanüstü çalışma süreleri (%99,99) sağlar.
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Hizmet Kalitesi**: Etkileyici çalışma süresine ek olarak, Graph Ağı yaklaşık 106 ms medyan sorgu hızı (gecikme) ve barındırılan alternatiflere kıyasla daha yüksek sorgu başarı oranlarına sahiptir. Daha fazla bilgi için [bu bloğa göz atın] (https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Merkezi olmayan yapısı, güvenliği ve şeffaflığı nedeniyle blok zincir ağını seçtiğiniz gibi, aynı şekilde Graph Ağı'nı tercih etmek bu ilkelerin bir devamı niteliğindedir. Veri altyapınızı bu değerlerle uyumlu hale getirerek bütünlük, dayanıklılık ve güvene dayalı bir geliştirme ortamını sağlarsınız.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From cbbf923664e426d710841820decb219103b098b2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:23 -0500
Subject: [PATCH 1143/1325] New translations sunrise.mdx (Ukrainian)

---
 website/pages/uk/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/uk/sunrise.mdx b/website/pages/uk/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/uk/sunrise.mdx
+++ b/website/pages/uk/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 82ee51f56deafb403534cf0fc4beaed31ec317a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:24 -0500
Subject: [PATCH 1144/1325] New translations sunrise.mdx (Chinese Simplified)

---
 website/pages/zh/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/zh/sunrise.mdx b/website/pages/zh/sunrise.mdx
index e38d91f89489..a39e1853cc94 100644
--- a/website/pages/zh/sunrise.mdx
+++ b/website/pages/zh/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-这一计划借鉴了 The Graph 生态系统的许多先前的发展，包括升级索引人以提供对新发布子图的查询服务，以及将新的区块链网络集成到 The Graph 中的能力。
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-请在[此处](/developing/supported-networks/) 查找支持的链的综合列表。
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### 为什么 Edge & Node 运行升级索引人？
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-升级索引人还向索引人社区提供关于 The Graph Network 上潜在的子图需求和新链的信息。
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### 这对于委托人来说意味着什么？
 
-升级索引人为代币委托人提供了强大的机会。随着越来越多的子图从托管服务迁移到 The Graph Network，委托人将从增加的网络活动中获益。
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### 升级索引人会与现有的索引人竞争奖励吗？
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-不，升级索引人只会为每个子图分配最低金额，并不会收集索引奖励。
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### 这将如何影响子图开发者？
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### 这如何使数据消费者受益？
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### 升级的索引人将如何定价查询？
-
-升级的索引人将按市场价格定价查询，以不影响查询费用市场。
-
-### 升级索引人停止支持一个子图的标准是什么？
-
-升级的索引人将为一个子图提供服务，直到它能够获得由至少3个其他索引人提供的持续且成功的查询服务。
-
-此外，如果一个子图在过去的30天内没有被查询，升级的索引人将停止支持该子图。
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### 我需要自己运行基础设施吗？
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-一旦您的子图达到足够的策展信号，并且其他索引人开始支持它，那么升级索引人将逐渐减少，这将允许其他索引人收集索引奖励和查询费用。
-
-### 我应该自己托管索引基础设施吗？
-
-与使用The Graph Network相比，为您自己的项目运行基础设施需要的资源明显更多(/network/benefits/)。
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-话虽如此，如果您仍有兴趣运行[Graph Node](https://github.com/graphprotocol/graph-node)，考虑加入The Graph Network，作为索引人，通过为您的子图和其他子图提供数据来赚取索引奖励和查询费用。了解如何成为索引人的更多信息，请参阅[此链接](https://thegraph.com/blog/how-to-become-indexer/)。
-
-### 我应该使用中心化的索引提供者吗？
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-以下是The Graph相对于中心化托管的好处的详细分析：
+### How does the upgrade Indexer price queries?
 
-- **弹性与冗余性**：分散系统因其分布式性质而本质上更加坚固和弹性十足。数据不存储在单一服务器或位置上，而是由全球数百个独立的索引人提供。这降低了数据丢失或服务中断的风险，即使一个节点失败，也能实现卓越的可用性（99.99%）。
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **服务质量**：除了令人印象深刻的可用性之外，The Graph Network具有约106毫秒的中位查询速度（延迟），以及相对于托管的替代方案，更高的查询成功率。更多信息请参阅[此博客](https://thegraph.com/blog/qos-the-graph-network/)。
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-正如您选择区块链网络以获取分散性、安全性和透明性一样，选择The Graph Network是这些相同原则的延伸。通过将您的数据基础设施与这些价值观保持一致，您确保了一个有凝聚力、弹性十足且以信任为驱动的开发环境。
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 73e6bb00f79157b4f0993ddd284ecaa28b73adad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:25 -0500
Subject: [PATCH 1145/1325] New translations sunrise.mdx (Urdu (Pakistan))

---
 website/pages/ur/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/ur/sunrise.mdx b/website/pages/ur/sunrise.mdx
index 17e5e917240a..89e51796c01e 100644
--- a/website/pages/ur/sunrise.mdx
+++ b/website/pages/ur/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-یہ منصوبہ گراف ایکو سسٹم کی کئی پچھلی پیشرفتوں پر مبنی ہے، بشمول نئے شائع شدہ سب گرافس پر کیوریز پیش کرنے کے لیے ایک اپ گریڈ انڈیکسر، اور نئے بلاکچین نیٹ ورکس کو گراف میں ضم کرنے کی صلاحیت.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## گراف نیٹ ورک میں سب گراف کو اپ گریڈ کرنا
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-معاون چینز کی ایک جامع فہرست [یہاں](/developing/supported-networks/) تلاش کریں.
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### ایج اور نوڈ اپ گریڈ انڈیکسر کیوں چلا رہا ہے؟
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-اپ گریڈ انڈیکسر انڈیکسر کمیونٹی کو گراف نیٹ ورک پر سب گرافس اور نئی چینز کی ممکنہ مانگ کے بارے میں معلومات بھی فراہم کرتا ہے.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### ڈیلیگیٹرز کے لیے اس کا کیا مطلب ہے؟
 
-اپ گریڈ انڈیکسر ڈیلیگیٹرز کے لیے ایک طاقتور موقع فراہم کرتا ہے۔ چونکہ زیادہ سب گراف ہوسٹڈ سروس سے گراف نیٹ ورک میں اپ گریڈ ہوتے ہیں، ڈیلیگیٹرز نیٹ ورک کی بڑھتی ہوئی سرگرمی سے فائدہ اٹھاتے ہیں.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### کیا اپ گریڈ انڈیکسر انعامات کے لیے موجودہ انڈیکسرز کا مقابلہ کرے گا؟
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-نہیں، اپ گریڈ انڈیکسر صرف فی سب گراف کم از کم رقم مختص کرے گا اور انڈیکسنگ انعامات جمع نہیں کرے گا.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### یہ سب گراف ڈویلپرز کو کیسے متاثر کرے گا؟
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### اس سے ڈیٹا صارفین کو کیسے فائدہ ہوتا ہے؟
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### اپ گریڈ انڈیکسر کیوریز کی قیمت کیسے لگائے گا؟
-
-اپ گریڈ انڈیکسر مارکیٹ ریٹ پر کیوریز کی قیمت لگائے گا تاکہ کیوری فیس مارکیٹ پر اثر انداز نہ ہو.
-
-### اپ گریڈ انڈیکسر کے سب گراف کو سپورٹ کرنے سے روکنے کے لیے کیا معیار ہیں؟
-
-اپ گریڈ انڈیکسر ایک سب گراف پر کام کرے گا جب تک کہ یہ کم از کم 3 دیگر انڈیکسرز کے ذریعہ پیش کردہ مستقل کیوریز کے ساتھ کافی اور کامیابی کے ساتھ پیش نہیں کیا جاتا ہے.
-
-مزید برآں، اپ گریڈ انڈیکسر سب گراف کو سپورٹ کرنا بند کر دے گا اگر اس سے پچھلے 30 دنوں میں کیوری نہیں کیا گیا ہے.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### کیا مجھے اپنا انفراسٹرکچر چلانے کی ضرورت ہے؟
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-ایک بار جب آپ کا سب گراف مناسب کیوریشن سگنل تک پہنچ جاتا ہے اور دوسرے انڈیکسرز اس کی حمایت کرنا شروع کر دیتے ہیں، تو اپ گریڈ انڈیکسر آہستہ آہستہ ختم ہو جائے گا، جس سے دوسرے انڈیکسرز کو انڈیکسنگ انعامات اور کیوری کی فیسیں جمع کرنے کی اجازت مل جائے گی.
-
-### کیا مجھے اپنے انڈیکسنگ انفراسٹرکچر کی میزبانی کرنی چاہئے؟
-
-گراف نیٹ ورک کے استعمال کے مقابلے میں آپ کے اپنے پروجیکٹ کے لیے انفراسٹرکچر چلانا [نمایاں طور پر زیادہ وسائل والا](/network/benefits/) ہے.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-یہ کہا جا رہا ہے، اگر آپ ابھی بھی [گراف نوڈ](https://github.com/graphprotocol/graph-node) چلانے میں دلچسپی رکھتے ہیں، تو گراف نیٹ ورک میں شامل ہونے پر غور کریں [بطور انڈیکسر](https://thegraph. com/blog/how-to-become-indexer/) اپنے سب گراف اور دیگر پر ڈیٹا پیش کرکے انڈیکسنگ انعامات اور کیوری کی فیس حاصل کرنے کے لیے.
-
-### کیا مجھے سینٹرلائزڈ انڈیکسنگ فراہم کنندہ استعمال کرنا چاہیے؟
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-سینٹرلائزڈ ہوسٹنگ پر گراف کے فوائد کی تفصیلی بریک ڈاؤن یہ ہے:
+### How does the upgrade Indexer price queries?
 
-- **لچک اور ریڈینڈینسی**: ڈیسینٹرالائزڈ نظام اپنی تقسیم شدہ نوعیت کی وجہ سے فطری طور پر زیادہ مضبوط اور لچکدار ہوتے ہیں۔ ڈیٹا کسی ایک سرور یا مقام پر محفوظ نہیں ہوتا ہے۔ اس کے بجائے، یہ دنیا بھر میں سینکڑوں آزاد انڈیکسرز کے ذریعہ پیش کیا جاتا ہے۔ اگر ایک نوڈ ناکام ہو جاتا ہے تو یہ ڈیٹا کے ضائع ہونے یا سروس میں رکاوٹ کا خطرہ کم کرتا ہے، جس سے غیر معمولی اپ ٹائم ہوتا ہے (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **سروس کا معیار**: متاثر کن اپ ٹائم کے علاوہ، گراف نیٹ ورک میں ~106ms میڈین کیوری کی رفتار (لیٹنسی) اور میزبان متبادل کے مقابلے میں کیوری کی کامیابی کی اعلی شرحیں شامل ہیں۔ مزید پڑھیں [اس بلاگ] میں (https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-جس طرح آپ نے اپنے بلاکچین نیٹ ورک کو اس کی ڈیسینٹرالائزڈ، سیکورٹی اور شفافیت کے لیے منتخب کیا ہے، اسی طرح گراف نیٹ ورک کا انتخاب انہی اصولوں کی توسیع ہے۔ اپنے ڈیٹا انفراسٹرکچر کو ان اقدار کے ساتھ سیدھ میں لا کر، آپ ایک مربوط، لچکدار، اور اعتماد پر مبنی ترقیاتی ماحول کو یقینی بناتے ہیں.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 5434740f9b399a555398ef56f6370a31db4ebe61 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:26 -0500
Subject: [PATCH 1146/1325] New translations sunrise.mdx (Vietnamese)

---
 website/pages/vi/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/vi/sunrise.mdx b/website/pages/vi/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/vi/sunrise.mdx
+++ b/website/pages/vi/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 7a2747f9f492d5aacf8bb5985b608cccedf7f0f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:27 -0500
Subject: [PATCH 1147/1325] New translations sunrise.mdx (Marathi)

---
 website/pages/mr/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/mr/sunrise.mdx b/website/pages/mr/sunrise.mdx
index 32bf6c6d26d4..14d1444cf8cd 100644
--- a/website/pages/mr/sunrise.mdx
+++ b/website/pages/mr/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
 
-## What is the Sunrise of Decentralized Data?
+## What was the Sunrise of Decentralized Data?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
 
-### What are the phases of the Sunrise?
+### What happened to the hosted service?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
 
-## Upgrading subgraphs to The Graph Network
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
 
-### When will hosted service subgraphs no longer be available?
+### Was Subgraph Studio impacted by this upgrade?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> The upgrade Indexer is currently active.
 
-### What chains does the upgrade Indexer support?
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### What does the upgrade Indexer do?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### Did the upgrade Indexer compete with existing Indexers for rewards?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
 
-### How will this affect subgraph developers?
+### How does this affect subgraph developers?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
 
-### How does this benefit data consumers?
+### How does the upgrade Indexer benefit data consumers?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### How does the upgrade Indexer price queries?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### When will the upgrade Indexer stop supporting a subgraph?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 7d1089fc46687813c0cef89081f03add7891beca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:28 -0500
Subject: [PATCH 1148/1325] New translations sunrise.mdx (Hindi)

---
 website/pages/hi/sunrise.mdx | 226 ++++++-----------------------------
 1 file changed, 36 insertions(+), 190 deletions(-)

diff --git a/website/pages/hi/sunrise.mdx b/website/pages/hi/sunrise.mdx
index 32bf6c6d26d4..577e562dd9df 100644
--- a/website/pages/hi/sunrise.mdx
+++ b/website/pages/hi/sunrise.mdx
@@ -1,233 +1,79 @@
 ---
-title: Sunrise + Upgrading to The Graph Network FAQ
+title: पोस्ट-सनराइज + The Graph Network में अपग्रेडिंग FAQ
 ---
 
-> Note: This document is continually updated to ensure the most accurate and helpful information is provided. New questions and answers are added on a regular basis. If you can’t find the information you’re looking for, or if you require immediate assistance, [reach out on Discord](https://discord.gg/graphprotocol). If you are looking for billing information, then please refer to [billing](/billing/).
+> नोट: Decentralized Data का Sunrise 12 जून, 2024 को समाप्त हो गया।
 
-## What is the Sunrise of Decentralized Data?
+## विकेंद्रीकृत डेटा का सूर्योदय क्या था?
 
-The Sunrise of Decentralized Data is an initiative spearheaded by Edge & Node. The goal is to enable subgraph developers to seamlessly upgrade to The Graph’s decentralized network.
+"Decentralized Data का उदय" Edge & Node द्वारा आरंभ की गई एक पहल थी। इस पहल ने subgraph डेवलपर्स को The Graph के विकेंद्रीकृत नेटवर्क में सहजता से अपग्रेड करने में सक्षम बनाया।
 
-This plan draws on many previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs, and the ability to integrate new blockchain networks to The Graph.
+इस योजना ने The Graph इकोसिस्टम के पिछले विकासों पर आधारित किया, जिसमें नए प्रकाशित सबग्राफ पर क्वेरी सर्व करने के लिए एक अपग्रेडेड इंडेक्सर शामिल था।
 
-### What are the phases of the Sunrise?
+### Hosted service का क्या होगा?
 
-**Sunray**: Enable support for hosted service chains, introduce a seamless upgrade flow, offer a free plan on The Graph Network, and provide simple payment options.\
-**Sunbeam**: The upgrade window that subgraph developers will have to upgrade their hosted service subgraphs to The Graph Network. This window will end at 10 a.m. PT on June 12th 2024.\
-**Sunrise**: Hosted service endpoints will no longer be available after 10 a.m. PT on June 12th, 2024.
+होस्टेड सेवा के क्वेरी एंडपॉइंट अब उपलब्ध नहीं हैं, और डेवलपर्स होस्टेड सेवा पर नए सबग्राफ्स को तैनात नहीं कर सकते हैं।
 
-## Upgrading subgraphs to The Graph Network
+अपग्रेड प्रक्रिया के दौरान, होस्टेड सर्विस सबग्राफ के मालिक अपने सबग्राफ को The Graph Network पर अपग्रेड कर सकते थे। इसके अतिरिक्त, डेवलपर्स ऑटो-अपग्रेड किए गए सबग्राफ को क्लेम करने में सक्षम थे।
 
-### When will hosted service subgraphs no longer be available?
+### क्या इस अपग्रेड से Subgraph Studio प्रभावित हुआ था?
 
-Hosted service query endpoints will remain active until 10 a.m. PT on June 12th. After June 12th at 10 a.m. PT, query endpoints will no longer be available, and developers will no longer be able to deploy new subgraph versions on the hosted service.
+नहीं, सबग्राफ स्टूडियो पर Sunrise का कोई प्रभाव नहीं पड़ा। सबग्राफ तुरंत क्वेरी के लिए उपलब्ध थे, जो अपग्रेड किए गए Indexer द्वारा संचालित हैं, जो उसी इंफ्रास्ट्रक्चर का उपयोग करता है जैसा Hosted Service में होता है।
 
-### I didn’t upgrade my subgraph by June 12th at 10 a.m. PT. What should I do if I still want to use it?
+### सबग्राफ्स को Arbitrum पर क्यों प्रकाशित किया गया, क्या इसने एक अलग नेटवर्क को इंडेक्स करना शुरू किया?
 
-The hosted service homepage is still accessible and can be used to search for legacy hosted service subgraphs. If your hosted service subgraph has already been auto-upgraded, you may claim its network equivalent as the original owner. If your subgraph was not [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam), you can still upgrade and publish it.
-
-Upgrading takes less than five minutes on average. Once your subgraph is up, simply set up an API key in Subgraph Studio, update your API query endpoint, and begin querying!
-
-### Will my hosted service subgraph be supported on The Graph Network?
-
-Yes, the upgrade Indexer will automatically support all hosted service subgraphs published to The Graph Network for a seamless upgrade experience.
-
-### How do I upgrade my hosted service subgraph?
-
-> Note: Upgrading a subgraph to The Graph Network cannot be undone.
-
-<VideoEmbed youtube="hCmX5Dlhdjw" />
-
-To upgrade a hosted service subgraph, you can visit the subgraph dashboard on the [hosted service](https://thegraph.com/hosted-service).
-
-1. Select the subgraph(s) you want to upgrade.
-2. Select the receiving wallet (the wallet that will become the owner of the subgraph).
-3. Click the "Upgrade" button.
-
-Once your subgraph is published, the [upgrade Indexer](#what-is-the-upgrade-indexer) will begin serving queries on it. Once you have generated an API key, you can begin making queries immediately. [Learn more](/cookbook/upgrading-a-subgraph/#what-next).
-
-### How can I get support with the upgrade process?
-
-The Graph community is here to support developers as they move to The Graph Network. Join The Graph's [Discord server](https://discord.gg/vtvv7FP) and request help in the #upgrade-decentralized-network channel.
-
-### How can I ensure high quality of service and redundancy for subgraphs on The Graph Network?
-
-All subgraphs will be supported by the upgrade Indexer. For a higher quality of service and more robust redundancy, you can add a curation signal to subgraphs eligible for indexing rewards. It is recommended that you curate your subgraph with at least 3000 GRT (per subgraph) to attract about 3 Indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-Please note that this indexing incentive does not deplete over time; it has no depletion rate and is instantly withdrawable at any time. If you want to add 3000 GRT in signal, you will need to signal 3030 GRT (as 1% would be burned). Note that a 0.5% fee is also deducted from the subgraph’s signal every time a new version is published.
-
-Subgraphs which are not eligible for indexing rewards may struggle to attract further Indexers. For example, indexing rewards may not be available for subgraphs on certain chains (check support [here](/developing/supported-networks)).
-
-Members from these blockchain communities are encouraged to integrate their chain through the [Chain Integration Process](/chain-integration-overview/).
-
-### How do I publish new versions to the network?
-
-You can deploy new versions of your subgraph directly to Subgraph Studio, which provides a testing environment, before publishing to the network for production usage. Subgraph Studio has a different deployment command and requires a `version-label` for each new deployment.
-
-1. Upgrade to the latest version of [graph-cli](https://www.npmjs.com/package/@graphprotocol/graph-cli)
-2. Update your deploy command
-
-```sh
-# Authorize with Subgraph Studio, available on your subgraph page
-## Alternativel pass this into the deploy command as --access-token (see below)
-graph auth --studio <deploy-key>
-
-# Deploy to Subgraph Studio
-## Unlike the hosted service, the name is just the subgraph name (no github id)
-## If using `--node` directly, you can pass in https://api.studio.thegraph.com/deploy/
-graph deploy --studio --version <version> --access-token <deploy-key> <subgraph-name>
-```
-
-This new version will then sync in Subgraph Studio, a testing and sandbox environment. When you are ready to move a new version to production, you can [publish the subgraph version](/publishing/publishing-a-subgraph).
-
-> Publishing requires Arbitrum ETH - upgrading your subgraph also airdrops a small amount to facilitate your first protocol interactions 🧑‍🚀
-
-### I use a subgraph developed by someone else, how can I make sure that my service isn't interrupted?
-
-When the owner has upgraded their subgraph, you will be able to easily go from the subgraph's hosted service page to the corresponding subgraph on The Graph Network, and update your application to use the new subgraph's query URL. [Learn more](/querying/querying-the-graph).
-
-Around the start of June, Edge & Node will automatically upgrade actively queried subgraphs. This will give any third-party data consumers an opportunity to move subgraph endpoints to The Graph Network before 10 a.m. on June 12th. The subgraph owners will still be able to claim these subgraphs on the network using the hosted service upgrade flow.
-
-### My subgraph has been auto-upgraded, what does that mean?
-
-Subgraphs on the hosted service are open APIs, and many subgraphs are relied upon by third-party developers to build their applications. To give those developers sufficient time to move to The Graph Network, Edge & Node will be "auto-upgrading" highly used subgraphs. A link to the "auto-upgraded" subgraph will be visible on the original subgraph's page on the hosted service.
-
-Owners of "auto-upgraded" subgraphs can easily claim their upgraded subgraphs using the same [upgrade flow](/cookbook/upgrading-a-subgraph) - such subgraphs can be identified by their "auto-upgraded" tag. Ownership of the subgraph on The Graph Network will be transferred to the owner's wallet.
-
-### My subgraph has been auto-upgraded, but I need to deploy a new version
-
-You can use the [upgrade flow](/cookbook/upgrading-a-subgraph) to claim the auto-upgraded subgraph, and then you can deploy a new version in Subgraph Studio, using the same infrastructure that powers the hosted service.
-
-If you require an urgent fix, please contact support.
-
-### What happens if I don't upgrade my subgraph?
-
-Subgraphs will be queryable on the hosted service until 10 a.m. PT on June 12th. After this date, the hosted service homepage will still be accessible, however, query endpoints will no longer be available. Owners of hosted service subgraphs will still be able to upgrade their subgraphs to The Graph Network after June 12th, though earlier upgrades are entitled to [earn rewards](https://thegraph.com/sunrise-upgrade-program/). Developers will also be able to claim [auto-upgraded subgraphs](https://thegraph.com/blog/unveiling-updated-sunrise-decentralized-data/#phase-2-sunbeam).
-
-### What should I do with my subgraphs on the hosted service? Will they stop working and should I delete them?
-
-It is not possible to delete subgraphs. Query endpoints will remain active until 10 a.m. PT on June 12th, regardless of whether they have been upgraded or not.
-
-### Will Subgraph Studio be impacted by this upgrade?
-
-No, Subgraph Studio will not be impacted by Sunrise.
-
-### What will happen to the hosted service?
-
-After 10 a.m. PT on June 12th, query endpoints will no longer be available, and owners won't be able to deploy or query the hosted service. However, the hosted service UI will still show subgraph pages, and subgraph owners will be able to upgrade their subgraphs if they haven't already. The hosted service UI will be retired at a later date.
-
-### Will subgraphs need to be re-indexed again?
-
-No, rest assured that your subgraph will not need to be re-indexed when it is upgraded to The Graph Network. Subgraphs will be immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service. If your subgraph is indexing a network that is eligible for indexing rewards, you can add signal to attract indexers. [Learn more about adding signal to your subgraph](/publishing/publishing-a-subgraph/#adding-signal-to-your-subgraph).
-
-### I’m experiencing indexing issues. What should I do?
-
-Rest assured that network Indexers are prepared to provide support during this upgrade. If you experience issues with any of your subgraph queries, please reach out to support@thegraph.zendesk.com
-
-### Why is my subgraph being published to Arbitrum, is it indexing a different network?
-
-The Graph Network was originally deployed on mainnet Ethereum but moved to Arbitrum One to reduce gas costs for all users. As such any new subgraphs are published to The Graph Network on Arbitrum so that they can be supported by Indexers. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](https://thegraph.com/docs/en/developing/supported-networks/)
-
-### How can I get started querying subgraphs on The Graph Network?
-
-You can explore available subgraphs on [Graph Explorer](https://thegraph.com/explorer). [Learn more about querying subgraphs on The Graph](/querying/querying-the-graph).
+The Graph Network को शुरू में Ethereum मेननेट पर तैनात किया गया था, लेकिन बाद में सभी उपयोगकर्ताओं के लिए गैस लागत को कम करने के लिए इसे Arbitrum वन पर स्थानांतरित कर दिया गया। परिणामस्वरूप, सभी नए सबग्राफ़ Arbitrum पर The Graph Network पर प्रकाशित किए जाते हैं ताकि Indexer उनका समर्थन कर सकें। Arbitrum वह नेटवर्क है जिस पर सबग्राफ़ प्रकाशित किए जाते हैं, लेकिन सबग्राफ़ किसी भी [समर्थित नेटवर्क](/developing/supported-networks/) को इंडेक्स कर सकते हैं।
 
 ## About the Upgrade Indexer
 
-### What is the upgrade Indexer?
-
-The upgrade Indexer is designed to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and to support new versions of existing subgraphs that have not yet been indexed.
-
-The upgrade Indexer aims to bootstrap chains that don't have indexing rewards yet on The Graph Network and to serve as a fallback for new subgraph versions. The goal is to ensure that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+> अपग्रेड Indexer वर्तमान में सक्रिय है।
 
-### What chains does the upgrade Indexer support?
+अपग्रेड Indexer को Hosted Service से The Graph Network में सबग्राफ़्स के अपग्रेड करने के अनुभव को सुधारने और उन मौजूदा सबग्राफ़्स के नए संस्करणों का समर्थन करने के लिए लागू किया गया था जो अभी तक इंडेक्स नहीं किए गए थे।
 
-The upgrade Indexer supports chains that were previously only available on the hosted service.
+### अपग्रेड Indexer क्या करता है?
 
-Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- यह उन चेन को बूटस्ट्रैप करता है जिन्हें अभी तक The Graph Network पर इंडेक्सिंग पुरस्कार नहीं मिले हैं और यह सुनिश्चित करता है कि एक Indexer उपलब्ध हो ताकि एक Subgraph प्रकाशित होने के तुरंत बाद क्वेरी को यथाशीघ्र सेवा दी जा सके।
+- यह उन चेन का समर्थन करता है जो पहले केवल Hosted Service पर उपलब्ध थीं। समर्थित चेन की एक व्यापक सूची [यहां](https://thegraph. com/developing/supported-networks/) देखें।
+- जो Indexer अपग्रेड इंडेक्सर का संचालन करते हैं, वे नए सबग्राफ़ और अतिरिक्त चेन का समर्थन करने के लिए एक सार्वजनिक सेवा के रूप में ऐसा करते हैं जो इंडेक्सिंग पुरस्कारों की कमी का सामना कर रहे हैं, जब तक कि The Graph काउंसिल उन्हें मंजूरी नहीं देती।
 
 ### Why is Edge & Node running the upgrade Indexer?
 
-Edge & Node has historically maintained the hosted service and, as a result, has already synced data for hosted service subgraphs.
-
-All Indexers are encouraged to become upgrade Indexers as well. However, note that operating an upgrade Indexer is primarily a public service to support new subgraphs and additional chains that lack indexing rewards before they are approved by The Graph Council.
+Edge & Node ने ऐतिहासिक रूप से होस्टेड सेवा का प्रबंधन किया है और, परिणामस्वरूप, उनके पास होस्टेड सेवा के सबग्राफ के लिए पहले से ही समन्वयित डेटा है।
 
 ### What does the upgrade indexer mean for existing Indexers?
 
-Chains that were previously only supported on the hosted service will now be available to developers on The Graph Network without indexing rewards at first, but it will unlock query fees for any Indexer that is interested. This should lead to an increase in the number of subgraphs being published on The Graph Network, providing more opportunities for Indexers to index and serve these subgraphs in return for query fees, even before indexing rewards are enabled for a chain.
+पहले केवल होस्टेड सेवा पर समर्थित चेन अब बिना indexing पुरस्कार के डेवलपर्स के लिएT he Graph Network पर उपलब्ध कराई गईं।
+
+हालांकि, इस कार्रवाई ने किसी भी इच्छुक Indexer के लिए क्वेरी शुल्क को अनलॉक कर दिया और The Graph Network पर प्रकाशित सबग्राफ की संख्या बढ़ा दी। परिणामस्वरूप, Indexers के पास इन सबग्राफ को इंडेक्स करने और सेवा देने के लिए अधिक अवसर हैं, जो कि क्वेरी शुल्क के बदले में हैं, यहां तक कि जब तक किसी चेन के लिए इंडेक्सिंग इनाम सक्षम नहीं होते।
 
-The upgrade Indexer also provides the Indexer community with information about potential demand for subgraphs and new chains on The Graph Network.
+अपग्रेड इंडेक्सर Indexer समुदाय को The Graph Network पर सबग्राफ और नए चेन की संभावित मांग के बारे में जानकारी भी प्रदान करता है।
 
 ### What does this mean for Delegators?
 
-The upgrade Indexer offers a powerful opportunity for Delegators. As more subgraphs are upgraded from the hosted service to The Graph Network, Delegators stand to benefit from the increased network activity.
+अपग्रेड Indexer डेलीगेटर्स के लिए एक शक्तिशाली अवसर प्रदान करता है। क्योंकि इससे अधिक सबग्राफ को होस्टेड सेवा से The Graph Network में अपग्रेड करने की अनुमति मिली, डेलीगेटर्स को बढ़ी हुई नेटवर्क गतिविधि का लाभ मिलता है।
 
-### Will the upgrade Indexer compete with existing Indexers for rewards?
+### क्या अपग्रेड किया गया Indexer मौजूदा Indexer के साथ पुरस्कारों के लिए प्रतिस्पर्धा करता था?
 
-No, the upgrade Indexer will only allocate the minimum amount per subgraph and will not collect indexing rewards.
+नहीं, अपग्रेड किया गया Indexer केवल प्रति Subgraph न्यूनतम राशि आवंटित करता है और indexing पुरस्कार एकत्र नहीं करता है।
 
-It operates on an “as needed” basis and serves as a fallback until sufficient service quality is achieved by at least 3 other Indexers in the network for respective chains and subgraphs.
+यह "आवश्यकता अनुसार" आधार पर काम करता है, एक बैकअप के रूप में कार्य करता है जब तक कि नेटवर्क में संबंधित चेन और सबग्राफ के लिए कम से कम तीन अन्य Indexer द्वारा पर्याप्त सेवा गुणवत्ता प्राप्त नहीं की जाती।
 
-### How will this affect subgraph developers?
+### यह Subgraph डेवलपर्स को कैसे प्रभावित करता है?
 
-Subgraph developers will be able to query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or publishing from Subgraph Studio, as no lead time will be required for indexing.
+सबग्राफ डेवलपर्स अपने सबग्राफ को The Graph Network पर लगभग तुरंत ही अपग्रेड किए जाने के बाद या [Subgraph Studio से प्रकाशित करने](/publishing/publishing-a-subgraph/) के बाद क्वेरी कर सकते हैं, क्योंकि indexing के लिए कोई लीड टाइम की आवश्यकता नहीं थी। कृपया ध्यान दें कि [सबग्राफ बनाना](/developing/creating-a-subgraph) इस अपग्रेड से प्रभावित नहीं हुआ था।
 
-### How does this benefit data consumers?
+### अपग्रेड Indexer डेटा उपभोक्ताओं को कैसे लाभ पहुंचाता है?
 
 The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
 
-### How will the upgrade Indexer price queries?
-
-The upgrade Indexer will price queries at the market rate so as not to influence the query fee market.
-
-### What are the criteria for the upgrade Indexer to stop supporting a subgraph?
-
-The upgrade Indexer will serve a subgraph until it is sufficiently and successfully served with consistent queries served by at least 3 other Indexers.
-
-Furthermore, the upgrade Indexer will stop supporting a subgraph if it has not been queried in the last 30 days.
-
-Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it will have a small allocation size, and other Indexers will be chosen for queries ahead of it.
-
-## About The Graph Network
-
-### Do I need to run my own infrastructure?
-
-No, all infrastructure is operated by independent Indexers on The Graph Network, including the upgrade Indexer ([read more below](#what-is-the-upgrade-indexer)).
-
-You can use [Subgraph Studio](https://thegraph.com/studio/) to create, test, and publish your subgraph. All hosted service users must upgrade their subgraph to The Graph Network before 10 a.m. PT on June 12th, 2024.
-
-The [Sunrise Upgrade Indexer](/sunrise/#what-is-the-upgrade-indexer) ensures the indexing of all subgraphs. However, signaling GRT on a particular subgraph will draw more indexers to it. This incentivization of additional Indexers through curation aims to enhance the quality of service for queries by reducing latency and enhancing network availability.
-
-When signaling, Curators can decide to signal on a specific version of the subgraph or to signal using auto-migrate. If they signal using auto-migrate, a curator’s shares will always be updated to the latest version published by the developer. If they decide to signal on a specific version instead, shares will always stay on that specific version.
-
-To assist teams that are transitioning subgraphs from the hosted service to the Graph Network, curation support is now available. If you require assistance with curation to enhance the quality of service, please send a request to the Edge & Node team at support@thegraph.zendesk.com and specify the subgraphs you need assistance with.
-
-Once your subgraph has reached adequate curation signal and other Indexers begin supporting it, the upgrade Indexer will gradually taper off, allowing other Indexers to collect indexing rewards and query fees.
-
-### Should I host my own indexing infrastructure?
-
-Running infrastructure for your own project is [significantly more resource intensive](/network/benefits/) when compared to using The Graph Network.
-
-Additionally, The Graph Network is significantly more robust, reliable, and cost-efficient than anything provided by a single organization or team. Hundreds of independent Indexers around the world power The Graph Network, ensuring safety, security, and redundancy.
-
-That being said, if you’re still interested in running a [Graph Node](https://github.com/graphprotocol/graph-node), consider joining The Graph Network [as an Indexer](https://thegraph.com/blog/how-to-become-indexer/) to earn indexing rewards and query fees by serving data on your subgraph and others.
-
-### Should I use a centralized indexing provider?
-
-If you are building in web3, the moment you use a centralized indexing provider, you are giving them control of your dapp and data. The Graph’s decentralized network offers [superior quality of service](https://thegraph.com/blog/qos-the-graph-network/), reliability with unbeatable uptime thanks to node redundancy, significantly [lower costs](/network/benefits/), and keeps you from being hostage at the data layer.
-
-With The Graph Network, your subgraph is public and anyone can query it openly, which increases the usage and network effects of your dapp.
-
-Additionally, Subgraph Studio provides 100,000 free monthly queries on the Free Plan, before payment is needed for additional usage.
-
-Here's a detailed breakdown of the benefits of The Graph over centralized hosting:
+### अपग्रेड Indexer क्वेरीज़ की कीमत कैसे तय करता है?
 
-- **Resilience and Redundancy**: Decentralized systems are inherently more robust and resilient due to their distributed nature. Data isn't stored on a single server or location. Instead, it's served by hundreds of independent Indexers around the globe. This reduces the risk of data loss or service interruptions if one node fails, leading to exceptional uptime (99.99%).
+अपग्रेड में Indexer बाज़ार दर पर क्वेरीज़ की कीमत तय करता है ताकि क्वेरी शुल्क बाज़ार पर कोई प्रभाव न पड़े।
 
-- **Quality of Service**: In addition to the impressive uptime, The Graph Network features a ~106ms median query speed (latency), and higher query success rates compared to hosted alternatives. Read more in [this blog](https://thegraph.com/blog/qos-the-graph-network/).
+### अपग्रेड Indexer कब एक Subgraph का समर्थन करना बंद करेगा?
 
-- **Censorship Resistance**: Centralized systems are targets for censorship, either through regulatory pressures or network attacks. In contrast, the dispersed architecture of decentralized systems makes them much harder to censor, which ensures continuous data availability.
+अपग्रेड Indexer एक Subgraph का समर्थन करता है जब तक कि कम से कम 3 अन्य Indexers सफलतापूर्वक और लगातार किए गए प्रश्नों का उत्तर नहीं देते।
 
-- **Transparency and Trust**: Decentralized systems operate openly, enabling anyone to independently verify the data. This transparency builds trust among network participants because they can verify the system's integrity without relying on a central authority.
+इसके अतिरिक्त, अपग्रेड Indexer एक Subgraph का समर्थन करना बंद कर देता है यदि उसे पिछले 30 दिनों में क्वेरी नहीं किया गया है।
 
-Just as you've chosen your blockchain network for its decentralized nature, security, and transparency, opting for The Graph Network is an extension of those same principles. By aligning your data infrastructure with these values, you ensure a cohesive, resilient, and trust-driven development environment.
+अन्य Indexer को उन सबग्राफ का समर्थन करने के लिए प्रोत्साहित किया जाता है जिनमें निरंतर क्वेरी वॉल्यूम होता है। अपग्रेड Indexer के लिए क्वेरी वॉल्यूम शून्य की ओर बढ़ना चाहिए, क्योंकि इसका आवंटन आकार छोटा होता है, और क्वेरी के लिए अन्य Indexer को प्राथमिकता दी जानी चाहिए।

From e1be1d6f6ebbd7b52285a089d8a4394804c4fcd8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:29 -0500
Subject: [PATCH 1149/1325] New translations sunrise.mdx (Swahili)

---
 website/pages/sw/sunrise.mdx | 79 ++++++++++++++++++++++++++++++++++++
 1 file changed, 79 insertions(+)
 create mode 100644 website/pages/sw/sunrise.mdx

diff --git a/website/pages/sw/sunrise.mdx b/website/pages/sw/sunrise.mdx
new file mode 100644
index 000000000000..14d1444cf8cd
--- /dev/null
+++ b/website/pages/sw/sunrise.mdx
@@ -0,0 +1,79 @@
+---
+title: Post-Sunrise + Upgrading to The Graph Network FAQ
+---
+
+> Note: The Sunrise of Decentralized Data ended June 12th, 2024.
+
+## What was the Sunrise of Decentralized Data?
+
+The Sunrise of Decentralized Data was an initiative spearheaded by Edge & Node. This initiative enabled subgraph developers to upgrade to The Graph’s decentralized network seamlessly.
+
+This plan drew on previous developments from The Graph ecosystem, including an upgrade Indexer to serve queries on newly published subgraphs.
+
+### What happened to the hosted service?
+
+The hosted service query endpoints are no longer available, and developers cannot deploy new subgraphs on the hosted service.
+
+During the upgrade process, owners of hosted service subgraphs could upgrade their subgraphs to The Graph Network. Additionally, developers were able to claim auto-upgraded subgraphs.
+
+### Was Subgraph Studio impacted by this upgrade?
+
+No, Subgraph Studio was not impacted by Sunrise. Subgraphs were immediately available for querying, powered by the upgrade Indexer, which uses the same infrastructure as the hosted service.
+
+### Why were subgraphs published to Arbitrum, did it start indexing a different network?
+
+The Graph Network was initially deployed on Ethereum mainnet but was later moved to Arbitrum One in order to lower gas costs for all users. As a result, all new subgraphs are published to The Graph Network on Arbitrum so that Indexers can support them. Arbitrum is the network that subgraphs are published to, but subgraphs can index any of the [supported networks](/developing/supported-networks/)
+
+## About the Upgrade Indexer
+
+> The upgrade Indexer is currently active.
+
+The upgrade Indexer was implemented to improve the experience of upgrading subgraphs from the hosted service to The Graph Network and support new versions of existing subgraphs that had not yet been indexed.
+
+### What does the upgrade Indexer do?
+
+- It bootstraps chains that have yet to receive indexing rewards on The Graph Network and ensures that an Indexer is available to serve queries as quickly as possible after a subgraph is published.
+- It supports chains that were previously only available on the hosted service. Find a comprehensive list of supported chains [here](/developing/supported-networks/).
+- Indexers that operate an upgrade Indexer do so as a public service to support new subgraphs and additional chains that lack indexing rewards before The Graph Council approves them.
+
+### Why is Edge & Node running the upgrade Indexer?
+
+Edge & Node historically maintained the hosted service and, as a result, already have synced data for hosted service subgraphs.
+
+### What does the upgrade indexer mean for existing Indexers?
+
+Chains previously only supported on the hosted service were made available to developers on The Graph Network without indexing rewards at first.
+
+However, this action unlocked query fees for any interested Indexer and increased the number of subgraphs published on The Graph Network. As a result, Indexers have more opportunities to index and serve these subgraphs in exchange for query fees, even before indexing rewards are enabled for a chain.
+
+The upgrade Indexer also provides the Indexer community with information about the potential demand for subgraphs and new chains on The Graph Network.
+
+### What does this mean for Delegators?
+
+The upgrade Indexer offers a powerful opportunity for Delegators. As it allowed more subgraphs to be upgraded from the hosted service to The Graph Network, Delegators benefit from the increased network activity.
+
+### Did the upgrade Indexer compete with existing Indexers for rewards?
+
+No, the upgrade Indexer only allocates the minimum amount per subgraph and does not collect indexing rewards.
+
+It operates on an “as needed” basis, serving as a fallback until sufficient service quality is achieved by at least three other Indexers in the network for respective chains and subgraphs.
+
+### How does this affect subgraph developers?
+
+Subgraph developers can query their subgraphs on The Graph Network almost immediately after upgrading from the hosted service or [publishing from Subgraph Studio](/publishing/publishing-a-subgraph/), as no lead time was required for indexing. Please note that [creating a subgraph](/developing/creating-a-subgraph) was not impacted by this upgrade.
+
+### How does the upgrade Indexer benefit data consumers?
+
+The upgrade Indexer enables chains on the network that were previously only supported on the hosted service. Therefore, it widens the scope and availability of data that can be queried on the network.
+
+### How does the upgrade Indexer price queries?
+
+The upgrade Indexer prices queries at the market rate to avoid influencing the query fee market.
+
+### When will the upgrade Indexer stop supporting a subgraph?
+
+The upgrade Indexer supports a subgraph until at least 3 other Indexers successfully and consistently serve queries made to it.
+
+Furthermore, the upgrade Indexer stops supporting a subgraph if it has not been queried in the last 30 days.
+
+Other Indexers are incentivized to support subgraphs with ongoing query volume. The query volume to the upgrade Indexer should trend towards zero, as it has a small allocation size, and other Indexers should be chosen for queries ahead of it.

From 2876b365c3b9e97f24c67b80dc511179a26b318a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:39 -0500
Subject: [PATCH 1150/1325] New translations querying-with-python.mdx (Swahili)

---
 .../sw/querying/querying-with-python.mdx      | 56 +++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 website/pages/sw/querying/querying-with-python.mdx

diff --git a/website/pages/sw/querying/querying-with-python.mdx b/website/pages/sw/querying/querying-with-python.mdx
new file mode 100644
index 000000000000..4fb618510070
--- /dev/null
+++ b/website/pages/sw/querying/querying-with-python.mdx
@@ -0,0 +1,56 @@
+---
+title: Query The Graph with Python and Subgrounds
+---
+
+Subgrounds is an intuitive Python library for querying subgraphs, built by [Playgrounds](https://playgrounds.network/). It allows you to directly connect subgraph data to a Python data environment, letting you use libraries like [pandas](https://pandas.pydata.org/) to perform data analysis!
+
+Subgrounds offers a simple Pythonic API for building GraphQL queries, automates tedious workflows such as pagination, and empowers advanced users through controlled schema transformations.
+
+## Getting Started
+
+Subgrounds requires Python 3.10 or higher and is available on [pypi](https://pypi.org/project/subgrounds/).
+
+```bash
+pip install --upgrade subgrounds
+# or
+python -m pip install --upgrade subgrounds
+```
+
+Once installed, you can test out subgrounds with the following query. The following example grabs a subgraph for the Aave v2 protocol and queries the top 5 markets ordered by TVL (Total Value Locked), selects their name and their TVL (in USD) and returns the data as a pandas [DataFrame](https://pandas.pydata.org/pandas-docs/dev/reference/api/pandas.DataFrame.html#pandas.DataFrame).
+
+```python
+from subgrounds import Subgrounds
+
+sg = Subgrounds()
+
+# Load the subgraph
+aave_v2 = sg.load_subgraph(
+    "https://api.thegraph.com/subgraphs/name/messari/aave-v2-ethereum")
+
+# Construct the query
+latest_markets = aave_v2.Query.markets(
+    orderBy=aave_v2.Market.totalValueLockedUSD,
+    orderDirection='desc',
+    first=5,
+)
+# Return query to a dataframe
+sg.query_df([
+    latest_markets.name,
+    latest_markets.totalValueLockedUSD,
+])
+```
+
+## Documentation
+
+Subgrounds is built and maintained by the [Playgrounds](https://playgrounds.network/) team and can be accessed on the [Playgrounds docs](https://docs.playgrounds.network/subgrounds).
+
+Since subgrounds has a large feature set to explore, here are some helpful starting places:
+
+- [Getting Started with Querying](https://docs.playgrounds.network/subgrounds/getting_started/basics/)
+  - A good first step for how to build queries with subgrounds.
+- [Building Synthetic Fields](https://docs.playgrounds.network/subgrounds/getting_started/synthetic_fields/)
+  - A gentle introduction to defining synthetic fields that transform data defined from the schema.
+- [Concurrent Queries](https://docs.playgrounds.network/subgrounds/getting_started/async/)
+  - Learn how to level up your queries by parallelizing them.
+- [Exporting Data to CSVs](https://docs.playgrounds.network/subgrounds/faq/exporting/)
+  - A quick article on how to seemlessly save your data as CSVs for further analysis.

From ee6da3f8d56acb439d8687445a71fdef4543a5fd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:41 -0500
Subject: [PATCH 1151/1325] New translations common-issues.mdx (French)

---
 website/pages/fr/developing/graph-ts/common-issues.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/fr/developing/graph-ts/common-issues.mdx b/website/pages/fr/developing/graph-ts/common-issues.mdx
index 5b99efa8f493..b50b0404002a 100644
--- a/website/pages/fr/developing/graph-ts/common-issues.mdx
+++ b/website/pages/fr/developing/graph-ts/common-issues.mdx
@@ -2,7 +2,7 @@
 title: Common AssemblyScript Issues
 ---
 
-There are certain [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) issues that are common to run into during subgraph development. They range in debug difficulty, however, being aware of them may help. The following is a non-exhaustive list of these issues:
+Il existe certains problèmes courants avec [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) lors du développement de subgraph. Ces problèmes varient en termes de difficulté de débogage, mais les connaître peut être utile. Voici une liste non exhaustive de ces problèmes :
 
-- `Private` class variables are not enforced in [AssembyScript](https://www.assemblyscript.org/status.html#language-features). There is no way to protect class variables from being directly changed from the class object.
-- Scope is not inherited into [closure functions](https://www.assemblyscript.org/status.html#on-closures), i.e. variables declared outside of closure functions cannot be used. Explanation in [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s).
+- Les variables de classe `Private` ne sont pas appliquées dans [AssembyScript] (https://www.assemblyscript.org/status.html#language-features). Il n'y a aucun moyen de protéger les variables de classe d'une modification directe à partir de l'objet de la classe.
+- La portée n'est pas héritée dans les [fonctions de fermeture] (https://www.assemblyscript.org/status.html#on-closures), c'est-à-dire que les variables déclarées en dehors des fonctions de fermeture ne peuvent pas être utilisées. Explication dans les [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s).

From 3678c4d64bf5310028e1155e08511e0c8cd71dcb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:50 -0500
Subject: [PATCH 1152/1325] New translations common-issues.mdx (Swahili)

---
 website/pages/sw/developing/graph-ts/common-issues.mdx | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 website/pages/sw/developing/graph-ts/common-issues.mdx

diff --git a/website/pages/sw/developing/graph-ts/common-issues.mdx b/website/pages/sw/developing/graph-ts/common-issues.mdx
new file mode 100644
index 000000000000..5b99efa8f493
--- /dev/null
+++ b/website/pages/sw/developing/graph-ts/common-issues.mdx
@@ -0,0 +1,8 @@
+---
+title: Common AssemblyScript Issues
+---
+
+There are certain [AssemblyScript](https://github.com/AssemblyScript/assemblyscript) issues that are common to run into during subgraph development. They range in debug difficulty, however, being aware of them may help. The following is a non-exhaustive list of these issues:
+
+- `Private` class variables are not enforced in [AssembyScript](https://www.assemblyscript.org/status.html#language-features). There is no way to protect class variables from being directly changed from the class object.
+- Scope is not inherited into [closure functions](https://www.assemblyscript.org/status.html#on-closures), i.e. variables declared outside of closure functions cannot be used. Explanation in [Developer Highlights #3](https://www.youtube.com/watch?v=1-8AW-lVfrA&t=3243s).

From 2174c2c551f640f682ec853b29d3c17ed9b4896d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:52 -0500
Subject: [PATCH 1153/1325] New translations supported-networks.json (French)

---
 website/pages/fr/developing/supported-networks.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/fr/developing/supported-networks.json b/website/pages/fr/developing/supported-networks.json
index 3cef93eaa809..dd6bbee71dc6 100644
--- a/website/pages/fr/developing/supported-networks.json
+++ b/website/pages/fr/developing/supported-networks.json
@@ -5,5 +5,5 @@
   "hostedService": "Service hébergé",
   "subgraphStudio": "Subgraph Studio",
   "decentralizedNetwork": "Réseau décentralisé",
-  "integrationType": "Integration Type"
+  "integrationType": "Type d'intégration"
 }

From 8d22d9411c5246e6d5e1b5eb9ede01590e041572 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:54:57 -0500
Subject: [PATCH 1154/1325] New translations supported-networks.json (Russian)

---
 website/pages/ru/developing/supported-networks.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ru/developing/supported-networks.json b/website/pages/ru/developing/supported-networks.json
index c51feaf71922..452617529078 100644
--- a/website/pages/ru/developing/supported-networks.json
+++ b/website/pages/ru/developing/supported-networks.json
@@ -5,5 +5,5 @@
   "hostedService": "Hosted Service",
   "subgraphStudio": "Subgraph Studio",
   "decentralizedNetwork": "Децентрализованная сеть",
-  "integrationType": "Integration Type"
+  "integrationType": "Тип интеграции"
 }

From 39d68be502a611fb5d68c2962c0edf37de86e00c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:00 -0500
Subject: [PATCH 1155/1325] New translations supported-networks.json (Urdu
 (Pakistan))

---
 website/pages/ur/developing/supported-networks.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ur/developing/supported-networks.json b/website/pages/ur/developing/supported-networks.json
index 49b9ac4de457..1db47456c314 100644
--- a/website/pages/ur/developing/supported-networks.json
+++ b/website/pages/ur/developing/supported-networks.json
@@ -2,7 +2,7 @@
   "network": "نیٹ ورک",
   "cliName": "CLI Name",
   "chainId": "Chain ID",
-  "hostedService": "ہوسٹڈ سروس",
+  "hostedService": "Hosted Service",
   "subgraphStudio": "سب گراف سٹوڈیو",
   "decentralizedNetwork": "Decentralized Network",
   "integrationType": "Integration Type"

From cdf238634f8f74d51fd82558bd6c0d888c407e87 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:03 -0500
Subject: [PATCH 1156/1325] New translations supported-networks.json (Swahili)

---
 website/pages/sw/developing/supported-networks.json | 9 +++++++++
 1 file changed, 9 insertions(+)
 create mode 100644 website/pages/sw/developing/supported-networks.json

diff --git a/website/pages/sw/developing/supported-networks.json b/website/pages/sw/developing/supported-networks.json
new file mode 100644
index 000000000000..9ae5a4b5aae8
--- /dev/null
+++ b/website/pages/sw/developing/supported-networks.json
@@ -0,0 +1,9 @@
+{
+  "network": "Network",
+  "cliName": "CLI Name",
+  "chainId": "Chain ID",
+  "hostedService": "Hosted Service",
+  "subgraphStudio": "Subgraph Studio",
+  "decentralizedNetwork": "Decentralized Network",
+  "integrationType": "Integration Type"
+}

From e168ef78805fff627aded5cbdd5ee7bf6426672b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:15 -0500
Subject: [PATCH 1157/1325] New translations
 querying-by-subgraph-id-vs-deployment-id.mdx (Swahili)

---
 ...erying-by-subgraph-id-vs-deployment-id.mdx | 27 +++++++++++++++++++
 1 file changed, 27 insertions(+)
 create mode 100644 website/pages/sw/querying/querying-by-subgraph-id-vs-deployment-id.mdx

diff --git a/website/pages/sw/querying/querying-by-subgraph-id-vs-deployment-id.mdx b/website/pages/sw/querying/querying-by-subgraph-id-vs-deployment-id.mdx
new file mode 100644
index 000000000000..103e470e14da
--- /dev/null
+++ b/website/pages/sw/querying/querying-by-subgraph-id-vs-deployment-id.mdx
@@ -0,0 +1,27 @@
+---
+title: Subgraph ID vs Deployment ID
+---
+
+A subgraph is identified by a Subgraph ID, and each version of the subgraph is identified by a Deployment ID.
+
+When querying a subgraph, either ID can be used, though it is generally suggested that the Deployment ID is used due to its ability to specify a specific version of a subgraph.
+
+Here are some key differences between the two IDs: ![](/img/subgraph-id-vs-deployment-id.png)
+
+## Deployment ID
+
+The Deployment ID is the IPFS hash of the compiled manifest file, which refers to other files on IPFS instead of relative URLs on the computer. For example, the compiled manifest can be accessed via: `https://api.thegraph.com/ipfs/api/v0/cat?arg=QmQKXcNQQRdUvNRMGJiE2idoTu9fo5F5MRtKztH4WyKxED`. To change the Deployment ID, one can simply update the manifest file, such as modifying the description field as described in the [subgraph manifest documentation](https://github.com/graphprotocol/graph-node/blob/master/docs/subgraph-manifest.md#13-top-level-api).
+
+When queries are made using a subgraph's Deployment ID, we are specifying a version of that subgraph to query. Using the Deployment ID to query a specific subgraph version results in a more sophisticated and robust setup as there is full control over the subgraph version being queried. However, this results in the need of updating the query code manually every time a new version of the subgraph is published.
+
+Example endpoint that uses Deployment ID:
+
+`https://gateway-arbitrum.network.thegraph.com/api/[api-key]/deployments/id/QmfYaVdSSekUeK6expfm47tP8adg3NNdEGnVExqswsSwaB`
+
+## Subgraph ID
+
+The Subgraph ID is a unique identifier for a subgraph. It remains constant across all versions of a subgraph. It is recommended to use the Subgraph ID to query the latest version of a subgraph, although there are some caveats.
+
+Be aware that querying using Subgraph ID may result in queries being responded to by an older version of the subgraph due to the new version needing time to sync. Also, new versions could introduce breaking schema changes.
+
+Example endpoint that uses Subgraph ID: `https://gateway-arbitrum.network.thegraph.com/api/[api-key]/subgraphs/id/FL3ePDCBbShPvfRJTaSCNnehiqxsPHzpLud6CpbHoeKW`

From 9d59c89295a8975b2cc97a44b0ddf35365faab21 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:17 -0500
Subject: [PATCH 1158/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Czech)

---
 ...pi-keys-using-nextjs-server-components.mdx | 56 +++++++++----------
 1 file changed, 28 insertions(+), 28 deletions(-)

diff --git a/website/pages/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index 6864eef796ff..12a504471cb7 100644
--- a/website/pages/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/cs/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -1,48 +1,48 @@
 ---
-title: How to Secure API Keys Using Next.js Server Components
+title: Jak zabezpečit klíče API pomocí komponent serveru Next.js
 ---
 
 ## Přehled
 
-We can use [Next.js server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) to properly secure our API key from exposure in the frontend of our dapp. To further increase our API key security, we can also [restrict our API key to certain subgraphs or domains in Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
+K řádnému zabezpečení našeho klíče API před odhalením ve frontendu naší aplikace můžeme použít [komponenty serveru Next.js](https://nextjs.org/docs/app/building-your-application/rendering/server-components). Pro další zvýšení zabezpečení našeho klíče API můžeme také [omezit náš klíč API na určité podgrafy nebo domény v Podgraf Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
 
-In this cookbook, we will go over how to create a Next.js server component that queries a subgraph while also hiding the API key from the frontend.
+V této kuchařce probereme, jak vytvořit serverovou komponentu Next.js, která se dotazuje na podgraf a zároveň skrývá klíč API před frontend.
 
-### Caveats
+### Upozornění
 
-- Next.js server components do not protect API keys from being drained using denial of service attacks.
-- The Graph Network gateways have denial of service detection and mitigation strategies in place, however using server components may weaken these protections.
-- Next.js server components introduce centralization risks as the server can go down.
+- Součásti serveru Next.js nechrání klíče API před odčerpáním pomocí útoků typu odepření služby.
+- Brány Graf síť mají zavedené strategie detekce a zmírňování odepření služby, avšak použití serverových komponent může tyto ochrany oslabit.
+- Server komponenty Next.js přinášejí rizika centralizace, protože může dojít k výpadku serveru.
 
-### Why It's Needed
+### Proč je to důležité
 
-In a standard React application, API keys included in the frontend code can be exposed to the client-side, posing a security risk. While `.env` files are commonly used, they don't fully protect the keys since React's code is executed on the client side, exposing the API key in the headers. Next.js Server Components address this issue by handling sensitive operations server-side.
+Ve standardní aplikaci React mohou být klíče API obsažené v kódu frontendu vystaveny na straně klienta, což představuje bezpečnostní riziko. Soubory `.env` se sice běžně používají, ale plně klíče nechrání, protože kód Reactu se spouští na straně klienta a vystavuje klíč API v hlavičkách. Serverové komponenty Next.js tento problém řeší tím, že citlivé operace zpracovávají na straně serveru.
 
-### Using client-side rendering to query a subgraph
+### Použití vykreslování na straně klienta k dotazování podgrafu
 
 ![Client-side rendering](/img/api-key-client-side-rendering.png)
 
 ### Požadavky
 
-- An API key from [Subgraph Studio](https://thegraph.com/studio)
-- Basic knowledge of Next.js and React.
-- An existing Next.js project that uses the [App Router](https://nextjs.org/docs/app).
+- Klíč API od [Subgraph Studio](https://thegraph.com/studio)
+- Základní znalosti Next.js a React.
+- Existující projekt Next.js, který používá [App Router](https://nextjs.org/docs/app).
 
-## Step-by-Step Cookbook
+## Kuchařka krok za krokem
 
-### Step 1: Set Up Environment Variables
+### Krok 1: Nastavení proměnných prostředí
 
-1. In our Next.js project root, create a `.env.local` file.
-2. Add our API key: `API_KEY=<api_key_here>`.
+1. V kořeni našeho projektu Next.js vytvořte soubor `.env.local`.
+2. Přidejte náš klíč API: `API_KEY=<api_key_here>`.
 
-### Step 2: Create a Server Component
+### Krok 2: Vytvoření součásti serveru
 
-1. In our `components` directory, create a new file, `ServerComponent.js`.
-2. Use the provided example code to set up the server component.
+1. V adresáři `components` vytvořte nový soubor `ServerComponent.js`.
+2. K nastavení komponenty serveru použijte přiložený ukázkový kód.
 
-### Step 3: Implement Server-Side API Request
+### Krok 3: Implementace požadavku API na straně serveru
 
-In `ServerComponent.js`, add the following code:
+Do souboru `ServerComponent.js` přidejte následující kód:
 
 ```javascript
 const API_KEY = process.env.API_KEY
@@ -95,10 +95,10 @@ export default async function ServerComponent() {
 }
 ```
 
-### Step 4: Use the Server Component
+### Krok 4: Použití komponenty serveru
 
-1. In our page file (e.g., `pages/index.js`), import `ServerComponent`.
-2. Render the component:
+1. V našem souboru stránky (např. `pages/index.js`) importujte `ServerComponent`.
+2. Vykreslení komponenty:
 
 ```javascript
 import ServerComponent from './components/ServerComponent'
@@ -112,12 +112,12 @@ export default function Home() {
 }
 ```
 
-### Step 5: Run and Test Our Dapp
+### Krok 5: Spusťte a otestujte náš Dapp
 
-Start our Next.js application using `npm run dev`. Verify that the server component is fetching data without exposing the API key.
+Spusťte naši aplikaci Next.js pomocí `npm run dev`. Ověřte, že serverová komponenta načítá data bez vystavení klíče API.
 
 ![Server-side rendering](/img/api-key-server-side-rendering.png)
 
 ### Závěr
 
-By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/cookbook/upgrading-a-subgraph/#securing-your-api-key) to increase your API key security even further.
+Použitím serverových komponent Next.js jsme efektivně skryli klíč API před klientskou stranou, čímž jsme zvýšili bezpečnost naší aplikace. Tato metoda zajišťuje, že citlivé operace jsou zpracovávány na straně serveru, mimo potenciální zranitelnosti na straně klienta. Nakonec nezapomeňte prozkoumat [další opatření pro zabezpečení klíče API](/cookbook/upgrading-a-subgraph/#securing-your-api-key), abyste ještě více zvýšili zabezpečení svého klíče API.

From 23dcd13d06fed7d3f1c6a1aea3b03b01ee50becd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:21 -0500
Subject: [PATCH 1159/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Portuguese)

---
 .../how-to-secure-api-keys-using-nextjs-server-components.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index 03b424569c4c..5bb8b017c0bc 100644
--- a/website/pages/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/pt/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -2,7 +2,7 @@
 title: Como Proteger Chaves de API com Componentes do Servidor Next.js
 ---
 
-## Visão Geral
+## Visão geral
 
 Podemos proteger a nossa chave API no frontend do nosso dApp com [componentes do servidor Next.js](https://nextjs.org/docs/app/building-your-application/rendering/server-components). Para ainda mais segurança, também podemos [restringir a nossa chave API a certos domínios ou subgraphs no Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
 

From 5853da46605b7fda404459da1b360b32391d51ca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:22 -0500
Subject: [PATCH 1160/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Turkish)

---
 .../how-to-secure-api-keys-using-nextjs-server-components.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index e85f3e13acef..b3eff9269cea 100644
--- a/website/pages/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/tr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -2,7 +2,7 @@
 title: How to Secure API Keys Using Next.js Server Components
 ---
 
-## Overview
+## Genel Bakış
 
 We can use [Next.js server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) to properly secure our API key from exposure in the frontend of our dapp. To further increase our API key security, we can also [restrict our API key to certain subgraphs or domains in Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
 

From 0b4b3fea3127f2e53378a3c1e4cd74a285fee8b6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:24 -0500
Subject: [PATCH 1161/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Ukrainian)

---
 .../how-to-secure-api-keys-using-nextjs-server-components.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index 86af97bcd350..e37d83acbe78 100644
--- a/website/pages/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/uk/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -2,7 +2,7 @@
 title: How to Secure API Keys Using Next.js Server Components
 ---
 
-## Короткий огляд
+## Overview
 
 We can use [Next.js server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) to properly secure our API key from exposure in the frontend of our dapp. To further increase our API key security, we can also [restrict our API key to certain subgraphs or domains in Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
 

From e544a1349ceda9b6aab1c2b793ffdc4475e232a3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:26 -0500
Subject: [PATCH 1162/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Marathi)

---
 .../how-to-secure-api-keys-using-nextjs-server-components.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index 9df73635859c..d4e672df4fdb 100644
--- a/website/pages/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/mr/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -2,7 +2,7 @@
 title: How to Secure API Keys Using Next.js Server Components
 ---
 
-## सारांश
+## सविश्लेषण
 
 We can use [Next.js server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) to properly secure our API key from exposure in the frontend of our dapp. To further increase our API key security, we can also [restrict our API key to certain subgraphs or domains in Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
 

From b9b6294b8f9b7a7c5cf9198b2cf0f668a81993de Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:27 -0500
Subject: [PATCH 1163/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Hindi)

---
 ...pi-keys-using-nextjs-server-components.mdx | 58 +++++++++----------
 1 file changed, 29 insertions(+), 29 deletions(-)

diff --git a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index d89037d63cc5..f8b39d9b664f 100644
--- a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -1,48 +1,48 @@
 ---
-title: How to Secure API Keys Using Next.js Server Components
+title: कैसे सुरक्षित करें API Keys का उपयोग करके Next.js Server Components
 ---
 
 ## अवलोकन
 
-We can use [Next.js server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) to properly secure our API key from exposure in the frontend of our dapp. To further increase our API key security, we can also [restrict our API key to certain subgraphs or domains in Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
+हम Next.js server components(https://nextjs.org/docs/app/building-your-application/rendering/server-components) का उपयोग करके अपने dapp के frontend में API key को exposure से सुरक्षित रख सकते हैं। API key की सुरक्षा को और बढ़ाने के लिए, हम Subgraph Studio में अपनी API key को कुछ subgraphs या domains तक सीमित कर सकते हैं(/cookbook/upgrading-a-subgraph/#securing-your-api-key)
 
-In this cookbook, we will go over how to create a Next.js server component that queries a subgraph while also hiding the API key from the frontend.
+इस cookbook में, हम यह समझेंगे कि कैसे एक Next.js server component बनाया जाए जो subgraph से query करता है, साथ ही API key को frontend से छिपाने का तरीका भी शामिल है।
 
-### Caveats
+### चेतावनी
 
-- Next.js server components do not protect API keys from being drained using denial of service attacks.
-- The Graph Network gateways have denial of service detection and mitigation strategies in place, however using server components may weaken these protections.
-- Next.js server components introduce centralization risks as the server can go down.
+- Next.js सर्वर घटक डिनायल ऑफ़ सर्विस अटैक का उपयोग करके API कुंजियों को समाप्त होने से सुरक्षित नहीं कर सकते।
+- The Graph Network gateways में सेवा को बाधित करने के हमलों का पता लगाने और उन्हें रोकने की रणनीतियाँ मौजूद हैं, हालांकि server components का उपयोग करने से ये सुरक्षा कमजोर हो सकती है।
+- Next.js server components केंद्रीकरण के जोखिम प्रस्तुत करते हैं क्योंकि सर्वर बंद हो सकता है।
 
-### Why It's Needed
+### यह क्यों आवश्यक है
 
-In a standard React application, API keys included in the frontend code can be exposed to the client-side, posing a security risk. While `.env` files are commonly used, they don't fully protect the keys since React's code is executed on the client side, exposing the API key in the headers. Next.js Server Components address this issue by handling sensitive operations server-side.
+एक मानक React एप्लिकेशन में, फ्रंटेंड कोड में शामिल API कुंजियाँ क्लाइंट-साइड पर उजागर हो सकती हैं, जिससे सुरक्षा का जोखिम बढ़ता है। जबकि.env फ़ाइलें सामान्यत: उपयोग की जाती हैं, ये कुंजियों की पूरी सुरक्षा नहीं करतीं क्योंकि React का कोड क्लाइंट साइड पर निष्पादित होता है, जो API कुंजी को हेडर में उजागर करता है। Next.js सर्वर घटक इस मुद्दे का समाधान करते हैं द्वारा संवेदनशील कार्यों को सर्वर-साइड पर संभालना।
 
-### Using client-side rendering to query a subgraph
+### क्लाइंट-साइड रेंडरिंग का उपयोग करके एक subgraph को क्वेरी करना
 
 ![Client-side rendering](/img/api-key-client-side-rendering.png)
 
 ### आवश्यक शर्तें
 
-- An API key from [Subgraph Studio](https://thegraph.com/studio)
-- Basic knowledge of Next.js and React.
-- An existing Next.js project that uses the [App Router](https://nextjs.org/docs/app).
+-  [Subgraph Studio](https://thegraph.com/studio) से एक API कुंजी
+- Next.js और React का बुनियादी ज्ञान
+- एक मौजूदा Next.js प्रोजेक्ट जो App Router (https://nextjs.org/docs/app). का उपयोग करता है।
 
-## Step-by-Step Cookbook
+## स्टेप-बाय-स्टेप कुकबुक
 
-### Step 1: Set Up Environment Variables
+### चरण 1: पर्यावरण चर सेट करें
 
-1. In our Next.js project root, create a `.env.local` file.
-2. Add our API key: `API_KEY=<api_key_here>`.
+1. हमारे Next.js प्रोजेक्ट की जड़ में, एक.env.local फ़ाइल बनाएं।
+2. हमारा API कुंजी जोड़ें: API_KEY=<api_key_here>.
 
-### Step 2: Create a Server Component
+### चरण 2: एक सर्वर घटक बनाएं
 
-1. In our `components` directory, create a new file, `ServerComponent.js`.
-2. Use the provided example code to set up the server component.
+1. हमारे components निर्देशिका में, एक नया फ़ाइल बनाएं, ServerComponent.js।
+2. प्रदान किए गए उदाहरण कोड का उपयोग करके सर्वर घटक सेट करें।
 
-### Step 3: Implement Server-Side API Request
+### चरण 3: सर्वर-साइड API अनुरोध को लागू करें
 
-In `ServerComponent.js`, add the following code:
+ServerComponent.js में, निम्नलिखित कोड जोड़ें:
 
 ```javascript
 const API_KEY = process.env.API_KEY
@@ -95,10 +95,10 @@ export default async function ServerComponent() {
 }
 ```
 
-### Step 4: Use the Server Component
+### चरण 4: सर्वर घटक का उपयोग करें
 
-1. In our page file (e.g., `pages/index.js`), import `ServerComponent`.
-2. Render the component:
+1. हमारी पृष्ठ फ़ाइल (जैसे, pages/index.js) में ServerComponent आयात करें।
+2. कंपोनेंट को रेंडर करें:
 
 ```javascript
 import ServerComponent from './components/ServerComponent'
@@ -112,12 +112,12 @@ export default function Home() {
 }
 ```
 
-### Step 5: Run and Test Our Dapp
+### चरण 5: हमारा Dapp चलाएँ और परीक्षण करें
 
-Start our Next.js application using `npm run dev`. Verify that the server component is fetching data without exposing the API key.
+अपने Next.js एप्लिकेशन को npm run dev का उपयोग करके प्रारंभ करें। सत्यापित करें कि सर्वर कंपोनेंट डेटा प्राप्त कर रहा है बिना API कुंजी को उजागर किए।
 
 ![Server-side rendering](/img/api-key-server-side-rendering.png)
 
-### Conclusion
+### निष्कर्ष
 
-By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/cookbook/upgrading-a-subgraph/#securing-your-api-key) to increase your API key security even further.
+Next.js Server Components का उपयोग करके, हमने प्रभावी रूप से API कुंजी को क्लाइंट-साइड से छिपा दिया है, जिससे हमारे एप्लिकेशन की सुरक्षा में वृद्धि हुई है। यह विधि सुनिश्चित करती है कि संवेदनशील संचालन सर्वर-साइड पर, संभावित क्लाइंट-साइड कमजोरियों से दूर, संभाले जाते हैं। अंत में, अपने API कुंजी की सुरक्षा बढ़ाने के लिए other API key security measures (/cookbook/upgrading-a-subgraph/#securing-your-api-key) का अन्वेषण करना न भूलें।

From d86656f5ba390ac7eb640b1a38e35f1b8e3ed88a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:28 -0500
Subject: [PATCH 1164/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Swahili)

---
 ...pi-keys-using-nextjs-server-components.mdx | 123 ++++++++++++++++++
 1 file changed, 123 insertions(+)
 create mode 100644 website/pages/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx

diff --git a/website/pages/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
new file mode 100644
index 000000000000..e37d83acbe78
--- /dev/null
+++ b/website/pages/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -0,0 +1,123 @@
+---
+title: How to Secure API Keys Using Next.js Server Components
+---
+
+## Overview
+
+We can use [Next.js server components](https://nextjs.org/docs/app/building-your-application/rendering/server-components) to properly secure our API key from exposure in the frontend of our dapp. To further increase our API key security, we can also [restrict our API key to certain subgraphs or domains in Subgraph Studio](/cookbook/upgrading-a-subgraph/#securing-your-api-key).
+
+In this cookbook, we will go over how to create a Next.js server component that queries a subgraph while also hiding the API key from the frontend.
+
+### Caveats
+
+- Next.js server components do not protect API keys from being drained using denial of service attacks.
+- The Graph Network gateways have denial of service detection and mitigation strategies in place, however using server components may weaken these protections.
+- Next.js server components introduce centralization risks as the server can go down.
+
+### Why It's Needed
+
+In a standard React application, API keys included in the frontend code can be exposed to the client-side, posing a security risk. While `.env` files are commonly used, they don't fully protect the keys since React's code is executed on the client side, exposing the API key in the headers. Next.js Server Components address this issue by handling sensitive operations server-side.
+
+### Using client-side rendering to query a subgraph
+
+![Client-side rendering](/img/api-key-client-side-rendering.png)
+
+### Prerequisites
+
+- An API key from [Subgraph Studio](https://thegraph.com/studio)
+- Basic knowledge of Next.js and React.
+- An existing Next.js project that uses the [App Router](https://nextjs.org/docs/app).
+
+## Step-by-Step Cookbook
+
+### Step 1: Set Up Environment Variables
+
+1. In our Next.js project root, create a `.env.local` file.
+2. Add our API key: `API_KEY=<api_key_here>`.
+
+### Step 2: Create a Server Component
+
+1. In our `components` directory, create a new file, `ServerComponent.js`.
+2. Use the provided example code to set up the server component.
+
+### Step 3: Implement Server-Side API Request
+
+In `ServerComponent.js`, add the following code:
+
+```javascript
+const API_KEY = process.env.API_KEY
+
+export default async function ServerComponent() {
+  const response = await fetch(
+    `https://gateway-arbitrum.network.thegraph.com/api/${API_KEY}/subgraphs/id/HUZDsRpEVP2AvzDCyzDHtdc64dyDxx8FQjzsmqSg4H3B`,
+    {
+      method: 'POST',
+      headers: {
+        'Content-Type': 'application/json',
+      },
+      body: JSON.stringify({
+        query: /* GraphQL */ `
+          {
+            factories(first: 5) {
+              id
+              poolCount
+              txCount
+              totalVolumeUSD
+            }
+          }
+        `,
+      }),
+    },
+  )
+
+  const responseData = await response.json()
+  const data = responseData.data
+
+  return (
+    <div>
+      <h1>Server Component</h1>
+      {data ? (
+        <ul>
+          {data.factories.map((factory) => (
+            <li key={factory.id}>
+              <p>ID: {factory.id}</p>
+              <p>Pool Count: {factory.poolCount}</p>
+              <p>Transaction Count: {factory.txCount}</p>
+              <p>Total Volume USD: {factory.totalVolumeUSD}</p>
+            </li>
+          ))}
+        </ul>
+      ) : (
+        <p>Loading data...</p>
+      )}
+    </div>
+  )
+}
+```
+
+### Step 4: Use the Server Component
+
+1. In our page file (e.g., `pages/index.js`), import `ServerComponent`.
+2. Render the component:
+
+```javascript
+import ServerComponent from './components/ServerComponent'
+
+export default function Home() {
+  return (
+    <main>
+      <ServerComponent />
+    </main>
+  )
+}
+```
+
+### Step 5: Run and Test Our Dapp
+
+Start our Next.js application using `npm run dev`. Verify that the server component is fetching data without exposing the API key.
+
+![Server-side rendering](/img/api-key-server-side-rendering.png)
+
+### Conclusion
+
+By utilizing Next.js Server Components, we've effectively hidden the API key from the client-side, enhancing the security of our application. This method ensures that sensitive operations are handled server-side, away from potential client-side vulnerabilities. Finally, be sure to explore [other API key security measures](/cookbook/upgrading-a-subgraph/#securing-your-api-key) to increase your API key security even further.

From b97bff540636ae202d9829a8a45ac9304731eff4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:35 -0500
Subject: [PATCH 1165/1325] New translations contracts.mdx (Russian)

---
 website/pages/ru/network/contracts.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ru/network/contracts.mdx b/website/pages/ru/network/contracts.mdx
index 6abd80577ced..6030fdf8e4e8 100644
--- a/website/pages/ru/network/contracts.mdx
+++ b/website/pages/ru/network/contracts.mdx
@@ -6,7 +6,7 @@ import { ProtocolContractsTable } from '@/src/contracts'
 
 Below are the deployed contracts which power The Graph Network. Visit the official [contracts repository](https://github.com/graphprotocol/contracts) to learn more.
 
-## Arbitrum
+## Арбитрум
 
 This is the principal deployment of The Graph Network.
 

From 9575080c9069ad440362cee9cf5357b525ba9f8b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:40 -0500
Subject: [PATCH 1166/1325] New translations contracts.mdx (Swahili)

---
 website/pages/sw/network/contracts.mdx | 29 ++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 website/pages/sw/network/contracts.mdx

diff --git a/website/pages/sw/network/contracts.mdx b/website/pages/sw/network/contracts.mdx
new file mode 100644
index 000000000000..6abd80577ced
--- /dev/null
+++ b/website/pages/sw/network/contracts.mdx
@@ -0,0 +1,29 @@
+---
+title: Protocol Contracts
+---
+
+import { ProtocolContractsTable } from '@/src/contracts'
+
+Below are the deployed contracts which power The Graph Network. Visit the official [contracts repository](https://github.com/graphprotocol/contracts) to learn more.
+
+## Arbitrum
+
+This is the principal deployment of The Graph Network.
+
+<ProtocolContractsTable networkId={42161} />
+
+## Mainnet
+
+This was the original deployment of The Graph Network. [Learn more](/arbitrum/arbitrum-faq) about The Graph's scaling with Arbitrum.
+
+<ProtocolContractsTable networkId={1} />
+
+## Arbitrum Sepolia
+
+This is the primary testnet for The Graph Network. Testnet is predominantly used by core developers and ecosystem participants for testing purposes. There are no guarantees of service or availability on The Graph's testnets.
+
+<ProtocolContractsTable networkId={421614} />
+
+## Sepolia
+
+<ProtocolContractsTable networkId={11155111} />

From 78e65f0937af967fed267c9e987488754f3b1b28 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:41 -0500
Subject: [PATCH 1167/1325] New translations supported-network-requirements.mdx
 (Romanian)

---
 .../ro/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/ro/supported-network-requirements.mdx b/website/pages/ro/supported-network-requirements.mdx
index df15ef48d762..afbf755c0a5a 100644
--- a/website/pages/ro/supported-network-requirements.mdx
+++ b/website/pages/ro/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From f96af54035b7ebc77c2bf83870b36a95ec7f3ff4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:42 -0500
Subject: [PATCH 1168/1325] New translations supported-network-requirements.mdx
 (French)

---
 .../fr/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/fr/supported-network-requirements.mdx b/website/pages/fr/supported-network-requirements.mdx
index 40d53ab2c69b..8df2bb4bc660 100644
--- a/website/pages/fr/supported-network-requirements.mdx
+++ b/website/pages/fr/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Réseau | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Réseau    | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 6393123420142d61b6095286bcd140cca285474d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:43 -0500
Subject: [PATCH 1169/1325] New translations supported-network-requirements.mdx
 (Spanish)

---
 .../es/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/es/supported-network-requirements.mdx b/website/pages/es/supported-network-requirements.mdx
index dfebec344880..c06461d981d6 100644
--- a/website/pages/es/supported-network-requirements.mdx
+++ b/website/pages/es/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Red | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Red       | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From ea71a6aa413f7f5f7202526047e53060728fe95a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:44 -0500
Subject: [PATCH 1170/1325] New translations supported-network-requirements.mdx
 (Arabic)

---
 .../ar/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/ar/supported-network-requirements.mdx b/website/pages/ar/supported-network-requirements.mdx
index 9c820d055399..811fb2a8cec7 100644
--- a/website/pages/ar/supported-network-requirements.mdx
+++ b/website/pages/ar/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| بوليجون | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| بوليجون   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 796eeec211f50a5195a51df43f8e1b8405a4448f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:45 -0500
Subject: [PATCH 1171/1325] New translations supported-network-requirements.mdx
 (Czech)

---
 .../cs/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/cs/supported-network-requirements.mdx b/website/pages/cs/supported-network-requirements.mdx
index a81118cec231..efbee1c17750 100644
--- a/website/pages/cs/supported-network-requirements.mdx
+++ b/website/pages/cs/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Síť | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Síť       | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From c5e18b94d3759ee69804a859ab0c3fbf4973075d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:46 -0500
Subject: [PATCH 1172/1325] New translations supported-network-requirements.mdx
 (German)

---
 .../de/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/de/supported-network-requirements.mdx b/website/pages/de/supported-network-requirements.mdx
index df15ef48d762..afbf755c0a5a 100644
--- a/website/pages/de/supported-network-requirements.mdx
+++ b/website/pages/de/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From fc02156a99ce8f81081ae2e895f3fc936dda3901 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:47 -0500
Subject: [PATCH 1173/1325] New translations supported-network-requirements.mdx
 (Italian)

---
 .../it/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/it/supported-network-requirements.mdx b/website/pages/it/supported-network-requirements.mdx
index 7eed955d1013..88be77e74cc8 100644
--- a/website/pages/it/supported-network-requirements.mdx
+++ b/website/pages/it/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| La rete | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| La rete   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 9c41f296372d96b38f2ee17c616a67836d306b61 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:48 -0500
Subject: [PATCH 1174/1325] New translations supported-network-requirements.mdx
 (Japanese)

---
 .../ja/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/ja/supported-network-requirements.mdx b/website/pages/ja/supported-network-requirements.mdx
index 6aa0c0caa16f..99ceda419e06 100644
--- a/website/pages/ja/supported-network-requirements.mdx
+++ b/website/pages/ja/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| ネットワーク | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| ネットワーク    | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From ff20054222cc5808af02fbc98e2926650ee865f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:49 -0500
Subject: [PATCH 1175/1325] New translations supported-network-requirements.mdx
 (Korean)

---
 .../ko/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/ko/supported-network-requirements.mdx b/website/pages/ko/supported-network-requirements.mdx
index df15ef48d762..afbf755c0a5a 100644
--- a/website/pages/ko/supported-network-requirements.mdx
+++ b/website/pages/ko/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From dfbd39b47eb83a884718210eea212acfaa0317d3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:50 -0500
Subject: [PATCH 1176/1325] New translations supported-network-requirements.mdx
 (Dutch)

---
 .../nl/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/nl/supported-network-requirements.mdx b/website/pages/nl/supported-network-requirements.mdx
index 9bfbc8d0fefd..4a5d2fa8f364 100644
--- a/website/pages/nl/supported-network-requirements.mdx
+++ b/website/pages/nl/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Netwerk | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Netwerk   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 878af7bb0a04c2ccd3019bc39c4a0f93ef8e0fec Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:51 -0500
Subject: [PATCH 1177/1325] New translations supported-network-requirements.mdx
 (Polish)

---
 .../pl/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/pl/supported-network-requirements.mdx b/website/pages/pl/supported-network-requirements.mdx
index df15ef48d762..afbf755c0a5a 100644
--- a/website/pages/pl/supported-network-requirements.mdx
+++ b/website/pages/pl/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 7f5607116e010d8df857dad6f23131960f2c8578 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:52 -0500
Subject: [PATCH 1178/1325] New translations supported-network-requirements.mdx
 (Portuguese)

---
 .../pt/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/pt/supported-network-requirements.mdx b/website/pages/pt/supported-network-requirements.mdx
index d678f0534f01..c1bd4433f1d7 100644
--- a/website/pages/pt/supported-network-requirements.mdx
+++ b/website/pages/pt/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Requisitos de Redes Apoiadas
 ---
 
-| Rede | Guias | Requisitos de sistema | Recompensas de Indexação |
-| --- | --- | --- | :-: |
-| Arbitrum | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Avalanche | [Guia Docker](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 5 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Base | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | CPU de 8+ núcleos<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> mais 4.5TB (NVMe preferido)<br /> _última atualização em 14 de maio de 2024_ | ✅ |
-| Binance | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | CPU de 8 núcleos e 16 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 14 TiB<br /> _última atualização em 22 de junho de 2024_ | ✅ |
-| Celo | [Guia Docker](https://docs.infradao.com/archive-nodes-101/celo/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 2 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Ethereum | [Guia Docker](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Frequência de clock maior que número de núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> Mais de 3TB (NVMe recomendado)<br /> _última atualização em agosto de 2023_ | ✅ |
-| Fantom | [Guia Docker](https://docs.infradao.com/archive-nodes-101/fantom/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 13 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Gnosis | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | CPU de 6 núcleos e 12 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 3 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Linea | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 1 TiB<br /> _última atualização em 2 de abril de 2024_ | ✅ |
-| Optimism | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Polygon | [Guia Docker](https://docs.infradao.com/archive-nodes-101/polygon/docker) | CPU de 16 núcleos<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= SSD NVMe com mais de 10 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
-| Scroll | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/scroll/docker) | CPU de 4 núcleos e 8 threads<br /> Debian 12<br /> 16GB+ RAM<br /> SSD NVMe com mais de 1 TiB<br /> _última atualização em 3 de abril de 2024_ | ✅ |
+| Rede      | Guias                                                                                                                                                                                                                                                                                            | Requisitos de sistema                                                                                                                                                | Recompensas de Indexação |
+| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------: |
+| Arbitrum  | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_                                |             ✅            |
+| Avalanche | [Guia Docker](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                      | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 5 TiB<br /> _última atualização em agosto de 2023_                        |             ✅            |
+| Base      | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | CPU de 8+ núcleos<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> mais 4.5TB (NVMe preferido)<br /> _última atualização em 14 de maio de 2024_                    |             ✅            |
+| Binance   | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                    | CPU de 8 núcleos e 16 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 14 TiB<br /> _última atualização em 22 de junho de 2024_                 |             ✅            |
+| Celo      | [Guia Docker](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                           | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 2 TiB<br /> _última atualização em agosto de 2023_                     |             ✅            |
+| Ethereum  | [Guia Docker](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                | Frequência de clock maior que número de núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> Mais de 3TB (NVMe recomendado)<br /> _última atualização em agosto de 2023_ |             ✅            |
+| Fantom    | [Guia Docker](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                         | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 13 TiB<br /> _última atualização em agosto de 2023_                       |             ✅            |
+| Gnosis    | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                            | CPU de 6 núcleos e 12 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 3 TiB<br /> _última atualização em agosto de 2023_                       |             ✅            |
+| Linea     | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                    | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 1 TiB<br /> _última atualização em 2 de abril de 2024_                            |             ✅            |
+| Optimism  | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_                        |             ✅            |
+| Polygon   | [Guia Docker](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                        | CPU de 16 núcleos<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= SSD NVMe com mais de 10 TiB<br /> _última atualização em agosto de 2023_                               |             ✅            |
+| Scroll    | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                    | CPU de 4 núcleos e 8 threads<br /> Debian 12<br /> 16GB+ RAM<br /> SSD NVMe com mais de 1 TiB<br /> _última atualização em 3 de abril de 2024_                       |             ✅            |

From 96b155e3e902d828a87b5759f96b655130e95b24 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:53 -0500
Subject: [PATCH 1179/1325] New translations supported-network-requirements.mdx
 (Russian)

---
 .../ru/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/ru/supported-network-requirements.mdx b/website/pages/ru/supported-network-requirements.mdx
index 2677263a063f..21a6f62ebb20 100644
--- a/website/pages/ru/supported-network-requirements.mdx
+++ b/website/pages/ru/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Сеть | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Сеть      | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Арбитрум  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From ebaf409fc76530a43aef405b5a30ccc56aa66c3b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:53 -0500
Subject: [PATCH 1180/1325] New translations supported-network-requirements.mdx
 (Swedish)

---
 .../sv/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/sv/supported-network-requirements.mdx b/website/pages/sv/supported-network-requirements.mdx
index f7a4943afd1b..f6c91108bac9 100644
--- a/website/pages/sv/supported-network-requirements.mdx
+++ b/website/pages/sv/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Nätverk | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Nätverk   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From d386b3791a72dd41b86927a7fa7c54a26c4e5c69 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:54 -0500
Subject: [PATCH 1181/1325] New translations supported-network-requirements.mdx
 (Turkish)

---
 .../tr/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/tr/supported-network-requirements.mdx b/website/pages/tr/supported-network-requirements.mdx
index 5329c6b9dad2..73adcca0dded 100644
--- a/website/pages/tr/supported-network-requirements.mdx
+++ b/website/pages/tr/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Ağ | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Ağ        | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From efe8bcf8c53e674bc8221624a00a72f5ab3a3420 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:55 -0500
Subject: [PATCH 1182/1325] New translations supported-network-requirements.mdx
 (Ukrainian)

---
 .../uk/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/uk/supported-network-requirements.mdx b/website/pages/uk/supported-network-requirements.mdx
index df15ef48d762..afbf755c0a5a 100644
--- a/website/pages/uk/supported-network-requirements.mdx
+++ b/website/pages/uk/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 72b986bb00116cff135ffe96f228a1def47e7ceb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:57 -0500
Subject: [PATCH 1183/1325] New translations supported-network-requirements.mdx
 (Chinese Simplified)

---
 .../zh/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/zh/supported-network-requirements.mdx b/website/pages/zh/supported-network-requirements.mdx
index 62bb55c63746..d9e844cbbe43 100644
--- a/website/pages/zh/supported-network-requirements.mdx
+++ b/website/pages/zh/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| 网络 | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| 以太坊 | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| 网络        | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| 以太坊       | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 86d5349dda86cede76799499ed547021ed4e687b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:58 -0500
Subject: [PATCH 1184/1325] New translations supported-network-requirements.mdx
 (Urdu (Pakistan))

---
 .../ur/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/ur/supported-network-requirements.mdx b/website/pages/ur/supported-network-requirements.mdx
index f4b5a7768f13..ee345dee7c3f 100644
--- a/website/pages/ur/supported-network-requirements.mdx
+++ b/website/pages/ur/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| نیٹ ورک | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| نیٹ ورک   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 92e97e35fb039c77fddefaaa202b0da1f91a29b4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:55:59 -0500
Subject: [PATCH 1185/1325] New translations supported-network-requirements.mdx
 (Vietnamese)

---
 .../vi/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/vi/supported-network-requirements.mdx b/website/pages/vi/supported-network-requirements.mdx
index 50cd5e88b459..a8305e895706 100644
--- a/website/pages/vi/supported-network-requirements.mdx
+++ b/website/pages/vi/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Mạng lưới | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Mạng lưới | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From d7a0e375928285fa82ba2c2d67335630079af9e0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:00 -0500
Subject: [PATCH 1186/1325] New translations supported-network-requirements.mdx
 (Marathi)

---
 .../mr/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/mr/supported-network-requirements.mdx b/website/pages/mr/supported-network-requirements.mdx
index a1a9e0338649..8d20c31f3fc5 100644
--- a/website/pages/mr/supported-network-requirements.mdx
+++ b/website/pages/mr/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| हिमस्खलन | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| इथरियम | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| फॅन्टम | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| आशावाद | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| बहुभुज | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| Network  | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| हिमस्खलन | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base     | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo     | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| इथरियम   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| फॅन्टम   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis   | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| आशावाद   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| बहुभुज   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll   | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 45ae8445249a89909b4804de23ba19ca9d6fcc66 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:01 -0500
Subject: [PATCH 1187/1325] New translations supported-network-requirements.mdx
 (Hindi)

---
 .../hi/supported-network-requirements.mdx     | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/hi/supported-network-requirements.mdx b/website/pages/hi/supported-network-requirements.mdx
index b5bb4a1ec8d5..29673e7529a7 100644
--- a/website/pages/hi/supported-network-requirements.mdx
+++ b/website/pages/hi/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| नेटवर्क | Guides | System Requirements | Indexing Rewards |
-| --- | --- | --- | :-: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
-| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
-| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
-| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
-| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
-| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
+| नेटवर्क   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _अंतिम बार अपडेट किया गया 22 जून 2024_    |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 3e85a42cdc59a38d6048b8f2ebab8ef8cd738067 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:01 -0500
Subject: [PATCH 1188/1325] New translations supported-network-requirements.mdx
 (Swahili)

---
 .../sw/supported-network-requirements.mdx      | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)
 create mode 100644 website/pages/sw/supported-network-requirements.mdx

diff --git a/website/pages/sw/supported-network-requirements.mdx b/website/pages/sw/supported-network-requirements.mdx
new file mode 100644
index 000000000000..afbf755c0a5a
--- /dev/null
+++ b/website/pages/sw/supported-network-requirements.mdx
@@ -0,0 +1,18 @@
+---
+title: Supported Network Requirements
+---
+
+| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
+| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
+| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
+| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
+| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
+| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
+| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
+| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
+| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |

From 7614ea03518b139596facf34bd08148f3be611a0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:03 -0500
Subject: [PATCH 1189/1325] New translations tap.mdx (Romanian)

---
 website/pages/ro/tap.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ro/tap.mdx b/website/pages/ro/tap.mdx
index 0a41faab9c11..3e8185186982 100644
--- a/website/pages/ro/tap.mdx
+++ b/website/pages/ro/tap.mdx
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 44be6e0048cc74eae881fe3d07d498c5459b175f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:04 -0500
Subject: [PATCH 1190/1325] New translations tap.mdx (French)

---
 website/pages/fr/tap.mdx | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/fr/tap.mdx b/website/pages/fr/tap.mdx
index 0a41faab9c11..3430199911ab 100644
--- a/website/pages/fr/tap.mdx
+++ b/website/pages/fr/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Aperçu
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -13,7 +13,7 @@ Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, T
 - Allows Indexers control of receipts and payments, guaranteeing payment for queries.
 - It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
 
-## Specifics
+## Spécificités⁠
 
 TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### Exigences
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Notez :
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 3a53803e7f424c49c23825608d8500f04df67f65 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:05 -0500
Subject: [PATCH 1191/1325] New translations tap.mdx (Spanish)

---
 website/pages/es/tap.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/es/tap.mdx b/website/pages/es/tap.mdx
index 0a41faab9c11..2f0b75160fa9 100644
--- a/website/pages/es/tap.mdx
+++ b/website/pages/es/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Descripción
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Notas:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 3785effe5f1f2737e3689a065ff7459888a26728 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:06 -0500
Subject: [PATCH 1192/1325] New translations tap.mdx (Arabic)

---
 website/pages/ar/tap.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/ar/tap.mdx b/website/pages/ar/tap.mdx
index 0a41faab9c11..0cef5f4209fa 100644
--- a/website/pages/ar/tap.mdx
+++ b/website/pages/ar/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## نظره عامة
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 92f8baeacd35adb231081fd883cd08f83415d097 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:07 -0500
Subject: [PATCH 1193/1325] New translations tap.mdx (Czech)

---
 website/pages/cs/tap.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/cs/tap.mdx b/website/pages/cs/tap.mdx
index 0a41faab9c11..6594ce05e1f5 100644
--- a/website/pages/cs/tap.mdx
+++ b/website/pages/cs/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Přehled
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### Požadavky
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Poznámky:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From fb953c17da4d090e55e6c03b888852b614bb939a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:08 -0500
Subject: [PATCH 1194/1325] New translations tap.mdx (German)

---
 website/pages/de/tap.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/de/tap.mdx b/website/pages/de/tap.mdx
index 0a41faab9c11..c259f0dbbf32 100644
--- a/website/pages/de/tap.mdx
+++ b/website/pages/de/tap.mdx
@@ -13,7 +13,7 @@ Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, T
 - Allows Indexers control of receipts and payments, guaranteeing payment for queries.
 - It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
 
-## Specifics
+## Besonderheiten
 
 TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
 
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 752e57286707cd8262b5d96cc3be470a3a275b2d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:09 -0500
Subject: [PATCH 1195/1325] New translations tap.mdx (Italian)

---
 website/pages/it/tap.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/it/tap.mdx b/website/pages/it/tap.mdx
index 0a41faab9c11..ed40e829a2cb 100644
--- a/website/pages/it/tap.mdx
+++ b/website/pages/it/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Panoramica
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 561e0fef7894a97f67df058dc61e044abaa8883e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:10 -0500
Subject: [PATCH 1196/1325] New translations tap.mdx (Japanese)

---
 website/pages/ja/tap.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/ja/tap.mdx b/website/pages/ja/tap.mdx
index 0a41faab9c11..ab14dd962926 100644
--- a/website/pages/ja/tap.mdx
+++ b/website/pages/ja/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## 概要
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### 要件
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+注：
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 65ef6363992a58aa77f945692145710218e7b8e8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:11 -0500
Subject: [PATCH 1197/1325] New translations tap.mdx (Korean)

---
 website/pages/ko/tap.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/ko/tap.mdx b/website/pages/ko/tap.mdx
index 0a41faab9c11..3e8185186982 100644
--- a/website/pages/ko/tap.mdx
+++ b/website/pages/ko/tap.mdx
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 19de6dc57d9ba2938d3fc1316076c4a8a439bfc5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:12 -0500
Subject: [PATCH 1198/1325] New translations tap.mdx (Dutch)

---
 website/pages/nl/tap.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/nl/tap.mdx b/website/pages/nl/tap.mdx
index 0a41faab9c11..3e8185186982 100644
--- a/website/pages/nl/tap.mdx
+++ b/website/pages/nl/tap.mdx
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 0b2b3f9cf8f7acc56ac681e3c4231bc65217dca5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:13 -0500
Subject: [PATCH 1199/1325] New translations tap.mdx (Polish)

---
 website/pages/pl/tap.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/pl/tap.mdx b/website/pages/pl/tap.mdx
index 0a41faab9c11..3e8185186982 100644
--- a/website/pages/pl/tap.mdx
+++ b/website/pages/pl/tap.mdx
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 236843eca07091ff99e28a3c7481a5a9145ef5b9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:14 -0500
Subject: [PATCH 1200/1325] New translations tap.mdx (Portuguese)

---
 website/pages/pt/tap.mdx | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/pt/tap.mdx b/website/pages/pt/tap.mdx
index 0a41faab9c11..c2fefbdd9694 100644
--- a/website/pages/pt/tap.mdx
+++ b/website/pages/pt/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Visão geral
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -13,7 +13,7 @@ Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, T
 - Allows Indexers control of receipts and payments, guaranteeing payment for queries.
 - It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
 
-## Specifics
+## Especificações
 
 TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### Requisitos
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Notas:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From c1358b141dc380f628710d295fd70cb3c2cdb68c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:15 -0500
Subject: [PATCH 1201/1325] New translations tap.mdx (Russian)

---
 website/pages/ru/tap.mdx | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/ru/tap.mdx b/website/pages/ru/tap.mdx
index 0a41faab9c11..699d25f0f1b5 100644
--- a/website/pages/ru/tap.mdx
+++ b/website/pages/ru/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Обзор
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -13,7 +13,7 @@ Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, T
 - Allows Indexers control of receipts and payments, guaranteeing payment for queries.
 - It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
 
-## Specifics
+## Специфические особенности
 
 TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### Требования
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Примечания:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From d7c9f32133de4a4c9499431c57612ab29eb527bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:16 -0500
Subject: [PATCH 1202/1325] New translations tap.mdx (Swedish)

---
 website/pages/sv/tap.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/sv/tap.mdx b/website/pages/sv/tap.mdx
index 0a41faab9c11..d55093c0862e 100644
--- a/website/pages/sv/tap.mdx
+++ b/website/pages/sv/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Översikt
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### Krav
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Noteringar:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From aa6d5563a98e1ecb3ce55be476ff49a9fd365a8c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:17 -0500
Subject: [PATCH 1203/1325] New translations tap.mdx (Turkish)

---
 website/pages/tr/tap.mdx | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/tr/tap.mdx b/website/pages/tr/tap.mdx
index 0a41faab9c11..cdee8f3f9111 100644
--- a/website/pages/tr/tap.mdx
+++ b/website/pages/tr/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Genel Bakış
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -13,7 +13,7 @@ Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, T
 - Allows Indexers control of receipts and payments, guaranteeing payment for queries.
 - It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
 
-## Specifics
+## Ayrıntılar
 
 TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### Gereksinimler
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+Notlar:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From c9ab537aea0694f5c3ce708d1ca4e4e309d5d69d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:18 -0500
Subject: [PATCH 1204/1325] New translations tap.mdx (Ukrainian)

---
 website/pages/uk/tap.mdx | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/website/pages/uk/tap.mdx b/website/pages/uk/tap.mdx
index 0a41faab9c11..3e8185186982 100644
--- a/website/pages/uk/tap.mdx
+++ b/website/pages/uk/tap.mdx
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From de827aa6dd4655e4f2606bdf28d676f7b5192c98 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:19 -0500
Subject: [PATCH 1205/1325] New translations tap.mdx (Chinese Simplified)

---
 website/pages/zh/tap.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/zh/tap.mdx b/website/pages/zh/tap.mdx
index 0a41faab9c11..a91191795f03 100644
--- a/website/pages/zh/tap.mdx
+++ b/website/pages/zh/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## 概述
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### 要求
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+注意：
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 832a2627464d6cf6386a8a9263d148ad34f7039f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:20 -0500
Subject: [PATCH 1206/1325] New translations tap.mdx (Urdu (Pakistan))

---
 website/pages/ur/tap.mdx | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/website/pages/ur/tap.mdx b/website/pages/ur/tap.mdx
index 0a41faab9c11..44b46f2e5fc7 100644
--- a/website/pages/ur/tap.mdx
+++ b/website/pages/ur/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## جائزہ
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,21 +45,21 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
 | Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
-### Requirements
+### تقاضے
 
 In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
 
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+نوٹس:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 8fe9e83ec27bde751332b92a3c7824892d612bc3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:21 -0500
Subject: [PATCH 1207/1325] New translations tap.mdx (Vietnamese)

---
 website/pages/vi/tap.mdx | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/website/pages/vi/tap.mdx b/website/pages/vi/tap.mdx
index 0a41faab9c11..63b32fa831f6 100644
--- a/website/pages/vi/tap.mdx
+++ b/website/pages/vi/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## Tổng quan
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 1666838261f1aea8ea005eb1eb38473a9e9b4f73 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:22 -0500
Subject: [PATCH 1208/1325] New translations tap.mdx (Marathi)

---
 website/pages/mr/tap.mdx | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/website/pages/mr/tap.mdx b/website/pages/mr/tap.mdx
index 0a41faab9c11..47cb3cbcee00 100644
--- a/website/pages/mr/tap.mdx
+++ b/website/pages/mr/tap.mdx
@@ -4,7 +4,7 @@ title: TAP Migration Guide
 
 Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
 
-## Overview
+## सविश्लेषण
 
 [TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
 
@@ -45,15 +45,15 @@ As long as you run `tap-agent` and `indexer-agent`, everything will be executed
 
 ### Contracts
 
-| Contract            | Arbitrum Sepolia (421614)                    | Arbitrum Mainnet (42161)                     |
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
 | ------------------- | -------------------------------------------- | -------------------------------------------- |
-| TAP Verifier        | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` |
-| AllocationIDTracker | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` |
-| Escrow              | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
 ### Gateway
 
-| Component  | Edge and Node Mainnet (Arbitrum Sepolia)      | Edge and Node Testnet (Aribtrum Mainnet)      |
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
 | ---------- | --------------------------------------------- | --------------------------------------------- |
 | Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
 | Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
@@ -168,7 +168,7 @@ max_amount_willing_to_lose_grt = 20
 0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
 ```
 
-Notes:
+नोट्स:
 
 - Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
 - Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
@@ -190,4 +190,4 @@ You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs
 
 ### Launchpad
 
-Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/feat/indexer-rs/charts/graph-network-indexer)
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 27c1c3ccb8161f58a2079aa7ad037c6db83319fd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:23 -0500
Subject: [PATCH 1209/1325] New translations tap.mdx (Swahili)

---
 website/pages/sw/tap.mdx | 193 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 193 insertions(+)
 create mode 100644 website/pages/sw/tap.mdx

diff --git a/website/pages/sw/tap.mdx b/website/pages/sw/tap.mdx
new file mode 100644
index 000000000000..3e8185186982
--- /dev/null
+++ b/website/pages/sw/tap.mdx
@@ -0,0 +1,193 @@
+---
+title: TAP Migration Guide
+---
+
+Learn about The Graph’s new payment system, **Timeline Aggregation Protocol, TAP**. This system provides fast, efficient microtransactions with minimized trust.
+
+## Overview
+
+[TAP](https://docs.rs/tap_core/latest/tap_core/index.html) is a drop-in replacement to the Scalar payment system currently in place. It provides the following key features:
+
+- Efficiently handles micropayments.
+- Adds a layer of consolidations to on-chain transactions and costs.
+- Allows Indexers control of receipts and payments, guaranteeing payment for queries.
+- It enables decentralized, trustless gateways and improves `indexer-service` performance for multiple senders.
+
+## Specifics
+
+TAP allows a sender to make multiple payments to a receiver, **TAP Receipts**, which aggregates these payments into a single payment, a **Receipt Aggregate Voucher**, also known as a **RAV**. This aggregated payment can then be verified on the blockchain, reducing the number of transactions and simplifying the payment process.
+
+For each query, the gateway will send you a `signed receipt` that is stored on your database. Then, these queries will be aggregated by a `tap-agent` through a request. Afterwards, you’ll receive a RAV. You can update a RAV by sending it with newer receipts and this will generate a new RAV with an increased value.
+
+### RAV Details
+
+- It’s money that is waiting to be sent to the blockchain.
+
+- It will continue to send requests to aggregate and ensure that the total value of non-aggregated receipts does not exceed the `amount willing to lose`.
+
+- Each RAV can be redeemed once in the contracts, which is why they are sent after the allocation is closed.
+
+### Redeeming RAV
+
+As long as you run `tap-agent` and `indexer-agent`, everything will be executed automatically. The following provides a detailed breakdown of the process:
+
+1. An Indexer closes allocation.
+
+2. `<recently-closed-allocation-buffer> period, tap-agent` takes all pending receipts for that specific allocation and requests an aggregation into a RAV, marking it as `last`.
+
+3. `indexer-agent` takes all the last RAVS and sends redeem requests to the blockchain, which will update the value of `redeem_at`.
+
+4. During the `<finality-time>` period, `indexer-agent` monitors if the blockchain has any reorganizations that revert the transaction.
+
+   - If it was reverted, the RAV is resent to the blockchain. If it was not reverted, it gets marked as `final`.
+
+## Blockchain Addresses
+
+### Contracts
+
+| Contract            | Arbitrum Mainnet (42161)                     | Arbitrum Sepolia (421614)                    |
+| ------------------- | -------------------------------------------- | -------------------------------------------- |
+| TAP Verifier        | `0x33f9E93266ce0E108fc85DdE2f71dab555A0F05a` | `0xfC24cE7a4428A6B89B52645243662A02BA734ECF` |
+| AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
+| Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
+
+### Gateway
+
+| Component  | Edge and Node Mainnet (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
+| ---------- | --------------------------------------------- | --------------------------------------------- |
+| Sender     | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
+| Signers    | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
+| Aggregator | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
+
+### Requirements
+
+In addition to the typical requirements to run an indexer, you’ll need a `tap-escrow-subgraph` endpoint to query TAP updates. You can use The Graph Network to query or host yourself on your `graph-node`.
+
+- [Graph TAP Aribtrum Sepolia subgraph (for The Graph testnet)](https://thegraph.com/explorer/subgraphs/7ubx365MiqBH5iUz6XWXWT8PTof5BVAyEzdb8m17RvbD)
+- [Graph TAP Arbitrum One subgraph (for The Graph mainnet)](https://thegraph.com/explorer/subgraphs/4sukbNVTzGELnhdnpyPqsf1QqtzNHEYKKmJkgaT8z6M1)
+
+> Note: `indexer-agent` does not currently handle the indexing of this subgraph like it does for the network subgraph deployement. As a result, you have to index it manually.
+
+## Migration Guide
+
+### Software versions
+
+The required software version can be found [here](https://github.com/graphprotocol/indexer/blob/main/docs/networks/arbitrum-one.md#latest-releases).
+
+### Steps
+
+1. **Indexer Agent**
+
+   - Follow the [same process](https://github.com/graphprotocol/indexer/pkgs/container/indexer-agent#graph-protocol-indexer-components).
+   - Give the new argument `--tap-subgraph-endpoint` to activate the new TAP codepaths and enable redeeming of TAP RAVs.
+
+2. **Indexer Service**
+
+   - Fully replace your current configuration with the [new Indexer Service rs](https://github.com/graphprotocol/indexer-rs). It's recommend that you use the [container image](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs).
+   - Like the older version, you can scale Indexer Service horizontally easily. It is still stateless.
+
+3. **TAP Agent**
+
+   - Run _one_ single instance of [TAP Agent](https://github.com/graphprotocol/indexer-rs) at all times. It's recommend that you use the [container image](https://github.com/orgs/graphprotocol/packages?repo_name=indexer-rs).
+
+4. **Configure Indexer Service and TAP Agent**
+
+   Configuration is a TOML file shared between `indexer-service` and `tap-agent`, supplied with the argument `--config /path/to/config.toml`.
+
+   Check out the full [configuration](https://github.com/graphprotocol/indexer-rs/blob/main/config/maximal-config-example.toml) and the [default values](https://github.com/graphprotocol/indexer-rs/blob/main/config/default_values.toml)
+
+For minimal configuration, use the following template:
+
+```bash
+# You will have to change *all* the values below to match your setup.
+#
+# Some of the config below are global graph network values, which you can find here:
+# <https://github.com/graphprotocol/indexer/tree/main/docs/networks>
+#
+# Pro tip: if you need to load some values from the environment into this config, you
+# can overwrite with environment variables. For example, the following can be replaced
+# by [PREFIX]_DATABASE_POSTGRESURL, where PREFIX can be `INDEXER_SERVICE` or `TAP_AGENT`:
+#
+# [database]
+# postgres_url = "postgresql://indexer:${POSTGRES_PASSWORD}@postgres:5432/indexer_components_0"
+
+[indexer]
+indexer_address = "0x1111111111111111111111111111111111111111"
+operator_mnemonic = "celery smart tip orange scare van steel radio dragon joy alarm crane"
+
+[database]
+# The URL of the Postgres database used for the indexer components. The same database
+# that is used by the `indexer-agent`. It is expected that `indexer-agent` will create
+# the necessary tables.
+postgres_url = "postgres://postgres@postgres:5432/postgres"
+
+[graph_node]
+# URL to your graph-node's query endpoint
+query_url = "<http://graph-node:8000>"
+# URL to your graph-node's status endpoint
+status_url = "<http://graph-node:8000/graphql>"
+
+[subgraphs.network]
+# Query URL for the Graph Network subgraph.
+query_url = "<http://example.com/network-subgraph>"
+# Optional, deployment to look for in the local `graph-node`, if locally indexed.
+# Locally indexing the subgraph is recommended.
+# NOTE: Use `query_url` or `deployment_id` only
+deployment_id = "Qmaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
+
+[subgraphs.escrow]
+# Query URL for the Escrow subgraph.
+query_url = "<http://example.com/network-subgraph>"
+# Optional, deployment to look for in the local `graph-node`, if locally indexed.
+# Locally indexing the subgraph is recommended.
+# NOTE: Use `query_url` or `deployment_id` only
+deployment_id = "Qmaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
+
+[blockchain]
+# The chain ID of the network that the graph network is running on
+chain_id = 1337
+# Contract address of TAP's receipt aggregate voucher (RAV) verifier.
+receipts_verifier_address = "0x2222222222222222222222222222222222222222"
+
+########################################
+# Specific configurations to tap-agent #
+########################################
+[tap]
+# This is the amount of fees you are willing to risk at any given time. For ex.
+# if the sender stops supplying RAVs for long enough and the fees exceed this
+# amount, the indexer-service will stop accepting queries from the sender
+# until the fees are aggregated.
+# NOTE: Use strings for decimal values to prevent rounding errors
+# e.g:
+# max_amount_willing_to_lose_grt = "0.1"
+max_amount_willing_to_lose_grt = 20
+
+[tap.sender_aggregator_endpoints]
+# Key-Value of all senders and their aggregator endpoints
+# This one below is for the E&N testnet gateway for example.
+0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467 = "https://tap-aggregator.network.thegraph.com"
+```
+
+Notes:
+
+- Values for `tap.sender_aggregator_endpoints` can be found in the [gateway section](/tap/#gateway).
+- Values for `blockchain.receipts_verifier_address` must be used accordingly to the [Blockchain addresses section](/tap/#contracts) using the appropriate chain id.
+
+**Log Level**
+
+- You can set the log level by using the `RUST_LOG` environment variable.
+- It’s recommended that you set it to `RUST_LOG=indexer_tap_agent=debug,info`.
+
+## Monitoring
+
+### Metrics
+
+All components expose the port 7300 to be queried by prometheus.
+
+### Grafana Dashboard
+
+You can download [Grafana Dashboard](https://github.com/graphprotocol/indexer-rs/blob/main/docs/dashboard.json) and import.
+
+### Launchpad
+
+Currently, there is a WIP version of `indexer-rs` and `tap-agent` that can be found [here](https://github.com/graphops/launchpad-charts/tree/main/charts/graph-network-indexer)

From 0f9bc88988b65cfafbf00349946757938fcce23b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:24 -0500
Subject: [PATCH 1210/1325] New translations introduction.mdx (Romanian)

---
 website/pages/ro/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ro/sps/introduction.mdx b/website/pages/ro/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/ro/sps/introduction.mdx
+++ b/website/pages/ro/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 2614cbb9c5630ad0c07e79d1bbd750456f018eae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:25 -0500
Subject: [PATCH 1211/1325] New translations introduction.mdx (French)

---
 website/pages/fr/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/fr/sps/introduction.mdx b/website/pages/fr/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/fr/sps/introduction.mdx
+++ b/website/pages/fr/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 84c95451e7d582dad1d8ee163ac77d4ceb06fefb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:26 -0500
Subject: [PATCH 1212/1325] New translations introduction.mdx (Spanish)

---
 website/pages/es/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/es/sps/introduction.mdx b/website/pages/es/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/es/sps/introduction.mdx
+++ b/website/pages/es/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From e4f29658af463921a59bbd7d485b86169a068147 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:27 -0500
Subject: [PATCH 1213/1325] New translations introduction.mdx (Arabic)

---
 website/pages/ar/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ar/sps/introduction.mdx b/website/pages/ar/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/ar/sps/introduction.mdx
+++ b/website/pages/ar/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 7a53d85dd5c306d1e7fb8ec4925467550d51d8ae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:28 -0500
Subject: [PATCH 1214/1325] New translations introduction.mdx (Czech)

---
 website/pages/cs/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/cs/sps/introduction.mdx b/website/pages/cs/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/cs/sps/introduction.mdx
+++ b/website/pages/cs/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 7ac0ad0f0bf253677d3fc2ad839728ebc2b3c2be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:29 -0500
Subject: [PATCH 1215/1325] New translations introduction.mdx (German)

---
 website/pages/de/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/de/sps/introduction.mdx b/website/pages/de/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/de/sps/introduction.mdx
+++ b/website/pages/de/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 6376b02404918d0050b773e3a2232bd41f8f0399 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:30 -0500
Subject: [PATCH 1216/1325] New translations introduction.mdx (Italian)

---
 website/pages/it/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/it/sps/introduction.mdx b/website/pages/it/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/it/sps/introduction.mdx
+++ b/website/pages/it/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 608a192fb44add5881144c2256b26bcb8a45d300 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:31 -0500
Subject: [PATCH 1217/1325] New translations introduction.mdx (Japanese)

---
 website/pages/ja/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ja/sps/introduction.mdx b/website/pages/ja/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/ja/sps/introduction.mdx
+++ b/website/pages/ja/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From ce4017d0af3bed2a3bd64a15ffab7105c8584568 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:32 -0500
Subject: [PATCH 1218/1325] New translations introduction.mdx (Korean)

---
 website/pages/ko/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ko/sps/introduction.mdx b/website/pages/ko/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/ko/sps/introduction.mdx
+++ b/website/pages/ko/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From fffccc40e07d2ae1e39d7e7d7003e828f3b4cfff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:33 -0500
Subject: [PATCH 1219/1325] New translations introduction.mdx (Dutch)

---
 website/pages/nl/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/nl/sps/introduction.mdx b/website/pages/nl/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/nl/sps/introduction.mdx
+++ b/website/pages/nl/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 14b1f0bbcdc7881c48ded69a8e9d820d7cdea145 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:34 -0500
Subject: [PATCH 1220/1325] New translations introduction.mdx (Polish)

---
 website/pages/pl/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/pl/sps/introduction.mdx b/website/pages/pl/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/pl/sps/introduction.mdx
+++ b/website/pages/pl/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From c6ee6d223a4b8cdd0c75b3524e4536575432f429 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:35 -0500
Subject: [PATCH 1221/1325] New translations introduction.mdx (Portuguese)

---
 website/pages/pt/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/pt/sps/introduction.mdx b/website/pages/pt/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/pt/sps/introduction.mdx
+++ b/website/pages/pt/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From bcf34b9647b14a31af0e025c96960396654b9d14 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:36 -0500
Subject: [PATCH 1222/1325] New translations introduction.mdx (Russian)

---
 website/pages/ru/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ru/sps/introduction.mdx b/website/pages/ru/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/ru/sps/introduction.mdx
+++ b/website/pages/ru/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 2bd8c96248241c1991778a4b79508ea308843612 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:37 -0500
Subject: [PATCH 1223/1325] New translations introduction.mdx (Swedish)

---
 website/pages/sv/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/sv/sps/introduction.mdx b/website/pages/sv/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/sv/sps/introduction.mdx
+++ b/website/pages/sv/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From e8e811ab0f006409a6c0a065926e4d96683b491e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:38 -0500
Subject: [PATCH 1224/1325] New translations introduction.mdx (Turkish)

---
 website/pages/tr/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/tr/sps/introduction.mdx b/website/pages/tr/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/tr/sps/introduction.mdx
+++ b/website/pages/tr/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From bc0b67242737b87e8231ca2679aef1687f40c2d4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:39 -0500
Subject: [PATCH 1225/1325] New translations introduction.mdx (Ukrainian)

---
 website/pages/uk/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/uk/sps/introduction.mdx b/website/pages/uk/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/uk/sps/introduction.mdx
+++ b/website/pages/uk/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From a52775bb8bccc8996d4308b0d8be0ad1275c621c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:40 -0500
Subject: [PATCH 1226/1325] New translations introduction.mdx (Chinese
 Simplified)

---
 website/pages/zh/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/zh/sps/introduction.mdx b/website/pages/zh/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/zh/sps/introduction.mdx
+++ b/website/pages/zh/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From c3d2fedaf47aae4a3d0244567843a5f3945b159d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:41 -0500
Subject: [PATCH 1227/1325] New translations introduction.mdx (Urdu (Pakistan))

---
 website/pages/ur/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/ur/sps/introduction.mdx b/website/pages/ur/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/ur/sps/introduction.mdx
+++ b/website/pages/ur/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From ac26e39ed6e8f16bfd057d302b4cf283521d1ff5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:42 -0500
Subject: [PATCH 1228/1325] New translations introduction.mdx (Vietnamese)

---
 website/pages/vi/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/vi/sps/introduction.mdx b/website/pages/vi/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/vi/sps/introduction.mdx
+++ b/website/pages/vi/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 94ffc6fdfee776f9a0648fdd67c2b03856515248 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:43 -0500
Subject: [PATCH 1229/1325] New translations introduction.mdx (Marathi)

---
 website/pages/mr/sps/introduction.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/pages/mr/sps/introduction.mdx b/website/pages/mr/sps/introduction.mdx
index 3e50521589af..12e3f81c6d53 100644
--- a/website/pages/mr/sps/introduction.mdx
+++ b/website/pages/mr/sps/introduction.mdx
@@ -14,6 +14,6 @@ It is really a matter of where you put your logic, in the subgraph or the Substr
 
 Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
 
-- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/solana)
-- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/evm)
-- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/intro-your-first-application/injective)
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 27c27f5533653cc172b3df33d32d9d45ce81bd2d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:44 -0500
Subject: [PATCH 1230/1325] New translations introduction.mdx (Swahili)

---
 website/pages/sw/sps/introduction.mdx | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)
 create mode 100644 website/pages/sw/sps/introduction.mdx

diff --git a/website/pages/sw/sps/introduction.mdx b/website/pages/sw/sps/introduction.mdx
new file mode 100644
index 000000000000..12e3f81c6d53
--- /dev/null
+++ b/website/pages/sw/sps/introduction.mdx
@@ -0,0 +1,19 @@
+---
+title: Introduction to Substreams-powered Subgraphs
+---
+
+By using a Substreams package (`.spkg`) as a data source, your subgraph gains access to a stream of pre-indexed blockchain data. This enables more efficient and scalable data handling, especially with large or complex blockchain networks.
+
+There are two methods of enabling this technology:
+
+Using Substreams [triggers](./triggers): Consume from any Substreams module by importing the Protobuf model through a subgraph handler and move all your logic into a subgraph. This method creates the subgraph entities directly in the subgraph.
+
+Using [Entity Changes](https://substreams.streamingfast.io/documentation/consume/subgraph/graph-out): By writing more of the logic into Substreams, you can consume the module's output directly into graph-node. In graph-node, you can use the Substreams data to create your subgraph entities.
+
+It is really a matter of where you put your logic, in the subgraph or the Substreams. Keep in mind that having more of your logic in Substreams benefits from a parallelized model, whereas triggers will be linearly consumed in graph-node.
+
+Visit the following links for How-To Guides on using code-generation tooling to build your first end-to-end project quickly:
+
+- [Solana](https://substreams.streamingfast.io/documentation/how-to-guides/solana)
+- [EVM](https://substreams.streamingfast.io/documentation/how-to-guides/evm)
+- [Injective](https://substreams.streamingfast.io/documentation/how-to-guides/injective)

From 8cb223aa36a693eeea6b5b23f496829e4f14c532 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:44 -0500
Subject: [PATCH 1231/1325] New translations triggers-example.mdx (Romanian)

---
 website/pages/ro/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/ro/sps/triggers-example.mdx b/website/pages/ro/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/ro/sps/triggers-example.mdx
+++ b/website/pages/ro/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 3b12ea63251e253aae567f837e777008ba57bebd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:45 -0500
Subject: [PATCH 1232/1325] New translations triggers-example.mdx (Spanish)

---
 website/pages/es/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/es/sps/triggers-example.mdx b/website/pages/es/sps/triggers-example.mdx
index d8d61566295e..b52cd3cf42e3 100644
--- a/website/pages/es/sps/triggers-example.mdx
+++ b/website/pages/es/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Prerrequisitos
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From f88869bc6145285f4ef939b4eac35bcf6e1f6b85 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:46 -0500
Subject: [PATCH 1233/1325] New translations triggers-example.mdx (Arabic)

---
 website/pages/ar/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/ar/sps/triggers-example.mdx b/website/pages/ar/sps/triggers-example.mdx
index d8d61566295e..3c1909f87ac8 100644
--- a/website/pages/ar/sps/triggers-example.mdx
+++ b/website/pages/ar/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## المتطلبات الأساسية
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 3c5c386ff3546c4c7275f3604fcde6d32fe78fe4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:47 -0500
Subject: [PATCH 1234/1325] New translations triggers-example.mdx (Czech)

---
 website/pages/cs/sps/triggers-example.mdx | 33 ++++++++++++-----------
 1 file changed, 18 insertions(+), 15 deletions(-)

diff --git a/website/pages/cs/sps/triggers-example.mdx b/website/pages/cs/sps/triggers-example.mdx
index d8d61566295e..a25f86fd5aa6 100644
--- a/website/pages/cs/sps/triggers-example.mdx
+++ b/website/pages/cs/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Požadavky
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,7 +123,17 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
-## Conclusion
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
+## Závěr
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.
 

From 69aafd3c7e15a3c31a78a58cd55e274138c8285d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:48 -0500
Subject: [PATCH 1235/1325] New translations triggers-example.mdx (German)

---
 website/pages/de/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/de/sps/triggers-example.mdx b/website/pages/de/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/de/sps/triggers-example.mdx
+++ b/website/pages/de/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 3fb82fb1cf93f713585058bdee6ed7c40064368c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:49 -0500
Subject: [PATCH 1236/1325] New translations triggers-example.mdx (Italian)

---
 website/pages/it/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/it/sps/triggers-example.mdx b/website/pages/it/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/it/sps/triggers-example.mdx
+++ b/website/pages/it/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 6752e74855aa76ed4c2c214d55847af323534134 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:50 -0500
Subject: [PATCH 1237/1325] New translations triggers-example.mdx (Japanese)

---
 website/pages/ja/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/ja/sps/triggers-example.mdx b/website/pages/ja/sps/triggers-example.mdx
index d8d61566295e..7c513edec723 100644
--- a/website/pages/ja/sps/triggers-example.mdx
+++ b/website/pages/ja/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## 前提条件
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 05ed8aa940769cd9f0b1115afc60de6e5ae79afd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:51 -0500
Subject: [PATCH 1238/1325] New translations triggers-example.mdx (Korean)

---
 website/pages/ko/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/ko/sps/triggers-example.mdx b/website/pages/ko/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/ko/sps/triggers-example.mdx
+++ b/website/pages/ko/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 32f774a063251d713bbdc590528e4d82a35a64aa Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:52 -0500
Subject: [PATCH 1239/1325] New translations triggers-example.mdx (Dutch)

---
 website/pages/nl/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/nl/sps/triggers-example.mdx b/website/pages/nl/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/nl/sps/triggers-example.mdx
+++ b/website/pages/nl/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 3c2db04b250ca5cea757fe10b8ad636e5face99c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:53 -0500
Subject: [PATCH 1240/1325] New translations triggers-example.mdx (Polish)

---
 website/pages/pl/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/pl/sps/triggers-example.mdx b/website/pages/pl/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/pl/sps/triggers-example.mdx
+++ b/website/pages/pl/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From a843f137ccd4853fb06a8ee85f47d4c32131a2d3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:54 -0500
Subject: [PATCH 1241/1325] New translations triggers-example.mdx (Portuguese)

---
 website/pages/pt/sps/triggers-example.mdx | 33 ++++++++++++-----------
 1 file changed, 18 insertions(+), 15 deletions(-)

diff --git a/website/pages/pt/sps/triggers-example.mdx b/website/pages/pt/sps/triggers-example.mdx
index d8d61566295e..503fcdeab65e 100644
--- a/website/pages/pt/sps/triggers-example.mdx
+++ b/website/pages/pt/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Pré-requisitos
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,7 +123,17 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
-## Conclusion
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
+## Conclusão
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.
 

From 466d22ce0fa1962cc6821fa63202fb339a852b2f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:56 -0500
Subject: [PATCH 1242/1325] New translations triggers-example.mdx (Swedish)

---
 website/pages/sv/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/sv/sps/triggers-example.mdx b/website/pages/sv/sps/triggers-example.mdx
index d8d61566295e..f0419707408a 100644
--- a/website/pages/sv/sps/triggers-example.mdx
+++ b/website/pages/sv/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Förutsättningar
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From f5252bb8d0375388021eecbf4e94671c69cda2a1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:57 -0500
Subject: [PATCH 1243/1325] New translations triggers-example.mdx (Turkish)

---
 website/pages/tr/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/tr/sps/triggers-example.mdx b/website/pages/tr/sps/triggers-example.mdx
index d8d61566295e..4301c586e460 100644
--- a/website/pages/tr/sps/triggers-example.mdx
+++ b/website/pages/tr/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Ön Koşullar
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 6ab98c6b79f7aa30d38ec8302ed34089f719fcc4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:58 -0500
Subject: [PATCH 1244/1325] New translations triggers-example.mdx (Ukrainian)

---
 website/pages/uk/sps/triggers-example.mdx | 29 +++++++++++++----------
 1 file changed, 16 insertions(+), 13 deletions(-)

diff --git a/website/pages/uk/sps/triggers-example.mdx b/website/pages/uk/sps/triggers-example.mdx
index d8d61566295e..495298871a22 100644
--- a/website/pages/uk/sps/triggers-example.mdx
+++ b/website/pages/uk/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
 ## Prerequisites
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 5684d4d0a2cb8bf2adf4cd77819e6c03e0752c24 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:56:59 -0500
Subject: [PATCH 1245/1325] New translations triggers-example.mdx (Chinese
 Simplified)

---
 website/pages/zh/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/zh/sps/triggers-example.mdx b/website/pages/zh/sps/triggers-example.mdx
index d8d61566295e..657a4d2402e2 100644
--- a/website/pages/zh/sps/triggers-example.mdx
+++ b/website/pages/zh/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## 先决条件
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 406b4e06d5145a38740bee9107ca3f13d2bc79df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:00 -0500
Subject: [PATCH 1246/1325] New translations triggers-example.mdx (Urdu
 (Pakistan))

---
 website/pages/ur/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/ur/sps/triggers-example.mdx b/website/pages/ur/sps/triggers-example.mdx
index d8d61566295e..604c864981b7 100644
--- a/website/pages/ur/sps/triggers-example.mdx
+++ b/website/pages/ur/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## شرطیں
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 6678ca18cc6016f558cb5fdae511f1d3e946e710 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:01 -0500
Subject: [PATCH 1247/1325] New translations triggers-example.mdx (Vietnamese)

---
 website/pages/vi/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/vi/sps/triggers-example.mdx b/website/pages/vi/sps/triggers-example.mdx
index d8d61566295e..3ed429e6133b 100644
--- a/website/pages/vi/sps/triggers-example.mdx
+++ b/website/pages/vi/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## Điều kiện tiên quyết
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 43d6970049262ebea2dbe67d1d6956d9570970d6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:02 -0500
Subject: [PATCH 1248/1325] New translations triggers-example.mdx (Marathi)

---
 website/pages/mr/sps/triggers-example.mdx | 31 +++++++++++++----------
 1 file changed, 17 insertions(+), 14 deletions(-)

diff --git a/website/pages/mr/sps/triggers-example.mdx b/website/pages/mr/sps/triggers-example.mdx
index d8d61566295e..7ea6674d7884 100644
--- a/website/pages/mr/sps/triggers-example.mdx
+++ b/website/pages/mr/sps/triggers-example.mdx
@@ -1,8 +1,8 @@
 ---
-title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
 ---
 
-## Prerequisites
+## पूर्वतयारी
 
 Before starting, make sure to:
 
@@ -11,6 +11,8 @@ Before starting, make sure to:
 
 ## Step 1: Initialize Your Project
 
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
 1. Open your Dev Container and run the following command to initialize your project:
 
    ```bash
@@ -18,6 +20,7 @@ Before starting, make sure to:
    ```
 
 2. Select the "minimal" project option.
+
 3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
 
 ```yaml
@@ -87,17 +90,7 @@ type MyTransfer @entity {
 
 This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
 
-## Step 4: Generate Protobuf Files
-
-To generate Protobuf objects in AssemblyScript, run the following command:
-
-```bash
-npm run protogen
-```
-
-This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
-
-## Step 5: Handle Substreams Data in `mappings.ts`
+## Step 4: Handle Substreams Data in `mappings.ts`
 
 With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
 
@@ -120,7 +113,7 @@ export function handleTriggers(bytes: Uint8Array): void {
       entity.designation = event.transfer!.accounts!.destination
 
       if (event.transfer!.accounts!.signer!.single != null) {
-        entity.signers = [event.transfer!.accounts!.signer!.single.signer]
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
       } else if (event.transfer!.accounts!.signer!.multisig != null) {
         entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
       }
@@ -130,6 +123,16 @@ export function handleTriggers(bytes: Uint8Array): void {
 }
 ```
 
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
 ## Conclusion
 
 You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.

From 4f32963115392ba7d39791274383f2fbd616822b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:03 -0500
Subject: [PATCH 1249/1325] New translations triggers-example.mdx (Swahili)

---
 website/pages/sw/sps/triggers-example.mdx | 140 ++++++++++++++++++++++
 1 file changed, 140 insertions(+)
 create mode 100644 website/pages/sw/sps/triggers-example.mdx

diff --git a/website/pages/sw/sps/triggers-example.mdx b/website/pages/sw/sps/triggers-example.mdx
new file mode 100644
index 000000000000..495298871a22
--- /dev/null
+++ b/website/pages/sw/sps/triggers-example.mdx
@@ -0,0 +1,140 @@
+---
+title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+---
+
+## Prerequisites
+
+Before starting, make sure to:
+
+- Complete the [Getting Started Guide](https://github.com/streamingfast/substreams-starter) to set up your development environment using a Dev Container.
+- Be familiar with The Graph and basic blockchain concepts such as transactions and Protobufs.
+
+## Step 1: Initialize Your Project
+
+<VideoEmbed youtube="RmKi-Nq9E_A" />
+
+1. Open your Dev Container and run the following command to initialize your project:
+
+   ```bash
+   substreams init
+   ```
+
+2. Select the "minimal" project option.
+
+3. Replace the contents of the generated `substreams.yaml` file with the following configuration, which filters transactions for the Orca account on the SPL token program ID:
+
+```yaml
+specVersion: v0.1.0
+package:
+  name: my_project_sol
+  version: v0.1.0
+
+imports: # Pass your spkg of interest
+  solana: https://github.com/streamingfast/substreams-solana-spl-token/raw/master/tokens/solana-spl-token-v0.1.0.spkg
+
+modules:
+  - name: map_spl_transfers
+    use: solana:map_block # Select corresponding modules available within your spkg
+    initialBlock: 260000082
+
+  - name: map_transactions_by_programid
+    use: solana:solana:transactions_by_programid_without_votes
+
+network: solana-mainnet-beta
+
+params: # Modify the param fields to meet your needs
+  # For program_id: TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA
+  map_spl_transfers: token_contract:orcaEKTdK7LKz57vaAYr9QeNsVEPfiu6QeMU1kektZE
+```
+
+## Step 2: Generate the Subgraph Manifest
+
+Once the project is initialized, generate a subgraph manifest by running the following command in the Dev Container:
+
+```bash
+substreams codegen subgraph
+```
+
+You will generate a`subgraph.yaml` manifest which imports the Substreams package as a data source:
+
+```yaml
+---
+dataSources:
+  - kind: substreams
+    name: my_project_sol
+    network: solana-mainnet-beta
+    source:
+      package:
+        moduleName: map_spl_transfers # Module defined in the substreams.yaml
+        file: ./my-project-sol-v0.1.0.spkg
+    mapping:
+      apiVersion: 0.0.7
+      kind: substreams/graph-entities
+      file: ./src/mappings.ts
+      handler: handleTriggers
+```
+
+## Step 3: Define Entities in `schema.graphql`
+
+Define the fields you want to save in your subgraph entities by updating the `schema.graphql` file. Here is an example:
+
+```graphql
+type MyTransfer @entity {
+  id: ID!
+  amount: String!
+  source: String!
+  designation: String!
+  signers: [String!]!
+}
+```
+
+This schema defines a `MyTransfer` entity with fields such as `id`, `amount`, `source`, `designation`, and `signers`.
+
+## Step 4: Handle Substreams Data in `mappings.ts`
+
+With the Protobuf objects generated, you can now handle the decoded Substreams data in your `mappings.ts` file found in the `./src` directory. The example below demonstrates how to extract to subgraph entities the non-derived transfers associated to the Orca account id:
+
+```ts
+import { Protobuf } from 'as-proto/assembly'
+import { Events as protoEvents } from './pb/sf/solana/spl/token/v1/Events'
+import { MyTransfer } from '../generated/schema'
+
+export function handleTriggers(bytes: Uint8Array): void {
+  const input: protoEvents = Protobuf.decode<protoEvents>(bytes, protoEvents.decode)
+
+  for (let i = 0; i < input.data.length; i++) {
+    const event = input.data[i]
+
+    if (event.transfer != null) {
+      let entity_id: string = `${event.txnId}-${i}`
+      const entity = new MyTransfer(entity_id)
+      entity.amount = event.transfer!.instruction!.amount.toString()
+      entity.source = event.transfer!.accounts!.source
+      entity.designation = event.transfer!.accounts!.destination
+
+      if (event.transfer!.accounts!.signer!.single != null) {
+        entity.signers = [event.transfer!.accounts!.signer!.single!.signer]
+      } else if (event.transfer!.accounts!.signer!.multisig != null) {
+        entity.signers = event.transfer!.accounts!.signer!.multisig!.signers
+      }
+      entity.save()
+    }
+  }
+}
+```
+
+## Step 5: Generate Protobuf Files
+
+To generate Protobuf objects in AssemblyScript, run the following command:
+
+```bash
+npm run protogen
+```
+
+This command converts the Protobuf definitions into AssemblyScript, allowing you to use them in the subgraph's handler.
+
+## Conclusion
+
+You’ve successfully set up a trigger-based Substreams-powered subgraph for a Solana SPL token. You can now further customize your schema, mappings, and modules to suit your specific use case.
+
+For more advanced customization and optimizations, check out the official [Substreams documentation](https://substreams.streamingfast.io/tutorials/solana).

From e78e59a607cc360a55ad0b4cfbbbf91a100623af Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:14 -0500
Subject: [PATCH 1250/1325] New translations triggers.mdx (Swahili)

---
 website/pages/sw/sps/triggers.mdx | 37 +++++++++++++++++++++++++++++++
 1 file changed, 37 insertions(+)
 create mode 100644 website/pages/sw/sps/triggers.mdx

diff --git a/website/pages/sw/sps/triggers.mdx b/website/pages/sw/sps/triggers.mdx
new file mode 100644
index 000000000000..ed19635d4768
--- /dev/null
+++ b/website/pages/sw/sps/triggers.mdx
@@ -0,0 +1,37 @@
+---
+title: Substreams Triggers
+---
+
+Custom triggers allow you to send data directly into your subgraph mappings file and entities (similar to tables and fields), enabling full use of the GraphQL layer. By importing the Protobuf definitions emitted by your Substreams module, you can receive and process this data within your subgraph’s handler, ensuring efficient and streamlined data management within the subgraph framework.
+
+> Note: If you haven’t already, visit one of the How-To Guides found [here](./introduction) to scaffold your first project in the Development Container.
+
+The following code demonstrates how to define a `handleTransactions` function in a subgraph handler. This function receives raw Substreams bytes as a parameter and decodes them into a `Transactions` object. For each transaction, a new subgraph entity is created.
+
+```tsx
+export function handleTransactions(bytes: Uint8Array): void {
+  let transactions = assembly.eth.transaction.v1.Transactions.decode(bytes.buffer).trasanctions // 1.
+  if (transactions.length == 0) {
+    log.info('No transactions found', [])
+    return
+  }
+
+  for (let i = 0; i < transactions.length; i++) {
+    // 2.
+    let transaction = transactions[i]
+
+    let entity = new Transaction(transaction.hash) // 3.
+    entity.from = transaction.from
+    entity.to = transaction.to
+    entity.save()
+  }
+}
+```
+
+Here's what you’re seeing in the `mappings.ts` file:
+
+1. The bytes containing Substreams data are decoded into the generated `Transactions` object, this object is used like any other AssemblyScript object
+2. Looping over the transactions
+3. Create a new subgraph entity for every transaction
+
+To go through a detailed example of a trigger-based subgraph, [click here](./triggers-example).

From 54a860cf1f35c66a716cf4373b4692f638da669f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:16 -0500
Subject: [PATCH 1251/1325] New translations multiple-networks.mdx (French)

---
 .../pages/fr/deploying/multiple-networks.mdx  | 99 +++++++++----------
 1 file changed, 49 insertions(+), 50 deletions(-)

diff --git a/website/pages/fr/deploying/multiple-networks.mdx b/website/pages/fr/deploying/multiple-networks.mdx
index dc2b8e533430..c4e981a572cc 100644
--- a/website/pages/fr/deploying/multiple-networks.mdx
+++ b/website/pages/fr/deploying/multiple-networks.mdx
@@ -1,37 +1,36 @@
 ---
-title: Deploying a Subgraph to Multiple Networks
+title: Déploiement d'un subgraph sur plusieurs réseaux
 ---
 
-This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
+Cette page explique comment déployer un subgraph sur plusieurs réseaux. Pour déployer un subgraph, vous devez premièrement installer le [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). Si vous n'avez pas encore créé de subgraph, consultez [Creation d'un subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Déploiement du subgraph sur plusieurs réseaux
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+Dans certains cas, vous souhaiterez déployer le même subgraph sur plusieurs réseaux sans dupliquer tout son code. Le principal défi qui en découle est que les adresses contractuelles sur ces réseaux sont différentes.
 
-### Using `graph-cli`
+### En utilisant `graph-cli`
 
-Both `graph build` (since `v0.29.0`) and `graph deploy` (since `v0.32.0`) accept two new options:
+Les commandes `graph build` (depuis la version `v0.29.0`) et `graph deploy` (depuis la version `v0.32.0`) acceptent deux nouvelles options:
 
 ```sh
 Options:
 
-      ...
-      --network <name>          Network configuration to use from the networks config file
-      --network-file <path>     Networks config file path (default: "./networks.json")
+      --network <nom>          Configuration du réseau à utiliser à partir du fichier de configuration des réseaux
+      --network-file <chemin>  Chemin du fichier de configuration des réseaux (par défaut : "./networks.json")
 ```
 
-You can use the `--network` option to specify a network configuration from a `json` standard file (defaults to `networks.json`) to easily update your subgraph during development.
+Vous pouvez utiliser l'option `--network` pour spécifier une configuration de réseau à partir d'un fichier standard `json` (par défaut networks.json) pour facilement mettre à jour votre subgraph pendant le développement.
 
-> Note: The `init` command will now auto-generate a `networks.json` based on the provided information. You will then be able to update existing or add additional networks.
+> Note : La commande `init` générera désormais automatiquement un fichier networks.json en se basant sur les informations fournies. Vous pourrez ensuite mettre à jour les réseaux existants ou en ajouter de nouveaux.
 
-If you don't have a `networks.json` file, you'll need to manually create one with the following structure:
+Si vous n'avez pas de fichier `networks.json`, vous devrez en créer un manuellement avec la structure suivante :
 
 ```json
 {
-    "network1": { // the network name
-        "dataSource1": { // the dataSource name
-            "address": "0xabc...", // the contract address (optional)
-            "startBlock": 123456 // the startBlock (optional)
+    "network1": { // le nom du réseau
+        "dataSource1": { // le nom de la source de données
+            "address": "0xabc...", // l'adresse du contrat (facultatif)
+            "startBlock": 123456 // le bloc de départ (facultatif)
         },
         "dataSource2": {
             "address": "0x123...",
@@ -52,9 +51,9 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 }
 ```
 
-> Note: You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
+> Note : Vous n'avez besoin de spécifier aucun des `templates` (si vous en avez) dans le fichier de configuration, uniquement les `dataSources`. Si des `templates` sont déclarés dans le fichier `subgraph.yaml`, leur réseau sera automatiquement mis à jour vers celui spécifié avec l'option `--network`.
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `sepolia` networks, and this is your `subgraph.yaml`:
+Supposons maintenant que vous souhaitiez déployer votre subgraph sur les réseaux `mainnet` et `sepolia`, et que ceci est votre fichier subgraph.yaml :
 
 ```yaml
 # ...
@@ -69,7 +68,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Voici à quoi devrait ressembler votre fichier de configuration réseau :
 
 ```json
 {
@@ -86,17 +85,17 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Nous pouvons maintenant exécuter l'une des commandes suivantes :
 
 ```sh
-# Using default networks.json file
+# En utilisant le fichier networks.json par défaut
 yarn build --network sepolia
 
-# Using custom named file
-yarn build --network sepolia --network-file path/to/config
+ # En utilisant un fichier personnalisé
+yarn build --network sepolia --network-file chemin/à/configurer
 ```
 
-The `build` command will update your `subgraph.yaml` with the `sepolia` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+La commande `build` mettra à jour votre fichier `subgraph.yaml` avec la configuration `sepolia` puis recompilera le subgraph. Votre fichier `subgraph.yaml` devrait maintenant ressembler à ceci:
 
 ```yaml
 # ...
@@ -111,23 +110,23 @@ dataSources:
       kind: ethereum/events
 ```
 
-Now you are ready to `yarn deploy`.
+Vous êtes maintenant prêt à utiliser la commande `yarn deploy`.
 
-> Note: As mentioned earlier, since `graph-cli 0.32.0` you can directly run `yarn deploy` with the `--network` option:
+> Note : Comme mentionné précédemment, depuis `graph-cli 0.32.0`, vous pouvez directement exécuter `yarn deploy` avec l'option `--network`:
 
 ```sh
-# Using default networks.json file
+# En utilisant le fichier networks.json par défaut
 yarn deploy --network sepolia
 
-# Using custom named file
-yarn deploy --network sepolia --network-file path/to/config
+ # En utilisant un fichier personnalisé
+yarn deploy --network sepolia --network-file chemin/à/configurer
 ```
 
-### Using subgraph.yaml template
+### Utilisation du modèle subgraph.yaml
 
-One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
+Une façon de paramétrer des aspects tels que les adresses de contrat en utilisant des versions plus anciennes de `graph-cli` est de générer des parties de celui-ci avec un système de creation de modèle comme [Mustache](https://mustache.github.io/) ou [Handlebars](https://handlebarsjs.com/).
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Sepolia using different contract addresses. You could then define two config files providing the addresses for each network:
+Pour illustrer cette approche, supposons qu'un subgraph doive être déployé sur le réseau principal (mainnet) et sur Sepolia en utilisant des adresses de contrat différentes. Vous pourriez alors définir deux fichiers de configuration fournissant les adresses pour chaque réseau :
 
 ```json
 {
@@ -136,7 +135,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+et
 
 ```json
 {
@@ -145,7 +144,7 @@ and
 }
 ```
 
-Along with that, you would substitute the network name and addresses in the manifest with variable placeholders `{{network}}` and `{{address}}` and rename the manifest to e.g. `subgraph.template.yaml`:
+Avec ceci, vous remplacerez le nom du réseau et les adresses dans le manifeste par des variables de type `{{network}}` et `{{address}}` et renommer le manifeste par exemple `subgraph.template.yaml`:
 
 ```yaml
 # ...
@@ -162,7 +161,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-In order to generate a manifest to either network, you could add two additional commands to `package.json` along with a dependency on `mustache`:
+Pour générer un manifeste pour l'un ou l'autre réseau, vous pourriez ajouter deux commandes supplémentaires au fichier `package.json` ainsi qu'une dépendance à `mustache` :
 
 ```json
 {
@@ -179,7 +178,7 @@ In order to generate a manifest to either network, you could add two additional
 }
 ```
 
-To deploy this subgraph for mainnet or Sepolia you would now simply run one of the two following commands:
+Pour déployer ce subgraph pour mainnet ou Sepolia, vous devez simplement exécuter l'une des deux commandes suivantes :
 
 ```sh
 # Mainnet:
@@ -189,29 +188,29 @@ yarn prepare:mainnet && yarn deploy
 yarn prepare:sepolia && yarn deploy
 ```
 
-A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
+Un exemple fonctionnel de ceci peut être trouvé [ici](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
 
-**Note:** This approach can also be applied to more complex situations, where it is necessary to substitute more than contract addresses and network names or where generating mappings or ABIs from templates as well.
+Note : Cette approche peut également être appliquée à des situations plus complexes, dans lesquelles il est nécessaire de remplacer plus que les adresses des contrats et les noms de réseau ou où il est nécessaire de générer des mappages ou alors des ABI à partir de modèles également.
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+Cela vous donnera le `chainHeadBlock` que vous pouvez comparer avec le `latestBlock` sur votre subgraph pour vérifier s'il est en retard. `synced` vous informe si le subgraph a déjà rattrapé la chaîne. `health` peut actuellement prendre les valeurs de `healthy` si aucune erreur ne s'est produite, ou `failed` s'il y a eu une erreur qui a stoppé la progression du subgraph. Dans ce cas, vous pouvez vérifier le champ `fatalError` pour les détails sur cette erreur.
 
-## Subgraph Studio subgraph archive policy
+## Politique d'archivage des subgraphs de Subgraph Studio
 
-A subgraph version in Studio is archived if and only if it meets the following criteria:
+Une version de subgraph dans Studio est archivée si et seulement si elle répond aux critères suivants :
 
-- The version is not published to the network (or pending publish)
-- The version was created 45 or more days ago
-- The subgraph hasn't been queried in 30 days
+- La version n'est pas publiée sur le réseau (ou en attente de publication)
+- La version a été créée il y a 45 jours ou plus
+- Le subgraph n'a pas été interrogé depuis 30 jours
 
-In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
+De plus, lorsqu'une nouvelle version est déployée, si le subgraph n'a pas été publié, la version N-2 du subgraph est archivée.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Chaque subgraph concerné par cette politique dispose d'une option de restauration de la version en question.
 
-## Checking subgraph health
+## Vérification de l'état des subgraphs
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Si un subgraph se synchronise avec succès, c'est un bon signe qu'il continuera à bien fonctionner pour toujours. Cependant, de nouveaux déclencheurs sur le réseau peuvent amener votre subgraph à rencontrer une condition d'erreur non testée ou il peut commencer à prendre du retard en raison de problèmes de performances ou de problèmes avec les opérateurs de nœuds.
 
-Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+Graph Node expose un endpoint GraphQL que vous pouvez interroger pour vérifier l'état de votre subgraph. Sur le service hébergé, il est disponible à l'adresse `https://api.thegraph.com/index-node/graphql`. Sur un nœud local, il est disponible sur le port `8030/graphql` par défaut. Le schéma complet de cet endpoint peut être trouvé [ici](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Voici un exemple de requête qui vérifie l'état de la version actuelle d'un subgraph:
 
 ```graphql
 {
@@ -238,4 +237,4 @@ Graph Node exposes a GraphQL endpoint which you can query to check the status of
 }
 ```
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+Cela vous donnera le `chainHeadBlock` que vous pouvez comparer avec le `latestBlock` sur votre subgraph pour vérifier s'il est en retard. `synced` vous informe si le subgraph a déjà rattrapé la chaîne. `health` peut actuellement prendre les valeurs de `healthy` si aucune erreur ne s'est produite, ou `failed` s'il y a eu une erreur qui a stoppé la progression du subgraph. Dans ce cas, vous pouvez vérifier le champ `fatalError` pour les détails sur cette erreur.

From 5289cbb565d6243389c3925ac8c8cfbc2b90803a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:16 -0500
Subject: [PATCH 1252/1325] New translations multiple-networks.mdx (Spanish)

---
 .../pages/es/deploying/multiple-networks.mdx  | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/es/deploying/multiple-networks.mdx b/website/pages/es/deploying/multiple-networks.mdx
index dc2b8e533430..276e10f5d0d4 100644
--- a/website/pages/es/deploying/multiple-networks.mdx
+++ b/website/pages/es/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Desplegando el subgráfo en múltiples redes
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+En algunos casos, querrás desplegar el mismo subgrafo en múltiples redes sin duplicar todo su código. El principal reto que conlleva esto es que las direcciones de los contratos en estas redes son diferentes.
 
 ### Using `graph-cli`
 
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Este es el aspecto que debe tener el archivo de configuración de tu red:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Ahora podemos ejecutar uno de los siguientes comandos:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Usando la plantilla subgraph.yaml
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+y
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## Política de archivo de subgrafos en Subgraph Studio
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Cada subgrafo afectado por esta política tiene una opción para recuperar la versión en cuestión.
 
-## Checking subgraph health
+## Comprobando la salud del subgrafo
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Si un subgrafo se sincroniza con éxito, es una buena señal de que seguirá funcionando bien para siempre. Sin embargo, los nuevos activadores en la red pueden hacer que tu subgrafo alcance una condición de error no probada o puede comenzar a retrasarse debido a problemas de rendimiento o problemas con los operadores de nodos.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From 92afe4f7cd5d7d20308ba5ffa6d9bb2ea85b2d2e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:18 -0500
Subject: [PATCH 1253/1325] New translations multiple-networks.mdx (Czech)

---
 .../pages/cs/deploying/multiple-networks.mdx  | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/cs/deploying/multiple-networks.mdx b/website/pages/cs/deploying/multiple-networks.mdx
index dc2b8e533430..0c53c9686fb4 100644
--- a/website/pages/cs/deploying/multiple-networks.mdx
+++ b/website/pages/cs/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Nasazení podgrafu do více sítí
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+V některých případech budete chtít nasadit stejný podgraf do více sítí, aniž byste museli duplikovat celý jeho kód. Hlavním problémem, který s tím souvisí, je skutečnost, že smluvní adresy v těchto sítích jsou různé.
 
 ### Using `graph-cli`
 
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Takto by měl vypadat konfigurační soubor sítě:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Nyní můžeme spustit jeden z následujících příkazů:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Použití šablony subgraph.yaml
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+a
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## Zásady archivace subgrafů Subgraph Studio
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Každý podgraf ovlivněný touto zásadou má možnost vrátit danou verzi zpět.
 
-## Checking subgraph health
+## Kontrola stavu podgrafů
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Pokud se podgraf úspěšně synchronizuje, je to dobré znamení, že bude dobře fungovat navždy. Nové spouštěče v síti však mohou způsobit, že se podgraf dostane do neověřeného chybového stavu, nebo může začít zaostávat kvůli problémům s výkonem či operátory uzlů.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From fb3b699202b7139e03ebc3a3273ba02f4097cfcf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:20 -0500
Subject: [PATCH 1254/1325] New translations multiple-networks.mdx (Italian)

---
 .../pages/it/deploying/multiple-networks.mdx  | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/it/deploying/multiple-networks.mdx b/website/pages/it/deploying/multiple-networks.mdx
index dc2b8e533430..a9385c5e1509 100644
--- a/website/pages/it/deploying/multiple-networks.mdx
+++ b/website/pages/it/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Distribuzione del subgraph su più reti
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+In alcuni casi, si desidera distribuire lo stesso subgraph su più reti senza duplicare tutto il suo codice. Il problema principale è che gli indirizzi dei contratti su queste reti sono diversi.
 
 ### Using `graph-cli`
 
@@ -28,10 +28,10 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 
 ```json
 {
-    "network1": { // the network name
-        "dataSource1": { // the dataSource name
-            "address": "0xabc...", // the contract address (optional)
-            "startBlock": 123456 // the startBlock (optional)
+    "network1": { // il nome della rete
+        "dataSource1": { // il nome del dataSource
+            "address": "0xabc...", // l'indirizzo del contratto (opzionale)
+            "startBlock": 123456 // il startBlock (opzionale)
         },
         "dataSource2": {
             "address": "0x123...",
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Questo è l'aspetto del file di configurazione delle reti:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Ora possiamo eseguire uno dei seguenti comandi:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Utilizzo del template subgraph.yaml
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+e
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## Politica di archiviazione dei subgraph di Subgraph Studio
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Ogni subgraph colpito da questa politica ha un'opzione per recuperare la versione in questione.
 
-## Checking subgraph health
+## Verifica dello stato di salute del subgraph
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Se un subgraph si sincronizza con successo, è un buon segno che continuerà a funzionare bene per sempre. Tuttavia, nuovi trigger sulla rete potrebbero far sì che il subgraph si trovi in una condizione di errore non testata o che inizi a rimanere indietro a causa di problemi di prestazioni o di problemi con gli operatori dei nodi.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From 5b098e4c4337cbe67d0b339347f28f6fc2d0d955 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:20 -0500
Subject: [PATCH 1255/1325] New translations multiple-networks.mdx (Japanese)

---
 .../pages/ja/deploying/multiple-networks.mdx  | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/ja/deploying/multiple-networks.mdx b/website/pages/ja/deploying/multiple-networks.mdx
index dc2b8e533430..d4f2935cb302 100644
--- a/website/pages/ja/deploying/multiple-networks.mdx
+++ b/website/pages/ja/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## サブグラフを複数のネットワークにデプロイする
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+場合によっては、すべてのコードを複製せずに、同じサブグラフを複数のネットワークに展開する必要があります。これに伴う主な課題は、これらのネットワークのコントラクト アドレスが異なることです。
 
 ### Using `graph-cli`
 
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+ネットワーク設定ファイルはこのようになっているはずです:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+これで、次のいずれかのコマンドを実行できるようになりました:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### subgraph.yamlテンプレートの使用
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+and/と
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## Subgraph Studio・サブグラフ・アーカイブポリシー
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+このポリシーで影響を受けるすべてのサブグラフには、問題のバージョンを戻すオプションがあります。
 
-## Checking subgraph health
+## サブグラフのヘルスチェック
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+サブグラフが正常に同期された場合、それはそれが永久に正常に動作し続けることを示す良い兆候です。ただし、ネットワーク上の新しいトリガーにより、サブグラフがテストされていないエラー状態に陥ったり、パフォーマンスの問題やノード オペレーターの問題により遅れが生じたりする可能性があります。
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From ddcd00d4b8c93a492315408ebd0d668de60a7938 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:23 -0500
Subject: [PATCH 1256/1325] New translations multiple-networks.mdx (Portuguese)

---
 .../pages/pt/deploying/multiple-networks.mdx  | 54 +++++++++----------
 1 file changed, 27 insertions(+), 27 deletions(-)

diff --git a/website/pages/pt/deploying/multiple-networks.mdx b/website/pages/pt/deploying/multiple-networks.mdx
index dc2b8e533430..91bdd9f3e94a 100644
--- a/website/pages/pt/deploying/multiple-networks.mdx
+++ b/website/pages/pt/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Como lançar o subgraph a várias redes
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+Em alguns casos, irá querer lançar o mesmo subgraph a várias redes sem duplicar o seu código completo. O grande desafio nisto é que os endereços de contrato nestas redes são diferentes.
 
 ### Using `graph-cli`
 
@@ -28,10 +28,10 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 
 ```json
 {
-    "network1": { // the network name
-        "dataSource1": { // the dataSource name
-            "address": "0xabc...", // the contract address (optional)
-            "startBlock": 123456 // the startBlock (optional)
+    "network1": { // nome da rede
+        "dataSource1": { // nome do dataSource
+            "address": "0xabc...", // endereço do contrato (opcional)
+            "startBlock": 123456 // bloco inicial (opcional)
         },
         "dataSource2": {
             "address": "0x123...",
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+O seu arquivo de config de redes deve ficar assim:
 
 ```json
 {
@@ -86,14 +86,14 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Agora podemos executar um dos seguintes comandos:
 
 ```sh
-# Using default networks.json file
+# Usar o arquivo networks.json padrão
 yarn build --network sepolia
 
-# Using custom named file
-yarn build --network sepolia --network-file path/to/config
+# Usar arquivo com nome personalizado
+yarn build --network sepolia --network-file local/do/config
 ```
 
 The `build` command will update your `subgraph.yaml` with the `sepolia` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
@@ -116,18 +116,18 @@ Now you are ready to `yarn deploy`.
 > Note: As mentioned earlier, since `graph-cli 0.32.0` you can directly run `yarn deploy` with the `--network` option:
 
 ```sh
-# Using default networks.json file
+# Usar o arquivo networks.json padrão
 yarn deploy --network sepolia
 
-# Using custom named file
-yarn deploy --network sepolia --network-file path/to/config
+# Usar arquivo com nome personalizado
+yarn deploy --network sepolia --network-file local/do/config
 ```
 
-### Using subgraph.yaml template
+### Como usar o template subgraph.yaml
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Sepolia using different contract addresses. You could then define two config files providing the addresses for each network:
+Por exemplo, vamos supor que um subgraph deve ser lançado à mainnet e à Sepolia, através de diferentes endereços de contratos. Então, seria possível definir dois arquivos de config ao fornecer os endereços para cada rede:
 
 ```json
 {
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+e
 
 ```json
 {
@@ -179,7 +179,7 @@ In order to generate a manifest to either network, you could add two additional
 }
 ```
 
-To deploy this subgraph for mainnet or Sepolia you would now simply run one of the two following commands:
+Para lançar este subgraph à mainnet ou à Sepolia, apenas um dos seguintes comandos precisaria ser executado:
 
 ```sh
 # Mainnet:
@@ -195,21 +195,21 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## Política de arqivamento do Subgraph Studio
 
-A subgraph version in Studio is archived if and only if it meets the following criteria:
+Uma versão de subgraph no Studio é arquivada se, e apenas se, atender aos seguintes critérios:
 
-- The version is not published to the network (or pending publish)
-- The version was created 45 or more days ago
-- The subgraph hasn't been queried in 30 days
+- A versão não foi publicada na rede (ou tem a publicação pendente)
+- A versão foi criada há 45 dias ou mais
+- O subgraph não foi consultado em 30 dias
 
-In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
+Além disto, quando uma nova versão é editada, se o subgraph ainda não foi publicado, então a versão N-2 do subgraph é arquivada.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Todos os subgraphs afetados por esta política têm a opção de trazer de volta a versão em questão.
 
-## Checking subgraph health
+## Como conferir a saúde do subgraph
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Se um subgraph for sincronizado com sucesso, isto indica que ele continuará a rodar bem para sempre. Porém, novos gatilhos na rede podem revelar uma condição de erro não testada, ou ele pode começar a se atrasar por problemas de desempenho ou com os operadores de nodes.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From e9135be2b7cf18cfca61bbe847f46995ec55fc83 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:24 -0500
Subject: [PATCH 1257/1325] New translations multiple-networks.mdx (Russian)

---
 .../pages/ru/deploying/multiple-networks.mdx  | 89 +++++++++----------
 1 file changed, 44 insertions(+), 45 deletions(-)

diff --git a/website/pages/ru/deploying/multiple-networks.mdx b/website/pages/ru/deploying/multiple-networks.mdx
index dc2b8e533430..9c790b17f559 100644
--- a/website/pages/ru/deploying/multiple-networks.mdx
+++ b/website/pages/ru/deploying/multiple-networks.mdx
@@ -1,30 +1,29 @@
 ---
-title: Deploying a Subgraph to Multiple Networks
+title: Развертывание субграфа в нескольких сетях
 ---
 
-This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
+На этой странице объясняется, как развернуть субграф в нескольких сетях. Чтобы развернуть субграф, сначала установите [Graph CLI] (https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). Если Вы еще не создали субграф, смотрите раздел [Создание субграфа] (/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Развертывание подграфа в нескольких сетях
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+В некоторых случаях вы захотите развернуть один и тот же подграф в нескольких сетях, не дублируя весь его код. Основная проблема, возникающая при этом, заключается в том, что адреса контрактов в этих сетях разные.
 
-### Using `graph-cli`
+### Использование `graph-cli`
 
-Both `graph build` (since `v0.29.0`) and `graph deploy` (since `v0.32.0`) accept two new options:
+Как `graph build` (начиная с `v0.29.0`), так и `graph deploy` (начиная с `v0.32.0`) допускают две новые опции:
 
 ```sh
-Options:
-
+Опции:
       ...
-      --network <name>          Network configuration to use from the networks config file
-      --network-file <path>     Networks config file path (default: "./networks.json")
+      --network <name> Конфигурация сети для использования из файла конфигурации сетей
+      --network-file <path> Путь к файлу конфигурации сетей (по умолчанию: "./networks.json")
 ```
 
-You can use the `--network` option to specify a network configuration from a `json` standard file (defaults to `networks.json`) to easily update your subgraph during development.
+Вы можете использовать опцию `--network` для указания конфигурации сети из стандартного файла `json` (по умолчанию используется `networks.json`), чтобы легко обновлять свой субграф во время разработки.
 
-> Note: The `init` command will now auto-generate a `networks.json` based on the provided information. You will then be able to update existing or add additional networks.
+> Примечание: Команда `init` теперь автоматически сгенерирует `networks.json` на основе предоставленной информации. Затем Вы сможете обновить существующие или добавить дополнительные сети.
 
-If you don't have a `networks.json` file, you'll need to manually create one with the following structure:
+Если у Вас нет файла `networks.json`, Вам нужно будет вручную создать его со следующей структурой:
 
 ```json
 {
@@ -52,9 +51,9 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 }
 ```
 
-> Note: You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
+> Примечание: Вам не нужно указывать ни один из `templates` (если они у Вас есть) в файле конфигурации, только `dataSources`. Если есть какие-либо `templates`, объявленные в файле `subgraph.yaml`, их сеть будет автоматически обновлена до указанной с помощью опции `--network`.
 
-Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `sepolia` networks, and this is your `subgraph.yaml`:
+Теперь давайте предположим, что Вы хотите иметь возможность развернуть свой субграф в сетях `mainnet` и `sepolia`, и это Ваш `subgraph.yaml`:
 
 ```yaml
 # ...
@@ -69,7 +68,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Вот как должен выглядеть файл конфигурации ваших сетей:
 
 ```json
 {
@@ -86,17 +85,17 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Теперь мы можем запустить одну из следующих команд:
 
 ```sh
-# Using default networks.json file
+# Использование стандартного файла networks.json
 yarn build --network sepolia
 
-# Using custom named file
+# Использование файла с пользовательским именем
 yarn build --network sepolia --network-file path/to/config
 ```
 
-The `build` command will update your `subgraph.yaml` with the `sepolia` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+Команда `build` обновит Ваш `subgraph.yaml` конфигурацией `sepolia`, а затем повторно скомпилирует субграф. Ваш файл `subgraph.yaml` теперь должен выглядеть следующим образом:
 
 ```yaml
 # ...
@@ -111,23 +110,23 @@ dataSources:
       kind: ethereum/events
 ```
 
-Now you are ready to `yarn deploy`.
+Теперь Вы готовы выполнить команду `yarn deploy`.
 
-> Note: As mentioned earlier, since `graph-cli 0.32.0` you can directly run `yarn deploy` with the `--network` option:
+> Примечание: Как упоминалось ранее, начиная с версии `graph-cli 0.32.0` Вы можете напрямую выполнить команду `yarn deploy` с опцией `--network`:
 
 ```sh
-# Using default networks.json file
+# Использование стандартного файла networks.json
 yarn deploy --network sepolia
 
-# Using custom named file
+# Использование файла с пользовательским именем
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Использование шаблона subgraph.yaml
 
-One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
+Одним из способов параметризации таких аспектов, как адреса контрактов, с использованием старых версий `graph-cli` является генерация его частей с помощью системы шаблонов, такой как [Mustache](https://mustache.github.io/) или [Handlebars](https://handlebarsjs.com/).
 
-To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Sepolia using different contract addresses. You could then define two config files providing the addresses for each network:
+Чтобы проиллюстрировать этот подход, давайте предположим, что субграф должен быть развернут в майннете и в сети Sepolia с использованием разных адресов контракта. Затем Вы можете определить два файла конфигурации, содержащие адреса для каждой сети:
 
 ```json
 {
@@ -136,7 +135,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+и
 
 ```json
 {
@@ -145,7 +144,7 @@ and
 }
 ```
 
-Along with that, you would substitute the network name and addresses in the manifest with variable placeholders `{{network}}` and `{{address}}` and rename the manifest to e.g. `subgraph.template.yaml`:
+Наряду с этим, необходимо заменить имя сети и адреса в манифесте на variable placeholders `{{network}}` и `{{address}}` и переименовать манифест, например, `subgraph.template.yaml`:
 
 ```yaml
 # ...
@@ -162,7 +161,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-In order to generate a manifest to either network, you could add two additional commands to `package.json` along with a dependency on `mustache`:
+Чтобы сгенерировать манифест для любой сети, можно добавить две дополнительные команды в `package.json` вместе с зависимостью от `mustache`:
 
 ```json
 {
@@ -179,7 +178,7 @@ In order to generate a manifest to either network, you could add two additional
 }
 ```
 
-To deploy this subgraph for mainnet or Sepolia you would now simply run one of the two following commands:
+Чтобы развернуть этот субграф для основной сети или сети Sepolia, Вам нужно просто запустить одну из двух следующих команд:
 
 ```sh
 # Mainnet:
@@ -189,29 +188,29 @@ yarn prepare:mainnet && yarn deploy
 yarn prepare:sepolia && yarn deploy
 ```
 
-A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
+Наглядный пример можно найти [здесь](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
 
-**Note:** This approach can also be applied to more complex situations, where it is necessary to substitute more than contract addresses and network names or where generating mappings or ABIs from templates as well.
+**Примечание:** Этот подход также можно применять в более сложных ситуациях, когда необходимо заменить не только адреса контрактов и сетевые имена, но и сгенерировать мэппинги или ABI из шаблонов.
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+Это предоставит Вам `chainHeadBlock`, который Вы сможете сравнить с `latestBlock` своего субграфа, чтобы проверить, не отстает ли он. `synced` сообщает, попал ли субграф в чейн. `health` в настоящее время может принимать значения `healthy`, если ошибки отсутствуют, или `failed`, если произошла ошибка, остановившая работу субграфа. В этом случае Вы можете проверить поле `fatalError` для получения подробной информации об этой ошибке.
 
-## Subgraph Studio subgraph archive policy
+## Политика архивирования подграфов в Subgraph Studio
 
-A subgraph version in Studio is archived if and only if it meets the following criteria:
+Версия субграфа в Studio архивируется, если и только если выполняются следующие критерии:
 
-- The version is not published to the network (or pending publish)
-- The version was created 45 or more days ago
-- The subgraph hasn't been queried in 30 days
+- Версия не опубликована в сети (или ожидает публикации)
+- Версия была создана 45 или более дней назад
+- Субграф не запрашивался в течение 30 дней
 
-In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
+Кроме того, когда развертывается новая версия, если субграф не был опубликован, то версия N-2 субграфа архивируется.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+У каждого подграфа, затронутого этой политикой, есть возможность вернуть соответствующую версию обратно.
 
-## Checking subgraph health
+## Проверка работоспособности подграфа
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Если подграф успешно синхронизируется, это хороший признак того, что он будет работать надёжно. Однако новые триггеры в сети могут привести к тому, что ваш подграф попадет в состояние непроверенной ошибки, или он может начать отставать из-за проблем с производительностью или проблем с операторами нод.
 
-Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+Graph Node предоставляет конечную точку GraphQL, которую Вы можете запросить для проверки статуса своего субграфа. В хостинговом сервисе он доступен по адресу `https://api.thegraph.com/index-node/graphql`. На локальной ноде он по умолчанию доступен через порт `8030/graphql`. Полную схему для этой конечной точки можно найти [здесь](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Вот пример запроса, проверяющего состояние текущей версии субграфа:
 
 ```graphql
 {
@@ -238,4 +237,4 @@ Graph Node exposes a GraphQL endpoint which you can query to check the status of
 }
 ```
 
-This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+Это предоставит Вам `chainHeadBlock`, который Вы сможете сравнить с `latestBlock` своего субграфа, чтобы проверить, не отстает ли он. `synced` сообщает, попал ли субграф в чейн. `health` в настоящее время может принимать значения `healthy`, если ошибки отсутствуют, или `failed`, если произошла ошибка, остановившая работу субграфа. В этом случае Вы можете проверить поле `fatalError` для получения подробной информации об этой ошибке.

From bfb6ec99de5096c862aac4a55e0d1ed78bd15921 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:25 -0500
Subject: [PATCH 1258/1325] New translations multiple-networks.mdx (Swedish)

---
 .../pages/sv/deploying/multiple-networks.mdx  | 28 +++++++++----------
 1 file changed, 14 insertions(+), 14 deletions(-)

diff --git a/website/pages/sv/deploying/multiple-networks.mdx b/website/pages/sv/deploying/multiple-networks.mdx
index dc2b8e533430..f35ab9327a4c 100644
--- a/website/pages/sv/deploying/multiple-networks.mdx
+++ b/website/pages/sv/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## Distribuera undergrafen till flera nätverk
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+I vissa fall vill du distribuera samma undergraf till flera nätverk utan att duplicera all dess kod. Den största utmaningen med detta är att kontraktsadresserna på dessa nätverk är olika.
 
 ### Using `graph-cli`
 
@@ -28,10 +28,10 @@ If you don't have a `networks.json` file, you'll need to manually create one wit
 
 ```json
 {
-    "network1": { // the network name
-        "dataSource1": { // the dataSource name
-            "address": "0xabc...", // the contract address (optional)
-            "startBlock": 123456 // the startBlock (optional)
+    "network1": { // nätverkets namn
+        "dataSource1": { // namn på datakällan
+            "address": "0xabc...", // Avtalets adress (frivillig uppgift)
+            "startBlock": 123456 // startBlock (valfritt)
         },
         "dataSource2": {
             "address": "0x123...",
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+Så här ska nätverkets konfigurationsfil se ut:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+Nu kan vi köra något av följande kommandon:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Använda subgraph.yaml mallen
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+och
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## Subgraph Studio subgraf arkivpolitik
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+Varje subgraf som påverkas av denna policy har en möjlighet att ta tillbaka versionen i fråga.
 
-## Checking subgraph health
+## Kontroll av undergrafens hälsa
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+Om en subgraf synkroniseras framgångsrikt är det ett gott tecken på att den kommer att fortsätta att fungera bra för alltid. Nya triggers i nätverket kan dock göra att din subgraf stöter på ett otestat feltillstånd eller så kan den börja halka efter på grund av prestandaproblem eller problem med nodoperatörerna.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From ebf8ffad2c85e2d91f4ae42d03d9eb8207ff0cac Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:27 -0500
Subject: [PATCH 1259/1325] New translations multiple-networks.mdx (Chinese
 Simplified)

---
 .../pages/zh/deploying/multiple-networks.mdx  | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/zh/deploying/multiple-networks.mdx b/website/pages/zh/deploying/multiple-networks.mdx
index dc2b8e533430..77292d1df580 100644
--- a/website/pages/zh/deploying/multiple-networks.mdx
+++ b/website/pages/zh/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## 将子图部署到多个网络
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+在某些情况下，您需要将相同的子图部署到多个网络，而不复制其所有代码。随之而来的主要挑战是这些网络上的合约地址不同。
 
 ### Using `graph-cli`
 
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+您的网络配置文件应该是这样的:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+现在我们可以运行以下命令之一:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### 使用 subgraph.yaml 模板
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+和
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## 子图工作室子图封存策略
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+受此策略影响的每个子图都有一个选项，可以回复有问题的版本。
 
-## Checking subgraph health
+## 检查子图状态
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+如果子图成功同步，这是一个好信号，表明它将永远运行良好。然而，网络上的新触发器可能会导致子图遇到未经测试的错误条件，或者由于性能问题或节点操作符的问题，子图开始落后。
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From d4d1ef4c9a82538b0d5d2889d690d038fd785fbf Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:27 -0500
Subject: [PATCH 1260/1325] New translations multiple-networks.mdx (Urdu
 (Pakistan))

---
 .../pages/ur/deploying/multiple-networks.mdx  | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/ur/deploying/multiple-networks.mdx b/website/pages/ur/deploying/multiple-networks.mdx
index dc2b8e533430..5e4fddd79b4f 100644
--- a/website/pages/ur/deploying/multiple-networks.mdx
+++ b/website/pages/ur/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## سب گراف کو متعدد نیٹ ورکس پر تعینات کرنا
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+کچھ معاملات میں، آپ ایک ہی سب گراف کو متعدد نیٹ ورکس پر اس کے تمام کوڈ کی نقل کیے بغیر تعینات کرنا چاہیں گے۔ اس کے ساتھ آنے والا بنیادی چیلنج یہ ہے کہ ان نیٹ ورکس پر کنٹریکٹ ایڈریس مختلف ہیں.
 
 ### Using `graph-cli`
 
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+آپ کے نیٹ ورکس کی تشکیل فائل کو اس طرح نظر آنا چاہئے:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+اب ہم زیل میں دی گئ کمانڈز میں سے ایک چلا سکتے ہیں:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### Subgraph.yaml ٹیمپلیٹ استعمال کرنا
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+اور
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## سب گراف سٹوڈیو سب گراف آرکائیو پالیسی
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+اس پالیسی سے متاثر ہونے والے ہر سب گراف کے پاس زیر بحث ورژن کو واپس لانے کا اختیار ہے.
 
-## Checking subgraph health
+## سب گراف کی صحت کی جانچ کرنا
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+اگر ایک سب گراف کامیابی کے ساتھ مطابقت پذیر ہوتا ہے، تو یہ ایک اچھی علامت ہے کہ یہ ہمیشہ کے لیے اچھی طرح چلتا رہے گا۔ تاہم، نیٹ ورک پر نئے محرکات آپ کے سب گراف کو بغیر جانچ کی خرابی کی حالت کو نشانہ بنا سکتے ہیں یا کارکردگی کے مسائل یا نوڈ آپریٹرز کے ساتھ مسائل کی وجہ سے یہ پیچھے پڑنا شروع کر سکتا ہے.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From 627c2bca9ec50ea99226857e2124aa9136f8d809 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:29 -0500
Subject: [PATCH 1261/1325] New translations multiple-networks.mdx (Marathi)

---
 .../pages/mr/deploying/multiple-networks.mdx  | 20 +++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

diff --git a/website/pages/mr/deploying/multiple-networks.mdx b/website/pages/mr/deploying/multiple-networks.mdx
index dc2b8e533430..ab644e836b37 100644
--- a/website/pages/mr/deploying/multiple-networks.mdx
+++ b/website/pages/mr/deploying/multiple-networks.mdx
@@ -4,9 +4,9 @@ title: Deploying a Subgraph to Multiple Networks
 
 This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
 
-## Deploying the subgraph to multiple networks
+## एकाधिक नेटवर्कवर सबग्राफ तैनात करणे
 
-In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+काही प्रकरणांमध्ये, तुम्हाला समान सबग्राफ एकाधिक नेटवर्कवर त्याच्या कोडची नक्कल न करता उपयोजित करायचा असेल. यासह येणारे मुख्य आव्हान हे आहे की या नेटवर्कवरील कराराचे पत्ते वेगळे आहेत.
 
 ### Using `graph-cli`
 
@@ -69,7 +69,7 @@ dataSources:
       kind: ethereum/events
 ```
 
-This is what your networks config file should look like:
+तुमची नेटवर्क कॉन्फिगरेशन फाइल अशी दिसली पाहिजे:
 
 ```json
 {
@@ -86,7 +86,7 @@ This is what your networks config file should look like:
 }
 ```
 
-Now we can run one of the following commands:
+आता आपण खालीलपैकी एक कमांड रन करू शकतो:
 
 ```sh
 # Using default networks.json file
@@ -123,7 +123,7 @@ yarn deploy --network sepolia
 yarn deploy --network sepolia --network-file path/to/config
 ```
 
-### Using subgraph.yaml template
+### वापरत आहे subgraph.yaml टेम्पलेट
 
 One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
 
@@ -136,7 +136,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-and
+आणि
 
 ```json
 {
@@ -195,7 +195,7 @@ A working example of this can be found [here](https://github.com/graphprotocol/e
 
 This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
 
-## Subgraph Studio subgraph archive policy
+## सबग्राफ स्टुडिओ सबग्राफ संग्रहण धोरण
 
 A subgraph version in Studio is archived if and only if it meets the following criteria:
 
@@ -205,11 +205,11 @@ A subgraph version in Studio is archived if and only if it meets the following c
 
 In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
 
-Every subgraph affected with this policy has an option to bring the version in question back.
+या धोरणामुळे प्रभावित झालेल्या प्रत्येक सबग्राफला प्रश्नातील आवृत्ती परत आणण्याचा पर्याय आहे.
 
-## Checking subgraph health
+## सबग्राफ आरोग्य तपासत आहे
 
-If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+जर सबग्राफ यशस्वीरित्या समक्रमित झाला, तर ते कायमचे चांगले चालत राहण्याचे चांगले चिन्ह आहे. तथापि, नेटवर्कवरील नवीन ट्रिगर्समुळे तुमच्या सबग्राफची चाचणी न केलेली त्रुटी स्थिती येऊ शकते किंवा कार्यप्रदर्शन समस्यांमुळे किंवा नोड ऑपरेटरमधील समस्यांमुळे ते मागे पडू शकते.
 
 Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
 

From 9f45a0c478743a6048116f44313e8e8c8b9cbf70 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:30 -0500
Subject: [PATCH 1262/1325] New translations multiple-networks.mdx (Swahili)

---
 .../pages/sw/deploying/multiple-networks.mdx  | 241 ++++++++++++++++++
 1 file changed, 241 insertions(+)
 create mode 100644 website/pages/sw/deploying/multiple-networks.mdx

diff --git a/website/pages/sw/deploying/multiple-networks.mdx b/website/pages/sw/deploying/multiple-networks.mdx
new file mode 100644
index 000000000000..dc2b8e533430
--- /dev/null
+++ b/website/pages/sw/deploying/multiple-networks.mdx
@@ -0,0 +1,241 @@
+---
+title: Deploying a Subgraph to Multiple Networks
+---
+
+This page explains how to deploy a subgraph to multiple networks. To deploy a subgraph you need to first install the [Graph CLI](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli). If you have not created a subgraph already, see [Creating a subgraph](/developing/creating-a-subgraph).
+
+## Deploying the subgraph to multiple networks
+
+In some cases, you will want to deploy the same subgraph to multiple networks without duplicating all of its code. The main challenge that comes with this is that the contract addresses on these networks are different.
+
+### Using `graph-cli`
+
+Both `graph build` (since `v0.29.0`) and `graph deploy` (since `v0.32.0`) accept two new options:
+
+```sh
+Options:
+
+      ...
+      --network <name>          Network configuration to use from the networks config file
+      --network-file <path>     Networks config file path (default: "./networks.json")
+```
+
+You can use the `--network` option to specify a network configuration from a `json` standard file (defaults to `networks.json`) to easily update your subgraph during development.
+
+> Note: The `init` command will now auto-generate a `networks.json` based on the provided information. You will then be able to update existing or add additional networks.
+
+If you don't have a `networks.json` file, you'll need to manually create one with the following structure:
+
+```json
+{
+    "network1": { // the network name
+        "dataSource1": { // the dataSource name
+            "address": "0xabc...", // the contract address (optional)
+            "startBlock": 123456 // the startBlock (optional)
+        },
+        "dataSource2": {
+            "address": "0x123...",
+            "startBlock": 123444
+        }
+    },
+    "network2": {
+        "dataSource1": {
+            "address": "0x987...",
+            "startBlock": 123
+        },
+        "dataSource2": {
+            "address": "0xxyz..",
+            "startBlock": 456
+        }
+    },
+    ...
+}
+```
+
+> Note: You don't have to specify any of the `templates` (if you have any) in the config file, only the `dataSources`. If there are any `templates` declared in the `subgraph.yaml` file, their network will be automatically updated to the one specified with the `--network` option.
+
+Now, let's assume you want to be able to deploy your subgraph to the `mainnet` and `sepolia` networks, and this is your `subgraph.yaml`:
+
+```yaml
+# ...
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    source:
+      address: '0x123...'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+```
+
+This is what your networks config file should look like:
+
+```json
+{
+  "mainnet": {
+    "Gravity": {
+      "address": "0x123..."
+    }
+  },
+  "sepolia": {
+    "Gravity": {
+      "address": "0xabc..."
+    }
+  }
+}
+```
+
+Now we can run one of the following commands:
+
+```sh
+# Using default networks.json file
+yarn build --network sepolia
+
+# Using custom named file
+yarn build --network sepolia --network-file path/to/config
+```
+
+The `build` command will update your `subgraph.yaml` with the `sepolia` configuration and then re-compile the subgraph. Your `subgraph.yaml` file now should look like this:
+
+```yaml
+# ...
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: sepolia
+    source:
+      address: '0xabc...'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+```
+
+Now you are ready to `yarn deploy`.
+
+> Note: As mentioned earlier, since `graph-cli 0.32.0` you can directly run `yarn deploy` with the `--network` option:
+
+```sh
+# Using default networks.json file
+yarn deploy --network sepolia
+
+# Using custom named file
+yarn deploy --network sepolia --network-file path/to/config
+```
+
+### Using subgraph.yaml template
+
+One way to parameterize aspects like contract addresses using older `graph-cli` versions is to generate parts of it with a templating system like [Mustache](https://mustache.github.io/) or [Handlebars](https://handlebarsjs.com/).
+
+To illustrate this approach, let's assume a subgraph should be deployed to mainnet and Sepolia using different contract addresses. You could then define two config files providing the addresses for each network:
+
+```json
+{
+  "network": "mainnet",
+  "address": "0x123..."
+}
+```
+
+and
+
+```json
+{
+  "network": "sepolia",
+  "address": "0xabc..."
+}
+```
+
+Along with that, you would substitute the network name and addresses in the manifest with variable placeholders `{{network}}` and `{{address}}` and rename the manifest to e.g. `subgraph.template.yaml`:
+
+```yaml
+# ...
+dataSources:
+  - kind: ethereum/contract
+    name: Gravity
+    network: mainnet
+    network: {{network}}
+    source:
+      address: '0x2E645469f354BB4F5c8a05B3b30A929361cf77eC'
+      address: '{{address}}'
+      abi: Gravity
+    mapping:
+      kind: ethereum/events
+```
+
+In order to generate a manifest to either network, you could add two additional commands to `package.json` along with a dependency on `mustache`:
+
+```json
+{
+  ...
+  "scripts": {
+    ...
+    "prepare:mainnet": "mustache config/mainnet.json subgraph.template.yaml > subgraph.yaml",
+    "prepare:sepolia": "mustache config/sepolia.json subgraph.template.yaml > subgraph.yaml"
+  },
+  "devDependencies": {
+    ...
+    "mustache": "^3.1.0"
+  }
+}
+```
+
+To deploy this subgraph for mainnet or Sepolia you would now simply run one of the two following commands:
+
+```sh
+# Mainnet:
+yarn prepare:mainnet && yarn deploy
+
+# Sepolia:
+yarn prepare:sepolia && yarn deploy
+```
+
+A working example of this can be found [here](https://github.com/graphprotocol/example-subgraph/tree/371232cf68e6d814facf5e5413ad0fef65144759).
+
+**Note:** This approach can also be applied to more complex situations, where it is necessary to substitute more than contract addresses and network names or where generating mappings or ABIs from templates as well.
+
+This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.
+
+## Subgraph Studio subgraph archive policy
+
+A subgraph version in Studio is archived if and only if it meets the following criteria:
+
+- The version is not published to the network (or pending publish)
+- The version was created 45 or more days ago
+- The subgraph hasn't been queried in 30 days
+
+In addition, when a new version is deployed, if the subgraph has not been published, then the N-2 version of the subgraph is archived.
+
+Every subgraph affected with this policy has an option to bring the version in question back.
+
+## Checking subgraph health
+
+If a subgraph syncs successfully, that is a good sign that it will continue to run well forever. However, new triggers on the network might cause your subgraph to hit an untested error condition or it may start to fall behind due to performance issues or issues with the node operators.
+
+Graph Node exposes a GraphQL endpoint which you can query to check the status of your subgraph. On the hosted service, it is available at `https://api.thegraph.com/index-node/graphql`. On a local node, it is available on port `8030/graphql` by default. The full schema for this endpoint can be found [here](https://github.com/graphprotocol/graph-node/blob/master/server/index-node/src/schema.graphql). Here is an example query that checks the status of the current version of a subgraph:
+
+```graphql
+{
+  indexingStatusForCurrentVersion(subgraphName: "org/subgraph") {
+    synced
+    health
+    fatalError {
+      message
+      block {
+        number
+        hash
+      }
+      handler
+    }
+    chains {
+      chainHeadBlock {
+        number
+      }
+      latestBlock {
+        number
+      }
+    }
+  }
+}
+```
+
+This will give you the `chainHeadBlock` which you can compare with the `latestBlock` on your subgraph to check if it is running behind. `synced` informs if the subgraph has ever caught up to the chain. `health` can currently take the values of `healthy` if no errors occurred, or `failed` if there was an error which halted the progress of the subgraph. In this case, you can check the `fatalError` field for details on this error.

From 561092f3a97dd6e7ad7193aef721e45f6f0b9909 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:31 -0500
Subject: [PATCH 1263/1325] New translations transfer-a-subgraph.mdx (Romanian)

---
 .../pages/ro/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/ro/managing/transfer-a-subgraph.mdx b/website/pages/ro/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/ro/managing/transfer-a-subgraph.mdx
+++ b/website/pages/ro/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 9e13e42be576b8d60846c1629faf52eb61c1def8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:32 -0500
Subject: [PATCH 1264/1325] New translations transfer-a-subgraph.mdx (French)

---
 .../pages/fr/managing/transfer-a-subgraph.mdx | 61 ++++++-------------
 1 file changed, 19 insertions(+), 42 deletions(-)

diff --git a/website/pages/fr/managing/transfer-a-subgraph.mdx b/website/pages/fr/managing/transfer-a-subgraph.mdx
index c4060284d5d9..4f12b5a94032 100644
--- a/website/pages/fr/managing/transfer-a-subgraph.mdx
+++ b/website/pages/fr/managing/transfer-a-subgraph.mdx
@@ -1,65 +1,42 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transférer un Subgraph
 ---
 
-## Transferring ownership of a subgraph
+Les subgraphs publiés sur le réseau décentralisé possèdent un NFT minté à l'adresse qui a publié le subgraph. Le NFT est basé sur la norme ERC721, ce qui facilite les transferts entre comptes sur The Graph Network.
 
-Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+## Rappels
 
-**Please note the following:**
+- Quiconque possède le NFT contrôle le subgraph.
+- Si le propriétaire décide de vendre ou de transférer le NFT, il ne pourra plus éditer ou mettre à jour ce subgraph sur le réseau.
+- Vous pouvez facilement déplacer le contrôle d'un subgraph vers un multi-sig.
+- Un membre de la communauté peut créer un subgraph au nom d'une DAO.
 
-- Whoever owns the NFT controls the subgraph.
-- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
-- You can easily move control of a subgraph to a multi-sig.
-- A community member can create a subgraph on behalf of a DAO.
+## Voir votre Subgraph en tant que NFT
 
-### View your subgraph as an NFT
-
-To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+Pour voir votre subgraph en tant que NFT, vous pouvez visiter une marketplace NFT telle que **OpenSea**:
 
 ```
 https://opensea.io/your-wallet-address
 ```
 
-Or a wallet explorer like **Rainbow.me**:
+Ou un explorateur de portefeuille comme **Rainbow.me**:
 
 ```
-https://rainbow.me/your-wallet-addres
+https://rainbow.me/adresse-de-votre-portefeuille
 ```
 
-### Step-by-Step
-
-To transfer ownership of a subgraph, do the following:
-
-1.  Use the UI built into Subgraph Studio:
-
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
-
-2.  Choose the address that you would like to transfer the subgraph to:
-
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
-
-Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
-
-![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
+## Étape par Étape
 
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+Pour transférer la propriété d'un subgraph, procédez comme suit :
 
-### Step-by-Step
+1. Utilisez l'interface utilisateur intégrée dans Subgraph Studio :
 
-To deprecate your subgraph, do the following:
+   ![Transfert de propriété de subgraph](/img/subgraph-ownership-transfer-1.png)
 
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
+2. Choisissez l'adresse vers laquelle vous souhaitez transférer le subgraph :
 
-**Please note the following:**
+   ![Transfert de propriété de subgraph](/img/subgraph-ownership-transfer-2.png)
 
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
+Optionnellement, vous pouvez également utiliser l'interface utilisateur intégrée dans les marketplaces NFT comme OpenSea :
 
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
+![Transfert de propriété de subgraph depuis la marketplace NFT](/img/subgraph-ownership-transfer-nft-marketplace.png)

From 514e87c04cbb8836d9a9fd4296a15127d36065d8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:33 -0500
Subject: [PATCH 1265/1325] New translations transfer-a-subgraph.mdx (Spanish)

---
 .../pages/es/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/es/managing/transfer-a-subgraph.mdx b/website/pages/es/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/es/managing/transfer-a-subgraph.mdx
+++ b/website/pages/es/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From a77ca4e1f21aaf63b928acdbd422b1409b6c6b42 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:34 -0500
Subject: [PATCH 1266/1325] New translations transfer-a-subgraph.mdx (Arabic)

---
 .../pages/ar/managing/transfer-a-subgraph.mdx | 37 ++++---------------
 1 file changed, 7 insertions(+), 30 deletions(-)

diff --git a/website/pages/ar/managing/transfer-a-subgraph.mdx b/website/pages/ar/managing/transfer-a-subgraph.mdx
index dc0a1d63936e..19999c39b1e3 100644
--- a/website/pages/ar/managing/transfer-a-subgraph.mdx
+++ b/website/pages/ar/managing/transfer-a-subgraph.mdx
@@ -2,18 +2,16 @@
 title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 0c6026957454f39f486d3604c54aca12ce9122cd Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:35 -0500
Subject: [PATCH 1267/1325] New translations transfer-a-subgraph.mdx (Czech)

---
 .../pages/cs/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/cs/managing/transfer-a-subgraph.mdx b/website/pages/cs/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/cs/managing/transfer-a-subgraph.mdx
+++ b/website/pages/cs/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 91258460fe6317fb01d2d114f4ae363b550c8ae0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:36 -0500
Subject: [PATCH 1268/1325] New translations transfer-a-subgraph.mdx (German)

---
 .../pages/de/managing/transfer-a-subgraph.mdx | 59 ++++++-------------
 1 file changed, 18 insertions(+), 41 deletions(-)

diff --git a/website/pages/de/managing/transfer-a-subgraph.mdx b/website/pages/de/managing/transfer-a-subgraph.mdx
index c4060284d5d9..ed29ea904e5b 100644
--- a/website/pages/de/managing/transfer-a-subgraph.mdx
+++ b/website/pages/de/managing/transfer-a-subgraph.mdx
@@ -1,65 +1,42 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Einen Subgraph übertragen
 ---
 
-## Transferring ownership of a subgraph
+Subgraphs, die im dezentralen Netzwerk veröffentlicht werden, haben eine NFT, die auf die Adresse geprägt wird, die den Subgraph veröffentlicht hat. Die NFT basiert auf dem Standard ERC721, der Überweisungen zwischen Konten im The Graph Network erleichtert.
 
-Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+## Erinnerungshilfen
 
-**Please note the following:**
+- Wer im Besitz der NFT ist, kontrolliert den Subgraph.
+- Wenn der Eigentümer beschließt, das NFT zu verkaufen oder zu übertragen, kann er diesen Subgraph im Netz nicht mehr bearbeiten oder aktualisieren.
+- Sie können die Kontrolle über einen Subgraph leicht an eine Multisig übertragen.
+- Ein Community-Mitglied kann einen Subgraph im Namen einer DAO erstellen.
 
-- Whoever owns the NFT controls the subgraph.
-- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
-- You can easily move control of a subgraph to a multi-sig.
-- A community member can create a subgraph on behalf of a DAO.
+## Betrachten Sie Ihren Subgraph als NFT
 
-### View your subgraph as an NFT
-
-To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+Um Ihren Subgraph als NFT zu betrachten, können Sie einen NFT-Marktplatz wie **OpenSea** besuchen:
 
 ```
 https://opensea.io/your-wallet-address
 ```
 
-Or a wallet explorer like **Rainbow.me**:
+Oder ein Wallet-Explorer wie **Rainbow.me**:
 
 ```
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
-
-To transfer ownership of a subgraph, do the following:
-
-1.  Use the UI built into Subgraph Studio:
-
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
-
-2.  Choose the address that you would like to transfer the subgraph to:
-
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
-
-Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
-
-![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
+## Schritt für Schritt
 
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+Um das Eigentum an einem Subgraph zu übertragen, gehen Sie wie folgt vor:
 
-### Step-by-Step
+1. Verwenden Sie die in Subgraph Studio integrierte Benutzeroberfläche:
 
-To deprecate your subgraph, do the following:
+   ![Subgraph-Besitzübertragung](/img/subgraph-ownership-transfer-1.png)
 
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
+2. Wählen Sie die Adresse, an die Sie den Subgraph übertragen möchten:
 
-**Please note the following:**
+   ![Subgraph-Besitzübertragung](/img/subgraph-ownership-transfer-2.png)
 
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
+Optional können Sie auch die integrierte Benutzeroberfläche von NFT-Marktplätzen wie OpenSea verwenden:
 
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
+![Subgraph-Eigentumsübertragung vom NFT-Marktplatz](/img/subgraph-ownership-transfer-nft-marketplace.png)

From 426c3002f89842d6ff15606f8af70ec214d1d0d7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:37 -0500
Subject: [PATCH 1269/1325] New translations transfer-a-subgraph.mdx (Italian)

---
 .../pages/it/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/it/managing/transfer-a-subgraph.mdx b/website/pages/it/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/it/managing/transfer-a-subgraph.mdx
+++ b/website/pages/it/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 954a84bf7f1cd2ab5592675bab0c57f7bb4ea42e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:38 -0500
Subject: [PATCH 1270/1325] New translations transfer-a-subgraph.mdx (Japanese)

---
 .../pages/ja/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/ja/managing/transfer-a-subgraph.mdx b/website/pages/ja/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/ja/managing/transfer-a-subgraph.mdx
+++ b/website/pages/ja/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 266cebfc7fb36136ac79029fc0cbc0f72c3b1511 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:38 -0500
Subject: [PATCH 1271/1325] New translations transfer-a-subgraph.mdx (Korean)

---
 .../pages/ko/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/ko/managing/transfer-a-subgraph.mdx b/website/pages/ko/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/ko/managing/transfer-a-subgraph.mdx
+++ b/website/pages/ko/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 7332279769996d8539f31d59d488bad7d65864ca Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:39 -0500
Subject: [PATCH 1272/1325] New translations transfer-a-subgraph.mdx (Dutch)

---
 .../pages/nl/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/nl/managing/transfer-a-subgraph.mdx b/website/pages/nl/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/nl/managing/transfer-a-subgraph.mdx
+++ b/website/pages/nl/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From a4551cb647344d251a35da1131cfd1df03488594 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:40 -0500
Subject: [PATCH 1273/1325] New translations transfer-a-subgraph.mdx (Polish)

---
 .../pages/pl/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/pl/managing/transfer-a-subgraph.mdx b/website/pages/pl/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/pl/managing/transfer-a-subgraph.mdx
+++ b/website/pages/pl/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From d7136ee1972bec4c2a7358551028e5dce5397c17 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:41 -0500
Subject: [PATCH 1274/1325] New translations transfer-a-subgraph.mdx
 (Portuguese)

---
 .../pages/pt/managing/transfer-a-subgraph.mdx | 59 ++++++-------------
 1 file changed, 18 insertions(+), 41 deletions(-)

diff --git a/website/pages/pt/managing/transfer-a-subgraph.mdx b/website/pages/pt/managing/transfer-a-subgraph.mdx
index c4060284d5d9..5ba353e28f7f 100644
--- a/website/pages/pt/managing/transfer-a-subgraph.mdx
+++ b/website/pages/pt/managing/transfer-a-subgraph.mdx
@@ -1,65 +1,42 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
+Subgraphs publicados na rede descentralizada terão um NFT mintado no endereço que publicou o subgraph. O NFT é baseado no padrão ERC-721, que facilita transferências entre contas na Graph Network.
 
-Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+## Reminders
 
-**Please note the following:**
+- O dono do NFT controla o subgraph.
+- Se o dono atual decidir vender ou transferir o NFT, ele não poderá mais editar ou atualizar aquele subgraph na rede.
+- É possível transferir o controle de um subgraph para uma multisig.
+- Um membro da comunidade pode criar um subgraph no nome de uma DAO.
 
-- Whoever owns the NFT controls the subgraph.
-- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
-- You can easily move control of a subgraph to a multi-sig.
-- A community member can create a subgraph on behalf of a DAO.
+## View Your Subgraph as an NFT
 
-### View your subgraph as an NFT
-
-To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+Para visualizar o seu subgraph como um NFT, visite um mercado de NFTs como o **OpenSea**:
 
 ```
 https://opensea.io/your-wallet-address
 ```
 
-Or a wallet explorer like **Rainbow.me**:
+Ou um explorador de carteiras, como o **Rainbow.me**:
 
 ```
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
-
-To transfer ownership of a subgraph, do the following:
-
-1.  Use the UI built into Subgraph Studio:
-
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
-
-2.  Choose the address that you would like to transfer the subgraph to:
-
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
-
-Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
-
-![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
+## Passo a Passo
 
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+Para transferir a titularidade de um subgraph, faça o seguinte:
 
-### Step-by-Step
+1. Use a interface embutida no Subgraph Studio:
 
-To deprecate your subgraph, do the following:
+   ![Transferência de Titularidade de Subgraph](/img/subgraph-ownership-transfer-1.png)
 
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
+2. Escolha o endereço para o qual gostaria de transferir o subgraph:
 
-**Please note the following:**
+   ![Transferência de Titularidade de Subgraph](/img/subgraph-ownership-transfer-2.png)
 
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
+Também é possível usar a interface embutida de mercados de NFT, como o OpenSea:
 
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
+![Transferência de Titularidade de Subgraph de um mercado de NFT](/img/subgraph-ownership-transfer-nft-marketplace.png)

From 8f073d0d2001e498b6cbbbff19a4dbfa5857841d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:42 -0500
Subject: [PATCH 1275/1325] New translations transfer-a-subgraph.mdx (Russian)

---
 .../pages/ru/managing/transfer-a-subgraph.mdx | 59 ++++++-------------
 1 file changed, 18 insertions(+), 41 deletions(-)

diff --git a/website/pages/ru/managing/transfer-a-subgraph.mdx b/website/pages/ru/managing/transfer-a-subgraph.mdx
index c4060284d5d9..42e2b5861eac 100644
--- a/website/pages/ru/managing/transfer-a-subgraph.mdx
+++ b/website/pages/ru/managing/transfer-a-subgraph.mdx
@@ -1,65 +1,42 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Перенос субграфа
 ---
 
-## Transferring ownership of a subgraph
+Субграфы, опубликованные в децентрализованной сети, имеют NFT, сминченный по адресу, опубликовавшему субграф. NFT основан на стандарте ERC721, который облегчает переводы между аккаунтами в The Graph Network.
 
-Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+## Напоминания
 
-**Please note the following:**
+- Тот, кто владеет NFT, управляет субграфом.
+- Если владелец решит продать или передать NFT, он больше не сможет редактировать или обновлять этот субграф в сети.
+- Вы можете легко перенести управление субграфом на мультиподпись.
+- Участник сообщества может создать субграф от имени DAO.
 
-- Whoever owns the NFT controls the subgraph.
-- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
-- You can easily move control of a subgraph to a multi-sig.
-- A community member can create a subgraph on behalf of a DAO.
+## Просмотр Вашего субграфа как NFT
 
-### View your subgraph as an NFT
-
-To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+Чтобы просмотреть свой субграф как NFT, Вы можете посетить маркетплейс NFT, например, **OpenSea**:
 
 ```
 https://opensea.io/your-wallet-address
 ```
 
-Or a wallet explorer like **Rainbow.me**:
+Или воспользоваться программой для поиска кошелька, например, **Rainbow.me**:
 
 ```
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
-
-To transfer ownership of a subgraph, do the following:
-
-1.  Use the UI built into Subgraph Studio:
-
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
-
-2.  Choose the address that you would like to transfer the subgraph to:
-
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
-
-Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
-
-![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
+## Пошаговое руководство
 
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
+Чтобы передать право собственности на субграф, выполните следующие действия:
 
-### Step-by-Step
+1. Используйте встроенный в Subgraph Studio пользовательский интерфейс:
 
-To deprecate your subgraph, do the following:
+   ![Передача права собственности на субграф](/image/subgraph-ownership-transfer-1.png)
 
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
+2. Выберите адрес, на который хотели бы передать субграф:
 
-**Please note the following:**
+   ![Передача права собственности на субграф](/image/subgraph-ownership-transfer-2.png)
 
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
+При желании Вы также можете использовать встроенный пользовательский интерфейс таких маркетплейсов NFT, как OpenSea:
 
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.
+![Передача права собственности на субграф с маркетплейса NFT](/img/subgraph-ownership-transfer-nft-marketplace.png)

From 4fc1910bcc7b1c132e512d87b471cdfd0a016c20 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:43 -0500
Subject: [PATCH 1276/1325] New translations transfer-a-subgraph.mdx (Swedish)

---
 .../pages/sv/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/sv/managing/transfer-a-subgraph.mdx b/website/pages/sv/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/sv/managing/transfer-a-subgraph.mdx
+++ b/website/pages/sv/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 25e9583753a9943aa38ba6a695e420f3ecd6c26c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:44 -0500
Subject: [PATCH 1277/1325] New translations transfer-a-subgraph.mdx
 (Ukrainian)

---
 .../pages/uk/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/uk/managing/transfer-a-subgraph.mdx b/website/pages/uk/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/uk/managing/transfer-a-subgraph.mdx
+++ b/website/pages/uk/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 554cd5898106d376d9b49b071ce02c270a6a7d2b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:45 -0500
Subject: [PATCH 1278/1325] New translations transfer-a-subgraph.mdx (Chinese
 Simplified)

---
 .../pages/zh/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/zh/managing/transfer-a-subgraph.mdx b/website/pages/zh/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/zh/managing/transfer-a-subgraph.mdx
+++ b/website/pages/zh/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 27373be1bd53b2b6f52159db608a12d3ca71dae5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:46 -0500
Subject: [PATCH 1279/1325] New translations transfer-a-subgraph.mdx (Urdu
 (Pakistan))

---
 .../pages/ur/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/ur/managing/transfer-a-subgraph.mdx b/website/pages/ur/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/ur/managing/transfer-a-subgraph.mdx
+++ b/website/pages/ur/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 95f1045ab0d4f54bf8cdc70912a4405a91c9faf5 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:47 -0500
Subject: [PATCH 1280/1325] New translations transfer-a-subgraph.mdx
 (Vietnamese)

---
 .../pages/vi/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/vi/managing/transfer-a-subgraph.mdx b/website/pages/vi/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/vi/managing/transfer-a-subgraph.mdx
+++ b/website/pages/vi/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From 8b426bcbdc43652b1593c8ef164702fd28e00f52 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:48 -0500
Subject: [PATCH 1281/1325] New translations transfer-a-subgraph.mdx (Marathi)

---
 .../pages/mr/managing/transfer-a-subgraph.mdx | 39 ++++---------------
 1 file changed, 8 insertions(+), 31 deletions(-)

diff --git a/website/pages/mr/managing/transfer-a-subgraph.mdx b/website/pages/mr/managing/transfer-a-subgraph.mdx
index c4060284d5d9..19999c39b1e3 100644
--- a/website/pages/mr/managing/transfer-a-subgraph.mdx
+++ b/website/pages/mr/managing/transfer-a-subgraph.mdx
@@ -1,19 +1,17 @@
 ---
-title: Transfer and Deprecate a Subgraph
+title: Transfer a Subgraph
 ---
 
-## Transferring ownership of a subgraph
-
 Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
 
-**Please note the following:**
+## Reminders
 
 - Whoever owns the NFT controls the subgraph.
 - If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
 - You can easily move control of a subgraph to a multi-sig.
 - A community member can create a subgraph on behalf of a DAO.
 
-### View your subgraph as an NFT
+## View Your Subgraph as an NFT
 
 To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
 
@@ -27,39 +25,18 @@ Or a wallet explorer like **Rainbow.me**:
 https://rainbow.me/your-wallet-addres
 ```
 
-### Step-by-Step
+## Step-by-Step
 
 To transfer ownership of a subgraph, do the following:
 
-1.  Use the UI built into Subgraph Studio:
+1. Use the UI built into Subgraph Studio:
 
-    ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
 
-2.  Choose the address that you would like to transfer the subgraph to:
+2. Choose the address that you would like to transfer the subgraph to:
 
-    ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
 
 Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
 
 ![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)
-
-## Deprecating a subgraph
-
-Although you cannot delete a subgraph, you can deprecate it on Graph Explorer.
-
-### Step-by-Step
-
-To deprecate your subgraph, do the following:
-
-1.  Visit the contract address for Arbitrum One subgraphs [here](https://arbiscan.io/address/0xec9A7fb6CbC2E41926127929c2dcE6e9c5D33Bec#writeProxyContract).
-2.  Call `deprecateSubgraph` with your `SubgraphID` as your argument.
-3.  Your subgraph will no longer appear in searches on Graph Explorer.
-
-**Please note the following:**
-
-- The owner's wallet should call the `deprecateSubgraph` function.
-- Curators will not be able to signal on the subgraph anymore.
-- Curators that already signaled on the subgraph can withdraw their signal at an average share price.
-- Deprecated subgraphs will show an error message.
-
-> If you interacted with the deprecated subgraph, you can find it in your user profile under the "Subgraphs", "Indexing", or "Curating" tab, respectively.

From d78ccd8779bcb1bec3ff701707b8da37d68ea356 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:49 -0500
Subject: [PATCH 1282/1325] New translations transfer-a-subgraph.mdx (Swahili)

---
 .../pages/sw/managing/transfer-a-subgraph.mdx | 42 +++++++++++++++++++
 1 file changed, 42 insertions(+)
 create mode 100644 website/pages/sw/managing/transfer-a-subgraph.mdx

diff --git a/website/pages/sw/managing/transfer-a-subgraph.mdx b/website/pages/sw/managing/transfer-a-subgraph.mdx
new file mode 100644
index 000000000000..19999c39b1e3
--- /dev/null
+++ b/website/pages/sw/managing/transfer-a-subgraph.mdx
@@ -0,0 +1,42 @@
+---
+title: Transfer a Subgraph
+---
+
+Subgraphs published to the decentralized network have an NFT minted to the address that published the subgraph. The NFT is based on a standard ERC721, which facilitates transfers between accounts on The Graph Network.
+
+## Reminders
+
+- Whoever owns the NFT controls the subgraph.
+- If the owner decides to sell or transfer the NFT, they will no longer be able to edit or update that subgraph on the network.
+- You can easily move control of a subgraph to a multi-sig.
+- A community member can create a subgraph on behalf of a DAO.
+
+## View Your Subgraph as an NFT
+
+To view your subgraph as an NFT, you can visit an NFT marketplace like **OpenSea**:
+
+```
+https://opensea.io/your-wallet-address
+```
+
+Or a wallet explorer like **Rainbow.me**:
+
+```
+https://rainbow.me/your-wallet-addres
+```
+
+## Step-by-Step
+
+To transfer ownership of a subgraph, do the following:
+
+1. Use the UI built into Subgraph Studio:
+
+   ![Subgraph Ownership Transfer](/img/subgraph-ownership-transfer-1.png)
+
+2. Choose the address that you would like to transfer the subgraph to:
+
+   ![Subgraph Ownership Trasfer](/img/subgraph-ownership-transfer-2.png)
+
+Optionally, you can also use the built-in UI of NFT marketplaces like OpenSea:
+
+![Subgraph Ownership Transfer from NFT marketplace](/img/subgraph-ownership-transfer-nft-marketplace.png)

From 27654818daf658b68c3145a915d6a1668ccdf4c1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:50 -0500
Subject: [PATCH 1283/1325] New translations deploy-using-subgraph-studio.mdx
 (Romanian)

---
 .../deploy-using-subgraph-studio.mdx          | 28 +++++++++----------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/website/pages/ro/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ro/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..d8bb14e9f3c1 100644
--- a/website/pages/ro/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/ro/deploying/deploy-using-subgraph-studio.mdx
@@ -14,11 +14,11 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 - Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Începe
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,7 +53,7 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
 ### Subgraph Compatibility with The Graph Network
 
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From 173a73bf1b9dd4b99ca205179a17e86e6ea4730a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:51 -0500
Subject: [PATCH 1284/1325] New translations deploy-using-subgraph-studio.mdx
 (French)

---
 .../deploy-using-subgraph-studio.mdx          | 138 +++++++++---------
 1 file changed, 68 insertions(+), 70 deletions(-)

diff --git a/website/pages/fr/deploying/deploy-using-subgraph-studio.mdx b/website/pages/fr/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..3aeb7730bd33 100644
--- a/website/pages/fr/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/fr/deploying/deploy-using-subgraph-studio.mdx
@@ -1,139 +1,137 @@
 ---
-title: Deploy Using Subgraph Studio
+title: Déploiement en utilisant Subgraph Studio
 ---
 
-Learn how to deploy your subgraph to Subgraph Studio.
+Apprenez à déployer votre subgraph sur Subgraph Studio.
 
-> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
+> Note : Lorsque vous déployez un subgraph, vous le poussez vers Subgraph Studio, où vous pourrez le tester. Il est important de se rappeler que déployer n'est pas la même chose que publier. Lorsque vous publiez un subgraph, vous le publiez sur la blockchain.
 
-## Subgraph Studio Overview
+## Présentation de Subgraph Studio
 
-In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
+Dans [Subgraph Studio](https://thegraph.com/studio/), vous pouvez faire ce qui suit:
 
-- View a list of subgraphs you've created
-- Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
-- Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
-- Test your subgraph in the playground environment
-- Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
-- Manage your billing
+- Voir une liste des subgraphs que vous avez créés
+- Gérer, voir les détails et visualiser l'état d'un subgraph spécifique
+- Créez et gérez vos clés API pour des subgraphs spécifiques
+- Limitez vos clés API à des domaines spécifiques et autorisez uniquement certains Indexers à les utiliser pour effectuer des requêtes
+- Créer votre subgraph
+- Déployer votre subgraph en utilisant The Graph CLI
+- Tester votre subgraph dans l'environnement de test
+- Intégrer votre subgraph en staging en utilisant l'URL de requête du développement
+- Publier votre subgraph sur The Graph Network
+- Gérer votre facturation
 
-## Install The Graph CLI
+## Installer The Graph CLI
 
-Before deploying, you must install The Graph CLI.
+Avant de déployer, vous devez installer The Graph CLI.
 
-You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+Vous devez avoir [Node.js](https://nodejs.org/) et un gestionnaire de packages de votre choix (`npm`, `yarn` ou `pnpm`) installés pour utiliser The Graph CLI. Vérifiez la version la [plus récente](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) de l'outil CLI.
 
-**Install with yarn:**
+### Installation avec yarn
 
 ```bash
-yarn global add @graphprotocol/graph-cli
+npm install -g @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Installation avec npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Commencer
 
-1. Open [Subgraph Studio](https://thegraph.com/studio/).
-2. Connect your wallet to sign in.
-   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
-3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
-   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
+1. Ouvrez [Subgraph Studio](https://thegraph.com/studio/).
+2. Connectez votre portefeuille pour vous connecter.
+   - Vous pouvez le faire via MetaMask, Coinbase Wallet, WalletConnect ou Safe.
+3. Après vous être connecté, votre clé de déploiement unique sera affichée sur la page des détails de votre subgraph.
+   - La clé de déploiement vous permet de publier vos subgraphs ou de gérer vos clés d'API et votre facturation. Elle est unique mais peut être régénérée si vous pensez qu'elle a été compromise.
 
-> Important: You need an API key to query subgraphs
+> Important : Vous avez besoin d'une clé API pour interroger les subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### Comment créer un subgraph dans Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> Pour des informations supplémentaires écrites, consultez le [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Compatibilité des subgraphs avec le réseau de The Graph
 
-In order to be supported by Indexers on The Graph Network, subgraphs must:
+Pour être pris en charge par les Indexeurs sur The Graph Network, les subgraphs doivent :
 
-- Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Indexer un [réseau pris en charge](/developing/supported-networks)
+- Ne doit utiliser aucune des fonctionnalités suivantes :
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - Erreurs non fatales
+  - La greffe
 
-## Initialize Your Subgraph
+## Initialisez votre Subgraph
 
-Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
+Une fois que votre subgraph a été créé dans Subgraph Studio, vous pouvez initialiser son code via la CLI en utilisant cette commande :
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
-You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+Vous pouvez trouver la valeur `<SUBGRAPH_SLUG>` sur la page des détails de votre subgraph dans Subgraph Studio, voir l'image ci-dessous :
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
-After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+Après avoir exécuté la commande `graph init`, ilvous sera demandé de saisir l'adresse du contrat, le réseau, et un ABI que vous souhaitez interroger. Cela générera un nouveau dossier sur votre machine locale avec quelques codes de base pour commencer à travailler sur votre subgraph. Vous pouvez ensuite finaliser votre subgraph pour vous assurer qu'il fonctionne comme prévu.
 
-## Graph Auth
+## Authentification The Graph
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Avant de pouvoir déployer votre subgraph sur Subgraph Studio, vous devez vous connecter à votre compte via la CLI. Pour le faire, vous aurez besoin de votre clé de déploiement, que vous pouvez trouver sur la page des détails de votre subgraph.
 
-Then, use the following command to authenticate from the CLI:
+Ensuite, utilisez la commande suivante pour vous authentifier depuis la CLI :
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
-## Deploying a Subgraph
+## Déploiement d'un Subgraph
 
-Once you are ready, you can deploy your subgraph to Subgraph Studio.
+Une fois prêt, vous pouvez déployer votre subgraph sur Subgraph Studio.
 
-> Deploying a subgraph with the CLI pushes it to the Studio, where you can test it and and update the metadata. This action won't publish your subgraph to the decentralized network.
+> Déployer un subgraph avec la CLI le pousse vers le Studio, où vous pouvez le tester et mettre à jour les métadonnées. Cette action ne publiera pas votre subgraph sur le réseau décentralisé.
 
-Use the following CLI command to deploy your subgraph:
+Utilisez la commande CLI suivante pour déployer votre subgraph :
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
-After running this command, the CLI will ask for a version label.
+Après avoir exécuté cette commande, la CLI demandera une étiquette de version.
 
-- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
-- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
+- Il est fortement recommandé d'utiliser [semver](https://semver.org/) pour le versionnage, comme `0.0.1`. Cela dit, vous êtes libre de choisir n'importe quelle chaîne de caractère comme version telle que v1, version1 ou asdf.
+- Les étiquettes que vous créez seront visibles dans Graph Explorer et pourront être utilisées par les Curateurs pour décider s'ils veulent signaler sur une version spécifique ou non, donc choisissez-les judicieusement.
 
-## Testing Your Subgraph
+## Tester votre Subgraph
 
-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.
+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 du 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.
 
-Use Subgraph Studio to check the logs on the dashboard and look for any errors with your subgraph.
+Utilisez Subgraph Studio pour vérifier les journaux (logs) sur le tableau de bord et rechercher les erreurs éventuelles de votre subgraph.
 
-## Publish Your Subgraph
+## Publiez votre subgraph
 
-In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/).
+Pour publier votre subgraph avec succès, consultez la page [publier un subgraph](/publishing/publishing-a-subgraph/).
 
-## Versioning Your Subgraph with the CLI
+## Versionning de votre subgraph avec le CLI
 
-If you want to update your subgraph, you can do the following:
+Si vous souhaitez mettre à jour votre subgraph, vous pouvez faire ce qui suit :
 
-- You can deploy a new version to Studio using the CLI (it will only be private at this point).
-- Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
-- This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
+- Vous pouvez déployer une nouvelle version dans Studio en utilisant la CLI (cette version sera privée à ce stade).
+- Une fois que vous en êtes satisfait, vous pouvez publier votre nouveau déploiement sur [Graph Explorer](https://thegraph.com/explorer).
+- Cette action créera une nouvelle version de votre subgraph sur laquelle les Curateurs pourront commencer à signaler et que les Indexeurs pourront indexer.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+Vous pouvez également mettre à jour les métadonnées de votre subgraph sans publier une nouvelle version. Vous pouvez mettre à jour les détails de votre subgraph dans Studio (sous la photo de profil, le nom, la description, etc.) en cochant une option appelée **Update Details** dans [Graph Explorer](https://thegraph.com/explorer). Si cette option est cochée, une transaction sera générée sur la blockchain (on-chain) pour mettre à jour les détails du subgraph dans Explorer sans avoir à publier une nouvelle version avec un nouveau déploiement.
 
-> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
+> Remarque : Il y a des coûts associés à la publication d'une nouvelle version d'un subgraph sur le réseau. En plus des frais de transaction, vous devez également financer une partie de la taxe de curation sur le signal d'auto-migration . Vous ne pouvez pas publier une nouvelle version de votre subgraph si les Curateurs n'ont pas signalé dessus. Pour plus d'informations, veuillez lire plus [ici](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Archivage automatique des versions de subgraphs
 
-Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
+Chaque fois que vous déployez une nouvelle version de subgraph dans Subgraph Studio, la version précédente sera archivée. Les versions archivées ne seront pas indexées/synchronisées et ne pourront donc pas être interrogées. Vous pouvez désarchiver une version de votre subgraph dans Subgraph Studio.
 
-> Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.
+> Remarque : les versions précédentes des subgraphs non publiés mais déployés dans Studio seront automatiquement archivées.
 
 ![Subgraph Studio - Unarchive](/img/Unarchive.png)

From c037959848d5f287e4284180a87978b8ebcbf430 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:52 -0500
Subject: [PATCH 1285/1325] New translations deploy-using-subgraph-studio.mdx
 (Spanish)

---
 .../deploy-using-subgraph-studio.mdx          | 38 +++++++++----------
 1 file changed, 18 insertions(+), 20 deletions(-)

diff --git a/website/pages/es/deploying/deploy-using-subgraph-studio.mdx b/website/pages/es/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..1ea90990a2d9 100644
--- a/website/pages/es/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/es/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- Crear y gestionar sus claves API para subgrafos específicos
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Comenzar
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,16 +53,16 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Compatibilidad de los Subgrafos con The Graph Network
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- No debe utilizar ninguna de las siguientes funciones:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
+  - Errores no fatales
   - Grafting
 
 ## Initialize Your Subgraph
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Archivado Automático de Versiones de Subgrafos
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 479c1d6d7810ff34d22d9bd8afa1a44eef246abb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:53 -0500
Subject: [PATCH 1286/1325] New translations deploy-using-subgraph-studio.mdx
 (Arabic)

---
 .../deploy-using-subgraph-studio.mdx          | 38 +++++++++----------
 1 file changed, 18 insertions(+), 20 deletions(-)

diff --git a/website/pages/ar/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ar/deploying/deploy-using-subgraph-studio.mdx
index 1e6e22de7282..3e357875b406 100644
--- a/website/pages/ar/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/ar/deploying/deploy-using-subgraph-studio.mdx
@@ -12,9 +12,9 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- إنشاء وإدارة مفاتيح API الخاصة بك لـ subgraphs محددة
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create a new subgraph
+- Create your subgraph
 - Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## البدء
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -49,30 +47,30 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
    - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
 
-> Important: You need an API key to query subgraphs.
+> Important: You need an API key to query subgraphs
 
 ### How to Create a Subgraph in Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### توافق الـ Subgraph مع شبكة The Graph
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- يجب ألا تستخدم أيًا من الميزات التالية:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - أخطاء غير فادحة
+  - تطعيم(Grafting)
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## الأرشفة التلقائية لإصدارات الـ Subgraph
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 14bd8012c6bf97825f85d20a6324563c574471cc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:54 -0500
Subject: [PATCH 1287/1325] New translations deploy-using-subgraph-studio.mdx
 (Czech)

---
 .../deploy-using-subgraph-studio.mdx          | 46 +++++++++----------
 1 file changed, 22 insertions(+), 24 deletions(-)

diff --git a/website/pages/cs/deploying/deploy-using-subgraph-studio.mdx b/website/pages/cs/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..160322951c6f 100644
--- a/website/pages/cs/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/cs/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- Vytváření a správa klíčů API pro konkrétní podgrafy
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Začněte
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -51,28 +49,28 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 > Important: You need an API key to query subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### Jak vytvořit podgraf v Podgraf Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Kompatibilita podgrafů se sítí grafů
 
-In order to be supported by Indexers on The Graph Network, subgraphs must:
+Aby mohly být podgrafy podporovány indexátory v síti grafů, musí:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Nesmí používat žádnou z následujících funkcí:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - Nefatální
+  - Roubování
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -81,26 +79,26 @@ You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgra
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
-## Graph Auth
+## Autorizace grafu
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Automatická archivace verzí podgrafů
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 1fe5f3414914d8581a2bb9e1198518d57b93e931 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:55 -0500
Subject: [PATCH 1288/1325] New translations deploy-using-subgraph-studio.mdx
 (German)

---
 .../deploy-using-subgraph-studio.mdx          | 92 +++++++++----------
 1 file changed, 45 insertions(+), 47 deletions(-)

diff --git a/website/pages/de/deploying/deploy-using-subgraph-studio.mdx b/website/pages/de/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..6b2f6a058019 100644
--- a/website/pages/de/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/de/deploying/deploy-using-subgraph-studio.mdx
@@ -1,106 +1,104 @@
 ---
-title: Deploy Using Subgraph Studio
+title: Bereitstellung mit Subgraph Studio
 ---
 
-Learn how to deploy your subgraph to Subgraph Studio.
+Erfahren Sie, wie Sie Ihren Subgraph in Subgraph Studio bereitstellen können.
 
-> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
+> Hinweis: Wenn Sie einen Subgraph bereitstellen, schieben Sie ihn zu Subgraph Studio, wo Sie ihn testen können. Es ist wichtig zu wissen, dass Bereitstellen nicht dasselbe ist wie Veröffentlichen. Wenn Sie einen Subgraph veröffentlichen, dann veröffentlichen Sie ihn in der Kette.
 
-## Subgraph Studio Overview
+## Subgraph Studio Überblick
 
-In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
+In [Subgraph Studio] (https://thegraph.com/studio/) können Sie Folgendes tun:
 
-- View a list of subgraphs you've created
-- Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
-- Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
-- Test your subgraph in the playground environment
-- Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
-- Manage your billing
+- Eine Liste der von Ihnen erstellten Subgraphs anzeigen
+- Verwalten, Anzeigen von Details und Visualisieren des Status eines bestimmten Subgraphen
+- Erstellen und verwalten Sie Ihre API-Schlüssel für bestimmte Subgraphen
+- Schränken Sie Ihre API-Schlüssel auf bestimmte Domains ein und erlauben Sie nur bestimmten Indexern die Abfrage mit diesen Schlüsseln
+- Erstellen Sie Ihren Subgraph
+- Verteilen Sie Ihren Subgraph mit The Graph CLI
+- Testen Sie Ihren Subgraph in der „Playground“-Umgebung
+- Integrieren Sie Ihren Subgraph in Staging unter Verwendung der Entwicklungsabfrage-URL
+- Veröffentlichen Sie Ihren Subgraph auf The Graph Network
+- Verwalten Sie Ihre Rechnungen
 
-## Install The Graph CLI
+## Installieren der Graph-CLI
 
-Before deploying, you must install The Graph CLI.
+Vor der Bereitstellung müssen Sie The Graph CLI installieren.
 
-You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+Sie müssen [Node.js](https://nodejs.org/) und einen Paketmanager Ihrer Wahl (`npm`, `yarn` oder `pnpm`) installiert haben, um The Graph CLI zu verwenden. Prüfen Sie, ob die [aktuellste](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI-Version installiert ist.
 
-**Install with yarn:**
+### Installieren mit yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Installieren mit npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
+## Los geht’s
 
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+1. Öffnen Sie [Subgraph Studio] (https://thegraph.com/studio/).
+2. Verbinden Sie Ihre Wallet, um sich anzumelden.
+   - Sie können dies über MetaMask, Coinbase Wallet, WalletConnect oder Safe tun.
+3. Nachdem Sie sich angemeldet haben, wird Ihr eindeutiger Verteilungsschlüssel auf der Detailseite Ihres Subgraphen angezeigt.
+   - Mit dem Bereitstellungsschlüssel können Sie Ihre Subgraphs veröffentlichen oder Ihre API-Schlüssel und Abrechnungen verwalten. Er ist einmalig, kann aber neu generiert werden, wenn Sie glauben, dass er kompromittiert wurde.
 
-1. Open [Subgraph Studio](https://thegraph.com/studio/).
-2. Connect your wallet to sign in.
-   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
-3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
-   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
+> Wichtig: Sie benötigen einen API-Schlüssel, um Subgraphs abzufragen
 
-> Important: You need an API key to query subgraphs
-
-### How to Create a Subgraph in Subgraph Studio
+### So erstellen Sie einen Subgraph in Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> Weitere schriftliche Informationen finden Sie im [Schnellstart](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Kompatibilität von Subgraphs mit dem The Graph Network
 
-In order to be supported by Indexers on The Graph Network, subgraphs must:
+Um von Indexern auf The Graph Network unterstützt zu werden, müssen Subgraphen:
 
-- Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Ein [unterstütztes Netzwerk] indizieren (/developing/supported-networks)
+- Sie dürfen keine der folgenden Funktionen verwenden:
   - ipfs.cat & ipfs.map
   - Non-fatal errors
   - Grafting
 
-## Initialize Your Subgraph
+## Initialisieren Ihres Subgraphen
 
-Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
+Sobald Ihr Subgraph in Subgraph Studio erstellt wurde, können Sie seinen Code über die CLI mit diesem Befehl initialisieren:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
-You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+Sie finden den Wert `<SUBGRAPH_SLUG>` auf der Detailseite Ihres Subgraphs in Subgraph Studio, siehe Abbildung unten:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
-After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+Nachdem Sie `graph init` ausgeführt haben, werden Sie aufgefordert, die Vertragsadresse, das Netzwerk und eine ABI einzugeben, die Sie abfragen möchten. Daraufhin wird ein neuer Ordner auf Ihrem lokalen Rechner erstellt, der einige grundlegende Codes enthält, um mit der Arbeit an Ihrem Subgraph zu beginnen. Anschließend können Sie Ihren Subgraph fertigstellen, um sicherzustellen, dass er wie erwartet funktioniert.
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Bevor Sie Ihren Subgraph in Subgraph Studio bereitstellen können, müssen Sie sich bei Ihrem Konto in der CLI anmelden. Dazu benötigen Sie Ihren Bereitstellungsschlüssel, den Sie auf der Seite mit den Details Ihres Subgraphen finden.
 
-Then, use the following command to authenticate from the CLI:
+Verwenden Sie dann den folgenden Befehl, um sich über die CLI zu authentifizieren:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
-## Deploying a Subgraph
+## Bereitstellen eines Subgraphs
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From dc9e9b669a17db42945b6735e80104ac17df5bda Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:56 -0500
Subject: [PATCH 1289/1325] New translations deploy-using-subgraph-studio.mdx
 (Italian)

---
 .../deploy-using-subgraph-studio.mdx          | 40 +++++++++----------
 1 file changed, 19 insertions(+), 21 deletions(-)

diff --git a/website/pages/it/deploying/deploy-using-subgraph-studio.mdx b/website/pages/it/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..5d36bc2e669a 100644
--- a/website/pages/it/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/it/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- Creare e gestire le chiavi API per specifici subgraph
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Iniziare
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -51,20 +49,20 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 > Important: You need an API key to query subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### Come creare un subgraph nel Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Compatibilità del subgraph con The Graph Network
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Non deve utilizzare nessuna delle seguenti funzioni:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
+  - Errori non fatali
   - Grafting
 
 ## Initialize Your Subgraph
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Archiviazione automatica delle versioni del subgraph
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From c805f8737207703e96fa83f13e75dd95861182e9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:57 -0500
Subject: [PATCH 1290/1325] New translations deploy-using-subgraph-studio.mdx
 (Japanese)

---
 .../deploy-using-subgraph-studio.mdx          | 42 +++++++++----------
 1 file changed, 20 insertions(+), 22 deletions(-)

diff --git a/website/pages/ja/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ja/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..0a867171a0c3 100644
--- a/website/pages/ja/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/ja/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- 特定のサブグラフ用の API キーの作成と管理
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## 始めましょう
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -51,20 +49,20 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 > Important: You need an API key to query subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### Subgraph Studio でサブグラフを作成する方法
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Subgraph と The Graph Network の互換性
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- 以下の機能のいずれも使用してはいけません:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
+  - 致命的でないエラー
   - Grafting
 
 ## Initialize Your Subgraph
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -81,26 +79,26 @@ You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgra
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
-## Graph Auth
+## グラフ認証
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## サブグラフのバージョンの自動アーカイブ
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 3eb0b7a32abcd2003eb2acb83a06f1f992047211 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:57:58 -0500
Subject: [PATCH 1291/1325] New translations deploy-using-subgraph-studio.mdx
 (Korean)

---
 .../deploy-using-subgraph-studio.mdx          | 28 +++++++++----------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/website/pages/ko/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ko/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..a3b2f150a79c 100644
--- a/website/pages/ko/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/ko/deploying/deploy-using-subgraph-studio.mdx
@@ -14,11 +14,11 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 - Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Get Started
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,7 +53,7 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
 ### Subgraph Compatibility with The Graph Network
 
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From 5bf04f67ee6a9a944b73421d7fb9b90a1f57cfa1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:00 -0500
Subject: [PATCH 1292/1325] New translations deploy-using-subgraph-studio.mdx
 (Dutch)

---
 .../deploy-using-subgraph-studio.mdx          | 28 +++++++++----------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/website/pages/nl/deploying/deploy-using-subgraph-studio.mdx b/website/pages/nl/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..1918c4b13f00 100644
--- a/website/pages/nl/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/nl/deploying/deploy-using-subgraph-studio.mdx
@@ -14,11 +14,11 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 - Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Begin
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,7 +53,7 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
 ### Subgraph Compatibility with The Graph Network
 
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From 473638541d6a9ad41ec3a3883d55240214548203 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:01 -0500
Subject: [PATCH 1293/1325] New translations deploy-using-subgraph-studio.mdx
 (Polish)

---
 .../deploy-using-subgraph-studio.mdx          | 28 +++++++++----------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/website/pages/pl/deploying/deploy-using-subgraph-studio.mdx b/website/pages/pl/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..2eb14f2ab083 100644
--- a/website/pages/pl/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/pl/deploying/deploy-using-subgraph-studio.mdx
@@ -14,11 +14,11 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 - Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Jak zacząć?
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,7 +53,7 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
 ### Subgraph Compatibility with The Graph Network
 
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From d8dfd1bc6be43677d65f7e8f22e703cf9310ca19 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:02 -0500
Subject: [PATCH 1294/1325] New translations deploy-using-subgraph-studio.mdx
 (Portuguese)

---
 .../deploy-using-subgraph-studio.mdx          | 46 +++++++++----------
 1 file changed, 22 insertions(+), 24 deletions(-)

diff --git a/website/pages/pt/deploying/deploy-using-subgraph-studio.mdx b/website/pages/pt/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..f54b8f30084a 100644
--- a/website/pages/pt/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/pt/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- Criar e gerir as suas chaves de API para subgraphs específicos
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Como Começar
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -51,28 +49,28 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 > Important: You need an API key to query subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### Como Criar um Subgraph no Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Compatibilidade de Subgraph com a Graph Network
 
-In order to be supported by Indexers on The Graph Network, subgraphs must:
+Para ter apoio de Indexadores na Graph Network, os subgraphs devem:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Não deve usar quaisquer das seguintes características:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - Erros não-fatais
+  - Enxertos
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -81,26 +79,26 @@ You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgra
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
-## Graph Auth
+## Autenticação
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Arquivamento Automático de Versões de Subgraphs
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 798ddc7f9e7bf79d3a578b878c4de1b64ef3bb7e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:03 -0500
Subject: [PATCH 1295/1325] New translations deploy-using-subgraph-studio.mdx
 (Russian)

---
 .../deploy-using-subgraph-studio.mdx          | 130 +++++++++---------
 1 file changed, 64 insertions(+), 66 deletions(-)

diff --git a/website/pages/ru/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ru/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..b8240d68ce51 100644
--- a/website/pages/ru/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/ru/deploying/deploy-using-subgraph-studio.mdx
@@ -1,139 +1,137 @@
 ---
-title: Deploy Using Subgraph Studio
+title: Развертывание с использованием Subgraph Studio
 ---
 
-Learn how to deploy your subgraph to Subgraph Studio.
+Узнайте, как развернуть свой субграф в Subgraph Studio.
 
-> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
+> Примечание: При развертывании субграфа Вы отправляете его в Subgraph Studio, где сможете его протестировать. Важно помнить, что развертывание — это не то же самое, что публикация. При публикации субграфа Вы размещаете его на чейне.
 
-## Subgraph Studio Overview
+## Обзор Subgraph Studio
 
-In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
+В [Subgraph Studio](https://thegraph.com/studio/) Вы можете выполнять следующие действия:
 
-- View a list of subgraphs you've created
-- Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
-- Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
-- Test your subgraph in the playground environment
-- Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
-- Manage your billing
+- Просматривать список созданных Вами субграфов
+- Управлять, просматривать детали и визуализировать статус конкретного субграфа
+- Создание и управление ключами API для определенных подграфов
+- Ограничивать использование своих API-ключей определенными доменами и разрешать только определенным индексаторам выполнять запросы с их помощью
+- Создавать свой субграф
+- Развертывать свой субграф, используя The Graph CLI
+- Тестировать свой субграф в тестовой среде Playground
+- Интегрировать свой субграф на стадии разработки, используя URL запроса разработки
+- Публиковать свой субграф в The Graph Network
+- Управлять своими платежами
 
-## Install The Graph CLI
+## Установка The Graph CLI
 
-Before deploying, you must install The Graph CLI.
+Перед развертыванием необходимо установить The Graph CLI.
 
-You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+Для использования 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.
 
-**Install with yarn:**
+### Установка с помощью yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Установка с помощью npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
+## Начнем
 
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+1. Откройте [Subgraph Studio](https://thegraph.com/studio/).
+2. Подключите свой кошелек для входа.
+   - Вы можете это сделать через MetaMask, Coinbase Wallet, WalletConnect или Safe.
+3. После входа в систему Ваш уникальный ключ развертывания будет отображаться на странице сведений о Вашем субграфе.
+   - Ключ развертывания позволяет публиковать субграфы, а также управлять вашими API-ключами и оплатой. Он уникален, но может быть восстановлен, если Вы подозреваете, что он был взломан.
 
-1. Open [Subgraph Studio](https://thegraph.com/studio/).
-2. Connect your wallet to sign in.
-   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
-3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
-   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
-
-> Important: You need an API key to query subgraphs
+> Важно: для выполнения запросов к субграфам необходим API-ключ
 
 ### How to Create a Subgraph in Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> Для получения дополнительной информации ознакомьтесь с разделом [Быстрый старт](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Совместимость подграфов с сетью Graph
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
-- Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Индексировать [поддерживаемую сеть](/developing/supported-networks)
+- Не должны использовать ни одну из следующих функций:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
+  - Неисправимые ошибки
   - Grafting
 
-## Initialize Your Subgraph
+## Инициализация Вашего Субграфа
 
-Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
+После создания субграфа в Subgraph Studio Вы можете инициализировать его код через CLI с помощью следующей команды:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
-You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+Значение `<SUBGRAPH_SLUG>` можно найти на странице сведений о субграфе в Subgraph Studio, см. изображение ниже:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 
-After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+После запуска `graph init` Вам будет предложено ввести адрес контракта, сеть и ABI, которые Вы хотите запросить. Это приведет к созданию новой папки на Вашем локальном компьютере с базовым кодом для начала работы над субграфом. Затем Вы можете завершить работу над своим субграфом, чтобы убедиться, что он функционирует должным образом.
 
-## Graph Auth
+## Аутентификация в Graph
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Прежде чем Вы сможете развернуть свой субграф в Subgraph Studio, Вам будет необходимо войти в свою учетную запись в CLI. Для этого Вам понадобится ключ развертывания, который Вы сможете найти на странице сведений о субграфе.
 
-Then, use the following command to authenticate from the CLI:
+После этого используйте следующую команду для аутентификации через CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
-## Deploying a Subgraph
+## Развертывание субграфа
 
-Once you are ready, you can deploy your subgraph to Subgraph Studio.
+Когда будете готовы, Вы сможете развернуть свой субграф в Subgraph Studio.
 
-> Deploying a subgraph with the CLI pushes it to the Studio, where you can test it and and update the metadata. This action won't publish your subgraph to the decentralized network.
+> Развертывание субграфа с помощью CLI отправляет его в Studio, где Вы сможете протестировать его и обновить метаданные. Это действие не приводит к публикации субграфа в децентрализованной сети.
 
-Use the following CLI command to deploy your subgraph:
+Используйте следующую команду CLI для развертывания своего субграфа:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
-After running this command, the CLI will ask for a version label.
+После выполнения этой команды CLI запросит метку версии.
 
-- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
-- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
+- Настоятельно рекомендуется использовать [semver](https://semver.org/) для управления версиями типа `0.0.1`. При этом Вы можете выбрать любую строку в качестве версии, например: `v1`, `version1` или `asdf`.
+- Созданные вами метки будут видны в Graph Explorer, и кураторы смогут использовать их для принятия решения, сигнализировать на определенную версию или нет, поэтому выбирайте метки с умом.
 
-## Testing Your Subgraph
+## Тестирование Вашего субграфа
 
-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.
+После развертывания Вы можете протестировать свой субграф (в Subgraph Studio или в собственном приложении, используя URL-адрес запроса на развертывание), развернуть другую версию, обновить метаданные и, когда будете готовы, опубликовать в [Graph Explorer](https://thegraph.com/explorer).
 
-Use Subgraph Studio to check the logs on the dashboard and look for any errors with your subgraph.
+Используйте Subgraph Studio, чтобы проверить логи на панели управления и обнаружить возможные ошибки в своем субграфе.
 
-## Publish Your Subgraph
+## Публикация Вашего субграфа
 
-In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/).
+Чтобы успешно опубликовать свой субграф, ознакомьтесь с [публикацией субграфа](/publishing/publishing-a-subgraph/).
 
-## Versioning Your Subgraph with the CLI
+## Управление версиями Вашего субграфа с помощью CLI
 
-If you want to update your subgraph, you can do the following:
+Если Вы хотите обновить свой субграф, Вы можете сделать следующее:
 
-- You can deploy a new version to Studio using the CLI (it will only be private at this point).
-- Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
-- This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
+- Вы можете развернуть новую версию в Studio, используя CLI (на этом этапе она будет только приватной).
+- Если результат Вас устроит, Вы можете опубликовать новое развертывание в [Graph Explorer](https://thegraph.com/explorer).
+- Это действие создаст новую версию вашего субграфа, о которой Кураторы смогут начать сигнализировать, а Индексаторы — индексировать.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+Вы также можете обновить метаданные субграфа без публикации новой версии. В Studio можно обновить данные субграфа (аватар, название, описание и т.д.), выбрав опцию **Обновить данные** в [Graph Explorer](https://thegraph.com/explorer). Если эта опция выбрана, будет сгенерирована транзакция в сети, которая обновит информацию о субграфе в Explorer без необходимости публиковать новую версию с новым развертыванием.
 
-> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
+> Примечание: Публикация новой версии субграфа в сети требует определенных затрат. Помимо комиссий за транзакцию, Вам нужно также оплатить часть кураторского сбора за авто-миграционный сигнал. Вы не сможете опубликовать новую версию субграфа, если на нее не был подан сигнал от Кураторов. Дополнительную информацию можно прочитать [здесь](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Автоматическое архивирование версий подграфа
 
-Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
+Каждый раз, когда Вы развертываете новую версию субграфа в Subgraph Studio, предыдущая версия архивируется. Архивированные версии не будут проиндексированы/синхронизированы и, следовательно, их нельзя будет запросить. Вы можете разархивировать архивированную версию своего субграфа в Subgraph Studio.
 
-> Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.
+> Примечание: предыдущие версии непубликованных субграфов, развернутых в Studio, будут автоматически архивированы.
 
 ![Subgraph Studio - Unarchive](/img/Unarchive.png)

From b015f3fd73b303b1208b257913ab4f0c5c0a26ff Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:04 -0500
Subject: [PATCH 1296/1325] New translations deploy-using-subgraph-studio.mdx
 (Swedish)

---
 .../deploy-using-subgraph-studio.mdx          | 44 +++++++++----------
 1 file changed, 21 insertions(+), 23 deletions(-)

diff --git a/website/pages/sv/deploying/deploy-using-subgraph-studio.mdx b/website/pages/sv/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..fefe0f330649 100644
--- a/website/pages/sv/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/sv/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- Skapa och hantera API nycklar för specifika undergrafer
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Komma igång
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -51,28 +49,28 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 > Important: You need an API key to query subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### Hur man skapar en subgraf i Subgraf Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### Kompatibilitet mellan undergrafer och grafnätet
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- Får inte använda någon av följande egenskaper:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - Icke dödliga fel
+  - Ympning
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -81,26 +79,26 @@ You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgra
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
-## Graph Auth
+## Auth för grafer
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## Automatisk arkivering av versioner av undergrafer
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 4679ce3422d84fa3d14d4622ca1019ec5926b230 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:05 -0500
Subject: [PATCH 1297/1325] New translations deploy-using-subgraph-studio.mdx
 (Ukrainian)

---
 .../deploy-using-subgraph-studio.mdx          | 28 +++++++++----------
 1 file changed, 13 insertions(+), 15 deletions(-)

diff --git a/website/pages/uk/deploying/deploy-using-subgraph-studio.mdx b/website/pages/uk/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..8e97e86976fd 100644
--- a/website/pages/uk/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/uk/deploying/deploy-using-subgraph-studio.mdx
@@ -14,11 +14,11 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 - Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Розпочати роботу
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,7 +53,7 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
 ### Subgraph Compatibility with The Graph Network
 
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From 21a99bebe401ef371dc3003654f5d01760108493 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:06 -0500
Subject: [PATCH 1298/1325] New translations deploy-using-subgraph-studio.mdx
 (Chinese Simplified)

---
 .../deploy-using-subgraph-studio.mdx          | 44 +++++++++----------
 1 file changed, 21 insertions(+), 23 deletions(-)

diff --git a/website/pages/zh/deploying/deploy-using-subgraph-studio.mdx b/website/pages/zh/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..d3ee2203f7d3 100644
--- a/website/pages/zh/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/zh/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- 为特定子图创建和管理 API 密钥
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## 开始
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -51,28 +49,28 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 > Important: You need an API key to query subgraphs
 
-### How to Create a Subgraph in Subgraph Studio
+### 如何在子图工作室中创建子图
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### 子图与图形网络的兼容性
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- 不得使用以下任何功能：
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - 非致命错误
+  - 嫁接
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -81,26 +79,26 @@ You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgra
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
-## Graph Auth
+## Graph 认证
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## 子图版本的自动归档
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 499d239b35d7c5e6ffa57d40d62e31b2b7ca9f34 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:07 -0500
Subject: [PATCH 1299/1325] New translations deploy-using-subgraph-studio.mdx
 (Urdu (Pakistan))

---
 .../deploy-using-subgraph-studio.mdx          | 36 +++++++++----------
 1 file changed, 17 insertions(+), 19 deletions(-)

diff --git a/website/pages/ur/deploying/deploy-using-subgraph-studio.mdx b/website/pages/ur/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..7a0e9d8ce26e 100644
--- a/website/pages/ur/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/ur/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- مخصوص سب گرافس کے لۓ API کیز بنائیں اور ان کا انتظام کریں
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## شروع کریں
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,14 +53,14 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### گراف نیٹ ورک کے ساتھ سب گراف مطابقت
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- درج ذیل خصوصیات میں سے کوئی بھی استعمال نہیں کرنا چاہیے:
   - ipfs.cat & ipfs.map
   - Non-fatal errors
   - Grafting
@@ -72,7 +70,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## سب گراف ورژن کی خودکار آرکائیونگ
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From a2918b0bcb563d2747d9f49511a49eda5c220574 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:08 -0500
Subject: [PATCH 1300/1325] New translations deploy-using-subgraph-studio.mdx
 (Vietnamese)

---
 .../deploy-using-subgraph-studio.mdx          | 32 +++++++++----------
 1 file changed, 15 insertions(+), 17 deletions(-)

diff --git a/website/pages/vi/deploying/deploy-using-subgraph-studio.mdx b/website/pages/vi/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..8e4333eec207 100644
--- a/website/pages/vi/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/vi/deploying/deploy-using-subgraph-studio.mdx
@@ -14,11 +14,11 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 - Manage, view details, and visualize the status of a specific subgraph
 - Create and manage your API keys for specific subgraphs
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## Bắt đầu
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,7 +53,7 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
 ### Subgraph Compatibility with The Graph Network
 
@@ -64,15 +62,15 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 - Index a [supported network](/developing/supported-networks)
 - Must not use any of the following features:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - Lỗi không nghiêm trọng
+  - Ghép
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -83,24 +81,24 @@ After running `graph init`, you will be asked to input the contract address, net
 
 ## Graph Auth
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,7 +124,7 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 

From d44128d15bfebc3b03acc4a860fcee3d79dba7a2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:09 -0500
Subject: [PATCH 1301/1325] New translations deploy-using-subgraph-studio.mdx
 (Marathi)

---
 .../deploy-using-subgraph-studio.mdx          | 42 +++++++++----------
 1 file changed, 20 insertions(+), 22 deletions(-)

diff --git a/website/pages/mr/deploying/deploy-using-subgraph-studio.mdx b/website/pages/mr/deploying/deploy-using-subgraph-studio.mdx
index 502169b4ccfa..72a5eca3d903 100644
--- a/website/pages/mr/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/mr/deploying/deploy-using-subgraph-studio.mdx
@@ -12,13 +12,13 @@ In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
 
 - View a list of subgraphs you've created
 - Manage, view details, and visualize the status of a specific subgraph
-- Create and manage your API keys for specific subgraphs
+- विशिष्ट सबग्राफसाठी तुमच्या API की तयार करा आणि व्यवस्थापित करा
 - Restrict your API keys to specific domains and allow only certain Indexers to query with them
-- Create your subgraph through the Studio UI
-- Deploy your subgraph using the The Graph CLI
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
 - Test your subgraph in the playground environment
 - Integrate your subgraph in staging using the development query URL
-- Publish your subgraph with the Studio UI
+- Publish your subgraph to The Graph Network
 - Manage your billing
 
 ## Install The Graph CLI
@@ -27,21 +27,19 @@ Before deploying, you must install The Graph CLI.
 
 You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
 
-**Install with yarn:**
+### Install with yarn
 
 ```bash
 yarn global add @graphprotocol/graph-cli
 ```
 
-**Install with npm:**
+### Install with npm
 
 ```bash
 npm install -g @graphprotocol/graph-cli
 ```
 
-## Create Your Subgraph
-
-Before deploying your subgraph you need to create an account in [Subgraph Studio](https://thegraph.com/studio/).
+## सुरु करूया
 
 1. Open [Subgraph Studio](https://thegraph.com/studio/).
 2. Connect your wallet to sign in.
@@ -55,24 +53,24 @@ Before deploying your subgraph you need to create an account in [Subgraph Studio
 
 <VideoEmbed youtube="nGIFuC69bSA" />
 
-> For additional written detail, review the [Quick-Start](/quick-start/).
+> For additional written detail, review the [Quick Start](/quick-start/).
 
-### Subgraph Compatibility with The Graph Network
+### ग्राफ नेटवर्कसह सबग्राफ सुसंगतता
 
 In order to be supported by Indexers on The Graph Network, subgraphs must:
 
 - Index a [supported network](/developing/supported-networks)
-- Must not use any of the following features:
+- खालीलपैकी कोणतीही वैशिष्ट्ये वापरू नयेत:
   - ipfs.cat & ipfs.map
-  - Non-fatal errors
-  - Grafting
+  - गैर-घातक त्रुटी
+  - कलम करणे
 
 ## Initialize Your Subgraph
 
 Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
 
 ```bash
-graph init --studio <SUBGRAPH_SLUG>
+graph init <SUBGRAPH_SLUG>
 ```
 
 You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
@@ -81,26 +79,26 @@ You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgra
 
 After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
 
-## Graph Auth
+## आलेख प्रमाणीकरण
 
-Before you can deploy your subgraph to Subgraph Studio, you need to login into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
 
 Then, use the following command to authenticate from the CLI:
 
 ```bash
-graph auth --studio <DEPLOY KEY>
+graph auth <DEPLOY KEY>
 ```
 
 ## Deploying a Subgraph
 
 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 and update the metadata. This action won't publish your subgraph to the decentralized network.
+> 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.
 
 Use the following CLI command to deploy your subgraph:
 
 ```bash
-graph deploy --studio <SUBGRAPH_SLUG>
+graph deploy <SUBGRAPH_SLUG>
 ```
 
 After running this command, the CLI will ask for a version label.
@@ -126,11 +124,11 @@ If you want to update your subgraph, you can do the following:
 - Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
 - This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
 
-You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in Graph Explorer. If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
 
 > Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
 
-## Automatic Archiving of Subgraph Versions
+## सबग्राफ आवृत्त्यांचे स्वयंचलित संग्रहण
 
 Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
 

From 3020da5dabb05cd70671af2f5f23013fb8dd1803 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:10 -0500
Subject: [PATCH 1302/1325] New translations deploy-using-subgraph-studio.mdx
 (Swahili)

---
 .../deploy-using-subgraph-studio.mdx          | 137 ++++++++++++++++++
 1 file changed, 137 insertions(+)
 create mode 100644 website/pages/sw/deploying/deploy-using-subgraph-studio.mdx

diff --git a/website/pages/sw/deploying/deploy-using-subgraph-studio.mdx b/website/pages/sw/deploying/deploy-using-subgraph-studio.mdx
new file mode 100644
index 000000000000..a3b2f150a79c
--- /dev/null
+++ b/website/pages/sw/deploying/deploy-using-subgraph-studio.mdx
@@ -0,0 +1,137 @@
+---
+title: Deploy Using Subgraph Studio
+---
+
+Learn how to deploy your subgraph to Subgraph Studio.
+
+> Note: When you deploy a subgraph, you push it to Subgraph Studio, where you'll be able to test it. It's important to remember that deploying is not the same as publishing. When you publish a subgraph, you're publishing it on-chain.
+
+## Subgraph Studio Overview
+
+In [Subgraph Studio](https://thegraph.com/studio/), you can do the following:
+
+- View a list of subgraphs you've created
+- Manage, view details, and visualize the status of a specific subgraph
+- Create and manage your API keys for specific subgraphs
+- Restrict your API keys to specific domains and allow only certain Indexers to query with them
+- Create your subgraph
+- Deploy your subgraph using The Graph CLI
+- Test your subgraph in the playground environment
+- Integrate your subgraph in staging using the development query URL
+- Publish your subgraph to The Graph Network
+- Manage your billing
+
+## Install The Graph CLI
+
+Before deploying, you must install The Graph CLI.
+
+You must have [Node.js](https://nodejs.org/) and a package manager of your choice (`npm`, `yarn` or `pnpm`) installed to use The Graph CLI. Check for the [most recent](https://github.com/graphprotocol/graph-tooling/releases?q=%40graphprotocol%2Fgraph-cli&expanded=true) CLI version.
+
+### Install with yarn
+
+```bash
+yarn global add @graphprotocol/graph-cli
+```
+
+### Install with npm
+
+```bash
+npm install -g @graphprotocol/graph-cli
+```
+
+## Get Started
+
+1. Open [Subgraph Studio](https://thegraph.com/studio/).
+2. Connect your wallet to sign in.
+   - You can do this via MetaMask, Coinbase Wallet, WalletConnect, or Safe.
+3. After you sign in, your unique deploy key will be displayed on your subgraph details page.
+   - The deploy key allows you to publish your subgraphs or manage your API keys and billing. It is unique but can be regenerated if you think it has been compromised.
+
+> Important: You need an API key to query subgraphs
+
+### How to Create a Subgraph in Subgraph Studio
+
+<VideoEmbed youtube="nGIFuC69bSA" />
+
+> For additional written detail, review the [Quick Start](/quick-start/).
+
+### Subgraph Compatibility with The Graph Network
+
+In order to be supported by Indexers on The Graph Network, subgraphs must:
+
+- Index a [supported network](/developing/supported-networks)
+- Must not use any of the following features:
+  - ipfs.cat & ipfs.map
+  - Non-fatal errors
+  - Grafting
+
+## Initialize Your Subgraph
+
+Once your subgraph has been created in Subgraph Studio, you can initialize its code through the CLI using this command:
+
+```bash
+graph init <SUBGRAPH_SLUG>
+```
+
+You can find the `<SUBGRAPH_SLUG>` value on your subgraph details page in Subgraph Studio, see image below:
+
+![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
+
+After running `graph init`, you will be asked to input the contract address, network, and an ABI that you want to query. This will generate a new folder on your local machine with some basic code to start working on your subgraph. You can then finalize your subgraph to make sure it works as expected.
+
+## Graph Auth
+
+Before you can deploy your subgraph to Subgraph Studio, you need to log into your account within the CLI. To do this, you will need your deploy key, which you can find under your subgraph details page.
+
+Then, use the following command to authenticate from the CLI:
+
+```bash
+graph auth <DEPLOY KEY>
+```
+
+## Deploying a Subgraph
+
+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.
+
+Use the following CLI command to deploy your subgraph:
+
+```bash
+graph deploy <SUBGRAPH_SLUG>
+```
+
+After running this command, the CLI will ask for a version label.
+
+- It's strongly recommended to use [semver](https://semver.org/) for versioning like `0.0.1`. That said, you are free to choose any string as version such as `v1`, `version1`, or `asdf`.
+- The labels you create will be visible in Graph Explorer and can be used by curators to decide if they want to signal on a specific version or not, so choose them wisely.
+
+## Testing Your Subgraph
+
+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.
+
+Use Subgraph Studio to check the logs on the dashboard and look for any errors with your subgraph.
+
+## Publish Your Subgraph
+
+In order to publish your subgraph successfully, review [publishing a subgraph](/publishing/publishing-a-subgraph/).
+
+## Versioning Your Subgraph with the CLI
+
+If you want to update your subgraph, you can do the following:
+
+- You can deploy a new version to Studio using the CLI (it will only be private at this point).
+- Once you're happy with it, you can publish your new deployment to [Graph Explorer](https://thegraph.com/explorer).
+- This action will create a new version of your subgraph that Curators can start signaling on and Indexers can index.
+
+You can also update your subgraph's metadata without publishing a new version. You can update your subgraph details in Studio (under the profile picture, name, description, etc.) by checking an option called **Update Details** in [Graph Explorer](https://thegraph.com/explorer). If this is checked, an on-chain transaction will be generated that updates subgraph details in Explorer without having to publish a new version with a new deployment.
+
+> Note: There are costs associated with publishing a new version of a subgraph to the network. In addition to the transaction fees, you must also fund a part of the curation tax on the auto-migrating signal. You cannot publish a new version of your subgraph if Curators have not signaled on it. For more information, please read more [here](/network/curating/).
+
+## Automatic Archiving of Subgraph Versions
+
+Whenever you deploy a new subgraph version in Subgraph Studio, the previous version will be archived. Archived versions won't be indexed/synced and therefore cannot be queried. You can unarchive an archived version of your subgraph in Subgraph Studio.
+
+> Note: Previous versions of non-published subgraphs deployed to Studio will be automatically archived.
+
+![Subgraph Studio - Unarchive](/img/Unarchive.png)

From 9185009d875c38b5749eea63b0f8fbcb09272679 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:11 -0500
Subject: [PATCH 1303/1325] New translations enums.mdx (Spanish)

---
 website/pages/es/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/es/cookbook/enums.mdx b/website/pages/es/cookbook/enums.mdx
index a10970c1539f..29b5b2d0bf38 100644
--- a/website/pages/es/cookbook/enums.mdx
+++ b/website/pages/es/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Recursos Adicionales
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 87dc9ce4f223e5584cff30c12c3b276358e2c295 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:12 -0500
Subject: [PATCH 1304/1325] New translations enums.mdx (Arabic)

---
 website/pages/ar/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ar/cookbook/enums.mdx b/website/pages/ar/cookbook/enums.mdx
index a10970c1539f..9508aa864b6c 100644
--- a/website/pages/ar/cookbook/enums.mdx
+++ b/website/pages/ar/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## مصادر إضافية
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From caf46a2b338f5f988359776371689ad517f52886 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:13 -0500
Subject: [PATCH 1305/1325] New translations enums.mdx (Czech)

---
 website/pages/cs/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/cs/cookbook/enums.mdx b/website/pages/cs/cookbook/enums.mdx
index a10970c1539f..71f3f784a0eb 100644
--- a/website/pages/cs/cookbook/enums.mdx
+++ b/website/pages/cs/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Další zdroje
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From d737b1f678c1828d26b5844553dfaa33618255be Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:14 -0500
Subject: [PATCH 1306/1325] New translations enums.mdx (German)

---
 website/pages/de/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/de/cookbook/enums.mdx b/website/pages/de/cookbook/enums.mdx
index a10970c1539f..8db81193d949 100644
--- a/website/pages/de/cookbook/enums.mdx
+++ b/website/pages/de/cookbook/enums.mdx
@@ -50,7 +50,7 @@ type Token @entity {
 
 In this schema, `TokenStatus` is a simple string with no specific, allowed values.
 
-#### Why is this a problem?
+#### Warum ist das ein Problem?
 
 - There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
 - It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.

From ec8476c7930e5cf16b1667aaaa932f3b27c46670 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:16 -0500
Subject: [PATCH 1307/1325] New translations enums.mdx (Japanese)

---
 website/pages/ja/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ja/cookbook/enums.mdx b/website/pages/ja/cookbook/enums.mdx
index a10970c1539f..8df21d2960f9 100644
--- a/website/pages/ja/cookbook/enums.mdx
+++ b/website/pages/ja/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## その他のリソース
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From f4e1f245c879028607d5b9896066102bcbf0f598 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:19 -0500
Subject: [PATCH 1308/1325] New translations enums.mdx (Portuguese)

---
 website/pages/pt/cookbook/enums.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/pt/cookbook/enums.mdx b/website/pages/pt/cookbook/enums.mdx
index a10970c1539f..ddfda1aae5bd 100644
--- a/website/pages/pt/cookbook/enums.mdx
+++ b/website/pages/pt/cookbook/enums.mdx
@@ -50,7 +50,7 @@ type Token @entity {
 
 In this schema, `TokenStatus` is a simple string with no specific, allowed values.
 
-#### Why is this a problem?
+#### Por que isto é um problema?
 
 - There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
 - It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Outros Recursos
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 808e4c5067a864f588507bdcb52b7f195f36a3e4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:20 -0500
Subject: [PATCH 1309/1325] New translations enums.mdx (Swedish)

---
 website/pages/sv/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/sv/cookbook/enums.mdx b/website/pages/sv/cookbook/enums.mdx
index a10970c1539f..2fc0efcc5831 100644
--- a/website/pages/sv/cookbook/enums.mdx
+++ b/website/pages/sv/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Ytterligare resurser
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From ef22eb540ae47ca15d3665216dcb7fa2881690e3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:21 -0500
Subject: [PATCH 1310/1325] New translations enums.mdx (Turkish)

---
 website/pages/tr/cookbook/enums.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/tr/cookbook/enums.mdx b/website/pages/tr/cookbook/enums.mdx
index a10970c1539f..99d1a01a02c0 100644
--- a/website/pages/tr/cookbook/enums.mdx
+++ b/website/pages/tr/cookbook/enums.mdx
@@ -50,7 +50,7 @@ type Token @entity {
 
 In this schema, `TokenStatus` is a simple string with no specific, allowed values.
 
-#### Why is this a problem?
+#### Bu neden bir sorun?
 
 - There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
 - It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## Ek Kaynaklar
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 04fae11ea9921cefe38fdab99c7ed195c8bae40d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:22 -0500
Subject: [PATCH 1311/1325] New translations enums.mdx (Chinese Simplified)

---
 website/pages/zh/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/cookbook/enums.mdx b/website/pages/zh/cookbook/enums.mdx
index a10970c1539f..43d1ad4cc0c2 100644
--- a/website/pages/zh/cookbook/enums.mdx
+++ b/website/pages/zh/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## 其他资源
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 1ba3696f4ceb0cfb91c1887f27095b5a746565e1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:23 -0500
Subject: [PATCH 1312/1325] New translations enums.mdx (Urdu (Pakistan))

---
 website/pages/ur/cookbook/enums.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/ur/cookbook/enums.mdx b/website/pages/ur/cookbook/enums.mdx
index a10970c1539f..8991c45dd81a 100644
--- a/website/pages/ur/cookbook/enums.mdx
+++ b/website/pages/ur/cookbook/enums.mdx
@@ -269,6 +269,6 @@ Expected output includes the marketplaces that meet the criteria, each represent
 }
 ```
 
-## Additional Resources
+## اضافی وسائل
 
 For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 09fbc1086d63d75d775f619588c8fceddf5acd87 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 15:58:25 -0500
Subject: [PATCH 1313/1325] New translations enums.mdx (Swahili)

---
 website/pages/sw/cookbook/enums.mdx | 274 ++++++++++++++++++++++++++++
 1 file changed, 274 insertions(+)
 create mode 100644 website/pages/sw/cookbook/enums.mdx

diff --git a/website/pages/sw/cookbook/enums.mdx b/website/pages/sw/cookbook/enums.mdx
new file mode 100644
index 000000000000..a10970c1539f
--- /dev/null
+++ b/website/pages/sw/cookbook/enums.mdx
@@ -0,0 +1,274 @@
+---
+title: Categorize NFT Marketplaces Using Enums
+---
+
+Use Enums to make your code cleaner and less error-prone. Here's a full example of using Enums on NFT marketplaces.
+
+## What are Enums?
+
+Enums, or enumeration types, are a specific data type that allows you to define a set of specific, allowed values.
+
+### Example of Enums in Your Schema
+
+If you're building a subgraph to track the ownership history of tokens on a marketplace, each token might go through different ownerships, such as `OriginalOwner`, `SecondOwner`, and `ThirdOwner`. By using enums, you can define these specific ownerships, ensuring only predefined values are assigned.
+
+You can define enums in your schema, and once defined, you can use the string representation of the enum values to set an enum field on an entity.
+
+Here's what an enum definition might look like in your schema, based on the example above:
+
+```graphql
+enum TokenStatus {
+  OriginalOwner
+  SecondOwner
+  ThirdOwner
+}
+```
+
+This means that when you use the `TokenStatus` type in your schema, you expect it to be exactly one of predefined values: `OriginalOwner`, `SecondOwner`, or `ThirdOwner`, ensuring consistency and validity.
+
+To learn more about enums, check out [Creating a Subgraph](/developing/creating-a-subgraph/#enums) and [GraphQL documentation](https://graphql.org/learn/schema/#enumeration-types).
+
+## Benefits of Using Enums
+
+- **Clarity:** Enums provide meaningful names for values, making data easier to understand.
+- **Validation:** Enums enforce strict value definitions, preventing invalid data entries.
+- **Maintainability:** When you need to change or add new categories, enums allow you to do this in a focused manner.
+
+### Without Enums
+
+If you choose to define the type as a string instead of using an Enum, your code might look like this:
+
+```graphql
+type Token @entity {
+  id: ID!
+  tokenId: BigInt!
+  owner: Bytes! # Owner of the token
+  tokenStatus: String! # String field to track token status
+  timestamp: BigInt!
+}
+```
+
+In this schema, `TokenStatus` is a simple string with no specific, allowed values.
+
+#### Why is this a problem?
+
+- There's no restriction of `TokenStatus` values, so any string can be accidentally assigned. This makes it hard to ensure that only valid statuses like `OriginalOwner`, `SecondOwner`, or `ThirdOwner` are set.
+- It's easy to make typos such as `Orgnalowner` instead of `OriginalOwner`, making the data and potential queries unreliable.
+
+### With Enums
+
+Instead of assigning free-form strings, you can define an enum for `TokenStatus` with specific values: `OriginalOwner`, `SecondOwner`, or `ThirdOwner`. Using an enum ensures only allowed values are used.
+
+Enums provide type safety, minimize typo risks, and ensure consistent and reliable results.
+
+## Defining Enums for NFT Marketplaces
+
+> Note: The following guide uses the CryptoCoven NFT smart contract.
+
+To define enums for the various marketplaces where NFTs are traded, use the following in your subgraph schema:
+
+```gql
+# Enum for Marketplaces that the CryptoCoven contract interacted with(likely a Trade/Mint)
+enum Marketplace {
+  OpenSeaV1 # Represents when a CryptoCoven NFT is traded on the marketplace
+  OpenSeaV2 # Represents when a CryptoCoven NFT is traded on the OpenSeaV2 marketplace
+  SeaPort # Represents when a CryptoCoven NFT is traded on the SeaPort marketplace
+  LooksRare # Represents when a CryptoCoven NFT is traded on the LookRare marketplace
+  # ...and other marketplaces
+}
+```
+
+## Using Enums for NFT Marketplaces
+
+Once defined, enums can be used throughout your subgraph to categorize transactions or events.
+
+For example, when logging NFT sales, you can specify the marketplace involved in the trade using the enum.
+
+### Implementing a Function for NFT Marketplaces
+
+Here's how you can implement a function to retrieve the marketplace name from the enum as a string:
+
+```ts
+export function getMarketplaceName(marketplace: Marketplace): string {
+  // Using if-else statements to map the enum value to a string
+  if (marketplace === Marketplace.OpenSeaV1) {
+    return 'OpenSeaV1' // If the marketplace is OpenSea, return its string representation
+  } else if (marketplace === Marketplace.OpenSeaV2) {
+    return 'OpenSeaV2'
+  } else if (marketplace === Marketplace.SeaPort) {
+    return 'SeaPort' // If the marketplace is SeaPort, return its string representation
+  } else if (marketplace === Marketplace.LooksRare) {
+    return 'LooksRare' // If the marketplace is LooksRare, return its string representation
+    // ... and other market places
+  }
+}
+```
+
+## Best Practices for Using Enums
+
+- **Consistent Naming:** Use clear, descriptive names for enum values to improve readability.
+- **Centralized Management:** Keep enums in a single file for consistency. This makes enums easier to update and ensures they are the single source of truth.
+- **Documentation:** Add comments to enum to clarify their purpose and usage.
+
+## Using Enums in Queries
+
+Enums in queries help you improve data quality and make your results easier to interpret. They function as filters and response elements, ensuring consistency and reducing errors in marketplace values.
+
+**Specifics**
+
+- **Filtering with Enums:** Enums provide clear filters, allowing you to confidently include or exclude specific marketplaces.
+- **Enums in Responses:** Enums guarantee that only recognized marketplace names are returned, making the results standardized and accurate.
+
+### Sample Queries
+
+#### Query 1: Account With The Highest NFT Marketplace Interactions
+
+This query does the following:
+
+- It finds the account with the highest unique NFT marketplace interactions, which is great for analyzing cross-marketplace activity.
+- The marketplaces field uses the marketplace enum, ensuring consistent and validated marketplace values in the response.
+
+```gql
+{
+  accounts(first: 1, orderBy: uniqueMarketplacesCount, orderDirection: desc) {
+    id
+    sendCount
+    receiveCount
+    totalSpent
+    uniqueMarketplacesCount
+    marketplaces {
+      marketplace # This field returns the enum value representing the marketplace
+    }
+  }
+}
+```
+
+#### Returns
+
+This response provides account details and a list of unique marketplace interactions with enum values for standardized clarity:
+
+```gql
+{
+  "data": {
+    "accounts": [
+      {
+        "id": "0xb3abc96cb9a61576c03c955d75b703a890a14aa0",
+        "sendCount": "44",
+        "receiveCount": "44",
+        "totalSpent": "1197500000000000000",
+        "uniqueMarketplacesCount": "7",
+        "marketplaces": [
+          {
+            "marketplace": "OpenSeaV1"
+          },
+          {
+            "marketplace": "OpenSeaV2"
+          },
+          {
+            "marketplace": "GenieSwap"
+          },
+          {
+            "marketplace": "CryptoCoven"
+          },
+          {
+            "marketplace": "Unknown"
+          },
+          {
+            "marketplace": "LooksRare"
+          },
+          {
+            "marketplace": "NFTX"
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
+#### Query 2: Most Active Marketplace for CryptoCoven transactions
+
+This query does the following:
+
+- It identifies the marketplace with the highest volume of CryptoCoven transactions.
+- It uses the marketplace enum to ensure that only valid marketplace types appear in the response, adding reliability and consistency to your data.
+
+```gql
+{
+  marketplaceInteractions(first: 1, orderBy: transactionCount, orderDirection: desc) {
+    marketplace
+    transactionCount
+  }
+}
+```
+
+#### Result 2
+
+The expected response includes the marketplace and the corresponding transaction count, using the enum to indicate the marketplace type:
+
+```gql
+{
+  "data": {
+    "marketplaceInteractions": [
+      {
+        "marketplace": "Unknown",
+        "transactionCount": "222"
+      }
+    ]
+  }
+}
+```
+
+#### Query 3: Marketplace Interactions with High Transaction Counts
+
+This query does the following:
+
+- It retrieves the top four marketplaces with over 100 transactions, excluding "Unknown" marketplaces.
+- It uses enums as filters to ensure that only valid marketplace types are included, increasing accuracy.
+
+```gql
+{
+  marketplaceInteractions(
+    first: 4
+    orderBy: transactionCount
+    orderDirection: desc
+    where: { transactionCount_gt: "100", marketplace_not: "Unknown" }
+  ) {
+    marketplace
+    transactionCount
+  }
+}
+```
+
+#### Result 3
+
+Expected output includes the marketplaces that meet the criteria, each represented by an enum value:
+
+```gql
+{
+  "data": {
+    "marketplaceInteractions": [
+      {
+        "marketplace": "NFTX",
+        "transactionCount": "201"
+      },
+      {
+        "marketplace": "OpenSeaV1",
+        "transactionCount": "148"
+      },
+      {
+        "marketplace": "CryptoCoven",
+        "transactionCount": "117"
+      },
+      {
+        "marketplace": "OpenSeaV1",
+        "transactionCount": "111"
+      }
+    ]
+  }
+}
+```
+
+## Additional Resources
+
+For additional information, check out this guide's [repo](https://github.com/chidubemokeke/Subgraph-Tutorial-Enums).

From 9d87dbc6e57ee76766a6232ebeff2c05a5a3879c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:29:42 -0500
Subject: [PATCH 1314/1325] New translations tap.mdx (Hindi)

---
 website/pages/hi/tap.mdx | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/website/pages/hi/tap.mdx b/website/pages/hi/tap.mdx
index 8ae86546431a..85f9f8b123ac 100644
--- a/website/pages/hi/tap.mdx
+++ b/website/pages/hi/tap.mdx
@@ -33,11 +33,11 @@ TAP एक प्रेषक को एक प्राप्तकर्ता
 
 1. एक Indexer आवंटन बंद करता है।
 
-2. <recently-closed-allocation-buffer> अवधि, tap-agent सभी लंबित प्राप्तियों को उस विशेष आवंटन के लिए लेता है और एक RAV में समेकन के लिए अनुरोध करता है, इसे 'last' के रूप में चिह्नित करता है।
+2. `<recently-closed-allocation-buffer> period, tap-agent` सभी लंबित प्राप्तियों को उस विशेष आवंटन के लिए लेता है और एक RAV में समेकन के लिए अनुरोध करता है, इसे 'last' के रूप में चिह्नित करता है।
 
 3. indexer-agent सभी पिछले RAVS लेता है और ब्लॉकचेन को रिडीम अनुरोध भेजता है, जो redeem_at के मान को अपडेट करेगा।
 
-4. <finality-time> अवधि के दौरान, indexer-agent यह देखता है कि क्या ब्लॉकचेन में कोई पुनर्गठन है जो लेनदेन को पूर्ववत करता है।
+4. `<finality-time>` अवधि के दौरान, `indexer-agent` यह देखता है कि क्या ब्लॉकचेन में कोई पुनर्गठन है जो लेनदेन को पूर्ववत करता है।
 
    - यदि इसे रिवर्ट किया गया, तो RAV को फिर से ब्लॉकचेन पर भेजा जाता है। यदि इसे रिवर्ट नहीं किया गया, तो इसे final के रूप में चिह्नित किया जाता है।
 

From 1d4b3e163eef48ada8503ccf30e39380bf9afa21 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:30:32 -0500
Subject: [PATCH 1315/1325] New translations api.mdx (Czech)

---
 website/pages/cs/developing/graph-ts/api.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/cs/developing/graph-ts/api.mdx b/website/pages/cs/developing/graph-ts/api.mdx
index 624e5b95d141..15d84077faf5 100644
--- a/website/pages/cs/developing/graph-ts/api.mdx
+++ b/website/pages/cs/developing/graph-ts/api.mdx
@@ -33,7 +33,7 @@ Knihovna `@graphprotocol/graph-ts` poskytuje následující API:
 | :---: | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                     |
 | 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity.                                                                                                                                                                      |
-| 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum<0/Přidání pole `receipt` do objektu Ethereum událost                                                                                                                  |
+| 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum<br />Přidání pole `receipt` do objektu Ethereum událost                                                                                                               |
 | 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction<br />Přidáno `baseFeePerGas` do objektu Ethereum bloku                                                                                                                      |
 | 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` |
 | 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall                                                                                                                                                           |

From c908b4bc294718a5a485a38a44dbb6e13af9c651 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:32:12 -0500
Subject: [PATCH 1316/1325] New translations deploy-using-subgraph-studio.mdx
 (Hindi)

---
 website/pages/hi/deploying/deploy-using-subgraph-studio.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx b/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
index ae89fa2d38fd..3f07a9b3b2e4 100644
--- a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
@@ -73,7 +73,7 @@ In order to be supported by Indexers on The Graph Network, subgraphs must:
 graph init <SUBGRAPH_SLUG>
 ```
 
-आप <SUBGRAPH_SLUG> मान को अपने subgraph विवरण पृष्ठ पर Subgraph Studio में पा सकते हैं, नीचे दी गई छवि देखें:
+आप `<SUBGRAPH_SLUG>` मान को अपने subgraph विवरण पृष्ठ पर Subgraph Studio में पा सकते हैं, नीचे दी गई छवि देखें:
 
 ![Subgraph Studio - Slug](/img/doc-subgraph-slug.png)
 

From d5c07acd0c0b50b13b21bd531d7f60cb7e7cfec3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:33:05 -0500
Subject: [PATCH 1317/1325] New translations avoid-eth-calls.mdx (Hindi)

---
 website/pages/hi/cookbook/avoid-eth-calls.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/cookbook/avoid-eth-calls.mdx b/website/pages/hi/cookbook/avoid-eth-calls.mdx
index 1892134f2a4c..9e56fbef5970 100644
--- a/website/pages/hi/cookbook/avoid-eth-calls.mdx
+++ b/website/pages/hi/cookbook/avoid-eth-calls.mdx
@@ -91,7 +91,7 @@ export function handleTransferWithPool(event: TransferWithPool): void {
   ERC20.poolInfo: ERC20[event.address].getPoolInfo(event.params.to)
 ```
 
-पीले रंग में हाइलाइट किया गया हिस्सा कॉल डिक्लेरेशन है। कॉल के पहले वाले हिस्से में जो टेक्स्ट लेबल है, वह केवल त्रुटि संदेशों के लिए उपयोग किया जाता है। कॉल के बाद वाला हिस्सा Contract[address].function(params) के रूप में होता है। address और params के लिए मान event.address और event.params.<name> अनुमेय हैं।
+पीले रंग में हाइलाइट किया गया हिस्सा कॉल डिक्लेरेशन है। कॉल के पहले वाले हिस्से में जो टेक्स्ट लेबल है, वह केवल त्रुटि संदेशों के लिए उपयोग किया जाता है। कॉल के बाद वाला हिस्सा Contract[address].function(params) के रूप में होता है। address और params के लिए मान `event.address` और `event.params.<name>` अनुमेय हैं।
 
 Handler स्वयं इस eth_call के परिणाम तक ठीक उसी तरह पहुंचता है जैसे पिछले अनुभाग में, अनुबंध से बाइंडिंग करके और कॉल करके। graph-node घोषित eth_calls के परिणामों को मेमोरी में कैश करता है और हैंडलर से कॉल इस मेमोरी कैश से परिणाम प्राप्त करेगा, बजाय इसके कि एक वास्तविक RPC कॉल की जाए।
 

From b9911424db53c710b43b6f3a189eb794eacfa44d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:33:09 -0500
Subject: [PATCH 1318/1325] New translations pruning.mdx (Hindi)

---
 website/pages/hi/cookbook/pruning.mdx | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/website/pages/hi/cookbook/pruning.mdx b/website/pages/hi/cookbook/pruning.mdx
index dbf07aa15e60..e583b0c2f373 100644
--- a/website/pages/hi/cookbook/pruning.mdx
+++ b/website/pages/hi/cookbook/pruning.mdx
@@ -13,8 +13,8 @@ Manifest में एक section को indexerHints के नाम से 
 indexerHints में तीन prune विकल्प होते हैं:
 
 - prune: auto: आवश्यक न्यूनतम इतिहास को बनाए रखता है जैसा कि Indexer द्वारा निर्धारित किया गया है, जो क्वेरी प्रदर्शन को अनुकूलित करता है। यह सामान्यतः अनुशंसित सेटिंग है और यह सभी subgraphs के लिए डिफ़ॉल्ट है जो graph-cli >= 0.66.0 द्वारा बनाए गए हैं।
-- prune: <Number of blocks to retain>: ऐतिहासिक ब्लॉकों को बनाए रखने की संख्या पर एक कस्टम सीमा निर्धारित करता है।
-- prune: never: ऐतिहासिक डेटा का कोई छंटाई नहीं; पूरी इतिहास को बनाए रखता है और यह डिफ़ॉल्ट है यदि indexerHints अनुभाग नहीं है। prune: never को तब चुना जाना चाहिए यदि Time Travel Queries (/querying/graphql-api/#time-travel-queries)की आवश्यकता हो।
+- `prune: <Number of blocks to retain>`: ऐतिहासिक ब्लॉकों को बनाए रखने की संख्या पर एक कस्टम सीमा निर्धारित करता है।
+- `prune: never`: ऐतिहासिक डेटा का कोई छंटाई नहीं; पूरी इतिहास को बनाए रखता है और यह डिफ़ॉल्ट है यदि indexerHints अनुभाग नहीं है। `prune: never` को तब चुना जाना चाहिए यदि Time Travel Queries (/querying/graphql-api/#time-travel-queries) की आवश्यकता हो।
 
 हम अपने 'subgraph' में indexerHints जोड़ सकते हैं हमारे subgraph.yaml को अपडेट करके:
 
@@ -32,9 +32,9 @@ dataSources:
 
 ## महत्वपूर्ण विचार
 
-- यदि Time Travel Queries(/querying/graphql-api/#time-travel-queries) की आवश्यकता हो और प्रूनिंग भी की जाए, तो Time Travel Query कार्यक्षमता बनाए रखने के लिए प्रूनिंग को सही ढंग से किया जाना चाहिए। इसलिए, Time Travel Queries के साथ indexerHints: prune: auto का उपयोग करना सामान्यतः अनुशंसित नहीं है। इसके बजाय, उस ब्लॉक ऊंचाई तक सही ढंग से प्रून करने के लिए indexerHints: prune: <Number of blocks to retain> का उपयोग करें जो Time Travel Queries के लिए आवश्यक ऐतिहासिक डेटा को बनाए रखता है, या prune: never का उपयोग करें ताकि सभी डेटा बनाए रखा जा सके।
+- यदि Time Travel Queries(/querying/graphql-api/#time-travel-queries) की आवश्यकता हो और प्रूनिंग भी की जाए, तो Time Travel Query कार्यक्षमता बनाए रखने के लिए प्रूनिंग को सही ढंग से किया जाना चाहिए। इसलिए, Time Travel Queries के साथ indexerHints: prune: auto का उपयोग करना सामान्यतः अनुशंसित नहीं है। इसके बजाय, उस ब्लॉक ऊंचाई तक सही ढंग से प्रून करने के लिए `indexerHints: prune: <Number of blocks to retain>` का उपयोग करें जो Time Travel Queries के लिए आवश्यक ऐतिहासिक डेटा को बनाए रखता है, या prune: never का उपयोग करें ताकि सभी डेटा बनाए रखा जा सके।
 
-- यह 'grafting' (/cookbook/grafting/) को उस ब्लॉक ऊँचाई पर करना संभव नहीं है जो छंटनी (pruned) की गई है। यदि 'grafting' नियमित रूप से किया जाता है और छंटनी (pruning) की आवश्यकता है, तो यह अनुशंसा की जाती है कि indexerHints: prune: <Number of blocks to retain> का उपयोग किया जाए जो सटीक रूप से एक निश्चित संख्या में ब्लॉकों (जैसे, छह महीने के लिए पर्याप्त) को बनाए रखेगा।
+- यह 'grafting' (/cookbook/grafting/) को उस ब्लॉक ऊँचाई पर करना संभव नहीं है जो छंटनी (pruned) की गई है। यदि 'grafting' नियमित रूप से किया जाता है और छंटनी (pruning) की आवश्यकता है, तो यह अनुशंसा की जाती है कि `indexerHints: prune: <Number of blocks to retain>` का उपयोग किया जाए जो सटीक रूप से एक निश्चित संख्या में ब्लॉकों (जैसे, छह महीने के लिए पर्याप्त) को बनाए रखेगा।
 
 ## निष्कर्ष
 

From e976d3a3ada178dbdff6a32dfb86c9b9c626a154 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:35:54 -0500
Subject: [PATCH 1319/1325] New translations assemblyscript-migration-guide.mdx
 (Russian)

---
 .../assemblyscript-migration-guide.mdx        | 157 +-----------------
 1 file changed, 2 insertions(+), 155 deletions(-)

diff --git a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
index efcb37d2c28d..1047cc70ad5b 100644
--- a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
@@ -27,12 +27,8 @@ title: Руководство по миграции AssemblyScript
 - Добавлена поддержка литеральных строк шаблона ([v0.18.17](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.17))
 - Добавление `encodeURI(Component)` и `decodeURI(Component)` ([v0.18.27](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.27))
 - Добавление `toString`, `toDateString` и `toTimeString` к `Date` ([v0.18.29](https://github.com/ AssemblyScript/assemblyscript/releases/tag/v0.18.29))
-- Добавление `toUTCString` для `Date` (
-v0.18.30</а>)</li> 
-  
-  - Добавление встроенного типа `nonnull/NonNullable` ([v0.19.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.19.2))</ul> 
-
-
+- Добавление `toUTCString` для `Date` ([v0.18.30](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.30))
+- Добавление встроенного типа `nonnull/NonNullable` ([v0.19.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.19.2))
 
 ### Оптимизации
 
@@ -41,21 +37,15 @@ v0.18.30</а>)</li>
 - Кэширование большего количества обращений к полям в std Map и Set ([v0.17.8](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.17.8))
 - Оптимизация по двум степеням в `ipow32/64` ([v0.18.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.18.2))
 
-
-
 ### Прочее
 
 - Тип литерала массива теперь можно определить по его содержимому ([v0.9.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.0))
 - Стандартная библиотека обновлена до версии Unicode 13.0.0 ([v0.10.0](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.10.0))
 
-
-
 ## Как выполнить обновление?
 
 1. Измените мэппинги `apiVersion` в `subgraph.yaml` на `0.0.6`:
 
-
-
 ```yaml
 ...
 dataSources:
@@ -66,11 +56,8 @@ dataSources:
       ...
 ```
 
-
 2. Обновите используемый Вами `graph-cli` до `latest` версии, выполнив:
 
-
-
 ```bash
 # если он у Вас установлен глобально
 npm install --global @graphprotocol/graph-cli@latest
@@ -79,31 +66,21 @@ npm install --global @graphprotocol/graph-cli@latest
 npm install --save-dev @graphprotocol/graph-cli@latest
 ```
 
-
 3. Сделайте то же самое для `graph-ts`, но вместо глобальной установки сохраните его в своих основных зависимостях:
 
-
-
 ```bash
 npm install --save @graphprotocol/graph-ts@latest
 ```
 
-
 4. Следуйте остальной части руководства, чтобы исправить языковые изменения.
 5. Снова запустите `codegen` и `deploy`.
 
-
-
 ## Критические изменения
 
-
-
 ### Обнуляемость
 
 В более старой версии AssemblyScript можно было создать такой код:
 
-
-
 ```typescript
 function load(): Value | null { ... }
 
@@ -111,11 +88,8 @@ let maybeValue = load();
 maybeValue.aMethod();
 ```
 
-
 Однако в новой версии, поскольку значение обнуляемо, требуется проверка, например, такая:
 
-
-
 ```typescript
 let maybeValue = load()
 
@@ -124,39 +98,28 @@ if (maybeValue) {
 }
 ```
 
-
 Или принудительно вот такая:
 
-
-
 ```typescript
 let maybeValue = load()! // прерывается во время выполнения, если значение равно null
 
 maybeValue.aMethod()
 ```
 
-
 Если Вы не уверены, что выбрать, мы рекомендуем всегда использовать безопасную версию. Если значение не существует, Вы можете просто выполнить раннее выражение if с возвратом в обработчике субграфа.
 
-
-
 ### Затенение переменных
 
 Раньше можно было сделать [затенение переменных](https://en.wikipedia.org/wiki/Variable_shadowing) и код, подобный этому, работал:
 
-
-
 ```typescript
 let a = 10
 let b = 20
 let a = a + b
 ```
 
-
 Однако теперь это больше невозможно, и компилятор возвращает эту ошибку:
 
-
-
 ```typescript
 ERROR TS2451: Cannot redeclare block-scoped variable 'a'
 
@@ -164,29 +127,18 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
-
-
 Вам нужно будет переименовать дублированные переменные, если Вы используете затенение переменных.
-
-
 ### Нулевые сравнения
-
 Выполняя обновление своего субграфа, иногда Вы можете получить такие ошибки:
 
-
-
 ```typescript
 ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' is not assignable to type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt'.
      if (decimals == null) {
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
-
-
 Чтобы решить эту проблему, Вы можете просто изменить оператор `if` на что-то вроде этого:
 
-
-
 ```typescript
   if (!decimals) {
 
@@ -195,23 +147,17 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
   if (decimals === null) {
 ```
 
-
 Подобное относится к случаям, когда вместо == используется !=.
 
-
-
 ### Кастинг
 
 Раньше для кастинга обычно использовалось ключевое слово `as`, например:
 
-
-
 ```typescript
 let byteArray = new ByteArray(10)
 let uint8Array = byteArray as Uint8Array // equivalent to: <Uint8Array>byteArray
 ```
 
-
 Однако это работает только в двух случаях:
 
 - Примитивный кастинг (между такими типами, как `u8`, `i32`, `bool`; например: `let b: isize = 10; b as usize`);
@@ -219,8 +165,6 @@ let uint8Array = byteArray as Uint8Array // equivalent to: <Uint8Array>byteArray
 
 Примеры:
 
-
-
 ```typescript
 // примитивный кастинг
 let a: usize = 10
@@ -228,9 +172,6 @@ let b: isize = 5
 let c: usize = a + (b as usize)
 ```
 
-
-
-
 ```typescript
 // укрупнение по наследованию классов
 class Bytes extends Uint8Array {}
@@ -239,14 +180,11 @@ let bytes = new Bytes(2)
 // <Uint8Array>bytes // то же, что: bytes as Uint8Array
 ```
 
-
 Есть два сценария, в которых Вы можете захотеть выполнить преобразование, но использовать `as`/`<T>var` **небезопасно**:
 
 - Понижение уровня наследования классов (superclass → subclass)
 - Между двумя типами, имеющими общий супер класс
 
-
-
 ```typescript
 // понижение уровня наследования классов
 class Bytes extends Uint8Array {}
@@ -255,9 +193,6 @@ let uint8Array = new Uint8Array(2)
 // <Bytes>uint8Array // перерывы в работе :(
 ```
 
-
-
-
 ```typescript
 // между двумя типами, имеющими общий суперкласс
 class Bytes extends Uint8Array {}
@@ -267,11 +202,8 @@ let bytes = new Bytes(2)
 // <ByteArray>bytes // перерывы в работе :(
 ```
 
-
 В таких случаях можно использовать функцию `changetype<T>`:
 
-
-
 ```typescript
 // понижение уровня наследования классов
 class Bytes extends Uint8Array {}
@@ -280,9 +212,6 @@ let uint8Array = new Uint8Array(2)
 changetype<Bytes>(uint8Array) // работает :)
 ```
 
-
-
-
 ```typescript
 // между двумя типами, имеющими общий суперкласс
 class Bytes extends Uint8Array {}
@@ -292,11 +221,8 @@ let bytes = new Bytes(2)
 changetype<ByteArray>(bytes) // работает :)
 ```
 
-
 Если Вы просто хотите удалить значение NULL, Вы можете продолжать использовать оператор `as` (или `<T>variable`), но помните, что значение не может быть нулевым, иначе оно сломается.
 
-
-
 ```typescript
 // удалить значение NULL
 let previousBalance = AccountBalance.load(balanceId) // AccountBalance | null
@@ -308,7 +234,6 @@ if (previousBalance != null) {
 let newBalance = new AccountBalance(balanceId)
 ```
 
-
 В случае обнуления мы рекомендуем Вам обратить внимание на [функцию проверки обнуления](https://www.assemblyscript.org/basics.html#nullability-checks), это сделает ваш код чище 🙂
 
 Также мы добавили еще несколько статических методов в некоторые типы, чтобы облегчить кастинг:
@@ -318,14 +243,10 @@ let newBalance = new AccountBalance(balanceId)
 - BigInt.fromByteArray
 - ByteArray.fromBigInt
 
-
-
 ### Проверка нулевого значения с доступом к свойству
 
 Чтобы применить [функцию проверки на нулевое значение](https://www.assemblyscript.org/basics.html#nullability-checks), Вы можете использовать операторы `if` или тернарный оператор (`?` и `:`) следующим образом:
 
-
-
 ```typescript
 let something: string | null = 'data'
 
@@ -342,11 +263,8 @@ if (something) {
 }
 ```
 
-
 Однако это работает только тогда, когда Вы выполняете `if` / тернарную операцию для переменной, а не для доступа к свойству, например:
 
-
-
 ```typescript
 class Container {
   data: string | null
@@ -358,23 +276,16 @@ container.data = 'data'
 let somethingOrElse: string = container.data ? container.data : 'else' // не компилируется
 ```
 
-
 В результате чего выдается ошибка:
 
-
-
 ```typescript
 ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/string/String'.
 
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
-
-
 Чтобы решить эту проблему, Вы можете создать переменную для доступа к этому свойству, чтобы компилятор мог выполнять проверку допустимости значений NULL:
 
-
-
 ```typescript
 class Container {
   data: string | null
@@ -388,15 +299,10 @@ let data = container.data
 let somethingOrElse: string = data ? data : 'else' // компилируется просто отлично :)
 ```
 
-
-
-
 ### Перегрузка оператора при доступе к свойствам
 
 Если Вы попытаетесь суммировать (например) тип, допускающий значение Null (из доступа к свойству), с типом, не допускающим значение Null, компилятор AssemblyScript вместо того, чтобы выдать предупреждение об ошибке компиляции, предупреждающую, что одно из значений допускает значение Null, просто компилируется молча, давая возможность сломать код во время выполнения.
 
-
-
 ```typescript
 class BigInt extends Uint8Array {
   @operator('+')
@@ -419,11 +325,8 @@ let wrapper = new Wrapper(y)
 wrapper.n = wrapper.n + x // не выдает ошибок времени компиляции, как это должно быть
 ```
 
-
 Мы открыли вопрос по этому поводу для компилятора AssemblyScript, но пока, если Вы выполняете подобные операции в своих мэппингах субграфов, Вам следует изменить их так, чтобы перед этим выполнялась проверка на нулевое значение.
 
-
-
 ```typescript
 let wrapper = new Wrapper(y)
 
@@ -434,37 +337,26 @@ if (!wrapper.n) {
 wrapper.n = wrapper.n + x // теперь `n` гарантированно будет BigInt
 ```
 
-
-
-
 ### Инициализация значения
 
 Если у Вас есть такой код:
 
-
-
 ```typescript
 var value: Type // null
 value.x = 10
 value.y = 'content'
 ```
 
-
 Он будет скомпилирован, но сломается во время выполнения. Это происходит из-за того, что значение не было инициализировано, поэтому убедитесь, что Ваш субграф инициализировал свои значения, например так:
 
-
-
 ```typescript
 var value = new Type() // initialized
 value.x = 10
 value.y = 'content'
 ```
 
-
 Также, если у Вас есть свойства, допускающие значение NULL, в объекте GraphQL, например:
 
-
-
 ```graphql
 type Total @entity {
   id: Bytes!
@@ -472,11 +364,8 @@ type Total @entity {
 }
 ```
 
-
 И у Вас есть код, аналогичный этому:
 
-
-
 ```typescript
 let total = Total.load('latest')
 
@@ -487,11 +376,8 @@ if (total === null) {
 total.amount = total.amount + BigInt.fromI32(1)
 ```
 
-
 Вам необходимо убедиться, что значение `total.amount` инициализировано, потому что, если Вы попытаетесь получить доступ к сумме, как в последней строке, произойдет сбой. Таким образом, Вы либо инициализируете его первым:
 
-
-
 ```typescript
 let total = Total.load('latest')
 
@@ -503,11 +389,8 @@ if (total === null) {
 total.tokens = total.tokens + BigInt.fromI32(1)
 ```
 
-
 Или Вы можете просто изменить свою схему GraphQL, чтобы не использовать тип, допускающий значение NULL для этого свойства. Тогда мы инициализируем его нулем на этапе `codegen` 😉
 
-
-
 ```graphql
 type Total @entity {
   id: Bytes!
@@ -515,9 +398,6 @@ type Total @entity {
 }
 ```
 
-
-
-
 ```typescript
 let total = Total.load('latest')
 
@@ -528,15 +408,10 @@ if (total === null) {
 total.amount = total.amount + BigInt.fromI32(1)
 ```
 
-
-
-
 ### Инициализация свойств класса
 
 Если Вы экспортируете какие-либо классы со свойствами, которые являются другими классами (декларированными Вами или стандартной библиотекой), то это выглядит следующим образом:
 
-
-
 ```typescript
 class Thing {}
 
@@ -545,11 +420,8 @@ export class Something {
 }
 ```
 
-
 Компилятор выдаст ошибку, потому что Вам нужно либо добавить инициализатор для свойств, являющихся классами, либо добавить оператор `!`:
 
-
-
 ```typescript
 export class Something {
   constructor(public value: Thing) {}
@@ -572,63 +444,44 @@ export class Something {
 }
 ```
 
-
-
-
 ### Инициализация массива
 
 Класс `Array` по-прежнему принимает число для инициализации длины списка, однако Вам следует соблюдать осторожность, поскольку такие операции, как `.push`, фактически увеличивают размер, а не добавляют его в начало, например:
 
-
-
 ```typescript
 let arr = new Array<string>(5) // ["", "", "", "", ""]
 
 arr.push('something') // ["", "", "", "", "", "something"] // size 6 :(
 ```
 
-
 В зависимости от используемых типов, например, допускающих значение NULL, и способа доступа к ним, можно столкнуться с ошибкой времени выполнения, подобной этой:
 
-
-
 ```
 ERRO Handler skipped due to execution failure, error: Mapping aborted at ~lib/array.ts, line 110, column 40, with message: Element type must be nullable if array is holey  wasm backtrace:     0: 0x19c4 - <unknown>!~lib/@graphprotocol/graph-ts/index/format         1: 0x1e75 - <unknown>!~lib/@graphprotocol/graph-ts/common/collections/Entity#constructor        2: 0x30b9 - <unknown>!node_modules/@graphprotocol/graph-ts/global/global/id_of_type
 ```
 
-
 Для того чтобы фактически начать, Вы должны либо инициализировать `Array` нулевым размером, следующим образом:
 
-
-
 ```typescript
 let arr = new Array<string>(0) // []
 
 arr.push('something') // ["something"]
 ```
 
-
 Или Вы должны изменить его через индекс:
 
-
-
 ```typescript
 let arr = new Array<string>(5) // ["", "", "", "", ""]
 
 arr[0] = 'something' // ["something", "", "", "", ""]
 ```
 
-
-
-
 ### Схема GraphQL
 
 Это не прямое изменение AssemblyScript, но Вам, возможно, придется обновить файл `schema.graphql`.
 
 Теперь Вы больше не можете определять поля в своих типах, которые являются списками, не допускающими значение NULL. Если у Вас такая схема:
 
-
-
 ```graphql
 type Something @entity {
   id: Bytes!
@@ -640,11 +493,8 @@ type MyEntity @entity {
 }
 ```
 
-
 Вам нужно добавить `!` к элементу типа List, например, так:
 
-
-
 ```graphql
 type Something @entity {
   id: Bytes!
@@ -656,11 +506,8 @@ type MyEntity @entity {
 }
 ```
 
-
 Изменение произошло из-за различий в допустимости значений NULL между версиями AssemblyScript и связано с файлом `src/generated/schema.ts` (путь по умолчанию, возможно, Вы его изменили).
 
-
-
 ### Прочее
 
 - `Map#set` и `Set#add` согласованы со спецификацией, произведён возврат к `this` ([v0.9.2](https://github.com/AssemblyScript/assemblyscript/releases/tag/v0.9.2))

From 474aee99ed8a84f56572029b2a8c78871c142da0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:36:01 -0500
Subject: [PATCH 1320/1325] New translations billing.mdx (German)

---
 website/pages/de/billing.mdx | 46 ++++++++++++++++++------------------
 1 file changed, 23 insertions(+), 23 deletions(-)

diff --git a/website/pages/de/billing.mdx b/website/pages/de/billing.mdx
index 5b390c4adf5e..83193509b958 100644
--- a/website/pages/de/billing.mdx
+++ b/website/pages/de/billing.mdx
@@ -6,16 +6,16 @@ title: Billing
 
 Es gibt zwei Pläne für die Abfrage von Subgraphen in The Graph Network.
 
-- <strong x-id=„1“>Free Plan</strong>: Der Free Plan beinhaltet 100.000 kostenlose monatliche Abfragen mit vollem Zugriff auf die Subgraph Studio Testumgebung. Dieser Plan ist für Hobbyisten, Hackathon-Teilnehmer und diejenigen mit Nebenprojekten gedacht, die The Graph ausprobieren möchten, bevor sie ihre Dapp skalieren.
+- **Free Plan**: Der Free Plan beinhaltet 100.000 kostenlose monatliche Abfragen mit vollem Zugriff auf die Subgraph Studio Testumgebung. Dieser Plan ist für Hobbyisten, Hackathon-Teilnehmer und diejenigen mit Nebenprojekten gedacht, die The Graph ausprobieren möchten, bevor sie ihre Dapp skalieren.
 
-- <strong x-id=„1“>Growth Plan</strong>: Der Growth Plan beinhaltet alles, was im Free Plan enthalten ist, wobei alle Abfragen nach 100.000 monatlichen Abfragen eine Zahlung mit GRT oder Kreditkarte erfordern. Der Growth Plan ist flexibel genug, um Teams abzudecken, die Dapps für eine Vielzahl von Anwendungsfällen entwickelt haben.
+- **Growth Plan**: Der Growth Plan beinhaltet alles, was im Free Plan enthalten ist, wobei alle Abfragen nach 100.000 monatlichen Abfragen eine Zahlung mit GRT oder Kreditkarte erfordern. Der Growth Plan ist flexibel genug, um Teams abzudecken, die Dapps für eine Vielzahl von Anwendungsfällen entwickelt haben.
 
 <VideoEmbed youtube="Nn771WagX2I" />
 
 ## Abfrage Zahlungen mit Kreditkarte
 
 - Um die Abrechnung mit Kredit-/Debitkarten einzurichten, müssen die Benutzer Subgraph Studio (https://thegraph.com/studio/) aufrufen
-  1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
+  1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf.
   2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
   3. Wählen Sie „ Upgrade Plan“, wenn Sie vom Free Plan upgraden oder wählen Sie „Manage Plan“, wenn Sie GRT bereits in der Vergangenheit zu Ihrem Abrechnungssaldo hinzugefügt haben. Als Nächstes können Sie die Anzahl der Abfragen schätzen, um einen Kostenvoranschlag zu erhalten, dieser Schritt ist jedoch nicht erforderlich.
   4. Um eine Zahlung per Kreditkarte zu wählen, wählen Sie „Kreditkarte“ als Zahlungsmethode und geben Sie Ihre Kreditkartendaten ein. Diejenigen, die Stripe bereits verwendet haben, können die Funktion „Link“ verwenden, um ihre Daten automatisch auszufüllen.
@@ -50,11 +50,11 @@ Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen
 
 ### Hinzufügen von GRT mit einer Wallet
 
-1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
+1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf.
 2. Click on the "Connect Wallet" button on the top right corner of the page. You'll be redirected to the wallet selection page. Select your wallet and click on "Connect".
 3. Wählen Sie die Schaltfläche „ Manage “ in der oberen rechten Ecke. Erstmalige Nutzer sehen die Option „Upgrade auf den Wachstumsplan“, während wiederkehrende Nutzer auf „Von der Wallet einzahlen“ klicken.
 4. Verwenden Sie den Slider, um die Anzahl der Abfragen zu schätzen, die Sie monatlich erwarten.
-   - Vorschläge für die Anzahl der Abfragen, die Sie verwenden können, finden Sie auf unserer Seite <strong x-id=„1“>Häufig gestellte Fragen</strong>.
+   - Vorschläge für die Anzahl der Abfragen, die Sie verwenden können, finden Sie auf unserer Seite **Häufig gestellte Fragen**.
 5. Wählen Sie „Kryptowährung“. GRT ist derzeit die einzige Kryptowährung, die im The Graph Network akzeptiert wird.
 6. Wählen Sie die Anzahl der Monate, die Sie im Voraus bezahlen möchten.
    - Die Zahlung im Voraus verpflichtet Sie nicht zu einer zukünftigen Nutzung. Ihnen wird nur das berechnet, was Sie verbrauchen, und Sie können Ihr Guthaben jederzeit abheben.
@@ -67,7 +67,7 @@ Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen
 
 ### GRT über eine Wallet abheben
 
-1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
+1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf.
 2. Klicken Sie auf die Schaltfläche „Connect Wallet“ in der oberen rechten Ecke der Seite. Wählen Sie Ihre Wallet aus und klicken Sie auf „Verbinden“.
 3. Klicken Sie auf die Schaltfläche „Verwalten“ in der oberen rechten Ecke der Seite. Wählen Sie „GRT abheben“. Ein Seitenfenster wird angezeigt.
 4. Geben Sie den Betrag der GRT ein, den Sie abheben möchten.
@@ -76,11 +76,11 @@ Sobald Sie GRT überbrücken, können Sie es zu Ihrem Rechnungssaldo hinzufügen
 
 ### Adding GRT using a multisig wallet
 
-1. Rufen Sie die <a href=„https://thegraph.com/studio/billing/“>Subgraph Studio Abrechnungsseite</a> auf.
+1. Rufen Sie die [Subgraph Studio Abrechnungsseite](https://thegraph.com/studio/billing/) auf.
 2. Klicke auf die Schaltfläche „Wallet verbinden“ in der oberen rechten Ecke der Seite. Wähle deine Wallet aus und klicke auf „Verbinden“. Wenn du die [Gnosis-Safe](https://gnosis-safe.io/) verwendest, kannst du sowohl deine Multisig-Wallet als auch deine Signatur-Wallet verbinden. Anschließend unterschreibe die zugehörige Nachricht. Dies verursacht keine Gasgebühren.
 3. Wählen Sie die Schaltfläche „ Manage “ in der oberen rechten Ecke. Erstmalige Nutzer sehen die Option „Upgrade auf den Wachstumsplan“, während wiederkehrende Nutzer auf „Von der Wallet einzahlen“ klicken.
 4. Verwenden Sie den Slider, um die Anzahl der Abfragen zu schätzen, die Sie monatlich erwarten.
-   - Vorschläge für die Anzahl der Abfragen, die Sie verwenden können, finden Sie auf unserer Seite <strong x-id=„1“>Häufig gestellte Fragen</strong>.
+   - Vorschläge für die Anzahl der Abfragen, die Sie verwenden können, finden Sie auf unserer Seite **Häufig gestellte Fragen**.
 5. Wählen Sie „Kryptowährung“. GRT ist derzeit die einzige Kryptowährung, die im The Graph Network akzeptiert wird.
 6. Wählen Sie die Anzahl der Monate, die Sie im Voraus bezahlen möchten.
    - Die Zahlung im Voraus verpflichtet Sie nicht zu einer zukünftigen Nutzung. Ihnen wird nur das berechnet, was Sie verbrauchen, und Sie können Ihr Guthaben jederzeit abheben.
@@ -98,7 +98,7 @@ In diesem Abschnitt erfahren Sie, wie Sie GRT dazu bringen können, die Abfrageg
 
 Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Coinbase.
 
-1. Gehen Sie zu <a href=„https://www.coinbase.com/“>Coinbase</a> und erstellen Sie ein Konto.
+1. Gehen Sie zu [Coinbase](https://www.coinbase.com/) und erstellen Sie ein Konto.
 2. Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
 3. Sobald Sie Ihre Identität überprüft haben, können Sie GRT kaufen. Dazu klicken Sie auf die Schaltfläche „Kaufen/Verkaufen“ oben rechts auf der Seite.
 4. Wählen Sie die Währung, die Sie kaufen möchten. Wählen Sie GRT.
@@ -106,19 +106,19 @@ Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Coinbase.
 6. Wählen Sie die Menge an GRT, die Sie kaufen möchten.
 7. Überprüfen Sie Ihren Einkauf. Überprüfen Sie Ihren Einkauf und klicken Sie auf „GRT kaufen“.
 8. Bestätigen Sie Ihren Kauf. Bestätigen Sie Ihren Kauf und Sie haben GRT erfolgreich gekauft.
-9. Sie können die GRT von Ihrem Konto auf Ihre Wallet wie <a href=„https://metamask.io/“>MetaMask</a> übertragen.
+9. Sie können die GRT von Ihrem Konto auf Ihre Wallet wie [MetaMask](https://metamask.io/) übertragen.
    - Um GRT auf Ihre Wallet zu übertragen, klicken Sie auf die Schaltfläche „Konten“ oben rechts auf der Seite.
    - Klicken Sie auf die Schaltfläche „Senden“ neben dem GRT Konto.
    - Geben Sie den Betrag an GRT ein, den Sie senden möchten, und die Wallet-Adresse, an die Sie ihn senden möchten.
    - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion. -Bitte beachten Sie, dass Coinbase Sie bei größeren Kaufbeträgen möglicherweise 7-10 Tage warten lässt, bevor Sie den vollen Betrag in eine Krypto-Wallet überweisen.
 
-Sie können mehr über den Erwerb von GRT auf Coinbase <a href=„https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency“>hier</a> erfahren.
+Sie können mehr über den Erwerb von GRT auf Coinbase [hier](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency) erfahren.
 
 ### Binance
 
 Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Binance.
 
-1. Gehen Sie auf <a href=„https://www.binance.com/en“>Binance</a> und erstellen Sie ein Konto.
+1. Gehen Sie auf [Binance](https://www.binance.com/en) und erstellen Sie ein Konto.
 2. Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
 3. Sobald Sie Ihre Identität überprüft haben, können Sie GRT kaufen. Dazu klicken Sie auf die Schaltfläche „Jetzt kaufen“ auf dem Banner der Homepage.
 4. Sie werden zu einer Seite weitergeleitet, auf der Sie die Währung auswählen können, die Sie kaufen möchten. Wählen Sie GRT.
@@ -126,19 +126,19 @@ Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Binance.
 6. Wählen Sie die Menge an GRT, die Sie kaufen möchten.
 7. Überprüfen Sie Ihren Kauf und klicken Sie auf „GRT kaufen“.
 8. Bestätigen Sie Ihren Kauf und Sie werden Ihr GRT in Ihrer Binance Spot Wallet sehen können.
-9. Sie können GRT von Ihrem Konto auf Ihre Wallet wie <a href=„https://metamask.io/“>MetaMask</a> abheben.
-   - <a href=„https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570“>Um GRT auf Ihr Wallet abzuheben</a>, fügen Sie die Adresse Ihres Wallets zur Whitelist für Abhebungen hinzu.
+9. Sie können GRT von Ihrem Konto auf Ihre Wallet wie [MetaMask](https://metamask.io/) abheben.
+   - [Um GRT auf Ihr Wallet abzuheben](https://www.binance.com/en/blog/ecosystem/how-to-transfer-crypto-from-binance-to-trust-wallet-8305050796630181570), fügen Sie die Adresse Ihres Wallets zur Whitelist für Abhebungen hinzu.
    - Klicken Sie auf die Schaltfläche „Wallet“, klicken Sie auf Abheben und wählen Sie GRT.
    - Geben Sie den GRT-Betrag ein, den Sie senden möchten, und die Wallet-Adresse, die auf der Whitelist steht.
    - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion.
 
-Sie können mehr über den Erwerb von GRT auf Binance <a href=„https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582“>hier</a> erfahren.
+Sie können mehr über den Erwerb von GRT auf Binance [hier](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582) erfahren.
 
 ### Uniswap
 
 So können Sie GRT auf Uniswap kaufen.
 
-1. Gehen Sie auf <a href=„https://app.uniswap.org/swap?chain=arbitrum“>Uniswap</a> und verbinden Sie Ihre Wallet.
+1. Gehen Sie auf [Uniswap](https://app.uniswap.org/swap?chain=arbitrum) und verbinden Sie Ihre Wallet.
 2. Wählen Sie den Token, von dem Sie tauschen möchten. Wählen Sie ETH.
 3. Wählen Sie den Token, in den Sie tauschen möchten. Wählen Sie GRT.
    - Stelle sicher, dass du den richtigen Token tauschst. Die Smart-Contract-Adresse von GRT auf Arbitrum One ist: [0x9623063377AD1B27544C965cCd7342f7EA7e88C7](https://arbiscan.io/token/0x9623063377ad1b27544c965ccd7342f7ea7e88c7)
@@ -146,7 +146,7 @@ So können Sie GRT auf Uniswap kaufen.
 5. Klicken Sie auf „Swap“.
 6. Bestätigen Sie die Transaktion in Ihrer Wallet und warten Sie auf die Abwicklung der Transaktion.
 
-Sie können mehr über den Erwerb von GRT auf Uniswap <a href=„https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-“>hier</a> erfahren.
+Sie können mehr über den Erwerb von GRT auf Uniswap [hier](https://support.uniswap.org/hc/en-us/articles/8370549680909-How-to-Swap-Tokens-) erfahren.
 
 ## Ether erhalten
 
@@ -156,7 +156,7 @@ In diesem Abschnitt erfahren Sie, wie Sie Ether (ETH) erhalten können, um Trans
 
 Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Coinbase.
 
-1.  Gehen Sie zu <a href=„https://www.coinbase.com/“>Coinbase</a> und erstellen Sie ein Konto.
+1.  Gehen Sie zu [Coinbase](https://www.coinbase.com/) und erstellen Sie ein Konto.
 2.  Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
 3.  Sobald Sie Ihre Identität bestätigt haben, können Sie ETH kaufen, indem Sie auf die Schaltfläche „Kaufen/Verkaufen“ oben rechts auf der Seite klicken.
 4.  Wählen Sie die Währung, die Sie kaufen möchten. Wählen Sie ETH.
@@ -164,20 +164,20 @@ Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von GRT auf Coinbase.
 6.  Geben Sie die Menge an ETH ein, die Sie kaufen möchten.
 7.  Überprüfen Sie Ihren Kauf und klicken Sie auf „ETH kaufen“.
 8.  Bestätigen Sie Ihren Kauf und Sie haben erfolgreich ETH gekauft.
-9.  Sie können die ETH von Ihrem Coinbase-Konto auf Ihr Wallet wie <a href=„https://metamask.io/“>MetaMask</a> übertragen.
+9.  Sie können die ETH von Ihrem Coinbase-Konto auf Ihr Wallet wie [MetaMask](https://metamask.io/) übertragen.
     - Um die ETH auf Ihre Wallet zu übertragen, klicken Sie auf die Schaltfläche „Konten“ oben rechts auf der Seite.
     - Klicken Sie auf die Schaltfläche „Senden“ neben dem ETH-Konto.
     - Geben Sie den ETH-Betrag ein, den Sie senden möchten, und die Wallet-Adresse, an die Sie ihn senden möchten.
     - Stellen Sie sicher, dass Sie an Ihre Ethereum Wallet Adresse auf Arbitrum One senden.
     - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion.
 
-Sie können mehr über den Erwerb von ETH auf Coinbase <a href=„https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency“>hier</a> erfahren.
+Sie können mehr über den Erwerb von ETH auf Coinbase [hier](https://help.coinbase.com/en/coinbase/trading-and-funding/buying-selling-or-converting-crypto/how-do-i-buy-digital-currency) erfahren.
 
 ### Binance
 
 Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von ETH auf Binance.
 
-1.  Gehen Sie auf <a href=„https://www.binance.com/en“>Binance</a> und erstellen Sie ein Konto.
+1.  Gehen Sie auf [Binance](https://www.binance.com/en) und erstellen Sie ein Konto.
 2.  Sobald Sie ein Konto erstellt haben, müssen Sie Ihre Identität durch ein Verfahren verifizieren, das als KYC (oder Know Your Customer) bekannt ist. Dies ist ein Standardverfahren für alle zentralisierten oder verwahrten Krypto-Börsen.
 3.  Sobald Sie Ihre Identität verifiziert haben, kaufen Sie ETH, indem Sie auf die Schaltfläche „Jetzt kaufen“ auf dem Banner der Homepage klicken.
 4.  Wählen Sie die Währung, die Sie kaufen möchten. Wählen Sie ETH.
@@ -185,14 +185,14 @@ Dies ist eine Schritt-für-Schritt-Anleitung für den Kauf von ETH auf Binance.
 6.  Geben Sie die Menge an ETH ein, die Sie kaufen möchten.
 7.  Überprüfen Sie Ihren Kauf und klicken Sie auf „ETH kaufen“.
 8.  Bestätigen Sie Ihren Kauf und Sie werden Ihre ETH in Ihrer Binance Spot Wallet sehen.
-9.  Sie können die ETH von Ihrem Konto auf Ihr Wallet wie <a href=„https://metamask.io/“>MetaMask</a> abheben.
+9.  Sie können die ETH von Ihrem Konto auf Ihr Wallet wie [MetaMask](https://metamask.io/) abheben.
     - Um die ETH auf Ihre Wallet abzuheben, fügen Sie die Adresse Ihrer Wallet zur Abhebungs-Whitelist hinzu.
     - Klicken Sie auf die Schaltfläche „Wallet“, klicken Sie auf „withdraw“ und wählen Sie ETH.
     - Geben Sie den ETH-Betrag ein, den Sie senden möchten, und die Adresse der Wallet, die auf der Whitelist steht, an die Sie den Betrag senden möchten.
     - Stellen Sie sicher, dass Sie an Ihre Ethereum Wallet Adresse auf Arbitrum One senden.
     - Klicken Sie auf „Weiter“ und bestätigen Sie Ihre Transaktion.
 
-Sie können mehr über den Erwerb von ETH auf Binance <a href=„https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582“>hier</a> erfahren.
+Sie können mehr über den Erwerb von ETH auf Binance [hier](https://www.binance.com/en/support/faq/how-to-buy-cryptocurrency-on-binance-homepage-400c38f5e0cd4b46a1d0805c296b5582) erfahren.
 
 ## FAQs zur Rechnungsstellung
 

From b78adac5f4a87b5c2d8dc82b9a4279d1261dd44d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:37:10 -0500
Subject: [PATCH 1321/1325] New translations
 graphql-validations-migration-guide.mdx (Chinese Simplified)

---
 .../zh/release-notes/graphql-validations-migration-guide.mdx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx b/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx
index 6316302a7142..8c4d5c52d93a 100644
--- a/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/zh/release-notes/graphql-validations-migration-guide.mdx
@@ -62,7 +62,7 @@ npx@graphql验证/cli-shttps://api-npx @graphql-validate/cli -s https://api-next
 
 或者
 
-- `https://api-next.thegraph.com/subgraphs/name`<GITHUB_USER>/<SUBGRAPH_NAME>
+- `https://api-next.thegraph.com/subgraphs/name/<GITHUB_USER>/<SUBGRAPH_NAME>`
 
 要处理标记为存在验证错误的查询，可以使用您最喜欢的GraphQL查询工具，如Altair或[GraphiQL](https://cloud.hasura.io/public/graphiql)，然后尝试您的查询。这些工具还会在用户界面中标记这些错误，甚至在您运行之前。
 

From 57779c3bcf92db056b50354e8190a5ae2a3abd8b Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 16:38:53 -0500
Subject: [PATCH 1322/1325] New translations
 how-to-secure-api-keys-using-nextjs-server-components.mdx (Hindi)

---
 .../how-to-secure-api-keys-using-nextjs-server-components.mdx   | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index f8b39d9b664f..e4f078918c5c 100644
--- a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -33,7 +33,7 @@ title: कैसे सुरक्षित करें API Keys का उप
 ### चरण 1: पर्यावरण चर सेट करें
 
 1. हमारे Next.js प्रोजेक्ट की जड़ में, एक.env.local फ़ाइल बनाएं।
-2. हमारा API कुंजी जोड़ें: API_KEY=<api_key_here>.
+2. हमारा API कुंजी जोड़ें: `API_KEY=<api_key_here>`.
 
 ### चरण 2: एक सर्वर घटक बनाएं
 

From f7843d0640313fb429b3d9c62b7f554fdc64d364 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 17:06:31 -0500
Subject: [PATCH 1323/1325] New translations multiple-networks.mdx (Hindi)

---
 website/pages/hi/deploying/multiple-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/hi/deploying/multiple-networks.mdx b/website/pages/hi/deploying/multiple-networks.mdx
index 4f0308b2e45b..44447e580313 100644
--- a/website/pages/hi/deploying/multiple-networks.mdx
+++ b/website/pages/hi/deploying/multiple-networks.mdx
@@ -146,7 +146,7 @@ To illustrate this approach, let's assume a subgraph should be deployed to mainn
 }
 ```
 
-साथ ही, आप नेटवर्क नाम और पते को मैनिफेस्ट में वेरिएबल प्लेसहोल्डर्स {{network}} और {{address}} से बदल देंगे और मैनिफेस्ट का नाम बदलकर उदाहरण के लिए subgraph.template.yaml रख देंगे:
+साथ ही, आप नेटवर्क नाम और पते को मैनिफेस्ट में वेरिएबल प्लेसहोल्डर्स `{{network}}` और `{{address}}` से बदल देंगे और मैनिफेस्ट का नाम बदलकर उदाहरण के लिए subgraph.template.yaml रख देंगे:
 
 ```yaml
 # ...

From 1bce0f1e91cb34c3c3d394abc5e0e6f582f2ee98 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Beno=C3=AEt=20Rouleau?= <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 17:08:09 -0500
Subject: [PATCH 1324/1325] New translations supported-networks.mdx (French)

---
 website/pages/fr/developing/supported-networks.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/pages/fr/developing/supported-networks.mdx b/website/pages/fr/developing/supported-networks.mdx
index 95f3b3c65b06..dc5f6841f6e3 100644
--- a/website/pages/fr/developing/supported-networks.mdx
+++ b/website/pages/fr/developing/supported-networks.mdx
@@ -5,7 +5,7 @@ title: Réseaux supportés
 import { getStaticPropsForSupportedNetworks } from '@/src/buildGetStaticProps'
 import { SupportedNetworksTable } from '@/src/supportedNetworks'
 
-export const getStaticProps = getStaticPropsForSupportedNetworks(__nomDuFichier)
+export const getStaticProps = getStaticPropsForSupportedNetworks(__filename)
 
 <SupportedNetworksTable networks={props.networks} />
 

From 87cd681b0f280eb96015fdd00508dc0b06e5b27f Mon Sep 17 00:00:00 2001
From: benface <benoit.rouleau@icloud.com>
Date: Fri, 13 Dec 2024 17:14:45 -0500
Subject: [PATCH 1325/1325] Run `pnpm check:fix`

---
 website/pages/ar/cookbook/near.mdx            |   6 +-
 .../ar/cookbook/subgraph-debug-forking.mdx    |   6 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  28 +--
 website/pages/ar/developing/graph-ts/api.mdx  |  20 +-
 .../ar/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/ar/network/benefits.mdx         |  70 +++---
 website/pages/ar/network/delegating.mdx       |   4 +-
 website/pages/ar/network/indexing.mdx         |  32 +--
 website/pages/ar/new-chain-integration.mdx    |   2 +-
 website/pages/ar/operating-graph-node.mdx     |  14 +-
 website/pages/ar/querying/graphql-api.mdx     |  14 +-
 .../ar/querying/querying-best-practices.mdx   |  12 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/ar/sps/triggers-example.mdx     |   2 +-
 .../ar/supported-network-requirements.mdx     |  28 +--
 .../cs/cookbook/subgraph-debug-forking.mdx    |   2 +-
 .../creating-a-subgraph/advanced.mdx          |   2 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  20 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/cs/developing/graph-ts/api.mdx  |  20 +-
 .../cs/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/cs/network/benefits.mdx         |  70 +++---
 website/pages/cs/network/delegating.mdx       |   4 +-
 website/pages/cs/network/indexing.mdx         |  32 +--
 website/pages/cs/new-chain-integration.mdx    |   2 +-
 website/pages/cs/operating-graph-node.mdx     |  14 +-
 website/pages/cs/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/cs/sps/triggers-example.mdx     |   2 +-
 .../cs/supported-network-requirements.mdx     |  28 +--
 .../de/arbitrum/l2-transfer-tools-faq.mdx     |   2 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/de/developing/graph-ts/api.mdx  |  20 +-
 .../de/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/de/network/benefits.mdx         |  70 +++---
 website/pages/de/network/indexing.mdx         |  32 +--
 website/pages/de/new-chain-integration.mdx    |   2 +-
 website/pages/de/operating-graph-node.mdx     |  14 +-
 website/pages/de/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/de/sps/triggers-example.mdx     |   2 +-
 .../de/supported-network-requirements.mdx     |  28 +--
 website/pages/es/cookbook/cosmos.mdx          |   2 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  28 +--
 website/pages/es/developing/graph-ts/api.mdx  |  20 +-
 .../es/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/es/network/benefits.mdx         |  70 +++---
 website/pages/es/network/indexing.mdx         |  32 +--
 website/pages/es/new-chain-integration.mdx    |   2 +-
 website/pages/es/operating-graph-node.mdx     |  14 +-
 website/pages/es/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 .../graphql-validations-migration-guide.mdx   |   1 -
 website/pages/es/sps/triggers-example.mdx     |   2 +-
 .../es/supported-network-requirements.mdx     |  28 +--
 .../fr/arbitrum/l2-transfer-tools-faq.mdx     |   6 +-
 website/pages/fr/cookbook/cosmos.mdx          |  44 ++--
 website/pages/fr/cookbook/near.mdx            |  50 ++--
 .../creating-a-subgraph/advanced.mdx          |   2 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  30 +--
 website/pages/fr/developing/graph-ts/api.mdx  |  96 ++++----
 .../fr/developing/unit-testing-framework.mdx  |  21 +-
 website/pages/fr/network/benefits.mdx         |  73 +++---
 website/pages/fr/network/delegating.mdx       |   6 +-
 website/pages/fr/network/indexing.mdx         |  32 +--
 website/pages/fr/new-chain-integration.mdx    |   2 +-
 website/pages/fr/operating-graph-node.mdx     |  14 +-
 .../fr/publishing/publishing-a-subgraph.mdx   |   6 +-
 .../pages/fr/querying/distributed-systems.mdx |  18 +-
 website/pages/fr/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |  15 +-
 .../graphql-validations-migration-guide.mdx   |   6 +-
 website/pages/fr/sps/triggers-example.mdx     |   2 +-
 .../fr/supported-network-requirements.mdx     |  28 +--
 website/pages/hi/about.mdx                    |   2 +-
 website/pages/hi/arbitrum/arbitrum-faq.mdx    |   5 +-
 website/pages/hi/billing.mdx                  |   4 +-
 ...pi-keys-using-nextjs-server-components.mdx |   2 +-
 .../immutable-entities-bytes-as-ids.mdx       |   4 +-
 .../hi/cookbook/subgraph-debug-forking.mdx    |   2 +-
 .../deploy-using-subgraph-studio.mdx          |   4 +-
 .../creating-a-subgraph/advanced.mdx          |   1 -
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  56 ++---
 .../creating-a-subgraph/subgraph-manifest.mdx |   2 +-
 .../pages/hi/developing/developer-faqs.mdx    |   2 +-
 website/pages/hi/developing/graph-ts/api.mdx  |  26 +-
 .../hi/developing/unit-testing-framework.mdx  |  14 +-
 .../pages/hi/managing/transfer-a-subgraph.mdx |   2 +-
 website/pages/hi/network/benefits.mdx         |  70 +++---
 website/pages/hi/network/curating.mdx         |   2 +-
 website/pages/hi/network/delegating.mdx       |   8 +-
 website/pages/hi/network/developing.mdx       |   2 +-
 website/pages/hi/network/indexing.mdx         |  38 +--
 website/pages/hi/operating-graph-node.mdx     |  14 +-
 .../hi/publishing/publishing-a-subgraph.mdx   |   2 +-
 website/pages/hi/querying/graphql-api.mdx     |  18 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/hi/sps/triggers-example.mdx     |   4 +-
 .../hi/supported-network-requirements.mdx     |  28 +--
 website/pages/hi/tap.mdx                      |  16 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/it/developing/graph-ts/api.mdx  |  96 ++++----
 .../it/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/it/network/benefits.mdx         |  70 +++---
 website/pages/it/network/delegating.mdx       |   8 +-
 website/pages/it/network/indexing.mdx         |  34 +--
 website/pages/it/new-chain-integration.mdx    |   2 +-
 website/pages/it/operating-graph-node.mdx     |  14 +-
 website/pages/it/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   7 +-
 website/pages/it/sps/triggers-example.mdx     |   2 +-
 .../it/supported-network-requirements.mdx     |  28 +--
 .../ja/cookbook/subgraph-debug-forking.mdx    |   6 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  20 +-
 .../creating-a-subgraph/ql-schema.mdx         |  62 ++---
 website/pages/ja/developing/graph-ts/api.mdx  |  96 ++++----
 .../ja/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/ja/network/benefits.mdx         |  70 +++---
 website/pages/ja/network/indexing.mdx         |  38 +--
 website/pages/ja/new-chain-integration.mdx    |   2 +-
 website/pages/ja/operating-graph-node.mdx     |  16 +-
 website/pages/ja/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 .../graphql-validations-migration-guide.mdx   |   2 +-
 website/pages/ja/sps/triggers-example.mdx     |   2 +-
 .../ja/supported-network-requirements.mdx     |  28 +--
 .../ko/arbitrum/l2-transfer-tools-faq.mdx     |   5 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/ko/developing/graph-ts/api.mdx  |  20 +-
 .../ko/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/ko/network/benefits.mdx         |  70 +++---
 website/pages/ko/network/indexing.mdx         |  34 +--
 website/pages/ko/new-chain-integration.mdx    |   2 +-
 website/pages/ko/operating-graph-node.mdx     |  14 +-
 website/pages/ko/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/ko/sps/triggers-example.mdx     |   2 +-
 .../ko/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  64 ++---
 website/pages/mr/developing/graph-ts/api.mdx  |  20 +-
 .../mr/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/mr/network/benefits.mdx         |  70 +++---
 website/pages/mr/network/delegating.mdx       |   6 +-
 website/pages/mr/network/indexing.mdx         |  36 +--
 website/pages/mr/new-chain-integration.mdx    |   2 +-
 website/pages/mr/operating-graph-node.mdx     |  14 +-
 website/pages/mr/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/mr/sps/triggers-example.mdx     |   2 +-
 .../mr/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/nl/developing/graph-ts/api.mdx  |  20 +-
 .../nl/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/nl/network/benefits.mdx         |  72 +++---
 website/pages/nl/network/delegating.mdx       |   6 +-
 website/pages/nl/network/indexing.mdx         |  34 +--
 website/pages/nl/new-chain-integration.mdx    |   2 +-
 website/pages/nl/operating-graph-node.mdx     |  14 +-
 website/pages/nl/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/nl/sps/triggers-example.mdx     |   2 +-
 .../nl/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/pl/developing/graph-ts/api.mdx  |  20 +-
 .../pl/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/pl/network/benefits.mdx         |  70 +++---
 website/pages/pl/network/indexing.mdx         |  34 +--
 website/pages/pl/new-chain-integration.mdx    |   2 +-
 website/pages/pl/operating-graph-node.mdx     |  14 +-
 website/pages/pl/querying/graphql-api.mdx     |  14 +-
 website/pages/pl/quick-start.mdx              |   2 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/pl/sps/triggers-example.mdx     |   2 +-
 .../pl/supported-network-requirements.mdx     |  28 +--
 website/pages/pt/cookbook/arweave.mdx         |   8 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/pt/developing/graph-ts/api.mdx  |  99 ++++----
 .../pt/developing/unit-testing-framework.mdx  |  12 +-
 website/pages/pt/network/benefits.mdx         |  73 +++---
 website/pages/pt/network/delegating.mdx       |   6 +-
 website/pages/pt/network/indexing.mdx         |  34 +--
 website/pages/pt/operating-graph-node.mdx     |  14 +-
 website/pages/pt/querying/graphql-api.mdx     |  14 +-
 .../querying/querying-from-an-application.mdx |   2 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 .../graphql-validations-migration-guide.mdx   |  13 +-
 website/pages/pt/sps/triggers-example.mdx     |   2 +-
 .../pt/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/ro/developing/graph-ts/api.mdx  |  20 +-
 .../ro/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/ro/network/benefits.mdx         |  70 +++---
 website/pages/ro/network/indexing.mdx         |  34 +--
 website/pages/ro/new-chain-integration.mdx    |   2 +-
 website/pages/ro/operating-graph-node.mdx     |  14 +-
 website/pages/ro/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/ro/sps/triggers-example.mdx     |   2 +-
 .../ro/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/ru/developing/graph-ts/api.mdx  | 106 ++++----
 .../ru/developing/unit-testing-framework.mdx  |  56 ++---
 website/pages/ru/network/benefits.mdx         |  70 +++---
 website/pages/ru/network/delegating.mdx       |   4 +-
 website/pages/ru/network/indexing.mdx         |  38 +--
 website/pages/ru/new-chain-integration.mdx    |   2 +-
 website/pages/ru/operating-graph-node.mdx     |  14 +-
 website/pages/ru/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 .../graphql-validations-migration-guide.mdx   |  10 +-
 website/pages/ru/sps/triggers-example.mdx     |   2 +-
 .../ru/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/advanced.mdx          |  24 +-
 .../assemblyscript-mappings.mdx               |   4 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  63 +++--
 .../creating-a-subgraph/subgraph-manifest.mdx |  54 ++--
 .../pages/sv/developing/developer-faqs.mdx    |   2 +-
 website/pages/sv/developing/graph-ts/api.mdx  | 164 ++++++-------
 .../sv/developing/unit-testing-framework.mdx  |  12 +-
 website/pages/sv/network/benefits.mdx         |  70 +++---
 website/pages/sv/network/delegating.mdx       |   9 +-
 website/pages/sv/network/indexing.mdx         |  32 +--
 website/pages/sv/new-chain-integration.mdx    |   2 +-
 website/pages/sv/operating-graph-node.mdx     |  14 +-
 .../pages/sv/querying/distributed-systems.mdx |  24 +-
 website/pages/sv/querying/graphql-api.mdx     |  14 +-
 .../sv/querying/querying-best-practices.mdx   |  26 +-
 .../querying/querying-from-an-application.mdx |  30 +--
 .../assemblyscript-migration-guide.mdx        | 127 +++++-----
 website/pages/sv/sps/triggers-example.mdx     |   2 +-
 .../sv/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/sw/developing/graph-ts/api.mdx  |  20 +-
 .../sw/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/sw/network/benefits.mdx         |  70 +++---
 website/pages/sw/network/indexing.mdx         |  34 +--
 website/pages/sw/new-chain-integration.mdx    |   2 +-
 website/pages/sw/operating-graph-node.mdx     |  14 +-
 website/pages/sw/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/sw/sps/triggers-example.mdx     |   2 +-
 .../sw/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  20 +-
 .../creating-a-subgraph/ql-schema.mdx         |  56 ++---
 website/pages/tr/developing/graph-ts/api.mdx  | 100 ++++----
 .../tr/developing/unit-testing-framework.mdx  |  14 +-
 website/pages/tr/network/benefits.mdx         |  70 +++---
 website/pages/tr/network/indexing.mdx         |  34 +--
 website/pages/tr/new-chain-integration.mdx    |   2 +-
 website/pages/tr/operating-graph-node.mdx     |  14 +-
 website/pages/tr/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/tr/sps/triggers-example.mdx     |   2 +-
 .../tr/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/uk/developing/graph-ts/api.mdx  |  20 +-
 .../uk/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/uk/network/benefits.mdx         |  70 +++---
 website/pages/uk/network/delegating.mdx       |   6 +-
 website/pages/uk/network/indexing.mdx         |  38 +--
 website/pages/uk/new-chain-integration.mdx    |   2 +-
 website/pages/uk/operating-graph-node.mdx     |  14 +-
 website/pages/uk/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/uk/sps/triggers-example.mdx     |   2 +-
 .../uk/supported-network-requirements.mdx     |  28 +--
 .../pages/ur/chain-integration-overview.mdx   |   3 +-
 website/pages/ur/cookbook/cosmos.mdx          |   2 +-
 website/pages/ur/cookbook/near.mdx            |   4 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  20 +-
 .../creating-a-subgraph/ql-schema.mdx         |  28 +--
 website/pages/ur/developing/graph-ts/api.mdx  |  18 +-
 .../substreams-powered-subgraphs-faq.mdx      |   3 +-
 .../ur/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/ur/network/benefits.mdx         |  74 +++---
 website/pages/ur/network/delegating.mdx       |   7 +-
 website/pages/ur/network/indexing.mdx         |  34 +--
 website/pages/ur/new-chain-integration.mdx    |   2 +-
 website/pages/ur/operating-graph-node.mdx     |  14 +-
 website/pages/ur/querying/graphql-api.mdx     |  16 +-
 .../ur/querying/querying-best-practices.mdx   |   2 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 .../graphql-validations-migration-guide.mdx   |   3 +-
 website/pages/ur/sps/triggers-example.mdx     |   2 +-
 .../ur/supported-network-requirements.mdx     |  28 +--
 .../creating-a-subgraph/install-the-cli.mdx   |  22 +-
 .../creating-a-subgraph/ql-schema.mdx         |  20 +-
 website/pages/vi/developing/graph-ts/api.mdx  |  20 +-
 .../vi/developing/unit-testing-framework.mdx  |  10 +-
 website/pages/vi/network/benefits.mdx         |  70 +++---
 website/pages/vi/network/indexing.mdx         |  34 +--
 website/pages/vi/new-chain-integration.mdx    |   2 +-
 website/pages/vi/operating-graph-node.mdx     |  14 +-
 website/pages/vi/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/vi/sps/triggers-example.mdx     |   2 +-
 .../vi/supported-network-requirements.mdx     |  28 +--
 .../zh/cookbook/subgraph-debug-forking.mdx    |   2 +-
 .../creating-a-subgraph/advanced.mdx          |   2 +-
 .../creating-a-subgraph/install-the-cli.mdx   |  20 +-
 .../creating-a-subgraph/ql-schema.mdx         |  64 ++---
 website/pages/zh/developing/graph-ts/api.mdx  |  24 +-
 .../zh/developing/unit-testing-framework.mdx  |  16 +-
 website/pages/zh/network/benefits.mdx         |  72 +++---
 website/pages/zh/network/delegating.mdx       |   7 +-
 website/pages/zh/network/indexing.mdx         |  40 +--
 website/pages/zh/new-chain-integration.mdx    |   2 +-
 website/pages/zh/operating-graph-node.mdx     |  14 +-
 website/pages/zh/querying/graphql-api.mdx     |  14 +-
 .../assemblyscript-migration-guide.mdx        |   5 +
 website/pages/zh/sps/triggers-example.mdx     |   2 +-
 .../zh/supported-network-requirements.mdx     |  28 +--
 website/route-lockfile.txt                    | 231 +++++++++++++++++-
 329 files changed, 3757 insertions(+), 3442 deletions(-)

diff --git a/website/pages/ar/cookbook/near.mdx b/website/pages/ar/cookbook/near.mdx
index 73428b6f6fd5..b2f9eaf75feb 100644
--- a/website/pages/ar/cookbook/near.mdx
+++ b/website/pages/ar/cookbook/near.mdx
@@ -27,13 +27,13 @@ title: بناء Subgraphs على NEAR
 
 `graphprotocol/graph-ts@` هي مكتبة لأنواع خاصة بـ subgraph.
 
-تطوير NEAR subgraph يتطلب `graph-cli` بإصدار أعلى من ` 0.23.0 ` و `graph-ts` بإصدار أعلى من ` 0.23.0 `.
+تطوير NEAR subgraph يتطلب `graph-cli` بإصدار أعلى من `0.23.0` و `graph-ts` بإصدار أعلى من `0.23.0`.
 
 > Building a NEAR subgraph is very similar to building a subgraph that indexes Ethereum.
 
 هناك ثلاثة جوانب لتعريف الـ subgraph:
 
-**subgraph.yaml:** الـ subgraph manifest ، وتحديد مصادر البيانات ذات الأهمية ، وكيف يجب أن تتم معالجتها.علما أن NEAR هو ` نوع ` جديد لمصدر البيانات.
+**subgraph.yaml:** الـ subgraph manifest ، وتحديد مصادر البيانات ذات الأهمية ، وكيف يجب أن تتم معالجتها.علما أن NEAR هو `نوع` جديد لمصدر البيانات.
 
 **schema.graphql:** a schema file that defines what data is stored for your subgraph, and how to query it via GraphQL. The requirements for NEAR subgraphs are covered by [the existing documentation](/developing/creating-a-subgraph#the-graphql-schema).
 
@@ -163,7 +163,7 @@ class ReceiptWithOutcome {
 These types are passed to block & receipt handlers:
 
 - معالجات الكتلة ستتلقى`Block`
-- معالجات الاستلام ستتلقى` ReceiptWithOutcome `
+- معالجات الاستلام ستتلقى`ReceiptWithOutcome`
 
 Otherwise, the rest of the [AssemblyScript API](/developing/graph-ts/api) is available to NEAR subgraph developers during mapping execution.
 
diff --git a/website/pages/ar/cookbook/subgraph-debug-forking.mdx b/website/pages/ar/cookbook/subgraph-debug-forking.mdx
index 44a8bfa28c2c..6c87d43045c5 100644
--- a/website/pages/ar/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/ar/cookbook/subgraph-debug-forking.mdx
@@ -69,14 +69,14 @@ Oops, how unfortunate, when I deploy my perfect looking subgraph to [Subgraph St
 
 وأنا أجيب:
 
-1. ` fork-base ` هو عنوان URL "الأساسي" ،فمثلا عند إلحاق _subgraph id_ ، يكون عنوان URL الناتج (`<fork-base>/<subgraph-id>`) هو GraphQL endpoint صالح لمخزن الـ subgraph.
+1. `fork-base` هو عنوان URL "الأساسي" ،فمثلا عند إلحاق _subgraph id_ ، يكون عنوان URL الناتج (`<fork-base>/<subgraph-id>`) هو GraphQL endpoint صالح لمخزن الـ subgraph.
 2. الـتفريع سهل ، فلا داعي للقلق:
 
 ```bash
 $ graph deploy <subgraph-name> --debug-fork <subgraph-id> --ipfs http://localhost:5001 --node http://localhost:8020
 ```
 
-أيضًا ، لا تنس تعيين حقل ` dataSources.source.startBlock ` في subgraph manifest لرقم الكتلة(block) التي بها المشكلة، حتى تتمكن من تخطي فهرسة الكتل الغير ضرورية والاستفادة من التفريع!
+أيضًا ، لا تنس تعيين حقل `dataSources.source.startBlock` في subgraph manifest لرقم الكتلة(block) التي بها المشكلة، حتى تتمكن من تخطي فهرسة الكتل الغير ضرورية والاستفادة من التفريع!
 
 لذلك ، هذا ما أفعله:
 
@@ -90,7 +90,7 @@ $ cargo run -p graph-node --release -- \
     --fork-base https://api.thegraph.com/subgraphs/id/
 ```
 
-2. بعد فحص دقيق ، لاحظت أن هناك عدم تطابق في تمثيلات الـ ` id ` المستخدمة عند فهرسة ` Gravatar ` في المعالجين الخاصين بي. بينما ` handleNewGravatar ` يحول (`event.params.id.toHex()`) إلى سداسي ، `handleUpdatedGravatar` يستخدم int32 (`event.params.id.toI32()`) مما يجعل ` handleUpdatedGravatar ` قلقا من "Gravatar not found!". أنا أجعلهم كلاهما يحولان ` id ` إلى سداسي.
+2. بعد فحص دقيق ، لاحظت أن هناك عدم تطابق في تمثيلات الـ `id` المستخدمة عند فهرسة `Gravatar` في المعالجين الخاصين بي. بينما `handleNewGravatar` يحول (`event.params.id.toHex()`) إلى سداسي ، `handleUpdatedGravatar` يستخدم int32 (`event.params.id.toI32()`) مما يجعل `handleUpdatedGravatar` قلقا من "Gravatar not found!". أنا أجعلهم كلاهما يحولان `id` إلى سداسي.
 3. After I made the changes I deploy my subgraph to the local Graph Node, **_forking the failing subgraph_** and setting `dataSources.source.startBlock` to `6190343` in `subgraph.yaml`:
 
 ```bash
diff --git a/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx
index 4aa9caae2a28..b18e9aa8f7fb 100644
--- a/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/ar/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is
 
 ## SpecVersion Releases
 
-| الاصدار | ملاحظات الإصدار                                                                                                                                                          |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| الاصدار | ملاحظات الإصدار |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx
index b66db45260f0..20b4acef827a 100644
--- a/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/ar/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| النوع        | الوصف                                                                                                                                                                                                            |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | مصفوفة Byte ، ممثلة كسلسلة سداسية عشرية. يشيع استخدامها في Ethereum hashes وعناوينه.                                                                                                                             |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| النوع | الوصف |
+| --- | --- |
+| `Bytes` | مصفوفة Byte ، ممثلة كسلسلة سداسية عشرية. يشيع استخدامها في Ethereum hashes وعناوينه. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -306,7 +306,7 @@ Supported language dictionaries:
 
 Supported algorithms for ordering results:
 
-| Algorithm     | Description                                                             |
-| ------------- | ----------------------------------------------------------------------- |
-| rank          | استخدم جودة مطابقة استعلام النص-الكامل (0-1) لترتيب النتائج.            |
-| proximityRank | Similar to rank but also includes the proximity of the matches.         |
+| Algorithm     | Description                                                     |
+| ------------- | --------------------------------------------------------------- |
+| rank          | استخدم جودة مطابقة استعلام النص-الكامل (0-1) لترتيب النتائج.    |
+| proximityRank | Similar to rank but also includes the proximity of the matches. |
diff --git a/website/pages/ar/developing/graph-ts/api.mdx b/website/pages/ar/developing/graph-ts/api.mdx
index 544f2118f489..2de72189db87 100644
--- a/website/pages/ar/developing/graph-ts/api.mdx
+++ b/website/pages/ar/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| الاصدار | ملاحظات الإصدار                                                                                                                                                                                                                               |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| الاصدار | ملاحظات الإصدار |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### الأنواع المضمنة (Built-in)
 
diff --git a/website/pages/ar/developing/unit-testing-framework.mdx b/website/pages/ar/developing/unit-testing-framework.mdx
index 67c565e95df8..d123dc0f994b 100644
--- a/website/pages/ar/developing/unit-testing-framework.mdx
+++ b/website/pages/ar/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/ar/network/benefits.mdx b/website/pages/ar/network/benefits.mdx
index 510e4e20eb78..3bdd3f1e6e25 100644
--- a/website/pages/ar/network/benefits.mdx
+++ b/website/pages/ar/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                        The Graph Network                        |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|       البنية الأساسية        |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| البنية الأساسية | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                        The Graph Network                        |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|       البنية الأساسية        |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| البنية الأساسية | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                        The Graph Network                        |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|       البنية الأساسية        |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| البنية الأساسية | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/ar/network/delegating.mdx b/website/pages/ar/network/delegating.mdx
index dd0a8164d29e..185dc09a8cac 100644
--- a/website/pages/ar/network/delegating.mdx
+++ b/website/pages/ar/network/delegating.mdx
@@ -48,9 +48,7 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
-<div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  لاحظ 0.5٪ رسوم التفويض ، بالإضافة إلى فترة 28 يوما لإلغاء التفويض.
-</div>
+<div sx={{ mx: 'auto', maxWidth: '400px' }}>لاحظ 0.5٪ رسوم التفويض ، بالإضافة إلى فترة 28 يوما لإلغاء التفويض.</div>
 
 ### اختيار مفهرس جدير بالثقة مع عائد جيد للمفوضين
 
diff --git a/website/pages/ar/network/indexing.mdx b/website/pages/ar/network/indexing.mdx
index 849d5d13f7b5..e5cb4d8ea17d 100644
--- a/website/pages/ar/network/indexing.mdx
+++ b/website/pages/ar/network/indexing.mdx
@@ -113,11 +113,11 @@ The `queryFeeCut` and `indexingRewardCut` values are delegation parameters that
 - **كبيرة** - مُعدة لفهرسة جميع ال subgraphs المستخدمة حاليا وأيضا لخدمة طلبات حركة مرور البيانات ذات الصلة.
 
 | Setup | Postgres<br /> (CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory 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 |
 
 ### What are some basic security precautions an Indexer should take?
 
@@ -149,20 +149,20 @@ At the center of an Indexer's infrastructure is the Graph Node which monitors th
 
 #### Graph Node
 
-| المنفذ | الغرض                                                   | المسار                                                              | CLI Argument      | متغيرات البيئة |
-| ------ | ------------------------------------------------------- | ------------------------------------------------------------------- | ----------------- | -------------- |
-| 8000   | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port--       | -              |
-| 8001   | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port--         | -              |
-| 8020   | JSON-RPC <br /> (for managing deployments)        | /                                                                   | admin-port--      | -              |
-| 8030   | Subgraph indexing status API                            | /graphql                                                            | index-node-port-- | -              |
-| 8040   | Prometheus metrics                                      | /metrics                                                            | metrics-port--    | -              |
+| المنفذ | الغرض | المسار | CLI Argument | متغيرات البيئة |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port-- | - |
+| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port-- | - |
+| 8020 | JSON-RPC <br /> (for managing deployments) | / | admin-port-- | - |
+| 8030 | Subgraph indexing status API | /graphql | index-node-port-- | - |
+| 8040 | Prometheus metrics | /metrics | metrics-port-- | - |
 
 #### خدمة المفهرس
 
-| المنفذ | الغرض                                                        | المسار                                                                      | CLI Argument   | متغيرات البيئة         |
-| ------ | ------------------------------------------------------------ | --------------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600   | GraphQL HTTP server <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | port--         | `INDEXER_SERVICE_PORT` |
-| 7300   | Prometheus metrics                                           | /metrics                                                                    | metrics-port-- | -                      |
+| المنفذ | الغرض | المسار | CLI Argument | متغيرات البيئة |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | port-- | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | metrics-port-- | - |
 
 #### وكيل المفهرس(Indexer Agent)
 
diff --git a/website/pages/ar/new-chain-integration.mdx b/website/pages/ar/new-chain-integration.mdx
index ec987dfa5b55..75df818160ce 100644
--- a/website/pages/ar/new-chain-integration.mdx
+++ b/website/pages/ar/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`، ضمن طلب دفعة استدعاء الإجراء عن بُعد باستخدام تمثيل كائنات جافا سكريبت
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/ar/operating-graph-node.mdx b/website/pages/ar/operating-graph-node.mdx
index ac2816215c96..ec9595ef8404 100644
--- a/website/pages/ar/operating-graph-node.mdx
+++ b/website/pages/ar/operating-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:
 
-| المنفذ | الغرض                                                   | المسار                                                              | CLI Argument      | متغيرات البيئة |
-| ------ | ------------------------------------------------------- | ------------------------------------------------------------------- | ----------------- | -------------- |
-| 8000   | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port--       | -              |
-| 8001   | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port--         | -              |
-| 8020   | JSON-RPC <br /> (for managing deployments)        | /                                                                   | admin-port--      | -              |
-| 8030   | Subgraph indexing status API                            | /graphql                                                            | index-node-port-- | -              |
-| 8040   | Prometheus metrics                                      | /metrics                                                            | metrics-port--    | -              |
+| المنفذ | الغرض | المسار | CLI Argument | متغيرات البيئة |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | http-port-- | - |
+| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | ws-port-- | - |
+| 8020 | JSON-RPC <br /> (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.
 
diff --git a/website/pages/ar/querying/graphql-api.mdx b/website/pages/ar/querying/graphql-api.mdx
index 258471c1d9d4..9699c231d93b 100644
--- a/website/pages/ar/querying/graphql-api.mdx
+++ b/website/pages/ar/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| رمز         | عامل التشغيل | الوصف                                                                                                                       |
-| ----------- | ------------ | --------------------------------------------------------------------------------------------------------------------------- |
-| `&`     | `And`        | لدمج عبارات بحث متعددة في فلتر للكيانات التي تتضمن جميع العبارات المتوفرة                                                   |
-| &#x7c;      | `أو`         | الاستعلامات التي تحتوي على عبارات بحث متعددة مفصولة بواسطة عامل التشغيل or ستعيد جميع الكيانات المتطابقة من أي عبارة متوفرة |
-| `<->` | `Follow by`  | يحدد المسافة بين كلمتين.                                                                                                    |
-| `:*`        | `Prefix`     | يستخدم عبارة البحث prefix للعثور على الكلمات التي تتطابق بادئتها (مطلوب حرفان.)                                             |
+| رمز | عامل التشغيل | الوصف |
+| --- | --- | --- |
+| `&` | `And` | لدمج عبارات بحث متعددة في فلتر للكيانات التي تتضمن جميع العبارات المتوفرة |
+| &#x7c; | `أو` | الاستعلامات التي تحتوي على عبارات بحث متعددة مفصولة بواسطة عامل التشغيل or ستعيد جميع الكيانات المتطابقة من أي عبارة متوفرة |
+| `<->` | `Follow by` | يحدد المسافة بين كلمتين. |
+| `:*` | `Prefix` | يستخدم عبارة البحث prefix للعثور على الكلمات التي تتطابق بادئتها (مطلوب حرفان.) |
 
 #### Examples
 
diff --git a/website/pages/ar/querying/querying-best-practices.mdx b/website/pages/ar/querying/querying-best-practices.mdx
index 99d7ed349b04..48e8dec63a28 100644
--- a/website/pages/ar/querying/querying-best-practices.mdx
+++ b/website/pages/ar/querying/querying-best-practices.mdx
@@ -14,7 +14,7 @@ Learn the essential GraphQL language rules and best practices to optimize your s
 
 على عكس REST API ، فإن GraphQL API مبنية على مخطط يحدد الاستعلامات التي يمكن تنفيذها.
 
-على سبيل المثال ، طلب الاستعلام للحصول على توكن باستخدام استعلام ` token ` سيبدو كما يلي:
+على سبيل المثال ، طلب الاستعلام للحصول على توكن باستخدام استعلام `token` سيبدو كما يلي:
 
 ```graphql
 query GetToken($id: ID!) {
@@ -38,7 +38,7 @@ query GetToken($id: ID!) {
 
 تستخدم استعلامات GraphQL لغة GraphQL ، التي تم تحديدها في [المواصفات](https://spec.graphql.org/).
 
-يتكون استعلام ` GetToken ` أعلاه من أجزاء متعددة للغة (تم استبدالها أدناه بـ placeholders ` [...] `):
+يتكون استعلام `GetToken` أعلاه من أجزاء متعددة للغة (تم استبدالها أدناه بـ placeholders `[...]`):
 
 ```graphql
 query [operationName]([variableName]: [variableType]) {
@@ -52,8 +52,8 @@ query [operationName]([variableName]: [variableType]) {
 
 ## Rules for Writing GraphQL Queries
 
-- يجب استخدام كل ` queryName ` مرة واحدة فقط لكل عملية.
-- يجب استخدام كل ` field ` مرة واحدة فقط في التحديد (لا يمكننا الاستعلام عن ` id ` مرتين ضمن ` token `)
+- يجب استخدام كل `queryName` مرة واحدة فقط لكل عملية.
+- يجب استخدام كل `field` مرة واحدة فقط في التحديد (لا يمكننا الاستعلام عن `id` مرتين ضمن `token`)
 - Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer).
 - يجب أن يكون أي متغير تم تعيينه لوسيط متطابقًا مع نوعه.
 - في قائمة المتغيرات المعطاة ، يجب أن يكون كل واحد منها فريدًا.
@@ -456,8 +456,8 @@ In order to keep up with the mentioned above best practices and syntactic rules,
 
 [Setup the "operations-recommended"](https://the-guild.dev/graphql/eslint/docs/configs) config will enforce essential rules such as:
 
-- ` @ graphql-eslint / field-on-right-type `: هل يتم استخدام الحقل على النوع المناسب؟
-- ` @ graphql-eslint / no-unused variables `: هل يجب أن يبقى المتغير المعطى غير مستخدم؟
+- `@ graphql-eslint / field-on-right-type`: هل يتم استخدام الحقل على النوع المناسب؟
+- `@ graphql-eslint / no-unused variables`: هل يجب أن يبقى المتغير المعطى غير مستخدم؟
 - و اكثر!
 
 This will allow you to **catch errors without even testing queries** on the playground or running them in production!
diff --git a/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx
index 9674f1777573..84e00f13b4e1 100644
--- a/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ar/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ let a = a + b
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 ستحتاج إلى إعادة تسمية المتغيرات المكررة إذا كان لديك variable shadowing.
+
 ### مقارانات Null
+
 من خلال إجراء الترقية على ال Subgraph الخاص بك ، قد تحصل أحيانًا على أخطاء مثل هذه:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 لحل المشكلة يمكنك ببساطة تغيير عبارة `if` إلى شيء مثل هذا:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 لإصلاح هذه المشكلة ، يمكنك إنشاء متغير للوصول إلى الخاصية حتى يتمكن المترجم من القيام بعملية التحقق من الـ nullability:
 
 ```typescript
diff --git a/website/pages/ar/sps/triggers-example.mdx b/website/pages/ar/sps/triggers-example.mdx
index 3c1909f87ac8..943e9898ed14 100644
--- a/website/pages/ar/sps/triggers-example.mdx
+++ b/website/pages/ar/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## المتطلبات الأساسية
diff --git a/website/pages/ar/supported-network-requirements.mdx b/website/pages/ar/supported-network-requirements.mdx
index 811fb2a8cec7..9c820d055399 100644
--- a/website/pages/ar/supported-network-requirements.mdx
+++ b/website/pages/ar/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| بوليجون   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| بوليجون | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/cs/cookbook/subgraph-debug-forking.mdx b/website/pages/cs/cookbook/subgraph-debug-forking.mdx
index 522c273a7e36..84df907a9602 100644
--- a/website/pages/cs/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/cs/cookbook/subgraph-debug-forking.mdx
@@ -14,7 +14,7 @@ V kontextu ladění vám ** vidličkování podgrafů** umožňuje ladit neúsp
 
 Když nasadíte podgraf do vzdáleného uzlu Graf pro indexování a ten selže v bloku _X_, dobrou zprávou je, že uzel Graf bude stále obsluhovat dotazy GraphQL pomocí svého úložiště, které je synchronizováno s blokem _X_. To je skvělé! To znamená, že můžeme využít tohoto "aktuálního" úložiště k opravě chyb vznikajících při indexování bloku _X_.
 
-Stručně řečeno, _rozvětvíme neúspěšný podgraf_ ze vzdáleného uzlu grafu, u kterého je zaručeno, že podgraf bude indexován až do bloku *X*, abychom lokálně nasazenému podgrafu laděnému v bloku _X_ poskytli aktuální pohled na stav indexování.
+Stručně řečeno, _rozvětvíme neúspěšný podgraf_ ze vzdáleného uzlu grafu, u kterého je zaručeno, že podgraf bude indexován až do bloku _X_, abychom lokálně nasazenému podgrafu laděnému v bloku _X_ poskytli aktuální pohled na stav indexování.
 
 ## Ukažte mi prosím nějaký kód!
 
diff --git a/website/pages/cs/developing/creating-a-subgraph/advanced.mdx b/website/pages/cs/developing/creating-a-subgraph/advanced.mdx
index fc663d24324b..7d62e06bd1cd 100644
--- a/website/pages/cs/developing/creating-a-subgraph/advanced.mdx
+++ b/website/pages/cs/developing/creating-a-subgraph/advanced.mdx
@@ -238,7 +238,7 @@ The CID of the file as a readable string can be accessed via the `dataSource` as
 const cid = dataSource.stringParam()
 ```
 
-Příklad 
+Příklad
 
 ```typescript
 import { json, Bytes, dataSource } from '@graphprotocol/graph-ts'
diff --git a/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx
index e03ed92103bf..41abfbdccf16 100644
--- a/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/cs/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ Soubor(y) ABI se musí shodovat s vaší smlouvou. Soubory ABI lze získat něko
 
 ## SpecVersion Releases
 
-| Verze | Poznámky vydání                                                                                                                                                          |
-| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| Verze | Poznámky vydání |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
 | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
-| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx
index b284541e1b5e..befce4a22bf8 100644
--- a/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/cs/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Typ          | Popis                                                                                                                                                                                                            |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Pole bajtů reprezentované jako hexadecimální řetězec. Běžně se používá pro hashe a adresy Ethereum.                                                                                                              |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Typ | Popis |
+| --- | --- |
+| `Bytes` | Pole bajtů reprezentované jako hexadecimální řetězec. Běžně se používá pro hashe a adresy Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/cs/developing/graph-ts/api.mdx b/website/pages/cs/developing/graph-ts/api.mdx
index 15d84077faf5..d8c0004d37ef 100644
--- a/website/pages/cs/developing/graph-ts/api.mdx
+++ b/website/pages/cs/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ Knihovna `@graphprotocol/graph-ts` poskytuje následující API:
 
 `apiVersion` v manifestu podgrafu určuje verzi mapovacího API, kterou pro daný podgraf používá uzel Graf.
 
-| Verze | Poznámky vydání                                                                                                                                                                                                                  |
-| :---: | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                     |
-| 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity.                                                                                                                                                                      |
-| 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum<br />Přidání pole `receipt` do objektu Ethereum událost                                                                                                               |
-| 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction<br />Přidáno `baseFeePerGas` do objektu Ethereum bloku                                                                                                                      |
+| Verze | Poznámky vydání |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Přidá ověření existence polí ve schéma při ukládání entity. |
+| 0.0.7 | Přidání tříd `TransactionReceipt` a `Log` do typů Ethereum<br />Přidání pole `receipt` do objektu Ethereum událost |
+| 0.0.6 | Přidáno pole `nonce` do objektu Ethereum Transaction<br />Přidáno `baseFeePerGas` do objektu Ethereum bloku |
 | 0.0.5 | AssemblyScript povýšen na verzi 0.19.10 (obsahuje rozbíjející změny, viz [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` přejmenováno na `ethereum.transaction.gasLimit` |
-| 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall                                                                                                                                                           |
-| 0.0.3 | Do objektu Ethereum Call přidáno pole `from`<br />`etherem.call.address` přejmenováno na `ethereum.call.to`                                                                                                                      |
-| 0.0.2 | Přidání pole `input` do objektu Ethereum Transackce                                                                                                                                                                              |
+| 0.0.4 | Přidání pole `functionSignature` do objektu Ethereum SmartContractCall |
+| 0.0.3 | Do objektu Ethereum Call přidáno pole `from`<br />`etherem.call.address` přejmenováno na `ethereum.call.to` |
+| 0.0.2 | Přidání pole `input` do objektu Ethereum Transackce |
 
 ### Vestavěné typy
 
@@ -147,7 +147,7 @@ _Math_
 - `x.notEqual(y: BigInt): bool` –lze zapsat jako `x != y`.
 - `x.lt(y: BigInt): bool` – lze zapsat jako `x < y`.
 - `x.le(y: BigInt): bool` – lze zapsat jako `x <= y`.
-- `x.gt(y: BigInt): bool` – lze zapsat jako   `x > y`.
+- `x.gt(y: BigInt): bool` – lze zapsat jako `x > y`.
 - `x.ge(y: BigInt): bool` – lze zapsat jako `x >= y`.
 - `x.neg(): BigInt` – lze zapsat jako `-x`.
 - `x.divDecimal(y: BigDecimal): BigDecimal` – dělí desetinným číslem, čímž získá desetinný výsledek.
diff --git a/website/pages/cs/developing/unit-testing-framework.mdx b/website/pages/cs/developing/unit-testing-framework.mdx
index 066874060887..ef2cdd645f76 100644
--- a/website/pages/cs/developing/unit-testing-framework.mdx
+++ b/website/pages/cs/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ Výstup protokolu obsahuje dobu trvání test. Zde je příklad:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Neshoda v argumentech je způsobena neshodou v `graph-ts` a `matchstick-as`. Nejlepší způsob, jak opravit problémy, jako je tento, je aktualizovat vše na nejnovější vydanou verzi.
diff --git a/website/pages/cs/network/benefits.mdx b/website/pages/cs/network/benefits.mdx
index 971f4a21f7e8..98d8bba2cb04 100644
--- a/website/pages/cs/network/benefits.mdx
+++ b/website/pages/cs/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Srovnání nákladů        |            Vlastní hostitel             |                       The Graph Network                       |
-|:-----------------------------:|:---------------------------------------:|:-------------------------------------------------------------:|
-| Měsíční náklady na server\* |              $350 měsíčně               |                              $0                               |
-|     Náklady na dotazování     |                   $0+                   |                         $0 per month                          |
-|  Inženýrský čas<sup>†</sup>   |              $400 měsíčně               | Žádné, zabudované do sítě s globálně distribuovanými indexery |
-|        Dotazy za měsíc        |       Omezeno na infra schopnosti       |                      100,000 (Free Plan)                      |
-|    Náklady na jeden dotaz     |                   $0                    |                        $0<sup>‡</sup>                         |
-|        Infrastruktura         |             Centralizovaný              |                       Decentralizované                        |
-|    Geografická redundancy     |         $750+ Usd za další uzel         |                           Zahrnuto                            |
-|       Provozuschopnost        |                  Různé                  |                            99.9%+                             |
-|    Celkové měsíční náklady    | <span className="highlight-row" />$750+ |                              $0                               |
+| Srovnání nákladů | Vlastní hostitel | The Graph Network |
+| :-: | :-: | :-: |
+| Měsíční náklady na server\* | $350 měsíčně | $0 |
+| Náklady na dotazování | $0+ | $0 per month |
+| Inženýrský čas<sup>†</sup> | $400 měsíčně | Žádné, zabudované do sítě s globálně distribuovanými indexery |
+| Dotazy za měsíc | Omezeno na infra schopnosti | 100,000 (Free Plan) |
+| Náklady na jeden dotaz | $0 | $0<sup>‡</sup> |
+| Infrastruktura | Centralizovaný | Decentralizované |
+| Geografická redundancy | $750+ Usd za další uzel | Zahrnuto |
+| Provozuschopnost | Různé | 99.9%+ |
+| Celkové měsíční náklady | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Srovnání nákladů        |              Vlastní hostitel              |                       The Graph Network                       |
-|:-----------------------------:|:------------------------------------------:|:-------------------------------------------------------------:|
-| Měsíční náklady na server\* |                $350 měsíčně                |                              $0                               |
-|     Náklady na dotazování     |                $500 měsíčně                |                        $120 per month                         |
-|  Inženýrský čas<sup>†</sup>   |                $800 měsíčně                | Žádné, zabudované do sítě s globálně distribuovanými indexery |
-|        Dotazy za měsíc        |        Omezeno na infra schopnosti         |                          ~3,000,000                           |
-|    Náklady na jeden dotaz     |                     $0                     |                           $0.00004                            |
-|        Infrastruktura         |               Centralizovaný               |                       Decentralizované                        |
-|      Výdaje inženýrskou       |               $200 za hodinu               |                           Zahrnuto                            |
-|    Geografická redundancy     |   $1,200 celkových nákladů na další uzel   |                           Zahrnuto                            |
-|       Provozuschopnost        |                   Různé                    |                            99.9%+                             |
-|    Celkové měsíční náklady    | <span className="highlight-row" /> $1,650+ |                             $120                              |
+| Srovnání nákladů | Vlastní hostitel | The Graph Network |
+| :-: | :-: | :-: |
+| Měsíční náklady na server\* | $350 měsíčně | $0 |
+| Náklady na dotazování | $500 měsíčně | $120 per month |
+| Inženýrský čas<sup>†</sup> | $800 měsíčně | Žádné, zabudované do sítě s globálně distribuovanými indexery |
+| Dotazy za měsíc | Omezeno na infra schopnosti | ~3,000,000 |
+| Náklady na jeden dotaz | $0 | $0.00004 |
+| Infrastruktura | Centralizovaný | Decentralizované |
+| Výdaje inženýrskou | $200 za hodinu | Zahrnuto |
+| Geografická redundancy | $1,200 celkových nákladů na další uzel | Zahrnuto |
+| Provozuschopnost | Různé | 99.9%+ |
+| Celkové měsíční náklady | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Srovnání nákladů        |              Vlastní hostitel               |                       The Graph Network                       |
-|:-----------------------------:|:-------------------------------------------:|:-------------------------------------------------------------:|
-| Měsíční náklady na server\* |            $1100 měsíčně za uzel            |                              $0                               |
-|     Náklady na dotazování     |                    $4000                    |                       $1,200 per month                        |
-|     Počet potřebných uzlů     |                     10                      |                         Nepoužije se                          |
-|  Inženýrský čas<sup>†</sup>   |          6$, 000 nebo více měsíčně          | Žádné, zabudované do sítě s globálně distribuovanými indexery |
-|        Dotazy za měsíc        |         Omezeno na infra schopnosti         |                          ~30,000,000                          |
-|    Náklady na jeden dotaz     |                     $0                      |                           $0.00004                            |
-|        Infrastruktura         |               Centralizovaný                |                       Decentralizované                        |
-|    Geografická redundancy     |   $1,200 celkových nákladů na další uzel    |                           Zahrnuto                            |
-|       Provozuschopnost        |                    Různé                    |                            99.9%+                             |
-|    Celkové měsíční náklady    | <span className="highlight-row" /> $11,000+ |                            $1,200                             |
+| Srovnání nákladů | Vlastní hostitel | The Graph Network |
+| :-: | :-: | :-: |
+| Měsíční náklady na server\* | $1100 měsíčně za uzel | $0 |
+| Náklady na dotazování | $4000 | $1,200 per month |
+| Počet potřebných uzlů | 10 | Nepoužije se |
+| Inženýrský čas<sup>†</sup> | 6$, 000 nebo více měsíčně | Žádné, zabudované do sítě s globálně distribuovanými indexery |
+| Dotazy za měsíc | Omezeno na infra schopnosti | ~30,000,000 |
+| Náklady na jeden dotaz | $0 | $0.00004 |
+| Infrastruktura | Centralizovaný | Decentralizované |
+| Geografická redundancy | $1,200 celkových nákladů na další uzel | Zahrnuto |
+| Provozuschopnost | Různé | 99.9%+ |
+| Celkové měsíční náklady | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*včetně nákladů na zálohování: $50-$100 měsíčně
 
diff --git a/website/pages/cs/network/delegating.mdx b/website/pages/cs/network/delegating.mdx
index 249cd411e45a..ef106bad0942 100644
--- a/website/pages/cs/network/delegating.mdx
+++ b/website/pages/cs/network/delegating.mdx
@@ -64,8 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Nejlepší indexátor dává delegátům 90 % odměn. Na
-  prostřední dává delegátům 20 % odměn. Spodní dává delegátům ~83 %.*
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Nejlepší indexátor dává delegátům 90 % odměn. Na prostřední dává
+  delegátům 20 % odměn. Spodní dává delegátům ~83 %.*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/cs/network/indexing.mdx b/website/pages/cs/network/indexing.mdx
index fe0a36c340ca..a3fb06a96484 100644
--- a/website/pages/cs/network/indexing.mdx
+++ b/website/pages/cs/network/indexing.mdx
@@ -113,11 +113,11 @@ Indexátory se mohou odlišovat použitím pokročilých technik pro rozhodován
 - **Large** - Připraveno k indexování všech aktuálně nepoužívaných příbuzných podgrafů.
 
 | Nastavení | Postgres<br />(CPUs) | Postgres<br />(paměť v GBs) | Postgres<br />(disk v TBs) | VMs<br />(CPUs) | VMs<br />(paměť v GBs) |
-| --------- |:--------------------------:|:---------------------------------:|:--------------------------------:|:---------------------:|:----------------------------:|
-| Malé      |             4              |                 8                 |                1                 |           4           |              16              |
-| Standard  |             8              |                30                 |                1                 |          12           |              48              |
-| Střední   |             16             |                64                 |                2                 |          32           |              64              |
-| Velký     |             72             |                468                |               3.5                |          48           |             184              |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Malé | 4 | 8 | 1 | 4 | 16 |
+| Standard | 8 | 30 | 1 | 12 | 48 |
+| Střední | 16 | 64 | 2 | 32 | 64 |
+| Velký | 72 | 468 | 3.5 | 48 | 184 |
 
 ### Jaká jsou základní bezpečnostní opatření, která by měl indexátor přijmout?
 
@@ -149,20 +149,20 @@ Poznámka: Pro podporu agilního škálování se doporučuje oddělit dotazová
 
 #### Uzel Graf
 
-| Port | Účel                                                 | Trasy                                                | CLI Argument      | Proměnná prostředí |
-| ---- | ---------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
-| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
-| 8001 | GraphQL WS<br />(pro odběry podgrafů)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
-| 8020 | JSON-RPC<br />(pro správu nasazení)            | /                                                    | --admin-port      | -                  |
-| 8030 | Stav indexování podgrafů API                         | /graphql                                             | --index-node-port | -                  |
-| 8040 | Metriky Prometheus                                   | /metrics                                             | --metrics-port    | -                  |
+| Port | Účel | Trasy | CLI Argument | Proměnná prostředí |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(pro odběry podgrafů) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(pro správu nasazení) | / | --admin-port | - |
+| 8030 | Stav indexování podgrafů API | /graphql | --index-node-port | - |
+| 8040 | Metriky Prometheus | /metrics | --metrics-port | - |
 
 #### Služba Indexer
 
-| Port | Účel                                                            | Trasy                                                                   | CLI Argument   | Proměnná prostředí     |
-| ---- | --------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL HTTP server<br />(pro placené dotazy na podgrafy) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Metriky Prometheus                                              | /metrics                                                                | --metrics-port | -                      |
+| Port | Účel | Trasy | CLI Argument | Proměnná prostředí |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(pro placené dotazy na podgrafy) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Metriky Prometheus | /metrics | --metrics-port | - |
 
 #### Agent indexátoru
 
diff --git a/website/pages/cs/new-chain-integration.mdx b/website/pages/cs/new-chain-integration.mdx
index 6fd34e39cbac..e9f52eb42a93 100644
--- a/website/pages/cs/new-chain-integration.mdx
+++ b/website/pages/cs/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/cs/operating-graph-node.mdx b/website/pages/cs/operating-graph-node.mdx
index 9a720348c8c5..b6067883a47a 100644
--- a/website/pages/cs/operating-graph-node.mdx
+++ b/website/pages/cs/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Kompletní příklad konfigurace Kubernetes naleznete v úložišti [indexer](ht
 
 Když je Graf Uzel spuštěn, zpřístupňuje následující ports:
 
-| Port | Účel                                                 | Trasy                                                | CLI Argument      | Proměnná prostředí |
-| ---- | ---------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
-| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
-| 8001 | GraphQL WS<br />(pro odběry podgrafů)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
-| 8020 | JSON-RPC<br />(pro správu nasazení)            | /                                                    | --admin-port      | -                  |
-| 8030 | Stav indexování podgrafů API                         | /graphql                                             | --index-node-port | -                  |
-| 8040 | Metriky Prometheus                                   | /metrics                                             | --metrics-port    | -                  |
+| Port | Účel | Trasy | CLI Argument | Proměnná prostředí |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(pro dotazy podgrafy) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(pro odběry podgrafů) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(pro správu nasazení) | / | --admin-port | - |
+| 8030 | Stav indexování podgrafů API | /graphql | --index-node-port | - |
+| 8040 | Metriky Prometheus | /metrics | --metrics-port | - |
 
 > **Důležité**: Dávejte pozor na veřejné vystavování portů - **administrační porty** by měly být uzamčeny. To se týká i koncového bodu JSON-RPC uzlu Graf.
 
diff --git a/website/pages/cs/querying/graphql-api.mdx b/website/pages/cs/querying/graphql-api.mdx
index 16b65fe32b1e..194d477a23c1 100644
--- a/website/pages/cs/querying/graphql-api.mdx
+++ b/website/pages/cs/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntaktický cukr:** Výše uvedený dotaz můžete zjednodušit odstraněním operátoru `a` předáním podvýrazu odděleného čárkami.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltextové vyhledávací dotazy mají jedno povinné pole `text` pro zadání
 
 Operátory fulltextového vyhledávání:
 
-| Symbol      | Operátor    | Popis                                                                                                                         |
-| ----------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
-| `&`     | `a`         | Pro kombinaci více vyhledávacích výrazů do filtru pro entity, které obsahují všechny zadané výrazy                            |
-| &#x7c;      | `Nebo`      | 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 |
+| --- | --- | --- |
+| `&` | `a` | Pro kombinaci více vyhledávacích výrazů do filtru pro entity, které obsahují všechny zadané výrazy |
+| &#x7c; | `Nebo` | 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
 
diff --git a/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx b/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx
index e59516868de6..d1b9eb00bc04 100644
--- a/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/cs/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Pokud jste použili stínování proměnných, musíte duplicitní proměnné přejmenovat.
+
 ### Nulová srovnání
+
 Při aktualizaci podgrafu může někdy dojít k těmto chybám:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Pro vyřešení můžete jednoduše změnit příkaz `if` na něco takového:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Chcete-li tento problém vyřešit, můžete vytvořit proměnnou pro přístup k této vlastnosti, aby překladač mohl provést kouzlo kontroly nulovatelnosti:
 
 ```typescript
diff --git a/website/pages/cs/sps/triggers-example.mdx b/website/pages/cs/sps/triggers-example.mdx
index a25f86fd5aa6..70dda12c61fd 100644
--- a/website/pages/cs/sps/triggers-example.mdx
+++ b/website/pages/cs/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Požadavky
diff --git a/website/pages/cs/supported-network-requirements.mdx b/website/pages/cs/supported-network-requirements.mdx
index efbee1c17750..a81118cec231 100644
--- a/website/pages/cs/supported-network-requirements.mdx
+++ b/website/pages/cs/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Síť       | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Síť | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx
index 48944eebbfbb..5ff21e03c171 100644
--- a/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/de/arbitrum/l2-transfer-tools-faq.mdx
@@ -64,7 +64,7 @@ Die Übertragungszeit beträgt etwa 20 Minuten. Die Arbitrum-Brücke arbeitet im
 
 ### Wird mein Subgraph noch auffindbar sein, nachdem ich ihn auf L2 übertragen habe?
 
-Ihr Subgraph ist nur in dem Netzwerk auffindbar, in dem er veröffentlicht ist. Wenn Ihr Subgraph zum Beispiel auf Arbitrum One ist, können Sie ihn nur im Explorer auf Arbitrum One finden und nicht auf Ethereum. Bitte vergewissern Sie sich, dass Sie Arbitrum One in der Netzwerkumschaltung oben auf der Seite ausgewählt haben, um sicherzustellen, dass Sie sich im richtigen Netzwerk befinden.  Nach der Übertragung wird der L1-Subgraph als veraltet angezeigt.
+Ihr Subgraph ist nur in dem Netzwerk auffindbar, in dem er veröffentlicht ist. Wenn Ihr Subgraph zum Beispiel auf Arbitrum One ist, können Sie ihn nur im Explorer auf Arbitrum One finden und nicht auf Ethereum. Bitte vergewissern Sie sich, dass Sie Arbitrum One in der Netzwerkumschaltung oben auf der Seite ausgewählt haben, um sicherzustellen, dass Sie sich im richtigen Netzwerk befinden. Nach der Übertragung wird der L1-Subgraph als veraltet angezeigt.
 
 ### Muss mein Subgraph ( Teilgraph ) veröffentlicht werden, um ihn zu übertragen?
 
diff --git a/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx
index 6b68f875fdd2..91922e0319e7 100644
--- a/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/de/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/de/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/de/developing/graph-ts/api.mdx b/website/pages/de/developing/graph-ts/api.mdx
index 020d37ade7f7..649dc4d73cd5 100644
--- a/website/pages/de/developing/graph-ts/api.mdx
+++ b/website/pages/de/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/de/developing/unit-testing-framework.mdx b/website/pages/de/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/de/developing/unit-testing-framework.mdx
+++ b/website/pages/de/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/de/network/benefits.mdx b/website/pages/de/network/benefits.mdx
index 35f0df7781e1..f9aec6eee091 100644
--- a/website/pages/de/network/benefits.mdx
+++ b/website/pages/de/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                        The Graph Network                        |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|        Infrastruktur         |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Infrastruktur | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                        The Graph Network                        |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|        Infrastruktur         |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastruktur | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                        The Graph Network                        |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|        Infrastruktur         |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastruktur | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/de/network/indexing.mdx b/website/pages/de/network/indexing.mdx
index 3b704381d0f0..c620276a90e7 100644
--- a/website/pages/de/network/indexing.mdx
+++ b/website/pages/de/network/indexing.mdx
@@ -113,11 +113,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.
 
 | Konfiguration | Postgres<br />(CPUs) | Postgres<br />(Speicher in GB) | Postgres<br />(Festplatte in TB) | VMs<br />(CPUs) | VMs<br />(Speicher in GB) |
-| ------------- |:--------------------------:|:------------------------------------:|:--------------------------------------:|:---------------------:|:-------------------------------:|
-| Klein         |             4              |                  8                   |                   1                    |           4           |               16                |
-| Standard      |             8              |                  30                  |                   1                    |          12           |               48                |
-| Mittel        |             16             |                  64                  |                   2                    |          32           |               64                |
-| Groß          |             72             |                 468                  |                  3.5                   |          48           |               184               |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Klein | 4 | 8 | 1 | 4 | 16 |
+| Standard | 8 | 30 | 1 | 12 | 48 |
+| Mittel | 16 | 64 | 2 | 32 | 64 |
+| Groß | 72 | 468 | 3.5 | 48 | 184 |
 
 ### What are some basic security precautions an Indexer should take?
 
@@ -149,20 +149,20 @@ Note: To support agile scaling, it is recommended that query and indexing concer
 
 #### Der Graph-Knoten
 
-| Port | Zweck                                                 | Routen                                               | CLI-Argument      | Umgebungsvariable |
-| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | ----------------- |
-| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                 |
-| 8001 | GraphQL WS<br />(für Subgraf-Abonnements)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                 |
-| 8020 | JSON-RPC<br />(zum Verwalten von Deployments)   | /                                                    | --admin-port      | -                 |
-| 8030 | Subgraf-Indizierungsstatus-API                        | /graphql                                             | --index-node-port | -                 |
-| 8040 | Prometheus-Metriken                                   | /metrics                                             | --metrics-port    | -                 |
+| Port | Zweck | Routen | CLI-Argument | Umgebungsvariable |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(für Subgraf-Abonnements) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(zum Verwalten von Deployments) | / | --admin-port | - |
+| 8030 | Subgraf-Indizierungsstatus-API | /graphql | --index-node-port | - |
+| 8040 | Prometheus-Metriken | /metrics | --metrics-port | - |
 
 #### Indexer Service
 
-| Port | Zweck                                                                  | Routen                                                                  | CLI-Argument   | Umgebungsvariable      |
-| ---- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL-HTTP-Server<br />(für kostenpflichtige Subgraf-Abfragen) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus-Metriken                                                    | /metrics                                                                | --metrics-port | -                      |
+| Port | Zweck | Routen | CLI-Argument | Umgebungsvariable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL-HTTP-Server<br />(für kostenpflichtige Subgraf-Abfragen) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus-Metriken | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/de/new-chain-integration.mdx b/website/pages/de/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/de/new-chain-integration.mdx
+++ b/website/pages/de/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/de/operating-graph-node.mdx b/website/pages/de/operating-graph-node.mdx
index 571f332cd774..0a2dda70086d 100644
--- a/website/pages/de/operating-graph-node.mdx
+++ b/website/pages/de/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Eine vollständige Kubernetes-Beispielkonfiguration finden Sie im [Indexer-Repos
 
 Wenn es ausgeführt wird, stellt Graph Node die folgenden Ports zur Verfügung:
 
-| Port | Zweck                                                 | Routen                                               | CLI-Argument      | Umgebungsvariable |
-| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | ----------------- |
-| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                 |
-| 8001 | GraphQL WS<br />(für Subgraf-Abonnements)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                 |
-| 8020 | JSON-RPC<br />(zum Verwalten von Deployments)   | /                                                    | --admin-port      | -                 |
-| 8030 | Subgraf-Indizierungsstatus-API                        | /graphql                                             | --index-node-port | -                 |
-| 8040 | Prometheus-Metriken                                   | /metrics                                             | --metrics-port    | -                 |
+| Port | Zweck | Routen | CLI-Argument | Umgebungsvariable |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP-Server<br />(für Subgraf-Abfragen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(für Subgraf-Abonnements) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(zum Verwalten von Deployments) | / | --admin-port | - |
+| 8030 | Subgraf-Indizierungsstatus-API | /graphql | --index-node-port | - |
+| 8040 | Prometheus-Metriken | /metrics | --metrics-port | - |
 
 > **Wichtig**: Seien Sie vorsichtig, wenn Sie Ports öffentlich zugänglich machen - **Administrationsports** sollten gesperrt bleiben. Dies schließt den JSON-RPC-Endpunkt des Graph-Knotens ein.
 
diff --git a/website/pages/de/querying/graphql-api.mdx b/website/pages/de/querying/graphql-api.mdx
index abe9db8cc7f4..cd06c27f4d94 100644
--- a/website/pages/de/querying/graphql-api.mdx
+++ b/website/pages/de/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Beschreibung                                                                                                                         |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 | Beschreibung |
+| --- | --- | --- |
+| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
+| &#x7c; | `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.) |
 
 #### Beispiele
 
diff --git a/website/pages/de/release-notes/assemblyscript-migration-guide.mdx b/website/pages/de/release-notes/assemblyscript-migration-guide.mdx
index 058c48b32e6f..fb1ad8beb382 100644
--- a/website/pages/de/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/de/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/de/sps/triggers-example.mdx b/website/pages/de/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/de/sps/triggers-example.mdx
+++ b/website/pages/de/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/de/supported-network-requirements.mdx b/website/pages/de/supported-network-requirements.mdx
index afbf755c0a5a..df15ef48d762 100644
--- a/website/pages/de/supported-network-requirements.mdx
+++ b/website/pages/de/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/es/cookbook/cosmos.mdx b/website/pages/es/cookbook/cosmos.mdx
index 67d7021cf6d0..fe36514f6de9 100644
--- a/website/pages/es/cookbook/cosmos.mdx
+++ b/website/pages/es/cookbook/cosmos.mdx
@@ -170,7 +170,7 @@ Cada tipo de handler viene con su propia estructura de datos que se pasa como ar
 - Los handlers de transacciones reciben el tipo `TransactionData`.
 - Los handlers de mensajes reciben el tipo `MessageData`.
 
-Como parte de `MessageData`, el message handler recibe un contexto de transacción, que contiene la información más importante sobre una transacción que abarca un mensaje. El contexto de transacción también está disponible en el tipo ` EventData `, pero solo cuando el evento correspondiente está asociado con una transacción. Además, todos los controladores reciben una referencia a un bloque (` HeaderOnlyBlock `).
+Como parte de `MessageData`, el message handler recibe un contexto de transacción, que contiene la información más importante sobre una transacción que abarca un mensaje. El contexto de transacción también está disponible en el tipo `EventData`, pero solo cuando el evento correspondiente está asociado con una transacción. Además, todos los controladores reciben una referencia a un bloque (`HeaderOnlyBlock`).
 
 Puedes encontrar una lista completa de los tipos para la integración Cosmos aquí [here](https://github.com/graphprotocol/graph-ts/blob/4c064a8118dff43b110de22c7756e5d47fcbc8df/chain/cosmos.ts).
 
diff --git a/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx
index 9a754fb67035..b70948811960 100644
--- a/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/es/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ Los archivos ABI deben coincidir con tu(s) contrato(s). Hay varias formas de obt
 
 ## SpecVersion Releases
 
-| Version | Notas del lanzamiento                                                                                                                                                    |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Notas del lanzamiento |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx
index 168d008294ed..4ecbc03b60a8 100644
--- a/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/es/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Tipo         | Descripción                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, representado como un string hexadecimal. Comúnmente utilizado para los hashes y direcciones de Ethereum.                                                                                             |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Tipo | Descripción |
+| --- | --- |
+| `Bytes` | Byte array, representado como un string hexadecimal. Comúnmente utilizado para los hashes y direcciones de Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -306,7 +306,7 @@ Diccionarios de idiomas admitidos:
 
 Algoritmos admitidos para ordenar los resultados:
 
-| Algorithm           | Description                                                                                        |
-| ------------------- | -------------------------------------------------------------------------------------------------- |
-| rank                | Usa la calidad de coincidencia (0-1) de la consulta de texto completo para ordenar los resultados. |
-| rango de proximidad | Similar to rank but also includes the proximity of the matches.                                    |
+| Algorithm | Description |
+| --- | --- |
+| rank | Usa la calidad de coincidencia (0-1) de la consulta de texto completo para ordenar los resultados. |
+| rango de proximidad | Similar to rank but also includes the proximity of the matches. |
diff --git a/website/pages/es/developing/graph-ts/api.mdx b/website/pages/es/developing/graph-ts/api.mdx
index 6660507ae768..5399f3838722 100644
--- a/website/pages/es/developing/graph-ts/api.mdx
+++ b/website/pages/es/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Notas del lanzamiento                                                                                                                                                                                                                         |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Notas del lanzamiento |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Tipos Incorporados
 
diff --git a/website/pages/es/developing/unit-testing-framework.mdx b/website/pages/es/developing/unit-testing-framework.mdx
index 68c3ff849637..63f6babad3d9 100644
--- a/website/pages/es/developing/unit-testing-framework.mdx
+++ b/website/pages/es/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ La salida del log incluye la duración de la ejecución de la prueba. Aquí hay
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 La falta de coincidencia en los argumentos se debe a la falta de coincidencia en `graph-ts` y `matchstick-as`. La mejor manera de solucionar problemas como este es actualizar todo a la última versión publicada.
diff --git a/website/pages/es/network/benefits.mdx b/website/pages/es/network/benefits.mdx
index f1055e96a426..1b8a5510f076 100644
--- a/website/pages/es/network/benefits.mdx
+++ b/website/pages/es/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|      Comparación de costos       |                Self Hosted                |                           The Graph Network                           |
-|:--------------------------------:|:-----------------------------------------:|:---------------------------------------------------------------------:|
-|  Costo mensual del servidor\*  |               $350 por mes                |                                  $0                                   |
-|        Costos de consulta        |                    $0+                    |                             $0 per month                              |
-| Tiempo de ingeniería<sup>†</sup> |               $400 por mes                | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
-|        Consultas por mes         | Limitado a capacidades de infraestructura |                          100,000 (Free Plan)                          |
-|        Costo por consulta        |                    $0                     |                            $0<sup>‡</sup>                             |
-|         Infraestructura          |               Centralizado                |                            Descentralizado                            |
-|      Redundancia geográfica      |         $750+ por nodo adicional          |                               Incluido                                |
-|       Tiempo de actividad        |                   Varía                   |                                99.9%+                                 |
-|     Costos mensuales totales     |  <span className="highlight-row" />$750+  |                                  $0                                   |
+| Comparación de costos | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Costo mensual del servidor\* | $350 por mes | $0 |
+| Costos de consulta | $0+ | $0 per month |
+| Tiempo de ingeniería<sup>†</sup> | $400 por mes | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
+| Consultas por mes | Limitado a capacidades de infraestructura | 100,000 (Free Plan) |
+| Costo por consulta | $0 | $0<sup>‡</sup> |
+| Infraestructura | Centralizado | Descentralizado |
+| Redundancia geográfica | $750+ por nodo adicional | Incluido |
+| Tiempo de actividad | Varía | 99.9%+ |
+| Costos mensuales totales | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|      Comparación de costos       |                 Self Hosted                 |                           The Graph Network                           |
-|:--------------------------------:|:-------------------------------------------:|:---------------------------------------------------------------------:|
-|  Costo mensual del servidor\*  |                $350 por mes                 |                                  $0                                   |
-|        Costos de consulta        |                $500 por mes                 |                            $120 per month                             |
-| Tiempo de ingeniería<sup>†</sup> |                $800 por mes                 | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
-|        Consultas por mes         |  Limitado a capacidades de infraestructura  |                              ~3,000,000                               |
-|        Costo por consulta        |                     $0                      |                               $0.00004                                |
-|         Infraestructura          |                Centralizado                 |                            Descentralizado                            |
-|       Gastos de ingeniería       |                $200 por hora                |                               Incluido                                |
-|      Redundancia geográfica      | $1,200 en costos totales por nodo adicional |                               Incluido                                |
-|       Tiempo de actividad        |                    Varía                    |                                99.9%+                                 |
-|     Costos mensuales totales     | <span className="highlight-row" /> $1,650+  |                                 $120                                  |
+| Comparación de costos | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Costo mensual del servidor\* | $350 por mes | $0 |
+| Costos de consulta | $500 por mes | $120 per month |
+| Tiempo de ingeniería<sup>†</sup> | $800 por mes | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
+| Consultas por mes | Limitado a capacidades de infraestructura | ~3,000,000 |
+| Costo por consulta | $0 | $0.00004 |
+| Infraestructura | Centralizado | Descentralizado |
+| Gastos de ingeniería | $200 por hora | Incluido |
+| Redundancia geográfica | $1,200 en costos totales por nodo adicional | Incluido |
+| Tiempo de actividad | Varía | 99.9%+ |
+| Costos mensuales totales | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|      Comparación de costos       |                 Self Hosted                 |                           The Graph Network                           |
-|:--------------------------------:|:-------------------------------------------:|:---------------------------------------------------------------------:|
-|  Costo mensual del servidor\*  |           $1100 por mes, por nodo           |                                  $0                                   |
-|        Costos de consulta        |                    $4000                    |                           $1,200 per month                            |
-|    Número de nodos necesarios    |                     10                      |                               No aplica                               |
-| Tiempo de ingeniería<sup>†</sup> |            $6,000 o más por mes             | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
-|        Consultas por mes         |  Limitado a capacidades de infraestructura  |                              ~30,000,000                              |
-|        Costo por consulta        |                     $0                      |                               $0.00004                                |
-|         Infraestructura          |                Centralizado                 |                            Descentralizado                            |
-|      Redundancia geográfica      | $1,200 en costos totales por nodo adicional |                               Incluido                                |
-|       Tiempo de actividad        |                    Varía                    |                                99.9%+                                 |
-|     Costos mensuales totales     | <span className="highlight-row" /> $11,000+ |                                $1,200                                 |
+| Comparación de costos | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Costo mensual del servidor\* | $1100 por mes, por nodo | $0 |
+| Costos de consulta | $4000 | $1,200 per month |
+| Número de nodos necesarios | 10 | No aplica |
+| Tiempo de ingeniería<sup>†</sup> | $6,000 o más por mes | Ninguno, integrado en la red con Indexadores distribuidos globalmente |
+| Consultas por mes | Limitado a capacidades de infraestructura | ~30,000,000 |
+| Costo por consulta | $0 | $0.00004 |
+| Infraestructura | Centralizado | Descentralizado |
+| Redundancia geográfica | $1,200 en costos totales por nodo adicional | Incluido |
+| Tiempo de actividad | Varía | 99.9%+ |
+| Costos mensuales totales | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*incluidos los costos de copia de seguridad: $50-$100 por mes
 
diff --git a/website/pages/es/network/indexing.mdx b/website/pages/es/network/indexing.mdx
index 076ee45d9703..e85cc01e0b86 100644
--- a/website/pages/es/network/indexing.mdx
+++ b/website/pages/es/network/indexing.mdx
@@ -113,11 +113,11 @@ Los indexadores pueden diferenciarse aplicando técnicas avanzadas para tomar de
 - **Grande**: Preparado para indexar todos los subgrafos utilizados actualmente y atender solicitudes para el tráfico relacionado.
 
 | Configuración | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
-| ------------- |:--------------------------:|:-----------------------------------:|:---------------------------------:|:---------------------:|:------------------------------:|
-| Pequeño       |             4              |                  8                  |                 1                 |           4           |               16               |
-| Estándar      |             8              |                 30                  |                 1                 |          12           |               48               |
-| Medio         |             16             |                 64                  |                 2                 |          32           |               64               |
-| Grande        |             72             |                 468                 |                3,5                |          48           |              184               |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Pequeño | 4 | 8 | 1 | 4 | 16 |
+| Estándar | 8 | 30 | 1 | 12 | 48 |
+| Medio | 16 | 64 | 2 | 32 | 64 |
+| Grande | 72 | 468 | 3,5 | 48 | 184 |
 
 ### ¿Qué precauciones básicas de seguridad debe tomar un Indexador?
 
@@ -149,20 +149,20 @@ Nota: Para admitir el escalado ágil, se recomienda que las inquietudes de consu
 
 #### Graph Node
 
-| Puerto | Objeto                                                         | Rutas                                                | Argumento CLI     | Variable de Entorno |
-| ------ | -------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------- |
-| 8000   | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                   |
-| 8001   | GraphQL WS<br />(para suscripciones a subgrafos)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                   |
-| 8020   | JSON-RPC<br />(para administrar implementaciones)        | /                                                    | --admin-port      | -                   |
-| 8030   | API de estado de indexación de subgrafos                       | /graphql                                             | --index-node-port | -                   |
-| 8040   | Métricas de Prometheus                                         | /metrics                                             | --metrics-port    | -                   |
+| Puerto | Objeto | Rutas | Argumento CLI | Variable de Entorno |
+| --- | --- | --- | --- | --- |
+| 8000 | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(para suscripciones a subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(para administrar implementaciones) | / | --admin-port | - |
+| 8030 | API de estado de indexación de subgrafos | /graphql | --index-node-port | - |
+| 8040 | Métricas de Prometheus | /metrics | --metrics-port | - |
 
 #### Servicio de Indexador
 
-| Puerto | Objeto                                                                | Rutas                                                                   | Argumento CLI  | Variable de Entorno    |
-| ------ | --------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600   | Servidor HTTP GraphQL<br />(para consultas de subgrafo pagadas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300   | Métricas de Prometheus                                                | /metrics                                                                | --metrics-port | -                      |
+| Puerto | Objeto | Rutas | Argumento CLI | Variable de Entorno |
+| --- | --- | --- | --- | --- |
+| 7600 | Servidor HTTP GraphQL<br />(para consultas de subgrafo pagadas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Métricas de Prometheus | /metrics | --metrics-port | - |
 
 #### Agente Indexador
 
diff --git a/website/pages/es/new-chain-integration.mdx b/website/pages/es/new-chain-integration.mdx
index ea501d78d47a..6e61fadecf0c 100644
--- a/website/pages/es/new-chain-integration.mdx
+++ b/website/pages/es/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, en una solicitud por lotes JSON-RPC
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/es/operating-graph-node.mdx b/website/pages/es/operating-graph-node.mdx
index 99e966da590a..2dc80685b400 100644
--- a/website/pages/es/operating-graph-node.mdx
+++ b/website/pages/es/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Puedes encontrar un ejemplo completo de configuración de Kubernetes en el [Inde
 
 Cuando está funcionando, Graph Node muestra los siguientes puertos:
 
-| Puerto | Objeto                                                         | Rutas                                                | Argumento CLI     | Variable de Entorno |
-| ------ | -------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------- |
-| 8000   | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                   |
-| 8001   | GraphQL WS<br />(para suscripciones a subgrafos)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                   |
-| 8020   | JSON-RPC<br />(para administrar implementaciones)        | /                                                    | --admin-port      | -                   |
-| 8030   | API de estado de indexación de subgrafos                       | /graphql                                             | --index-node-port | -                   |
-| 8040   | Métricas de Prometheus                                         | /metrics                                             | --metrics-port    | -                   |
+| Puerto | Objeto | Rutas | Argumento CLI | Variable de Entorno |
+| --- | --- | --- | --- | --- |
+| 8000 | Servidor HTTP GraphQL<br />(para consultas de subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(para suscripciones a subgrafos) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(para administrar implementaciones) | / | --admin-port | - |
+| 8030 | API de estado de indexación de subgrafos | /graphql | --index-node-port | - |
+| 8040 | Métricas de Prometheus | /metrics | --metrics-port | - |
 
 > **Importante**: Ten cuidado con exponer puertos públicamente - los **puertos de administración** deben mantenerse bloqueados. Esto incluye el punto final JSON-RPC de Graph Node.
 
diff --git a/website/pages/es/querying/graphql-api.mdx b/website/pages/es/querying/graphql-api.mdx
index e0281d0b1bdc..0817a89f807e 100644
--- a/website/pages/es/querying/graphql-api.mdx
+++ b/website/pages/es/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Azúcar sintáctico**: Puedes simplificar la consulta anterior eliminando el operador `and` pasando una subexpresión separada por comas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Las consultas de búsqueda de texto completo tienen un campo obligatorio, `text`
 
 Operadores de búsqueda de texto completo:
 
-| 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                                                |
-| &#x7c;      | `O`         | 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.                                                                                                                         |
-| `:*`        | `Prefijo`   | 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 |
+| &#x7c; | `O` | 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. |
+| `:*` | `Prefijo` | Utilice el término de búsqueda del prefijo para encontrar palabras cuyo prefijo coincida (se requieren 2 caracteres.) |
 
 #### Ejemplos
 
diff --git a/website/pages/es/release-notes/assemblyscript-migration-guide.mdx b/website/pages/es/release-notes/assemblyscript-migration-guide.mdx
index c3770a5c9ef7..bfc973f982dd 100644
--- a/website/pages/es/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/es/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Tendrás que cambiar el nombre de las variables duplicadas si tienes una variable shadowing.
+
 ### Comparaciones Nulas
+
 Al hacer la actualización en un subgrafo, a veces pueden aparecer errores como estos:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Para solucionarlo puedes simplemente cambiar la declaración `if` por algo así:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Para solucionar este problema, puedes crear una variable para ese acceso a la propiedad de manera que el compilador pueda hacer la magia de la comprobación de nulidad:
 
 ```typescript
diff --git a/website/pages/es/release-notes/graphql-validations-migration-guide.mdx b/website/pages/es/release-notes/graphql-validations-migration-guide.mdx
index 292c60a70cf9..55801738ddca 100644
--- a/website/pages/es/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/es/release-notes/graphql-validations-migration-guide.mdx
@@ -406,7 +406,6 @@ query {
   user {
     id
     image # 'image' requiere un conjunto de selección para subcampos!
-
   }
 }
 ```
diff --git a/website/pages/es/sps/triggers-example.mdx b/website/pages/es/sps/triggers-example.mdx
index b52cd3cf42e3..f5b1d99ba473 100644
--- a/website/pages/es/sps/triggers-example.mdx
+++ b/website/pages/es/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerrequisitos
diff --git a/website/pages/es/supported-network-requirements.mdx b/website/pages/es/supported-network-requirements.mdx
index c06461d981d6..dfebec344880 100644
--- a/website/pages/es/supported-network-requirements.mdx
+++ b/website/pages/es/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Red       | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Red | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx
index d43463682da5..45ec79e9d4f9 100644
--- a/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/fr/arbitrum/l2-transfer-tools-faq.mdx
@@ -336,13 +336,11 @@ Si vous n’avez transféré aucun solde de contrat de vesting à L2 et que votr
 
 ### J’utilise mon contrat de vesting pour investir dans mainnet. Puis-je transférer ma participation à Arbitrum?
 
-Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat d’acquisition L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat d’acquisition dans Explorer. Si
-votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
+Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat d’acquisition L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat d’acquisition dans Explorer. Si votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
 
 ### J’utilise mon contrat de vesting pour déléguer sur mainnet. Puis-je transférer mes délégations à Arbitrum?
 
-Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat de vesting L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat de vesting dans Explorer. Si
-votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
+Oui, mais si votre contrat est toujours acquis, vous ne pouvez transférer la participation que pour qu’elle soit détenue par votre contrat de vesting L2. Vous devez d’abord initialiser ce contrat L2 en transférant un solde de GRT à l’aide de l’outil de transfert de contrat de vesting dans Explorer. Si votre contrat est entièrement acquis, vous pouvez transférer votre participation à n’importe quelle adresse en L2, mais vous devez le définir au préalable et déposer des GRT pour l’outil de transfert L2 pour payer le gaz L2.
 
 ### Puis-je spécifier un bénéficiaire différent pour mon contrat de vesting sur L2?
 
diff --git a/website/pages/fr/cookbook/cosmos.mdx b/website/pages/fr/cookbook/cosmos.mdx
index d21938a729dd..ed318635f292 100644
--- a/website/pages/fr/cookbook/cosmos.mdx
+++ b/website/pages/fr/cookbook/cosmos.mdx
@@ -48,30 +48,30 @@ La définition d'un subgraph comporte trois éléments clés :
 Le manifeste du subgraph (`subgraph.yaml`) identifie les sources de données du subgraph, les déclencheurs d'intérêt et les fonctions (`handlers`) qui doivent être exécutées en réponse à ces déclencheurs. Vous trouverez ci-dessous un exemple de manifeste de subgraph pour un subgraph Cosmos :
 
 ```yaml
-version spec : 0.0.5
-description : Exemple de subgraph Cosmos
+version spec: 0.0.5
+description: Exemple de subgraph Cosmos
 schéma:
-   fichier : ./schema.graphql # lien vers le fichier de schéma
+  fichier: ./schema.graphql # lien vers le fichier de schéma
 les sources de données:
-   - genre : cosmos
-     nom : CosmosHub
-     réseau : cosmoshub-4 # Cela changera pour chaque blockchain basée sur le cosmos. Dans ce cas, l’exemple utilise le mainnet Cosmos Hub.
-     source:
-       startBlock : 0 # Requis pour Cosmos, définissez-le sur 0 pour démarrer l'indexation à partir de la genèse de la chaîne
-     cartographie :
-       Version api : 0.0.7
-       langage : wasm/assemblyscript
-       gestionnaires de blocs :
-         - handler: handleNewBlock # le nom de la fonction dans le fichier de mappage
-       Gestionnaires d'événements :
-         - event : récompenses # le type d'événement qui sera géré
-           handler: handleReward # le nom de la fonction dans le fichier de mappage
-       Gestionnaires de transactions :
-         - handler: handleTransaction # le nom de la fonction dans le fichier de mappage
-       Gestionnaires de messages :
-         - message : /cosmos.staking.v1beta1.MsgDelegate # le type d'un message
-           handler : handleMsgDelegate # le nom de la fonction dans le fichier de mappage
-       fichier : ./src/mapping.ts # lien vers le fichier avec les mappages Assemblyscript
+  - genre: cosmos
+    nom: CosmosHub
+    réseau: cosmoshub-4 # Cela changera pour chaque blockchain basée sur le cosmos. Dans ce cas, l’exemple utilise le mainnet Cosmos Hub.
+    source:
+      startBlock: 0 # Requis pour Cosmos, définissez-le sur 0 pour démarrer l'indexation à partir de la genèse de la chaîne
+    cartographie:
+      Version api: 0.0.7
+      langage: wasm/assemblyscript
+      gestionnaires de blocs:
+        - handler: handleNewBlock # le nom de la fonction dans le fichier de mappage
+      Gestionnaires d'événements:
+        - event: récompenses # le type d'événement qui sera géré
+          handler: handleReward # le nom de la fonction dans le fichier de mappage
+      Gestionnaires de transactions:
+        - handler: handleTransaction # le nom de la fonction dans le fichier de mappage
+      Gestionnaires de messages:
+        - message: /cosmos.staking.v1beta1.MsgDelegate # le type d'un message
+          handler: handleMsgDelegate # le nom de la fonction dans le fichier de mappage
+      fichier: ./src/mapping.ts # lien vers le fichier avec les mappages Assemblyscript
 ```
 
 - Les subgraphs cosmos introduisent un nouveau `type` de source de données (`cosmos`).
diff --git a/website/pages/fr/cookbook/near.mdx b/website/pages/fr/cookbook/near.mdx
index e922801be61e..cb3ed047e136 100644
--- a/website/pages/fr/cookbook/near.mdx
+++ b/website/pages/fr/cookbook/near.mdx
@@ -51,23 +51,23 @@ $ graph build # génère le Web Assembly à partir des fichiers AssemblyScript,
 Le manifeste de subgraph (`subgraph.yaml`) identifie les sources de données pour le subgraph, les déclencheurs d'intérêt et les fonctions qui doivent être exécutées en réponse à ces déclencheurs. Voici un exemple de manifeste de subgraph pour un subgraph NEAR:
 
 ```yaml
-specVersion : 0.0.2
-schema :
-  file : ./src/schema.graphql # lien vers le fichier de schéma
-dataSources :
-  - kind : near
-    network : near-mainnet
-    source :
-      account : app.good-morning.near # Cette source de données surveillera ce compte
-      startBlock : 10662188 # Requis pour NEAR
-    mapping :
-      apiVersion : 0.0.5
-      language : wasm/assemblyscript
-      blockHandlers :
-        - handler : handleNewBlock # le nom de la fonction dans le fichier de mapping
-      receiptHandlers :
-        - handler : handleReceipt # le nom de la fonction dans le fichier de mappage
-      file : ./src/mapping.ts # lien vers le fichier contenant les mappings Assemblyscript
+specVersion: 0.0.2
+schema:
+  file: ./src/schema.graphql # lien vers le fichier de schéma
+dataSources:
+  - kind: near
+    network: near-mainnet
+    source:
+      account: app.good-morning.near # Cette source de données surveillera ce compte
+      startBlock: 10662188 # Requis pour NEAR
+    mapping:
+      apiVersion: 0.0.5
+      language: wasm/assemblyscript
+      blockHandlers:
+        - handler: handleNewBlock # le nom de la fonction dans le fichier de mapping
+      receiptHandlers:
+        - handler: handleReceipt # le nom de la fonction dans le fichier de mappage
+      file: ./src/mapping.ts # lien vers le fichier contenant les mappings Assemblyscript
 ```
 
 - Les subgraphs NEAR introduisent un nouveau `type` de source de données (`near`)
@@ -77,12 +77,12 @@ dataSources :
 
 ```yaml
 comptes:
-   préfixes :
-     - application
-     - bien
-   suffixes :
-     - matin.près
-     - matin.testnet
+  préfixes:
+    - application
+    - bien
+  suffixes:
+    - matin.près
+    - matin.testnet
 ```
 
 Les fichiers de données NEAR prennent en charge deux types de gestionnaires :
@@ -258,8 +258,8 @@ Si un `compte` est spécifié, il correspondra uniquement au nom exact du compte
 
 ```yaml
 comptes:
-   suffixes :
-     - mintbase1.near
+  suffixes:
+    - mintbase1.near
 ```
 
 ### Les subgraphs NEAR peuvent-ils faire des appels de view aux comptes NEAR pendant les mappings?
diff --git a/website/pages/fr/developing/creating-a-subgraph/advanced.mdx b/website/pages/fr/developing/creating-a-subgraph/advanced.mdx
index 7416cd495bcf..9788771e2158 100644
--- a/website/pages/fr/developing/creating-a-subgraph/advanced.mdx
+++ b/website/pages/fr/developing/creating-a-subgraph/advanced.mdx
@@ -284,7 +284,7 @@ import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
 const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
 //Cet exemple de code concerne un sous-graphe de Crypto coven. Le hachage ipfs ci-dessus est un répertoire contenant les métadonnées des jetons pour toutes les NFT de l'alliance cryptographique.
 
-export function handleTransfer(event : TransferEvent) : void {
+export function handleTransfer(event: TransferEvent): void {
   let token = Token.load(event.params.tokenId.toString())
   if (!token) {
     token = new Token(event.params.tokenId.toString())
diff --git a/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx
index b96964966bb9..d5f137f2260f 100644
--- a/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/fr/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ Le(s) fichier(s) ABI doivent correspondre à votre(vos) contrat(s). Il existe pl
 
 ## Versions disponibles de SpecVersion
 
-| Version | Notes de version                                                                                                                                                         |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Ajout de la prise en charge des gestionnaires d'événement ayant accès aux reçus de transactions.                                                                         |
-|  0.0.4  | Ajout de la prise en charge du management des fonctionnalités de subgraph.                                                                                               |
+| Version | Notes de version |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Ajout de la prise en charge des gestionnaires d'événement ayant accès aux reçus de transactions. |
+| 0.0.4 | Ajout de la prise en charge du management des fonctionnalités de subgraph. |
diff --git a/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx
index cbf7c64078a3..b0c91ff4665f 100644
--- a/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/fr/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 Les scalaires suivants sont supportés dans l'API GraphQL :
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Tableau d'octets, représenté sous forme de chaîne hexadécimale. Couramment utilisé pour les hachages et adresses Ethereum.                                                                                       |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Tableau d'octets, représenté sous forme de chaîne hexadécimale. Couramment utilisé pour les hachages et adresses Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -210,7 +210,7 @@ Cette approche nécessite que les requêtes descendent vers un niveau supplémen
 query usersWithOrganizations {
   users {
     organizations {
-       # ceci est une entité UserOrganization
+      # ceci est une entité UserOrganization
       organization {
         name
       }
@@ -306,7 +306,7 @@ Dictionnaires de langues pris en charge :
 
 Algorithmes de classement:
 
-| Algorithm     | Description                                                                                           |
-| ------------- | ----------------------------------------------------------------------------------------------------- |
-| rank          | Utilisez la qualité de correspondance (0-1) de la requête en texte intégral pour trier les résultats. |
-| proximitéRang | Similar to rank but also includes the proximity of the matches.                                       |
+| Algorithm | Description |
+| --- | --- |
+| rank | Utilisez la qualité de correspondance (0-1) de la requête en texte intégral pour trier les résultats. |
+| proximitéRang | Similar to rank but also includes the proximity of the matches. |
diff --git a/website/pages/fr/developing/graph-ts/api.mdx b/website/pages/fr/developing/graph-ts/api.mdx
index 1fecf7dd1dd4..3587758f3f64 100644
--- a/website/pages/fr/developing/graph-ts/api.mdx
+++ b/website/pages/fr/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ La bibliothèque `@graphprotocol/graph-ts` fournit les API suivantes :
 
 La `apiVersion` dans le manifeste du subgraph spécifie la version de l'API de mappage exécutée par Graph Node pour un subgraph donné.
 
-| Version | Notes de version                                                                                                                                                                                                                                                                     |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  0.0.9  | Ajout de nouvelles fonctions hôtes [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                              |
-|  0.0.8  | Ajout de la validation pour l'existence des champs dans le schéma lors de l'enregistrement d'une entité.                                                                                                                                                                             |
-|  0.0.7  | Ajout des classes `TransactionReceipt` et `Log`aux types Ethereum<br />Ajout du champ `receipt` à l'objet Ethereum Event                                                                                                                                                             |
-|  0.0.6  | Ajout du champ `nonce` à l'objet Ethereum Transaction<br />Ajout de `baseFeePerGas` à l'objet Ethereum Block                                                                                                                                                                         |
-|  0.0.5  | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/release-notes/assemblyscript-migration-guide))<br />. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` |
-|  0.0.4  | Ajout du champ `functionSignature` à l'objet Ethereum SmartContractCall                                                                                                                                                                                                              |
-|  0.0.3  | Ajout du champ `from` à l'objet Ethereum Call<br />`etherem.call.address` est renommé en `ethereum.call.to`                                                                                                                                                                          |
-|  0.0.2  | Ajout du champ `input` à l'objet Ethereum Transaction                                                                                                                                                                                                                                |
+| Version | Notes de version |
+| :-: | --- |
+| 0.0.9 | Ajout de nouvelles fonctions hôtes [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Ajout de la validation pour l'existence des champs dans le schéma lors de l'enregistrement d'une entité. |
+| 0.0.7 | Ajout des classes `TransactionReceipt` et `Log`aux types Ethereum<br />Ajout du champ `receipt` à l'objet Ethereum Event |
+| 0.0.6 | Ajout du champ `nonce` à l'objet Ethereum Transaction<br />Ajout de `baseFeePerGas` à l'objet Ethereum Block |
+| 0.0.5 | AssemblyScript a été mis à niveau vers la version 0.19.10 (ceci inclut des changements importants, veuillez consulter le [`Guide de Migration`](/release-notes/assemblyscript-migration-guide))<br />. `ethereum.transaction.gasUsed` est renommé en `ethereum.transaction.gasLimit` |
+| 0.0.4 | Ajout du champ `functionSignature` à l'objet Ethereum SmartContractCall |
+| 0.0.3 | Ajout du champ `from` à l'objet Ethereum Call<br />`etherem.call.address` est renommé en `ethereum.call.to` |
+| 0.0.2 | Ajout du champ `input` à l'objet Ethereum Transaction |
 
 ### Types intégrés
 
@@ -770,44 +770,44 @@ Lorsque le type d'une valeur est certain, il peut être converti en un [type int
 
 ### Référence des conversions de types
 
-| Source(s)             | Destination          | Fonctions de conversion          |
-| --------------------- | -------------------- | -------------------------------- |
-| Address               | Bytes                | aucune                           |
-| Address               | String               | s.toHexString()                  |
-| BigDecimal            | String               | s.toString()                     |
-| BigInt                | BigDecimal           | s.toBigDecimal()                 |
-| BigInt                | String (hexadecimal) | s.toHexString() or s.toHex()     |
-| BigInt                | String (unicode)     | s.toString()                     |
-| BigInt                | i32                  | s.toI32()                        |
-| Boolean               | Boolean              | aucune                           |
-| Bytes (signé)         | BigInt               | BigInt.fromSignedBytes(s)        |
-| Bytes (non signé)     | BigInt               | BigInt.fromUnsignedBytes(s)      |
-| Bytes                 | String (hexadecimal) | s.toHexString() or s.toHex()     |
-| Bytes                 | String (unicode)     | s.toString()                     |
-| Bytes                 | String (base58)      | s.toBase58()                     |
-| Bytes                 | i32                  | s.toI32()                        |
-| Bytes                 | u32                  | s.toU32()                        |
-| Bytes                 | JSON                 | json.fromBytes(s)                |
-| int8                  | i32                  | aucune                           |
-| int32                 | i32                  | aucune                           |
-| int32                 | BigInt               | BigInt.fromI32(s)                |
-| uint24                | i32                  | aucune                           |
-| int64 - int256        | BigInt               | aucune                           |
-| uint32 - uint256      | BigInt               | aucune                           |
-| JSON                  | boolean              | s.toBool()                       |
-| JSON                  | i64                  | s.toI64()                        |
-| JSON                  | u64                  | s.toU64()                        |
-| JSON                  | f64                  | s.toF64()                        |
-| JSON                  | BigInt               | s.toBigInt()                     |
-| JSON                  | string               | s.toString()                     |
-| JSON                  | Array                | s.toArray()                      |
-| JSON                  | Object               | s.toObject()                     |
-| String                | Address              | Address.fromString(s)            |
-| Bytes                 | Address              | Address.fromBytes(s)             |
-| String                | BigInt               | BigInt.fromString(s)             |
-| String                | BigDecimal           | BigDecimal.fromString(s)         |
-| String (hexadecimal)  | Bytes                | ByteArray.fromHexString(s)       |
-| String (UTF-8)        | Bytes                | ByteArray.fromUTF8(s)            |
+| Source(s)            | Destination          | Fonctions de conversion      |
+| -------------------- | -------------------- | ---------------------------- |
+| Address              | Bytes                | aucune                       |
+| Address              | String               | s.toHexString()              |
+| BigDecimal           | String               | s.toString()                 |
+| BigInt               | BigDecimal           | s.toBigDecimal()             |
+| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex() |
+| BigInt               | String (unicode)     | s.toString()                 |
+| BigInt               | i32                  | s.toI32()                    |
+| Boolean              | Boolean              | aucune                       |
+| Bytes (signé)        | BigInt               | BigInt.fromSignedBytes(s)    |
+| Bytes (non signé)    | BigInt               | BigInt.fromUnsignedBytes(s)  |
+| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex() |
+| Bytes                | String (unicode)     | s.toString()                 |
+| Bytes                | String (base58)      | s.toBase58()                 |
+| Bytes                | i32                  | s.toI32()                    |
+| Bytes                | u32                  | s.toU32()                    |
+| Bytes                | JSON                 | json.fromBytes(s)            |
+| int8                 | i32                  | aucune                       |
+| int32                | i32                  | aucune                       |
+| int32                | BigInt               | BigInt.fromI32(s)            |
+| uint24               | i32                  | aucune                       |
+| int64 - int256       | BigInt               | aucune                       |
+| uint32 - uint256     | BigInt               | aucune                       |
+| JSON                 | boolean              | s.toBool()                   |
+| JSON                 | i64                  | s.toI64()                    |
+| JSON                 | u64                  | s.toU64()                    |
+| JSON                 | f64                  | s.toF64()                    |
+| JSON                 | BigInt               | s.toBigInt()                 |
+| JSON                 | string               | s.toString()                 |
+| JSON                 | Array                | s.toArray()                  |
+| JSON                 | Object               | s.toObject()                 |
+| String               | Address              | Address.fromString(s)        |
+| Bytes                | Address              | Address.fromBytes(s)         |
+| String               | BigInt               | BigInt.fromString(s)         |
+| String               | BigDecimal           | BigDecimal.fromString(s)     |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
 
 ### Métadonnées de la source de données
 
diff --git a/website/pages/fr/developing/unit-testing-framework.mdx b/website/pages/fr/developing/unit-testing-framework.mdx
index b0ec41e8b131..b3c5e2dde822 100644
--- a/website/pages/fr/developing/unit-testing-framework.mdx
+++ b/website/pages/fr/developing/unit-testing-framework.mdx
@@ -950,7 +950,7 @@ Les utilisateurs peuvent également simuler une panne critique, comme ceci :
 
 ```typescript
 test('Tout faire exploser', () => {
-   log.critical('Boom!')
+  log.critical('Boom!')
 })
 ```
 
@@ -1107,7 +1107,7 @@ Depuis la version `0.6.0`, il est possible de tester si une nouvelle source de d
 #### Test des modèles `ethereum/contract`
 
 ```typescript
-test('ethereum/contract dataSource creation example', () =>  {
+test('ethereum/contract dataSource creation example', () => {
   // affirme qu'aucune source de données n'est créée à partir du modèle GraphTokenLockWallet
   assert.dataSourceCount('GraphTokenLockWallet', 0)
   // Crée une nouvelle source de données GraphTokenLockWallet avec l'adresse 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
@@ -1157,7 +1157,8 @@ De même que les sources de données dynamiques de contrat, les utilisateurs peu
 ##### Exemple `subgraph.yaml`
 
 ```yaml
-...
+
+---
 templates:
   - kind: file/ipfs
     name: GraphTokenLockMetadata
@@ -1220,7 +1221,7 @@ export function handleMetadata(content: Bytes): void {
     const endTime = value.get('endTime')
     const periods = value.get('periods')
     const releaseStartTime = value.get('releaseStartTime')
-   if (startTime && endTime && periods && releaseStartTime) {
+    if (startTime && endTime && periods && releaseStartTime) {
       tokenMetadata.startTime = startTime.toBigInt()
       tokenMetadata.endTime = endTime.toBigInt()
       tokenMetadata.periods = periods.toBigInt()
@@ -1240,7 +1241,7 @@ import { handleMetadata } from '../../src/token-lock-wallet'
 import { TokenLockMetadata } from '../../generated/schema'
 import { GraphTokenLockMetadata } from '../../generated/templates'
 
-test('exemple de création de source de données file/ipfs', () =>  {
+test('exemple de création de source de données file/ipfs', () => {
   // Générer le CID de la source de données à partir du ipfsHash + chemin du fichier du ipfs
   // Par exemple QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm/example.json
   const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
@@ -1367,15 +1368,15 @@ La sortie du journal inclut la durée de l’exécution du test. Voici un exempl
 Ceci signifie que vous avez utilisé `console.log` dans votre code, ce qui n'est pas pris en charge par AssemblyScript. Veuillez envisager d'utiliser l'[API de journalisation](/developing/graph-ts/api/#logging-api)
 
 > ERREUR TS2554 : attendu ? arguments, mais j'ai eu ?.
-> 
+>
 > renvoyer le nouveau ethereum.Block (defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt) ;
-> 
+>
 > dans ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > renvoyer un nouveau ethereum.Transaction (defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt) ;
-> 
+>
 > dans ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 L'inadéquation des arguments est causée par une inadéquation entre `graph-ts` et `matchstick-as`. La meilleure façon de résoudre des problèmes comme celui-ci est de tout mettre à jour vers la dernière version publiée.
diff --git a/website/pages/fr/network/benefits.mdx b/website/pages/fr/network/benefits.mdx
index 702f6c0a5a86..d290716f01bd 100644
--- a/website/pages/fr/network/benefits.mdx
+++ b/website/pages/fr/network/benefits.mdx
@@ -27,53 +27,54 @@ Les coûts d'interrogation peuvent varier ; le coût indiqué est la moyenne au
 
 ## Utilisateur à faible volume (moins de 100 000 requêtes par mois)
 
-|        Cost Comparison         |               Auto-hébergé                |                              The Graph Network                              |
-|:------------------------------:|:-----------------------------------------:|:---------------------------------------------------------------------------:|
-|  Coût mensuel du serveur\*   |               350 $ au mois               |                                     0 $                                     |
-|        Frais de requête        |                   + 0 $                   |                                 0$ par mois                                 |
-| Temps d'ingénierie<sup>†</sup> |               400 $ au mois               | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
-|        Requêtes au mois        |        Limité aux capacités infra         |                           100 000 (Plan Gratuit)                            |
-|       Tarif par requête        |                    0 $                    |                               0$<sup>‡</sup>                                |
-|      Les infrastructures       |                Centralisée                |                                Décentralisée                                |
-|   La redondance géographique   |       750$+ par nœud complémentaire       |                                   Compris                                   |
-|     Temps de disponibilité     |                 Variable                  |                                   + 99.9%                                   |
-|    Total des coûts mensuels    | <span className="highlight-row" />+ 750 $ |                                     0 $                                     |
+| Cost Comparison | Auto-hébergé | The Graph Network |
+| :-: | :-: | :-: |
+| Coût mensuel du serveur\* | 350 $ au mois | 0 $ |
+| Frais de requête | + 0 $ | 0$ par mois |
+| Temps d'ingénierie<sup>†</sup> | 400 $ au mois | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
+| Requêtes au mois | Limité aux capacités infra | 100 000 (Plan Gratuit) |
+| Tarif par requête | 0 $ | 0$<sup>‡</sup> |
+| Les infrastructures | Centralisée | Décentralisée |
+| La redondance géographique | 750$+ par nœud complémentaire | Compris |
+| Temps de disponibilité | Variable | + 99.9% |
+| Total des coûts mensuels | <span className="highlight-row" />+ 750 $ | 0 $ |
 
 ## Utilisateur à volume moyen (~3M requêtes par mois)
 
-|      Comparaison de coût       |                Auto-hébergé                 |                              The Graph Network                              |
-|:------------------------------:|:-------------------------------------------:|:---------------------------------------------------------------------------:|
-|  Coût mensuel du serveur\*   |                350 $ au mois                |                                     0 $                                     |
-|        Frais de requête        |                500 $ au mois                |                                120$ par mois                                |
-| Temps d'ingénierie<sup>†</sup> |                800 $ au mois                | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
-|        Requêtes au mois        |         Limité aux capacités infra          |                                 ~3,000,000                                  |
-|       Tarif par requête        |                     0 $                     |                                  $0.00004                                   |
-|        L'infrastructure        |                 Centralisée                 |                                Décentralisée                                |
-|       Frais d'ingénierie       |                200 $ au mois                |                                   Compris                                   |
-|   La redondance géographique   | 1 200 $ coût total par nœud supplémentaire  |                                   Compris                                   |
-|     Temps de disponibilité     |                  Variable                   |                                   + 99.9%                                   |
-|    Total des coûts mensuels    | <span className="highlight-row" /> + 1650 $ |                                    120$                                     |
+| Comparaison de coût | Auto-hébergé | The Graph Network |
+| :-: | :-: | :-: |
+| Coût mensuel du serveur\* | 350 $ au mois | 0 $ |
+| Frais de requête | 500 $ au mois | 120$ par mois |
+| Temps d'ingénierie<sup>†</sup> | 800 $ au mois | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
+| Requêtes au mois | Limité aux capacités infra | ~3,000,000 |
+| Tarif par requête | 0 $ | $0.00004 |
+| L'infrastructure | Centralisée | Décentralisée |
+| Frais d'ingénierie | 200 $ au mois | Compris |
+| La redondance géographique | 1 200 $ coût total par nœud supplémentaire | Compris |
+| Temps de disponibilité | Variable | + 99.9% |
+| Total des coûts mensuels | <span className="highlight-row" /> + 1650 $ | 120$ |
 
 ## Utilisateur à volume élevé (~30M requêtes par mois)
 
-|     Comparaison des coûts      |                  Auto-hébergé                   |                              The Graph Network                              |
-|:------------------------------:|:-----------------------------------------------:|:---------------------------------------------------------------------------:|
-|  Coût mensuel du serveur\*   |            1100 $ au mois, par nœud             |                                     0 $                                     |
-|        Frais de requête        |                     4000 $                      |                              1 200 $ par mois                               |
-|  Nombre de nœuds obligatoires  |                       10                        |                                 Sans objet                                  |
-| Temps d'ingénierie<sup>†</sup> |             6000 $ ou plus au mois              | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
-|        Requêtes au mois        |           Limité aux capacités infra            |                                 ~30,000,000                                 |
-|       Tarif par requête        |                       0 $                       |                                  0.00004$                                   |
-|        L'infrastructure        |                   Centralisée                   |                                Décentralisée                                |
-|   La redondance géographique   | 1 200 $ de coûts totaux par nœud supplémentaire |                                   Compris                                   |
-|     Temps de disponibilité     |                    Variable                     |                                   + 99.9%                                   |
-|    Total des coûts mensuels    |  <span className="highlight-row" /> + 11 000 $  |                                   1,200$                                    |
+| Comparaison des coûts | Auto-hébergé | The Graph Network |
+| :-: | :-: | :-: |
+| Coût mensuel du serveur\* | 1100 $ au mois, par nœud | 0 $ |
+| Frais de requête | 4000 $ | 1 200 $ par mois |
+| Nombre de nœuds obligatoires | 10 | Sans objet |
+| Temps d'ingénierie<sup>†</sup> | 6000 $ ou plus au mois | Aucun, intégré au réseau avec des indexeurs distribués à l'échelle mondiale |
+| Requêtes au mois | Limité aux capacités infra | ~30,000,000 |
+| Tarif par requête | 0 $ | 0.00004$ |
+| L'infrastructure | Centralisée | Décentralisée |
+| La redondance géographique | 1 200 $ de coûts totaux par nœud supplémentaire | Compris |
+| Temps de disponibilité | Variable | + 99.9% |
+| Total des coûts mensuels | <span className="highlight-row" /> + 11 000 $ | 1,200$ |
 
 \*y compris les coûts de sauvegarde : $50-$ à 100 dollars au mois
 
 <sup>†</sup>Temps d'ingénierie basé sur une hypothèse de 200 $ de l'heure
 
-<sup>‡</sup>Reflète le coût pour le consommateur de données. Les frais de requête sont toujours payés aux Indexeurs pour les requêtes du Plan Gratuit.
+<sup>‡</sup>Reflète le coût pour le consommateur de données. Les frais de requête sont toujours payés aux Indexeurs pour
+les requêtes du Plan Gratuit.
 
 Les coûts estimés sont uniquement pour les subgraphs Ethereum Mainnet - les coûts sont encore plus élevés lorsqu'on héberge soi-même un `graph-node` sur d'autres réseaux. Certains utilisateurs peuvent avoir besoin de mettre à jour leur subgraph vers une nouvelle version. En raison des frais de gaz Ethereum, une mise à jour coûte ~50 $ au moment de la rédaction. Notez que les frais de gaz sur [Arbitrum](/arbitrum/arbitrum-faq) sont considérablement plus bas que ceux d'Ethereum mainnet.
 
diff --git a/website/pages/fr/network/delegating.mdx b/website/pages/fr/network/delegating.mdx
index de7d6558d89c..a67c4240c3f9 100644
--- a/website/pages/fr/network/delegating.mdx
+++ b/website/pages/fr/network/delegating.mdx
@@ -49,8 +49,8 @@ Chaque fois qu'un Délégateur veut se désengager, ses jetons sont soumis à un
 Si vous choisissez un Indexeur qui n'est pas fiable ou qui ne fait pas du bon travail, vous voudrez vous désengager. Cela signifie que vous perdrez beaucoup d'opportunités de gagner des récompenses, ce qui peut être aussi mauvais que de brûler des GRT. Par conséquent, il est recommandé de choisir judicieusement un Indexeur.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  !Délégation débondage](/img/Delegation-Unbonding.png) _Notez la commission de 0,5% dans l'interface utilisateur de la délégation, ainsi que la période de débondage de 28 jours.
-  de 28 jours
+  !Délégation débondage](/img/Delegation-Unbonding.png) _Notez la commission de 0,5% dans l'interface utilisateur de la
+  délégation, ainsi que la période de débondage de 28 jours. de 28 jours
 </div>
 
 ### Choisir un indexeur digne de confiance avec une rémunération équitable pour les délégués
@@ -65,7 +65,7 @@ Pour comprendre comment choisir un Indexeur fiable, vous devez comprendre les pa
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
   ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Le meilleur indexeur donne aux délégués 90 % des récompenses. Le
-   celui du milieu donne 20 % aux délégués. Celui du bas donne aux délégués environ 83 %.*
+  celui du milieu donne 20 % aux délégués. Celui du bas donne aux délégués environ 83 %.*
 </div>
 
 - **Part de Frais de Requête** - C'est comme la part de récompense d'indexation, mais elle s'applique aux gains sur les frais de requête que l'Indexeur collecte.
diff --git a/website/pages/fr/network/indexing.mdx b/website/pages/fr/network/indexing.mdx
index 55955d4a56b9..cb42d6d859be 100644
--- a/website/pages/fr/network/indexing.mdx
+++ b/website/pages/fr/network/indexing.mdx
@@ -113,11 +113,11 @@ Les indexeurs peuvent se différencier en appliquant des techniques avancées po
 - **Large** : Prêt à indexer tous les subgraphs actuellement utilisés et à répondre aux demandes pour le trafic associé.
 
 | Installation | Postgres<br />(CPUs) | Postgres<br />(mémoire en Gbs) | Postgres<br />(disque en TB) | VMs<br />(CPUs) | VMs<br />(mémoire en Gbs) |
-| ------------ |:--------------------------:|:------------------------------------:|:----------------------------------:|:---------------------:|:-------------------------------:|
-| Petit        |             4              |                  8                   |                 1                  |           4           |               16                |
-| Standard     |             8              |                  30                  |                 11                 |          12           |               48                |
-| Moyen        |             16             |                  64                  |                 2                  |          32           |               64                |
-| Large        |             72             |                 468                  |                3.5                 |          48           |                                 |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Petit | 4 | 8 | 1 | 4 | 16 |
+| Standard | 8 | 30 | 11 | 12 | 48 |
+| Moyen | 16 | 64 | 2 | 32 | 64 |
+| Large | 72 | 468 | 3.5 | 48 |  |
 
 ### Quelles sont les précautions de sécurité de base qu’un indexeur doit prendre ?
 
@@ -149,20 +149,20 @@ Remarque : Pour prendre en charge la mise à l'échelle agile, il est recommand
 
 #### Nœud de The Graph
 
-| Port | Objectif                                                         | Routes                                               | Argument CLI      | Variable d'environnement |
-| ---- | ---------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------------ |
-| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                        |
-| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                        |
-| 8020 | JSON-RPC<br />(pour gérer les déploiements)                | /                                                    | --admin-port      | -                        |
-| 8030 | API de statut d'indexation des subgraphs                         | /graphq                                              | --index-node-port | -                        |
-| 8040 | Métriques Prometheus                                             | /metrics                                             | --metrics-port    | -                        |
+| Port | Objectif | Routes | Argument CLI | Variable d'environnement |
+| --- | --- | --- | --- | --- |
+| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(pour gérer les déploiements) | / | --admin-port | - |
+| 8030 | API de statut d'indexation des subgraphs | /graphq | --index-node-port | - |
+| 8040 | Métriques Prometheus | /metrics | --metrics-port | - |
 
 #### Service d'indexation
 
-| Port | Objectif                                                                  | Routes                                                                  | Argument CLI   | Variable d'environnement |
-| ---- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ------------------------ |
-| 7600 | Serveur HTTP GraphQL<br />(pour les requêtes payantes de subgraphs) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT`   |
-| 7300 | Métriques Prometheus                                                      | /metrics                                                                | --metrics-port | -                        |
+| Port | Objectif | Routes | Argument CLI | Variable d'environnement |
+| --- | --- | --- | --- | --- |
+| 7600 | Serveur HTTP GraphQL<br />(pour les requêtes payantes de subgraphs) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Métriques Prometheus | /metrics | --metrics-port | - |
 
 #### Agent indexeur
 
diff --git a/website/pages/fr/new-chain-integration.mdx b/website/pages/fr/new-chain-integration.mdx
index 398e4770837e..3f0e6d2612d6 100644
--- a/website/pages/fr/new-chain-integration.mdx
+++ b/website/pages/fr/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/fr/operating-graph-node.mdx b/website/pages/fr/operating-graph-node.mdx
index 329f1ac72adf..252894e113a0 100644
--- a/website/pages/fr/operating-graph-node.mdx
+++ b/website/pages/fr/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Un exemple complet de configuration de Kubernetes est disponible dans le [dépô
 
 Lorsqu'il est en cours d'exécution, Graph Node expose les ports suivants :
 
-| Port | Objectif                                                         | Routes                                               | Argument CLI      | Variable d'environnement |
-| ---- | ---------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------------ |
-| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                        |
-| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs)       | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                        |
-| 8020 | JSON-RPC<br />(pour gérer les déploiements)                | /                                                    | --admin-port      | -                        |
-| 8030 | API de statut d'indexation des subgraphs                         | /graphq                                              | --index-node-port | -                        |
-| 8040 | Métriques Prometheus                                             | /metrics                                             | --metrics-port    | -                        |
+| Port | Objectif | Routes | Argument CLI | Variable d'environnement |
+| --- | --- | --- | --- | --- |
+| 8000 | Serveur HTTP GraphQL<br />(pour les requêtes de subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(pour les abonnements aux subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(pour gérer les déploiements) | / | --admin-port | - |
+| 8030 | API de statut d'indexation des subgraphs | /graphq | --index-node-port | - |
+| 8040 | Métriques Prometheus | /metrics | --metrics-port | - |
 
 > **Important** : Soyez prudent lorsque vous exposez les ports publiquement : les **ports d'administration** doivent rester verrouillés. Cela inclut le point de terminaison Graph Node JSON-RPC.
 
diff --git a/website/pages/fr/publishing/publishing-a-subgraph.mdx b/website/pages/fr/publishing/publishing-a-subgraph.mdx
index c66f02c0b12f..fba2c9221675 100644
--- a/website/pages/fr/publishing/publishing-a-subgraph.mdx
+++ b/website/pages/fr/publishing/publishing-a-subgraph.mdx
@@ -47,15 +47,15 @@ Vous pouvez uploader votre build de subgraph sur un nœud IPFS spécifique et pe
 
 ```
 USAGE
-  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url 
+  $ graph publish [SUBGRAPH-MANIFEST] [-h] [--protocol-network arbitrum-one|arbitrum-sepolia --subgraph-id <value>] [-i <value>] [--ipfs-hash <value>] [--webapp-url
      <value>]
 
 FLAGS
   -h, --help Afficher l'aide du CLI.
   -i, --ipfs=<value>      [default: https://api.thegraph.com/ipfs/api/v0] Téléchargez les résultats du build sur un nœud IPFS.
-  --ipfs-hash=<value>       Hash IPFS du manifeste du subgraph à déployer. 
+  --ipfs-hash=<value>       Hash IPFS du manifeste du subgraph à déployer.
   --protocol-network=<option> [default: arbitrum-one] Le réseau à utiliser pour le déploiement du subgraph.
-                                <options: arbitrum-one|arbitrum-sepolia> 
+                                <options: arbitrum-one|arbitrum-sepolia>
   --subgraph-id=<value>         ID du subgraph à publier.
   --webapp-url=<value>        [default: https://cli.thegraph.com/publish] URL de l'interface web que vous souhaitez utiliser pour déployer.
 
diff --git a/website/pages/fr/querying/distributed-systems.mdx b/website/pages/fr/querying/distributed-systems.mdx
index 270b55bfd86d..cc52558ba647 100644
--- a/website/pages/fr/querying/distributed-systems.mdx
+++ b/website/pages/fr/querying/distributed-systems.mdx
@@ -34,21 +34,21 @@ Le graph fournit l'API `block : { number_gte: $minBlock }`, qui garantit que la
 Nous pouvons utiliser `number_gte` pour nous assurer que le temps ne recule jamais lorsque nous interrogeons des données dans une boucle. Voici un exemple :
 
 ```javascript
-/// Met à jour la variable protocol.paused avec la dernière valeur 
+/// Met à jour la variable protocol.paused avec la dernière valeur
 /// connue dans une boucle en la récupérant en utilisant The Graph.
 async function updateProtocolPaused() {
   // Il est correct de commencer avec minBlock à 0. La requête sera servie
   // en utilisant le dernier bloc disponible. Définir minBlock à 0 revient
   // à omettre cet argument.
   let minBlock = 0
-  
+
   for (;;) {
-    // Planifie une promesse qui sera prête une fois que le prochain bloc 
+    // Planifie une promesse qui sera prête une fois que le prochain bloc
     // Ethereum sera probablement disponible.
     const nextBlock = new Promise((f) => {
       setTimeout(f, 14000)
     })
- 
+
     const query = `
         query GetProtocol($minBlock: Int!) {
             protocol(block: { number_gte: $minBlock }  id: "0") {
@@ -60,14 +60,14 @@ async function updateProtocolPaused() {
                 }
             }
         }`
-    
+
     const variables = { minBlock }
     const response = await graphql(query, variables)
     minBlock = response._meta.block.number
-    
+
     // TODO: Faites quelque chose avec les données de réponse ici au lieu de les journaliser.
     console.log(response.protocol.paused)
-    
+
     // Dort pour attendre le prochain bloc
     await nextBlock
   }
@@ -87,9 +87,9 @@ async function getDomainNames() {
   let pages = 5
   const perPage = 1000
 
-  // La première requête obtiendra la première page de résultats et obtiendra également le 
+  // La première requête obtiendra la première page de résultats et obtiendra également le
   // hachage du bloc afin que le reste des requêtes soit cohérent avec la première.
- const listDomainsQuery = `
+  const listDomainsQuery = `
     query ListDomains($perPage: Int!) {
         domains(first: $perPage) {
             name
diff --git a/website/pages/fr/querying/graphql-api.mdx b/website/pages/fr/querying/graphql-api.mdx
index d6965cc4cc87..ddc2030bdef5 100644
--- a/website/pages/fr/querying/graphql-api.mdx
+++ b/website/pages/fr/querying/graphql-api.mdx
@@ -223,7 +223,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Sucre syntaxique :** Vous pouvez simplifier la requête ci-dessus en supprimant l'opérateur `et` en passant une sous-expression séparée par des virgules.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -337,12 +337,12 @@ Les champs de requête de recherche en texte `intégral`, fournissent une Api de
 
 Opérateurs de recherche en texte intégral :
 
-| Symbole    | Opérateur   | Description                                                                                                                                            |
-| ---------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`    | `And`       | Pour combiner plusieurs termes de recherche dans un filtre pour les entités incluant tous les termes fournis                                           |
-| &#x7c;     | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx
index 619ba98b326a..49e76d908653 100644
--- a/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/fr/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Vous devrez renommer vos variables en double si vous conservez une observation de variables.
+
 ### Comparaisons nulles
+
 En effectuant la mise à niveau sur votre subgraph, vous pouvez parfois obtenir des erreurs comme celles-ci :
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Pour résoudre, vous pouvez simplement remplacer l'instruction `if` par quelque chose comme ceci :
 
 ```typescript
@@ -209,7 +213,7 @@ Dans ces cas-là, vous pouvez utiliser la fonction `changetype<T>` :
 class Bytes extends Uint8Array {}
 
 let uint8Array = new Uint8Array(2)
-changetype<Bytes>(uint8Array ) // fonctionne :)
+changetype<Bytes>(uint8Array) // fonctionne :)
 ```
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Pour résoudre ce problème, vous pouvez créer une variable pour l'accès à cette propriété afin que le compilateur puisse effectuer la vérification magique de la nullité :
 
 ```typescript
@@ -401,7 +406,7 @@ type Total @entity {
 let total = Total.load('latest')
 
 if (total === null) {
-    total = new Total('latest') // initialise déjà les propriétés non-nullables
+  total = new Total('latest') // initialise déjà les propriétés non-nullables
 }
 
 total.amount = total.amount + BigInt.fromI32(1)
@@ -483,12 +488,12 @@ Vous ne pouvez désormais plus définir de champs dans vos types qui sont des li
 
 ```graphql
 type Something @entity {
-    id: Bytes!
+  id: Bytes!
 }
 
 type MyEntity @entity {
-    id: Bytes!
-    invalidField: [Something]! # n'est plus valide
+  id: Bytes!
+  invalidField: [Something]! # n'est plus valide
 }
 ```
 
diff --git a/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx b/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx
index 567231e0bedf..62e5435c0fc3 100644
--- a/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/fr/release-notes/graphql-validations-migration-guide.mdx
@@ -103,7 +103,7 @@ query myData {
 }
 
 query myData2 {
-   # renommer la deuxième requête
+  # renommer la deuxième requête
   name
 }
 ```
@@ -158,7 +158,7 @@ _Solution:_
 
 ```graphql
 query myData($id: String) {
-   # conserver la variable pertinente (ici : `$id: String`)
+  # conserver la variable pertinente (ici : `$id: String`)
   id
   ...MyFields
 }
@@ -259,7 +259,7 @@ query {
 
 ```graphql
 # Différents arguments peuvent conduire à des données différentes,
-# donc nous ne pouvons pas supposer que les champs seront les mêmes. 
+# donc nous ne pouvons pas supposer que les champs seront les mêmes.
 query {
   dogs {
     doesKnowCommand(dogCommand: SIT)
diff --git a/website/pages/fr/sps/triggers-example.mdx b/website/pages/fr/sps/triggers-example.mdx
index 2b4aaa27a8ca..92f5cb305599 100644
--- a/website/pages/fr/sps/triggers-example.mdx
+++ b/website/pages/fr/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Conditions préalables
diff --git a/website/pages/fr/supported-network-requirements.mdx b/website/pages/fr/supported-network-requirements.mdx
index 8df2bb4bc660..40d53ab2c69b 100644
--- a/website/pages/fr/supported-network-requirements.mdx
+++ b/website/pages/fr/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Réseau    | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Réseau | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/hi/about.mdx b/website/pages/hi/about.mdx
index e2937886768f..182d6d6b068e 100644
--- a/website/pages/hi/about.mdx
+++ b/website/pages/hi/about.mdx
@@ -28,7 +28,7 @@ The Graph एक शक्तिशाली विकेंद्रीकृ
 
 ब्लॉकचेन की विशेषताएँ, जैसे अंतिमता, चेन पुनर्गठन, और अंकल ब्लॉक्स, प्रक्रिया में जटिलता जोड़ती हैं, जिससे ब्लॉकचेन डेटा से सटीक क्वेरी परिणाम प्राप्त करना समय लेने वाला और अवधारणात्मक रूप से चुनौतीपूर्ण हो जाता है।
 
-## The Graph  एक समाधान प्रदान करता है
+## The Graph एक समाधान प्रदान करता है
 
 The Graph इस चुनौती को एक विकेन्द्रीकृत प्रोटोकॉल के माध्यम से हल करता है जो ब्लॉकचेन डेटा को इंडेक्स करता है और उसकी कुशल और उच्च-प्रदर्शन वाली क्वेरी करने की सुविधा प्रदान करता है। ये एपीआई (इंडेक्स किए गए "सबग्राफ") फिर एक मानक GraphQL एपीआई के साथ क्वेरी की जा सकती हैं।
 
diff --git a/website/pages/hi/arbitrum/arbitrum-faq.mdx b/website/pages/hi/arbitrum/arbitrum-faq.mdx
index b694353d661e..885ebdc4f88f 100644
--- a/website/pages/hi/arbitrum/arbitrum-faq.mdx
+++ b/website/pages/hi/arbitrum/arbitrum-faq.mdx
@@ -6,7 +6,7 @@ Click [here](#billing-on-arbitrum-faqs) if you would like to skip to the Arbitru
 
 ## The Graph ने L2 समाधान को लागू करने का कारण क्या था?
 
- L2 पर The Graph को स्केल करके, नेटवर्क के प्रतिभागी अब निम्नलिखित लाभ उठा सकते हैं:
+L2 पर The Graph को स्केल करके, नेटवर्क के प्रतिभागी अब निम्नलिखित लाभ उठा सकते हैं:
 
 - Upwards of 26x savings on gas fees
 
@@ -47,8 +47,7 @@ L2 पर द ग्राफ़ का उपयोग करने का ल
 
 ## क्या नेटवर्क को L2 पर स्केल करने से संबंधित कोई जोखिम थे?
 
-सभी स्मार्ट कॉन्ट्रैक्ट्स का पूरी तरह से परीक्षित किया गया है।
-(https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
+सभी स्मार्ट कॉन्ट्रैक्ट्स का पूरी तरह से परीक्षित किया गया है। (https://github.com/graphprotocol/contracts/blob/main/packages/contracts/audits/OpenZeppelin/2022-07-graph-arbitrum-bridge-audit.pdf).
 
 हर चीज़ का पूरी तरह से परीक्षण किया गया है, और एक सुरक्षित और निर्बाध संक्रमण सुनिश्चित करने के लिए एक आकस्मिक योजना बनाई गई है। विवरण यहां पाया जा सकता है [here] (https://forum.thegraph.com/t/gip-0037-the-graph-arbitrum-deployment-with-linear-rewards-minted-in-l2/3551#risks-and- सुरक्षा-विचार-20).
 
diff --git a/website/pages/hi/billing.mdx b/website/pages/hi/billing.mdx
index d67ec53497ca..1462d5d49ea6 100644
--- a/website/pages/hi/billing.mdx
+++ b/website/pages/hi/billing.mdx
@@ -31,11 +31,11 @@ Subgraph users can use The Graph Token (or GRT) to pay for queries on The Graph
 
 ### GRT on Arbitrum or Ethereum
 
-The Graph का बिलिंग सिस्टम Arbitrum पर GRT को स्वीकार करता है, और उपयोगकर्ताओं को गैस के भुगतान के लिए Arbitrum  पर ETH की आवश्यकता होगी। जबकि The Graph प्रोटोकॉल Ethereum Mainnet पर शुरू हुआ, सभी गतिविधियाँ, जिसमें बिलिंग कॉन्ट्रैक्ट्स भी शामिल हैं, अब Arbitrum One पर हैं।
+The Graph का बिलिंग सिस्टम Arbitrum पर GRT को स्वीकार करता है, और उपयोगकर्ताओं को गैस के भुगतान के लिए Arbitrum पर ETH की आवश्यकता होगी। जबकि The Graph प्रोटोकॉल Ethereum Mainnet पर शुरू हुआ, सभी गतिविधियाँ, जिसमें बिलिंग कॉन्ट्रैक्ट्स भी शामिल हैं, अब Arbitrum One पर हैं।
 
 क्वेरियों के लिए भुगतान करने के लिए, आपको Arbitrum पर GRT की आवश्यकता है। इसे प्राप्त करने के लिए कुछ विभिन्न तरीके यहां दिए गए हैं:
 
-- यदि आपके पास पहले से  Ethereum पर GRT है, तो आप इसे Arbitrum पर ब्रिज कर सकते हैं। आप यह Subgraph Studio में प्रदान किए गए GRT ब्रिजिंग विकल्प के माध्यम से या निम्नलिखित में से किसी एक ब्रिज का उपयोग करके कर सकते हैं:
+- यदि आपके पास पहले से Ethereum पर GRT है, तो आप इसे Arbitrum पर ब्रिज कर सकते हैं। आप यह Subgraph Studio में प्रदान किए गए GRT ब्रिजिंग विकल्प के माध्यम से या निम्नलिखित में से किसी एक ब्रिज का उपयोग करके कर सकते हैं:
 
 - [The Arbitrum Bridge](https://bridge.arbitrum.io/?l2ChainId=42161)
 - [TransferTo](https://transferto.xyz/swap)
diff --git a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx b/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
index e4f078918c5c..cce3d8339979 100644
--- a/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
+++ b/website/pages/hi/cookbook/how-to-secure-api-keys-using-nextjs-server-components.mdx
@@ -24,7 +24,7 @@ title: कैसे सुरक्षित करें API Keys का उप
 
 ### आवश्यक शर्तें
 
--  [Subgraph Studio](https://thegraph.com/studio) से एक API कुंजी
+- [Subgraph Studio](https://thegraph.com/studio) से एक API कुंजी
 - Next.js और React का बुनियादी ज्ञान
 - एक मौजूदा Next.js प्रोजेक्ट जो App Router (https://nextjs.org/docs/app). का उपयोग करता है।
 
diff --git a/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx b/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx
index 4875006914e4..a58adda01cc3 100644
--- a/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx
+++ b/website/pages/hi/cookbook/immutable-entities-bytes-as-ids.mdx
@@ -90,7 +90,7 @@ Query:
 }
 ```
 
-प्रश्न प्रतिक्रिया: 
+प्रश्न प्रतिक्रिया:
 
 ```json
 {
@@ -146,7 +146,7 @@ Query
 }
 ```
 
-प्रश्न प्रतिक्रिया: 
+प्रश्न प्रतिक्रिया:
 
 ```json
 {
diff --git a/website/pages/hi/cookbook/subgraph-debug-forking.mdx b/website/pages/hi/cookbook/subgraph-debug-forking.mdx
index 89d0d58605ff..da72d452509e 100644
--- a/website/pages/hi/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/hi/cookbook/subgraph-debug-forking.mdx
@@ -8,7 +8,7 @@ As with many systems processing large amounts of data, The Graph's Indexers (Gra
 
 **सबग्राफ फोर्किंग** आलसी ढंग से _दूसरे_ सबग्राफ के स्टोर (आमतौर पर एक परोक्ष सबग्राफ) से इकाइयां को लाने की प्रक्रिया है।
 
-डिबगिंग के संदर्भ में, **सबग्राफ फोर्किंग** आपको ब्लॉक_X_ को सिंक-अप करने के लिए बिना प्रतीक्षा किए ब्लॉक _X_ पर अपने विफल सबग्राफ को डीबग करने की अनुमति देता है ।
+डिबगिंग के संदर्भ में, **सबग्राफ फोर्किंग** आपको ब्लॉक*X* को सिंक-अप करने के लिए बिना प्रतीक्षा किए ब्लॉक _X_ पर अपने विफल सबग्राफ को डीबग करने की अनुमति देता है ।
 
 ## क्या?! कैसे?
 
diff --git a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx b/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
index 3f07a9b3b2e4..b57efc206319 100644
--- a/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
+++ b/website/pages/hi/deploying/deploy-using-subgraph-studio.mdx
@@ -17,7 +17,7 @@ In <a href="https://thegraph.com/studio/">Subgraph Studio</a>,आप निम
 - अपना subgraph बनाएं
 - अपने subgraph को The Graph CLI का उपयोग करके डिप्लॉय करें
 - अपने 'subgraph' को 'playground' वातावरण में टेस्ट करें
-- अपने स्टेजिंग में 'subgraph' को विकास क्वेरी URL का उपयोग करके एकीकृत करें 
+- अपने स्टेजिंग में 'subgraph' को विकास क्वेरी URL का उपयोग करके एकीकृत करें
 - अपने subgraph को The Graph Network पर प्रकाशित करें
 - अपने बिलिंग को प्रबंधित करें
 
@@ -25,7 +25,7 @@ In <a href="https://thegraph.com/studio/">Subgraph Studio</a>,आप निम
 
 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' के साथ
 
diff --git a/website/pages/hi/developing/creating-a-subgraph/advanced.mdx b/website/pages/hi/developing/creating-a-subgraph/advanced.mdx
index 17ea3311f5a9..b92e6528b52f 100644
--- a/website/pages/hi/developing/creating-a-subgraph/advanced.mdx
+++ b/website/pages/hi/developing/creating-a-subgraph/advanced.mdx
@@ -521,7 +521,6 @@ calls:
 ```yaml
 calls:
   - ERC20DecimalsToken0: ERC20[event.params.token0].decimals()
-
 ```
 
 ### मौजूदा सबग्राफ पर ग्राफ्टिंग
diff --git a/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx
index d9660acfb4b2..f4ddd954e659 100644
--- a/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/hi/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is
 
 ## स्पेकवर्जन रिलीज़
 
-| संस्करण | रिलीज नोट्स                                                                                                                                                              |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है।                                                                                          |
-|  0.0.4  | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है।                                                                                          |
+| संस्करण | रिलीज नोट्स |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है। |
+| 0.0.4 | घटना हैंडलरों को लेनदेन रसीदों तक पहुंच प्रदान करने के लिए समर्थन जोड़ा गया है। |
diff --git a/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx
index a554978d786b..cc56484e1fb3 100644
--- a/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/hi/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 नीचे दिए गए स्केलर्स GraphQL API में समर्थित हैं:
 
-| प्रकार       | विवरण                                                                                                                                                                                                            |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | बाइट सरणी, एक हेक्साडेसिमल स्ट्रिंग के रूप में दर्शाया गया है। आमतौर पर एथेरियम हैश और पतों के लिए उपयोग किया जाता है।                                                                                           |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| प्रकार | विवरण |
+| --- | --- |
+| `Bytes` | बाइट सरणी, एक हेक्साडेसिमल स्ट्रिंग के रूप में दर्शाया गया है। आमतौर पर एथेरियम हैश और पतों के लिए उपयोग किया जाता है। |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -283,24 +283,24 @@ query {
 
 समर्थित भाषा शब्दकोश:
 
-| Code   | शब्दकोष    |
-| ------ | ---------- |
-| simple | General    |
-| da     | Danish     |
-| nl     | Dutch      |
-| en     | English    |
-| fi     | Finnish    |
-| fr     | French     |
-| de     | German     |
-| hu     | Hungarian  |
-| it     | Italian    |
-| no     | Norwegian  |
-| pt     | पुर्तगाली  |
-| ro     | Romanian   |
-| ru     | Russian    |
-| es     | Spanish    |
-| sv     | Swedish    |
-| tr     | Turkish    |
+| Code   | शब्दकोष   |
+| ------ | --------- |
+| simple | General   |
+| da     | Danish    |
+| nl     | Dutch     |
+| en     | English   |
+| fi     | Finnish   |
+| fr     | French    |
+| de     | German    |
+| hu     | Hungarian |
+| it     | Italian   |
+| no     | Norwegian |
+| pt     | पुर्तगाली |
+| ro     | Romanian  |
+| ru     | Russian   |
+| es     | Spanish   |
+| sv     | Swedish   |
+| tr     | Turkish   |
 
 ### रैंकिंग एल्गोरिदम
 
diff --git a/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx
index 7a554404dd2c..3afa290667f2 100644
--- a/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx
+++ b/website/pages/hi/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -20,7 +20,7 @@ subgraph मैनिफेस्ट, subgraph.yaml, उन स्मार्
 
 - कई स्मार्ट कॉन्ट्रैक्ट्स से डेटा को इंडेक्स करें (लेकिन कई नेटवर्क नहीं)।
 
-- IPFS फ़ाइलों से डेटा को डेटा स्रोत फ़ाइलें  का उपयोग करके अनुक्रमित करें।
+- IPFS फ़ाइलों से डेटा को डेटा स्रोत फ़ाइलें का उपयोग करके अनुक्रमित करें।
 
 - Add an entry for each contract that requires indexing to the `dataSources` array.
 
diff --git a/website/pages/hi/developing/developer-faqs.mdx b/website/pages/hi/developing/developer-faqs.mdx
index ec23a849d8cb..b335b8eb8867 100644
--- a/website/pages/hi/developing/developer-faqs.mdx
+++ b/website/pages/hi/developing/developer-faqs.mdx
@@ -135,7 +135,7 @@ someCollection(first: 1000, skip: <number>) { ... }
 
 ## विविध
 
-### क्या Apollo Federation  का उपयोग graph-node के ऊपर किया जा सकता है?
+### क्या Apollo Federation का उपयोग graph-node के ऊपर किया जा सकता है?
 
 Federation अभी समर्थित नहीं है। फिलहाल, आप schema stitching का उपयोग कर सकते हैं, या तो क्लाइंट पर या एक प्रॉक्सी सेवा के माध्यम से।
 
diff --git a/website/pages/hi/developing/graph-ts/api.mdx b/website/pages/hi/developing/graph-ts/api.mdx
index b43331af7860..9d914991e327 100644
--- a/website/pages/hi/developing/graph-ts/api.mdx
+++ b/website/pages/hi/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| संस्करण | रिलीज नोट्स                                                                                                                                                                                                                                   |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| संस्करण | रिलीज नोट्स |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### अंतर्निहित प्रकार
 
@@ -595,7 +595,11 @@ The `log` API includes the following functions:
 The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
 
 ```typescript
-log.info ('संदेश प्रदर्शित किया जाना है: {}, {}, {}', [value.toString (), OtherValue.toString (), 'पहले से ही एक स्ट्रिंग'])
+log.info('संदेश प्रदर्शित किया जाना है: {}, {}, {}', [
+  value.toString(),
+  OtherValue.toString(),
+  'पहले से ही एक स्ट्रिंग',
+])
 ```
 
 #### एक या अधिक मान लॉग करना
diff --git a/website/pages/hi/developing/unit-testing-framework.mdx b/website/pages/hi/developing/unit-testing-framework.mdx
index e0ef7821aec7..30433a184d2b 100644
--- a/website/pages/hi/developing/unit-testing-framework.mdx
+++ b/website/pages/hi/developing/unit-testing-framework.mdx
@@ -420,7 +420,7 @@ describe('handleUpdatedGravatars', () => {
 
 उदाहरण:
 
-प्रत्येक परीक्षण के बाद ` afterEach ` के अंदर का कोड निष्पादित होगा।
+प्रत्येक परीक्षण के बाद `afterEach` के अंदर का कोड निष्पादित होगा।
 
 ```typescript
 import { describe, test, beforeEach, afterEach } from "matchstick-as/assembly/index"
@@ -459,7 +459,7 @@ describe("handleUpdatedGravatar", () => {
 })
 ```
 
-उस वर्णन में प्रत्येक परीक्षण के बाद ` afterEach ` के अंदर का कोड निष्पादित होगा
+उस वर्णन में प्रत्येक परीक्षण के बाद `afterEach` के अंदर का कोड निष्पादित होगा
 
 ```typescript
 import { describe, test, beforeEach, afterEach } from "matchstick-as/assembly/index"
@@ -1380,15 +1380,15 @@ Global test coverage: 22.2% (2/9 handlers).
 इसका मतलब है कि आपने अपने कोड में ``console.log`\` का उपयोग किया है, जिसे AssemblyScript द्वारा सपोर्ट नहीं किया जाता है। कृपया [Logging API](/developing/graph-ts/api/#logging-api) का उपयोग करने पर विचार करें।
 
 > त्रुटि TS2554: अपेक्षित? तर्क, लेकिन मिला ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > त्रुटि TS2554: अपेक्षित? तर्क, लेकिन मिला ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 तर्कों में बेमेल `ग्राफ़-टीएस` और `मैचस्टिक-एज़` में बेमेल होने के कारण होता है। इस तरह की समस्याओं को ठीक करने का सबसे अच्छा तरीका है कि सभी चीज़ों को नवीनतम रिलीज़ किए गए संस्करण में अपडेट कर दिया जाए.
diff --git a/website/pages/hi/managing/transfer-a-subgraph.mdx b/website/pages/hi/managing/transfer-a-subgraph.mdx
index f424782f7940..fa8e363f09df 100644
--- a/website/pages/hi/managing/transfer-a-subgraph.mdx
+++ b/website/pages/hi/managing/transfer-a-subgraph.mdx
@@ -4,7 +4,7 @@ title: सबग्राफ ट्रांसफर करें
 
 विभिन्न नेटवर्क पर प्रकाशित subgraphs के लिए उस पते पर एक NFT जारी किया गया है जिसने subgraph प्रकाशित किया। NFT एक मानक ERC721 पर आधारित है, जो The Graph नेटवर्क पर खातों के बीच स्थानांतरण की सुविधा देता है।
 
-## अनुस्मारक 
+## अनुस्मारक
 
 - जो भी 'NFT' का मालिक है, वह subgraph को नियंत्रित करता है।
 - यदि मालिक 'NFT' को बेचने या स्थानांतरित करने का निर्णय लेता है, तो वे नेटवर्क पर उस subgraph को संपादित या अपडेट नहीं कर पाएंगे।
diff --git a/website/pages/hi/network/benefits.mdx b/website/pages/hi/network/benefits.mdx
index fb724441c964..72171c86bf9c 100644
--- a/website/pages/hi/network/benefits.mdx
+++ b/website/pages/hi/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|           लागत तुलना           |          स्वयं होस्ट किया गया           |                           The Graph Network                            |
-|:------------------------------:|:---------------------------------------:|:----------------------------------------------------------------------:|
-|      मासिक सर्वर लागत\*      |             $350 प्रति माह              |                                   $0                                   |
-|          पूछताछ लागत           |                   $0+                   |                              $0 per month                              |
-| इंजीनियरिंग का समय<sup>†</sup> |             $ 400 प्रति माह             | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
-|        प्रति माह प्रश्न        |        इन्फ्रा क्षमताओं तक सीमित        |                          100,000 (Free Plan)                           |
-|       लागत प्रति क्वेरी        |                   $0                    |                             $0<sup>‡</sup>                             |
-|         आधारभूत संरचना         |               केंद्रीकृत                |                             विकेन्द्रीकृत                              |
-|         भौगोलिक अतिरेक         |        $750+ प्रति अतिरिक्त नोड         |                                 शामिल                                  |
-|             अपटाइम             |                  भिन्न                  |                                 99.9%+                                 |
-|         कुल मासिक लागत         | <span className="highlight-row" />$750+ |                                   $0                                   |
+| लागत तुलना | स्वयं होस्ट किया गया | The Graph Network |
+| :-: | :-: | :-: |
+| मासिक सर्वर लागत\* | $350 प्रति माह | $0 |
+| पूछताछ लागत | $0+ | $0 per month |
+| इंजीनियरिंग का समय<sup>†</sup> | $ 400 प्रति माह | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
+| प्रति माह प्रश्न | इन्फ्रा क्षमताओं तक सीमित | 100,000 (Free Plan) |
+| लागत प्रति क्वेरी | $0 | $0<sup>‡</sup> |
+| आधारभूत संरचना | केंद्रीकृत | विकेन्द्रीकृत |
+| भौगोलिक अतिरेक | $750+ प्रति अतिरिक्त नोड | शामिल |
+| अपटाइम | भिन्न | 99.9%+ |
+| कुल मासिक लागत | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|           लागत तुलना           |            स्वयं होस्ट किया गया            |                           The Graph Network                            |
-|:------------------------------:|:------------------------------------------:|:----------------------------------------------------------------------:|
-|      मासिक सर्वर लागत\*      |               $350 प्रति माह               |                                   $0                                   |
-|          पूछताछ लागत           |              $ 500 प्रति माह               |                             $120 per month                             |
-| इंजीनियरिंग का समय<sup>†</sup> |               $800 प्रति माह               | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
-|        प्रति माह प्रश्न        |         इन्फ्रा क्षमताओं तक सीमित          |                               ~3,000,000                               |
-|       लागत प्रति क्वेरी        |                     $0                     |                                $0.00004                                |
-|         आधारभूत संरचना         |                 केंद्रीकृत                 |                             विकेन्द्रीकृत                              |
-|        इंजीनियरिंग खर्च        |              $ 200 प्रति घंटा              |                                 शामिल                                  |
-|         भौगोलिक अतिरेक         |   प्रति अतिरिक्त नोड कुल लागत में $1,200   |                                 शामिल                                  |
-|             अपटाइम             |                   भिन्न                    |                                 99.9%+                                 |
-|         कुल मासिक लागत         | <span className="highlight-row" /> $1,650+ |                                  $120                                  |
+| लागत तुलना | स्वयं होस्ट किया गया | The Graph Network |
+| :-: | :-: | :-: |
+| मासिक सर्वर लागत\* | $350 प्रति माह | $0 |
+| पूछताछ लागत | $ 500 प्रति माह | $120 per month |
+| इंजीनियरिंग का समय<sup>†</sup> | $800 प्रति माह | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
+| प्रति माह प्रश्न | इन्फ्रा क्षमताओं तक सीमित | ~3,000,000 |
+| लागत प्रति क्वेरी | $0 | $0.00004 |
+| आधारभूत संरचना | केंद्रीकृत | विकेन्द्रीकृत |
+| इंजीनियरिंग खर्च | $ 200 प्रति घंटा | शामिल |
+| भौगोलिक अतिरेक | प्रति अतिरिक्त नोड कुल लागत में $1,200 | शामिल |
+| अपटाइम | भिन्न | 99.9%+ |
+| कुल मासिक लागत | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|           लागत तुलना           |            स्वयं होस्ट किया गया             |                           The Graph Network                            |
-|:------------------------------:|:-------------------------------------------:|:----------------------------------------------------------------------:|
-|      मासिक सर्वर लागत\*      |         $1100 प्रति माह, प्रति नोड          |                                   $0                                   |
-|          पूछताछ लागत           |                    $4000                    |                            $1,200 per month                            |
-|     आवश्यक नोड्स की संख्या     |                     10                      |                             Not applicable                             |
-| इंजीनियरिंग का समय<sup>†</sup> |          $6,000 or more per month           | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
-|        प्रति माह प्रश्न        |          इन्फ्रा क्षमताओं तक सीमित          |                              ~30,000,000                               |
-|       लागत प्रति क्वेरी        |                     $0                      |                                $0.00004                                |
-|         आधारभूत संरचना         |                 केंद्रीकृत                  |                             विकेन्द्रीकृत                              |
-|         भौगोलिक अतिरेक         |   प्रति अतिरिक्त नोड कुल लागत में $1,200    |                                 शामिल                                  |
-|             अपटाइम             |                    भिन्न                    |                                 99.9%+                                 |
-|         कुल मासिक लागत         | <span className="highlight-row" /> $11,000+ |                                 $1,200                                 |
+| लागत तुलना | स्वयं होस्ट किया गया | The Graph Network |
+| :-: | :-: | :-: |
+| मासिक सर्वर लागत\* | $1100 प्रति माह, प्रति नोड | $0 |
+| पूछताछ लागत | $4000 | $1,200 per month |
+| आवश्यक नोड्स की संख्या | 10 | Not applicable |
+| इंजीनियरिंग का समय<sup>†</sup> | $6,000 or more per month | कोई नहीं, विश्व स्तर पर वितरित इंडेक्सर्स के साथ नेटवर्क में बनाया गया |
+| प्रति माह प्रश्न | इन्फ्रा क्षमताओं तक सीमित | ~30,000,000 |
+| लागत प्रति क्वेरी | $0 | $0.00004 |
+| आधारभूत संरचना | केंद्रीकृत | विकेन्द्रीकृत |
+| भौगोलिक अतिरेक | प्रति अतिरिक्त नोड कुल लागत में $1,200 | शामिल |
+| अपटाइम | भिन्न | 99.9%+ |
+| कुल मासिक लागत | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*बैकअप की लागत सहित: $50-$100 प्रति माह
 
diff --git a/website/pages/hi/network/curating.mdx b/website/pages/hi/network/curating.mdx
index 34d446b1314f..ed5965d0e5cd 100644
--- a/website/pages/hi/network/curating.mdx
+++ b/website/pages/hi/network/curating.mdx
@@ -47,7 +47,7 @@ However, it is recommended that curators leave their signaled GRT in place not o
 ## जोखिम
 
 1. क्वेरी बाजार द ग्राफ में स्वाभाविक रूप से युवा है और इसमें जोखिम है कि नवजात बाजार की गतिशीलता के कारण आपका %APY आपकी अपेक्षा से कम हो सकता है।
-2. क्यूरेशन शुल्क  - जब कोई क्यूरेटर किसी सबग्राफ़ पर GRT सिग्नल करता है, तो उसे 1% क्यूरेशन टैक्स देना होता है। यह शुल्क जला दिया जाता है।
+2. क्यूरेशन शुल्क - जब कोई क्यूरेटर किसी सबग्राफ़ पर GRT सिग्नल करता है, तो उसे 1% क्यूरेशन टैक्स देना होता है। यह शुल्क जला दिया जाता है।
 3. (Ethereum only) When curators burn their shares to withdraw GRT, the GRT valuation of the remaining shares will be reduced. Be aware that in some cases, curators may decide to burn their shares **all at once**. This situation may be common if a dapp developer stops versioning/improving and querying their subgraph or if a subgraph fails. As a result, remaining curators might only be able to withdraw a fraction of their initial GRT. For a network role with a lower risk profile, see [Delegators](/network/delegating).
 4. बग के कारण सबग्राफ विफल हो सकता है। एक विफल सबग्राफ क्वेरी शुल्क अर्जित नहीं करता है। नतीजतन, आपको तब तक इंतजार करना होगा जब तक कि डेवलपर बग को ठीक नहीं करता है और एक नया संस्करण तैनात करता है।
    - यदि आपने सबग्राफ के नवीनतम संस्करण की सदस्यता ली है, तो आपके शेयर उस नए संस्करण में स्वत: माइग्रेट हो जाएंगे। इस पर 0.5% क्यूरेशन टैक्स लगेगा।
diff --git a/website/pages/hi/network/delegating.mdx b/website/pages/hi/network/delegating.mdx
index 09c0de82002b..926c4520fc6e 100644
--- a/website/pages/hi/network/delegating.mdx
+++ b/website/pages/hi/network/delegating.mdx
@@ -49,8 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 यदि आप किसी ऐसे Indexer का चयन करते हैं जो विश्वसनीय नहीं है या अच्छा काम नहीं कर रहा है, तो आप डेलीगेट को रद्द करना चाहेंगे। इसका मतलब है कि आप पुरस्कार कमाने के कई अवसर खो देंगे, जो GRT को जलाने के समान बुरा हो सकता है। परिणामस्वरूप, यह अनुशंसा की जाती है कि आप एक Indexer का चयन समझदारी से करें।
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![डेलिगेशन अनबॉन्डिंग](/img/Delegation-Unbonding.png) _डेलीगेशन UI में 0.5% शुल्क और साथ ही 28 दिन पर ध्यान दें
-   बंधन अवधि._
+  ![डेलिगेशन अनबॉन्डिंग](/img/Delegation-Unbonding.png) _डेलीगेशन UI में 0.5% शुल्क और साथ ही 28 दिन पर ध्यान दें बंधन
+  अवधि._
 </div>
 
 ### डेलीगेटर्स के लिए उचित इनाम भुगतान के साथ एक भरोसेमंद इंडेक्सर चुनना
@@ -64,8 +64,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
   - यदि इसे 80% पर सेट किया गया है, तो एक Delegator के रूप में, आप 20% प्राप्त करेंगे।
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *शीर्ष इंडेक्सर डेलीगेटर्स को पुरस्कारों का 90% दे रहा है। 
-   बीच वाला प्रतिनिधि को 20% दे रहा है। नीचे वाला डेलिगेटरों को ~83% दे रहा है।*
+  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *शीर्ष इंडेक्सर डेलीगेटर्स को पुरस्कारों का 90% दे रहा है। बीच
+  वाला प्रतिनिधि को 20% दे रहा है। नीचे वाला डेलिगेटरों को ~83% दे रहा है।*
 </div>
 
 - **क्वेरी शुल्क कटौती** - यह बिल्कुल 'Indexing Reward Cut' जैसा है, लेकिन यह उन रिटर्न पर लागू होता है जो 'query fees' से प्राप्त होते हैं जो Indexers एकत्र करते हैं।
diff --git a/website/pages/hi/network/developing.mdx b/website/pages/hi/network/developing.mdx
index edd73ccbe18e..6c027c7e2b1c 100644
--- a/website/pages/hi/network/developing.mdx
+++ b/website/pages/hi/network/developing.mdx
@@ -15,7 +15,7 @@ The Graph पर, आप:
 
 ### GraphQL क्या है?
 
-- [GraphQL](https://graphql.org/learn/) APIs  के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है।
+- [GraphQL](https://graphql.org/learn/) APIs के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है।
 
 ### डेवलपर क्रियाएँ
 
diff --git a/website/pages/hi/network/indexing.mdx b/website/pages/hi/network/indexing.mdx
index 62544f991701..bae7b6240635 100644
--- a/website/pages/hi/network/indexing.mdx
+++ b/website/pages/hi/network/indexing.mdx
@@ -112,12 +112,12 @@ Once an allocation has been closed the rebates are available to be claimed by th
 - **माध्यम** - प्रोडक्शन इंडेक्सर प्रति सेकंड 100 सबग्राफ और 200-500 अनुरोधों का समर्थन करता है।
 - **बड़ा** - वर्तमान में उपयोग किए जाने वाले सभी सबग्राफ को अनुक्रमित करने और संबंधित ट्रैफ़िक के अनुरोधों को पूरा करने के लिए तैयार है।
 
-| Setup    | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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 |
 
 ### एक इंडेक्सर को कौन सी बुनियादी सुरक्षा सावधानियां बरतनी चाहिए?
 
@@ -149,20 +149,20 @@ Once an allocation has been closed the rebates are available to be claimed by th
 
 #### Graph Node
 
-| Port | Purpose                                                  | Routes                                               | CLI Argument      | Environment Variable |
-| ---- | -------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए)           | /                                                    | --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<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए) | / | --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<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                       | /metrics                                                                | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
@@ -559,7 +559,7 @@ graph indexer status
 
 - `ग्राफ़ अनुक्रमणिका क्रियाएँ स्वीकृत निष्पादित करती हैं` - कार्यकर्ता को स्वीकृत क्रियाओं को तुरंत निष्पादित करने के लिए बाध्य करें
 
-सभी आदेश जो आउटपुट में नियम प्रदर्शित करते हैं, समर्थित आउटपुट स्वरूपों (`तालिका`, `yaml`, और `json`) के बीच ` का उपयोग करके चुन सकते हैं - आउटपुट ` तर्क।
+सभी आदेश जो आउटपुट में नियम प्रदर्शित करते हैं, समर्थित आउटपुट स्वरूपों (`तालिका`, `yaml`, और `json`) के बीच `का उपयोग करके चुन सकते हैं - आउटपुट` तर्क।
 
 #### Indexing rules
 
@@ -623,7 +623,7 @@ graph indexer rules delete QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
 - सभी कतारबद्ध क्रियाओं को देखने के लिए इंडेक्सर `indexer-cli` का उपयोग कर सकता है
 - इंडेक्सर (या अन्य सॉफ़्टवेयर) `इंडेक्सर-क्ली` का उपयोग करके कतार में क्रियाओं को स्वीकृत या रद्द कर सकता है। स्वीकृति और रद्द करने के आदेश इनपुट के रूप में क्रिया आईडी की एक सरणी लेते हैं।
 - निष्पादन कार्यकर्ता नियमित रूप से स्वीकृत कार्यों के लिए कतार का चुनाव करता है। यह कतार से `अनुमोदित` कार्यों को पकड़ लेगा, उन्हें निष्पादित करने का प्रयास करेगा, और निष्पादन की स्थिति के आधार पर डीबी में मूल्यों को `सफलता` या `विफल< पर अपडेट करेगा। /0>.</li>
-<li>If an action is successful the worker will ensure that there is an indexing rule present that tells the agent how to manage the allocation moving forward, useful when taking manual actions while the agent is in <code>auto` or `oversight` mode.
+  <li>If an action is successful the worker will ensure that there is an indexing rule present that tells the agent how to manage the allocation moving forward, useful when taking manual actions while the agent is in <code>auto` or `oversight` mode.
 - अनुक्रमणक क्रिया निष्पादन के इतिहास को देखने के लिए क्रिया कतार की निगरानी कर सकता है और यदि आवश्यक हो तो निष्पादन विफल होने पर क्रिया आइटम को पुन: अनुमोदित और अद्यतन कर सकता है। क्रिया कतार पंक्तिबद्ध और की गई सभी कार्रवाइयों का इतिहास प्रदान करती है।
 
 डेटा मॉडल:
diff --git a/website/pages/hi/operating-graph-node.mdx b/website/pages/hi/operating-graph-node.mdx
index 706cfcb7f112..d8707dae894c 100644
--- a/website/pages/hi/operating-graph-node.mdx
+++ b/website/pages/hi/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 जब यह चल रहा होता है तो ग्राफ़ नोड निम्नलिखित पोर्ट को उजागर करता है:
 
-| Port | Purpose                                                  | Routes                                               | CLI Argument      | Environment Variable |
-| ---- | -------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए)           | /                                                    | --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<br />(सबग्राफ प्रश्नों के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(सबग्राफ सब्सक्रिप्शन के लिए) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(तैनाती के प्रबंधन के लिए) | / | --admin-port | - |
+| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
 
 > **महत्वपूर्ण**: बंदरगाहों को सार्वजनिक रूप से उजागर करने के बारे में सावधान रहें - **प्रशासन बंदरगाहों** को बंद रखा जाना चाहिए। इसमें ग्राफ़ नोड JSON-RPC समापन बिंदु शामिल है।
 
diff --git a/website/pages/hi/publishing/publishing-a-subgraph.mdx b/website/pages/hi/publishing/publishing-a-subgraph.mdx
index d851b7952e7e..dfeec280edfc 100644
--- a/website/pages/hi/publishing/publishing-a-subgraph.mdx
+++ b/website/pages/hi/publishing/publishing-a-subgraph.mdx
@@ -33,7 +33,7 @@ title: विकेंद्रीकृत नेटवर्क के लि
 
 ## Publishing from the CLI
 
-Version 0.73.0 के अनुसार, आप अपने subgraph को[` graph-cli `](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)के साथ भी publish कर सकते हैं।
+Version 0.73.0 के अनुसार, आप अपने subgraph को[`graph-cli`](https://github.com/graphprotocol/graph-tooling/tree/main/packages/cli)के साथ भी publish कर सकते हैं।
 
 1. `graph-cli` खोलें।
 2. निम्नलिखित कमांड का उपयोग करें: `graph codegen && graph build` फिर `graph publish`।
diff --git a/website/pages/hi/querying/graphql-api.mdx b/website/pages/hi/querying/graphql-api.mdx
index cc4946bed045..999a29b08e1a 100644
--- a/website/pages/hi/querying/graphql-api.mdx
+++ b/website/pages/hi/querying/graphql-api.mdx
@@ -6,7 +6,7 @@ The Graph में उपयोग किए जाने वाले GraphQL
 
 ## GraphQL क्या है?
 
-[GraphQL](https://graphql.org/learn/) APIs  के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है।
+[GraphQL](https://graphql.org/learn/) APIs के लिए एक क्वेरी भाषा और आपके मौजूदा डेटा के साथ उन क्वेरीज़ को पूरा करने के लिए एक रनटाइम। The Graph सबग्राफ को क्वेरी करने के लिए GraphQL का उपयोग करता है।
 
 GraphQL की बड़ी भूमिका को समझने के लिए, [developing](/network/developing/) और [creating a subgraph](/developing/creating-a-subgraph/) की समीक्षा करें।
 
@@ -105,7 +105,7 @@ GraphQL की बड़ी भूमिका को समझने के ल
 
 #### उदाहरण का उपयोग करना `पहले` और `छोड़ें`
 
-क्वेरी 10 ` टोकन ` इकाइयां, संग्रह की शुरुआत से 10 स्थानों से ऑफसेट:
+क्वेरी 10 `टोकन` इकाइयां, संग्रह की शुरुआत से 10 स्थानों से ऑफसेट:
 
 ```graphql
 {
@@ -221,7 +221,7 @@ This can be useful if you are looking to fetch only entities which have changed,
 ```
 
 > **सिंटैक्टिक शुगर:** आप `और` ऑपरेटर को कॉमा द्वारा अलग किए गए सब-एक्सप्रेशन को पास करके उपरोक्त क्वेरी को सरल बना सकते हैं।
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search query fields provide an expressive text search API that can be a
 
 पूर्ण पाठ खोज ऑपरेटर:
 
-| प्रतीक      | ऑपरेटर      | विवरण                                                                                                                                |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | सभी प्रदान किए गए शब्दों को शामिल करने वाली संस्थाओं के लिए एक से अधिक खोज शब्दों को फ़िल्टर में संयोजित करने के लिए                 |
-| &#x7c;      | `Or`        | या ऑपरेटर द्वारा अलग किए गए एकाधिक खोज शब्दों वाली क्वेरी सभी संस्थाओं को प्रदान की गई शर्तों में से किसी से मेल के साथ वापस कर देगी |
-| `<->` | `Follow by` | दो शब्दों के बीच की दूरी निर्दिष्ट करें।                                                                                             |
-| `:*`        | `Prefix`    | उन शब्दों को खोजने के लिए उपसर्ग खोज शब्द का उपयोग करें जिनके उपसर्ग मेल खाते हैं (2 वर्ण आवश्यक हैं।)                               |
+| प्रतीक | ऑपरेटर | विवरण |
+| --- | --- | --- |
+| `&` | `And` | सभी प्रदान किए गए शब्दों को शामिल करने वाली संस्थाओं के लिए एक से अधिक खोज शब्दों को फ़िल्टर में संयोजित करने के लिए |
+| &#x7c; | `Or` | या ऑपरेटर द्वारा अलग किए गए एकाधिक खोज शब्दों वाली क्वेरी सभी संस्थाओं को प्रदान की गई शर्तों में से किसी से मेल के साथ वापस कर देगी |
+| `<->` | `Follow by` | दो शब्दों के बीच की दूरी निर्दिष्ट करें। |
+| `:*` | `Prefix` | उन शब्दों को खोजने के लिए उपसर्ग खोज शब्द का उपयोग करें जिनके उपसर्ग मेल खाते हैं (2 वर्ण आवश्यक हैं।) |
 
 #### उदाहरण
 
diff --git a/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx b/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx
index 031b1d2dd195..6bc091a4083a 100644
--- a/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/hi/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 यदि आपके पास वेरिएबल शैडोइंग है, तो आपको अपने डुप्लिकेट वेरिएबल्स का नाम बदलने की आवश्यकता होगी।
+
 ### Null Comparisons
+
 अपने सबग्राफ पर अपग्रेड करने से, कभी-कभी आपको इस तरह की त्रुटियाँ मिल सकती हैं:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 हल करने के लिए आप केवल `if` कथन को कुछ इस तरह से बदल सकते हैं:
 
 ```typescript
@@ -283,6 +287,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
 
    let somethingOrElse: string = container.data ? container.data : "else";
 ```
+
 इस समस्या को ठीक करने के लिए, आप उस प्रॉपर्टी एक्सेस के लिए एक वेरिएबल बना सकते हैं ताकि कंपाइलर अशक्तता जांच जादू कर सके:
 
 ```typescript
diff --git a/website/pages/hi/sps/triggers-example.mdx b/website/pages/hi/sps/triggers-example.mdx
index 2f9eab3900f0..ae7347e22d72 100644
--- a/website/pages/hi/sps/triggers-example.mdx
+++ b/website/pages/hi/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "ट्यूटोरियल: Solana पर एक Substreams-शक्ति वाले Subgraph सेट करें"
+title: 'ट्यूटोरियल: Solana पर एक Substreams-शक्ति वाले Subgraph सेट करें'
 ---
 
 ## आवश्यक शर्तें
@@ -49,7 +49,7 @@ params: # Modify the param fields to meet your needs
 
 ## चरण 2: Subgraph Manifest उत्पन्न करें
 
-एक बार जब प्रोजेक्ट इनिशियलाइज़ हो जाए, Dev Container में निम्नलिखित कमांड चलाकर subgraph मैनिफेस्ट जेनरेट करें: 
+एक बार जब प्रोजेक्ट इनिशियलाइज़ हो जाए, Dev Container में निम्नलिखित कमांड चलाकर subgraph मैनिफेस्ट जेनरेट करें:
 
 ```bash
 'सबस्ट्रीम्स कोडजेन' subgraph
diff --git a/website/pages/hi/supported-network-requirements.mdx b/website/pages/hi/supported-network-requirements.mdx
index 29673e7529a7..647eda3e6651 100644
--- a/website/pages/hi/supported-network-requirements.mdx
+++ b/website/pages/hi/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| नेटवर्क   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _अंतिम बार अपडेट किया गया 22 जून 2024_    |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| नेटवर्क | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _अंतिम बार अपडेट किया गया 22 जून 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/hi/tap.mdx b/website/pages/hi/tap.mdx
index 85f9f8b123ac..ca4837de335e 100644
--- a/website/pages/hi/tap.mdx
+++ b/website/pages/hi/tap.mdx
@@ -51,13 +51,13 @@ TAP एक प्रेषक को एक प्राप्तकर्ता
 | AllocationIDTracker | `0x5B2F33d7Ca6Ec88f5586f2528f58c20843D9FE7c` | `0xAaC28a10d707bbc6e02029f1bfDAEB5084b2aD11` |
 | Escrow              | `0x8f477709eF277d4A880801D01A140a9CF88bA0d3` | `0x1e4dC4f9F95E102635D8F7ED71c5CdbFa20e2d02` |
 
-### गेटवे 
+### गेटवे
 
-| घटक               | Edge and Node Mainnet (Aribtrum 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 (Aribtrum Mainnet)      | Edge and Node Testnet (Arbitrum Sepolia)      |
+| ---------------- | --------------------------------------------- | --------------------------------------------- |
+| प्रेषक           | `0xDDE4cfFd3D9052A9cb618fC05a1Cd02be1f2F467`  | `0xC3dDf37906724732FfD748057FEBe23379b0710D`  |
+| हस्ताक्षरकर्ता   | `0xfF4B7A5EfD00Ff2EC3518D4F250A27e4c29A2211`  | `0xFb142dE83E261e43a81e9ACEADd1c66A0DB121FE`  |
+| संकेन्द्रीयकर्ता | `https://tap-aggregator.network.thegraph.com` | `https://tap-aggregator.testnet.thegraph.com` |
 
 ### Requirements
 
@@ -171,7 +171,7 @@ max_amount_willing_to_lose_grt = 20
 टिप्पणियाँ:
 
 - tap.sender_aggregator_endpoints के लिए मान gateway section (/tap/#gateway). में पाए जा सकते हैं।
-- blockchain.receipts_verifier_address के लिए मानों का उपयोग उचित तरीके से Blockchain addresses section (/tap/#contracts)  के अनुसार किया जाना चाहिए, जिसमें उचित चेन आईडी का उपयोग किया गया है।
+- blockchain.receipts_verifier_address के लिए मानों का उपयोग उचित तरीके से Blockchain addresses section (/tap/#contracts) के अनुसार किया जाना चाहिए, जिसमें उचित चेन आईडी का उपयोग किया गया है।
 
 **लॉग स्तर**
 
@@ -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) डाउनलोड कर सकते हैं और इम्पोर्ट कर सकते हैं।
 
 ### लॉन्चपैड
 
diff --git a/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx
index fd63493e4eea..bc62da7231bc 100644
--- a/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/it/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ I file ABI devono corrispondere al vostro contratto. Esistono diversi modi per o
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx
index 3445fc2a0ef9..74c9f4274cf2 100644
--- a/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/it/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Tipo         | Descrizione                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, rappresentato come una stringa esadecimale. Comunemente utilizzato per gli hash e gli indirizzi di Ethereum.                                                                                         |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Tipo | Descrizione |
+| --- | --- |
+| `Bytes` | Byte array, rappresentato come una stringa esadecimale. Comunemente utilizzato per gli hash e gli indirizzi di Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enum
 
diff --git a/website/pages/it/developing/graph-ts/api.mdx b/website/pages/it/developing/graph-ts/api.mdx
index 4edadedcff5e..502644810be8 100644
--- a/website/pages/it/developing/graph-ts/api.mdx
+++ b/website/pages/it/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ La libreria `@graphprotocol/graph-ts` fornisce le seguenti API:
 
 La `apiVersion` nel manifest del subgraph specifica la versione dell'API di mappatura che viene eseguita da the Graph Node per un dato subgraph.
 
-| Versione | Note di rilascio                                                                                                                                                                                                                                                |
-| :------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|   0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                    |
-|   0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                                    |
-|   0.0.7  | Aggiunte le classi `TransactionReceipt` e `Log` ai tipi di Ethereum<br />Aggiunto il campo `receipt` all'oggetto Ethereum Event                                                                                                                                 |
-|   0.0.6  | Aggiunto il campo `nonce` all'oggetto Ethereum Transaction<br />Aggiunto `baseFeePerGas` all'oggetto Ethereum Block                                                                                                                                             |
-|   0.0.5  | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` |
-|   0.0.4  | Aggiunto il campo `functionSignature` all'oggetto Ethereum SmartContractCall                                                                                                                                                                                    |
-|   0.0.3  | Aggiunto il campo `from` all'oggetto Ethereum Call<br />`etherem.call.address` rinominato in `ethereum.call.to`                                                                                                                                                 |
-|   0.0.2  | Aggiunto il campo `input` all'oggetto Ethereum Transaction                                                                                                                                                                                                      |
+| Versione | Note di rilascio |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Aggiunte le classi `TransactionReceipt` e `Log` ai tipi di Ethereum<br />Aggiunto il campo `receipt` all'oggetto Ethereum Event |
+| 0.0.6 | Aggiunto il campo `nonce` all'oggetto Ethereum Transaction<br />Aggiunto `baseFeePerGas` all'oggetto Ethereum Block |
+| 0.0.5 | AssemblyScript aggiornato alla versione 0.19.10 (questo include modifiche di rottura, consultare la [`Guida alla migrazione`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` rinominato in `ethereum.transaction.gasLimit` |
+| 0.0.4 | Aggiunto il campo `functionSignature` all'oggetto Ethereum SmartContractCall |
+| 0.0.3 | Aggiunto il campo `from` all'oggetto Ethereum Call<br />`etherem.call.address` rinominato in `ethereum.call.to` |
+| 0.0.2 | Aggiunto il campo `input` all'oggetto Ethereum Transaction |
 
 ### Tipi integrati
 
@@ -770,44 +770,44 @@ Quando il tipo di un valore è certo, può essere convertito in un [tipo incorpo
 
 ### Riferimento alle conversioni di tipo
 
-| Fonte(i)             | Destinazione          | Funzione di conversione          |
-| -------------------- | --------------------- | -------------------------------- |
-| Address              | Bytes                 | none                             |
-| Address              | String                | s.toHexString()                  |
-| BigDecimal           | String                | s.toString()                     |
-| BigInt               | BigDecimal            | s.toBigDecimal()                 |
-| BigInt               | String (hexadecimal)  | s.toHexString() o s.toHex()      |
-| BigInt               | String (unicode)      | s.toString()                     |
-| BigInt               | i32                   | s.toI32()                        |
-| Boolean              | Boolean               | none                             |
-| Bytes (signed)       | BigInt                | BigInt.fromSignedBytes(s)        |
-| Bytes (unsigned)     | BigInt                | BigInt.fromUnsignedBytes(s)      |
-| Bytes                | String (hexadecimal)  | s.toHexString() o s.toHex()      |
-| Bytes                | String (unicode)      | s.toString()                     |
-| Bytes                | String (base58)       | s.toBase58()                     |
-| Bytes                | i32                   | s.toI32()                        |
-| Bytes                | u32                   | s.toU32()                        |
-| Bytes                | JSON                  | json.fromBytes(s)                |
-| int8                 | i32                   | none                             |
-| int32                | i32                   | none                             |
-| int32                | BigInt                | BigInt.fromI32(s)                |
-| uint24               | i32                   | none                             |
-| int64 - int256       | BigInt                | none                             |
-| uint32 - uint256     | BigInt                | none                             |
-| JSON                 | boolean               | s.toBool()                       |
-| JSON                 | i64                   | s.toI64()                        |
-| JSON                 | u64                   | s.toU64()                        |
-| JSON                 | f64                   | s.toF64()                        |
-| JSON                 | BigInt                | s.toBigInt()                     |
-| JSON                 | string                | s.toString()                     |
-| JSON                 | Array                 | s.toArray()                      |
-| JSON                 | Object                | s.toObject()                     |
-| String               | Address               | Address.fromString(s)            |
-| Bytes                | Address               | Address.fromBytes(s)             |
-| String               | BigInt                | BigInt.fromString(s)             |
-| String               | BigDecimal            | BigDecimal.fromString(s)         |
-| String (hexadecimal) | Bytes                 | ByteArray.fromHexString(s)       |
-| String (UTF-8)       | Bytes                 | ByteArray.fromUTF8(s)            |
+| Fonte(i)             | Destinazione         | Funzione di conversione     |
+| -------------------- | -------------------- | --------------------------- |
+| Address              | Bytes                | none                        |
+| Address              | String               | s.toHexString()             |
+| BigDecimal           | String               | s.toString()                |
+| BigInt               | BigDecimal           | s.toBigDecimal()            |
+| BigInt               | String (hexadecimal) | s.toHexString() o s.toHex() |
+| BigInt               | String (unicode)     | s.toString()                |
+| BigInt               | i32                  | s.toI32()                   |
+| Boolean              | Boolean              | none                        |
+| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)   |
+| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s) |
+| Bytes                | String (hexadecimal) | s.toHexString() o s.toHex() |
+| Bytes                | String (unicode)     | s.toString()                |
+| Bytes                | String (base58)      | s.toBase58()                |
+| Bytes                | i32                  | s.toI32()                   |
+| Bytes                | u32                  | s.toU32()                   |
+| Bytes                | JSON                 | json.fromBytes(s)           |
+| int8                 | i32                  | none                        |
+| int32                | i32                  | none                        |
+| int32                | BigInt               | BigInt.fromI32(s)           |
+| uint24               | i32                  | none                        |
+| int64 - int256       | BigInt               | none                        |
+| uint32 - uint256     | BigInt               | none                        |
+| JSON                 | boolean              | s.toBool()                  |
+| JSON                 | i64                  | s.toI64()                   |
+| JSON                 | u64                  | s.toU64()                   |
+| JSON                 | f64                  | s.toF64()                   |
+| JSON                 | BigInt               | s.toBigInt()                |
+| JSON                 | string               | s.toString()                |
+| JSON                 | Array                | s.toArray()                 |
+| JSON                 | Object               | s.toObject()                |
+| String               | Address              | Address.fromString(s)       |
+| Bytes                | Address              | Address.fromBytes(s)        |
+| String               | BigInt               | BigInt.fromString(s)        |
+| String               | BigDecimal           | BigDecimal.fromString(s)    |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)  |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)       |
 
 ### Metadati della Data Source
 
diff --git a/website/pages/it/developing/unit-testing-framework.mdx b/website/pages/it/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/it/developing/unit-testing-framework.mdx
+++ b/website/pages/it/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/it/network/benefits.mdx b/website/pages/it/network/benefits.mdx
index 304e99031863..19b319509f8a 100644
--- a/website/pages/it/network/benefits.mdx
+++ b/website/pages/it/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|          Confronto costi           |               Self Hosted               |                               The Graph Network                               |
-|:----------------------------------:|:---------------------------------------:|:-----------------------------------------------------------------------------:|
-|    Costo mensile del server\*    |              $350 al mese               |                                      $0                                       |
-|           Costi di query           |                   $0+                   |                                 $0 per month                                  |
-| Tempo di progettazione<sup>†</sup> |              $400 al mese               | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
-|           Query al mese            |     Limitato alle capacità di infra     |                              100,000 (Free Plan)                              |
-|          Costo per query           |                   $0                    |                                $0<sup>‡</sup>                                 |
-|           Infrastruttura           |              Centralizzato              |                                Decentralizzato                                |
-|       Ridondanza geografica        |        $750+ per nodo aggiuntivo        |                                    Incluso                                    |
-|         Tempo di attività          |                Variabile                |                                    99.9%+                                     |
-|        Costo totale mensile        | <span className="highlight-row" />$750+ |                                      $0                                       |
+| Confronto costi | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Costo mensile del server\* | $350 al mese | $0 |
+| Costi di query | $0+ | $0 per month |
+| Tempo di progettazione<sup>†</sup> | $400 al mese | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
+| Query al mese | Limitato alle capacità di infra | 100,000 (Free Plan) |
+| Costo per query | $0 | $0<sup>‡</sup> |
+| Infrastruttura | Centralizzato | Decentralizzato |
+| Ridondanza geografica | $750+ per nodo aggiuntivo | Incluso |
+| Tempo di attività | Variabile | 99.9%+ |
+| Costo totale mensile | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|        Confronto dei costi         |                Self Hosted                 |                               The Graph Network                               |
-|:----------------------------------:|:------------------------------------------:|:-----------------------------------------------------------------------------:|
-|    Costo mensile del server\*    |                $350 al mese                |                                      $0                                       |
-|           Costi di query           |                $500 al mese                |                                $120 per month                                 |
-| Tempo di progettazione<sup>†</sup> |                $800 al mese                | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
-|           Query al mese            | Limitato alle capacità dell'infrastruttura |                                  ~3,000,000                                   |
-|          Costo per query           |                     $0                     |                                   $0.00004                                    |
-|           Infrastruttura           |               Centralizzato                |                                Decentralizzato                                |
-|        Costi di ingegneria         |                $200 all'ora                |                                    Incluso                                    |
-|       Ridondanza geografica        | $1.200 di costi totali per nodo aggiuntivo |                                    Incluso                                    |
-|         Tempo di attività          |                 Variabile                  |                                    99.9%+                                     |
-|        Costo totale mensile        | <span className="highlight-row" /> $1,650+ |                                     $120                                      |
+| Confronto dei costi | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Costo mensile del server\* | $350 al mese | $0 |
+| Costi di query | $500 al mese | $120 per month |
+| Tempo di progettazione<sup>†</sup> | $800 al mese | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
+| Query al mese | Limitato alle capacità dell'infrastruttura | ~3,000,000 |
+| Costo per query | $0 | $0.00004 |
+| Infrastruttura | Centralizzato | Decentralizzato |
+| Costi di ingegneria | $200 all'ora | Incluso |
+| Ridondanza geografica | $1.200 di costi totali per nodo aggiuntivo | Incluso |
+| Tempo di attività | Variabile | 99.9%+ |
+| Costo totale mensile | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|          Confronto costi           |                 Self Hosted                 |                               The Graph Network                               |
-|:----------------------------------:|:-------------------------------------------:|:-----------------------------------------------------------------------------:|
-|    Costo mensile del server\*    |           $1100 al mese, per nodo           |                                      $0                                       |
-|           Costi di query           |                    $4000                    |                               $1,200 per month                                |
-|      Numero di nodi necessari      |                     10                      |                                Non applicabile                                |
-| Tempo di progettazione<sup>†</sup> |            $6.000 o più al mese             | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
-|           Query al mese            |       Limitato alle capacità di infra       |                                  ~30,000,000                                  |
-|          Costo per query           |                     $0                      |                                   $0.00004                                    |
-|           Infrastruttura           |                Centralizzato                |                                Decentralizzato                                |
-|       Ridondanza geografica        | $1.200 di costi totali per nodo aggiuntivo  |                                    Incluso                                    |
-|         Tempo di attività          |                  Variabile                  |                                    99.9%+                                     |
-|        Costo totale mensile        | <span className="highlight-row" /> $11,000+ |                                    $1,200                                     |
+| Confronto costi | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Costo mensile del server\* | $1100 al mese, per nodo | $0 |
+| Costi di query | $4000 | $1,200 per month |
+| Numero di nodi necessari | 10 | Non applicabile |
+| Tempo di progettazione<sup>†</sup> | $6.000 o più al mese | Nessuno, integrato nella rete con indicizzatori distribuiti a livello globale |
+| Query al mese | Limitato alle capacità di infra | ~30,000,000 |
+| Costo per query | $0 | $0.00004 |
+| Infrastruttura | Centralizzato | Decentralizzato |
+| Ridondanza geografica | $1.200 di costi totali per nodo aggiuntivo | Incluso |
+| Tempo di attività | Variabile | 99.9%+ |
+| Costo totale mensile | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*inclusi i costi per il backup: $50-$100 al mese
 
diff --git a/website/pages/it/network/delegating.mdx b/website/pages/it/network/delegating.mdx
index d5c86e5ecf43..e7d832347433 100644
--- a/website/pages/it/network/delegating.mdx
+++ b/website/pages/it/network/delegating.mdx
@@ -49,8 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Sblocco di Delegator](/img/Delegation-Unbonding.png) _Nota la commissione del 0,5% nel UI della delegazione, così come il periodo di sblocco di 28 giorni.
-  periodo di sblocco._
+  ![Sblocco di Delegator](/img/Delegation-Unbonding.png) _Nota la commissione del 0,5% nel UI della delegazione, così
+  come il periodo di sblocco di 28 giorni. periodo di sblocco._
 </div>
 
 ### Scegliere un Indexer affidabile con una giusta ricompensa per i Delegator
@@ -64,8 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Taglio delle ricompense dell'indicizzazione](/img/Indexing-Reward-Cut.png) *Il top Indexer sta dando ai Delegator il 90% delle ricompense. Il
-  centrale dà ai Delegator il 20%. Quello in basso dà ai Delegator ~83%.*
+  ![Taglio delle ricompense dell'indicizzazione](/img/Indexing-Reward-Cut.png) *Il top Indexer sta dando ai Delegator il
+  90% delle ricompense. Il centrale dà ai Delegator il 20%. Quello in basso dà ai Delegator ~83%.*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/it/network/indexing.mdx b/website/pages/it/network/indexing.mdx
index 183041694bb7..3b449dc021fa 100644
--- a/website/pages/it/network/indexing.mdx
+++ b/website/pages/it/network/indexing.mdx
@@ -112,12 +112,12 @@ Gli Indexer possono differenziarsi applicando tecniche avanzate per prendere dec
 - **Medio** - Indexer di produzione che supporta 100 subgraph e 200-500 richieste al secondo.
 - **Grande** - È pronto a indicizzare tutti i subgraph attualmente utilizzati e a servire le richieste per il relativo traffico.
 
-| Setup    | Postgres<br />(CPUs) | Postgres<br />(memoria in GBs) | Postgres<br />(disco in TBs) | VMs<br />(CPUs) | VMs<br />(memoria in GBs) |
-| -------- |:--------------------------:|:------------------------------------:|:----------------------------------:|:---------------------:|:-------------------------------:|
-| Piccolo  |             4              |                  8                   |                 1                  |           4           |               16                |
-| Standard |             8              |                  30                  |                 1                  |          12           |               48                |
-| Medio    |             16             |                  64                  |                 2                  |          32           |               64                |
-| Grande   |             72             |                 468                  |                3.5                 |          48           |               184               |
+| Setup | Postgres<br />(CPUs) | Postgres<br />(memoria in GBs) | Postgres<br />(disco in TBs) | VMs<br />(CPUs) | VMs<br />(memoria in GBs) |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Piccolo | 4 | 8 | 1 | 4 | 16 |
+| Standard | 8 | 30 | 1 | 12 | 48 |
+| Medio | 16 | 64 | 2 | 32 | 64 |
+| Grande | 72 | 468 | 3.5 | 48 | 184 |
 
 ### Quali sono le precauzioni di base per la sicurezza che un Indexer dovrebbe adottare?
 
@@ -149,20 +149,20 @@ Nota: Per supportare una scalabilità agile, si consiglia di separare le attivit
 
 #### Graph Node
 
-| Porta | Obiettivo                                                 | Routes                                               | Argomento CLI     | Variabile d'ambiente |
-| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000  | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001  | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020  | JSON-RPC<br />(per la gestione dei deployment)      | /                                                    | --admin-port      | -                    |
-| 8030  | Subgraph indexing status API                              | /graphql                                             | --index-node-port | -                    |
-| 8040  | Metriche di Prometheus                                    | /metrics                                             | --metrics-port    | -                    |
+| Porta | Obiettivo | Routes | Argomento CLI | Variabile d'ambiente |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(per la gestione dei deployment) | / | --admin-port | - |
+| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
+| 8040 | Metriche di Prometheus | /metrics | --metrics-port | - |
 
 #### Servizio Indexer
 
-| Porta | Obiettivo                                                             | Routes                                                                  | Argomento CLI  | Variabile d'ambiente   |
-| ----- | --------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600  | GraphQL HTTP server<br />(per le query di subgraph a pagamento) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300  | Metriche di Prometheus                                                | /metrics                                                                | --metrics-port | -                      |
+| Porta | Obiettivo | Routes | Argomento CLI | Variabile d'ambiente |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(per le query di subgraph a pagamento) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Metriche di Prometheus | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/it/new-chain-integration.mdx b/website/pages/it/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/it/new-chain-integration.mdx
+++ b/website/pages/it/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/it/operating-graph-node.mdx b/website/pages/it/operating-graph-node.mdx
index 276c3022ec6c..b3b3ca24e204 100644
--- a/website/pages/it/operating-graph-node.mdx
+++ b/website/pages/it/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Un esempio completo di configurazione Kubernetes si trova nel [repository indexe
 
 Quando è in funzione, Graph Node espone le seguenti porte:
 
-| Porta | Obiettivo                                                 | Routes                                               | Argomento CLI     | Variabile d'ambiente |
-| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000  | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001  | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020  | JSON-RPC<br />(per la gestione dei deployment)      | /                                                    | --admin-port      | -                    |
-| 8030  | Subgraph indexing status API                              | /graphql                                             | --index-node-port | -                    |
-| 8040  | Metriche di Prometheus                                    | /metrics                                             | --metrics-port    | -                    |
+| Porta | Obiettivo | Routes | Argomento CLI | Variabile d'ambiente |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(per le query di subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(per le sottoscrizioni ai subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(per la gestione dei deployment) | / | --admin-port | - |
+| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
+| 8040 | Metriche di Prometheus | /metrics | --metrics-port | - |
 
 > **Importante**: fare attenzione a esporre le porte pubblicamente - le porte di **amministrazione** devono essere tenute sotto chiave. Questo include l'endpoint JSON-RPC del Graph Node.
 
diff --git a/website/pages/it/querying/graphql-api.mdx b/website/pages/it/querying/graphql-api.mdx
index 4c89c5b31f13..39369363a1d5 100644
--- a/website/pages/it/querying/graphql-api.mdx
+++ b/website/pages/it/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** Si può semplificare la query precedente eliminando l'operatore `and` passando una sottoespressione separata da virgole.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Le query di ricerca fulltext hanno un campo obbligatorio, `text`, per fornire i
 
 Operatori di ricerca fulltext:
 
-| Simbolo     | Operatore   | Descrizione                                                                                                                               |
-| ----------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
-| `&`     | `And`       | Per combinare più termini di ricerca in un filtro per le entità che includono tutti i termini forniti                                     |
-| &#x7c;      | `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.                                                                                                     |
-| `:*`        | `Prefisso`  | 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 |
+| &#x7c; | `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. |
+| `:*` | `Prefisso` | Utilizzare il termine di ricerca del prefisso per trovare le parole il cui prefisso corrisponde (sono richiesti 2 caratteri.) |
 
 #### Esempi
 
diff --git a/website/pages/it/release-notes/assemblyscript-migration-guide.mdx b/website/pages/it/release-notes/assemblyscript-migration-guide.mdx
index 64cbf23decf7..b6bd7ecc38d2 100644
--- a/website/pages/it/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/it/release-notes/assemblyscript-migration-guide.mdx
@@ -59,7 +59,7 @@ dataSources:
 2. Aggiornare il `graph-cli` in uso alla versione `ultima` eseguendo:
 
 ```bash
-# se è installato globalmente 
+# se è installato globalmente
 npm install --global @graphprotocol/graph-cli@latest
 
 # o nel proprio subgraph, se è una dipendenza di dev
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 È necessario rinominare le variabili duplicate se si dispone di un'ombreggiatura delle variabili.
+
 ### Confronti nulli
+
 Eseguendo l'aggiornamento sul subgraph, a volte si possono ottenere errori come questi:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Per risolvere il problema è sufficiente modificare l'istruzione `if` in qualcosa di simile:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Per risolvere questo problema, si può creare una variabile per l'accesso alla proprietà, in modo che il compilatore possa fare la magia del controllo di annullabilità:
 
 ```typescript
diff --git a/website/pages/it/sps/triggers-example.mdx b/website/pages/it/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/it/sps/triggers-example.mdx
+++ b/website/pages/it/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/it/supported-network-requirements.mdx b/website/pages/it/supported-network-requirements.mdx
index 88be77e74cc8..7eed955d1013 100644
--- a/website/pages/it/supported-network-requirements.mdx
+++ b/website/pages/it/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| La rete   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| La rete | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/ja/cookbook/subgraph-debug-forking.mdx b/website/pages/ja/cookbook/subgraph-debug-forking.mdx
index 6fbb5070e2ec..a18cf73d17b7 100644
--- a/website/pages/ja/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/ja/cookbook/subgraph-debug-forking.mdx
@@ -6,9 +6,9 @@ As with many systems processing large amounts of data, The Graph's Indexers (Gra
 
 ## さて、それは何でしょうか？
 
-**サブグラフのフォーク**とは、_他_のサブグラフのストア(通常はリモート) からエンティティをフェッチするプロセスです。
+**サブグラフのフォーク**とは、*他*のサブグラフのストア(通常はリモート) からエンティティをフェッチするプロセスです。
 
-デバッグの文脈では、**サブグラフのフォーク**により、ブロック_X_への同期を待つことなく、ブロック_X_で失敗したサブグラフのデバッグを行うことができます。
+デバッグの文脈では、**サブグラフのフォーク**により、ブロック*X*への同期を待つことなく、ブロック*X*で失敗したサブグラフのデバッグを行うことができます。
 
 ## その方法は？
 
@@ -69,7 +69,7 @@ Oops, how unfortunate, when I deploy my perfect looking subgraph to [Subgraph St
 
 回答：
 
-1. `fork-base`は「ベース」URLで、_subgraph id_が追加されたときのURL (`<fork-base>/<subgraph-id>`) はサブグラフのストアに対する有効な GraphQL endpoint であることを示します。
+1. `fork-base`は「ベース」URLで、*subgraph id*が追加されたときのURL (`<fork-base>/<subgraph-id>`) はサブグラフのストアに対する有効な GraphQL endpoint であることを示します。
 2. フォーキングは簡単であり煩雑な手間はありません
 
 ```bash
diff --git a/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx
index 9934e852df3a..80ecfac7d53c 100644
--- a/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/ja/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ ABI ファイルは、契約内容と一致している必要があります。A
 
 ## SpecVersion Releases
 
-| バージョン | リリースノート                                                                                                                                                                  |
-| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| バージョン | リリースノート |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
 | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
-| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx
index 17d9779c58f6..dca410c2b319 100644
--- a/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/ja/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| タイプ          | 説明書き                                                                                                                                                                                                             |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte 配列で、16 進数の文字列で表されます。Ethereum のハッシュやアドレスによく使われます。                                                                                                                                                            |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| タイプ | 説明書き |
+| --- | --- |
+| `Bytes` | Byte 配列で、16 進数の文字列で表されます。Ethereum のハッシュやアドレスによく使われます。 |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -284,29 +284,29 @@ query {
 サポートされている言語の辞書:
 
 | Code   | 辞書         |
-| ------ | ---------- |
-| simple | General    |
-| da     | Danish     |
-| nl     | Dutch      |
-| en     | English    |
-| fi     | Finnish    |
-| fr     | French     |
-| de     | German     |
-| hu     | Hungarian  |
-| it     | Italian    |
-| no     | Norwegian  |
-| pt     | ポルトガル語     |
-| ro     | Romanian   |
-| ru     | Russian    |
-| es     | Spanish    |
-| sv     | Swedish    |
-| tr     | Turkish    |
+| ------ | ------------ |
+| simple | General      |
+| da     | Danish       |
+| nl     | Dutch        |
+| en     | English      |
+| fi     | Finnish      |
+| fr     | French       |
+| de     | German       |
+| hu     | Hungarian    |
+| it     | Italian      |
+| no     | Norwegian    |
+| pt     | ポルトガル語 |
+| ro     | Romanian     |
+| ru     | Russian      |
+| es     | Spanish      |
+| sv     | Swedish      |
+| tr     | Turkish      |
 
 ### ランキングアルゴリズム
 
 サポートされている結果の順序付けのアルゴリズム:
 
-| Algorithm     | Description                                                             |
-| ------------- | ----------------------------------------------------------------------- |
-| rank          | フルテキストクエリのマッチ品質 (0-1) を使用して結果を並べ替えます。                                   |
-| proximityRank | Similar to rank but also includes the proximity of the matches.         |
+| Algorithm     | Description                                                         |
+| ------------- | ------------------------------------------------------------------- |
+| rank          | フルテキストクエリのマッチ品質 (0-1) を使用して結果を並べ替えます。 |
+| proximityRank | Similar to rank but also includes the proximity of the matches.     |
diff --git a/website/pages/ja/developing/graph-ts/api.mdx b/website/pages/ja/developing/graph-ts/api.mdx
index cea9a55eb75c..e6f0d323fd82 100644
--- a/website/pages/ja/developing/graph-ts/api.mdx
+++ b/website/pages/ja/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ Since language mappings are written in AssemblyScript, it is useful to review th
 
 サブグラフマニフェストapiVersionは、特定のサブグラフのマッピングAPIバージョンを指定します。このバージョンは、Graph Nodeによって実行されます。
 
-| バージョン | リリースノート                                                                                                                                                                                                                                                                 |
-| :---: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                            |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                                            |
-| 0.0.7 | Ethereum タイプに `TransactionReceipt` と `Log` クラスを追加<br /> Ethereum Event オブジェクトに `receipt` フィールドを追加。                                                                                                                                                                      |
-| 0.0.6 | Ethereum Transactionオブジェクトに`nonce`フィールドを追加<br /> Ethereum Blockオブジェクトに`baseFeePerGas`を追加。                                                                                                                                                                               |
+| バージョン | リリースノート |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Ethereum タイプに `TransactionReceipt` と `Log` クラスを追加<br /> Ethereum Event オブジェクトに `receipt` フィールドを追加。 |
+| 0.0.6 | Ethereum Transactionオブジェクトに`nonce`フィールドを追加<br /> Ethereum Blockオブジェクトに`baseFeePerGas`を追加。 |
 | 0.0.5 | AssemblyScriptはバージョン0.19.10にアップグレードされました（このバージョンアップには変更点が含まれていますので <a href="/release-notes/assemblyscript-migration-guide"><code>Migration Guide</code></a>) をご覧ください）。 <br /><code>ethereum.transaction.gasUsed</code>の名前が<code>ethereum.transaction.gasLimit</code>に変更 |
-| 0.0.4 | Ethereum SmartContractCall オブジェクトにfunctionSignatureフィールドを追加                                                                                                                                                                                                             |
-| 0.0.3 | イーサリアムコールオブジェクトに`from`フィールドを追加<br />`etherem.call.address`を`ethereum.call.to`に変更。                                                                                                                                                                                       |
-| 0.0.2 | Ethereum Transaction オブジェクトに inputフィールドを追加                                                                                                                                                                                                                              |
+| 0.0.4 | Ethereum SmartContractCall オブジェクトにfunctionSignatureフィールドを追加 |
+| 0.0.3 | イーサリアムコールオブジェクトに`from`フィールドを追加<br />`etherem.call.address`を`ethereum.call.to`に変更。 |
+| 0.0.2 | Ethereum Transaction オブジェクトに inputフィールドを追加 |
 
 ### 組み込み型
 
@@ -286,7 +286,7 @@ The store API facilitates the retrieval of entities that were created or updated
 - For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
-let id =event.transaction.hash // または ID が構築される方法
+let id = event.transaction.hash // または ID が構築される方法
 let transfer = Transfer.loadInBlock(id)
 if (transfer == null) {
   transfer = 新しい転送(id)
@@ -770,44 +770,44 @@ if (value.kind == JSONValueKind.BOOL) {
 
 ### タイプ 変換参照
 
-| Source(s)            | Destination          | Conversion function              |
-| -------------------- | -------------------- | -------------------------------- |
-| Address              | Bytes                | none                             |
-| Address              | String               | s.toHexString()                  |
-| BigDecimal           | String               | s.toString()                     |
-| BigInt               | BigDecimal           | s.toBigDecimal()                 |
-| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex()     |
-| BigInt               | String (unicode)     | s.toString()                     |
-| BigInt               | i32                  | s.toI32()                        |
-| Boolean              | Boolean              | none                             |
-| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)        |
-| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)      |
-| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex()     |
-| Bytes                | String (unicode)     | s.toString()                     |
-| Bytes                | String (base58)      | s.toBase58()                     |
-| Bytes                | i32                  | s.toI32()                        |
-| Bytes                | u32                  | s.toU32()                        |
-| Bytes                | JSON                 | json.fromBytes(s)                |
-| int8                 | i32                  | none                             |
-| int32                | i32                  | none                             |
-| int32                | BigInt               | Bigint.fromI32(s)                |
-| uint24               | i32                  | none                             |
-| int64 - int256       | BigInt               | none                             |
-| uint32 - uint256     | BigInt               | none                             |
-| JSON                 | boolean              | s.toBool()                       |
-| JSON                 | i64                  | s.toI64()                        |
-| JSON                 | u64                  | s.toU64()                        |
-| JSON                 | f64                  | s.toF64()                        |
-| JSON                 | BigInt               | s.toBigInt()                     |
-| JSON                 | string               | s.toString()                     |
-| JSON                 | Array                | s.toArray()                      |
-| JSON                 | Object               | s.toObject()                     |
-| String               | Address              | Address.fromString(s)            |
-| Bytes                | Address              | Address.fromString(s)            |
-| String               | BigInt               | BigDecimal.fromString(s)         |
-| String               | BigDecimal           | BigDecimal.fromString(s)         |
-| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)       |
-| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)            |
+| Source(s)            | Destination          | Conversion function          |
+| -------------------- | -------------------- | ---------------------------- |
+| Address              | Bytes                | none                         |
+| Address              | String               | s.toHexString()              |
+| BigDecimal           | String               | s.toString()                 |
+| BigInt               | BigDecimal           | s.toBigDecimal()             |
+| BigInt               | String (hexadecimal) | s.toHexString() or s.toHex() |
+| BigInt               | String (unicode)     | s.toString()                 |
+| BigInt               | i32                  | s.toI32()                    |
+| Boolean              | Boolean              | none                         |
+| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
+| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)  |
+| Bytes                | String (hexadecimal) | s.toHexString() or s.toHex() |
+| Bytes                | String (unicode)     | s.toString()                 |
+| Bytes                | String (base58)      | s.toBase58()                 |
+| Bytes                | i32                  | s.toI32()                    |
+| Bytes                | u32                  | s.toU32()                    |
+| Bytes                | JSON                 | json.fromBytes(s)            |
+| int8                 | i32                  | none                         |
+| int32                | i32                  | none                         |
+| int32                | BigInt               | Bigint.fromI32(s)            |
+| uint24               | i32                  | none                         |
+| int64 - int256       | BigInt               | none                         |
+| uint32 - uint256     | BigInt               | none                         |
+| JSON                 | boolean              | s.toBool()                   |
+| JSON                 | i64                  | s.toI64()                    |
+| JSON                 | u64                  | s.toU64()                    |
+| JSON                 | f64                  | s.toF64()                    |
+| JSON                 | BigInt               | s.toBigInt()                 |
+| JSON                 | string               | s.toString()                 |
+| JSON                 | Array                | s.toArray()                  |
+| JSON                 | Object               | s.toObject()                 |
+| String               | Address              | Address.fromString(s)        |
+| Bytes                | Address              | Address.fromString(s)        |
+| String               | BigInt               | BigDecimal.fromString(s)     |
+| String               | BigDecimal           | BigDecimal.fromString(s)     |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
 
 ### データソースのメタデータ
 
diff --git a/website/pages/ja/developing/unit-testing-framework.mdx b/website/pages/ja/developing/unit-testing-framework.mdx
index 89cbd8222458..8e20b4fe8312 100644
--- a/website/pages/ja/developing/unit-testing-framework.mdx
+++ b/website/pages/ja/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ Global test coverage: 22.2% (2/9 handlers).
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: 期待された引数は?
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: 期待された引数は?
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 引数の不一致は、`graph-ts`と`matchstick-as`の不一致によって起こります。このような問題を解決する最善の方法は、すべてを最新のリリース版にアップデートすることです。
diff --git a/website/pages/ja/network/benefits.mdx b/website/pages/ja/network/benefits.mdx
index 7869ee86e955..da4b2d00900b 100644
--- a/website/pages/ja/network/benefits.mdx
+++ b/website/pages/ja/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|          コスト比較          |                 セルフホスト                  |              グラフネットワーク              |
-|:-----------------------:|:---------------------------------------:|:-----------------------------------:|
-|         月額サーバー代         |                 $350/月                  |                 $0                  |
-|         クエリコスト          |                   $0+                   |            $0 per month             |
-| エンジニアリングタイム<sup>†</sup> |                 $400/月                  | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
-|         月ごとのクエリ         |                インフラ機能に限定                |         100,000 (Free Plan)         |
-|        クエリごとのコスト        |                   $0                    |           $0<sup>‡</sup>            |
-|       インフラストラクチャ        |                  集中管理型                  |                 分散型                 |
-|         地理的な冗長性         |             追加1ノードにつき$750+              |                含まれる                 |
-|         アップタイム          |                 バリエーション                 |               99.9%+                |
-|         月額費用合計          | <span className="highlight-row" />$750+ |                 $0                  |
+| コスト比較 | セルフホスト | グラフネットワーク |
+| :-: | :-: | :-: |
+| 月額サーバー代 | $350/月 | $0 |
+| クエリコスト | $0+ | $0 per month |
+| エンジニアリングタイム<sup>†</sup> | $400/月 | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
+| 月ごとのクエリ | インフラ機能に限定 | 100,000 (Free Plan) |
+| クエリごとのコスト | $0 | $0<sup>‡</sup> |
+| インフラストラクチャ | 集中管理型 | 分散型 |
+| 地理的な冗長性 | 追加1ノードにつき$750+ | 含まれる |
+| アップタイム | バリエーション | 99.9%+ |
+| 月額費用合計 | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|          コスト比較          |                   セルフホスト                   |              グラフネットワーク              |
-|:-----------------------:|:------------------------------------------:|:-----------------------------------:|
-|         月額サーバー代         |                   $350/月                   |                 $0                  |
-|         クエリコスト          |                   $500/月                   |           $120 per month            |
-| エンジニアリングタイム<sup>†</sup> |                   $800/月                   | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
-|         月ごとのクエリ         |                 インフラ機能に限定                  |             ~3,000,000              |
-|        クエリごとのコスト        |                     $0                     |              $0.00004               |
-|       インフラストラクチャ        |                   中央管理型                    |                 分散型                 |
-|       エンジニアリングコスト       |                   $200/時                   |                含まれる                 |
-|         地理的な冗長性         |            ノード追加1台につき合計1,200ドル             |                含まれる                 |
-|         アップタイム          |                     変動                     |               99.9%+                |
-|         月額費用合計          | <span className="highlight-row" /> $1,650+ |                $120                 |
+| コスト比較 | セルフホスト | グラフネットワーク |
+| :-: | :-: | :-: |
+| 月額サーバー代 | $350/月 | $0 |
+| クエリコスト | $500/月 | $120 per month |
+| エンジニアリングタイム<sup>†</sup> | $800/月 | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
+| 月ごとのクエリ | インフラ機能に限定 | ~3,000,000 |
+| クエリごとのコスト | $0 | $0.00004 |
+| インフラストラクチャ | 中央管理型 | 分散型 |
+| エンジニアリングコスト | $200/時 | 含まれる |
+| 地理的な冗長性 | ノード追加1台につき合計1,200ドル | 含まれる |
+| アップタイム | 変動 | 99.9%+ |
+| 月額費用合計 | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|          コスト比較          |                   セルフホスト                    |              グラフネットワーク              |
-|:-----------------------:|:-------------------------------------------:|:-----------------------------------:|
-|         月額サーバー代         |               $1100/月（ノードごと）                |                 $0                  |
-|         クエリコスト          |                    $4000                    |          $1,200 per month           |
-|         必要ノード数          |                     10                      |                該当なし                 |
-| エンジニアリングタイム<sup>†</sup> |                  $6,000/月                   | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
-|         月ごとのクエリ         |                  インフラ機能に限定                  |             ~30,000,000             |
-|        クエリごとのコスト        |                     $0                      |              $0.00004               |
-|       インフラストラクチャ        |                    集中管理型                    |                 分散型                 |
-|         地理的な冗長性         |             ノード追加1台につき合計1,200ドル             |                含まれる                 |
-|         アップタイム          |                     変動                      |               99.9%+                |
-|         月額費用合計          | <span className="highlight-row" /> $11,000+ |               $1,200                |
+| コスト比較 | セルフホスト | グラフネットワーク |
+| :-: | :-: | :-: |
+| 月額サーバー代 | $1100/月（ノードごと） | $0 |
+| クエリコスト | $4000 | $1,200 per month |
+| 必要ノード数 | 10 | 該当なし |
+| エンジニアリングタイム<sup>†</sup> | $6,000/月 | なし/ グローバルに分散されたインデクサーでネットワークに組み込まれる |
+| 月ごとのクエリ | インフラ機能に限定 | ~30,000,000 |
+| クエリごとのコスト | $0 | $0.00004 |
+| インフラストラクチャ | 集中管理型 | 分散型 |
+| 地理的な冗長性 | ノード追加1台につき合計1,200ドル | 含まれる |
+| アップタイム | 変動 | 99.9%+ |
+| 月額費用合計 | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*バックアップ費用含む：月額$50〜$100
 
diff --git a/website/pages/ja/network/indexing.mdx b/website/pages/ja/network/indexing.mdx
index a1202e884ecc..54d5a7c19f23 100644
--- a/website/pages/ja/network/indexing.mdx
+++ b/website/pages/ja/network/indexing.mdx
@@ -112,12 +112,12 @@ Use Etherscan to call `getRewards()`:
 - **Medium** - 100 個のサブグラフと 1 秒あたり 200 ～ 500 のリクエストをサポートするプロダクションインデクサー
 - **Large** - 現在使用されているすべてのサブグラフのインデックスを作成し、関連するトラフィックのリクエストに対応します
 
-| Setup    | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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 |
 
 ### インデクサーが取るべきセキュリティ対策は？
 
@@ -149,20 +149,20 @@ Use Etherscan to call `getRewards()`:
 
 #### グラフノード
 
-| Port | Purpose                                                 | Routes                                                 | CLI Argument      | Environment Variable |
-| ---- | ------------------------------------------------------- | ------------------------------------------------------ | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC <br /> (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 <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC <br /> (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 <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                           | /metrics                                                                    | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server <br /> (for paid subgraph queries) | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
@@ -730,10 +730,10 @@ default => 0.1 * $SYSTEM_LOAD;
 
 上記のモデルを使用したクエリのコスト計算の例:
 
-| クエリ                                                                          | 価格      |
+| クエリ                                                                       | 価格    |
 | ---------------------------------------------------------------------------- | ------- |
 | &#123; pairs(skip: 5000) &#123; id &#125; &#125;                             | 0.5 GRT |
-| &#123; トークン &#123; シンボル &#125; &#125;                                        | 0.1 GRT |
+| &#123; トークン &#123; シンボル &#125; &#125;                                | 0.1 GRT |
 | &#123; pairs(skip: 5000) &#123; id &#125; tokens &#123; symbol &#125; &#125; | 0.6 GRT |
 
 #### コストモデルの適用
diff --git a/website/pages/ja/new-chain-integration.mdx b/website/pages/ja/new-chain-integration.mdx
index 76d085dc6ea8..ce4d66cccdc7 100644
--- a/website/pages/ja/new-chain-integration.mdx
+++ b/website/pages/ja/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/ja/operating-graph-node.mdx b/website/pages/ja/operating-graph-node.mdx
index 71da764773e6..cb9e4f14e8f3 100644
--- a/website/pages/ja/operating-graph-node.mdx
+++ b/website/pages/ja/operating-graph-node.mdx
@@ -26,7 +26,7 @@ title: オペレーティンググラフノード
 
 ### IPFSノード
 
-IPFS ノード（バージョン  未満） - サブグラフのデプロイメタデータは IPFS ネットワーク上に保存されます。 グラフノードは、サブグラフのデプロイ時に主に IPFS ノードにアクセスし、サブグラフマニフェストと全てのリンクファイルを取得します。 ネットワーク・インデクサーは独自の IPFS ノードをホストする必要はありません。 ネットワーク用の IPFS ノードは、https://ipfs.network.thegraph.com でホストされています。
+IPFS ノード（バージョン 未満） - サブグラフのデプロイメタデータは IPFS ネットワーク上に保存されます。 グラフノードは、サブグラフのデプロイ時に主に IPFS ノードにアクセスし、サブグラフマニフェストと全てのリンクファイルを取得します。 ネットワーク・インデクサーは独自の IPFS ノードをホストする必要はありません。 ネットワーク用の IPFS ノードは、https://ipfs.network.thegraph.com でホストされています。
 
 ### Prometheus メトリクスサーバー
 
@@ -77,13 +77,13 @@ Kubernetesの完全な設定例は、[indexerリポジトリ](https://github.com
 
 グラフノードは起動時に以下のポートを公開します。
 
-| Port | Purpose                                                 | Routes                                                 | CLI Argument      | Environment Variable |
-| ---- | ------------------------------------------------------- | ------------------------------------------------------ | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS <br /> (for subgraph subscriptions)    | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC <br /> (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 <br /> (for subgraph queries) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS <br /> (for subgraph subscriptions) | /subgraphs/id/... <br /> /subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC <br /> (for managing deployments) | / | --admin-port | - |
+| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
 
 > **重要**: ポートを公に公開する場合は注意してください。**管理ポート**はロックしておく必要があります。ノードの JSON-RPC エンドポイント
 
diff --git a/website/pages/ja/querying/graphql-api.mdx b/website/pages/ja/querying/graphql-api.mdx
index 839a9bff35f4..2c8ec74321ed 100644
--- a/website/pages/ja/querying/graphql-api.mdx
+++ b/website/pages/ja/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **シンタックス シュガー:** コンマで区切られた部分式を渡すことで `and` 演算子を削除することで、上記のクエリを簡素化できます。
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ The result of such a query will not change over time, i.e., querying at a certai
 
 全文検索演算子:
 
-| シンボル        | オペレーター      | 説明書き                                                      |
-| ----------- | ----------- | --------------------------------------------------------- |
-| `&`     | `と`         | 複数の検索語を組み合わせて、指定したすべての検索語を含むエンティティをフィルタリングします。            |
-| &#x7c;      | `Or`        | 複数の検索語をオペレーターで区切って検索すると、指定した語のいずれかにマッチするすべてのエンティティが返されます。 |
-| `<->` | `Follow by` | 2 つの単語の間の距離を指定します。                                        |
-| `:*`        | `プレフィックス`   | プレフィックス検索語を使って、プレフィックスが一致する単語を検索します（2 文字必要）               |
+| シンボル | オペレーター | 説明書き |
+| --- | --- | --- |
+| `&` | `と` | 複数の検索語を組み合わせて、指定したすべての検索語を含むエンティティをフィルタリングします。 |
+| &#x7c; | `Or` | 複数の検索語をオペレーターで区切って検索すると、指定した語のいずれかにマッチするすべてのエンティティが返されます。 |
+| `<->` | `Follow by` | 2 つの単語の間の距離を指定します。 |
+| `:*` | `プレフィックス` | プレフィックス検索語を使って、プレフィックスが一致する単語を検索します（2 文字必要） |
 
 #### 例
 
diff --git a/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx
index 82a7d23de3f8..766fbb6c80a3 100644
--- a/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ja/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 変数シャドウイングを行っていた場合は、重複する変数の名前を変更する必要があります。
+
 ### Null 比較
+
 サブグラフのアップグレードを行うと、時々以下のようなエラーが発生することがあります。
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 解決するには、 `if` 文を以下のように変更するだけです。
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 この問題を解決するには、そのプロパティアクセスのための変数を作成して、コンパイラが nullability check のマジックを行うようにします。
 
 ```typescript
diff --git a/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx
index 9a8bcf34625f..b004e14d9f98 100644
--- a/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/ja/release-notes/graphql-validations-migration-guide.mdx
@@ -521,7 +521,7 @@ query {
 }
 ```
 
-_注: `@stream`、`@live`、`@defer` はサポートされていません。
+\_注: `@stream`、`@live`、`@defer` はサポートされていません。
 
 **ディレクティブは、この場所で 1 回だけ使用できます (#UniqueDirectivesPerLocationRule)**
 
diff --git a/website/pages/ja/sps/triggers-example.mdx b/website/pages/ja/sps/triggers-example.mdx
index 7c513edec723..b547721bc3c7 100644
--- a/website/pages/ja/sps/triggers-example.mdx
+++ b/website/pages/ja/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## 前提条件
diff --git a/website/pages/ja/supported-network-requirements.mdx b/website/pages/ja/supported-network-requirements.mdx
index 99ceda419e06..6aa0c0caa16f 100644
--- a/website/pages/ja/supported-network-requirements.mdx
+++ b/website/pages/ja/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| ネットワーク    | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| ネットワーク | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx b/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx
index 602b2a2c3aa2..de12152a1f00 100644
--- a/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx
+++ b/website/pages/ko/arbitrum/l2-transfer-tools-faq.mdx
@@ -22,8 +22,7 @@ The exception is with smart contract wallets like multisigs: these are smart con
 
 ### 만약 7일 안에 이체를 완료하지 못하면 어떻게 되나요?
 
-L2 전송 도구는 Arbitrum의 기본 메커니즘을 사용하여 L1에서 L2로 메시지를 보냅니다. 이 메커니즘은 "재시도 가능한 티켓"이라고 하며 Arbitrum GRT 브리지를 포함한 모든 네이티브 토큰 브리지를 사용하여 사용됩니다. 재시도 가능한 티켓에 대해 자세히 읽을 수 있습니다 [Arbitrum 문서] 
-(https://docs.arbitrum.io/arbos/l1-to-l2-messaging).
+L2 전송 도구는 Arbitrum의 기본 메커니즘을 사용하여 L1에서 L2로 메시지를 보냅니다. 이 메커니즘은 "재시도 가능한 티켓"이라고 하며 Arbitrum GRT 브리지를 포함한 모든 네이티브 토큰 브리지를 사용하여 사용됩니다. 재시도 가능한 티켓에 대해 자세히 읽을 수 있습니다 [Arbitrum 문서] (https://docs.arbitrum.io/arbos/l1-to-l2-messaging).
 
 자산(하위 그래프, 스테이크, 위임 또는 큐레이션) 을 L2로 이전하면 L2에서 재시도 가능한 티켓을 생성하는 Arbitrum GRT 브리지를 통해 메시지가 전송됩니다. 전송 도구에는 거래에 일부 ETH 값이 포함되어 있으며, 이는 1) 티켓 생성 비용을 지불하고 2) L2에서 티켓을 실행하기 위해 가스 비용을 지불하는 데 사용됩니다. 그러나 티켓이 L2에서 실행될 준비가 될 때까지 가스 가격이 시간에 따라 달라질 수 있으므로 이 자동 실행 시도가 실패할 수 있습니다. 그런 일이 발생하면 Arbitrum 브릿지는 재시도 가능한 티켓을 최대 7일 동안 유지하며 누구나 티켓 "사용"을 재시도할 수 있습니다(Arbitrum에 브릿지된 일부 ETH가 있는 지갑이 필요함).
 
@@ -41,8 +40,6 @@ If you have the L1 transaction hash (which you can find by looking at the recent
 
 <VideoEmbed youtube="R8_vz4lx2Co" />
 
-
-
 1. 이더리움 메인넷에서 전송 시작
 
 2. 확인을 위해 20분 정도 기다리세요
diff --git a/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx
index 5897ae02b134..282c68973a8a 100644
--- a/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/ko/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/ko/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/ko/developing/graph-ts/api.mdx b/website/pages/ko/developing/graph-ts/api.mdx
index 8fc1f4b48b61..6a0c4e208b99 100644
--- a/website/pages/ko/developing/graph-ts/api.mdx
+++ b/website/pages/ko/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/ko/developing/unit-testing-framework.mdx b/website/pages/ko/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/ko/developing/unit-testing-framework.mdx
+++ b/website/pages/ko/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/ko/network/benefits.mdx b/website/pages/ko/network/benefits.mdx
index 4fd17e17727d..80e18ef87c62 100644
--- a/website/pages/ko/network/benefits.mdx
+++ b/website/pages/ko/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                         The Graph 네트워크                          |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|        Infrastructure        |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | The Graph 네트워크 |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                         The Graph 네트워크                          |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|        Infrastructure        |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | The Graph 네트워크 |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                         The Graph 네트워크                          |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | The Graph 네트워크 |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/ko/network/indexing.mdx b/website/pages/ko/network/indexing.mdx
index 0eb017b5be3f..a6844c2da009 100644
--- a/website/pages/ko/network/indexing.mdx
+++ b/website/pages/ko/network/indexing.mdx
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/ko/new-chain-integration.mdx b/website/pages/ko/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/ko/new-chain-integration.mdx
+++ b/website/pages/ko/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/ko/operating-graph-node.mdx b/website/pages/ko/operating-graph-node.mdx
index fb3d538f952a..dbbfcd5fc545 100644
--- a/website/pages/ko/operating-graph-node.mdx
+++ b/website/pages/ko/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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.
 
diff --git a/website/pages/ko/querying/graphql-api.mdx b/website/pages/ko/querying/graphql-api.mdx
index d8671e53a77c..3dd70fc7b004 100644
--- a/website/pages/ko/querying/graphql-api.mdx
+++ b/website/pages/ko/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Description                                                                                                                          |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx
index 17224699570d..85f6903a6c69 100644
--- a/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ko/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/ko/sps/triggers-example.mdx b/website/pages/ko/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/ko/sps/triggers-example.mdx
+++ b/website/pages/ko/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/ko/supported-network-requirements.mdx b/website/pages/ko/supported-network-requirements.mdx
index afbf755c0a5a..df15ef48d762 100644
--- a/website/pages/ko/supported-network-requirements.mdx
+++ b/website/pages/ko/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx
index 4489fad1955b..7c50a40e48fd 100644
--- a/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/mr/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| आवृत्ती | रिलीझ नोट्स                                                                                                                                                              |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| आवृत्ती | रिलीझ नोट्स |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx
index 5d567ca32ddc..57d5ceb7ecf7 100644
--- a/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/mr/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| प्रकार       | वर्णन                                                                                                                                                                                                            |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| प्रकार | वर्णन |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### एनम्स
 
@@ -283,30 +283,30 @@ query {
 
 समर्थित भाषा शब्दकोश:
 
-| Code   | शब्दकोश    |
-| ------ | ---------- |
-| सोपे   | General    |
-| da     | Danish     |
-| nl     | Dutch      |
-| en     | English    |
-| fi     | Finnish    |
-| fr     | French     |
-| de     | German     |
-| hu     | Hungarian  |
-| it     | Italian    |
-| no     | Norwegian  |
-| pt     | पोर्तुगीज  |
-| ro     | Romanian   |
-| ru     | Russian    |
-| es     | Spanish    |
-| sv     | Swedish    |
-| tr     | Turkish    |
+| Code | शब्दकोश   |
+| ---- | --------- |
+| सोपे | General   |
+| da   | Danish    |
+| nl   | Dutch     |
+| en   | English   |
+| fi   | Finnish   |
+| fr   | French    |
+| de   | German    |
+| hu   | Hungarian |
+| it   | Italian   |
+| no   | Norwegian |
+| pt   | पोर्तुगीज |
+| ro   | Romanian  |
+| ru   | Russian   |
+| es   | Spanish   |
+| sv   | Swedish   |
+| tr   | Turkish   |
 
 ### रँकिंग अल्गोरिदम
 
 परिणाम ऑर्डर करण्यासाठी समर्थित अल्गोरिदम:
 
-| Algorithm     | Description                                                             |
-| ------------- | ----------------------------------------------------------------------- |
-| rank          | निकाल ऑर्डर करण्यासाठी फुलटेक्स्ट क्वेरीची जुळणी गुणवत्ता (0-1) वापरा.  |
-| proximityRank | Similar to rank but also includes the proximity of the matches.         |
+| Algorithm     | Description                                                            |
+| ------------- | ---------------------------------------------------------------------- |
+| rank          | निकाल ऑर्डर करण्यासाठी फुलटेक्स्ट क्वेरीची जुळणी गुणवत्ता (0-1) वापरा. |
+| proximityRank | Similar to rank but also includes the proximity of the matches.        |
diff --git a/website/pages/mr/developing/graph-ts/api.mdx b/website/pages/mr/developing/graph-ts/api.mdx
index 36c6c0e9db2d..1ab6b8e6fad8 100644
--- a/website/pages/mr/developing/graph-ts/api.mdx
+++ b/website/pages/mr/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| आवृत्ती | रिलीझ नोट्स                                                                                                                                                                                                                                   |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| आवृत्ती | रिलीझ नोट्स |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### अंगभूत प्रकार
 
diff --git a/website/pages/mr/developing/unit-testing-framework.mdx b/website/pages/mr/developing/unit-testing-framework.mdx
index 00db6cc5372c..86ac5cbcd673 100644
--- a/website/pages/mr/developing/unit-testing-framework.mdx
+++ b/website/pages/mr/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ ___ ___ _ _ _ _ _
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > त्रुटी TS2554: अपेक्षित आहे? युक्तिवाद, पण मिळाले?.
-> 
+>
 > नवीन ethereum.Transaction परत करा(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 `graph-ts` आणि `matchstick-as` मधील जुळत नसल्यामुळे वितर्कांमधील जुळत नाही. यासारख्या समस्यांचे निराकरण करण्याचा सर्वोत्तम मार्ग म्हणजे नवीनतम रिलीझ केलेल्या आवृत्तीवर सर्वकाही अद्यतनित करणे.
diff --git a/website/pages/mr/network/benefits.mdx b/website/pages/mr/network/benefits.mdx
index 95d7187a2039..50102fc70729 100644
--- a/website/pages/mr/network/benefits.mdx
+++ b/website/pages/mr/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|        खर्चाची तुलना         |           स्वत: होस्ट केलेले            |                               आलेख नेटवर्क                               |
-|:----------------------------:|:---------------------------------------:|:------------------------------------------------------------------------:|
-|    मासिक सर्व्हर खर्च\*    |               दरमहा $350                |                                    $0                                    |
-|         क्वेरी खर्च          |                   $0+                   |                               $0 per month                               |
-| अभियांत्रिकी वेळ<sup>†</sup> |               दरमहा $400                | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
-|      प्रति महिना प्रश्न      |      इन्फ्रा क्षमतांपुरती मर्यादित      |                           100,000 (Free Plan)                            |
-|      प्रति क्वेरी खर्च       |                   $0                    |                              $0<sup>‡</sup>                              |
-|        पायाभूत सुविधा        |               केंद्रीकृत                |                                विकेंद्रित                                |
-|       भौगोलिक रिडंडंसी       |        प्रति अतिरिक्त नोड $750+         |                                 समाविष्ट                                 |
-|            अपटाइम            |                  बदलते                  |                                  99.9%+                                  |
-|       एकूण मासिक खर्च        | <span className="highlight-row" />$750+ |                                    $0                                    |
+| खर्चाची तुलना | स्वत: होस्ट केलेले | आलेख नेटवर्क |
+| :-: | :-: | :-: |
+| मासिक सर्व्हर खर्च\* | दरमहा $350 | $0 |
+| क्वेरी खर्च | $0+ | $0 per month |
+| अभियांत्रिकी वेळ<sup>†</sup> | दरमहा $400 | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
+| प्रति महिना प्रश्न | इन्फ्रा क्षमतांपुरती मर्यादित | 100,000 (Free Plan) |
+| प्रति क्वेरी खर्च | $0 | $0<sup>‡</sup> |
+| पायाभूत सुविधा | केंद्रीकृत | विकेंद्रित |
+| भौगोलिक रिडंडंसी | प्रति अतिरिक्त नोड $750+ | समाविष्ट |
+| अपटाइम | बदलते | 99.9%+ |
+| एकूण मासिक खर्च | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|        खर्चाची तुलना         |             स्वत: होस्ट केलेले             |                               आलेख नेटवर्क                               |
-|:----------------------------:|:------------------------------------------:|:------------------------------------------------------------------------:|
-|    मासिक सर्व्हर खर्च\*    |                 दरमहा $350                 |                                    $0                                    |
-|         क्वेरी खर्च          |                 दरमहा $500                 |                              $120 per month                              |
-| अभियांत्रिकी वेळ<sup>†</sup> |                 दरमहा $800                 | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
-|      प्रति महिना प्रश्न      |       इन्फ्रा क्षमतांपुरती मर्यादित        |                                ~3,000,000                                |
-|      प्रति क्वेरी खर्च       |                     $0                     |                                 $0.00004                                 |
-|        पायाभूत सुविधा        |                 केंद्रीकृत                 |                                विकेंद्रित                                |
-|      अभियांत्रिकी खर्च       |               $200 प्रति तास               |                                 समाविष्ट                                 |
-|       भौगोलिक रिडंडंसी       |   प्रति अतिरिक्त नोड एकूण खर्चात $1,200    |                                 समाविष्ट                                 |
-|            अपटाइम            |                   बदलते                    |                                  99.9%+                                  |
-|       एकूण मासिक खर्च        | <span className="highlight-row" /> $1,650+ |                                   $120                                   |
+| खर्चाची तुलना | स्वत: होस्ट केलेले | आलेख नेटवर्क |
+| :-: | :-: | :-: |
+| मासिक सर्व्हर खर्च\* | दरमहा $350 | $0 |
+| क्वेरी खर्च | दरमहा $500 | $120 per month |
+| अभियांत्रिकी वेळ<sup>†</sup> | दरमहा $800 | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
+| प्रति महिना प्रश्न | इन्फ्रा क्षमतांपुरती मर्यादित | ~3,000,000 |
+| प्रति क्वेरी खर्च | $0 | $0.00004 |
+| पायाभूत सुविधा | केंद्रीकृत | विकेंद्रित |
+| अभियांत्रिकी खर्च | $200 प्रति तास | समाविष्ट |
+| भौगोलिक रिडंडंसी | प्रति अतिरिक्त नोड एकूण खर्चात $1,200 | समाविष्ट |
+| अपटाइम | बदलते | 99.9%+ |
+| एकूण मासिक खर्च | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|        खर्चाची तुलना         |             स्वत: होस्ट केलेले              |                               आलेख नेटवर्क                               |
-|:----------------------------:|:-------------------------------------------:|:------------------------------------------------------------------------:|
-|    मासिक सर्व्हर खर्च\*    |        प्रति नोड, प्रति महिना $1100         |                                    $0                                    |
-|         क्वेरी खर्च          |                    $4000                    |                             $1,200 per month                             |
-|    आवश्यक नोड्सची संख्या     |                     10                      |                                लागू नाही                                 |
-| अभियांत्रिकी वेळ<sup>†</sup> |           दरमहा $6,000 किंवा अधिक           | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
-|      प्रति महिना प्रश्न      |        इन्फ्रा क्षमतांपुरती मर्यादित        |                               ~30,000,000                                |
-|      प्रति क्वेरी खर्च       |                     $0                      |                                 $0.00004                                 |
-|        पायाभूत सुविधा        |                 केंद्रीकृत                  |                                विकेंद्रित                                |
-|       भौगोलिक रिडंडंसी       |    प्रति अतिरिक्त नोड एकूण खर्चात $1,200    |                                 समाविष्ट                                 |
-|            अपटाइम            |                    बदलते                    |                                  99.9%+                                  |
-|       एकूण मासिक खर्च        | <span className="highlight-row" /> $11,000+ |                                  $1,200                                  |
+| खर्चाची तुलना | स्वत: होस्ट केलेले | आलेख नेटवर्क |
+| :-: | :-: | :-: |
+| मासिक सर्व्हर खर्च\* | प्रति नोड, प्रति महिना $1100 | $0 |
+| क्वेरी खर्च | $4000 | $1,200 per month |
+| आवश्यक नोड्सची संख्या | 10 | लागू नाही |
+| अभियांत्रिकी वेळ<sup>†</sup> | दरमहा $6,000 किंवा अधिक | काहीही नाही, जागतिक स्तरावर वितरित इंडेक्सर्ससह नेटवर्कमध्ये तयार केलेले |
+| प्रति महिना प्रश्न | इन्फ्रा क्षमतांपुरती मर्यादित | ~30,000,000 |
+| प्रति क्वेरी खर्च | $0 | $0.00004 |
+| पायाभूत सुविधा | केंद्रीकृत | विकेंद्रित |
+| भौगोलिक रिडंडंसी | प्रति अतिरिक्त नोड एकूण खर्चात $1,200 | समाविष्ट |
+| अपटाइम | बदलते | 99.9%+ |
+| एकूण मासिक खर्च | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*बॅकअपच्या खर्चासह: $50-$100 प्रति महिना
 
diff --git a/website/pages/mr/network/delegating.mdx b/website/pages/mr/network/delegating.mdx
index 8877d25721c4..a3cffb359ffe 100644
--- a/website/pages/mr/network/delegating.mdx
+++ b/website/pages/mr/network/delegating.mdx
@@ -50,7 +50,7 @@ If you choose an Indexer that is not trustworthy or not doing a good job, you wi
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
   ![प्रतिनिधी अनबॉन्डिंग](/img/Delegation-Unbonding.png) _डेलिगेशन UI मध्ये 0.5% शुल्क तसेच २८ दिवसांची नोंद घ्या
-   अनबॉन्डिंग कालावधी._
+  अनबॉन्डिंग कालावधी._
 </div>
 
 ### Choosing a trustworthy Indexer with a fair reward payout for Delegators
@@ -64,8 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *टॉप इंडेक्सर प्रतिनिधींना 90% बक्षिसे देत आहे. द
-   मधला प्रतिनिधी 20% देत आहे. सर्वात खालचा भाग प्रतिनिधींना ~83% देत आहे.*
+  ![इंडेक्सिंग रिवॉर्ड कट](/img/Indexing-Reward-Cut.png) *टॉप इंडेक्सर प्रतिनिधींना 90% बक्षिसे देत आहे. द मधला
+  प्रतिनिधी 20% देत आहे. सर्वात खालचा भाग प्रतिनिधींना ~83% देत आहे.*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/mr/network/indexing.mdx b/website/pages/mr/network/indexing.mdx
index 4f87435bda60..e725d445b914 100644
--- a/website/pages/mr/network/indexing.mdx
+++ b/website/pages/mr/network/indexing.mdx
@@ -112,12 +112,12 @@ Once an allocation has been closed the rebates are available to be claimed by th
 - **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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
-| ------ |:--------------------------:|:-----------------------------------:|:---------------------------------:|:---------------------:|:------------------------------:|
-| Small  |             4              |                  8                  |                 1                 |           4           |               16               |
-| मानक   |             8              |                 30                  |                 1                 |          12           |               48               |
-| Medium |             16             |                 64                  |                 2                 |          32           |               64               |
-| Large  |             72             |                 468                 |                3.5                |          48           |              184               |
+| Setup | Postgres<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(memory in GBs) |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Small | 4 | 8 | 1 | 4 | 16 |
+| मानक | 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?
 
@@ -149,20 +149,20 @@ Once an allocation has been closed the rebates are available to be claimed by th
 
 #### आलेख नोड
 
-| बंदर | Purpose                                               | Routes                                               | CLI Argument      | Environment Variable |
-| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(for managing deployments)        | /                                                    | --admin-port      | -                    |
-| 8030 | Subgraph indexing status API                          | /graphql                                             | --index-node-port | -                    |
-| 8040 | Prometheus metrics                                    | /metrics                                             | --metrics-port    | -                    |
+| बंदर | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(for managing deployments) | / | --admin-port | - |
+| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Service
 
-| बंदर | Purpose                                                    | Routes                                                                  | CLI Argument   | Environment Variable   |
-| ---- | ---------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
+| बंदर | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
@@ -623,7 +623,7 @@ graph indexer rules delete QmZfeJYR86UARzp9HiXbURWunYgC9ywvPvoePNbuaATrEK
 - Indexer can use the `indexer-cli` to view all queued actions
 - इंडेक्सर (किंवा इतर सॉफ्टवेअर) `indexer-cli` वापरून रांगेतील क्रिया मंजूर किंवा रद्द करू शकतात. मंजूर आणि रद्द आदेश इनपुट म्हणून अॅक्शन आयडीचा अॅरे घेतात.
 - अंमलबजावणी कर्मचारी नियमितपणे मंजूर कृतींसाठी रांगेत मतदान करतात. ते रांगेतील `मंजूर` क्रिया पकडेल, त्या कार्यान्वित करण्याचा प्रयत्न करेल आणि अंमलबजावणीच्या स्थितीनुसार `यशस्वी` किंवा `अयशस्वी< वर db मधील मूल्ये अपडेट करेल. /code>.</li>
-<li>एखादी कृती यशस्वी झाल्यास कार्यकर्ता खात्री करेल की एक अनुक्रमणिका नियम उपस्थित आहे जो एजंटला वाटप कसे व्यवस्थापित करावे हे सांगते, एजंट <code>ऑटो` किंवा ` मध्ये असताना मॅन्युअल क्रिया करताना उपयुक्त oversight` मोड.
+  <li>एखादी कृती यशस्वी झाल्यास कार्यकर्ता खात्री करेल की एक अनुक्रमणिका नियम उपस्थित आहे जो एजंटला वाटप कसे व्यवस्थापित करावे हे सांगते, एजंट <code>ऑटो` किंवा ` मध्ये असताना मॅन्युअल क्रिया करताना उपयुक्त oversight` मोड.
 - इंडेक्सर कारवाईच्या अंमलबजावणीचा इतिहास पाहण्यासाठी कृती रांगेचे निरीक्षण करू शकतो आणि आवश्यक असल्यास क्रिया आयटमची अंमलबजावणी अयशस्वी झाल्यास पुन्हा मंजूर आणि अद्यतनित करू शकतो. कृती रांग रांगेत लावलेल्या आणि केलेल्या सर्व क्रियांचा इतिहास प्रदान करते.
 
 Data model:
diff --git a/website/pages/mr/new-chain-integration.mdx b/website/pages/mr/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/mr/new-chain-integration.mdx
+++ b/website/pages/mr/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/mr/operating-graph-node.mdx b/website/pages/mr/operating-graph-node.mdx
index 84d5fb6d4d9b..907114f75be5 100644
--- a/website/pages/mr/operating-graph-node.mdx
+++ b/website/pages/mr/operating-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:
 
-| बंदर | Purpose                                               | Routes                                               | CLI Argument      | Environment Variable |
-| ---- | ----------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(for managing deployments)        | /                                                    | --admin-port      | -                    |
-| 8030 | Subgraph indexing status API                          | /graphql                                             | --index-node-port | -                    |
-| 8040 | Prometheus metrics                                    | /metrics                                             | --metrics-port    | -                    |
+| बंदर | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(for managing deployments) | / | --admin-port | - |
+| 8030 | Subgraph indexing status API | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
 
 > **महत्त्वाचे**: पोर्ट सार्वजनिकपणे उघड करण्याबाबत सावधगिरी बाळगा - **प्रशासन पोर्ट** लॉक डाउन ठेवले पाहिजेत. यामध्ये ग्राफ नोड JSON-RPC एंडपॉइंटचा समावेश आहे.
 
diff --git a/website/pages/mr/querying/graphql-api.mdx b/website/pages/mr/querying/graphql-api.mdx
index 7fefa001aca4..ed5f483cfc2a 100644
--- a/website/pages/mr/querying/graphql-api.mdx
+++ b/website/pages/mr/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator            | वर्णन                                                                                                                                |
-| ----------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `आणि`               | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `किंवा`             | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms |
-| `<->` | `द्वारे अनुसरण करा` | Specify the distance between two words.                                                                                              |
-| `:*`        | `Prefix`            | Use the prefix search term to find words whose prefix match (2 characters required.)                                                 |
+| Symbol | Operator | वर्णन |
+| --- | --- | --- |
+| `&` | `आणि` | For combining multiple search terms into a filter for entities that include all of the provided terms |
+| &#x7c; | `किंवा` | Queries with multiple search terms separated by the or operator will return all entities with a match from any of the provided terms |
+| `<->` | `द्वारे अनुसरण करा` | Specify the distance between two words. |
+| `:*` | `Prefix` | Use the prefix search term to find words whose prefix match (2 characters required.) |
 
 #### Examples
 
diff --git a/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx
index 2d735415bebb..a170ebec8cda 100644
--- a/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/mr/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ However now this isn't possible anymore, and the compiler returns this error:
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/mr/sps/triggers-example.mdx b/website/pages/mr/sps/triggers-example.mdx
index 7ea6674d7884..5291e4a404b3 100644
--- a/website/pages/mr/sps/triggers-example.mdx
+++ b/website/pages/mr/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## पूर्वतयारी
diff --git a/website/pages/mr/supported-network-requirements.mdx b/website/pages/mr/supported-network-requirements.mdx
index 8d20c31f3fc5..a1a9e0338649 100644
--- a/website/pages/mr/supported-network-requirements.mdx
+++ b/website/pages/mr/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network  | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| हिमस्खलन | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base     | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo     | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| इथरियम   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| फॅन्टम   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis   | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| आशावाद   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| बहुभुज   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll   | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| हिमस्खलन | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| इथरियम | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| फॅन्टम | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| आशावाद | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| बहुभुज | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx
index 92a75ed476d9..a23e14babbb2 100644
--- a/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/nl/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/nl/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/nl/developing/graph-ts/api.mdx b/website/pages/nl/developing/graph-ts/api.mdx
index 8fc1f4b48b61..6a0c4e208b99 100644
--- a/website/pages/nl/developing/graph-ts/api.mdx
+++ b/website/pages/nl/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/nl/developing/unit-testing-framework.mdx b/website/pages/nl/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/nl/developing/unit-testing-framework.mdx
+++ b/website/pages/nl/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/nl/network/benefits.mdx b/website/pages/nl/network/benefits.mdx
index 85fb9bde66ce..3c8d31ec132f 100644
--- a/website/pages/nl/network/benefits.mdx
+++ b/website/pages/nl/network/benefits.mdx
@@ -5,7 +5,7 @@ socialImage: https://thegraph.com/docs/img/seo/benefits.jpg
 
 Het gedecentraliseerde netwerk van The Graph is ontworpen en verfijnd om een robuuste ervaring te creëren bij het indexeren en opvragen van data. Het netwerk wordt iedere dag sterker door de duizenden bijdragers wereldwijd.
 
-De voordelen van dit gedecentraliseerde protocol is dat het niet gerepliceerd kan worden door een  `graph-node` lokaal te laten werken. Het Graph Netwerk is betrouwbaarder, efficiënter en goedkoper.
+De voordelen van dit gedecentraliseerde protocol is dat het niet gerepliceerd kan worden door een `graph-node` lokaal te laten werken. Het Graph Netwerk is betrouwbaarder, efficiënter en goedkoper.
 
 Hier is een analyse:
 
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|     Kostenvergelijking     |               Zelf hosten               |                                         De Graph Netwerk                                         |
-|:--------------------------:|:---------------------------------------:|:------------------------------------------------------------------------------------------------:|
-| Maandelijkse serverkosten  |             $350 per maand              |                                                $0                                                |
-|        Querykosten         |                   $0+                   |                                           $0 per month                                           |
-| Onderhoud tijd<sup>†</sup> |             $400 per maand              | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
-|  Aantal queries per maand  | Beperkt tot infrastructuurcapaciteiten  |                                       100,000 (Free Plan)                                        |
-|      Kosten per query      |                   $0                    |                                          $0<sup>‡</sup>                                          |
-|       Infrastructuur       |             Gecentraliseerd             |                                        Gedecentraliseerd                                         |
-|  Geografische redundantie  |          $750+ per extra node           |                                            Inbegrepen                                            |
-|           Uptime           |                Wisselend                |                                              99,9%+                                              |
-| Totale maandelijkse kosten | <span className="highlight-row" />$750+ |                                                $0                                                |
+| Kostenvergelijking | Zelf hosten | De Graph Netwerk |
+| :-: | :-: | :-: |
+| Maandelijkse serverkosten | $350 per maand | $0 |
+| Querykosten | $0+ | $0 per month |
+| Onderhoud tijd<sup>†</sup> | $400 per maand | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
+| Aantal queries per maand | Beperkt tot infrastructuurcapaciteiten | 100,000 (Free Plan) |
+| Kosten per query | $0 | $0<sup>‡</sup> |
+| Infrastructuur | Gecentraliseerd | Gedecentraliseerd |
+| Geografische redundantie | $750+ per extra node | Inbegrepen |
+| Uptime | Wisselend | 99,9%+ |
+| Totale maandelijkse kosten | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|     Kostenvergelijking      |                Zelf hosten                |                                         De Graph Netwerk                                         |
-|:---------------------------:|:-----------------------------------------:|:------------------------------------------------------------------------------------------------:|
-|  Maandelijkse serverkosten  |              $350 per maand               |                                                $0                                                |
-|         Querykosten         |              $500 per maand               |                                          $120 per month                                          |
-|    Onderhoud<sup>†</sup>    |              $800 per maand               | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
-|  Aantal queries per maand   |  Beperkt tot infrastructuurcapaciteiten   |                                            ~3,000,000                                            |
-|      Kosten per query       |                    $0                     |                                             $0.00004                                             |
-|       Infrastructuur        |              Gecentraliseerd              |                                        Gedecentraliseerd                                         |
-| Technische personeelskosten |               $200 per uur                |                                            Inbegrepen                                            |
-|  Geografische redundantie   |    $1200 totale kosten per extra node     |                                            Inbegrepen                                            |
-|           Uptime            |                 Wisselend                 |                                              99,9%+                                              |
-| Totale maandelijkse kosten  | <span className="highlight-row" /> $1650+ |                                               $120                                               |
+| Kostenvergelijking | Zelf hosten | De Graph Netwerk |
+| :-: | :-: | :-: |
+| Maandelijkse serverkosten | $350 per maand | $0 |
+| Querykosten | $500 per maand | $120 per month |
+| Onderhoud<sup>†</sup> | $800 per maand | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
+| Aantal queries per maand | Beperkt tot infrastructuurcapaciteiten | ~3,000,000 |
+| Kosten per query | $0 | $0.00004 |
+| Infrastructuur | Gecentraliseerd | Gedecentraliseerd |
+| Technische personeelskosten | $200 per uur | Inbegrepen |
+| Geografische redundantie | $1200 totale kosten per extra node | Inbegrepen |
+| Uptime | Wisselend | 99,9%+ |
+| Totale maandelijkse kosten | <span className="highlight-row" /> $1650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|     Kostenvergelijking     |                Zelf hosten                 |                                         De Graph Netwerk                                         |
-|:--------------------------:|:------------------------------------------:|:------------------------------------------------------------------------------------------------:|
-| Maandelijkse serverkosten  |         $1100 per maand, per node          |                                                $0                                                |
-|        Querykosten         |                   $4000                    |                                         $1,200 per month                                         |
-|   Aantal benodigde nodes   |                     10                     |                                       Niet van toepassing                                        |
-|   Onderhoud<sup>†</sup>    |          $6000 of meer per maand           | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
-|  Aantal queries per maand  |   Beperkt tot infrastructuurcapaciteiten   |                                           ~30,000,000                                            |
-|      Kosten per query      |                     $0                     |                                             $0.00004                                             |
-|       Infrastructuur       |              Gecentraliseerd               |                                        Gedecentraliseerd                                         |
-|  Geografische redundantie  |   $1200 in totale kosten per extra node    |                                            Inbegrepen                                            |
-|           Uptime           |                 Wisselend                  |                                              99,9%+                                              |
-| Totale maandelijkse kosten | <span className="highlight-row" /> $11000+ |                                              $1,200                                              |
+| Kostenvergelijking | Zelf hosten | De Graph Netwerk |
+| :-: | :-: | :-: |
+| Maandelijkse serverkosten | $1100 per maand, per node | $0 |
+| Querykosten | $4000 | $1,200 per month |
+| Aantal benodigde nodes | 10 | Niet van toepassing |
+| Onderhoud<sup>†</sup> | $6000 of meer per maand | Geen, deze kosten worden opgevangen door het wereldwijd gedistribueerde netwerk van indexeerders |
+| Aantal queries per maand | Beperkt tot infrastructuurcapaciteiten | ~30,000,000 |
+| Kosten per query | $0 | $0.00004 |
+| Infrastructuur | Gecentraliseerd | Gedecentraliseerd |
+| Geografische redundantie | $1200 in totale kosten per extra node | Inbegrepen |
+| Uptime | Wisselend | 99,9%+ |
+| Totale maandelijkse kosten | <span className="highlight-row" /> $11000+ | $1,200 |
 
 \*inclusief kosten voor een back-up: $50-$100 per maand
 
diff --git a/website/pages/nl/network/delegating.mdx b/website/pages/nl/network/delegating.mdx
index c0a3224f156c..84d2c6dd2118 100644
--- a/website/pages/nl/network/delegating.mdx
+++ b/website/pages/nl/network/delegating.mdx
@@ -49,7 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Let op de 0,5% belasting in de Delegatie UI, evenals de 28-daagse ontbindingsperiode_
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Let op de 0,5% belasting in de Delegatie UI, evenals de
+  28-daagse ontbindingsperiode_
 </div>
 
 ### Het kiezen van een betrouwbare Indexeerder met een eerlijke beloningsuitbetaling voor Delegeerders
@@ -63,7 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png)  *De bovenste Indexeerder geeft Delegeerders 90% van de beloningen. De middelste geeft Delegeerders 20%. De onderste geeft Delegeerders ~83%.*
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *De bovenste Indexeerder geeft Delegeerders 90% van de
+  beloningen. De middelste geeft Delegeerders 20%. De onderste geeft Delegeerders ~83%.*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/nl/network/indexing.mdx b/website/pages/nl/network/indexing.mdx
index 40c0fc8f131e..ee65031735f6 100644
--- a/website/pages/nl/network/indexing.mdx
+++ b/website/pages/nl/network/indexing.mdx
@@ -112,12 +112,12 @@ Indexeerders kunnen zich onderscheiden door geavanceerde technieken toe te passe
 - **Middel** - Indexer die 100 subgraphs ondersteund en 200-500 query's per seconde verwerkt.
 - **Groot** - Voorbereid om alle momenteel gebruikte subgraphs te indexeren en de bijbehorende query's te verwerken.
 
-| Setup     | Postgres<br />(CPUs) | Postgres<br />(Geheugen in GBs) | Postgres<br />(schijf in TBs) | VMs<br />(CPUs) | VMs<br />(geheugen in GBs) |
-| --------- |:--------------------------:|:-------------------------------------:|:-----------------------------------:|:---------------------:|:--------------------------------:|
-| Klein     |             4              |                   8                   |                  1                  |           4           |                16                |
-| Standaard |             8              |                  30                   |                  1                  |          12           |                48                |
-| Middel    |             16             |                  64                   |                  2                  |          32           |                64                |
-| Groot     |             72             |                  468                  |                 3.5                 |          48           |               184                |
+| Setup | Postgres<br />(CPUs) | Postgres<br />(Geheugen in GBs) | Postgres<br />(schijf in TBs) | VMs<br />(CPUs) | VMs<br />(geheugen in GBs) |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Klein | 4 | 8 | 1 | 4 | 16 |
+| Standaard | 8 | 30 | 1 | 12 | 48 |
+| Middel | 16 | 64 | 2 | 32 | 64 |
+| Groot | 72 | 468 | 3.5 | 48 | 184 |
 
 ### Wat zijn enkele basisveiligheidsmaatregelen die een Indexeerder moet nemen?
 
@@ -149,20 +149,20 @@ Tip: Om wendbare schaalvergroting te ondersteunen, wordt aanbevolen om Query- en
 
 #### Graph Node
 
-| Poort | Doel                                                      | Routes                                               | CLI-Argument      | Omgevingsvariabele |
-| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
-| 8000  | GraphQL HTTP server<br />(voor subgraph query's)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
-| 8001  | GraphQL WS<br />(voor subgraph abonnementen)        | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
-| 8020  | JSON-RPC<br />(voor het beheren van implementaties) | /                                                    | --admin-port      | -                  |
-| 8030  | Subgraph indexeerstatus API                               | /graphql                                             | --index-node-port | -                  |
-| 8040  | Prometheus metrics                                        | /metrics                                             | --metrics-port    | -                  |
+| Poort | Doel | Routes | CLI-Argument | Omgevingsvariabele |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(voor subgraph query's) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(voor subgraph abonnementen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(voor het beheren van implementaties) | / | --admin-port | - |
+| 8030 | Subgraph indexeerstatus API | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Service
 
-| Poort | Doel                                                            | Routes                                                                  | CLI-Argument   | Omgevingsvariabele     |
-| ----- | --------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600  | GraphQL HTTP server<br />(voor betaalde subgraph query's) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300  | Prometheus metrics                                              | /metrics                                                                | --metrics-port | -                      |
+| Poort | Doel | Routes | CLI-Argument | Omgevingsvariabele |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(voor betaalde subgraph query's) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/nl/new-chain-integration.mdx b/website/pages/nl/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/nl/new-chain-integration.mdx
+++ b/website/pages/nl/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/nl/operating-graph-node.mdx b/website/pages/nl/operating-graph-node.mdx
index 7524b17721c9..d2117bcf07d5 100644
--- a/website/pages/nl/operating-graph-node.mdx
+++ b/website/pages/nl/operating-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:
 
-| Poort | Doel                                                      | Routes                                               | CLI-Argument      | Omgevingsvariabele |
-| ----- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
-| 8000  | GraphQL HTTP server<br />(voor subgraph query's)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                  |
-| 8001  | GraphQL WS<br />(voor subgraph abonnementen)        | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
-| 8020  | JSON-RPC<br />(voor het beheren van implementaties) | /                                                    | --admin-port      | -                  |
-| 8030  | Subgraph indexeerstatus API                               | /graphql                                             | --index-node-port | -                  |
-| 8040  | Prometheus metrics                                        | /metrics                                             | --metrics-port    | -                  |
+| Poort | Doel | Routes | CLI-Argument | Omgevingsvariabele |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(voor subgraph query's) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(voor subgraph abonnementen) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(voor het beheren van implementaties) | / | --admin-port | - |
+| 8030 | Subgraph indexeerstatus 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.
 
diff --git a/website/pages/nl/querying/graphql-api.mdx b/website/pages/nl/querying/graphql-api.mdx
index d8671e53a77c..3dd70fc7b004 100644
--- a/website/pages/nl/querying/graphql-api.mdx
+++ b/website/pages/nl/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Description                                                                                                                          |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx b/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx
index 17224699570d..85f6903a6c69 100644
--- a/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/nl/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/nl/sps/triggers-example.mdx b/website/pages/nl/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/nl/sps/triggers-example.mdx
+++ b/website/pages/nl/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/nl/supported-network-requirements.mdx b/website/pages/nl/supported-network-requirements.mdx
index 4a5d2fa8f364..9bfbc8d0fefd 100644
--- a/website/pages/nl/supported-network-requirements.mdx
+++ b/website/pages/nl/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Netwerk   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Netwerk | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx
index 5665b2730198..37a742e7c78a 100644
--- a/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/pl/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/pl/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/pl/developing/graph-ts/api.mdx b/website/pages/pl/developing/graph-ts/api.mdx
index 8fc1f4b48b61..6a0c4e208b99 100644
--- a/website/pages/pl/developing/graph-ts/api.mdx
+++ b/website/pages/pl/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/pl/developing/unit-testing-framework.mdx b/website/pages/pl/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/pl/developing/unit-testing-framework.mdx
+++ b/website/pages/pl/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/pl/network/benefits.mdx b/website/pages/pl/network/benefits.mdx
index 2ff74600cf86..7416ff6346fe 100644
--- a/website/pages/pl/network/benefits.mdx
+++ b/website/pages/pl/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                         Sieć The Graph                          |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|        Infrastructure        |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | Sieć The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                         Sieć The Graph                          |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|        Infrastructure        |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | Sieć The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                         Sieć The Graph                          |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | Sieć The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/pl/network/indexing.mdx b/website/pages/pl/network/indexing.mdx
index 0eb017b5be3f..a6844c2da009 100644
--- a/website/pages/pl/network/indexing.mdx
+++ b/website/pages/pl/network/indexing.mdx
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/pl/new-chain-integration.mdx b/website/pages/pl/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/pl/new-chain-integration.mdx
+++ b/website/pages/pl/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/pl/operating-graph-node.mdx b/website/pages/pl/operating-graph-node.mdx
index fb3d538f952a..dbbfcd5fc545 100644
--- a/website/pages/pl/operating-graph-node.mdx
+++ b/website/pages/pl/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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.
 
diff --git a/website/pages/pl/querying/graphql-api.mdx b/website/pages/pl/querying/graphql-api.mdx
index d8671e53a77c..3dd70fc7b004 100644
--- a/website/pages/pl/querying/graphql-api.mdx
+++ b/website/pages/pl/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Description                                                                                                                          |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/pl/quick-start.mdx b/website/pages/pl/quick-start.mdx
index 9a4ebfc960d3..6953408d9420 100644
--- a/website/pages/pl/quick-start.mdx
+++ b/website/pages/pl/quick-start.mdx
@@ -1,5 +1,5 @@
 ---
-title: " Na start"
+title: ' Na start'
 ---
 
 Learn how to easily build, publish and query a [subgraph](/developing/developer-faqs/#1-what-is-a-subgraph) on The Graph.
diff --git a/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx b/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx
index 17224699570d..85f6903a6c69 100644
--- a/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/pl/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/pl/sps/triggers-example.mdx b/website/pages/pl/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/pl/sps/triggers-example.mdx
+++ b/website/pages/pl/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/pl/supported-network-requirements.mdx b/website/pages/pl/supported-network-requirements.mdx
index afbf755c0a5a..df15ef48d762 100644
--- a/website/pages/pl/supported-network-requirements.mdx
+++ b/website/pages/pl/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/pt/cookbook/arweave.mdx b/website/pages/pt/cookbook/arweave.mdx
index beac71cf7ea5..83781cb0165e 100644
--- a/website/pages/pt/cookbook/arweave.mdx
+++ b/website/pages/pt/cookbook/arweave.mdx
@@ -86,7 +86,7 @@ dataSources:
 - A rede deve corresponder a uma rede no Graph Node que a hospeda. No Subgraph Studio, a mainnet do Arweave é `arweave-mainnet`
 - Fontes de dados no Arweave introduzem um campo `source.owner` opcional, a chave pública de uma carteira no Arweave
 
-Fontes de dados no Arweave apoiam duas categorias de *handlers*:
+Fontes de dados no Arweave apoiam duas categorias de _handlers_:
 
 - `blockHandlers` - Executar em cada bloco novo no Arweave. Nenhum `source.owner` é exigido.
 - `transactionHandlers` — Executar em todas as transações onde o `source.owner` da fonte de dados é o dono. Atualmente, um dono é exigido para o `transactionHandlers`; caso utilizadores queiram processar todas as transações, eles devem providenciar "" como o `source.owner`
@@ -97,13 +97,13 @@ Fontes de dados no Arweave apoiam duas categorias de *handlers*:
 
 > Nota: Transações no [Irys (antigo Bundlr)](https://bundlr.network/) não são apoiadas presentemente.
 
-## Definição de *Schema*
+## Definição de _Schema_
 
 A definição de Schema descreve a estrutura do banco de dados resultado do subgraph, e os relacionamentos entre entidades. Isto é agnóstico da fonte de dados original. Há mais detalhes na definição de schema de subgraph [aqui](/developing/creating-a-subgraph/#the-graphql-schema).
 
 ## Mapeamentos de AssemblyScript
 
-Os *handlers* para eventos de processamento são escritos em [AssemblyScript](https://www.assemblyscript.org/).
+Os _handlers_ para eventos de processamento são escritos em [AssemblyScript](https://www.assemblyscript.org/).
 
 Arweave indexing introduces Arweave-specific data types to the [AssemblyScript API](/developing/graph-ts/api/).
 
@@ -146,7 +146,7 @@ class Transaction {
 }
 ```
 
-*Handlers* de bloco recebem um `Block`, enquanto transações recebem uma `Transaction`.
+_Handlers_ de bloco recebem um `Block`, enquanto transações recebem uma `Transaction`.
 
 Escrever os mapeamentos de um Subgraph no Arweave é muito similar à escrita dos mapeamentos de um Subgraph no Ethereum. Para mais informações, clique [aqui](/developing/creating-a-subgraph/#writing-mappings).
 
diff --git a/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx
index aa88b936bbf8..5a1bf2c57245 100644
--- a/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/pt/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ Os arquivos da ABI devem combinar com o(s) seu(s) contrato(s). Há algumas manei
 
 ## SpecVersion Releases
 
-| Versão | Notas de atualização                                                                                                                                                     |
-| :----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9 | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5 | Adicionado apoio a handlers de eventos com acesso a recibos de transação.                                                                                                |
-|  0.0.4 | Adicionado apoio à gestão de recursos de subgraph.                                                                                                                       |
+| Versão | Notas de atualização |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Adicionado apoio a handlers de eventos com acesso a recibos de transação. |
+| 0.0.4 | Adicionado apoio à gestão de recursos de subgraph. |
diff --git a/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx
index 592372b0de60..a1518a96b957 100644
--- a/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/pt/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Tipo         | Descrição                                                                                                                                                                                                        |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Arranjo de bytes, representado como string hexadecimal. Usado frequentemente por hashes e endereços no Ethereum.                                                                                                 |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Tipo | Descrição |
+| --- | --- |
+| `Bytes` | Arranjo de bytes, representado como string hexadecimal. Usado frequentemente por hashes e endereços no Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/pt/developing/graph-ts/api.mdx b/website/pages/pt/developing/graph-ts/api.mdx
index acc557d643ab..0705480c4f03 100644
--- a/website/pages/pt/developing/graph-ts/api.mdx
+++ b/website/pages/pt/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ A biblioteca `@graphprotocol/graph-ts` fornece as seguintes APIs:
 
 No manifest do subgraph, `apiVersion` especifica a versão da API de mapeamento, executada pelo Graph Node para um subgraph.
 
-| Versão | Notas de atualização                                                                                                                                                                                                                      |
-| :----: | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9 | Adiciona novas funções de host [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                       |
-|  0.0.8 | Adiciona validação para existência de campos no schema ao salvar uma entidade.                                                                                                                                                            |
-|  0.0.7 | Classes `TransactionReceipt` e `Log` adicionadas aos tipos do EthereumCampo <br />Campo `receipt` adicionado ao objeto Ethereum Event                                                                                                     |
-|  0.0.6 | Campo `nonce` adicionado ao objeto Ethereum TransactionCampo <br />`baseFeePerGas` adicionado ao objeto Ethereum Block                                                                                                                    |
-|  0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` |
-|  0.0.4 | Campo `functionSignature` adicionado ao objeto Ethereum SmartContractCall                                                                                                                                                                 |
-|  0.0.3 | Campo `from` adicionado ao objeto Ethereum<br /> `Calletherem.call.address` renomeado para `ethereum.call.to`                                                                                                                             |
-|  0.0.2 | Campo `input` adicionado ao objeto Ethereum Transaction                                                                                                                                                                                   |
+| Versão | Notas de atualização |
+| :-: | --- |
+| 0.0.9 | Adiciona novas funções de host [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adiciona validação para existência de campos no schema ao salvar uma entidade. |
+| 0.0.7 | Classes `TransactionReceipt` e `Log` adicionadas aos tipos do EthereumCampo <br />Campo `receipt` adicionado ao objeto Ethereum Event |
+| 0.0.6 | Campo `nonce` adicionado ao objeto Ethereum TransactionCampo <br />`baseFeePerGas` adicionado ao objeto Ethereum Block |
+| 0.0.5 | AssemblyScript atualizado à versão 0.19.10 (inclui mudanças recentes, favor ler o [`Guia de Migração`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renomeado para `ethereum.transaction.gasLimit` |
+| 0.0.4 | Campo `functionSignature` adicionado ao objeto Ethereum SmartContractCall |
+| 0.0.3 | Campo `from` adicionado ao objeto Ethereum<br /> `Calletherem.call.address` renomeado para `ethereum.call.to` |
+| 0.0.2 | Campo `input` adicionado ao objeto Ethereum Transaction |
 
 ### Tipos Embutidos
 
@@ -166,8 +166,7 @@ _Matemática_
 import { TypedMap } from '@graphprotocol/graph-ts'
 ```
 
-O `TypedMap` pode servir para armazenar pares de chave e valor (key e value
-). Confira [este exemplo](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
+O `TypedMap` pode servir para armazenar pares de chave e valor (key e value ). Confira [este exemplo](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
 
 A classe `TypedMap` tem a seguinte API:
 
@@ -771,44 +770,44 @@ Quando o tipo de um valor é confirmado, ele pode ser convertido num [tipo embut
 
 ### Referência de Conversões de Tipos
 
-| Fonte(s)                 | Destino              | Função de conversão            |
-| ------------------------ | -------------------- | ------------------------------ |
-| Address                  | Bytes                | nenhum                         |
-| Address                  | String               | s.toHexString()                |
-| BigDecimal               | String               | s.toString()                   |
-| BigInt                   | BigDecimal           | s.toBigDecimal()               |
-| BigInt                   | String (hexadecimal) | s.toHexString() ou s.toHex()   |
-| BigInt                   | String (unicode)     | s.toString()                   |
-| BigInt                   | i32                  | s.toI32()                      |
-| Boolean                  | Boolean              | nenhum                         |
-| Bytes (assinado)         | BigInt               | BigInt.fromSignedBytes(s)      |
-| Bytes (não assinado)     | BigInt               | BigInt.fromUnsignedBytes(s)    |
-| Bytes                    | String (hexadecimal) | s.toHexString() ou s.toHex()   |
-| Bytes                    | String (unicode)     | s.toString()                   |
-| Bytes                    | String (base58)      | s.toBase58()                   |
-| Bytes                    | i32                  | s.toI32()                      |
-| Bytes                    | u32                  | s.toU32()                      |
-| Bytes                    | JSON                 | json.fromBytes(s)              |
-| int8                     | i32                  | nenhum                         |
-| int32                    | i32                  | nenhum                         |
-| int32                    | BigInt               | BigInt.fromI32(s)              |
-| uint24                   | i32                  | nenhum                         |
-| int64 - int256           | BigInt               | nenhum                         |
-| uint32 - uint256         | BigInt               | nenhum                         |
-| JSON                     | boolean              | s.toBool()                     |
-| JSON                     | i64                  | s.toI64()                      |
-| JSON                     | u64                  | s.toU64()                      |
-| JSON                     | f64                  | s.toF64()                      |
-| JSON                     | BigInt               | s.toBigInt()                   |
-| JSON                     | string               | s.toString()                   |
-| JSON                     | Array                | s.toArray()                    |
-| JSON                     | Object               | s.toObject()                   |
-| String                   | Address              | Address.fromString(s)          |
-| Bytes                    | Address              | Address.fromBytes(s)           |
-| String                   | BigInt               | BigInt.fromString(s)           |
-| String                   | BigDecimal           | BigDecimal.fromString(s)       |
-| String (hexadecimal)     | Bytes                | ByteArray.fromHexString(s)     |
-| String (UTF-8)           | Bytes                | ByteArray.fromUTF8(s)          |
+| Fonte(s)             | Destino              | Função de conversão          |
+| -------------------- | -------------------- | ---------------------------- |
+| Address              | Bytes                | nenhum                       |
+| Address              | String               | s.toHexString()              |
+| BigDecimal           | String               | s.toString()                 |
+| BigInt               | BigDecimal           | s.toBigDecimal()             |
+| BigInt               | String (hexadecimal) | s.toHexString() ou s.toHex() |
+| BigInt               | String (unicode)     | s.toString()                 |
+| BigInt               | i32                  | s.toI32()                    |
+| Boolean              | Boolean              | nenhum                       |
+| Bytes (assinado)     | BigInt               | BigInt.fromSignedBytes(s)    |
+| Bytes (não assinado) | BigInt               | BigInt.fromUnsignedBytes(s)  |
+| Bytes                | String (hexadecimal) | s.toHexString() ou s.toHex() |
+| Bytes                | String (unicode)     | s.toString()                 |
+| Bytes                | String (base58)      | s.toBase58()                 |
+| Bytes                | i32                  | s.toI32()                    |
+| Bytes                | u32                  | s.toU32()                    |
+| Bytes                | JSON                 | json.fromBytes(s)            |
+| int8                 | i32                  | nenhum                       |
+| int32                | i32                  | nenhum                       |
+| int32                | BigInt               | BigInt.fromI32(s)            |
+| uint24               | i32                  | nenhum                       |
+| int64 - int256       | BigInt               | nenhum                       |
+| uint32 - uint256     | BigInt               | nenhum                       |
+| JSON                 | boolean              | s.toBool()                   |
+| JSON                 | i64                  | s.toI64()                    |
+| JSON                 | u64                  | s.toU64()                    |
+| JSON                 | f64                  | s.toF64()                    |
+| JSON                 | BigInt               | s.toBigInt()                 |
+| JSON                 | string               | s.toString()                 |
+| JSON                 | Array                | s.toArray()                  |
+| JSON                 | Object               | s.toObject()                 |
+| String               | Address              | Address.fromString(s)        |
+| Bytes                | Address              | Address.fromBytes(s)         |
+| String               | BigInt               | BigInt.fromString(s)         |
+| String               | BigDecimal           | BigDecimal.fromString(s)     |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)   |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)        |
 
 ### Metadados de Fontes de Dados
 
diff --git a/website/pages/pt/developing/unit-testing-framework.mdx b/website/pages/pt/developing/unit-testing-framework.mdx
index c2c04c318f4f..68acc7e892b9 100644
--- a/website/pages/pt/developing/unit-testing-framework.mdx
+++ b/website/pages/pt/developing/unit-testing-framework.mdx
@@ -1112,7 +1112,7 @@ test('ethereum/contract dataSource creation example', () => {
   assert.dataSourceCount('GraphTokenLockWallet', 0)
 
   // Crie uma nova fonte de dados GraphTokenLockWallet com o endereço
-  0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
+  0xa16081f360e3847006db660bae1c6d1b2e17ec2a
   GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
 
   // Garanta que a dataSource foi criada
@@ -1381,15 +1381,15 @@ A saída do log inclui a duração do teste. Veja um exemplo:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > `ERROR TS2554: Expected ? arguments, but got ?.`
-> 
+>
 > `return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);`
-> 
+>
 > `in ~lib/matchstick-as/assembly/defaults.ts(18,12)`
-> 
+>
 > `ERROR TS2554: Expected ? arguments, but got ?.`
-> 
+>
 > `return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);`
-> 
+>
 > `in ~lib/matchstick-as/assembly/defaults.ts(24,12)`
 
 A diferença nos argumentos é causada pela diferença no `graph-ts` e no `matchstick-as`. Problemas como este são melhor resolvidos ao atualizar tudo para a versão mais recente.
diff --git a/website/pages/pt/network/benefits.mdx b/website/pages/pt/network/benefits.mdx
index 081aef23ec08..ff04d9e965ce 100644
--- a/website/pages/pt/network/benefits.mdx
+++ b/website/pages/pt/network/benefits.mdx
@@ -27,53 +27,54 @@ Os custos de query podem variar; o custo citado é o normal até o fechamento da
 
 ## Utilizador de Baixo Volume (menos de 100 mil queries por mês)
 
-|      Comparação de Custos       |             Auto-hospedagem             |                         The Graph Network                         |
-|:-------------------------------:|:---------------------------------------:|:-----------------------------------------------------------------:|
-|  Custo mensal de servidor\*   |              $350 por mês               |                                $0                                 |
-|         Custos de query         |                   $0+                   |                            $0 por mês                             |
-| Tempo de engenharia<sup>†</sup> |              $400 por mês               | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
-|         Queries por mês         | Limitadas pelas capabilidades da infra  |                      100 mil (Plano Grátis)                       |
-|         Custo por query         |                   $0                    |                          $0<sup>‡</sup>                           |
-|         Infraestrutura          |              Centralizada               |                          Descentralizada                          |
-|     Redundância geográfica      |        $750+ por node adicional         |                             Incluída                              |
-|    Uptime (disponibilidade)     |                  Varia                  |                              99.9%+                               |
-|      Custos mensais totais      | <span className="highlight-row" />$750+ |                                $0                                 |
+| Comparação de Custos | Auto-hospedagem | The Graph Network |
+| :-: | :-: | :-: |
+| Custo mensal de servidor\* | $350 por mês | $0 |
+| Custos de query | $0+ | $0 por mês |
+| Tempo de engenharia<sup>†</sup> | $400 por mês | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
+| Queries por mês | Limitadas pelas capabilidades da infra | 100 mil (Plano Grátis) |
+| Custo por query | $0 | $0<sup>‡</sup> |
+| Infraestrutura | Centralizada | Descentralizada |
+| Redundância geográfica | $750+ por node adicional | Incluída |
+| Uptime (disponibilidade) | Varia | 99.9%+ |
+| Custos mensais totais | <span className="highlight-row" />$750+ | $0 |
 
 ## Utilizador de Volume Médio (cerca de 3 milhões de queries por mês)
 
-|      Comparação de Custos       |              Auto-hospedagem               |                         The Graph Network                         |
-|:-------------------------------:|:------------------------------------------:|:-----------------------------------------------------------------:|
-|  Custo mensal de servidor\*   |                $350 por mês                |                                $0                                 |
-|         Custos de query         |                $500 por mês                |                           $120 por mês                            |
-| Tempo de engenharia<sup>†</sup> |                $800 por mês                | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
-|         Queries por mês         |   Limitadas pelas capabilidades da infra   |                            ~3 milhões                             |
-|         Custo por query         |                     $0                     |                             $0.00004                              |
-|         Infraestrutura          |                Centralizada                |                          Descentralizada                          |
-|       Custo de engenharia       |               $200 por hora                |                             Incluído                              |
-|     Redundância geográfica      | $1.200 em custos totais por node adicional |                             Incluída                              |
-|    Uptime (disponibilidade)     |                   Varia                    |                              99.9%+                               |
-|      Custos mensais totais      | <span className="highlight-row" /> $1.650+ |                               $120                                |
+| Comparação de Custos | Auto-hospedagem | The Graph Network |
+| :-: | :-: | :-: |
+| Custo mensal de servidor\* | $350 por mês | $0 |
+| Custos de query | $500 por mês | $120 por mês |
+| Tempo de engenharia<sup>†</sup> | $800 por mês | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
+| Queries por mês | Limitadas pelas capabilidades da infra | ~3 milhões |
+| Custo por query | $0 | $0.00004 |
+| Infraestrutura | Centralizada | Descentralizada |
+| Custo de engenharia | $200 por hora | Incluído |
+| Redundância geográfica | $1.200 em custos totais por node adicional | Incluída |
+| Uptime (disponibilidade) | Varia | 99.9%+ |
+| Custos mensais totais | <span className="highlight-row" /> $1.650+ | $120 |
 
 ## Utilizador de Volume Alto (cerca de 30 milhões de queries por mês)
 
-|      Comparação de Custos       |               Auto-hospedagem               |                         The Graph Network                         |
-|:-------------------------------:|:-------------------------------------------:|:-----------------------------------------------------------------:|
-|  Custo mensal de servidor\*   |          $1.100 por mês, por node           |                                $0                                 |
-|         Custos de query         |                   $4.000                    |                          $1,200 por mês                           |
-|   Número de nodes necessário    |                     10                      |                           Não se aplica                           |
-| Tempo de engenharia<sup>†</sup> |           $6.000 ou mais por mês            | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
-|         Queries por mês         |   Limitadas pelas capabilidades da infra    |                        Cerca de 30 milhões                        |
-|         Custo por query         |                     $0                      |                             $0.00004                              |
-|         Infraestrutura          |                Centralizada                 |                          Descentralizada                          |
-|     Redundância geográfica      | $1.200 em custos totais por node adicional  |                             Incluída                              |
-|    Uptime (disponibilidade)     |                    Varia                    |                              99.9%+                               |
-|      Custos mensais totais      | <span className="highlight-row" /> $11.000+ |                              $1.200                               |
+| Comparação de Custos | Auto-hospedagem | The Graph Network |
+| :-: | :-: | :-: |
+| Custo mensal de servidor\* | $1.100 por mês, por node | $0 |
+| Custos de query | $4.000 | $1,200 por mês |
+| Número de nodes necessário | 10 | Não se aplica |
+| Tempo de engenharia<sup>†</sup> | $6.000 ou mais por mês | Nenhum, embutido na rede com Indexadores distribuídos globalmente |
+| Queries por mês | Limitadas pelas capabilidades da infra | Cerca de 30 milhões |
+| Custo por query | $0 | $0.00004 |
+| Infraestrutura | Centralizada | Descentralizada |
+| Redundância geográfica | $1.200 em custos totais por node adicional | Incluída |
+| Uptime (disponibilidade) | Varia | 99.9%+ |
+| Custos mensais totais | <span className="highlight-row" /> $11.000+ | $1.200 |
 
 \*com custos de backup incluídos: $50-$100 por mês
 
 <sup>†</sup>Tempo de engenharia baseado numa hipótese de $200 por hora
 
-<sup>‡</sup>Reflete o custo ao consumidor de dados. Taxas de query ainda são pagas a Indexadores por queries do Plano Grátis.
+<sup>‡</sup>Reflete o custo ao consumidor de dados. Taxas de query ainda são pagas a Indexadores por queries do Plano
+Grátis.
 
 Os custos estimados são apenas para subgraphs na Mainnet do Ethereum — os custos são maiores ao auto-hospedar um `graph-node` em outras redes. Alguns utilizadores devem atualizar o seu subgraph a uma versão mais recente. Até o fechamento deste texto, devido às taxas de gas do Ethereum, uma atualização custa cerca de 50 dólares. Note que as taxas de gás no [Arbitrum](/arbitrum/arbitrum-faq) são muito menores que as da mainnet do Ethereum.
 
diff --git a/website/pages/pt/network/delegating.mdx b/website/pages/pt/network/delegating.mdx
index 97c25db9c751..e2880912d7b3 100644
--- a/website/pages/pt/network/delegating.mdx
+++ b/website/pages/pt/network/delegating.mdx
@@ -49,7 +49,8 @@ Se um Delegado quiser cancelar a sua delegação, seus tokens estarão sujeitos
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Perceba a taxa de 0.5% na interface da Delegação, além do período de separação de 28 dias._
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Perceba a taxa de 0.5% na interface da Delegação, além do
+  período de separação de 28 dias._
 </div>
 
 ### Como escolher um Indexador de confiança, com um pagamento justo para Delegantes
@@ -63,7 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *O Indexador acima está a dar 90% das recompensas aos Delegantes, o do meio dá 20%, e o de baixo dá cerca de 83%.*
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *O Indexador acima está a dar 90% das recompensas aos Delegantes,
+  o do meio dá 20%, e o de baixo dá cerca de 83%.*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/pt/network/indexing.mdx b/website/pages/pt/network/indexing.mdx
index 36e588e4237e..00392d71f392 100644
--- a/website/pages/pt/network/indexing.mdx
+++ b/website/pages/pt/network/indexing.mdx
@@ -112,12 +112,12 @@ Os Indexadores podem se diferenciar ao aplicar técnicas avançadas para decidir
 - **Médio** — Indexador de Produção. Apoia 100 subgraphs e 200 – 500 pedidos por segundo.
 - **Grande** — Preparado para indexar todos os subgraphs usados atualmente e servir pedidos para o tráfego relacionado.
 
-| Setup   | Postgres<br />(CPUs) | Postgres<br />(memória em GBs) | Postgres<br />(disco em TBs) | VMs<br />(CPUs) | VMs<br />(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               |
+| Setup | Postgres<br />(CPUs) | Postgres<br />(memória em GBs) | Postgres<br />(disco em TBs) | VMs<br />(CPUs) | VMs<br />(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 |
 
 ### Há alguma precaução básica de segurança que um Indexador deve tomar?
 
@@ -149,20 +149,20 @@ Nota: Para apoiar o escalamento ágil, recomendamos que assuntos de consulta e i
 
 #### Graph Node
 
-| Porta | Propósito                                                     | Rotas                                                | Argumento CLI     | Variável de Ambiente |
-| ----- | ------------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000  | Servidor HTTP GraphQL<br />(para consultas de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001  | WS GraphQL<br />(para inscrições a subgraphs)           | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020  | JSON-RPC<br />(para gerir lançamentos)                  | /                                                    | --admin-port      | -                    |
-| 8030  | API de status de indexamento 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<br />(para consultas de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | WS GraphQL<br />(para inscrições a subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(para gerir lançamentos) | / | --admin-port | - |
+| 8030 | API de status de indexamento 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<br />(para consultas de subgraph pagas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300  | Prometheus metrics                                                  | /metrics                                                                | --metrics-port | -                      |
+| Porta | Propósito | Rotas | Argumento CLI | Variável de Ambiente |
+| --- | --- | --- | --- | --- |
+| 7600 | Servidor HTTP GraphQL<br />(para consultas de subgraph pagas) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Agente Indexador
 
diff --git a/website/pages/pt/operating-graph-node.mdx b/website/pages/pt/operating-graph-node.mdx
index 5eb6c795dcd5..38202b73da9c 100644
--- a/website/pages/pt/operating-graph-node.mdx
+++ b/website/pages/pt/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Veja uma configuração de exemplo completa do Kubernetes no [repositório de in
 
 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<br />(para queries de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001  | WS GraphQL<br />(para inscrições a subgraphs)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020  | JSON-RPC<br />(para gerir lançamentos)                | /                                                    | --admin-port      | -                    |
-| 8030  | API de status de indexamento 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<br />(para queries de subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | WS GraphQL<br />(para inscrições a subgraphs) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(para gerir lançamentos) | / | --admin-port | - |
+| 8030 | API de status de indexamento do subgraph | /graphql | --index-node-port | - |
+| 8040 | Métricas Prometheus | /metrics | --metrics-port | - |
 
 > **Importante:** Cuidado ao expor portas publicamente; as **portas de administração** devem ser trancadas a sete chaves. Isto inclui o endpoint JSON-RPC do Graph Node.
 
diff --git a/website/pages/pt/querying/graphql-api.mdx b/website/pages/pt/querying/graphql-api.mdx
index 4f64d26bf2a2..1a7a109cdaaf 100644
--- a/website/pages/pt/querying/graphql-api.mdx
+++ b/website/pages/pt/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Açúcar sintático**: pode simplificar a consulta acima ao retirar o operador `and`, com o passe de uma subexpressão separada por vírgulas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Buscas fulltext têm um campo obrigatório, `text`, para ofertar termos de busca
 
 Operadores de busca fulltext:
 
-| Símbolo     | Operador    | Descrição                                                                                                                                               |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `&`     | `And`       | Para combinar múltiplos termos de busca num filtro para entidades que incluem todos os termos fornecidos                                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/pt/querying/querying-from-an-application.mdx b/website/pages/pt/querying/querying-from-an-application.mdx
index 477899816aab..c073a9d05bde 100644
--- a/website/pages/pt/querying/querying-from-an-application.mdx
+++ b/website/pages/pt/querying/querying-from-an-application.mdx
@@ -114,7 +114,7 @@ Update your `.ts` file to use the generated typed GraphQL documents:
 import React, { useEffect } from 'react'
 // ...
 // nós importamos tipos e documentos em graphql do código gerado
-(`..graphclient/`)
+;`..graphclient/`
 import { ExampleQueryDocument, ExampleQueryQuery, execute } from '../.graphclient'
 
 function App() {
diff --git a/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx b/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx
index df425838fea1..ce410b9ed255 100644
--- a/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/pt/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Renomeie as suas variáveis duplicadas, se tinha o sombreamento variável.
+
 ### Comparações de Nulos
+
 Ao fazer a atualização no seu subgraph, às vezes aparecem erros como este:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Para resolver isto, basta mudar a declaração `if` para algo assim:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Para consertar este problema, vale criar uma variável para aquele acesso à propriedade, para que o compilador faça a magia da checagem de anulabilidade:
 
 ```typescript
diff --git a/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx b/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx
index 75c8799b9286..7b94db58a11d 100644
--- a/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/pt/release-notes/graphql-validations-migration-guide.mdx
@@ -256,8 +256,7 @@ query {
 }
 ```
 
-**Conflicting fields with arguments (#OverlappingFieldsCanBeMergedRule)**
-(Campos em conflito com argumentos)
+**Conflicting fields with arguments (#OverlappingFieldsCanBeMergedRule)** (Campos em conflito com argumentos)
 
 ```graphql
 # Argumentos diferentes podem levar a dados diferentes,
@@ -466,10 +465,10 @@ Estas referências desconhecidas devem ser consertadas:
 - caso contrário, remova
 
 ### Fragment: invalid spread or definition
+
 (Fragment: espalhamento ou definição inválidos)
 
-**Invalid Fragment spread (#PossibleFragmentSpreadsRule)**
-(Espalhamento de fragment inválido)
+**Invalid Fragment spread (#PossibleFragmentSpreadsRule)** (Espalhamento de fragment inválido)
 
 Um Fragment não pode ser espalhado em um tipo não aplicável.
 
@@ -509,8 +508,7 @@ fragment inlineFragOnScalar on Dog {
 
 ### Uso de Diretivas
 
-**Directive cannot be used at this location (#KnownDirectivesRule)**
-(A diretiva não pode ser usada neste local)
+**Directive cannot be used at this location (#KnownDirectivesRule)** (A diretiva não pode ser usada neste local)
 
 Apenas diretivas GraphQL (`@...`) apoiadas pela API do The Graph podem ser usadas.
 
@@ -527,8 +525,7 @@ query {
 
 _Nota: `@stream`, `@live`, e `@defer` não têm apoio._
 
-**Directive can only be used once at this location (#UniqueDirectivesPerLocationRule)**
-(A diretiva só pode ser usada neste local uma vez)
+**Directive can only be used once at this location (#UniqueDirectivesPerLocationRule)** (A diretiva só pode ser usada neste local uma vez)
 
 As diretivas apoiadas pelo The Graph só podem ser usadas uma vez por local.
 
diff --git a/website/pages/pt/sps/triggers-example.mdx b/website/pages/pt/sps/triggers-example.mdx
index 503fcdeab65e..5562eb4ee073 100644
--- a/website/pages/pt/sps/triggers-example.mdx
+++ b/website/pages/pt/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Pré-requisitos
diff --git a/website/pages/pt/supported-network-requirements.mdx b/website/pages/pt/supported-network-requirements.mdx
index c1bd4433f1d7..d678f0534f01 100644
--- a/website/pages/pt/supported-network-requirements.mdx
+++ b/website/pages/pt/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Requisitos de Redes Apoiadas
 ---
 
-| Rede      | Guias                                                                                                                                                                                                                                                                                            | Requisitos de sistema                                                                                                                                                | Recompensas de Indexação |
-| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------------------: |
-| Arbitrum  | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_                                |             ✅            |
-| Avalanche | [Guia Docker](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                      | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 5 TiB<br /> _última atualização em agosto de 2023_                        |             ✅            |
-| Base      | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | CPU de 8+ núcleos<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> mais 4.5TB (NVMe preferido)<br /> _última atualização em 14 de maio de 2024_                    |             ✅            |
-| Binance   | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                    | CPU de 8 núcleos e 16 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 14 TiB<br /> _última atualização em 22 de junho de 2024_                 |             ✅            |
-| Celo      | [Guia Docker](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                           | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 2 TiB<br /> _última atualização em agosto de 2023_                     |             ✅            |
-| Ethereum  | [Guia Docker](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                | Frequência de clock maior que número de núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> Mais de 3TB (NVMe recomendado)<br /> _última atualização em agosto de 2023_ |             ✅            |
-| Fantom    | [Guia Docker](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                         | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 13 TiB<br /> _última atualização em agosto de 2023_                       |             ✅            |
-| Gnosis    | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                            | CPU de 6 núcleos e 12 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 3 TiB<br /> _última atualização em agosto de 2023_                       |             ✅            |
-| Linea     | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                    | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 1 TiB<br /> _última atualização em 2 de abril de 2024_                            |             ✅            |
-| Optimism  | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_                        |             ✅            |
-| Polygon   | [Guia Docker](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                        | CPU de 16 núcleos<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= SSD NVMe com mais de 10 TiB<br /> _última atualização em agosto de 2023_                               |             ✅            |
-| Scroll    | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                    | CPU de 4 núcleos e 8 threads<br /> Debian 12<br /> 16GB+ RAM<br /> SSD NVMe com mais de 1 TiB<br /> _última atualização em 3 de abril de 2024_                       |             ✅            |
+| Rede | Guias | Requisitos de sistema | Recompensas de Indexação |
+| --- | --- | --- | :-: |
+| Arbitrum | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Avalanche | [Guia Docker](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 5 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Base | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | CPU de 8+ núcleos<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> mais 4.5TB (NVMe preferido)<br /> _última atualização em 14 de maio de 2024_ | ✅ |
+| Binance | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | CPU de 8 núcleos e 16 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 14 TiB<br /> _última atualização em 22 de junho de 2024_ | ✅ |
+| Celo | [Guia Docker](https://docs.infradao.com/archive-nodes-101/celo/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 2 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Ethereum | [Guia Docker](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Frequência de clock maior que número de núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> Mais de 3TB (NVMe recomendado)<br /> _última atualização em agosto de 2023_ | ✅ |
+| Fantom | [Guia Docker](https://docs.infradao.com/archive-nodes-101/fantom/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 13 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Gnosis | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | CPU de 6 núcleos e 12 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> NVMe SSD com mais de 3 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Linea | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | CPU de 4+ núcleos<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= SSD NVMe com mais de 1 TiB<br /> _última atualização em 2 de abril de 2024_ | ✅ |
+| Optimism | [Guia Erigon Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [Guia GETH Baremetal](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [Guia GETH Docker](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | CPU de 4 núcleos e 8 threads<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> SSD NVMe com mais de 8 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Polygon | [Guia Docker](https://docs.infradao.com/archive-nodes-101/polygon/docker) | CPU de 16 núcleos<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= SSD NVMe com mais de 10 TiB<br /> _última atualização em agosto de 2023_ | ✅ |
+| Scroll | [Guia Baremetal](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Guia Docker](https://docs.infradao.com/archive-nodes-101/scroll/docker) | CPU de 4 núcleos e 8 threads<br /> Debian 12<br /> 16GB+ RAM<br /> SSD NVMe com mais de 1 TiB<br /> _última atualização em 3 de abril de 2024_ | ✅ |
diff --git a/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx
index 7da774ac392c..20748328de9e 100644
--- a/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/ro/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/ro/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/ro/developing/graph-ts/api.mdx b/website/pages/ro/developing/graph-ts/api.mdx
index 8fc1f4b48b61..6a0c4e208b99 100644
--- a/website/pages/ro/developing/graph-ts/api.mdx
+++ b/website/pages/ro/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/ro/developing/unit-testing-framework.mdx b/website/pages/ro/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/ro/developing/unit-testing-framework.mdx
+++ b/website/pages/ro/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/ro/network/benefits.mdx b/website/pages/ro/network/benefits.mdx
index b54165acd51b..47216a1b6219 100644
--- a/website/pages/ro/network/benefits.mdx
+++ b/website/pages/ro/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                        Rețeaua The Graph                        |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|        Infrastructure        |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | Rețeaua The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                        Rețeaua The Graph                        |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|        Infrastructure        |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | Rețeaua The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                        Rețeaua The Graph                        |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | Rețeaua The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/ro/network/indexing.mdx b/website/pages/ro/network/indexing.mdx
index 0eb017b5be3f..a6844c2da009 100644
--- a/website/pages/ro/network/indexing.mdx
+++ b/website/pages/ro/network/indexing.mdx
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/ro/new-chain-integration.mdx b/website/pages/ro/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/ro/new-chain-integration.mdx
+++ b/website/pages/ro/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/ro/operating-graph-node.mdx b/website/pages/ro/operating-graph-node.mdx
index fb3d538f952a..dbbfcd5fc545 100644
--- a/website/pages/ro/operating-graph-node.mdx
+++ b/website/pages/ro/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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.
 
diff --git a/website/pages/ro/querying/graphql-api.mdx b/website/pages/ro/querying/graphql-api.mdx
index d8671e53a77c..3dd70fc7b004 100644
--- a/website/pages/ro/querying/graphql-api.mdx
+++ b/website/pages/ro/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Description                                                                                                                          |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx
index 17224699570d..85f6903a6c69 100644
--- a/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ro/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/ro/sps/triggers-example.mdx b/website/pages/ro/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/ro/sps/triggers-example.mdx
+++ b/website/pages/ro/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/ro/supported-network-requirements.mdx b/website/pages/ro/supported-network-requirements.mdx
index afbf755c0a5a..df15ef48d762 100644
--- a/website/pages/ro/supported-network-requirements.mdx
+++ b/website/pages/ro/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx
index bb6722d19f5e..69757f55a845 100644
--- a/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/ru/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is
 
 ## Релизы SpecVersion
 
-| Версия | Примечания к релизу                                                                                                                                                      |
-| :----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9 | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5 | Добавлена поддержка обработчиков событий, имеющих доступ к чекам транзакций.                                                                                             |
-|  0.0.4 | Добавлена ​​поддержка управления функциями субграфа.                                                                                                                     |
+| Версия | Примечания к релизу |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Добавлена поддержка обработчиков событий, имеющих доступ к чекам транзакций. |
+| 0.0.4 | Добавлена ​​поддержка управления функциями субграфа. |
diff --git a/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx
index 0fe26c115582..687ed4af4826 100644
--- a/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/ru/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 В API GraphQL поддерживаются следующие скаляры:
 
-| Тип          | Описание                                                                                                                                                                                                         |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Массив байтов, представленный в виде шестнадцатеричной строки. Обычно используется для хэшей и адресов Ethereum.                                                                                                 |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Тип | Описание |
+| --- | --- |
+| `Bytes` | Массив байтов, представленный в виде шестнадцатеричной строки. Обычно используется для хэшей и адресов Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Перечисления
 
diff --git a/website/pages/ru/developing/graph-ts/api.mdx b/website/pages/ru/developing/graph-ts/api.mdx
index b5a90b9930fb..ae9840e913d9 100644
--- a/website/pages/ru/developing/graph-ts/api.mdx
+++ b/website/pages/ru/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ title: AssemblyScript API
 
 `apiVersion` в манифесте субграфа указывает версию мэппинга API, которая запускается посредством Graph Node для данного субграфа.
 
-| Версия | Примечания к релизу                                                                                                                                                                                                                          |
-| :----: | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9 | Добавлены новые функции хоста [`eth_get_balance`](#balance-of-an-address) и [`hasCode`](#check-if-an-address-a-contract-or-eoa)                                                                                                              |
-|  0.0.8 | Добавлена проверка наличия полей в схеме при сохранении объекта.                                                                                                                                                                             |
-|  0.0.7 | К типам Ethereum добавлены классы `TransactionReceipt` и `Log`<br />К объекту Ethereum Event добавлено поле `receipt`                                                                                                                        |
-|  0.0.6 | В объект Ethereum Transaction добавлено поле `nonce`<br />В объект Ethereum Block добавлено поле `baseFeePerGas`                                                                                                                             |
-|  0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` |
-|  0.0.4 | В объект Ethereum SmartContractCall добавлено поле `functionSignature`                                                                                                                                                                       |
-|  0.0.3 | В объект Ethereum Call добавлено поле `from`<br />`etherem.call.address` переименован в ethereum.call.to\`                                                                                                                                   |
-|  0.0.2 | В объект Ethereum Transaction добавлено поле `input`                                                                                                                                                                                         |
+| Версия | Примечания к релизу |
+| :-: | --- |
+| 0.0.9 | Добавлены новые функции хоста [`eth_get_balance`](#balance-of-an-address) и [`hasCode`](#check-if-an-address-a-contract-or-eoa) |
+| 0.0.8 | Добавлена проверка наличия полей в схеме при сохранении объекта. |
+| 0.0.7 | К типам Ethereum добавлены классы `TransactionReceipt` и `Log`<br />К объекту Ethereum Event добавлено поле `receipt` |
+| 0.0.6 | В объект Ethereum Transaction добавлено поле `nonce`<br />В объект Ethereum Block добавлено поле `baseFeePerGas` |
+| 0.0.5 | AssemblyScript обновлен до версии 0.19.10 (включая критические изменения, см. [`Руководство по миграции`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` переименован в `ethereum.transaction.gasLimit` |
+| 0.0.4 | В объект Ethereum SmartContractCall добавлено поле `functionSignature` |
+| 0.0.3 | В объект Ethereum Call добавлено поле `from`<br />`etherem.call.address` переименован в ethereum.call.to\` |
+| 0.0.2 | В объект Ethereum Transaction добавлено поле `input` |
 
 ### Встроенные типы
 
@@ -233,7 +233,7 @@ API `store` позволяет загружать, сохранять и уда
 // Импорт класса событий Transfer, сгенерированного из ERC20 ABI
 import { Transfer as TransferEvent } from '../generated/ERC20/ERC20'
 
-// Импорт типа объекта Transfer, сгенерированного из схемы GraphQL 
+// Импорт типа объекта Transfer, сгенерированного из схемы GraphQL
 import { Transfer } from '../generated/schema'
 событие
 // Обработчик события передачи
@@ -269,7 +269,6 @@ if (transfer == null) {
   transfer = new Transfer(id)
 }
 
-
 // Используйте объект Transfer, как и раньше
 ```
 
@@ -293,7 +292,6 @@ if (transfer == null) {
   transfer = new Transfer(id)
 }
 
-
 // Используйте объект Transfer, как и раньше
 ```
 
@@ -697,8 +695,8 @@ let data = ipfs.cat(path)
 import { JSONValue, Value } from '@graphprotocol/graph-ts'
 
 export function processItem(value: JSONValue, userData: Value): void {
-// Смотрите документацию по JsonValue для получения подробной информации о работе
-// со значениями JSON
+  // Смотрите документацию по JsonValue для получения подробной информации о работе
+  // со значениями JSON
   let obj = value.toObject()
   let id = obj.get('id')
   let title = obj.get('title')
@@ -707,7 +705,7 @@ export function processItem(value: JSONValue, userData: Value): void {
     return
   }
 
-// Обратные вызовы также могут создавать объекты
+  // Обратные вызовы также могут создавать объекты
   let newItem = new Item(id)
   newItem.title = title.toString()
   newitem.parent = userData.toString() // Установите для родителя значение "parentId"
@@ -772,44 +770,44 @@ if (value.kind == JSONValueKind.BOOL) {
 
 ### Справка по преобразованию типов
 
-| Источник(и)            | Место назначения          | Функция преобразования              |
-| ---------------------- | ------------------------- | ----------------------------------- |
-| Address                | Bytes                     | отсутствует                         |
-| Address                | String                    | s.toHexString()                     |
-| BigDecimal             | String                    | s.toString()                        |
-| BigInt                 | BigDecimal                | s.toBigDecimal()                    |
-| BigInt                 | String (hexadecimal)      | s.toHexString() или s.toHex()       |
-| BigInt                 | String (unicode)          | s.toString()                        |
-| BigInt                 | i32                       | s.toI32()                           |
-| Boolean                | Boolean                   | отсутствует                         |
-| Bytes (signed)         | BigInt                    | BigInt.fromSignedBytes(s)           |
-| Bytes (unsigned)       | BigInt                    | BigInt.fromUnsignedBytes(s)         |
-| Bytes                  | String (hexadecimal)      | s.toHexString() или s.toHex()       |
-| Bytes                  | String (unicode)          | s.toString()                        |
-| Bytes                  | String (base58)           | s.toBase58()                        |
-| Bytes                  | i32                       | s.toI32()                           |
-| Bytes                  | u32                       | s.toU32()                           |
-| Bytes                  | JSON                      | json.fromBytes(s)                   |
-| int8                   | i32                       | отсутствует                         |
-| int32                  | i32                       | отсутствует                         |
-| int32                  | BigInt                    | BigInt.fromI32(s)                   |
-| uint24                 | i32                       | отсутствует                         |
-| int64 - int256         | BigInt                    | отсутствует                         |
-| uint32 - uint256       | BigInt                    | отсутствует                         |
-| JSON                   | boolean                   | s.toBool()                          |
-| JSON                   | i64                       | s.toU64()                           |
-| JSON                   | u64                       | s.toU64()                           |
-| JSON                   | f64                       | s.toF64()                           |
-| JSON                   | BigInt                    | s.toBigInt()                        |
-| JSON                   | string                    | s.toString()                        |
-| JSON                   | Array                     | s.toArray()                         |
-| JSON                   | Object                    | s.toObject()                        |
-| String                 | Address                   | Address.fromString(s)               |
-| Bytes                  | Address                   | Address.fromBytes(s)                |
-| String                 | BigInt                    | BigInt.fromString(s)                |
-| String                 | BigDecimal                | BigDecimal.fromString(s)            |
-| String (hexadecimal)   | Bytes                     | ByteArray.fromHexString(s)          |
-| String (UTF-8)         | Bytes                     | ByteArray.fromUTF8(s)               |
+| Источник(и)          | Место назначения     | Функция преобразования        |
+| -------------------- | -------------------- | ----------------------------- |
+| Address              | Bytes                | отсутствует                   |
+| Address              | String               | s.toHexString()               |
+| BigDecimal           | String               | s.toString()                  |
+| BigInt               | BigDecimal           | s.toBigDecimal()              |
+| BigInt               | String (hexadecimal) | s.toHexString() или s.toHex() |
+| BigInt               | String (unicode)     | s.toString()                  |
+| BigInt               | i32                  | s.toI32()                     |
+| Boolean              | Boolean              | отсутствует                   |
+| Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)     |
+| Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)   |
+| Bytes                | String (hexadecimal) | s.toHexString() или s.toHex() |
+| Bytes                | String (unicode)     | s.toString()                  |
+| Bytes                | String (base58)      | s.toBase58()                  |
+| Bytes                | i32                  | s.toI32()                     |
+| Bytes                | u32                  | s.toU32()                     |
+| Bytes                | JSON                 | json.fromBytes(s)             |
+| int8                 | i32                  | отсутствует                   |
+| int32                | i32                  | отсутствует                   |
+| int32                | BigInt               | BigInt.fromI32(s)             |
+| uint24               | i32                  | отсутствует                   |
+| int64 - int256       | BigInt               | отсутствует                   |
+| uint32 - uint256     | BigInt               | отсутствует                   |
+| JSON                 | boolean              | s.toBool()                    |
+| JSON                 | i64                  | s.toU64()                     |
+| JSON                 | u64                  | s.toU64()                     |
+| JSON                 | f64                  | s.toF64()                     |
+| JSON                 | BigInt               | s.toBigInt()                  |
+| JSON                 | string               | s.toString()                  |
+| JSON                 | Array                | s.toArray()                   |
+| JSON                 | Object               | s.toObject()                  |
+| String               | Address              | Address.fromString(s)         |
+| Bytes                | Address              | Address.fromBytes(s)          |
+| String               | BigInt               | BigInt.fromString(s)          |
+| String               | BigDecimal           | BigDecimal.fromString(s)      |
+| String (hexadecimal) | Bytes                | ByteArray.fromHexString(s)    |
+| String (UTF-8)       | Bytes                | ByteArray.fromUTF8(s)         |
 
 ### Метаданные источника данных
 
diff --git a/website/pages/ru/developing/unit-testing-framework.mdx b/website/pages/ru/developing/unit-testing-framework.mdx
index 698e25117b45..e50b9e7f4d2b 100644
--- a/website/pages/ru/developing/unit-testing-framework.mdx
+++ b/website/pages/ru/developing/unit-testing-framework.mdx
@@ -382,7 +382,7 @@ describe("handleNewGravatars, () => {
 
 ```typescript
 import { describe, test, beforeEach } from 'matchstick-as/assembly/index'
-import { handleUpdatedGravatar, handleNewGravatar } from "../../src/gravity"
+import { handleUpdatedGravatar, handleNewGravatar } from '../../src/gravity'
 
 describe('handleUpdatedGravatars', () => {
   beforeEach(() => {
@@ -1108,29 +1108,29 @@ test('Data source simple mocking example', () => {
 
 ```typescript
 test('ethereum/contract dataSource creation example', () => {
-// Подтверждаем, что не создано ни одного источника данных из шаблона GraphTokenLockWallet
-assert.dataSourceCount('GraphTokenLockWallet', 0)
+  // Подтверждаем, что не создано ни одного источника данных из шаблона GraphTokenLockWallet
+  assert.dataSourceCount('GraphTokenLockWallet', 0)
 
-// Создаем новый источник данных GraphTokenLockWallet с адресом 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
-GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
+  // Создаем новый источник данных GraphTokenLockWallet с адресом 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A
+  GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
 
-// Подтверждаем, что источник данных создан
-assert.dataSourceCount('GraphTokenLockWallet', 1)
+  // Подтверждаем, что источник данных создан
+  assert.dataSourceCount('GraphTokenLockWallet', 1)
 
-// Добавляем второй источник данных с контекстом
-let context = new DataSourceContext()
-context.set('contextVal', Value.fromI32(325))
+  // Добавляем второй источник данных с контекстом
+  let context = new DataSourceContext()
+  context.set('contextVal', Value.fromI32(325))
 
-GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
+  GraphTokenLockWallet.createWithContext(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'), context)
 
-// Подтверждаем, что теперь есть 2 источника данных
-assert.dataSourceCount('GraphTokenLockWallet', 2)
+  // Подтверждаем, что теперь есть 2 источника данных
+  assert.dataSourceCount('GraphTokenLockWallet', 2)
 
-// Подтверждаем, что был создан источник данных с адресом "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B"
-// Имейте в виду, что тип `Address` преобразуется в строчные буквы при декодировании, поэтому адрес нужно передавать полностью в нижнем регистре, когда Вы проверяете его наличие.
-assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
+  // Подтверждаем, что был создан источник данных с адресом "0xA16081F360e3847006dB660bae1c6d1b2e17eC2B"
+  // Имейте в виду, что тип `Address` преобразуется в строчные буквы при декодировании, поэтому адрес нужно передавать полностью в нижнем регистре, когда Вы проверяете его наличие.
+  assert.dataSourceExists('GraphTokenLockWallet', '0xA16081F360e3847006dB660bae1c6d1b2e17eC2B'.toLowerCase())
 
-logDataSources('GraphTokenLockWallet')
+  logDataSources('GraphTokenLockWallet')
 })
 ```
 
@@ -1218,11 +1218,11 @@ type TokenLockMetadata @entity {
 
 ```typescript
 export function handleMetadata(content: Bytes): void {
- // dataSource.stringParams() возвращает CID источника данных файла
-// stringParam() будет имитироваться в тесте обработчика
-// для получения дополнительной информации https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
-let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
-const value = json.fromBytes(content).toObject()
+  // dataSource.stringParams() возвращает CID источника данных файла
+  // stringParam() будет имитироваться в тесте обработчика
+  // для получения дополнительной информации https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
+  let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
+  const value = json.fromBytes(content).toObject()
 
   if (value) {
     const startTime = value.get('startTime')
@@ -1267,7 +1267,7 @@ test('file/ipfs dataSource creation example', () => {
   logDataSources('GraphTokenLockMetadata')
 
   // Теперь нам нужно смоделировать метаданные dataSource, в частности,
- dataSource.stringParam()
+  dataSource.stringParam()
   // dataSource.stringParams на самом деле использует значение dataSource.address(), поэтому мы будем имитировать адрес, используя dataSourceMock из matchstick-as
   // Сначала мы сбросим значения, а затем используем dataSourceMock.setAddress() для установки CID
   dataSourceMock.resetValues()
@@ -1381,15 +1381,15 @@ Global test coverage: 22.2% (2/9 handlers).
 Это означает, что Вы использовали в своем коде `console.log`, который не поддерживается AssemblyScript. Пожалуйста, рассмотрите возможность использования [API логирования](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Несовпадение в аргументах вызвано несоответствием в `graph-ts` и `matchstick-as`. Лучший способ устранить проблемы, подобные этой, - обновить всё до последней выпущенной версии.
diff --git a/website/pages/ru/network/benefits.mdx b/website/pages/ru/network/benefits.mdx
index a11455ede307..809d32f249df 100644
--- a/website/pages/ru/network/benefits.mdx
+++ b/website/pages/ru/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|         Сравнение затрат          |         Самостоятельный хостинг         |                         Сеть The Graph                          |
-|:---------------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-| Ежемесячная стоимость сервера\* |              $350 в месяц               |                               $0                                |
-|         Стоимость запроса         |                   $0+                   |                          $0 per month                           |
-|   Время разработки<sup>†</sup>    |              $400 в месяц               | Никто, встроен в сеть с глобально распределенными индексаторами |
-|          Запросы в месяц          | Ограничен возможностями инфраструктуры  |                       100,000 (Free Plan)                       |
-|     Стоимость одного запроса      |                   $0                    |                         $0<sup>‡</sup>                          |
-|          Инфраструктура           |            Централизованная             |                       Децентрализованная                        |
-|    Географическая избыточность    |   $750+ за каждую дополнительную ноду   |                            Включено                             |
-|     Время безотказной работы      |               Варьируется               |                             99.9%+                              |
-|     Общие ежемесячные расходы     | <span className="highlight-row" />$750+ |                               $0                                |
+| Сравнение затрат | Самостоятельный хостинг | Сеть The Graph |
+| :-: | :-: | :-: |
+| Ежемесячная стоимость сервера\* | $350 в месяц | $0 |
+| Стоимость запроса | $0+ | $0 per month |
+| Время разработки<sup>†</sup> | $400 в месяц | Никто, встроен в сеть с глобально распределенными индексаторами |
+| Запросы в месяц | Ограничен возможностями инфраструктуры | 100,000 (Free Plan) |
+| Стоимость одного запроса | $0 | $0<sup>‡</sup> |
+| Инфраструктура | Централизованная | Децентрализованная |
+| Географическая избыточность | $750+ за каждую дополнительную ноду | Включено |
+| Время безотказной работы | Варьируется | 99.9%+ |
+| Общие ежемесячные расходы | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|         Сравнение затрат          |                    Самостоятельный хостинг                    |                         Сеть The Graph                          |
-|:---------------------------------:|:-------------------------------------------------------------:|:---------------------------------------------------------------:|
-| Ежемесячная стоимость сервера\* |                         $350 в месяц                          |                               $0                                |
-|         Стоимость запроса         |                         $500 в месяц                          |                         $120 per month                          |
-|   Время разработки<sup>†</sup>    |                         $800 в месяц                          | Никто, встроен в сеть с глобально распределенными индексаторами |
-|          Запросы в месяц          |            Ограничен возможностями инфраструктуры             |                           ~3,000,000                            |
-|     Стоимость одного запроса      |                              $0                               |                            $0.00004                             |
-|          Инфраструктура           |                       Централизованная                        |                       Децентрализованная                        |
-|        Инженерные расходы         |                          $200 в час                           |                            Включено                             |
-|    Географическая избыточность    | общие затраты на каждую дополнительную ноду составляют $1,200 |                            Включено                             |
-|     Время безотказной работы      |                          Варьируется                          |                             99.9%+                              |
-|     Общие ежемесячные расходы     |          <span className="highlight-row" /> $1,650+           |                              $120                               |
+| Сравнение затрат | Самостоятельный хостинг | Сеть The Graph |
+| :-: | :-: | :-: |
+| Ежемесячная стоимость сервера\* | $350 в месяц | $0 |
+| Стоимость запроса | $500 в месяц | $120 per month |
+| Время разработки<sup>†</sup> | $800 в месяц | Никто, встроен в сеть с глобально распределенными индексаторами |
+| Запросы в месяц | Ограничен возможностями инфраструктуры | ~3,000,000 |
+| Стоимость одного запроса | $0 | $0.00004 |
+| Инфраструктура | Централизованная | Децентрализованная |
+| Инженерные расходы | $200 в час | Включено |
+| Географическая избыточность | общие затраты на каждую дополнительную ноду составляют $1,200 | Включено |
+| Время безотказной работы | Варьируется | 99.9%+ |
+| Общие ежемесячные расходы | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|         Сравнение затрат          |                    Самостоятельный хостинг                    |                         Сеть The Graph                          |
-|:---------------------------------:|:-------------------------------------------------------------:|:---------------------------------------------------------------:|
-| Ежемесячная стоимость сервера\* |                     $1100 в месяц за ноду                     |                               $0                                |
-|         Стоимость запроса         |                             $4000                             |                        $1,200 per month                         |
-|    Необходимое количество нод     |                              10                               |                           Не подходит                           |
-|   Время разработки<sup>†</sup>    |                   $6,000 или больше в месяц                   | Никто, встроен в сеть с глобально распределенными индексаторами |
-|          Запросы в месяц          |            Ограничен возможностями инфраструктуры             |                           ~30,000,000                           |
-|     Стоимость одного запроса      |                              $0                               |                            $0.00004                             |
-|          Инфраструктура           |                       Централизованная                        |                       Децентрализованная                        |
-|    Географическая избыточность    | общие затраты на каждую дополнительную ноду составляют $1,200 |                            Включено                             |
-|     Время безотказной работы      |                          Варьируется                          |                             99.9%+                              |
-|     Общие ежемесячные расходы     |          <span className="highlight-row" /> $11,000+          |                             $1,200                              |
+| Сравнение затрат | Самостоятельный хостинг | Сеть The Graph |
+| :-: | :-: | :-: |
+| Ежемесячная стоимость сервера\* | $1100 в месяц за ноду | $0 |
+| Стоимость запроса | $4000 | $1,200 per month |
+| Необходимое количество нод | 10 | Не подходит |
+| Время разработки<sup>†</sup> | $6,000 или больше в месяц | Никто, встроен в сеть с глобально распределенными индексаторами |
+| Запросы в месяц | Ограничен возможностями инфраструктуры | ~30,000,000 |
+| Стоимость одного запроса | $0 | $0.00004 |
+| Инфраструктура | Централизованная | Децентрализованная |
+| Географическая избыточность | общие затраты на каждую дополнительную ноду составляют $1,200 | Включено |
+| Время безотказной работы | Варьируется | 99.9%+ |
+| Общие ежемесячные расходы | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \* включая расходы на резервное копирование: $50-$100 в месяц
 
diff --git a/website/pages/ru/network/delegating.mdx b/website/pages/ru/network/delegating.mdx
index 423bafc439ab..95e737c063a9 100644
--- a/website/pages/ru/network/delegating.mdx
+++ b/website/pages/ru/network/delegating.mdx
@@ -49,8 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Обратите внимание на комиссию в размере 0,5% в пользовательском интерфейсе Delegation, а также на 28-дневный срок
-  период разблокировки._
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Обратите внимание на комиссию в размере 0,5% в
+  пользовательском интерфейсе Delegation, а также на 28-дневный срок период разблокировки._
 </div>
 
 ### Выбор надежного Индексатора со справедливым распределением вознаграждений для Делегаторов
diff --git a/website/pages/ru/network/indexing.mdx b/website/pages/ru/network/indexing.mdx
index 978878e51f41..be34140f88fa 100644
--- a/website/pages/ru/network/indexing.mdx
+++ b/website/pages/ru/network/indexing.mdx
@@ -113,11 +113,11 @@ Once an allocation has been closed the rebates are available to be claimed by th
 - **Large** – готовность индексировать все используемые в настоящее время подграфы и обслуживать запросы на соответствующий трафик.
 
 | Настройка | Postgres<br />(ЦП) | Postgres<br />(память в ГБ) | Postgres<br />(диск в ТБ) | VMs<br />(ЦП) | VMs<br />(память в ГБ) |
-| --------- |:------------------------:|:---------------------------------:|:-------------------------------:|:-------------------:|:----------------------------:|
-| 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 |
 
 ### Какие основные меры безопасности следует предпринять индексатору?
 
@@ -149,26 +149,26 @@ Once an allocation has been closed the rebates are available to be claimed by th
 
 #### Graph Node
 
-| Порт | Назначение                                                   | Расположение                                         | CLI-аргумент      | Переменная среды |
-| ---- | ------------------------------------------------------------ | ---------------------------------------------------- | ----------------- | ---------------- |
-| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                |
-| 8001 | GraphQL WS<br />(для подписок на подграфы)             | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                |
-| 8020 | JSON-RPC<br />(для управления процессом развертывания) | /                                                    | --admin-port      | -                |
-| 8030 | API для определения статуса индексирования подграфов         | /graphql                                             | --index-node-port | -                |
-| 8040 | Показатели Prometheus                                        | /metrics                                             | --metrics-port    | -                |
+| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
+| --- | --- | --- | --- | --- |
+| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(для подписок на подграфы) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(для управления процессом развертывания) | / | --admin-port | - |
+| 8030 | API для определения статуса индексирования подграфов | /graphql | --index-node-port | - |
+| 8040 | Показатели Prometheus | /metrics | --metrics-port | - |
 
 #### Indexer Service
 
-| Порт | Назначение                                                        | Расположение                                                            | CLI-аргумент   | Переменная среды       |
-| ---- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | HTTP-сервер GraphQL<br />(для платных запросов к подграфам) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Показатели Prometheus                                             | /metrics                                                                | --metrics-port | -                      |
+| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
+| --- | --- | --- | --- | --- |
+| 7600 | HTTP-сервер GraphQL<br />(для платных запросов к подграфам) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Показатели Prometheus | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
-| Порт | Назначение                      | Расположение | CLI-аргумент              | Переменная среды                        |
-| ---- | ------------------------------- | ------------ | ------------------------- | --------------------------------------- |
-| 8000 | API для управления индексатором | /            | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
+| --- | --- | --- | --- | --- |
+| 8000 | API для управления индексатором | / | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
 
 ### Настройка серверной инфраструктуры с помощью Terraform в Google Cloud
 
diff --git a/website/pages/ru/new-chain-integration.mdx b/website/pages/ru/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/ru/new-chain-integration.mdx
+++ b/website/pages/ru/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/ru/operating-graph-node.mdx b/website/pages/ru/operating-graph-node.mdx
index d4ac6c51a05d..dad9f543237a 100644
--- a/website/pages/ru/operating-graph-node.mdx
+++ b/website/pages/ru/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 Во время работы Graph Node предоставляет следующие порты:
 
-| Порт | Назначение                                                   | Расположение                                         | CLI-аргумент      | Переменная среды |
-| ---- | ------------------------------------------------------------ | ---------------------------------------------------- | ----------------- | ---------------- |
-| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов)      | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                |
-| 8001 | GraphQL WS<br />(для подписок на подграфы)             | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                |
-| 8020 | JSON-RPC<br />(для управления процессом развертывания) | /                                                    | --admin-port      | -                |
-| 8030 | API для определения статуса индексирования подграфов         | /graphql                                             | --index-node-port | -                |
-| 8040 | Показатели Prometheus                                        | /metrics                                             | --metrics-port    | -                |
+| Порт | Назначение | Расположение | CLI-аргумент | Переменная среды |
+| --- | --- | --- | --- | --- |
+| 8000 | HTTP-сервер GraphQL<br />(для запросов подграфов) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(для подписок на подграфы) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(для управления процессом развертывания) | / | --admin-port | - |
+| 8030 | API для определения статуса индексирования подграфов | /graphql | --index-node-port | - |
+| 8040 | Показатели Prometheus | /metrics | --metrics-port | - |
 
 > **Важно**. Будьте осторожны, открывая порты для общего доступа — **порты администрирования** должны быть заблокированы. Это касается конечных точек Graph Node JSON-RPC.
 
diff --git a/website/pages/ru/querying/graphql-api.mdx b/website/pages/ru/querying/graphql-api.mdx
index 2553a41b50ec..f539ff5637c4 100644
--- a/website/pages/ru/querying/graphql-api.mdx
+++ b/website/pages/ru/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:**. Вы можете упростить приведенный выше запрос, удалив оператор `and`, передав подвыражение, разделенное запятыми.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ The result of such a query will not change over time, i.e., querying at a certai
 
 Полнотекстовые поисковые операторы:
 
-| Символ      | Оператор    | Описание                                                                                                                                       |
-| ----------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
-| `&`     | `And`       | Для объединения нескольких условий поиска в фильтр для объектов, которые включают все указанные условия                                        |
-| &#x7c;      | `Or`        | Запросы с несколькими условиями поиска, разделенные оператором or, вернут все объекты, которые соответствуют любому из предоставленных условий |
-| `<->` | `Follow by` | Укажите расстояние между двумя словами.                                                                                                        |
-| `:*`        | `Prefix`    | Используйте поисковый запрос по префиксу, чтобы найти слова с соответствующим префиксом (необходимо 2 символа)                                 |
+| Символ | Оператор | Описание |
+| --- | --- | --- |
+| `&` | `And` | Для объединения нескольких условий поиска в фильтр для объектов, которые включают все указанные условия |
+| &#x7c; | `Or` | Запросы с несколькими условиями поиска, разделенные оператором or, вернут все объекты, которые соответствуют любому из предоставленных условий |
+| `<->` | `Follow by` | Укажите расстояние между двумя словами. |
+| `:*` | `Prefix` | Используйте поисковый запрос по префиксу, чтобы найти слова с соответствующим префиксом (необходимо 2 символа) |
 
 #### Примеры
 
diff --git a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
index 1047cc70ad5b..af444be7a6e3 100644
--- a/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ru/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Вам нужно будет переименовать дублированные переменные, если Вы используете затенение переменных.
+
 ### Нулевые сравнения
+
 Выполняя обновление своего субграфа, иногда Вы можете получить такие ошибки:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Чтобы решить эту проблему, Вы можете просто изменить оператор `if` на что-то вроде этого:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Чтобы решить эту проблему, Вы можете создать переменную для доступа к этому свойству, чтобы компилятор мог выполнять проверку допустимости значений NULL:
 
 ```typescript
diff --git a/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx
index 25238b858a50..b7cb792259b3 100644
--- a/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/ru/release-notes/graphql-validations-migration-guide.mdx
@@ -284,8 +284,8 @@ query {
 
 ```graphql
 query {
- # В конце концов, у нас есть два определения "x", указывающие
- # на разные поля!
+  # В конце концов, у нас есть два определения "x", указывающие
+  # на разные поля!
   ...A
   ...B
 }
@@ -437,7 +437,7 @@ query {
 ```graphql
 query purposes {
   # Если в схеме "name" определено как "String",
-   # этот запрос не пройдёт валидацию.
+  # этот запрос не пройдёт валидацию.
   purpose(name: 1) {
     id
   }
@@ -447,8 +447,8 @@ query purposes {
 
 query purposes($name: Int!) {
   # Если "name" определено в схеме как `String`,
-   # этот запрос не пройдёт валидацию, потому что
-   # используемая переменная имеет тип `Int`
+  # этот запрос не пройдёт валидацию, потому что
+  # используемая переменная имеет тип `Int`
   purpose(name: $name) {
     id
   }
diff --git a/website/pages/ru/sps/triggers-example.mdx b/website/pages/ru/sps/triggers-example.mdx
index aa110f80d8f7..6ade2c0d8816 100644
--- a/website/pages/ru/sps/triggers-example.mdx
+++ b/website/pages/ru/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Предварительные требования
diff --git a/website/pages/ru/supported-network-requirements.mdx b/website/pages/ru/supported-network-requirements.mdx
index 21a6f62ebb20..abc7b820fde7 100644
--- a/website/pages/ru/supported-network-requirements.mdx
+++ b/website/pages/ru/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Сеть      | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Арбитрум  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Сеть | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Арбитрум | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/sv/developing/creating-a-subgraph/advanced.mdx b/website/pages/sv/developing/creating-a-subgraph/advanced.mdx
index 676c666ff0e8..46220d0a9a0a 100644
--- a/website/pages/sv/developing/creating-a-subgraph/advanced.mdx
+++ b/website/pages/sv/developing/creating-a-subgraph/advanced.mdx
@@ -279,29 +279,29 @@ For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave b
 Exempel:
 
 ```typescript
-import { TokenMetadata as TokenMetadataTemplate } from "../generated/templates";
+import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
 
-const ipfshash = "QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm";
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
 //Denna exempelkod är för en undergraf för kryptosamverkan. Ovanstående ipfs-hash är en katalog med tokenmetadata för alla kryptosamverkande NFT:er.
 
 export function handleTransfer(event: TransferEvent): void {
-  let token = Token.load(event.params.tokenId.toString());
+  let token = Token.load(event.params.tokenId.toString())
   if (!token) {
-    token = new Token(event.params.tokenId.toString());
-    token.tokenID = event.params.tokenId;
+    token = new Token(event.params.tokenId.toString())
+    token.tokenID = event.params.tokenId
 
-    token.tokenURI = "/" + event.params.tokenId.toString() + ".json";
-    const tokenIpfsHash = ipfshash + token.tokenURI;
+    token.tokenURI = '/' + event.params.tokenId.toString() + '.json'
+    const tokenIpfsHash = ipfshash + token.tokenURI
     //Detta skapar en sökväg till metadata för en enskild Crypto coven NFT. Den konkaterar katalogen med "/" + filnamn + ".json"
 
-    token.ipfsURI = tokenIpfsHash;
+    token.ipfsURI = tokenIpfsHash
 
-    TokenMetadataTemplate.create(tokenIpfsHash);
+    TokenMetadataTemplate.create(tokenIpfsHash)
   }
 
-  token.updatedAtTimestamp = event.block.timestamp;
-  token.owner = event.params.to.toHexString();
-  token.save();
+  token.updatedAtTimestamp = event.block.timestamp
+  token.owner = event.params.to.toHexString()
+  token.save()
 }
 ```
 
diff --git a/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx b/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx
index 646645e79ccc..259ae147af9f 100644
--- a/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx
+++ b/website/pages/sv/developing/creating-a-subgraph/assemblyscript-mappings.mdx
@@ -99,13 +99,13 @@ import {
   // The events classes:
   NewGravatar,
   UpdatedGravatar,
-} from "../generated/Gravity/Gravity";
+} from '../generated/Gravity/Gravity'
 ```
 
 In addition to this, one class is generated for each entity type in the subgraph's GraphQL schema. These classes provide type-safe entity loading, read and write access to entity fields as well as a `save()` method to write entities to store. All entity classes are written to `<OUTPUT_DIR>/schema.ts`, allowing mappings to import them with
 
 ```javascript
-import { Gravatar } from "../generated/schema"
+import { Gravatar } from '../generated/schema'
 ```
 
 > **Note:** The code generation must be performed again after every change to the GraphQL schema or the ABIs included in the manifest. It must also be performed at least once before building or deploying the subgraph.
diff --git a/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx
index 09b66d92660e..8166fa4088c1 100644
--- a/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/sv/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ ABI-filerna måste matcha ditt/dina kontrakt. Det finns några olika sätt att f
 
 ## SpecVersion Releases
 
-| Version | Versionsanteckningar                                                                                                                                                     |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Versionsanteckningar |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx
index 7c769d036458..5428162b401f 100644
--- a/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/sv/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Typ          | Beskrivning                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Bytematris, representerad som en hexadecimal sträng. Vanligt används för Ethereum-hashar och adresser.                                                                                                           |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Typ | Beskrivning |
+| --- | --- |
+| `Bytes` | Bytematris, representerad som en hexadecimal sträng. Vanligt används för Ethereum-hashar och adresser. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -247,12 +247,7 @@ type _Schema_
     name: "bandSearch"
     language: en
     algorithm: rank
-    include: [
-      {
-        entity: "Band"
-        fields: [{ name: "name" }, { name: "description" }, { name: "bio" }]
-      }
-    ]
+    include: [{ entity: "Band", fields: [{ name: "name" }, { name: "description" }, { name: "bio" }] }]
   )
 
 type Band @entity {
@@ -288,24 +283,24 @@ Att välja ett annat språk kommer att ha en definitiv, om än ibland subtil, ef
 
 Stödda språkordböcker:
 
-| Code   | Ordbok       |
-| ------ | ------------ |
-| enkel  | General      |
-| da     | Danish       |
-| nl     | Dutch        |
-| en     | English      |
-| fi     | Finnish      |
-| fr     | French       |
-| de     | German       |
-| hu     | Hungarian    |
-| it     | Italian      |
-| no     | Norwegian    |
-| pt     | Portugisiska |
-| ro     | Romanian     |
-| ru     | Russian      |
-| es     | Spanish      |
-| sv     | Swedish      |
-| tr     | Turkish      |
+| Code  | Ordbok       |
+| ----- | ------------ |
+| enkel | General      |
+| da    | Danish       |
+| nl    | Dutch        |
+| en    | English      |
+| fi    | Finnish      |
+| fr    | French       |
+| de    | German       |
+| hu    | Hungarian    |
+| it    | Italian      |
+| no    | Norwegian    |
+| pt    | Portugisiska |
+| ro    | Romanian     |
+| ru    | Russian      |
+| es    | Spanish      |
+| sv    | Swedish      |
+| tr    | Turkish      |
 
 ### Rankningsalgoritmer
 
diff --git a/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx b/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx
index eedbf6b73287..fa653c523940 100644
--- a/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx
+++ b/website/pages/sv/developing/creating-a-subgraph/subgraph-manifest.mdx
@@ -165,7 +165,7 @@ dataSources:
     name: Gravity
     network: mainnet
     source:
-      address: "0x731a10897d267e19b34503ad902d0a29173ba4b1"
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
       abi: Gravity
     mapping:
       kind: ethereum/events
@@ -189,15 +189,15 @@ The `function` is the normalized function signature to filter calls by. The `han
 Each call handler takes a single parameter that has a type corresponding to the name of the called function. In the example subgraph above, the mapping contains a handler for when the `createGravatar` function is called and receives a `CreateGravatarCall` parameter as an argument:
 
 ```typescript
-import { CreateGravatarCall } from "../generated/Gravity/Gravity";
-import { Transaction } from "../generated/schema";
+import { CreateGravatarCall } from '../generated/Gravity/Gravity'
+import { Transaction } from '../generated/schema'
 
 export function handleCreateGravatar(call: CreateGravatarCall): void {
-  let id = call.transaction.hash;
-  let transaction = new Transaction(id);
-  transaction.displayName = call.inputs._displayName;
-  transaction.imageUrl = call.inputs._imageUrl;
-  transaction.save();
+  let id = call.transaction.hash
+  let transaction = new Transaction(id)
+  transaction.displayName = call.inputs._displayName
+  transaction.imageUrl = call.inputs._imageUrl
+  transaction.save()
 }
 ```
 
@@ -228,7 +228,7 @@ dataSources:
     name: Gravity
     network: dev
     source:
-      address: "0x731a10897d267e19b34503ad902d0a29173ba4b1"
+      address: '0x731a10897d267e19b34503ad902d0a29173ba4b1'
       abi: Gravity
     mapping:
       kind: ethereum/events
@@ -280,9 +280,9 @@ Den definierade hanteraren med filtret once kommer att anropas endast en gång i
 
 ```ts
 export function handleOnce(block: ethereum.Block): void {
-  let data = new InitialData(Bytes.fromUTF8("initial"));
-  data.data = "Setup data here";
-  data.save();
+  let data = new InitialData(Bytes.fromUTF8('initial'))
+  data.data = 'Setup data here'
+  data.save()
 }
 ```
 
@@ -291,12 +291,12 @@ export function handleOnce(block: ethereum.Block): void {
 The mapping function will receive an `ethereum.Block` as its only argument. Like mapping functions for events, this function can access existing subgraph entities in the store, call smart contracts and create or update entities.
 
 ```typescript
-import { ethereum } from "@graphprotocol/graph-ts";
+import { ethereum } from '@graphprotocol/graph-ts'
 
 export function handleBlock(block: ethereum.Block): void {
-  let id = block.hash;
-  let entity = new Block(id);
-  entity.save();
+  let id = block.hash
+  let entity = new Block(id)
+  entity.save()
 }
 ```
 
@@ -356,7 +356,7 @@ dataSources:
     name: Factory
     network: mainnet
     source:
-      address: "0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95"
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
       abi: Factory
     mapping:
       kind: ethereum/events
@@ -414,12 +414,12 @@ templates:
 In the final step, you update your main contract mapping to create a dynamic data source instance from one of the templates. In this example, you would change the main contract mapping to import the `Exchange` template and call the `Exchange.create(address)` method on it to start indexing the new exchange contract.
 
 ```typescript
-import { Exchange } from "../generated/templates";
+import { Exchange } from '../generated/templates'
 
 export function handleNewExchange(event: NewExchange): void {
   // Start indexing the exchange; `event.params.exchange` is the
   // address of the new exchange contract
-  Exchange.create(event.params.exchange);
+  Exchange.create(event.params.exchange)
 }
 ```
 
@@ -432,22 +432,22 @@ export function handleNewExchange(event: NewExchange): void {
 Data source contexts allow passing extra configuration when instantiating a template. In our example, let's say exchanges are associated with a particular trading pair, which is included in the `NewExchange` event. That information can be passed into the instantiated data source, like so:
 
 ```typescript
-import { Exchange } from "../generated/templates";
+import { Exchange } from '../generated/templates'
 
 export function handleNewExchange(event: NewExchange): void {
-  let context = new DataSourceContext();
-  context.setString("tradingPair", event.params.tradingPair);
-  Exchange.createWithContext(event.params.exchange, context);
+  let context = new DataSourceContext()
+  context.setString('tradingPair', event.params.tradingPair)
+  Exchange.createWithContext(event.params.exchange, context)
 }
 ```
 
 Inside a mapping of the `Exchange` template, the context can then be accessed:
 
 ```typescript
-import { dataSource } from "@graphprotocol/graph-ts";
+import { dataSource } from '@graphprotocol/graph-ts'
 
-let context = dataSource.context();
-let tradingPair = context.getString("tradingPair")
+let context = dataSource.context()
+let tradingPair = context.getString('tradingPair')
 ```
 
 There are setters and getters like `setString` and `getString` for all value types.
@@ -462,7 +462,7 @@ dataSources:
     name: ExampleSource
     network: mainnet
     source:
-      address: "0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95"
+      address: '0xc0a47dFe034B400B47bDaD5FecDa2621de6c4d95'
       abi: ExampleContract
       startBlock: 6627917
     mapping:
diff --git a/website/pages/sv/developing/developer-faqs.mdx b/website/pages/sv/developing/developer-faqs.mdx
index 907509ee9f9d..e79a1bf808e1 100644
--- a/website/pages/sv/developing/developer-faqs.mdx
+++ b/website/pages/sv/developing/developer-faqs.mdx
@@ -93,7 +93,7 @@ Du kan hitta listan över de stödda nätverken [här](/developing/supported-net
 Ja, du kan göra detta genom att importera `graph-ts` enligt exemplet nedan:
 
 ```javascript
-import { dataSource } from "@graphprotocol/graph-ts"
+import { dataSource } from '@graphprotocol/graph-ts'
 
 dataSource.network()
 dataSource.address()
diff --git a/website/pages/sv/developing/graph-ts/api.mdx b/website/pages/sv/developing/graph-ts/api.mdx
index 2dbb19d8f5cf..9fb6713242bf 100644
--- a/website/pages/sv/developing/graph-ts/api.mdx
+++ b/website/pages/sv/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Versionsanteckningar                                                                                                                                                                                                                          |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Versionsanteckningar |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Inbyggda typer
 
@@ -163,7 +163,7 @@ _Math_
 #### TypedMap
 
 ```typescript
-import { TypedMap } from "@graphprotocol/graph-ts";
+import { TypedMap } from '@graphprotocol/graph-ts'
 ```
 
 `TypedMap` can be used to store key-value pairs. See [this example](https://github.com/graphprotocol/aragon-subgraph/blob/29dd38680c5e5104d9fdc2f90e740298c67e4a31/individual-dao-subgraph/mappings/constants.ts#L51).
@@ -179,7 +179,7 @@ The `TypedMap` class has the following API:
 #### Bytes
 
 ```typescript
-import { Bytes } from "@graphprotocol/graph-ts";
+import { Bytes } from '@graphprotocol/graph-ts'
 ```
 
 `Bytes` is used to represent arbitrary-length arrays of bytes. This includes Ethereum values of type `bytes`, `bytes32`, etc.
@@ -205,7 +205,7 @@ _Operators_
 #### Address
 
 ```typescript
-import { Address } from "@graphprotocol/graph-ts";
+import { Address } from '@graphprotocol/graph-ts'
 ```
 
 `Address` extends `Bytes` to represent Ethereum `address` values.
@@ -218,7 +218,7 @@ It adds the following method on top of the `Bytes` API:
 ### Store API
 
 ```typescript
-import { store } from "@graphprotocol/graph-ts";
+import { store } from '@graphprotocol/graph-ts'
 ```
 
 The `store` API allows to load, save and remove entities from and to the Graph Node store.
@@ -231,24 +231,24 @@ Följande är ett vanligt mönster för att skapa entiteter från Ethereum-händ
 
 ```typescript
 // Importera händelseklassen Transfer som genererats från ERC20 ABI
-import { Transfer as TransferEvent } from "../generated/ERC20/ERC20";
+import { Transfer as TransferEvent } from '../generated/ERC20/ERC20'
 
 // Importera entitetstypen Transfer som genererats från GraphQL-schemat
-import { Transfer } from "../generated/schema";
+import { Transfer } from '../generated/schema'
 
 // Händelsehanterare för överföring
 export function handleTransfer(event: TransferEvent): void {
   // Skapa en Transfer-entitet, med transaktionshash som enhets-ID
-  let id = event.transaction.hash;
-  let transfer = new Transfer(id);
+  let id = event.transaction.hash
+  let transfer = new Transfer(id)
 
   // Ange egenskaper för entiteten med hjälp av händelseparametrarna
-  transfer.from = event.params.from;
-  transfer.to = event.params.to;
-  transfer.amount = event.params.amount;
+  transfer.from = event.params.from
+  transfer.to = event.params.to
+  transfer.amount = event.params.amount
 
   // Spara entiteten till lagret
-  transfer.save();
+  transfer.save()
 }
 ```
 
@@ -263,10 +263,10 @@ Each entity must have a unique ID to avoid collisions with other entities. It is
 Om en entitet redan finns kan den laddas från lagret med följande:
 
 ```typescript
-let id = event.transaction.hash; // eller hur ID konstrueras
-let transfer = Transfer.load(id);
+let id = event.transaction.hash // eller hur ID konstrueras
+let transfer = Transfer.load(id)
 if (transfer == null) {
-  transfer = new Transfer(id);
+  transfer = new Transfer(id)
 }
 
 // Använd överföringsenheten som tidigare
@@ -286,10 +286,10 @@ The store API facilitates the retrieval of entities that were created or updated
 - For some subgraphs, these missed lookups can contribute significantly to the indexing time.
 
 ```typescript
-let id = event.transaction.hash; // eller hur ID konstrueras
-let transfer = Transfer.loadInBlock(id);
+let id = event.transaction.hash // eller hur ID konstrueras
+let transfer = Transfer.loadInBlock(id)
 if (transfer == null) {
-  transfer = new Transfer(id);
+  transfer = new Transfer(id)
 }
 
 // Använd överföringsenheten som tidigare
@@ -343,7 +343,7 @@ transfer.amount = ...
 Det är också möjligt att avaktivera egenskaper med en av följande två instruktioner:
 
 ```typescript
-transfer.from.unset();
+transfer.from.unset()
 transfer.from = null
 ```
 
@@ -353,14 +353,14 @@ Updating array properties is a little more involved, as the getting an array fro
 
 ```typescript
 // Detta kommer inte att fungera
-entity.numbers.push(BigInt.fromI32(1));
-entity.save();
+entity.numbers.push(BigInt.fromI32(1))
+entity.save()
 
 // Detta kommer att fungera
-let numbers = entity.numbers;
-numbers.push(BigInt.fromI32(1));
-entity.numbers = numbers;
-entity.save();
+let numbers = entity.numbers
+numbers.push(BigInt.fromI32(1))
+entity.numbers = numbers
+entity.save()
 ```
 
 #### Ta bort entiteter från lagret
@@ -398,12 +398,12 @@ type Transfer @entity {
 and a `Transfer(address,address,uint256)` event signature on Ethereum, the `from`, `to` and `amount` values of type `address`, `address` and `uint256` are converted to `Address` and `BigInt`, allowing them to be passed on to the `Bytes!` and `BigInt!` properties of the `Transfer` entity:
 
 ```typescript
-let id = event.transaction.hash;
-let transfer = new Transfer(id);
-transfer.from = event.params.from;
-transfer.to = event.params.to;
-transfer.amount = event.params.amount;
-transfer.save();
+let id = event.transaction.hash
+let transfer = new Transfer(id)
+transfer.from = event.params.from
+transfer.to = event.params.to
+transfer.amount = event.params.amount
+transfer.save()
 ```
 
 #### Händelser och Block/Transaktionsdata
@@ -489,19 +489,16 @@ En vanlig mönster är att komma åt kontraktet från vilket en händelse härst
 
 ```typescript
 // Importera den genererade kontraktsklassen och den genererade klassen för överföringshändelser
-import {
-  ERC20Contract,
-  Transfer as TransferEvent,
-} from "../generated/ERC20Contract/ERC20Contract";
+import { ERC20Contract, Transfer as TransferEvent } from '../generated/ERC20Contract/ERC20Contract'
 // Importera den genererade entitetsklassen
-import { Transfer } from "../generated/schema";
+import { Transfer } from '../generated/schema'
 
 export function handleTransfer(event: TransferEvent) {
   // Bind kontraktet till den adress som skickade händelsen
-  let contract = ERC20Contract.bind(event.address);
+  let contract = ERC20Contract.bind(event.address)
 
   // Åtkomst till tillståndsvariabler och funktioner genom att anropa dem
-  let erc20Symbol = contract.symbol();
+  let erc20Symbol = contract.symbol()
 }
 ```
 
@@ -518,12 +515,12 @@ If the read-only methods of your contract may revert, then you should handle tha
 - For example, the Gravity contract exposes the `gravatarToOwner` method. This code would be able to handle a revert in that method:
 
 ```typescript
-let gravitera = gravitera.bind(event.address);
-let callResult = gravitera_gravatarToOwner(gravatar);
+let gravitera = gravitera.bind(event.address)
+let callResult = gravitera_gravatarToOwner(gravatar)
 if (callResult.reverted) {
-  log.info("getGravatar reverted", []);
+  log.info('getGravatar reverted', [])
 } else {
-  let owner = callResult.value;
+  let owner = callResult.value
 }
 ```
 
@@ -582,7 +579,7 @@ let isContract = ethereum.hasCode(eoa).inner // returns false
 ### API för loggning
 
 ```typescript
-import { log } from "@graphprotocol/graph-ts";
+import { log } from '@graphprotocol/graph-ts'
 ```
 
 The `log` API allows subgraphs to log information to the Graph Node standard output as well as Graph Explorer. Messages can be logged using different log levels. A basic format string syntax is provided to compose log messages from argument.
@@ -598,11 +595,7 @@ The `log` API includes the following functions:
 The `log` API takes a format string and an array of string values. It then replaces placeholders with the string values from the array. The first `{}` placeholder gets replaced by the first value in the array, the second `{}` placeholder gets replaced by the second value and so on.
 
 ```typescript
-log.info("Message to be displayed: {}, {}, {}", [
-  value.toString(),
-  anotherValue.toString(),
-  "already a string",
-]);
+log.info('Message to be displayed: {}, {}, {}', [value.toString(), anotherValue.toString(), 'already a string'])
 ```
 
 #### Loggning av ett eller flera värden
@@ -625,11 +618,11 @@ export function handleSomeEvent(event: SomeEvent): void {
 I exemplet nedan loggas endast det första värdet i argument arrayen, trots att arrayen innehåller tre värden.
 
 ```typescript
-let myArray = ["A", "B", "C"];
+let myArray = ['A', 'B', 'C']
 
 export function handleSomeEvent(event: SomeEvent): void {
   // Visar : "Mitt värde är: A" (Även om tre värden skickas till `log.info`)
-  log.info("Mitt värde är: {}", myArray);
+  log.info('Mitt värde är: {}', myArray)
 }
 ```
 
@@ -638,14 +631,11 @@ export function handleSomeEvent(event: SomeEvent): void {
 Each entry in the arguments array requires its own placeholder `{}` in the log message string. The below example contains three placeholders `{}` in the log message. Because of this, all three values in `myArray` are logged.
 
 ```typescript
-let myArray = ["A", "B", "C"];
+let myArray = ['A', 'B', 'C']
 
 export function handleSomeEvent(event: SomeEvent): void {
   // Visar: "Mitt första värde är: A, andra värdet är: B, tredje värdet är: C"
-  log.info(
-    "My first value is: {}, second value is: {}, third value is: {}",
-    myArray
-  );
+  log.info('My first value is: {}, second value is: {}, third value is: {}', myArray)
 }
 ```
 
@@ -656,7 +646,7 @@ För att visa ett specifikt värde i arrayen måste det indexeras och tillhandah
 ```typescript
 export function handleSomeEvent(event: SomeEvent): void {
   // Visar : "Mitt tredje värde är C"
-  log.info("My third value is: {}", [myArray[2]]);
+  log.info('My third value is: {}', [myArray[2]])
 }
 ```
 
@@ -665,21 +655,21 @@ export function handleSomeEvent(event: SomeEvent): void {
 I exemplet nedan loggas blocknummer, blockhash och transaktionshash från en händelse:
 
 ```typescript
-import { log } from "@graphprotocol/graph-ts";
+import { log } from '@graphprotocol/graph-ts'
 
 export function handleSomeEvent(event: SomeEvent): void {
-  log.debug("Block number: {}, block hash: {}, transaction hash: {}", [
+  log.debug('Block number: {}, block hash: {}, transaction hash: {}', [
     event.block.number.toString(), // "47596000"
     event.block.hash.toHexString(), // "0x..."
     event.transaction.hash.toHexString(), // "0x..."
-  ]);
+  ])
 }
 ```
 
 ### IPFS API
 
 ```typescript
-import { ipfs } from "@graphprotocol/graph-ts"
+import { ipfs } from '@graphprotocol/graph-ts'
 ```
 
 Smart contracts occasionally anchor IPFS files on chain. This allows mappings to obtain the IPFS hashes from the contract and read the corresponding files from IPFS. The file data will be returned as `Bytes`, which usually requires further processing, e.g. with the `json` API documented later on this page.
@@ -688,13 +678,13 @@ För att läsa en fil från IPFS med en given IPFS-hash eller sökväg görs fö
 
 ```typescript
 // Placera detta i en händelsehanterare i mappningen
-let hash = "QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D";
-let data = ipfs.cat(hash);
+let hash = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D'
+let data = ipfs.cat(hash)
 
 // Sökvägar som `QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile`
 // som inkluderar filer i kataloger stöds också
-let path = "QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile";
-let data = ipfs.cat(path);
+let path = 'QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/Makefile'
+let data = ipfs.cat(path)
 ```
 
 **Note:** `ipfs.cat` is not deterministic at the moment. If the file cannot be retrieved over the IPFS network before the request times out, it will return `null`. Due to this, it's always worth checking the result for `null`.
@@ -702,31 +692,31 @@ let data = ipfs.cat(path);
 It is also possible to process larger files in a streaming fashion with `ipfs.map`. The function expects the hash or path for an IPFS file, the name of a callback, and flags to modify its behavior:
 
 ```typescript
-import { JSONValue, Value } from "@graphprotocol/graph-ts";
+import { JSONValue, Value } from '@graphprotocol/graph-ts'
 
 export function processItem(value: JSONValue, userData: Value): void {
   // Se JSONValue-dokumentationen för mer information om hur man hanterar
   // med JSON-värden
-  let obj = value.toObject();
-  let id = obj.get("id");
-  let title = obj.get("title");
+  let obj = value.toObject()
+  let id = obj.get('id')
+  let title = obj.get('title')
 
   if (!id || !title) {
-    return;
+    return
   }
 
   // Callbacks kan också skapa enheter
-  let newItem = new Item(id);
-  newItem.title = title.toString();
-  newitem.parent = userData.toString(); // Ange parent till "parentId"
-  newitem.save();
+  let newItem = new Item(id)
+  newItem.title = title.toString()
+  newitem.parent = userData.toString() // Ange parent till "parentId"
+  newitem.save()
 }
 
 // Placera detta i en händelsehanterare i mappningen
-ipfs.map("Qm...", "processItem", Value.fromString("parentId"), ["json"]);
+ipfs.map('Qm...', 'processItem', Value.fromString('parentId'), ['json'])
 
 // Alternativt kan du använda `ipfs.mapJSON`.
-ipfs.mapJSON("Qm...", "processItem", Value.fromString("parentId"));
+ipfs.mapJSON('Qm...', 'processItem', Value.fromString('parentId'))
 ```
 
 The only flag currently supported is `json`, which must be passed to `ipfs.map`. With the `json` flag, the IPFS file must consist of a series of JSON values, one value per line. The call to `ipfs.map` will read each line in the file, deserialize it into a `JSONValue` and call the callback for each of them. The callback can then use entity operations to store data from the `JSONValue`. Entity changes are stored only when the handler that called `ipfs.map` finishes successfully; in the meantime, they are kept in memory, and the size of the file that `ipfs.map` can process is therefore limited.
@@ -736,7 +726,7 @@ On success, `ipfs.map` returns `void`. If any invocation of the callback causes
 ### Crypto API
 
 ```typescript
-import { crypto } from "@graphprotocol/graph-ts";
+import { crypto } from '@graphprotocol/graph-ts'
 ```
 
 The `crypto` API makes a cryptographic functions available for use in mappings. Right now, there is only one:
@@ -746,7 +736,7 @@ The `crypto` API makes a cryptographic functions available for use in mappings.
 ### JSON API
 
 ```typescript
-import { json, JSONValueKind } from "@graphprotocol/graph-ts"
+import { json, JSONValueKind } from '@graphprotocol/graph-ts'
 ```
 
 JSON data can be parsed using the `json` API:
diff --git a/website/pages/sv/developing/unit-testing-framework.mdx b/website/pages/sv/developing/unit-testing-framework.mdx
index 03affcca6484..1835214d90f8 100644
--- a/website/pages/sv/developing/unit-testing-framework.mdx
+++ b/website/pages/sv/developing/unit-testing-framework.mdx
@@ -61,7 +61,7 @@ eller
 <PROJECT_PATH>/node_modules/gluegun/build/index.js:13 throw up;
 ```
 
-Se till att du använder en nyare version av Node.js eftersom graph-cli inte längre stöder **v10.19.0**, och det är fortfarande standardversionen för nya Ubuntu-bilder på WSL. Till exempel är Matchstick bekräftat fungerande på WSL med **v18.1.0**. Du kan byta till den antingen via** nvm ** eller genom att uppdatera din globala Node.js. Glöm inte att ta bort `node_modules` och köra ` npm install `igen efter att du har uppdaterat Node.js! Sedan, se till att du har **libpq** installerat, du kan göra det genom att köra
+Se till att du använder en nyare version av Node.js eftersom graph-cli inte längre stöder **v10.19.0**, och det är fortfarande standardversionen för nya Ubuntu-bilder på WSL. Till exempel är Matchstick bekräftat fungerande på WSL med **v18.1.0**. Du kan byta till den antingen via** nvm ** eller genom att uppdatera din globala Node.js. Glöm inte att ta bort `node_modules` och köra `npm install`igen efter att du har uppdaterat Node.js! Sedan, se till att du har **libpq** installerat, du kan göra det genom att köra
 
 ```
 sudo apt-get install libpq-dev
@@ -1380,15 +1380,15 @@ Loggutmatningen innehåller testkörningens varaktighet. Här är ett exempel:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Motsägelsen i argumenten beror på en motsägelse i `graph-ts` och `matchstick-as`. Det bästa sättet att åtgärda problem som detta är att uppdatera allt till den senaste utgivna versionen.
diff --git a/website/pages/sv/network/benefits.mdx b/website/pages/sv/network/benefits.mdx
index 3b8ace79fa89..2ad0e58e1e1b 100644
--- a/website/pages/sv/network/benefits.mdx
+++ b/website/pages/sv/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Kostnadsjämförelse        |                Egen Värd                |                       The Graph Nätverk                       |
-|:-------------------------------:|:---------------------------------------:|:-------------------------------------------------------------:|
-| Månatlig kostnad för server\* |             $350 per månad              |                              $0                               |
-|       Kostnad för frågor        |                   $0+                   |                         $0 per month                          |
-|  Konstruktionstid<sup>†</sup>   |             $400 per månad              | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
-|        Frågor per månad         |     Begränsad till infra kapacitet      |                      100,000 (Free Plan)                      |
-|        Kostnad per fråga        |                   $0                    |                        $0<sup>‡</sup>                         |
-|          Infrastruktur          |              Centraliserad              |                        Decentraliserad                        |
-|      Geografisk redundans       |           $750+ per extra nod           |                          Inkluderat                           |
-|            Drifttid             |               Varierande                |                            99.9%+                             |
-|       Total Månadskostnad       | <span className="highlight-row" />$750+ |                              $0                               |
+| Kostnadsjämförelse | Egen Värd | The Graph Nätverk |
+| :-: | :-: | :-: |
+| Månatlig kostnad för server\* | $350 per månad | $0 |
+| Kostnad för frågor | $0+ | $0 per month |
+| Konstruktionstid<sup>†</sup> | $400 per månad | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
+| Frågor per månad | Begränsad till infra kapacitet | 100,000 (Free Plan) |
+| Kostnad per fråga | $0 | $0<sup>‡</sup> |
+| Infrastruktur | Centraliserad | Decentraliserad |
+| Geografisk redundans | $750+ per extra nod | Inkluderat |
+| Drifttid | Varierande | 99.9%+ |
+| Total Månadskostnad | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|      Kostnadsjämförelse       |                 Egen Värd                  |                       The Graph Nätverk                       |
-|:-----------------------------:|:------------------------------------------:|:-------------------------------------------------------------:|
-| Månadskostnad för server\*  |               $350 per månad               |                              $0                               |
-|      Kostnad för frågor       |               $500 per månad               |                        $120 per month                         |
-|   Ingenjörstid<sup>†</sup>    |               $800 per månad               | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
-|       Frågor per månad        |       Begränsad till infra kapacitet       |                          ~3,000,000                           |
-|       Kostnad per fråga       |                     $0                     |                           $0.00004                            |
-|         Infrastruktur         |               Centraliserad                |                        Decentraliserad                        |
-| Kostnader för ingenjörsarbete |               $200 per timme               |                          Inkluderat                           |
-|     Geografisk redundans      |  $1,200 i totala kostnader per extra nod   |                          Inkluderat                           |
-|           Drifttid            |                  Varierar                  |                            99.9%+                             |
-|      Total Månadskostnad      | <span className="highlight-row" /> $1,650+ |                             $120                              |
+| Kostnadsjämförelse | Egen Värd | The Graph Nätverk |
+| :-: | :-: | :-: |
+| Månadskostnad för server\* | $350 per månad | $0 |
+| Kostnad för frågor | $500 per månad | $120 per month |
+| Ingenjörstid<sup>†</sup> | $800 per månad | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
+| Frågor per månad | Begränsad till infra kapacitet | ~3,000,000 |
+| Kostnad per fråga | $0 | $0.00004 |
+| Infrastruktur | Centraliserad | Decentraliserad |
+| Kostnader för ingenjörsarbete | $200 per timme | Inkluderat |
+| Geografisk redundans | $1,200 i totala kostnader per extra nod | Inkluderat |
+| Drifttid | Varierar | 99.9%+ |
+| Total Månadskostnad | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|      Kostnadsjämförelse      |                  Egen Värd                  |                       The Graph Nätverk                       |
-|:----------------------------:|:-------------------------------------------:|:-------------------------------------------------------------:|
-| Månadskostnad för server\* |          $1100 per månad, per nod           |                              $0                               |
-|      Kostnad för frågor      |                    $4000                    |                       $1,200 per month                        |
-|    Antal noder som behövs    |                     10                      |                        Ej tillämpligt                         |
-|   Ingenjörstid<sup>†</sup>   |         $6,000 eller mer per månad          | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
-|       Frågor per månad       |       Begränsad till infra kapacitet        |                          ~30,000,000                          |
-|      Kostnad per fråga       |                     $0                      |                           $0.00004                            |
-|        Infrastruktur         |                Centraliserad                |                        Decentraliserad                        |
-|     Geografisk redundans     |   $1,200 i totala kostnader per extra nod   |                          Inkluderat                           |
-|           Drifttid           |                  Varierar                   |                            99.9%+                             |
-|     Total Månadskostnad      | <span className="highlight-row" /> $11,000+ |                            $1,200                             |
+| Kostnadsjämförelse | Egen Värd | The Graph Nätverk |
+| :-: | :-: | :-: |
+| Månadskostnad för server\* | $1100 per månad, per nod | $0 |
+| Kostnad för frågor | $4000 | $1,200 per month |
+| Antal noder som behövs | 10 | Ej tillämpligt |
+| Ingenjörstid<sup>†</sup> | $6,000 eller mer per månad | Ingen, inbyggd i nätverket med globalt distribuerade Indexers |
+| Frågor per månad | Begränsad till infra kapacitet | ~30,000,000 |
+| Kostnad per fråga | $0 | $0.00004 |
+| Infrastruktur | Centraliserad | Decentraliserad |
+| Geografisk redundans | $1,200 i totala kostnader per extra nod | Inkluderat |
+| Drifttid | Varierar | 99.9%+ |
+| Total Månadskostnad | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*inklusive kostnader för backup: $50-$100 per månad
 
diff --git a/website/pages/sv/network/delegating.mdx b/website/pages/sv/network/delegating.mdx
index 42363dfd0958..a342ea0e34eb 100644
--- a/website/pages/sv/network/delegating.mdx
+++ b/website/pages/sv/network/delegating.mdx
@@ -49,8 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation upphävning](/img/Delegation-Unbonding.png) _Observera avgiften
-på 0,5% i Delegation UI, samt den 28 dagar långa   upphävningsperioden._
+  ![Delegation upphävning](/img/Delegation-Unbonding.png) _Observera avgiften på 0,5% i Delegation UI, samt den 28 dagar
+  långa upphävningsperioden._
 </div>
 
 ### Att välja en pålitlig Indexer med en rättvis belöningsutbetalning till Delegater
@@ -64,9 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Edward Cut](/img/Indexing-Reward-Cut.png) *Den översta Indexet ger
-Delegater 90% av belöningarna. Den   mellersta ger Delegater 20%. Den nedersta
-ger Delegater ~83%.*
+  ![Indexing Edward Cut](/img/Indexing-Reward-Cut.png) *Den översta Indexet ger Delegater 90% av belöningarna. Den
+  mellersta ger Delegater 20%. Den nedersta ger Delegater ~83%.*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/sv/network/indexing.mdx b/website/pages/sv/network/indexing.mdx
index c249ed8f3404..c1916a3e9a8e 100644
--- a/website/pages/sv/network/indexing.mdx
+++ b/website/pages/sv/network/indexing.mdx
@@ -113,11 +113,11 @@ Indexers kan skilja sig åt genom att tillämpa avancerade tekniker för att fat
 - **Stor** - Förberedd för att indexera alla för närvarande använda subgrafer och att ta emot förfrågningar för relaterad trafik.
 
 | Konfiguration | Postgres<br />(CPU:er) | Postgres<br />(minne i GB) | Postgres<br />(disk i TB) | VM:er<br />(CPU:er) | VM:er<br />(minne i GB) |
-| ------------- |:----------------------------:|:--------------------------------:|:-------------------------------:|:-------------------------:|:-----------------------------:|
-| Liten         |              4               |                8                 |                1                |             4             |              16               |
-| Standard      |              8               |                30                |                1                |            12             |              48               |
-| Medium        |              16              |                64                |                2                |            32             |              64               |
-| Stor          |              72              |               468                |               3,5               |            48             |              184              |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Liten | 4 | 8 | 1 | 4 | 16 |
+| Standard | 8 | 30 | 1 | 12 | 48 |
+| Medium | 16 | 64 | 2 | 32 | 64 |
+| Stor | 72 | 468 | 3,5 | 48 | 184 |
 
 ### Vilka grundläggande säkerhetsåtgärder bör en Indexer vidta?
 
@@ -149,20 +149,20 @@ Observera: För att stödja smidig skalning rekommenderas det att fråge- och in
 
 #### Graf Node
 
-| Port | Syfte                                                      | Vägar                                                | CLI-argument      | Miljövariabel |
-| ---- | ---------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------- |
-| 8000 | GraphQL HTTP-server<br />(för subgraf-förfrågningar) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -             |
-| 8001 | GraphQL WS<br />(för subgraf-prenumerationer)        | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -             |
-| 8020 | JSON-RPC<br />(för hantering av distributioner)      | /                                                    | --admin-port      | -             |
-| 8030 | Subgrafindexeringsstatus-API                               | /graphql                                             | --index-node-port | -             |
-| 8040 | Prometheus-metrar                                          | /metrics                                             | --metrics-port    | -             |
+| Port | Syfte | Vägar | CLI-argument | Miljövariabel |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP-server<br />(för subgraf-förfrågningar) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(för subgraf-prenumerationer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(för hantering av distributioner) | / | --admin-port | - |
+| 8030 | Subgrafindexeringsstatus-API | /graphql | --index-node-port | - |
+| 8040 | Prometheus-metrar | /metrics | --metrics-port | - |
 
 #### Indexertjänst
 
-| Port | Syfte                                                              | Vägar                                                                   | CLI-argument   | Miljövariabel          |
-| ---- | ------------------------------------------------------------------ | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL HTTP-server<br />(för betalda subgraf-förfrågningar) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus-metrar                                                  | /metrics                                                                | --metrics-port | -                      |
+| Port | Syfte | Vägar | CLI-argument | Miljövariabel |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP-server<br />(för betalda subgraf-förfrågningar) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus-metrar | /metrics | --metrics-port | - |
 
 #### Indexeragent
 
diff --git a/website/pages/sv/new-chain-integration.mdx b/website/pages/sv/new-chain-integration.mdx
index 7902ed6f31b2..d3584aea08f5 100644
--- a/website/pages/sv/new-chain-integration.mdx
+++ b/website/pages/sv/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, i en JSON-RPC batch-begäran
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/sv/operating-graph-node.mdx b/website/pages/sv/operating-graph-node.mdx
index 83c59421c17b..65b506e574dd 100644
--- a/website/pages/sv/operating-graph-node.mdx
+++ b/website/pages/sv/operating-graph-node.mdx
@@ -77,13 +77,13 @@ En komplett exempelkonfiguration för Kubernetes finns i [indexer repository](ht
 
 När Graph Node är igång exponerar den följande portar:
 
-| Port | Syfte                                                      | Rutter                                               | Argument för CLI  | Miljö Variabel |
-| ---- | ---------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------- |
-| 8000 | GraphQL HTTP-server<br />(för frågor om undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -              |
-| 8001 | GraphQL WS<br />(för prenumerationer på undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -              |
-| 8020 | JSON-RPC<br />(för hantering av distributioner)      | /                                                    | --admin-port      | -              |
-| 8030 | Status för indexering av undergrafer API                   | /graphql                                             | --index-node-port | -              |
-| 8040 | Prometheus mätvärden                                       | /metrics                                             | --metrics-port    | -              |
+| Port | Syfte | Rutter | Argument för CLI | Miljö Variabel |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP-server<br />(för frågor om undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(för prenumerationer på undergrafer) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(för hantering av distributioner) | / | --admin-port | - |
+| 8030 | Status för indexering av undergrafer API | /graphql | --index-node-port | - |
+| 8040 | Prometheus mätvärden | /metrics | --metrics-port | - |
 
 > **Viktigt**: Var försiktig med att exponera portar offentligt - **administrationsportar** bör hållas säkra. Detta inkluderar JSON-RPC-slutpunkten för Graph Node.
 
diff --git a/website/pages/sv/querying/distributed-systems.mdx b/website/pages/sv/querying/distributed-systems.mdx
index 3143d4859eb8..365340f65a1b 100644
--- a/website/pages/sv/querying/distributed-systems.mdx
+++ b/website/pages/sv/querying/distributed-systems.mdx
@@ -84,8 +84,8 @@ Här kommer vi att använda argumentet `block: { hash: $blockHash }` för att bi
 /// Gets a list of domain names from a single block using pagination
 async function getDomainNames() {
   // Set a cap on the maximum number of items to pull.
-  let pages = 5;
-  const perPage = 1000;
+  let pages = 5
+  const perPage = 1000
 
   // The first query will get the first page of results and also get the block
   // hash so that the remainder of the queries are consistent with the first.
@@ -100,34 +100,34 @@ async function getDomainNames() {
                 hash
             }
         }
-    }`;
+    }`
 
-  let data = await graphql(listDomainsQuery, { perPage });
-  let result = data.domains.map((d) => d.name);
-  let blockHash = data._meta.block.hash;
+  let data = await graphql(listDomainsQuery, { perPage })
+  let result = data.domains.map((d) => d.name)
+  let blockHash = data._meta.block.hash
 
-  let query;
+  let query
   // Continue fetching additional pages until either we run into the limit of
   // 5 pages total (specified above) or we know we have reached the last page
   // because the page has fewer entities than a full page.
   while (data.domains.length == perPage && --pages) {
-    let lastID = data.domains[data.domains.length - 1].id;
+    let lastID = data.domains[data.domains.length - 1].id
     query = `
         query ListDomains($perPage: Int!, $lastID: ID!, $blockHash: Bytes!) {
             domains(first: $perPage, where: { id_gt: $lastID }, block: { hash: $blockHash }) {
                 name
                 id
             }
-        }`;
+        }`
 
-    data = await graphql(query, { perPage, lastID, blockHash });
+    data = await graphql(query, { perPage, lastID, blockHash })
 
     // Accumulate domain names into the result
     for (domain of data.domains) {
-      result.push(domain.name);
+      result.push(domain.name)
     }
   }
-  return result;
+  return result
 }
 ```
 
diff --git a/website/pages/sv/querying/graphql-api.mdx b/website/pages/sv/querying/graphql-api.mdx
index 89b541abf5eb..06f0568d0e53 100644
--- a/website/pages/sv/querying/graphql-api.mdx
+++ b/website/pages/sv/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** Du kan förenkla ovanstående fråga genom att ta bort `and`-operatorn och istället skicka ett underuttryck separerat med kommatecken.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltextsökförfrågningar har ett obligatoriskt fält, `text`, för att tillha
 
 Fulltextsökoperatorer:
 
-| Symbol      | Operatör   | Beskrivning                                                                                                                                     |
-| ----------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `&`     | `Och`      | För att kombinera flera söktermer till ett filter för entiteter som inkluderar alla de angivna termerna                                         |
-| &#x7c;      | `Eller`    | 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 |
-| `<->` | `Följs av` | 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 |
+| --- | --- | --- |
+| `&` | `Och` | För att kombinera flera söktermer till ett filter för entiteter som inkluderar alla de angivna termerna |
+| &#x7c; | `Eller` | 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 |
+| `<->` | `Följs av` | Ange avståndet mellan två ord. |
+| `:*` | `Prefix` | Använd prefixsöktermen för att hitta ord vars prefix matchar (2 tecken krävs.) |
 
 #### Exempel
 
diff --git a/website/pages/sv/querying/querying-best-practices.mdx b/website/pages/sv/querying/querying-best-practices.mdx
index 0acb3a3f0351..4f836b50ab52 100644
--- a/website/pages/sv/querying/querying-best-practices.mdx
+++ b/website/pages/sv/querying/querying-best-practices.mdx
@@ -79,7 +79,7 @@ However, as mentioned in ["Querying from an Application"](/querying/querying-fro
 Here's how to query The Graph with `graph-client`:
 
 ```tsx
-import { execute } from "../.graphclient";
+import { execute } from '../.graphclient'
 
 const query = `
 query GetToken($id: ID!) {
@@ -88,13 +88,13 @@ query GetToken($id: ID!) {
     owner
   }
 }
-`;
+`
 const variables = { id: '1' }
 
 async function main() {
-  const result = await execute(query, variables);
+  const result = await execute(query, variables)
   // `result` är fullständigt typad!
-  console.log(result);
+  console.log(result)
 }
 
 main()
@@ -111,15 +111,15 @@ More GraphQL client alternatives are covered in ["Querying from an Application"]
 A common (bad) practice is to dynamically build query strings as follows:
 
 ```tsx
-const id = params.id;
-const fields = ["id", "owner"];
+const id = params.id
+const fields = ['id', 'owner']
 const query = `
 query GetToken {
   token(id: ${id}) {
-    ${fields.join("\n")}
+    ${fields.join('\n')}
   }
 }
-`;
+`
 
 // Execute query...
 ```
@@ -134,9 +134,9 @@ While the above snippet produces a valid GraphQL query, **it has many drawbacks*
 For this reason, it is recommended to always write queries as static strings:
 
 ```tsx
-import { execute } from "your-favorite-graphql-client";
+import { execute } from 'your-favorite-graphql-client'
 
-const id = params.id;
+const id = params.id
 const query = `
 query GetToken($id: ID!) {
   token(id: $id) {
@@ -144,7 +144,7 @@ query GetToken($id: ID!) {
     owner
   }
 }
-`;
+`
 
 const result = await execute(query, {
   variables: {
@@ -167,9 +167,9 @@ You might want to include the `owner` field only on a particular condition.
 For this, you can leverage the `@include(if:...)` directive as follows:
 
 ```tsx
-import { execute } from "your-favorite-graphql-client";
+import { execute } from 'your-favorite-graphql-client'
 
-const id = params.id;
+const id = params.id
 const query = `
 query GetToken($id: ID!, $includeOwner: Boolean) {
   token(id: $id) {
diff --git a/website/pages/sv/querying/querying-from-an-application.mdx b/website/pages/sv/querying/querying-from-an-application.mdx
index cf26ba6cac68..d46eed0ef858 100644
--- a/website/pages/sv/querying/querying-from-an-application.mdx
+++ b/website/pages/sv/querying/querying-from-an-application.mdx
@@ -177,9 +177,9 @@ npm install @apollo/client graphql
 Query the API with the following code:
 
 ```javascript
-import { ApolloClient, InMemoryCache, gql } from "@apollo/client";
+import { ApolloClient, InMemoryCache, gql } from '@apollo/client'
 
-const APIURL = "https://api.studio.thegraph.com/query//<SUBGRAPH_NAME>/";
+const APIURL = 'https://api.studio.thegraph.com/query//<SUBGRAPH_NAME>/'
 
 const tokensQuery = `
   query {
@@ -190,20 +190,20 @@ const tokensQuery = `
       metadataURI
     }
   }
-`;
+`
 
 const client = new ApolloClient({
   uri: APIURL,
   cache: new InMemoryCache(),
-});
+})
 
 client
   .query({
     query: gql(tokensQuery),
   })
-  .then((data) => console.log("Subgraph data: ", data))
+  .then((data) => console.log('Subgraph data: ', data))
   .catch((err) => {
-    console.log("Error fetching data: ", err);
+    console.log('Error fetching data: ', err)
   })
 ```
 
@@ -223,20 +223,20 @@ const tokensQuery = `
       metadataURI
     }
   }
-`;
+`
 
 client
   .query({
     query: gql(tokensQuery),
     variables: {
       first: 10,
-      orderBy: "createdAtTimestamp",
-      orderDirection: "desc",
+      orderBy: 'createdAtTimestamp',
+      orderDirection: 'desc',
     },
   })
-  .then((data) => console.log("Subgraph data: ", data))
+  .then((data) => console.log('Subgraph data: ', data))
   .catch((err) => {
-    console.log("Error fetching data: ", err);
+    console.log('Error fetching data: ', err)
   })
 ```
 
@@ -266,9 +266,9 @@ npm install urql graphql
 Query the API with the following code:
 
 ```javascript
-import { createClient } from "urql";
+import { createClient } from 'urql'
 
-const APIURL = "https://api.thegraph.com/subgraphs/name/username/subgraphname";
+const APIURL = 'https://api.thegraph.com/subgraphs/name/username/subgraphname'
 
 const tokensQuery = `
   query {
@@ -279,11 +279,11 @@ const tokensQuery = `
       metadataURI
     }
   }
-`;
+`
 
 const client = createClient({
   url: APIURL,
-});
+})
 
 const data = await client.query(tokensQuery).toPromise()
 ```
diff --git a/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx b/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx
index afa4a7df4747..97c6bb95635a 100644
--- a/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/sv/release-notes/assemblyscript-migration-guide.mdx
@@ -91,17 +91,17 @@ maybeValue.aMethod();
 Men i den nyare versionen, eftersom värdet är nullable, måste du kontrollera, så här:
 
 ```typescript
-let maybeValue = load();
+let maybeValue = load()
 
 if (maybeValue) {
-  maybeValue.aMethod(); // `maybeValue` is not null anymore
+  maybeValue.aMethod() // `maybeValue` is not null anymore
 }
 ```
 
 Eller gör så här:
 
 ```typescript
-let maybeValue = load()!; // bryts i runtime om värdet är null
+let maybeValue = load()! // bryts i runtime om värdet är null
 
 maybeValue.aMethod()
 ```
@@ -113,8 +113,8 @@ Om du är osäker på vilken du ska välja, rekommenderar vi alltid att använda
 Tidigare kunde du använda [variabelskuggning](https://en.wikipedia.org/wiki/Variable_shadowing) och kod som detta skulle fungera:
 
 ```typescript
-let a = 10;
-let b = 20;
+let a = 10
+let b = 20
 let a = a + b
 ```
 
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Du måste döpa om dina duplicerade variabler om du hade variabelskuggning.
+
 ### Jämförelser med nollvärden
+
 När du gör uppgraderingen av din subgraf kan du ibland få fel som dessa:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 För att lösa problemet kan du helt enkelt ändra `if`-satsen till något i den här stilen:
 
 ```typescript
@@ -154,8 +158,8 @@ Samma gäller om du använder != istället för ==.
 Det vanliga sättet att göra kasting tidigare var att bara använda nyckelordet `as`, som så här:
 
 ```typescript
-let byteArray = new ByteArray(10);
-let uint8Array = byteArray as Uint8Array; // motsvarande: <Uint8Array>byteArray
+let byteArray = new ByteArray(10)
+let uint8Array = byteArray as Uint8Array // motsvarande: <Uint8Array>byteArray
 ```
 
 Detta fungerar dock endast i två scenarier:
@@ -167,8 +171,8 @@ Exempel:
 
 ```typescript
 // primitive casting
-let a: usize = 10;
-let b: isize = 5;
+let a: usize = 10
+let b: isize = 5
 let c: usize = a + (b as usize)
 ```
 
@@ -176,7 +180,7 @@ let c: usize = a + (b as usize)
 // upcasting on class inheritance
 class Bytes extends Uint8Array {}
 
-let bytes = new Bytes(2);
+let bytes = new Bytes(2)
 // <Uint8Array>bytes // same as: bytes as Uint8Array
 ```
 
@@ -189,7 +193,7 @@ Det finns två scenarier där du kan vilja casta, men att använda `as`/`<T>var`
 // downcasting om klassarv
 class Bytes extends Uint8Array {}
 
-let uint8Array = new Uint8Array(2);
+let uint8Array = new Uint8Array(2)
 // <Bytes>uint8Array // breaks in runtime :(
 ```
 
@@ -198,7 +202,7 @@ let uint8Array = new Uint8Array(2);
 class Bytes extends Uint8Array {}
 class ByteArray extends Uint8Array {}
 
-let bytes = new Bytes(2);
+let bytes = new Bytes(2)
 // <ByteArray>bytes // breaks in runtime :(
 ```
 
@@ -208,8 +212,8 @@ I dessa fall kan du använda funktionen `changetype<T>`:
 // downcasting om klassarv
 class Bytes extends Uint8Array {}
 
-let uint8Array = new Uint8Array(2);
-changetype<Bytes>(uint8Array); // works :)
+let uint8Array = new Uint8Array(2)
+changetype<Bytes>(uint8Array) // works :)
 ```
 
 ```typescript
@@ -217,18 +221,18 @@ changetype<Bytes>(uint8Array); // works :)
 class Bytes extends Uint8Array {}
 class ByteArray extends Uint8Array {}
 
-let bytes = new Bytes(2);
-changetype<ByteArray>(bytes); // works :)
+let bytes = new Bytes(2)
+changetype<ByteArray>(bytes) // works :)
 ```
 
 Om du bara vill ta bort nullability kan du fortsätta använda `as`-operatorn (eller `<T>variable`), men se till att du vet att värdet inte kan vara null, annars kommer det att bryta.
 
 ```typescript
 // ta bort ogiltighet
-let previousBalance = AccountBalance.load(balanceId); // AccountBalance | null
+let previousBalance = AccountBalance.load(balanceId) // AccountBalance | null
 
 if (previousBalance != null) {
-  return previousBalance as AccountBalance; // safe remove null
+  return previousBalance as AccountBalance // safe remove null
 }
 
 let newBalance = new AccountBalance(balanceId)
@@ -248,18 +252,18 @@ Vi har också lagt till några fler statiska metoder i vissa typer för att unde
 För att använda [nullability check feature](https://www.assemblyscript.org/basics.html#nullability-checks) kan du använda antingen `if`-satser eller den ternära operatorn (`?` och `:`) så här:
 
 ```typescript
-let something: string | null = "data";
+let something: string | null = 'data'
 
-let somethingOrElse = something ? something : "else";
+let somethingOrElse = something ? something : 'else'
 
 // or
 
-let somethingOrElse;
+let somethingOrElse
 
 if (something) {
-  somethingOrElse = something;
+  somethingOrElse = something
 } else {
-  somethingOrElse = "else";
+  somethingOrElse = 'else'
 }
 ```
 
@@ -270,10 +274,10 @@ class Container {
   data: string | null
 }
 
-let container = new Container();
-container.data = "data";
+let container = new Container()
+container.data = 'data'
 
-let somethingOrElse: string = container.data ? container.data : "else"; // Kompilerar inte
+let somethingOrElse: string = container.data ? container.data : 'else' // Kompilerar inte
 ```
 
 Vilket ger detta fel:
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 För att åtgärda problemet kan du skapa en variabel för den egenskapen så att kompilatorn kan utföra den magiska nollbarhetskontrollen:
 
 ```typescript
@@ -291,12 +296,12 @@ class Container {
   data: string | null
 }
 
-let container = new Container();
-container.data = "data";
+let container = new Container()
+container.data = 'data'
 
-let data = container.data;
+let data = container.data
 
-let somethingOrElse: string = data ? data : "else"; // kompilerar helt okej :)
+let somethingOrElse: string = data ? data : 'else' // kompilerar helt okej :)
 ```
 
 ### Operatörsöverladdning med egenskapsaccess
@@ -305,7 +310,7 @@ Om du försöker summera (till exempel) en nullable typ (från en property acces
 
 ```typescript
 class BigInt extends Uint8Array {
-  @operator("+")
+  @operator('+')
   plus(other: BigInt): BigInt {
     // ...
   }
@@ -315,26 +320,26 @@ class Wrapper {
   public constructor(public n: BigInt | null) {}
 }
 
-let x = BigInt.fromI32(2);
-let y: BigInt | null = null;
+let x = BigInt.fromI32(2)
+let y: BigInt | null = null
 
-x + y; // ge kompileringsfel om ogiltighet
+x + y // ge kompileringsfel om ogiltighet
 
-let wrapper = new Wrapper(y);
+let wrapper = new Wrapper(y)
 
-wrapper.n = wrapper.n + x; // ger inte kompileringsfel som det borde
+wrapper.n = wrapper.n + x // ger inte kompileringsfel som det borde
 ```
 
 Vi har öppnat en fråga om AssemblyScript-kompilatorn för detta, men om du gör den här typen av operationer i dina subgraf-mappningar bör du ändra dem så att de gör en null-kontroll innan den.
 
 ```typescript
-let wrapper = new Wrapper(y);
+let wrapper = new Wrapper(y)
 
 if (!wrapper.n) {
-  wrapper.n = BigInt.fromI32(0);
+  wrapper.n = BigInt.fromI32(0)
 }
 
-wrapper.n = wrapper.n + x; // nu är `n` garanterat ett BigInt
+wrapper.n = wrapper.n + x // nu är `n` garanterat ett BigInt
 ```
 
 ### Initialisering av värde
@@ -342,17 +347,17 @@ wrapper.n = wrapper.n + x; // nu är `n` garanterat ett BigInt
 Om du har någon kod som denna:
 
 ```typescript
-var value: Type; // null
-value.x = 10;
-value.y = "content"
+var value: Type // null
+value.x = 10
+value.y = 'content'
 ```
 
 Det kommer att kompilera men brytas vid körning, det händer eftersom värdet inte har initialiserats, så se till att din subgraf har initialiserat sina värden, så här:
 
 ```typescript
-var value = new Type(); // initialized
-value.x = 10;
-value.y = "content"
+var value = new Type() // initialized
+value.x = 10
+value.y = 'content'
 ```
 
 Även om du har nullable properties i en GraphQL-entitet, som denna:
@@ -367,10 +372,10 @@ type Total @entity {
 Och du har en kod som liknar den här:
 
 ```typescript
-let total = Total.load("latest");
+let total = Total.load('latest')
 
 if (total === null) {
-  total = new Total("latest")
+  total = new Total('latest')
 }
 
 total.amount = total.amount + BigInt.fromI32(1)
@@ -379,11 +384,11 @@ total.amount = total.amount + BigInt.fromI32(1)
 Du måste se till att initialisera värdet `total.amount`, för om du försöker komma åt som i den sista raden för summan, kommer det att krascha. Så antingen initialiserar du det först:
 
 ```typescript
-let total = Total.load("latest")
+let total = Total.load('latest')
 
 if (total === null) {
-  total = new Total("latest")
-  total.amount = BigInt.fromI32(0);
+  total = new Total('latest')
+  total.amount = BigInt.fromI32(0)
 }
 
 total.tokens = total.tokens + BigInt.fromI32(1)
@@ -399,10 +404,10 @@ type Total @entity {
 ```
 
 ```typescript
-let total = Total.load("latest");
+let total = Total.load('latest')
 
 if (total === null) {
-  total = new Total("latest"); // initierar redan icke-nullställbara egenskaper
+  total = new Total('latest') // initierar redan icke-nullställbara egenskaper
 }
 
 total.amount = total.amount + BigInt.fromI32(1)
@@ -430,17 +435,17 @@ export class Something {
 // or
 
 export class Something {
-  value: Thing;
+  value: Thing
 
   constructor(value: Thing) {
-    this.value = value;
+    this.value = value
   }
 }
 
 // or
 
 export class Something {
-  value!: Thing;
+  value!: Thing
 }
 ```
 
@@ -449,9 +454,9 @@ export class Something {
 Klassen `Array` accepterar fortfarande ett tal för att initiera längden på listan, men du bör vara försiktig eftersom operationer som `.push` faktiskt ökar storleken istället för att lägga till i början, till exempel:
 
 ```typescript
-let arr = new Array<string>(5); // ["", "", "", "", ""]
+let arr = new Array<string>(5) // ["", "", "", "", ""]
 
-arr.push("something"); // ["", "", "", "", "", "something"] // size 6 :(
+arr.push('something') // ["", "", "", "", "", "something"] // size 6 :(
 ```
 
 Beroende på vilka typer du använder, t.ex. nullable-typer, och hur du kommer åt dem, kan du stöta på ett runtime-fel som det här:
@@ -463,17 +468,17 @@ ERRO Handler skipped due to execution failure, error: Mapping aborted at ~lib/ar
 För att faktiskt trycka i början bör du antingen initiera `Array` med storlek noll, så här:
 
 ```typescript
-let arr = new Array<string>(0); // []
+let arr = new Array<string>(0) // []
 
-arr.push("something"); // ["something"]
+arr.push('something') // ["something"]
 ```
 
 Eller så bör du mutera den via index:
 
 ```typescript
-let arr = new Array<string>(5); // ["", "", "", "", ""]
+let arr = new Array<string>(5) // ["", "", "", "", ""]
 
-arr[0] = "something"; // ["something", "", "", "", ""]
+arr[0] = 'something' // ["something", "", "", "", ""]
 ```
 
 ### GraphQL-schema
diff --git a/website/pages/sv/sps/triggers-example.mdx b/website/pages/sv/sps/triggers-example.mdx
index f0419707408a..8140015d7721 100644
--- a/website/pages/sv/sps/triggers-example.mdx
+++ b/website/pages/sv/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Förutsättningar
diff --git a/website/pages/sv/supported-network-requirements.mdx b/website/pages/sv/supported-network-requirements.mdx
index f6c91108bac9..f7a4943afd1b 100644
--- a/website/pages/sv/supported-network-requirements.mdx
+++ b/website/pages/sv/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Nätverk   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Nätverk | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx
index 5897ae02b134..282c68973a8a 100644
--- a/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/sw/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/sw/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/sw/developing/graph-ts/api.mdx b/website/pages/sw/developing/graph-ts/api.mdx
index 8fc1f4b48b61..6a0c4e208b99 100644
--- a/website/pages/sw/developing/graph-ts/api.mdx
+++ b/website/pages/sw/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/sw/developing/unit-testing-framework.mdx b/website/pages/sw/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/sw/developing/unit-testing-framework.mdx
+++ b/website/pages/sw/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/sw/network/benefits.mdx b/website/pages/sw/network/benefits.mdx
index 9000c85bc383..7b50daa789a4 100644
--- a/website/pages/sw/network/benefits.mdx
+++ b/website/pages/sw/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                        The Graph Network                        |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|        Infrastructure        |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                        The Graph Network                        |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|        Infrastructure        |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                        The Graph Network                        |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|        Infrastructure        |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | The Graph Network |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Infrastructure | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/sw/network/indexing.mdx b/website/pages/sw/network/indexing.mdx
index 0eb017b5be3f..a6844c2da009 100644
--- a/website/pages/sw/network/indexing.mdx
+++ b/website/pages/sw/network/indexing.mdx
@@ -112,12 +112,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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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<br />(CPUs) | Postgres<br />(memory in GBs) | Postgres<br />(disk in TBs) | VMs<br />(CPUs) | VMs<br />(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?
 
@@ -149,20 +149,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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrics                                         | /metrics                                                                | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(for paid subgraph queries) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrics | /metrics | --metrics-port | - |
 
 #### Indexer Agent
 
diff --git a/website/pages/sw/new-chain-integration.mdx b/website/pages/sw/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/sw/new-chain-integration.mdx
+++ b/website/pages/sw/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/sw/operating-graph-node.mdx b/website/pages/sw/operating-graph-node.mdx
index fb3d538f952a..dbbfcd5fc545 100644
--- a/website/pages/sw/operating-graph-node.mdx
+++ b/website/pages/sw/operating-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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(for subgraph subscriptions)    | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(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<br />(for subgraph queries) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(for subgraph subscriptions) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(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.
 
diff --git a/website/pages/sw/querying/graphql-api.mdx b/website/pages/sw/querying/graphql-api.mdx
index d8671e53a77c..3dd70fc7b004 100644
--- a/website/pages/sw/querying/graphql-api.mdx
+++ b/website/pages/sw/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Description                                                                                                                          |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx b/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx
index 17224699570d..85f6903a6c69 100644
--- a/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/sw/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/sw/sps/triggers-example.mdx b/website/pages/sw/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/sw/sps/triggers-example.mdx
+++ b/website/pages/sw/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/sw/supported-network-requirements.mdx b/website/pages/sw/supported-network-requirements.mdx
index afbf755c0a5a..df15ef48d762 100644
--- a/website/pages/sw/supported-network-requirements.mdx
+++ b/website/pages/sw/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx
index 1fc26595c11d..6b0ed88435dc 100644
--- a/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/tr/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ ABI dosya(lar)ı sözleşme(ler) inizle uygun olmalıdır. ABI dosyalarını edi
 
 ## SpecVersion Sürümleri
 
-| Sürüm | Sürüm Notları                                                                                                                                                            |
-| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| Sürüm | Sürüm Notları |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
 | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-| 0.0.5 | İşleyicilerin işlem makbuzlarına erişim desteği eklendi.                                                                                                                 |
-| 0.0.4 | Subgraph özelliklerini yönetme desteği eklendi.                                                                                                                          |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | İşleyicilerin işlem makbuzlarına erişim desteği eklendi. |
+| 0.0.4 | Subgraph özelliklerini yönetme desteği eklendi. |
diff --git a/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx
index aa158eda5efa..c11d86e38b0e 100644
--- a/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/tr/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 GraphQL API'sinde desteklenen skalarlardan bazıları şunlardır:
 
-| Tür          | Tanım                                                                                                                                                                                                            |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte dizisi, onaltılık bir dizgi olarak temsil edilir. Ethereum hash değerleri ve adresleri için yaygın olarak kullanılır.                                                                                       |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Tür | Tanım |
+| --- | --- |
+| `Bytes` | Byte dizisi, onaltılık bir dizgi olarak temsil edilir. Ethereum hash değerleri ve adresleri için yaygın olarak kullanılır. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Numaralandırmalar
 
@@ -283,24 +283,24 @@ Farklı bir dil seçmek, tam metin arama API'sı üzerinde bazen az olsa da kesi
 
 Desteklenen dil sözlükleri:
 
-| Code   | Sözlük     |
-| ------ | ---------- |
-| yalın  | General    |
-| da     | Danish     |
-| nl     | Dutch      |
-| en     | English    |
-| fi     | Finnish    |
-| fr     | French     |
-| de     | German     |
-| hu     | Hungarian  |
-| it     | Italian    |
-| no     | Norwegian  |
-| pt     | Portekizce |
-| ro     | Romanian   |
-| ru     | Russian    |
-| es     | Spanish    |
-| sv     | Swedish    |
-| tr     | Turkish    |
+| Code  | Sözlük     |
+| ----- | ---------- |
+| yalın | General    |
+| da    | Danish     |
+| nl    | Dutch      |
+| en    | English    |
+| fi    | Finnish    |
+| fr    | French     |
+| de    | German     |
+| hu    | Hungarian  |
+| it    | Italian    |
+| no    | Norwegian  |
+| pt    | Portekizce |
+| ro    | Romanian   |
+| ru    | Russian    |
+| es    | Spanish    |
+| sv    | Swedish    |
+| tr    | Turkish    |
 
 ### Algoritmaları Sıralama
 
diff --git a/website/pages/tr/developing/graph-ts/api.mdx b/website/pages/tr/developing/graph-ts/api.mdx
index b8a4af72cc47..9ea83c6096c9 100644
--- a/website/pages/tr/developing/graph-ts/api.mdx
+++ b/website/pages/tr/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ Dil eşlemeleri AssemblyScript ile yazıldığından, [AssemblyScript wiki'sinde
 
 Subgraph manifestosundaki `apiVersion`, bir subgraph için Graph Düğümü tarafından çalıştırılan eşleme (mapping) API'sinin sürümünü belirtir.
 
-| Sürüm | Sürüm Notları                                                                                                                                                                                                                                                                                                |
-| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 0.0.9 | Yeni host fonksiyonları ekler: [`eth_get_balance`](#balance-of-an-address) ve [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                                                                         |
-| 0.0.8 | Bir varlığı kaydederken şemadaki alanların varlığını doğrulama mekanizması ekler.                                                                                                                                                                                                                            |
-| 0.0.7 | Ethereum türlerine `TransactionReceipt` ve `Log` sınıfları eklendi<br />Ethereum Event nesnesine `receipt` alanı eklendi                                                                                                                                                                                     |
-| 0.0.6 | Ethereum Transaction nesnesine `nonce` alanı eklendi<br />Ethereum Block nesnesine `baseFeePerGas` eklendi                                                                                                                                                                                                   |
+| Sürüm | Sürüm Notları |
+| :-: | --- |
+| 0.0.9 | Yeni host fonksiyonları ekler: [`eth_get_balance`](#balance-of-an-address) ve [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Bir varlığı kaydederken şemadaki alanların varlığını doğrulama mekanizması ekler. |
+| 0.0.7 | Ethereum türlerine `TransactionReceipt` ve `Log` sınıfları eklendi<br />Ethereum Event nesnesine `receipt` alanı eklendi |
+| 0.0.6 | Ethereum Transaction nesnesine `nonce` alanı eklendi<br />Ethereum Block nesnesine `baseFeePerGas` eklendi |
 | 0.0.5 | AssemblyScript sürümü 0.19.10'a yükseltildi (bu sürümle birlikte uyumluluğu bozabilecek değişiklikler yapılmıştır, lütfen [`Geçiş Kılavuzu`](/release-notes/assemblyscript-migration-guide) bölümüne bakın)<br />`ethereum.transaction.gasUsed`, `ethereum.transaction.gasLimit` olarak yeniden adlandırıldı |
-| 0.0.4 | Ethereum SmartContractCall nesnesine `functionSignature` alanı eklendi                                                                                                                                                                                                                                       |
-| 0.0.3 | Ethereum Call nesnesine `from` alanı eklendi<br />`etherem.call.address`, `ethereum.call.to` olarak yeniden adlandırıldı                                                                                                                                                                                     |
-| 0.0.2 | Ethereum Transaction nesnesine `input` alanı eklendi                                                                                                                                                                                                                                                         |
+| 0.0.4 | Ethereum SmartContractCall nesnesine `functionSignature` alanı eklendi |
+| 0.0.3 | Ethereum Call nesnesine `from` alanı eklendi<br />`etherem.call.address`, `ethereum.call.to` olarak yeniden adlandırıldı |
+| 0.0.2 | Ethereum Transaction nesnesine `input` alanı eklendi |
 
 ### Dahili Türler
 
@@ -241,15 +241,15 @@ export function handleTransfer(event: TransferEvent): void {
   // İşlem hash'ını olay kimliği olarak kullanarak bir Transfer varlığı oluşturun
   let id = event.transaction.hash
   let transfer = new Transfer(id)
-  
+
   // Olay parametrelerini kullanarak varlığın özelliklerini ayarlayın
   transfer.from = event.params.from
   transfer.to = event.params.to
   transfer.amount = event.params.amount
-  
+
   // Varlığı depoya kaydedin
   transfer.save()
-  }
+}
 ```
 
 Zincir işlenirken bir `Transfer` olayıyla karşılaşıldığında, oluşturulan `Transfer` türü (burada varlık türüyle adlandırma çakışmasını önlemek için `TransferEvent` olarak adlandırılmıştır) kullanılarak `handleTransfer` olay işleyicisine aktarılır. Bu tür, olayın ana işlemi ve parametreleri gibi verilere erişim sağlar.
@@ -771,44 +771,44 @@ Bir değerin türü kesin olduğunda, aşağıdaki yöntemlerden biri kullanıla
 
 ### Tip Dönüşümleri Referansı
 
-| Kaynak(lar)            | Hedef                | Dönüşüm fonksiyonu           |
-| ---------------------- | -------------------- | ---------------------------- |
-| Address                | Bytes                | yok                          |
-| Address                | String               | s.toHexString()              |
-| BigDecimal             | String               | s.toString()                 |
-| BigInt                 | BigDecimal           | s.toBigDecimal()             |
-| BigInt                 | Dizgi (onaltılık)    | s.toHexString() or s.toHex() |
-| BigInt                 | String (unicode)     | s.toString()                 |
-| BigInt                 | i32                  | s.toI32()                    |
-| Boolean                | Boolean              | yok                          |
-| Bytes (işaretli)       | BigInt               | BigInt.fromSignedBytes(s)    |
-| Bytes (işaretsiz)      | BigInt               | BigInt.fromUnsignedBytes(s)  |
-| Bytes                  | Dizgi (onaltılık)    | s.toHexString() or s.toHex() |
-| Bytes                  | String (unicode)     | s.toString()                 |
-| Bytes                  | String (base58)      | s.toBase58()                 |
-| Bytes                  | i32                  | s.toI32()                    |
-| Bytes                  | u32                  | s.toU32()                    |
-| Bytes                  | JSON                 | json.fromBytes(s)            |
-| int8                   | i32                  | yok                          |
-| int32                  | i32                  | yok                          |
-| int32                  | BigInt               | BigInt.fromI32(s)            |
-| uint24                 | i32                  | yok                          |
-| int64 - int256         | BigInt               | yok                          |
-| uint32 - uint256       | BigInt               | yok                          |
-| JSON                   | boolean              | s.toBool()                   |
-| JSON                   | i64                  | s.toI64()                    |
-| JSON                   | u64                  | s.toU64()                    |
-| JSON                   | f64                  | s.toF64()                    |
-| JSON                   | BigInt               | s.toBigInt()                 |
-| JSON                   | string               | s.toString()                 |
-| JSON                   | Array                | s.toArray()                  |
-| JSON                   | Object               | s.toObject()                 |
-| String                 | Address              | Address.fromString(s)        |
-| Bytes                  | Address              | Address.fromBytes(s)         |
-| String                 | BigInt               | BigInt.fromString(s)         |
-| String                 | BigDecimal           | BigDecimal.fromString(s)     |
-| Dizgi (onaltılık)      | Bytes                | ByteArray.fromHexString(s)   |
-| String (UTF-8)         | Bytes                | ByteArray.fromUTF8(s)        |
+| Kaynak(lar)       | Hedef             | Dönüşüm fonksiyonu           |
+| ----------------- | ----------------- | ---------------------------- |
+| Address           | Bytes             | yok                          |
+| Address           | String            | s.toHexString()              |
+| BigDecimal        | String            | s.toString()                 |
+| BigInt            | BigDecimal        | s.toBigDecimal()             |
+| BigInt            | Dizgi (onaltılık) | s.toHexString() or s.toHex() |
+| BigInt            | String (unicode)  | s.toString()                 |
+| BigInt            | i32               | s.toI32()                    |
+| Boolean           | Boolean           | yok                          |
+| Bytes (işaretli)  | BigInt            | BigInt.fromSignedBytes(s)    |
+| Bytes (işaretsiz) | BigInt            | BigInt.fromUnsignedBytes(s)  |
+| Bytes             | Dizgi (onaltılık) | s.toHexString() or s.toHex() |
+| Bytes             | String (unicode)  | s.toString()                 |
+| Bytes             | String (base58)   | s.toBase58()                 |
+| Bytes             | i32               | s.toI32()                    |
+| Bytes             | u32               | s.toU32()                    |
+| Bytes             | JSON              | json.fromBytes(s)            |
+| int8              | i32               | yok                          |
+| int32             | i32               | yok                          |
+| int32             | BigInt            | BigInt.fromI32(s)            |
+| uint24            | i32               | yok                          |
+| int64 - int256    | BigInt            | yok                          |
+| uint32 - uint256  | BigInt            | yok                          |
+| JSON              | boolean           | s.toBool()                   |
+| JSON              | i64               | s.toI64()                    |
+| JSON              | u64               | s.toU64()                    |
+| JSON              | f64               | s.toF64()                    |
+| JSON              | BigInt            | s.toBigInt()                 |
+| JSON              | string            | s.toString()                 |
+| JSON              | Array             | s.toArray()                  |
+| JSON              | Object            | s.toObject()                 |
+| String            | Address           | Address.fromString(s)        |
+| Bytes             | Address           | Address.fromBytes(s)         |
+| String            | BigInt            | BigInt.fromString(s)         |
+| String            | BigDecimal        | BigDecimal.fromString(s)     |
+| Dizgi (onaltılık) | Bytes             | ByteArray.fromHexString(s)   |
+| String (UTF-8)    | Bytes             | ByteArray.fromUTF8(s)        |
 
 ### Veri Kaynağı Meta Verileri
 
diff --git a/website/pages/tr/developing/unit-testing-framework.mdx b/website/pages/tr/developing/unit-testing-framework.mdx
index 85ebc99baaae..379ab4aaa125 100644
--- a/website/pages/tr/developing/unit-testing-framework.mdx
+++ b/website/pages/tr/developing/unit-testing-framework.mdx
@@ -1114,7 +1114,7 @@ test('ethereum/sözleşme dataSource oluşturma örneği', () => {
   // 0xA16081F360e3847006dB660bae1c6d1b2e17eC2A adresiyle yeni bir GraphTokenLockWallet veri kaynağı oluştur
   GraphTokenLockWallet.create(Address.fromString('0xA16081F360e3847006dB660bae1c6d1b2e17eC2A'))
 
-  // datSource oluşturulduğunu doğrula  
+  // datSource oluşturulduğunu doğrula
   assert.dataSourceCount('GraphTokenLockWallet', 1)
 
   // İkinci dataSource'u bağlamıyla ekle
@@ -1221,7 +1221,7 @@ export function handleMetadata(content: Bytes): void {
   // dataSource.stringParams() File Veri Kaynağı CID'sini döndürür
   // stringParam() işleyici testinde taklit edilecektir
   // daha fazla bilgi için https://thegraph.com/docs/en/developing/creating-a-subgraph/#create-a-new-handler-to-process-files
-process-files
+  process - files
   let tokenMetadata = new TokenLockMetadata(dataSource.stringParam())
   const value = json.fromBytes(content).toObject()
 
@@ -1381,15 +1381,15 @@ Tutulan kayıt çıktısı test çalışma süresini içerir. İşte buna bir ö
 Bu hata kodunuzda `console.log` kullandığınız anlamına gelir. Bu komut AssemblyScript tarafından desteklenmez. Lütfen [Logging API](/developing/graph-ts/api/#logging-api)'yi kullanmayı düşünün.
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 Argümanlardaki uyumsuzluk, `graph-ts` ve `matchstick-as` arasındaki uyumsuzluktan kaynaklanır. Bu gibi sorunları düzeltmenin en iyi yolu her şeyi en son yayınlanan sürüme güncellemektir.
diff --git a/website/pages/tr/network/benefits.mdx b/website/pages/tr/network/benefits.mdx
index 282c68f00f68..60bed9f2847a 100644
--- a/website/pages/tr/network/benefits.mdx
+++ b/website/pages/tr/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                            Graph Ağı                            |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|           Altyapı            |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | Graph Ağı |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Altyapı | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                            Graph Ağı                            |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|           Altyapı            |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | Graph Ağı |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Altyapı | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                            Graph Ağı                            |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|           Altyapı            |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | Graph Ağı |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Altyapı | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/tr/network/indexing.mdx b/website/pages/tr/network/indexing.mdx
index a9c25ebeee43..27984b79fe2a 100644
--- a/website/pages/tr/network/indexing.mdx
+++ b/website/pages/tr/network/indexing.mdx
@@ -112,12 +112,12 @@ Indexers may differentiate themselves by applying advanced techniques for making
 - **Orta** - 100 subgraph ve saniyede 200-500 isteği destekleyen Üretim İndeksleyici.
 - **Yüksek** - Şu anda kullanılan tüm subgraphları indekslemek ve ilgili trafik için istekleri sunmak için hazırlanmıştır.
 
-| Kurulum  | Postgres<br />(CPU'lar) | Postgres<br />(GB cinsinden bellek) | Postgres<br />(TB cinsinden disk) | VM'ler<br />(CPU'lar) | VM'ler<br />(GB cinsinden bellek) |
-| -------- |:-----------------------------:|:-----------------------------------------:|:---------------------------------------:|:---------------------------:|:---------------------------------------:|
-| Düşük    |               4               |                     8                     |                    1                    |              4              |                   16                    |
-| Standart |               8               |                    30                     |                    1                    |             12              |                   48                    |
-| Orta     |              16               |                    64                     |                    2                    |             32              |                   64                    |
-| Yüksek   |              72               |                    468                    |                   3.5                   |             48              |                   184                   |
+| Kurulum | Postgres<br />(CPU'lar) | Postgres<br />(GB cinsinden bellek) | Postgres<br />(TB cinsinden disk) | VM'ler<br />(CPU'lar) | VM'ler<br />(GB cinsinden bellek) |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Düşük | 4 | 8 | 1 | 4 | 16 |
+| Standart | 8 | 30 | 1 | 12 | 48 |
+| Orta | 16 | 64 | 2 | 32 | 64 |
+| Yüksek | 72 | 468 | 3.5 | 48 | 184 |
 
 ### Bir İndeksleyicinin alması gereken bazı temel güvenlik önlemleri nelerdir?
 
@@ -149,20 +149,20 @@ Not: Çevik ölçeklendirmeyi desteklemek için, sorgulama ve indeksleme endişe
 
 #### Graph Node
 
-| Port | Amaç                                                        | Rotalar                                              | CLI Argümanı      | Ortam Değişkeni |
-| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
-| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
-| 8001 | GraphQL WS<br />( subgraph abonelikleri için)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
-| 8020 | JSON-RPC<br />(dağıtımları yönetmek için)             | /                                                    | --admin-port      | -               |
-| 8030 | Subgraph indeksleme durum API'si                            | /graphql                                             | --index-node-port | -               |
-| 8040 | Prometheus metrikleri                                       | /metrics                                             | --metrics-port    | -               |
+| Port | Amaç | Rotalar | CLI Argümanı | Ortam Değişkeni |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />( subgraph abonelikleri için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(dağıtımları yönetmek için) | / | --admin-port | - |
+| 8030 | Subgraph indeksleme durum API'si | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrikleri | /metrics | --metrics-port | - |
 
 #### İndeksleyici Hizmeti
 
-| Port | Amaç                                                               | Rotalar                                                                 | CLI Argümanı   | Ortam Değişkeni        |
-| ---- | ------------------------------------------------------------------ | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL HTTP sunucusu<br />(ücretli subgraph sorguları için) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus metrikleri                                              | /metrics                                                                | --metrics-port | -                      |
+| Port | Amaç | Rotalar | CLI Argümanı | Ortam Değişkeni |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP sunucusu<br />(ücretli subgraph sorguları için) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus metrikleri | /metrics | --metrics-port | - |
 
 #### İndeksleyici Aracı
 
diff --git a/website/pages/tr/new-chain-integration.mdx b/website/pages/tr/new-chain-integration.mdx
index 9f2bc45f75cd..f9553b1ba605 100644
--- a/website/pages/tr/new-chain-integration.mdx
+++ b/website/pages/tr/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, bir JSON-RPC toplu talebinde
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/tr/operating-graph-node.mdx b/website/pages/tr/operating-graph-node.mdx
index 7112df5b91c5..7a9039808b81 100644
--- a/website/pages/tr/operating-graph-node.mdx
+++ b/website/pages/tr/operating-graph-node.mdx
@@ -77,13 +77,13 @@ Tam Kubernetes örnek yapılandırması [indeksleyici Github deposunda](https://
 
 Graph Düğümü çalışırken aşağıdaki portları açar:
 
-| Port | Amaç                                                        | Rotalar                                              | CLI Argümanı      | Ortam Değişkeni |
-| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
-| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
-| 8001 | GraphQL WS<br />( subgraph abonelikleri için)         | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
-| 8020 | JSON-RPC<br />(dağıtımları yönetmek için)             | /                                                    | --admin-port      | -               |
-| 8030 | Subgraph indeksleme durum API'si                            | /graphql                                             | --index-node-port | -               |
-| 8040 | Prometheus metrikleri                                       | /metrics                                             | --metrics-port    | -               |
+| Port | Amaç | Rotalar | CLI Argümanı | Ortam Değişkeni |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP sunucusu<br />( subgraph sorguları için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />( subgraph abonelikleri için) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(dağıtımları yönetmek için) | / | --admin-port | - |
+| 8030 | Subgraph indeksleme durum API'si | /graphql | --index-node-port | - |
+| 8040 | Prometheus metrikleri | /metrics | --metrics-port | - |
 
 > **Önemli**: Bağlantı noktalarını herkese açık olarak açarken dikkatli olun - **yönetim portları** kilitli tutulmalıdır. Bu, Graph Düğümü JSON-RPC uç noktasını içerir.
 
diff --git a/website/pages/tr/querying/graphql-api.mdx b/website/pages/tr/querying/graphql-api.mdx
index 54a450425b25..c43734c04dd1 100644
--- a/website/pages/tr/querying/graphql-api.mdx
+++ b/website/pages/tr/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** Yukarıdaki sorguyu, virgülle ayrılmış bir alt ifade geçirerek, `and` operatörünü kaldırarak basitleştirebilirsiniz.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Tam metin arama sorgularının kullanması gereken bir zorunlu alanı vardır, b
 
 Tam metin arama operatörleri:
 
-| Symbol      | Operator    | Tanım                                                                                                                                |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 | Tanım |
+| --- | --- | --- |
+| `&` | `And` | For combining multiple search terms into a filter for entities that include all of the provided terms |
+| &#x7c; | `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.) |
 
 #### Örnekler
 
diff --git a/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx b/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx
index fd305a2ca624..a8bb2e376807 100644
--- a/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/tr/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/tr/sps/triggers-example.mdx b/website/pages/tr/sps/triggers-example.mdx
index 4301c586e460..219363637aaa 100644
--- a/website/pages/tr/sps/triggers-example.mdx
+++ b/website/pages/tr/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Ön Koşullar
diff --git a/website/pages/tr/supported-network-requirements.mdx b/website/pages/tr/supported-network-requirements.mdx
index 73adcca0dded..5329c6b9dad2 100644
--- a/website/pages/tr/supported-network-requirements.mdx
+++ b/website/pages/tr/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Ağ        | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Ağ | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx
index 46d489f24d76..0100b66c4427 100644
--- a/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/uk/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The ABI file(s) must match your contract(s). There are a few ways to obtain ABI
 
 ## SpecVersion Releases
 
-| Version | Release notes                                                                                                                                                            |
-| :-----: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|  1.2.0  | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|  1.1.0  | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|  1.0.0  | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|  0.0.9  | Supports `endBlock` feature                                                                                                                                              |
-|  0.0.8  | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|  0.0.7  | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|  0.0.6  | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|  0.0.5  | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|  0.0.4  | Added support for managing subgraph features.                                                                                                                            |
+| Version | Release notes |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx
index 3df39853f82b..90036d1bfab9 100644
--- a/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/uk/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Type         | Description                                                                                                                                                                                                      |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses.                                                                                                                |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Type | Description |
+| --- | --- |
+| `Bytes` | Byte array, represented as a hexadecimal string. Commonly used for Ethereum hashes and addresses. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/uk/developing/graph-ts/api.mdx b/website/pages/uk/developing/graph-ts/api.mdx
index 8fc1f4b48b61..6a0c4e208b99 100644
--- a/website/pages/uk/developing/graph-ts/api.mdx
+++ b/website/pages/uk/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Version | Release notes                                                                                                                                                                                                                                 |
-| :-----: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|  0.0.9  | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|  0.0.8  | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|  0.0.7  | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|  0.0.6  | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|  0.0.5  | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|  0.0.4  | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|  0.0.3  | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|  0.0.2  | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Version | Release notes |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Built-in Types
 
diff --git a/website/pages/uk/developing/unit-testing-framework.mdx b/website/pages/uk/developing/unit-testing-framework.mdx
index 53a5c43dedcf..553eec2157b3 100644
--- a/website/pages/uk/developing/unit-testing-framework.mdx
+++ b/website/pages/uk/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/uk/network/benefits.mdx b/website/pages/uk/network/benefits.mdx
index b37047538c52..2ab73dd7d7ba 100644
--- a/website/pages/uk/network/benefits.mdx
+++ b/website/pages/uk/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|        Порівняння вартості послуг         |            Самостійний хостинг             |                           Graph мережа                            |
-|:-----------------------------------------:|:------------------------------------------:|:-----------------------------------------------------------------:|
-|       Щомісячна плата за сервер\*       |               $350 на місяць               |                                $0                                 |
-|             Вартість запитів              |                    $0+                     |                           $0 per month                            |
-| Час технічного обслуговування<sup>†</sup> |               $400 на місяць               | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
-|        Кількість запитів за місяць        | Обмежується інфраструктурними можливостями |                        100,000 (Free Plan)                        |
-|          Вартість одного запиту           |                     $0                     |                          $0<sup>‡</sup>                           |
-|              Інфраструктура               |               Централізована               |                         Децентралізована                          |
-|         Географічне резервування          |       $750+ за кожну додаткову ноду        |                             Включено                              |
-|          Час безвідмовної роботи          |                 Варіюється                 |                              99.9%+                               |
-|      Загальна сума щомісячних витрат      |  <span className="highlight-row" />$750+   |                                $0                                 |
+| Порівняння вартості послуг | Самостійний хостинг | Graph мережа |
+| :-: | :-: | :-: |
+| Щомісячна плата за сервер\* | $350 на місяць | $0 |
+| Вартість запитів | $0+ | $0 per month |
+| Час технічного обслуговування<sup>†</sup> | $400 на місяць | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
+| Кількість запитів за місяць | Обмежується інфраструктурними можливостями | 100,000 (Free Plan) |
+| Вартість одного запиту | $0 | $0<sup>‡</sup> |
+| Інфраструктура | Централізована | Децентралізована |
+| Географічне резервування | $750+ за кожну додаткову ноду | Включено |
+| Час безвідмовної роботи | Варіюється | 99.9%+ |
+| Загальна сума щомісячних витрат | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|        Порівняння вартості послуг         |               Самостійний хостинг               |                           Graph мережа                            |
-|:-----------------------------------------:|:-----------------------------------------------:|:-----------------------------------------------------------------:|
-|       Щомісячна плата за сервер\*       |                 $350 на місяць                  |                                $0                                 |
-|             Вартість запитів              |                 $500 на місяць                  |                          $120 per month                           |
-| Час технічного обслуговування<sup>†</sup> |                 $800 на місяць                  | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
-|        Кількість запитів за місяць        |   Обмежується інфраструктурними можливостями    |                            ~3,000,000                             |
-|          Вартість одного запиту           |                       $0                        |                             $0.00004                              |
-|              Інфраструктура               |                 Централізована                  |                         Децентралізована                          |
-|        Інженерно-технічні витрати         |                 $200 на годину                  |                             Включено                              |
-|         Географічне резервування          | $1,200 загальних витрат на кожну додаткову ноду |                             Включено                              |
-|          Час безвідмовної роботи          |                   Варіюється                    |                              99.9%+                               |
-|      Загальна сума щомісячних витрат      |   <span className="highlight-row" /> $1,650+    |                               $120                                |
+| Порівняння вартості послуг | Самостійний хостинг | Graph мережа |
+| :-: | :-: | :-: |
+| Щомісячна плата за сервер\* | $350 на місяць | $0 |
+| Вартість запитів | $500 на місяць | $120 per month |
+| Час технічного обслуговування<sup>†</sup> | $800 на місяць | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
+| Кількість запитів за місяць | Обмежується інфраструктурними можливостями | ~3,000,000 |
+| Вартість одного запиту | $0 | $0.00004 |
+| Інфраструктура | Централізована | Децентралізована |
+| Інженерно-технічні витрати | $200 на годину | Включено |
+| Географічне резервування | $1,200 загальних витрат на кожну додаткову ноду | Включено |
+| Час безвідмовної роботи | Варіюється | 99.9%+ |
+| Загальна сума щомісячних витрат | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|        Порівняння вартості послуг         |               Самостійний хостинг               |                           Graph мережа                            |
-|:-----------------------------------------:|:-----------------------------------------------:|:-----------------------------------------------------------------:|
-|       Щомісячна плата за сервер\*       |          $1100 на місяць, за одну ноду          |                                $0                                 |
-|             Вартість запитів              |                      $4000                      |                         $1,200 per month                          |
-|         Кількість необхідних нод          |                       10                        |                           Не стосується                           |
-| Час технічного обслуговування<sup>†</sup> |            $6,000 і більше на місяць            | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
-|        Кількість запитів за місяць        |   Обмежується інфраструктурними можливостями    |                            ~30,000,000                            |
-|          Вартість одного запиту           |                       $0                        |                             $0.00004                              |
-|              Інфраструктура               |                 Централізована                  |                         Децентралізована                          |
-|         Географічне резервування          | $1,200 загальних витрат на кожну додаткову ноду |                             Включено                              |
-|          Час безвідмовної роботи          |                   Варіюється                    |                              99.9%+                               |
-|      Загальна сума щомісячних витрат      |   <span className="highlight-row" /> $11,000+   |                              $1,200                               |
+| Порівняння вартості послуг | Самостійний хостинг | Graph мережа |
+| :-: | :-: | :-: |
+| Щомісячна плата за сервер\* | $1100 на місяць, за одну ноду | $0 |
+| Вартість запитів | $4000 | $1,200 per month |
+| Кількість необхідних нод | 10 | Не стосується |
+| Час технічного обслуговування<sup>†</sup> | $6,000 і більше на місяць | Немає, вбудовані в мережу з глобально розподіленими індексаторами |
+| Кількість запитів за місяць | Обмежується інфраструктурними можливостями | ~30,000,000 |
+| Вартість одного запиту | $0 | $0.00004 |
+| Інфраструктура | Централізована | Децентралізована |
+| Географічне резервування | $1,200 загальних витрат на кожну додаткову ноду | Включено |
+| Час безвідмовної роботи | Варіюється | 99.9%+ |
+| Загальна сума щомісячних витрат | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*включаючи витрати на резервне копіювання: $50-$100 на місяць
 
diff --git a/website/pages/uk/network/delegating.mdx b/website/pages/uk/network/delegating.mdx
index 8327acb60b7b..be1802797a9a 100644
--- a/website/pages/uk/network/delegating.mdx
+++ b/website/pages/uk/network/delegating.mdx
@@ -49,7 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Зверніть увагу на комісію в розмірі 0,5% в Інтерфейсі для делегацій, а також на 28-денний період розблокування._
+  ![Delegation unbonding](/img/Delegation-Unbonding.png) _Зверніть увагу на комісію в розмірі 0,5% в Інтерфейсі для
+  делегацій, а також на 28-денний період розблокування._
 </div>
 
 ### Вибір надійного індексатора зі справедливою винагородою для делегатів
@@ -63,7 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Найкращий індексатор віддає делегатам 90% від суми винагороди. Середній - 20%. Найменший індексатор дає ~83%. *
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *Найкращий індексатор віддає делегатам 90% від суми винагороди.
+  Середній - 20%. Найменший індексатор дає ~83%. *
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/uk/network/indexing.mdx b/website/pages/uk/network/indexing.mdx
index 8c30f75568e8..d9f39f72fe02 100644
--- a/website/pages/uk/network/indexing.mdx
+++ b/website/pages/uk/network/indexing.mdx
@@ -113,11 +113,11 @@ Query fees are collected by the gateway and distributed to indexers according to
 - **Large** - підготовлений для індексації всіх підграфів, що використовуються наразі, і обслуговування запитів на відповідний трафік.
 
 | Налаштування | Postgres<br />(CPU) | Postgres<br />(пам'ять в GB) | Postgres<br />(диск у ТБ) | VMs<br />(Центральні CPU) | VMs<br />(пам'ять у ГБ) |
-| ------------ |:-------------------------:|:----------------------------------:|:-------------------------------:|:-------------------------------:|:-----------------------------:|
-| 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 |
 
 ### Яких основних заходів безпеки повинен дотримуватися індексатор?
 
@@ -149,26 +149,26 @@ Query fees are collected by the gateway and distributed to indexers according to
 
 #### Graph Node
 
-| Порт | Призначення                                               | Розташування                                         | Аргумент CLI      | Перемінна оточення |
-| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
-| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт       | -                  |
-| 8001 | GraphQL WS<br />(для підписок на підграфи)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
-| 8020 | JSON-RPC<br />(для керування розгортаннями)         | /                                                    | --admin-port      | -                  |
-| 8030 | API стану індексації підграфів                            | /graphql                                             | --index-node-port | -                  |
-| 8040 | Метрики Prometheus                                        | /metrics                                             | --metrics-port    | -                  |
+| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
+| --- | --- | --- | --- | --- |
+| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт | - |
+| 8001 | GraphQL WS<br />(для підписок на підграфи) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(для керування розгортаннями) | / | --admin-port | - |
+| 8030 | API стану індексації підграфів | /graphql | --index-node-port | - |
+| 8040 | Метрики Prometheus | /metrics | --metrics-port | - |
 
 #### Служба індексації
 
-| Порт | Призначення                                                       | Розташування                                                            | Аргумент CLI   | Перемінна оточення     |
-| ---- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | HTTP-сервер GraphQL<br />(для платних запитів до підграфів) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Метрики Prometheus                                                | /metrics                                                                | --metrics-port | -                      |
+| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
+| --- | --- | --- | --- | --- |
+| 7600 | HTTP-сервер GraphQL<br />(для платних запитів до підграфів) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Метрики Prometheus | /metrics | --metrics-port | - |
 
 #### Агент індексації
 
-| Порт | Призначення                    | Розташування | Аргумент CLI              | Перемінна оточення                      |
-| ---- | ------------------------------ | ------------ | ------------------------- | --------------------------------------- |
-| 8000 | API для керування індексатором | /            | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
+| --- | --- | --- | --- | --- |
+| 8000 | API для керування індексатором | / | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
 
 ### Налаштування серверної інфраструктури з використанням Terraform на Google Cloud
 
diff --git a/website/pages/uk/new-chain-integration.mdx b/website/pages/uk/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/uk/new-chain-integration.mdx
+++ b/website/pages/uk/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/uk/operating-graph-node.mdx b/website/pages/uk/operating-graph-node.mdx
index cd8118b275b7..30a9ee532653 100644
--- a/website/pages/uk/operating-graph-node.mdx
+++ b/website/pages/uk/operating-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:
 
-| Порт | Призначення                                               | Розташування                                         | Аргумент CLI      | Перемінна оточення |
-| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | ------------------ |
-| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт       | -                  |
-| 8001 | GraphQL WS<br />(для підписок на підграфи)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                  |
-| 8020 | JSON-RPC<br />(для керування розгортаннями)         | /                                                    | --admin-port      | -                  |
-| 8030 | API стану індексації підграфів                            | /graphql                                             | --index-node-port | -                  |
-| 8040 | Метрики Prometheus                                        | /metrics                                             | --metrics-port    | -                  |
+| Порт | Призначення | Розташування | Аргумент CLI | Перемінна оточення |
+| --- | --- | --- | --- | --- |
+| 8000 | HTTP-сервер GraphQL<br />(для запитів до підграфів) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-порт | - |
+| 8001 | GraphQL WS<br />(для підписок на підграфи) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(для керування розгортаннями) | / | --admin-port | - |
+| 8030 | API стану індексації підграфів | /graphql | --index-node-port | - |
+| 8040 | Метрики Prometheus | /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.
 
diff --git a/website/pages/uk/querying/graphql-api.mdx b/website/pages/uk/querying/graphql-api.mdx
index d8671e53a77c..3dd70fc7b004 100644
--- a/website/pages/uk/querying/graphql-api.mdx
+++ b/website/pages/uk/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext search operators:
 
-| Symbol      | Operator    | Description                                                                                                                          |
-| ----------- | ----------- | ------------------------------------------------------------------------------------------------------------------------------------ |
-| `&`     | `And`       | For combining multiple search terms into a filter for entities that include all of the provided terms                                |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx b/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx
index 17224699570d..85f6903a6c69 100644
--- a/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/uk/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 You'll need to rename your duplicate variables if you had variable shadowing.
+
 ### Null Comparisons
+
 By doing the upgrade on your subgraph, sometimes you might get errors like these:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 To solve you can simply change the `if` statement to something like this:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 To fix this issue, you can create a variable for that property access so that the compiler can do the nullability check magic:
 
 ```typescript
diff --git a/website/pages/uk/sps/triggers-example.mdx b/website/pages/uk/sps/triggers-example.mdx
index 495298871a22..bb278b7f0eee 100644
--- a/website/pages/uk/sps/triggers-example.mdx
+++ b/website/pages/uk/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Prerequisites
diff --git a/website/pages/uk/supported-network-requirements.mdx b/website/pages/uk/supported-network-requirements.mdx
index afbf755c0a5a..df15ef48d762 100644
--- a/website/pages/uk/supported-network-requirements.mdx
+++ b/website/pages/uk/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Network   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Network | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/ur/chain-integration-overview.mdx b/website/pages/ur/chain-integration-overview.mdx
index 43b53094048a..6230099cd0f5 100644
--- a/website/pages/ur/chain-integration-overview.mdx
+++ b/website/pages/ur/chain-integration-overview.mdx
@@ -7,8 +7,7 @@ title: چین انٹیگریشن کے عمل کا جائزہ
 ## مرحلہ 1. تکنیکی انٹیگریشن
 
 - Please visit [New Chain Integration](/new-chain-integration) for information on `graph-node` support for new chains.
-- ٹیمیں فورم تھریڈ بنا کر پروٹوکول انٹیگریشن کا عمل شروع کرتی ہیں [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)(گورننس اور GIPs کے تحت نئے ڈیٹا ذرائع ذیلی زمرہ)
-  ۔ پہلے سے طے شدہ فورم ٹیمپلیٹ کا استعمال لازمی ہے.
+- ٹیمیں فورم تھریڈ بنا کر پروٹوکول انٹیگریشن کا عمل شروع کرتی ہیں [here](https://forum.thegraph.com/c/governance-gips/new-chain-support/71)(گورننس اور GIPs کے تحت نئے ڈیٹا ذرائع ذیلی زمرہ) ۔ پہلے سے طے شدہ فورم ٹیمپلیٹ کا استعمال لازمی ہے.
 
 ## مرحلہ 2۔ انٹیگریشن کی توثیق
 
diff --git a/website/pages/ur/cookbook/cosmos.mdx b/website/pages/ur/cookbook/cosmos.mdx
index 19ef50e2ca0d..64a25e1cef88 100644
--- a/website/pages/ur/cookbook/cosmos.mdx
+++ b/website/pages/ur/cookbook/cosmos.mdx
@@ -165,7 +165,7 @@ class Any {
 
 ہر ہینڈلر کی قسم اس کے اپنے ڈیٹا ڈھانچے کے ساتھ آتی ہے جو میپنگ فنکشن کی دلیل کے طور پر پاس کی جاتی ہے.
 
-- بلاک ہینڈلرز کو ` Block ` قسم موصول ہوتی ہے.
+- بلاک ہینڈلرز کو `Block` قسم موصول ہوتی ہے.
 - ایونٹ ہینڈلرز کو `EventData` قسم موصول ہوتی ہے.
 - ٹرانزیکشن ہینڈلرز کو `TransactionData` قسم موصول ہوتی ہے.
 - میسج ہینڈلرز کو `MessageData` قسم موصول ہوتی ہے.
diff --git a/website/pages/ur/cookbook/near.mdx b/website/pages/ur/cookbook/near.mdx
index 30855c266732..2ce706542d8c 100644
--- a/website/pages/ur/cookbook/near.mdx
+++ b/website/pages/ur/cookbook/near.mdx
@@ -70,7 +70,7 @@ dataSources:
       file: ./src/mapping.ts # link to the file with the Assemblyscript mappings
 ```
 
-- NEAR سب گراف ڈیٹا ماخذ کا ایک نیا ` kind ` متعارف کراتے ہیں (`near`)
+- NEAR سب گراف ڈیٹا ماخذ کا ایک نیا `kind` متعارف کراتے ہیں (`near`)
 - The `network` should correspond to a network on the hosting Graph Node. On Subgraph Studio, NEAR's mainnet is `near-mainnet`, and NEAR's testnet is `near-testnet`
 - NEAR data sources introduce an optional `source.account` field, which is a human-readable ID corresponding to a [NEAR account](https://docs.near.org/concepts/protocol/account-model). This can be an account or a sub-account.
 - NEAR ڈیٹا کے ذرائع ایک متبادل اختیاری `source.accounts` فیلڈ متعارف کراتے ہیں، جس میں اختیاری لاحقے اور سابقے ہوتے ہیں۔ کم از کم سابقہ ​​یا لاحقہ متعین ہونا ضروری ہے، وہ بالترتیب اقدار کی فہرست کے ساتھ شروع یا ختم ہونے والے کسی بھی اکاؤنٹ سے مماثل ہوں گے۔ نیچے دی گئی مثال مماثل ہوگی: `[app|good].*[morning.near|morning.testnet]`۔ اگر صرف سابقوں یا لاحقوں کی فہرست ضروری ہو تو دوسری فیلڈ کو چھوڑا جا سکتا ہے.
@@ -254,7 +254,7 @@ NEAR سپورٹ بیٹا میں ہے، جس کا مطلب ہے کہ API میں 
 
 ### کیا رسید ہینڈلرز اکاؤنٹس اور ان کے سب اکاؤنٹس کو متحرک کریں گے؟
 
-اگر ایک ` account ` متعین کیا گیا ہے، تو وہ صرف صحیح اکاؤنٹ کے نام سے مماثل ہوگا۔ مثال کے طور پر، اکاؤنٹس اور سب اکاؤنٹس سے ملنے کے لیے مخصوص ` prefixes ` اور ` suffixes` کے ساتھ، `accounts` فیلڈ کی وضاحت کرکے سب اکاؤنٹس کو ملانا ممکن ہے۔ درج ذیل تمام `mintbase1.near` سب اکاؤنٹس سے مماثل ہوں گے:
+اگر ایک `account` متعین کیا گیا ہے، تو وہ صرف صحیح اکاؤنٹ کے نام سے مماثل ہوگا۔ مثال کے طور پر، اکاؤنٹس اور سب اکاؤنٹس سے ملنے کے لیے مخصوص `prefixes` اور ` suffixes` کے ساتھ، `accounts` فیلڈ کی وضاحت کرکے سب اکاؤنٹس کو ملانا ممکن ہے۔ درج ذیل تمام `mintbase1.near` سب اکاؤنٹس سے مماثل ہوں گے:
 
 ```yaml
 accounts:
diff --git a/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx
index df53c1b48b6e..118eeea3c5f3 100644
--- a/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/ur/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ ABI فائل (فائلیں) آپ کے کنٹریکٹ (کنٹریکٹس) سے م
 
 ## SpecVersion Releases
 
-|  ورزن | جاری کردہ نوٹس                                                                                                                                                           |
-| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| ورزن | جاری کردہ نوٹس |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
 | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
-| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx
index 7838cac596df..7b866d878c0b 100644
--- a/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/ur/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| قسم          | تفصیل                                                                                                                                                                                                            |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Byte array، ایک ہیکساڈیسیمل سٹرنگ کے طور پر پیش کیا جاتا ہے. عام طور پر Ethereum hashes اور ایڈریسیس کے لیے استعمال ہوتا ہے.                                                                                     |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| قسم | تفصیل |
+| --- | --- |
+| `Bytes` | Byte array، ایک ہیکساڈیسیمل سٹرنگ کے طور پر پیش کیا جاتا ہے. عام طور پر Ethereum hashes اور ایڈریسیس کے لیے استعمال ہوتا ہے. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
@@ -306,7 +306,7 @@ query {
 
 نتائج ترتیب دینے کے لیے معاون الگورتھم:
 
-| Algorithm     | Description                                                                 |
-| ------------- | --------------------------------------------------------------------------- |
-| rank          | نتائج ترتیب دینے کے لیے فل ٹیکسٹ کیوری کے میچ کوالٹی (1-0) کا استعمال کریں. |
-| قربت کا درجہ  | Similar to rank but also includes the proximity of the matches.             |
+| Algorithm    | Description                                                                 |
+| ------------ | --------------------------------------------------------------------------- |
+| rank         | نتائج ترتیب دینے کے لیے فل ٹیکسٹ کیوری کے میچ کوالٹی (1-0) کا استعمال کریں. |
+| قربت کا درجہ | Similar to rank but also includes the proximity of the matches.             |
diff --git a/website/pages/ur/developing/graph-ts/api.mdx b/website/pages/ur/developing/graph-ts/api.mdx
index a8d423b77148..c96035a03ceb 100644
--- a/website/pages/ur/developing/graph-ts/api.mdx
+++ b/website/pages/ur/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-|  ورزن | جاری کردہ نوٹس                                                                                                                                                                                                                                |
-| :---: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
+| ورزن | جاری کردہ نوٹس |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
 | 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-| 0.0.2 | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### بلٹ ان اقسام
 
diff --git a/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx b/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx
index ff87c267315c..d00028321854 100644
--- a/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx
+++ b/website/pages/ur/developing/substreams-powered-subgraphs-faq.mdx
@@ -44,8 +44,7 @@ Substreams-powered subgraphs combine all the benefits of Substreams with the que
 
 [StreamingFast](https://www.streamingfast.io/) کے ذریعے تیار کردہ، Firehose ایک بلاکچین ڈیٹا نکالنے کی پرت ہے جسے شروع سے بلاکچینز کی مکمل تاریخ کو اس رفتار سے پروسیس کرنے کے لیے ڈیزائن کیا گیا ہے جو پہلے نظر نہیں آتی تھیں۔ فائلوں پر مبنی اور سٹریمنگ فرسٹ اپروچ فراہم کرنا، یہ سٹریمنگ فاسٹ کے اوپن سورس ٹیکنالوجیز کے سوٹ کا بنیادی جزو اور سب اسٹریمز کی بنیاد ہے.
 
-Firehose کے بارے میں مزید جاننے کے لیے[documentation]
-(https://firehose.streamingfast.io/) پر جائیں.
+Firehose کے بارے میں مزید جاننے کے لیے[documentation] (https://firehose.streamingfast.io/) پر جائیں.
 
 ## Firehose کے کیا فوائد ہیں؟
 
diff --git a/website/pages/ur/developing/unit-testing-framework.mdx b/website/pages/ur/developing/unit-testing-framework.mdx
index 23e3d1695189..76d1bd43664a 100644
--- a/website/pages/ur/developing/unit-testing-framework.mdx
+++ b/website/pages/ur/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ Global test coverage: 22.2% (2/9 handlers).
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 دلائل میں عدم مماثلت `graph-ts` اور `matchstick-as` میں عدم مماثلت کی وجہ سے ہوتی ہے۔ اس طرح کے مسائل کو حل کرنے کا بہترین طریقہ یہ ہے کہ ہر چیز کو تازہ ترین جاری کردہ ورژن میں اپ ڈیٹ کیا جائے.
diff --git a/website/pages/ur/network/benefits.mdx b/website/pages/ur/network/benefits.mdx
index 21ef629e8418..2597116aef61 100644
--- a/website/pages/ur/network/benefits.mdx
+++ b/website/pages/ur/network/benefits.mdx
@@ -27,49 +27,49 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|      اخراجات کا موازنہ       |               خود میزبان                |                                The Graph Network                                |
-|:----------------------------:|:---------------------------------------:|:-------------------------------------------------------------------------------:|
-|    ماہانہ سرور کی قیمت/*     |              $350 فی مہینہ              |                                       $0                                        |
-|      استفسار کے اخراجات      |                   $0+                   |                                  $0 per month                                   |
-| انجینئرنگ کا وقت<sup>†</sup> |              $400 فی مہینہ              | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
-|       فی مہینہ سوالات        |        بنیادی صلاحیتوں تک محدود         |                               100,000 (Free Plan)                               |
-|         قیمت فی سوال         |                   $0                    |                                 $0<sup>‡</sup>                                  |
-|        بنیادی ڈھانچہ         |               سینٹرلائزڈ                |                                  ڈیسینٹرلائزڈ                                   |
-|      جغرافیائی فالتو پن      |           $750+ فی اضافی نوڈ            |                                      شامل                                       |
-|           اپ ٹائم            |               اتار چڑھاو                |                                     99.9%+                                      |
-|      کل ماہانہ اخراجات       | <span className="highlight-row" />$750+ |                                       $0                                        |
+| اخراجات کا موازنہ | خود میزبان | The Graph Network |
+| :-: | :-: | :-: |
+| ماہانہ سرور کی قیمت/\* | $350 فی مہینہ | $0 |
+| استفسار کے اخراجات | $0+ | $0 per month |
+| انجینئرنگ کا وقت<sup>†</sup> | $400 فی مہینہ | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
+| فی مہینہ سوالات | بنیادی صلاحیتوں تک محدود | 100,000 (Free Plan) |
+| قیمت فی سوال | $0 | $0<sup>‡</sup> |
+| بنیادی ڈھانچہ | سینٹرلائزڈ | ڈیسینٹرلائزڈ |
+| جغرافیائی فالتو پن | $750+ فی اضافی نوڈ | شامل |
+| اپ ٹائم | اتار چڑھاو | 99.9%+ |
+| کل ماہانہ اخراجات | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|      اخراجات کا موازنہ       |                 خود میزبان                 |                                The Graph Network                                |
-|:----------------------------:|:------------------------------------------:|:-------------------------------------------------------------------------------:|
-|    ماہانہ سرور کی قیمت/*     |               $350 فی مہینہ                |                                       $0                                        |
-|      استفسار کے اخراجات      |               $500 فی مہینہ                |                                 $120 per month                                  |
-| انجینئرنگ کا وقت<sup>†</sup> |               $800 فی مہینہ                | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
-|       فی مہینہ سوالات        |          بنیادی صلاحیتوں تک محدود          |                                   ~3,000,000                                    |
-|         قیمت فی سوال         |                     $0                     |                                    $0.00004                                     |
-|        بنیادی ڈھانچہ         |                 سینٹرلائزڈ                 |                                  ڈیسینٹرلائزڈ                                   |
-|     انجینئرنگ کے اخراجات     |               $200 فی گھنٹہ                |                                      شامل                                       |
-|      جغرافیائی فالتو پن      |     فی اضافی نوڈ کل اخراجات میں $1,200     |                                      شامل                                       |
-|           اپ ٹائم            |                 اتار چڑھاو                 |                                     99.9%+                                      |
-|      کل ماہانہ اخراجات       | <span className="highlight-row" /> $1,650+ |                                      $120                                       |
+| اخراجات کا موازنہ | خود میزبان | The Graph Network |
+| :-: | :-: | :-: |
+| ماہانہ سرور کی قیمت/\* | $350 فی مہینہ | $0 |
+| استفسار کے اخراجات | $500 فی مہینہ | $120 per month |
+| انجینئرنگ کا وقت<sup>†</sup> | $800 فی مہینہ | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
+| فی مہینہ سوالات | بنیادی صلاحیتوں تک محدود | ~3,000,000 |
+| قیمت فی سوال | $0 | $0.00004 |
+| بنیادی ڈھانچہ | سینٹرلائزڈ | ڈیسینٹرلائزڈ |
+| انجینئرنگ کے اخراجات | $200 فی گھنٹہ | شامل |
+| جغرافیائی فالتو پن | فی اضافی نوڈ کل اخراجات میں $1,200 | شامل |
+| اپ ٹائم | اتار چڑھاو | 99.9%+ |
+| کل ماہانہ اخراجات | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|      اخراجات کا موازنہ       |                 سیلف ہوسٹڈ                  |                                The Graph Network                                |
-|:----------------------------:|:-------------------------------------------:|:-------------------------------------------------------------------------------:|
-|    ماہانہ سرور کی قیمت/*     |           $1100 فی مہینہ، فی نوڈ            |                                       $0                                        |
-|      استفسار کے اخراجات      |                    $4000                    |                                $1,200 per month                                 |
-|    نوڈس کی تعداد درکار ہے    |                     10                      |                                 قابل اطلاق نہیں                                 |
-| انجینئرنگ کا وقت<sup>†</sup> |       $6,000 یا اس سے زیادہ فی مہینہ        | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
-|       فی مہینہ سوالات        |          بنیادی صلاحیتوں تک محدود           |                                   ~30,000,000                                   |
-|         قیمت فی سوال         |                     $0                      |                                    $0.00004                                     |
-|        بنیادی ڈھانچہ         |                 سینٹرلائزڈ                  |                                  ڈیسینٹرلائزڈ                                   |
-|      جغرافیائی فالتو پن      |     فی اضافی نوڈ کل اخراجات میں $1,200      |                                      شامل                                       |
-|           اپ ٹائم            |                 اتار چڑھاو                  |                                     99.9%+                                      |
-|      کل ماہانہ اخراجات       | <span className="highlight-row" /> $11,000+ |                                     $1,200                                      |
-
-/*بیک اپ کے اخراجات سمیت: $50-$100 فی مہینہ
+| اخراجات کا موازنہ | سیلف ہوسٹڈ | The Graph Network |
+| :-: | :-: | :-: |
+| ماہانہ سرور کی قیمت/\* | $1100 فی مہینہ، فی نوڈ | $0 |
+| استفسار کے اخراجات | $4000 | $1,200 per month |
+| نوڈس کی تعداد درکار ہے | 10 | قابل اطلاق نہیں |
+| انجینئرنگ کا وقت<sup>†</sup> | $6,000 یا اس سے زیادہ فی مہینہ | کوئی بھی نہیں، عالمی سطح پر تقسیم شدہ انڈیکسرز کے ساتھ نیٹ ورک میں بنایا گیا ہے |
+| فی مہینہ سوالات | بنیادی صلاحیتوں تک محدود | ~30,000,000 |
+| قیمت فی سوال | $0 | $0.00004 |
+| بنیادی ڈھانچہ | سینٹرلائزڈ | ڈیسینٹرلائزڈ |
+| جغرافیائی فالتو پن | فی اضافی نوڈ کل اخراجات میں $1,200 | شامل |
+| اپ ٹائم | اتار چڑھاو | 99.9%+ |
+| کل ماہانہ اخراجات | <span className="highlight-row" /> $11,000+ | $1,200 |
+
+/\*بیک اپ کے اخراجات سمیت: $50-$100 فی مہینہ
 
 <sup>†</sup>$200 فی گھنٹہ کے مفروضے کی بنیاد پر انجینئرنگ کا وقت
 
diff --git a/website/pages/ur/network/delegating.mdx b/website/pages/ur/network/delegating.mdx
index 5bc50cb9ce02..062b3c7db382 100644
--- a/website/pages/ur/network/delegating.mdx
+++ b/website/pages/ur/network/delegating.mdx
@@ -49,8 +49,8 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
 <div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  [ڈیلیگیشن ان بانڈنگ](/img/Delegation-Unbonding.png) _ڈیلیگیشن UI میں 0.5% فیس نوٹ کریں، ساتھ ہی 28 دن
-  غیر بندھن کی مدت۔_
+  [ڈیلیگیشن ان بانڈنگ](/img/Delegation-Unbonding.png) _ڈیلیگیشن UI میں 0.5% فیس نوٹ کریں، ساتھ ہی 28 دن غیر بندھن کی
+  مدت۔_
 </div>
 
 ### ڈیلیگیٹرز کے لیے منصفانہ انعامی ادائیگی کے ساتھ ایک قابل اعتماد انڈیکسر کا انتخاب کرنا
@@ -64,7 +64,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![انڈیکسنگ ریوارڈ کٹ](/img/Indexing-Reward-Cut.png) *سب سے اوپر انڈیکسر ڈیلیگیٹرز کو 90% انعامات دے رہا ہے. درمیان والا ڈیلیگیٹرز کو 20% دے رہا ہے۔ نیچے والا ڈیلیگیٹرز کو ~83% دے رہا ہے۔*
+  ![انڈیکسنگ ریوارڈ کٹ](/img/Indexing-Reward-Cut.png) *سب سے اوپر انڈیکسر ڈیلیگیٹرز کو 90% انعامات دے رہا ہے. درمیان
+  والا ڈیلیگیٹرز کو 20% دے رہا ہے۔ نیچے والا ڈیلیگیٹرز کو ~83% دے رہا ہے۔*
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/ur/network/indexing.mdx b/website/pages/ur/network/indexing.mdx
index 59933c810c92..a115bb4c34a3 100644
--- a/website/pages/ur/network/indexing.mdx
+++ b/website/pages/ur/network/indexing.mdx
@@ -112,12 +112,12 @@ query indexerAllocations {
 - **درمیانہ** - پروڈکشن انڈیکسر 100 سب گراف اور 200-500 درخواستیں فی سیکنڈ کو اٹھا سکتا ہے.
 - **بڑا** - تمام فی الحال زیر استعمال سب گرافس کو انڈیکس کرنے اور متعلقہ ٹریفک کے لیے درخواستیں پیش کرنے کے لیے تیار ہے.
 
-| سیٹ اپ  | Postgres<br />(CPUs) | Postgres<br />(GBs میں میموری) | Postgres<br />(TBs میں ڈسک) | VMs<br />(CPUs) | VMs<br />(GBs میں میموری) |
-| ------- |:--------------------------:|:------------------------------------:|:---------------------------------:|:---------------------:|:-------------------------------:|
-| چھوٹا   |             4              |                  8                   |                 1                 |           4           |               16                |
-| معیاری  |             8              |                  30                  |                 1                 |          12           |               48                |
-| درمیانہ |             16             |                  64                  |                 2                 |          32           |               64                |
-| بڑا     |             72             |                 468                  |                3.5                |          48           |               184               |
+| سیٹ اپ | Postgres<br />(CPUs) | Postgres<br />(GBs میں میموری) | Postgres<br />(TBs میں ڈسک) | VMs<br />(CPUs) | VMs<br />(GBs میں میموری) |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| چھوٹا | 4 | 8 | 1 | 4 | 16 |
+| معیاری | 8 | 30 | 1 | 12 | 48 |
+| درمیانہ | 16 | 64 | 2 | 32 | 64 |
+| بڑا | 72 | 468 | 3.5 | 48 | 184 |
 
 ### وہ کون سی چند بنیادی حفاظتی تدابیر ہیں جو ایک انڈیکسر کو اختیار کرنی چاہیے؟
 
@@ -149,20 +149,20 @@ query indexerAllocations {
 
 #### گراف نوڈ
 
-| Port | Purpose                                                   | Routes                                               | CLI Argument      | Environment Variable |
-| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے)          | /                                                    | --admin-port      | -                    |
-| 8030 | سب گراف انڈیکسنگ اسٹیٹس API                               | /graphql                                             | --index-node-port | -                    |
-| 8040 | Prometheus میٹرکس                                         | /metrics                                             | --metrics-port    | -                    |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے) | / | --admin-port | - |
+| 8030 | سب گراف انڈیکسنگ اسٹیٹس API | /graphql | --index-node-port | - |
+| 8040 | Prometheus میٹرکس | /metrics | --metrics-port | - |
 
 #### انڈیکسر سروس
 
-| Port | Purpose                                                           | Routes                                                                  | CLI Argument   | Environment Variable   |
-| ---- | ----------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL HTTP server<br />(ادا شدہ سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus میٹرکس                                                 | /metrics                                                                | --metrics-port | -                      |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP server<br />(ادا شدہ سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus میٹرکس | /metrics | --metrics-port | - |
 
 #### انڈیکسر ایجنٹ
 
diff --git a/website/pages/ur/new-chain-integration.mdx b/website/pages/ur/new-chain-integration.mdx
index 8a348a4970ea..6853e523e756 100644
--- a/website/pages/ur/new-chain-integration.mdx
+++ b/website/pages/ur/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/ur/operating-graph-node.mdx b/website/pages/ur/operating-graph-node.mdx
index 1591a45dd2d0..53ed532c07f8 100644
--- a/website/pages/ur/operating-graph-node.mdx
+++ b/website/pages/ur/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 جب یہ چل رہا ہوتا ہے گراف نوڈ مندرجہ ذیل پورٹس کو بے نقاب کرتا ہے:
 
-| Port | Purpose                                                   | Routes                                               | CLI Argument      | Environment Variable |
-| ---- | --------------------------------------------------------- | ---------------------------------------------------- | ----------------- | -------------------- |
-| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -                    |
-| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے)          | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -                    |
-| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے)          | /                                                    | --admin-port      | -                    |
-| 8030 | سب گراف انڈیکسنگ اسٹیٹس API                               | /graphql                                             | --index-node-port | -                    |
-| 8040 | Prometheus میٹرکس                                         | /metrics                                             | --metrics-port    | -                    |
+| Port | Purpose | Routes | CLI Argument | Environment Variable |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP server<br />(سب گراف کی کیوریز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(سب گراف سبسکرپشنز کے لیے) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(تعیناتیوں کے انتظام کے لیے) | / | --admin-port | - |
+| 8030 | سب گراف انڈیکسنگ اسٹیٹس API | /graphql | --index-node-port | - |
+| 8040 | Prometheus میٹرکس | /metrics | --metrics-port | - |
 
 > **اہم**: پورٹس کو عوامی طور پر ظاہر کرنے میں محتاط رہیں - **انتظامی پورٹس** کو بند رکھا جانا چاہیے. اس میں گراف نوڈ کا JSON-RPC اینڈ پوائنٹ شامل ہے.
 
diff --git a/website/pages/ur/querying/graphql-api.mdx b/website/pages/ur/querying/graphql-api.mdx
index 3dfdf8d64d89..dca35f1f671a 100644
--- a/website/pages/ur/querying/graphql-api.mdx
+++ b/website/pages/ur/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic شوگر:** آپ `and` آپریٹر کو ہٹا کر کوما سے الگ کردہ سب اظہار کو پاس کر کے مذکورہ کیوری کو آسان بنا سکتے ہیں.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ The result of such a query will not change over time, i.e., querying at a certai
 
 فل ٹیکسٹ سرچ آپریٹرز:
 
-| علامت      | آپریٹر      | تفصیل                                                                                                                                           |
-| ---------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
-| `&`    | `And`       | ایک سے زیادہ تلاش کی اصطلاحات کو ایک فلٹر میں یکجا کرنے کے لیے ان ہستیوں کے لیے جس میں فراہم کردہ تمام اصطلاحات شامل ہوں                        |
-| &#x7c;     | `Or`        | Or آپریٹر کے ذریعہ الگ کردہ متعدد تلاش کی اصطلاحات کے ساتھ کیوریز فراہم کردہ شرائط میں سے کسی سے بھی مماثلت کے ساتھ تمام ہستیوں کو واپس کریں گے |
-| `<>` | `Follow by` | دو الفاظ کے درمیان فاصلہ بتائیں.                                                                                                                |
-| `:*`       | `Prefix`    | ایسے الفاظ تلاش کرنے کے لیے پریفکس ​​تلاش کی اصطلاح استعمال کریں جن کا سابقہ ​​مماثل ہو (۲ حروف درکار ہیں.)                                     |
+| علامت | آپریٹر | تفصیل |
+| --- | --- | --- |
+| `&` | `And` | ایک سے زیادہ تلاش کی اصطلاحات کو ایک فلٹر میں یکجا کرنے کے لیے ان ہستیوں کے لیے جس میں فراہم کردہ تمام اصطلاحات شامل ہوں |
+| &#x7c; | `Or` | Or آپریٹر کے ذریعہ الگ کردہ متعدد تلاش کی اصطلاحات کے ساتھ کیوریز فراہم کردہ شرائط میں سے کسی سے بھی مماثلت کے ساتھ تمام ہستیوں کو واپس کریں گے |
+| `<>` | `Follow by` | دو الفاظ کے درمیان فاصلہ بتائیں. |
+| `:*` | `Prefix` | ایسے الفاظ تلاش کرنے کے لیے پریفکس ​​تلاش کی اصطلاح استعمال کریں جن کا سابقہ ​​مماثل ہو (۲ حروف درکار ہیں.) |
 
 #### مثالیں
 
@@ -421,7 +421,7 @@ GraphQL schemas generally define root types for `queries`, `subscriptions` and `
 
 اگر کوئی بلاک فراہم کیا جاتا ہے تو، میٹا ڈیٹا اس بلاک کا ہوتا ہے، اگر تازہ ترین انڈیکسڈ بلاک استعمال نہیں کیا جاتا ہے۔ اگر فراہم کیا گیا ہو، تو بلاک سب گراف کے اسٹارٹ بلاک کے بعد ہونا چاہیے، اور حال ہی میں انڈیکس کیے گئے بلاک سے کم یا اس کے برابر ہونا چاہیے.
 
-` deployment ` ایک منفرد ID ہے، جو `subgraph.yaml` فائل کے IPFS CID سے مطابقت رکھتی ہے.
+`deployment` ایک منفرد ID ہے، جو `subgraph.yaml` فائل کے IPFS CID سے مطابقت رکھتی ہے.
 
 `block` تازہ ترین بلاک کے بارے میں معلومات فراہم کرتا ہے (`_meta` کو بھیجی گئی کسی بھی بلاک کی رکاوٹوں کو مدنظر رکھتے ہوئے):
 
diff --git a/website/pages/ur/querying/querying-best-practices.mdx b/website/pages/ur/querying/querying-best-practices.mdx
index cd9942f43ea4..47954840b8fe 100644
--- a/website/pages/ur/querying/querying-best-practices.mdx
+++ b/website/pages/ur/querying/querying-best-practices.mdx
@@ -53,7 +53,7 @@ query [operationName]([variableName]: [variableType]) {
 ## Rules for Writing GraphQL Queries
 
 - ہر ایک `queryName` کو فی آپریشن صرف ایک بار استعمال کیا جانا چاہیے.
-- ہر ایک ` field ` کو انتخاب میں صرف ایک بار استعمال کیا جانا چاہیے (ہم `token` کے تحت دو بار `id` سے کیوری نہیں کرسکتے ہیں)
+- ہر ایک `field` کو انتخاب میں صرف ایک بار استعمال کیا جانا چاہیے (ہم `token` کے تحت دو بار `id` سے کیوری نہیں کرسکتے ہیں)
 - Some `field`s or queries (like `tokens`) return complex types that require a selection of sub-field. Not providing a selection when expected (or providing one when not expected - for example, on `id`) will raise an error. To know a field type, please refer to [Graph Explorer](/network/explorer).
 - کسی دلیل کو تفویض کردہ کوئی بھی متغیر اس کی قسم سے مماثل ہونا چاہیے.
 - متغیرات کی دی گئی فہرست میں، ان میں سے ہر ایک منفرد ہونا چاہیے.
diff --git a/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx b/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx
index 9c8d0512a4eb..31439d43c505 100644
--- a/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/ur/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 اگر آپ کے پاس متغیر شیڈونگ ہے تو آپ کو اپنے ڈپلیکیٹ متغیرات کا نام تبدیل کرنے کی ضرورت ہوگی.
+
 ### کالعدم موازنہ
+
 اپنے سب گراف پر اپ گریڈ کرنے سے، بعض اوقات آپ کو اس طرح کی غلطیاں مل سکتی ہیں:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 حل کرنے کے لیے آپ صرف `if` اسٹیٹمنٹ کو اس طرح تبدیل کر سکتے ہیں:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 اس مسئلے کو حل کرنے کے لیے، آپ اس پراپرٹی تک رسائی کے لیے ایک متغیر بنا سکتے ہیں تاکہ مرتب کرنے والا منسوخی چیک میجک کر سکے:
 
 ```typescript
diff --git a/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx b/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx
index 3d1289e29dd2..fba78a067915 100644
--- a/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx
+++ b/website/pages/ur/release-notes/graphql-validations-migration-guide.mdx
@@ -4,8 +4,7 @@ title: GraphQL کی توثیق کی منتقلی گائیڈ
 
 جلد ہی `گراف نوڈ` [GraphQL توثیق کی تفصیلات](https://spec.graphql.org/June2018/#sec-Validation) کی 100% کوریج کو سپورٹ کرے گا.
 
-`گراف نوڈ` کے پچھلے ورژن تمام توثیقوں کی حمایت نہیں کرتے تھے اور زیادہ خوبصورت جوابات فراہم کرتے تھے - لہذا، ابہام کی صورت میں، `گراف نوڈ` غلط گراف کیو ایل
- آپریشن کے اجزاء کو نظر انداز کر رہا تھا.
+`گراف نوڈ` کے پچھلے ورژن تمام توثیقوں کی حمایت نہیں کرتے تھے اور زیادہ خوبصورت جوابات فراہم کرتے تھے - لہذا، ابہام کی صورت میں، `گراف نوڈ` غلط گراف کیو ایل آپریشن کے اجزاء کو نظر انداز کر رہا تھا.
 
 GraphQL ویلیڈیشن سپورٹ آنے والی نئی خصوصیات اور گراف نیٹ ورک کے پیمانے پر کارکردگی کا ایک ستون ہے.
 
diff --git a/website/pages/ur/sps/triggers-example.mdx b/website/pages/ur/sps/triggers-example.mdx
index 604c864981b7..eb250dc250c5 100644
--- a/website/pages/ur/sps/triggers-example.mdx
+++ b/website/pages/ur/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## شرطیں
diff --git a/website/pages/ur/supported-network-requirements.mdx b/website/pages/ur/supported-network-requirements.mdx
index ee345dee7c3f..f4b5a7768f13 100644
--- a/website/pages/ur/supported-network-requirements.mdx
+++ b/website/pages/ur/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| نیٹ ورک   | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| نیٹ ورک | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx
index 92e75af5d3ad..ce25fbcafc6d 100644
--- a/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/vi/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ The `graph add` command will fetch the ABI from Etherscan (unless an ABI path is
 
 ## SpecVersion Releases
 
-| Phiên bản | Ghi chú phát hành                                                                                                                                                        |
-| :-------: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-|   1.2.0   | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-|   1.1.0   | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-|   1.0.0   | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-|   0.0.9   | Supports `endBlock` feature                                                                                                                                              |
-|   0.0.8   | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-|   0.0.7   | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-|   0.0.6   | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-|   0.0.5   | Added support for event handlers having access to transaction receipts.                                                                                                  |
-|   0.0.4   | Added support for managing subgraph features.                                                                                                                            |
+| Phiên bản | Ghi chú phát hành |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
+| 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx
index 4367bbd4b7f1..6f440ca3ca8c 100644
--- a/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/vi/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| Loại         | Miêu tả                                                                                                                                                                                                          |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | Mảng byte, được biểu diễn dưới dạng chuỗi thập lục phân. Thường được sử dụng cho các mã băm và địa chỉ Ethereum.                                                                                                 |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| Loại | Miêu tả |
+| --- | --- |
+| `Bytes` | Mảng byte, được biểu diễn dưới dạng chuỗi thập lục phân. Thường được sử dụng cho các mã băm và địa chỉ Ethereum. |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### Enums
 
diff --git a/website/pages/vi/developing/graph-ts/api.mdx b/website/pages/vi/developing/graph-ts/api.mdx
index cff2389b0279..9595add2bc4c 100644
--- a/website/pages/vi/developing/graph-ts/api.mdx
+++ b/website/pages/vi/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ The `@graphprotocol/graph-ts` library provides the following APIs:
 
 The `apiVersion` in the subgraph manifest specifies the mapping API version which is run by Graph Node for a given subgraph.
 
-| Phiên bản | Ghi chú phát hành                                                                                                                                                                                                                             |
-| :-------: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-|   0.0.9   | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa)                                                                                                                  |
-|   0.0.8   | Adds validation for existence of fields in the schema when saving an entity.                                                                                                                                                                  |
-|   0.0.7   | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object                                                                                                                    |
-|   0.0.6   | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object                                                                                                                                |
-|   0.0.5   | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
-|   0.0.4   | Added `functionSignature` field to the Ethereum SmartContractCall object                                                                                                                                                                      |
-|   0.0.3   | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to`                                                                                                                                      |
-|   0.0.2   | Added `input` field to the Ethereum Transaction object                                                                                                                                                                                        |
+| Phiên bản | Ghi chú phát hành |
+| :-: | --- |
+| 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | Added `TransactionReceipt` and `Log` classes to the Ethereum types<br />Added `receipt` field to the Ethereum Event object |
+| 0.0.6 | Added `nonce` field to the Ethereum Transaction object<br />Added `baseFeePerGas` to the Ethereum Block object |
+| 0.0.5 | AssemblyScript upgraded to version 0.19.10 (this includes breaking changes, please see the [`Migration Guide`](/release-notes/assemblyscript-migration-guide))<br />`ethereum.transaction.gasUsed` renamed to `ethereum.transaction.gasLimit` |
+| 0.0.4 | Added `functionSignature` field to the Ethereum SmartContractCall object |
+| 0.0.3 | Added `from` field to the Ethereum Call object<br />`etherem.call.address` renamed to `ethereum.call.to` |
+| 0.0.2 | Added `input` field to the Ethereum Transaction object |
 
 ### Các loại cài sẵn
 
diff --git a/website/pages/vi/developing/unit-testing-framework.mdx b/website/pages/vi/developing/unit-testing-framework.mdx
index 7bab8ce8c859..63da75a0cc84 100644
--- a/website/pages/vi/developing/unit-testing-framework.mdx
+++ b/website/pages/vi/developing/unit-testing-framework.mdx
@@ -1380,15 +1380,15 @@ The log output includes the test run duration. Here's an example:
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > return new ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 The mismatch in arguments is caused by mismatch in `graph-ts` and `matchstick-as`. The best way to fix issues like this one is to update everything to the latest released version.
diff --git a/website/pages/vi/network/benefits.mdx b/website/pages/vi/network/benefits.mdx
index a5857ff2ed86..41f8bc870b9a 100644
--- a/website/pages/vi/network/benefits.mdx
+++ b/website/pages/vi/network/benefits.mdx
@@ -27,47 +27,47 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       Cost Comparison        |               Self Hosted               |                         Mạng The Graph                          |
-|:----------------------------:|:---------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |             $350 per month              |                               $0                                |
-|         Query costs          |                   $0+                   |                          $0 per month                           |
-| Engineering time<sup>†</sup> |             $400 per month              | None, built into the network with globally distributed Indexers |
-|      Queries per month       |      Limited to infra capabilities      |                       100,000 (Free Plan)                       |
-|        Cost per query        |                   $0                    |                         $0<sup>‡</sup>                          |
-|        Cơ sở hạ tầng         |               Centralized               |                          Decentralized                          |
-|    Geographic redundancy     |        $750+ per additional node        |                            Included                             |
-|            Uptime            |                 Varies                  |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" />$750+ |                               $0                                |
+| Cost Comparison | Self Hosted | Mạng The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $0+ | $0 per month |
+| Engineering time<sup>†</sup> | $400 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | 100,000 (Free Plan) |
+| Cost per query | $0 | $0<sup>‡</sup> |
+| Cơ sở hạ tầng | Centralized | Decentralized |
+| Geographic redundancy | $750+ per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" />$750+ | $0 |
 
 ## Medium Volume User (~3M queries per month)
 
-|       Cost Comparison        |                Self Hosted                 |                         Mạng The Graph                          |
-|:----------------------------:|:------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |               $350 per month               |                               $0                                |
-|         Query costs          |               $500 per month               |                         $120 per month                          |
-| Engineering time<sup>†</sup> |               $800 per month               | None, built into the network with globally distributed Indexers |
-|      Queries per month       |       Limited to infra capabilities        |                           ~3,000,000                            |
-|        Cost per query        |                     $0                     |                            $0.00004                             |
-|        Cơ sở hạ tầng         |                Centralized                 |                          Decentralized                          |
-|     Engineering expense      |               $200 per hour                |                            Included                             |
-|    Geographic redundancy     | $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                   |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $1,650+ |                              $120                               |
+| Cost Comparison | Self Hosted | Mạng The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $350 per month | $0 |
+| Query costs | $500 per month | $120 per month |
+| Engineering time<sup>†</sup> | $800 per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~3,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Cơ sở hạ tầng | Centralized | Decentralized |
+| Engineering expense | $200 per hour | Included |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $1,650+ | $120 |
 
 ## High Volume User (~30M queries per month)
 
-|       Cost Comparison        |                 Self Hosted                 |                         Mạng The Graph                          |
-|:----------------------------:|:-------------------------------------------:|:---------------------------------------------------------------:|
-|   Monthly server cost\*    |          $1100 per month, per node          |                               $0                                |
-|         Query costs          |                    $4000                    |                        $1,200 per month                         |
-|    Number of nodes needed    |                     10                      |                         Not applicable                          |
-| Engineering time<sup>†</sup> |          $6,000 or more per month           | None, built into the network with globally distributed Indexers |
-|      Queries per month       |        Limited to infra capabilities        |                           ~30,000,000                           |
-|        Cost per query        |                     $0                      |                            $0.00004                             |
-|        Cơ sở hạ tầng         |                 Centralized                 |                          Decentralized                          |
-|    Geographic redundancy     |  $1,200 in total costs per additional node  |                            Included                             |
-|            Uptime            |                   Varies                    |                             99.9%+                              |
-|     Total Monthly Costs      | <span className="highlight-row" /> $11,000+ |                             $1,200                              |
+| Cost Comparison | Self Hosted | Mạng The Graph |
+| :-: | :-: | :-: |
+| Monthly server cost\* | $1100 per month, per node | $0 |
+| Query costs | $4000 | $1,200 per month |
+| Number of nodes needed | 10 | Not applicable |
+| Engineering time<sup>†</sup> | $6,000 or more per month | None, built into the network with globally distributed Indexers |
+| Queries per month | Limited to infra capabilities | ~30,000,000 |
+| Cost per query | $0 | $0.00004 |
+| Cơ sở hạ tầng | Centralized | Decentralized |
+| Geographic redundancy | $1,200 in total costs per additional node | Included |
+| Uptime | Varies | 99.9%+ |
+| Total Monthly Costs | <span className="highlight-row" /> $11,000+ | $1,200 |
 
 \*including costs for backup: $50-$100 per month
 
diff --git a/website/pages/vi/network/indexing.mdx b/website/pages/vi/network/indexing.mdx
index b19e9f99a983..8c5ac85fb98e 100644
--- a/website/pages/vi/network/indexing.mdx
+++ b/website/pages/vi/network/indexing.mdx
@@ -112,12 +112,12 @@ Indexer có thể tự phân biệt bản thân bằng cách áp dụng các k
 - **Medium** - Production Indexer supporting 100 subgraphs and 200-500 requests per second.
 - **Lớn** - Được chuẩn bị để index tất cả các subgraph hiện đang được sử dụng và phục vụ các yêu cầu cho lưu lượng truy cập liên quan.
 
-| Cài đặt     | Postgres<br />(CPUs) | Postgres<br />(bộ nhớ tính bằng GB) | Postgres<br />(đĩa tính bằng TB) | VMs<br />(CPUs) | VMs<br />(bộ nhớ tính bằng GB) |
-| ----------- |:--------------------------:|:-----------------------------------------:|:--------------------------------------:|:---------------------:|:------------------------------------:|
-| Nhỏ         |             4              |                     8                     |                   1                    |           4           |                  16                  |
-| Tiêu chuẩn  |             8              |                    30                     |                   1                    |          12           |                  48                  |
-| Trung bình |             16             |                    64                     |                   2                    |          32           |                  64                  |
-| Lớn         |             72             |                    468                    |                  3.5                   |          48           |                 184                  |
+| Cài đặt | Postgres<br />(CPUs) | Postgres<br />(bộ nhớ tính bằng GB) | Postgres<br />(đĩa tính bằng TB) | VMs<br />(CPUs) | VMs<br />(bộ nhớ tính bằng GB) |
+| --- | :-: | :-: | :-: | :-: | :-: |
+| Nhỏ | 4 | 8 | 1 | 4 | 16 |
+| Tiêu chuẩn | 8 | 30 | 1 | 12 | 48 |
+| Trung bình | 16 | 64 | 2 | 32 | 64 |
+| Lớn | 72 | 468 | 3.5 | 48 | 184 |
 
 ### What are some basic security precautions an Indexer should take?
 
@@ -149,20 +149,20 @@ Lưu ý: Để hỗ trợ mở rộng quy mô nhanh, bạn nên tách các mối
 
 #### Graph Node
 
-| Cổng | Mục đích                                                    | Tuyến                                                | Đối số CLI        | Biến môi trường |
-| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
-| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
-| 8001 | GraphQL WS<br />(cho các đăng ký subgraph)            | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
-| 8020 | JSON-RPC<br />(để quản lý triển khai)                 | /                                                    | --admin-port      | -               |
-| 8030 | API trạng thái lập chỉ mục Subgraph                         | /graphql                                             | --index-node-port | -               |
-| 8040 | Số liệu Prometheus                                          | /metrics                                             | --metrics-port    | -               |
+| Cổng | Mục đích | Tuyến | Đối số CLI | Biến môi trường |
+| --- | --- | --- | --- | --- |
+| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(cho các đăng ký subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(để quản lý triển khai) | / | --admin-port | - |
+| 8030 | API trạng thái lập chỉ mục Subgraph | /graphql | --index-node-port | - |
+| 8040 | Số liệu Prometheus | /metrics | --metrics-port | - |
 
 #### Dịch vụ Indexer
 
-| Cổng | Mục đích                                                               | Tuyến                                                                   | Đối số CLI     | Biến môi trường        |
-| ---- | ---------------------------------------------------------------------- | ----------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph có trả phí) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Số liệu Prometheus                                                     | /metrics                                                                | --metrics-port | -                      |
+| Cổng | Mục đích | Tuyến | Đối số CLI | Biến môi trường |
+| --- | --- | --- | --- | --- |
+| 7600 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph có trả phí) | /subgraphs/id/...<br />/status<br />/channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Số liệu Prometheus | /metrics | --metrics-port | - |
 
 #### Đại lý Indexer
 
diff --git a/website/pages/vi/new-chain-integration.mdx b/website/pages/vi/new-chain-integration.mdx
index 534d6701efdb..3bb6c774f961 100644
--- a/website/pages/vi/new-chain-integration.mdx
+++ b/website/pages/vi/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, in a JSON-RPC batch request
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/vi/operating-graph-node.mdx b/website/pages/vi/operating-graph-node.mdx
index 9185043e72a4..82cebd402554 100644
--- a/website/pages/vi/operating-graph-node.mdx
+++ b/website/pages/vi/operating-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:
 
-| Cổng | Mục đích                                                    | Tuyến                                                | Đối số CLI        | Biến môi trường |
-| ---- | ----------------------------------------------------------- | ---------------------------------------------------- | ----------------- | --------------- |
-| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port       | -               |
-| 8001 | GraphQL WS<br />(cho các đăng ký subgraph)            | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port         | -               |
-| 8020 | JSON-RPC<br />(để quản lý triển khai)                 | /                                                    | --admin-port      | -               |
-| 8030 | API trạng thái lập chỉ mục Subgraph                         | /graphql                                             | --index-node-port | -               |
-| 8040 | Số liệu Prometheus                                          | /metrics                                             | --metrics-port    | -               |
+| Cổng | Mục đích | Tuyến | Đối số CLI | Biến môi trường |
+| --- | --- | --- | --- | --- |
+| 8000 | Máy chủ GraphQL HTTP<br />(cho các truy vấn subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS<br />(cho các đăng ký subgraph) | /subgraphs/id/...<br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC<br />(để quản lý triển khai) | / | --admin-port | - |
+| 8030 | API trạng thái lập chỉ mục Subgraph | /graphql | --index-node-port | - |
+| 8040 | Số liệu Prometheus | /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.
 
diff --git a/website/pages/vi/querying/graphql-api.mdx b/website/pages/vi/querying/graphql-api.mdx
index 65d0a40a7bd4..8db543089d78 100644
--- a/website/pages/vi/querying/graphql-api.mdx
+++ b/website/pages/vi/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **Syntactic sugar:** You can simplify the above query by removing the `and` operator by passing a sub-expression separated by commas.
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ Fulltext search queries have one required field, `text`, for supplying search te
 
 Fulltext 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                                               |
-| &#x7c;      | `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 |
+| &#x7c; | `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
 
diff --git a/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx b/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx
index 8536b657e78a..69c36218d8af 100644
--- a/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/vi/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 Bạn sẽ cần đổi tên các biến trùng lặp của mình nếu bạn có che biến.
+
 ### So sánh Null
+
 Bằng cách thực hiện nâng cấp trên subgraph của bạn, đôi khi bạn có thể gặp các lỗi như sau:
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 Để giải quyết, bạn có thể chỉ cần thay đổi câu lệnh `if` thành một cái gì đó như sau:
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 Để khắc phục sự cố này, bạn có thể tạo một biến cho quyền truy cập thuộc tính đó để trình biên dịch có thể thực hiện phép thuật kiểm tra tính nullability:
 
 ```typescript
diff --git a/website/pages/vi/sps/triggers-example.mdx b/website/pages/vi/sps/triggers-example.mdx
index 3ed429e6133b..8912961e3be0 100644
--- a/website/pages/vi/sps/triggers-example.mdx
+++ b/website/pages/vi/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## Điều kiện tiên quyết
diff --git a/website/pages/vi/supported-network-requirements.mdx b/website/pages/vi/supported-network-requirements.mdx
index a8305e895706..50cd5e88b459 100644
--- a/website/pages/vi/supported-network-requirements.mdx
+++ b/website/pages/vi/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| Mạng lưới | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Ethereum  | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| Mạng lưới | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Ethereum | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/pages/zh/cookbook/subgraph-debug-forking.mdx b/website/pages/zh/cookbook/subgraph-debug-forking.mdx
index 96fdd046a87f..9407cd0d670a 100644
--- a/website/pages/zh/cookbook/subgraph-debug-forking.mdx
+++ b/website/pages/zh/cookbook/subgraph-debug-forking.mdx
@@ -6,7 +6,7 @@ As with many systems processing large amounts of data, The Graph's Indexers (Gra
 
 ## 首先，让我们来看什么是子图分叉
 
-**子图分叉** 是从_另一个_ 子图的存储（通常是远程存储）中缓慢获取实体的过程。
+**子图分叉** 是从*另一个* 子图的存储（通常是远程存储）中缓慢获取实体的过程。
 
 在调试时，**subgraph forking** 允许您在固定的区块 _X_ 中调试失败的子图，而无需等待区块同步 _X_。
 
diff --git a/website/pages/zh/developing/creating-a-subgraph/advanced.mdx b/website/pages/zh/developing/creating-a-subgraph/advanced.mdx
index d8abf7fb58cc..7ecc521091c6 100644
--- a/website/pages/zh/developing/creating-a-subgraph/advanced.mdx
+++ b/website/pages/zh/developing/creating-a-subgraph/advanced.mdx
@@ -281,7 +281,7 @@ For Arweave, as of version 0.33.0 Graph Node can fetch files stored on Arweave b
 ```typescript
 import { TokenMetadata as TokenMetadataTemplate } from '../generated/templates'
 
-const ipfshash = "QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm"
+const ipfshash = 'QmaXzZhcYnsisuue5WRdQDH6FDvqkLQX1NckLqBYeYYEfm'
 //This example code is for a Crypto coven subgraph. The above ipfs hash is a directory with token metadata for all crypto coven NFTs.
 
 export function handleTransfer(event: TransferEvent): void {
diff --git a/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx b/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx
index 50df657982d7..9db4e62530b6 100644
--- a/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx
+++ b/website/pages/zh/developing/creating-a-subgraph/install-the-cli.mdx
@@ -106,14 +106,14 @@ ABI 文件必须与您的合约相匹配。 获取 ABI 文件的方法有以下
 
 ## SpecVersion Releases
 
-|   版本  | Release 说明                                                                                                                                                               |
-| :---: | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call`                                                          |
-| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`.                                                              |
-| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs                                                                     |
-| 0.0.9 | Supports `endBlock` feature                                                                                                                                              |
+| 版本 | Release 说明 |
+| :-: | --- |
+| 1.2.0 | Added support for [Indexed Argument Filtering](/#indexed-argument-filters--topic-filters) & declared `eth_call` |
+| 1.1.0 | Supports [Timeseries & Aggregations](#timeseries-and-aggregations). Added support for type `Int8` for `id`. |
+| 1.0.0 | Supports [`indexerHints`](/developing/creating-a-subgraph/#indexer-hints) feature to prune subgraphs |
+| 0.0.9 | Supports `endBlock` feature |
 | 0.0.8 | Added support for polling [Block Handlers](/developing/creating-a-subgraph/#polling-filter) and [Initialisation Handlers](/developing/creating-a-subgraph/#once-filter). |
-| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources).                                                                               |
-| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant.                                                               |
-| 0.0.5 | Added support for event handlers having access to transaction receipts.                                                                                                  |
-| 0.0.4 | Added support for managing subgraph features.                                                                                                                            |
+| 0.0.7 | Added support for [File Data Sources](/developing/creating-a-subgraph/#file-data-sources). |
+| 0.0.6 | Supports fast [Proof of Indexing](/network/indexing/#what-is-a-proof-of-indexing-poi) calculation variant. |
+| 0.0.5 | Added support for event handlers having access to transaction receipts. |
+| 0.0.4 | Added support for managing subgraph features. |
diff --git a/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx b/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx
index d9ca63c76b45..eb5be4580baf 100644
--- a/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx
+++ b/website/pages/zh/developing/creating-a-subgraph/ql-schema.mdx
@@ -72,16 +72,16 @@ For some entity types the `id` for `Bytes!` is constructed from the id's of two
 
 The following scalars are supported in the GraphQL API:
 
-| 类型           | 描述                                                                                                                                                                                                               |
-| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `Bytes`      | 字节数组，表示为十六进制字符串。 通常用于以太坊hash和地址。                                                                                                                                                                                 |
-| `String`     | Scalar for `string` values. Null characters are not supported and are automatically removed.                                                                                                                     |
-| `Boolean`    | Scalar for `boolean` values.                                                                                                                                                                                     |
-| `Int`        | The GraphQL spec defines `Int` to be a signed 32-bit integer.                                                                                                                                                    |
-| `Int8`       | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
-| `BigInt`     | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`.                             |
-| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits.                                                  |
-| `Timestamp`  | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations.                                                                                                      |
+| 类型 | 描述 |
+| --- | --- |
+| `Bytes` | 字节数组，表示为十六进制字符串。 通常用于以太坊hash和地址。 |
+| `String` | Scalar for `string` values. Null characters are not supported and are automatically removed. |
+| `Boolean` | Scalar for `boolean` values. |
+| `Int` | The GraphQL spec defines `Int` to be a signed 32-bit integer. |
+| `Int8` | An 8-byte signed integer, also known as a 64-bit signed integer, can store values in the range from -9,223,372,036,854,775,808 to 9,223,372,036,854,775,807. Prefer using this to represent `i64` from ethereum. |
+| `BigInt` | Large integers. Used for Ethereum's `uint32`, `int64`, `uint64`, ..., `uint256` types. Note: Everything below `uint32`, such as `int32`, `uint24` or `int8` is represented as `i32`. |
+| `BigDecimal` | `BigDecimal` High precision decimals represented as a significand and an exponent. The exponent range is from −6143 to +6144. Rounded to 34 significant digits. |
+| `Timestamp` | It is an `i64` value in microseconds. Commonly used for `timestamp` fields for timeseries and aggregations. |
 
 ### 枚举类型
 
@@ -283,30 +283,30 @@ query {
 
 支持的语言词典：
 
-| Code   | 词典         |
-| ------ | ---------- |
-| simple | General    |
-| da     | Danish     |
-| nl     | Dutch      |
-| en     | English    |
-| fi     | Finnish    |
-| fr     | French     |
-| de     | German     |
-| hu     | Hungarian  |
-| it     | Italian    |
-| no     | Norwegian  |
-| pt     | 葡萄牙语       |
-| ro     | Romanian   |
-| ru     | Russian    |
-| es     | Spanish    |
-| sv     | Swedish    |
-| tr     | Turkish    |
+| Code   | 词典      |
+| ------ | --------- |
+| simple | General   |
+| da     | Danish    |
+| nl     | Dutch     |
+| en     | English   |
+| fi     | Finnish   |
+| fr     | French    |
+| de     | German    |
+| hu     | Hungarian |
+| it     | Italian   |
+| no     | Norwegian |
+| pt     | 葡萄牙语  |
+| ro     | Romanian  |
+| ru     | Russian   |
+| es     | Spanish   |
+| sv     | Swedish   |
+| tr     | Turkish   |
 
 ### 排序算法
 
 支持的排序结果算法：
 
-| Algorithm     | Description                                                             |
-| ------------- | ----------------------------------------------------------------------- |
-| rank          | 使用全文查询的匹配质量 (0-1) 对结果进行排序。                                              |
-| proximityRank | Similar to rank but also includes the proximity of the matches.         |
+| Algorithm     | Description                                                     |
+| ------------- | --------------------------------------------------------------- |
+| rank          | 使用全文查询的匹配质量 (0-1) 对结果进行排序。                   |
+| proximityRank | Similar to rank but also includes the proximity of the matches. |
diff --git a/website/pages/zh/developing/graph-ts/api.mdx b/website/pages/zh/developing/graph-ts/api.mdx
index 0bb53153fae9..7a814fcd9a7e 100644
--- a/website/pages/zh/developing/graph-ts/api.mdx
+++ b/website/pages/zh/developing/graph-ts/api.mdx
@@ -29,16 +29,16 @@ Since language mappings are written in AssemblyScript, it is useful to review th
 
 子图清单中的 `apiVersion` 指定了由 Graph Node 运行的特定子图的映射 API 版本。
 
-|   版本  | Release 说明                                                                                                                   |
-| :---: | ---------------------------------------------------------------------------------------------------------------------------- |
+| 版本 | Release 说明 |
+| :-: | --- |
 | 0.0.9 | Adds new host functions [`eth_get_balance`](#balance-of-an-address) & [`hasCode`](#check-if-an-address-is-a-contract-or-eoa) |
-| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity.                                                 |
-| 0.0.7 | 添加了 `TransactionReceipt` 和 `Log` 类到以太坊类型。<br />已将 `receipt` 字段添加到Ethereum Event对象。                                           |
-| 0.0.6 | 向Ethereum Transaction对象添加了 nonce 字段 向 Etherum Block对象添加<br /> baseFeePerGas字段                                                |
-| 0.0.5 | AssemblyScript 升级到版本 0.19.10(这包括重大更改，参阅 <br />迁移指南)ethereum.transaction.gasUsed 重命名为 ethereum.transaction.gasLimit           |
-| 0.0.4 | 已向 Ethereum SmartContractCall对象添加了 `functionSignature` 字段。                                                                   |
-| 0.0.3 | 已向Ethereum Call 对象添加了 `from` 字段。<br />`etherem.call.address` 被重命名为 `ethereum.call.to`。                                       |
-| 0.0.2 | 已向Ethereum Transaction对象添加了 `input` 字段。                                                                                      |
+| 0.0.8 | Adds validation for existence of fields in the schema when saving an entity. |
+| 0.0.7 | 添加了 `TransactionReceipt` 和 `Log` 类到以太坊类型。<br />已将 `receipt` 字段添加到Ethereum Event对象。 |
+| 0.0.6 | 向Ethereum Transaction对象添加了 nonce 字段 向 Etherum Block对象添加<br /> baseFeePerGas字段 |
+| 0.0.5 | AssemblyScript 升级到版本 0.19.10(这包括重大更改，参阅 <br />迁移指南)ethereum.transaction.gasUsed 重命名为 ethereum.transaction.gasLimit |
+| 0.0.4 | 已向 Ethereum SmartContractCall对象添加了 `functionSignature` 字段。 |
+| 0.0.3 | 已向Ethereum Call 对象添加了 `from` 字段。<br />`etherem.call.address` 被重命名为 `ethereum.call.to`。 |
+| 0.0.2 | 已向Ethereum Transaction对象添加了 `input` 字段。 |
 
 ### 内置类型
 
@@ -769,19 +769,19 @@ if (value.kind == JSONValueKind.BOOL) {
 
 ### 类型转换参考
 
-| 源类型                  | 目标类型                 | 转换函数                         |
+| 源类型               | 目标类型             | 转换函数                     |
 | -------------------- | -------------------- | ---------------------------- |
 | Address              | Bytes                | none                         |
 | Address              | String               | s.toHexString()              |
 | BigDecimal           | String               | s.toString()                 |
 | BigInt               | BigDecimal           | s.toBigDecimal()             |
-| BigInt               | String (hexadecimal) | s.toHexString() 或 s.toHex()  |
+| BigInt               | String (hexadecimal) | s.toHexString() 或 s.toHex() |
 | BigInt               | String (unicode)     | s.toString()                 |
 | BigInt               | i32                  | s.toI32()                    |
 | Boolean              | Boolean              | none                         |
 | Bytes (signed)       | BigInt               | BigInt.fromSignedBytes(s)    |
 | Bytes (unsigned)     | BigInt               | BigInt.fromUnsignedBytes(s)  |
-| Bytes                | String (hexadecimal) | s.toHexString() 或 s.toHex()  |
+| Bytes                | String (hexadecimal) | s.toHexString() 或 s.toHex() |
 | Bytes                | String (unicode)     | s.toString()                 |
 | Bytes                | String (base58)      | s.toBase58()                 |
 | Bytes                | i32                  | s.toI32()                    |
diff --git a/website/pages/zh/developing/unit-testing-framework.mdx b/website/pages/zh/developing/unit-testing-framework.mdx
index f5b3d4e5f28c..6a6c46fd3d9b 100644
--- a/website/pages/zh/developing/unit-testing-framework.mdx
+++ b/website/pages/zh/developing/unit-testing-framework.mdx
@@ -33,7 +33,7 @@ Installation command:
 brew install postgresql
 ```
 
-创建到最新 libpq.5. lib_ 的符号链接，可能需要首先创建这个目录_`/usr/local/opt/postgreql/lib/`
+创建到最新 libpq.5. lib* 的符号链接，可能需要首先创建这个目录*`/usr/local/opt/postgreql/lib/`
 
 ```sh
 ln -sf /usr/local/opt/postgresql@14/lib/postgresql@14/libpq.5.dylib /usr/local/opt/postgresql/lib/libpq.5.dylib
@@ -236,7 +236,7 @@ test("handleNewGravatar() should create a new entity", () => {
 
 例子：
 
-`beforeAll`中的代码将在文件中的_all_测试之前执行一次。
+`beforeAll`中的代码将在文件中的*all*测试之前执行一次。
 
 ```typescript
 import { describe, test, beforeAll } from "matchstick-as/assembly/index"
@@ -296,7 +296,7 @@ describe("handleUpdatedGravatar()", () => {
 
 例子:
 
-`afterAll`中的代码将在文件中的_all_测试之后执行一次。
+`afterAll`中的代码将在文件中的*all*测试之后执行一次。
 
 ```typescript
 import { describe, test, afterAll } from "matchstick-as/assembly/index"
@@ -1380,15 +1380,15 @@ Global test coverage: 22.2% (2/9 handlers).
 This means you have used `console.log` in your code, which is not supported by AssemblyScript. Please consider using the [Logging API](/developing/graph-ts/api/#logging-api)
 
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > 返回ethereum.Block(defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultAddress, defaultAddressBytes, defaultAddressBytes, defaultAddressBytes, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(18,12)
-> 
+>
 > ERROR TS2554: Expected ? arguments, but got ?.
-> 
+>
 > 返回新ethereum.Transaction(defaultAddressBytes, defaultBigInt, defaultAddress, defaultAddress, defaultBigInt, defaultBigInt, defaultBigInt, defaultAddressBytes, defaultBigInt);
-> 
+>
 > in ~lib/matchstick-as/assembly/defaults.ts(24,12)
 
 参数不匹配是由`graph-ts` and `matchstick-as`不匹配造成的。解决此类问题的最佳方法是将所有内容更新到最新发布的版本。
diff --git a/website/pages/zh/network/benefits.mdx b/website/pages/zh/network/benefits.mdx
index 56e7fbfdbde5..e9170c43c645 100644
--- a/website/pages/zh/network/benefits.mdx
+++ b/website/pages/zh/network/benefits.mdx
@@ -27,49 +27,49 @@ Query costs may vary; the quoted cost is the average at time of publication (Mar
 
 ## Low Volume User (less than 100,000 queries per month)
 
-|       成本比较       |                   自托管                   |        Graph网络        |
-|:----------------:|:---------------------------------------:|:---------------------:|
-|   每月服务器费用 \*   |                 每月350美元                 |          0美元          |
-|       查询成本       |                   $0+                   |     $0 per month      |
-| 工程时间<sup>†</sup> |                 400美元每月                 | 没有，内置在具有全球去中心化索引者的网络中 |
-|       每月查询       |                受限于基础设施能力                |  100,000 (Free Plan)  |
-|     每个查询的成本      |                   0美元                   |    $0<sup>‡</sup>     |
-|       基础设施       |                   中心化                   |         去中心化          |
-|       异地备援       |              每个额外节点 $750 +              |         包括在内          |
-|      正常工作时间      |                   变量                    |        99.9%+         |
-|      每月总成本       | <span className="highlight-row" />$750+ |          0美元          |
+|       成本比较       |                 自托管                  |                 Graph网络                  |
+| :------------------: | :-------------------------------------: | :----------------------------------------: |
+|  每月服务器费用 \*   |               每月350美元               |                   0美元                    |
+|       查询成本       |                   $0+                   |                $0 per month                |
+| 工程时间<sup>†</sup> |               400美元每月               | 没有，内置在具有全球去中心化索引者的网络中 |
+|       每月查询       |           受限于基础设施能力            |            100,000 (Free Plan)             |
+|    每个查询的成本    |                  0美元                  |               $0<sup>‡</sup>               |
+|       基础设施       |                 中心化                  |                  去中心化                  |
+|       异地备援       |           每个额外节点 $750 +           |                  包括在内                  |
+|     正常工作时间     |                  变量                   |                   99.9%+                   |
+|      每月总成本      | <span className="highlight-row" />$750+ |                   0美元                    |
 
 ## Medium Volume User (~3M queries per month)
 
-|       成本比较       |                     自托管                     |        Graph网络        |
-|:----------------:|:-------------------------------------------:|:---------------------:|
-|   每月服务器费用 \*   |                   每月350美元                   |          0美元          |
-|       查询成本       |                   每月500美元                   |    $120 per month     |
+|       成本比较       |                     自托管                      |                 Graph网络                  |
+| :------------------: | :---------------------------------------------: | :----------------------------------------: |
+|  每月服务器费用 \*   |                   每月350美元                   |                   0美元                    |
+|       查询成本       |                   每月500美元                   |               $120 per month               |
 | 工程时间<sup>†</sup> |                   每月800美元                   | 没有，内置在具有全球去中心化索引者的网络中 |
-|       每月查询       |                  受限于基础设施能力                  |      ~3,000,000       |
-|     每个查询的成本      |                     0美元                     |       $0.00004        |
-|       基础设施       |                     中心化                     |         去中心化          |
-|       工程费用       |                  每小时200美元                   |         包括在内          |
-|       异地备援       |              每个额外节点的总成本为1200美元              |         包括在内          |
-|      正常工作时间      |                     变量                      |        99.9%+         |
-|      每月总成本       | <span className="highlight-row" /> 1650美元以上 |         $120          |
+|       每月查询       |               受限于基础设施能力                |                 ~3,000,000                 |
+|    每个查询的成本    |                      0美元                      |                  $0.00004                  |
+|       基础设施       |                     中心化                      |                  去中心化                  |
+|       工程费用       |                  每小时200美元                  |                  包括在内                  |
+|       异地备援       |         每个额外节点的总成本为1200美元          |                  包括在内                  |
+|     正常工作时间     |                      变量                       |                   99.9%+                   |
+|      每月总成本      | <span className="highlight-row" /> 1650美元以上 |                    $120                    |
 
 ## High Volume User (~30M queries per month)
 
-|       成本比较       |                     自托管                     |        Graph网络        |
-|:----------------:|:-------------------------------------------:|:---------------------:|
-|   每月服务器费用 \*   |                 1100美元每月每节点                 |          0美元          |
-|       查询成本       |                   4000美元                    |   $1,200 per month    |
-|     需要的节点数量      |                     10                      |          不适用          |
-| 工程时间<sup>†</sup> |                 每月6000美元或以上                 | 没有，内置在具有全球去中心化索引人的网络中 |
-|       每月查询       |                  受限于基础设施能力                  |      ~30,000,000      |
-|     每个查询的成本      |                     0美元                     |       $0.00004        |
-|       基础设施       |                     中心化                     |         去中心化          |
-|       异地备援       |              每个额外节点的总成本为1200美元              |         包括在内          |
-|      正常工作时间      |                     变量                      |        99.9%+         |
-|      每月总成本       | <span className="highlight-row" /> 11000+美元 |        $1,200         |
-
-* 包括后备费用: 每月$50-$100美元
+|       成本比较       |                    自托管                     |                 Graph网络                  |
+| :------------------: | :-------------------------------------------: | :----------------------------------------: |
+|  每月服务器费用 \*   |              1100美元每月每节点               |                   0美元                    |
+|       查询成本       |                   4000美元                    |              $1,200 per month              |
+|    需要的节点数量    |                      10                       |                   不适用                   |
+| 工程时间<sup>†</sup> |              每月6000美元或以上               | 没有，内置在具有全球去中心化索引人的网络中 |
+|       每月查询       |              受限于基础设施能力               |                ~30,000,000                 |
+|    每个查询的成本    |                     0美元                     |                  $0.00004                  |
+|       基础设施       |                    中心化                     |                  去中心化                  |
+|       异地备援       |        每个额外节点的总成本为1200美元         |                  包括在内                  |
+|     正常工作时间     |                     变量                      |                   99.9%+                   |
+|      每月总成本      | <span className="highlight-row" /> 11000+美元 |                   $1,200                   |
+
+- 包括后备费用: 每月$50-$100美元
 
 <sup>†</sup>按每小时200美元的假设计算的工程时间
 
diff --git a/website/pages/zh/network/delegating.mdx b/website/pages/zh/network/delegating.mdx
index 80ca76888364..7f7954b42fdc 100644
--- a/website/pages/zh/network/delegating.mdx
+++ b/website/pages/zh/network/delegating.mdx
@@ -48,9 +48,7 @@ Whenever a Delegator wants to undelegate, their tokens are subject to a 28-day u
 
 If you choose an Indexer that is not trustworthy or not doing a good job, you will want to undelegate. This means you will be losing a lot of opportunities to earn rewards, which can be just as bad as burning GRT. As a result, it’s recommended that you choose an Indexer wisely.
 
-<div sx={{ mx: 'auto', maxWidth: '400px' }}>
-  请注意委托用户界面中的0.5%费用，以及28天的解约期。
-</div>
+<div sx={{ mx: 'auto', maxWidth: '400px' }}>请注意委托用户界面中的0.5%费用，以及28天的解约期。</div>
 
 ### 选择一个为委托人提供公平的奖励分配的值得信赖的索引人
 
@@ -63,7 +61,8 @@ In order to understand how to choose a trustworthy Indexer, you need to understa
   - If it is set to 80%, as a Delegator, you will receive 20%.
 
 <div sx={{ mx: 'auto', maxWidth: '700px' }}>
-  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *上 面的索引人分给委托人 90% 的收益。 中间的给委托人 20%。 下面的给委托人约 83%。
+  ![Indexing Reward Cut](/img/Indexing-Reward-Cut.png) *上 面的索引人分给委托人 90% 的收益。 中间的给委托人 20%。
+  下面的给委托人约 83%。
 </div>
 
 - **Query Fee Cut** - This is just like the Indexing Reward Cut, but it applies to returns on the query fees that the Indexer collects.
diff --git a/website/pages/zh/network/indexing.mdx b/website/pages/zh/network/indexing.mdx
index 9451572c8438..9daffa4ac7d0 100644
--- a/website/pages/zh/network/indexing.mdx
+++ b/website/pages/zh/network/indexing.mdx
@@ -113,11 +113,11 @@ Query fees are collected by the gateway and distributed to indexers according to
 - **大型** -准备对当前使用的所有子图进行索引，并为相关流量的请求提供服务。
 
 | 设置 | (CPU 数量) | (内存 GB) | (硬盘 TB) | (CPU 数量) | (内存 GB) |
-| -- |:--------:|:-------:|:-------:|:--------:|:-------:|
-| 小型 |    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    |
 
 ### 索引人应该采取哪些基本的安全防范措施？
 
@@ -149,26 +149,26 @@ Query fees are collected by the gateway and distributed to indexers according to
 
 #### Graph 节点
 
-| 端口   | 用途                                   | 路径                                                                  | CLI 参数            | 环境 变量 |
-| ---- | ------------------------------------ | ------------------------------------------------------------------- | ----------------- | ----- |
-| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port       | -     |
-| 8001 | GraphQL WS <br />（用于子图订阅）      | /subgraphs/id/... <br />/subgraphs/name/.../...               | --ws-port         | -     |
-| 8020 | JSON-RPC <br />（用于管理部署）        | /                                                                   | --admin-port      | -     |
-| 8030 | 子图索引状态 API                           | /graphql                                                            | --index-node-port | -     |
-| 8040 | Prometheus 指标                        | /metrics                                                            | --metrics-port    | -     |
+| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS <br />（用于子图订阅） | /subgraphs/id/... <br />/subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC <br />（用于管理部署） | / | --admin-port | - |
+| 8030 | 子图索引状态 API | /graphql | --index-node-port | - |
+| 8040 | Prometheus 指标 | /metrics | --metrics-port | - |
 
 #### 索引人服务
 
-| 端口   | 用途                                      | 路径                                                                          | CLI 参数         | 环境 变量                  |
-| ---- | --------------------------------------- | --------------------------------------------------------------------------- | -------------- | ---------------------- |
-| 7600 | GraphQL HTTP 服务器<br /> （用于付费子图查询） | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port         | `INDEXER_SERVICE_PORT` |
-| 7300 | Prometheus 指标                           | /metrics                                                                    | --metrics-port | -                      |
+| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 |
+| --- | --- | --- | --- | --- |
+| 7600 | GraphQL HTTP 服务器<br /> （用于付费子图查询） | /subgraphs/id/... <br /> /status <br /> /channel-messages-inbox | --port | `INDEXER_SERVICE_PORT` |
+| 7300 | Prometheus 指标 | /metrics | --metrics-port | - |
 
 #### 索引人代理
 
-| 端口   | 用途        | 路径 | CLI 参数                    | 环境 变量                                   |
-| ---- | --------- | -- | ------------------------- | --------------------------------------- |
-| 8000 | 索引人管理 API | /  | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
+| 端口 | 用途           | 路径 | CLI 参数                  | 环境 变量                               |
+| ---- | -------------- | ---- | ------------------------- | --------------------------------------- |
+| 8000 | 索引人管理 API | /    | --indexer-management-port | `INDEXER_AGENT_INDEXER_MANAGEMENT_PORT` |
 
 ### 在谷歌云上使用 Terraform 建立服务器基础设施
 
@@ -731,7 +731,7 @@ default => 0.1 * $SYSTEM_LOAD;
 
 使用上述模型的查询成本计算示例：
 
-| 询问                                                                           | 价格      |
+| 询问                                                                         | 价格    |
 | ---------------------------------------------------------------------------- | ------- |
 | &#123; pairs(skip: 5000) &#123; id &#125; &#125;                             | 0.5 GRT |
 | &#123; tokens &#123; symbol &#125; &#125;                                    | 0.1 GRT |
diff --git a/website/pages/zh/new-chain-integration.mdx b/website/pages/zh/new-chain-integration.mdx
index a3074f0c8223..d7a098e18184 100644
--- a/website/pages/zh/new-chain-integration.mdx
+++ b/website/pages/zh/new-chain-integration.mdx
@@ -25,7 +25,7 @@ For Graph Node to be able to ingest data from an EVM chain, the RPC node must ex
 - `eth_getBlockByHash`
 - `net_version`
 - `eth_getTransactionReceipt`, 在JSON-RPC批量请求中
-- `trace_filter` _(optionally required for Graph Node to support call handlers)_
+- `trace_filter` *(optionally required for Graph Node to support call handlers)*
 
 ### 2. Firehose Integration
 
diff --git a/website/pages/zh/operating-graph-node.mdx b/website/pages/zh/operating-graph-node.mdx
index ecda26fa9061..0847fd1c03c6 100644
--- a/website/pages/zh/operating-graph-node.mdx
+++ b/website/pages/zh/operating-graph-node.mdx
@@ -77,13 +77,13 @@ cargo run -p graph-node --release -- \
 
 当运行Graph Node时，会暴露以下端口：
 
-| 端口   | 用途                                   | 路径                                                                  | CLI 参数            | 环境 变量 |
-| ---- | ------------------------------------ | ------------------------------------------------------------------- | ----------------- | ----- |
-| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port       | -     |
-| 8001 | GraphQL WS <br />（用于子图订阅）      | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --ws-port         | -     |
-| 8020 | JSON-RPC <br />（用于管理部署）        | /                                                                   | --admin-port      | -     |
-| 8030 | 子图索引状态 API                           | /graphql                                                            | --index-node-port | -     |
-| 8040 | Prometheus 指标                        | /metrics                                                            | --metrics-port    | -     |
+| 端口 | 用途 | 路径 | CLI 参数 | 环境 变量 |
+| --- | --- | --- | --- | --- |
+| 8000 | GraphQL HTTP 服务 <br />（用于子图查询） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --http-port | - |
+| 8001 | GraphQL WS <br />（用于子图订阅） | /subgraphs/id/... <br /> <br /> /subgraphs/name/.../... | --ws-port | - |
+| 8020 | JSON-RPC <br />（用于管理部署） | / | --admin-port | - |
+| 8030 | 子图索引状态 API | /graphql | --index-node-port | - |
+| 8040 | Prometheus 指标 | /metrics | --metrics-port | - |
 
 > **重要**: 公开暴露端口时要小心 - **管理端口** 应保持锁定。 这包括下面详述的 Graph 节点 JSON-RPC 和索引人管理端点。
 
diff --git a/website/pages/zh/querying/graphql-api.mdx b/website/pages/zh/querying/graphql-api.mdx
index 2e4b4a0e6f54..7ba254944ed7 100644
--- a/website/pages/zh/querying/graphql-api.mdx
+++ b/website/pages/zh/querying/graphql-api.mdx
@@ -221,7 +221,7 @@ The following example filters for challenges with `outcome` `succeeded` and `num
 ```
 
 > **语法糖：**您可以通过传递一个用逗号分隔的子表达式来删除`and`运算符，从而简化上述查询。
-> 
+>
 > ```graphql
 > {
 >   challenges(where: { number_gte: 100, outcome: "succeeded" }) {
@@ -335,12 +335,12 @@ The result of such a query will not change over time, i.e., querying at a certai
 
 全文搜索运算符：
 
-| 符号          | 运算符         | 描述                                    |
-| ----------- | ----------- | ------------------------------------- |
-| `&`     | `And`       | 用于将多个搜索词组合到包含所有提供词条的实体的过滤器中           |
-| &#x7c;      | `Or`        | 由 or 运算符分隔的多个搜索词的查询，将返回与任何提供的词匹配的所有实体 |
-| `<->` | `Follow by` | 指定两个单词之间的距离。                          |
-| `:*`        | `Prefix`    | 使用前缀搜索词查找前缀匹配的单词（需要 2 个字符）            |
+| 符号   | 运算符      | 描述                                                                   |
+| ------ | ----------- | ---------------------------------------------------------------------- |
+| `&`    | `And`       | 用于将多个搜索词组合到包含所有提供词条的实体的过滤器中                 |
+| &#x7c; | `Or`        | 由 or 运算符分隔的多个搜索词的查询，将返回与任何提供的词匹配的所有实体 |
+| `<->`  | `Follow by` | 指定两个单词之间的距离。                                               |
+| `:*`   | `Prefix`    | 使用前缀搜索词查找前缀匹配的单词（需要 2 个字符）                      |
 
 #### 例子
 
diff --git a/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx b/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx
index 3ff2d318c88f..622bdeef307e 100644
--- a/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx
+++ b/website/pages/zh/release-notes/assemblyscript-migration-guide.mdx
@@ -127,8 +127,11 @@ ERROR TS2451: Cannot redeclare block-scoped variable 'a'
  ~~~~~~~~~~~~~
 in assembly/index.ts(4,3)
 ```
+
 如果您有变量遮蔽的情况，则需要重命名重名变量。
+
 ### 空值比较
+
 对子图进行升级后，有时您可能会遇到如下错误：
 
 ```typescript
@@ -137,6 +140,7 @@ ERROR TS2322: Type '~lib/@graphprotocol/graph-ts/common/numbers/BigInt | null' i
                      ~~~~
  in src/mappings/file.ts(41,21)
 ```
+
 要解决此问题，您只需将 `if` 语句更改为如下所示代码：
 
 ```typescript
@@ -284,6 +288,7 @@ ERROR TS2322: Type '~lib/string/String | null' is not assignable to type '~lib/s
    let somethingOrElse: string = container.data ? container.data : "else";
                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 ```
+
 要解决此问题，您可以为该属性访问创建一个变量，以便编译器可以执行可空性检查：
 
 ```typescript
diff --git a/website/pages/zh/sps/triggers-example.mdx b/website/pages/zh/sps/triggers-example.mdx
index 657a4d2402e2..9782a9989ba5 100644
--- a/website/pages/zh/sps/triggers-example.mdx
+++ b/website/pages/zh/sps/triggers-example.mdx
@@ -1,5 +1,5 @@
 ---
-title: "Tutorial: Set Up a Substreams-Powered Subgraph on Solana"
+title: 'Tutorial: Set Up a Substreams-Powered Subgraph on Solana'
 ---
 
 ## 先决条件
diff --git a/website/pages/zh/supported-network-requirements.mdx b/website/pages/zh/supported-network-requirements.mdx
index d9e844cbbe43..62bb55c63746 100644
--- a/website/pages/zh/supported-network-requirements.mdx
+++ b/website/pages/zh/supported-network-requirements.mdx
@@ -2,17 +2,17 @@
 title: Supported Network Requirements
 ---
 
-| 网络        | Guides                                                                                                                                                                                                                                                                                              | System Requirements                                                                                                                   | Indexing Rewards |
-| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------- | :--------------: |
-| Arbitrum  | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker)                                                                                                                                 | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                               |         ✅        |
-| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker)                                                                                                                                                                                                                        | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Base      | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker)             | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_           |         ✅        |
-| Binance   | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal)                                                                                                                                                                                                      | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_             |         ✅        |
-| Celo      | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker)                                                                                                                                                                                                                             | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| 以太坊       | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker)                                                                                                                                                                                                                  | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ |         ✅        |
-| Fantom    | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker)                                                                                                                                                                                                                           | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Gnosis    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal)                                                                                                                                                                                                              | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_                   |         ✅        |
-| Linea     | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal)                                                                                                                                                                                                                      | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_                            |         ✅        |
-| Optimism  | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_                    |         ✅        |
-| Polygon   | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker)                                                                                                                                                                                                                          | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_                              |         ✅        |
-| Scroll    | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker)                                                                                                                                     | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_                    |         ✅        |
+| 网络 | Guides | System Requirements | Indexing Rewards |
+| --- | --- | --- | :-: |
+| Arbitrum | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/arbitrum/docker) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Avalanche | [Docker Guide](https://docs.infradao.com/archive-nodes-101/avalanche/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 5 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Base | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/base/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/base/geth/docker) | 8+ core CPU<br /> Debian 12/Ubuntu 22.04<br /> 16 GB RAM<br /> >= 4.5TB (NVME preffered)<br /> _last updated 14th May 2024_ | ✅ |
+| Binance | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/binance/erigon/baremetal) | 8 core / 16 threads CPU<br /> Ubuntu 22.04<br /> >=32 GB RAM<br /> >= 14 TiB NVMe SSD<br /> _last updated 22nd June 2024_ | ✅ |
+| Celo | [Docker Guide](https://docs.infradao.com/archive-nodes-101/celo/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 2 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| 以太坊 | [Docker Guide](https://docs.infradao.com/archive-nodes-101/ethereum/erigon/docker) | Higher clock speed over core count<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >=3TB (NVMe recommended)<br /> _last updated August 2023_ | ✅ |
+| Fantom | [Docker Guide](https://docs.infradao.com/archive-nodes-101/fantom/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 13 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Gnosis | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/gnosis/erigon/baremetal) | 6 core / 12 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 3 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Linea | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/linea/baremetal) | 4+ core CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 2nd April 2024_ | ✅ |
+| Optimism | [Erigon Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/erigon/baremetal)<br /><br /> [GETH Baremetal Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/baremetal)<br /> [GETH Docker Guide](https://docs.infradao.com/archive-nodes-101/optimism/geth/docker) | 4 core / 8 threads CPU<br /> Ubuntu 22.04<br /> 16GB+ RAM<br /> >= 8 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Polygon | [Docker Guide](https://docs.infradao.com/archive-nodes-101/polygon/docker) | 16 core CPU<br /> Ubuntu 22.04<br /> 32GB+ RAM<br /> >= 10 TiB NVMe SSD<br /> _last updated August 2023_ | ✅ |
+| Scroll | [Baremetal Guide](https://docs.infradao.com/archive-nodes-101/scroll/baremetal)<br /> [Docker Guide](https://docs.infradao.com/archive-nodes-101/scroll/docker) | 4 core / 8 threads CPU<br /> Debian 12<br /> 16GB+ RAM<br /> >= 1 TiB NVMe SSD<br /> _last updated 3rd April 2024_ | ✅ |
diff --git a/website/route-lockfile.txt b/website/route-lockfile.txt
index cef279b371fe..3632901afe11 100644
--- a/website/route-lockfile.txt
+++ b/website/route-lockfile.txt
@@ -30,6 +30,12 @@
 /ar/deploying/subgraph-studio-faqs/
 /ar/deploying/subgraph-studio/
 /ar/developing/creating-a-subgraph/
+/ar/developing/creating-a-subgraph/advanced/
+/ar/developing/creating-a-subgraph/assemblyscript-mappings/
+/ar/developing/creating-a-subgraph/install-the-cli/
+/ar/developing/creating-a-subgraph/ql-schema/
+/ar/developing/creating-a-subgraph/starting-your-subgraph/
+/ar/developing/creating-a-subgraph/subgraph-manifest/
 /ar/developing/developer-faqs/
 /ar/developing/graph-ts/api/
 /ar/developing/graph-ts/common-issues/
@@ -39,6 +45,7 @@
 /ar/firehose/
 /ar/glossary/
 /ar/graphcast/
+/ar/managing/delete-a-subgraph/
 /ar/managing/deprecate-a-subgraph/
 /ar/managing/transfer-a-subgraph/
 /ar/mips-faqs/
@@ -105,6 +112,12 @@
 /cs/deploying/subgraph-studio-faqs/
 /cs/deploying/subgraph-studio/
 /cs/developing/creating-a-subgraph/
+/cs/developing/creating-a-subgraph/advanced/
+/cs/developing/creating-a-subgraph/assemblyscript-mappings/
+/cs/developing/creating-a-subgraph/install-the-cli/
+/cs/developing/creating-a-subgraph/ql-schema/
+/cs/developing/creating-a-subgraph/starting-your-subgraph/
+/cs/developing/creating-a-subgraph/subgraph-manifest/
 /cs/developing/developer-faqs/
 /cs/developing/graph-ts/api/
 /cs/developing/graph-ts/common-issues/
@@ -114,6 +127,7 @@
 /cs/firehose/
 /cs/glossary/
 /cs/graphcast/
+/cs/managing/delete-a-subgraph/
 /cs/managing/deprecate-a-subgraph/
 /cs/managing/transfer-a-subgraph/
 /cs/mips-faqs/
@@ -178,6 +192,12 @@
 /de/deploying/subgraph-studio-faqs/
 /de/deploying/subgraph-studio/
 /de/developing/creating-a-subgraph/
+/de/developing/creating-a-subgraph/advanced/
+/de/developing/creating-a-subgraph/assemblyscript-mappings/
+/de/developing/creating-a-subgraph/install-the-cli/
+/de/developing/creating-a-subgraph/ql-schema/
+/de/developing/creating-a-subgraph/starting-your-subgraph/
+/de/developing/creating-a-subgraph/subgraph-manifest/
 /de/developing/developer-faqs/
 /de/developing/graph-ts/api/
 /de/developing/graph-ts/common-issues/
@@ -187,6 +207,7 @@
 /de/firehose/
 /de/glossary/
 /de/graphcast/
+/de/managing/delete-a-subgraph/
 /de/managing/deprecate-a-subgraph/
 /de/managing/transfer-a-subgraph/
 /de/mips-faqs/
@@ -248,7 +269,12 @@
 /en/deploying/deploy-using-subgraph-studio/
 /en/deploying/multiple-networks/
 /en/deploying/subgraph-studio-faqs/
-/en/developing/creating-a-subgraph/
+/en/developing/creating-a-subgraph/advanced/
+/en/developing/creating-a-subgraph/assemblyscript-mappings/
+/en/developing/creating-a-subgraph/install-the-cli/
+/en/developing/creating-a-subgraph/ql-schema/
+/en/developing/creating-a-subgraph/starting-your-subgraph/
+/en/developing/creating-a-subgraph/subgraph-manifest/
 /en/developing/developer-faqs/
 /en/developing/graph-ts/CHANGELOG/
 /en/developing/graph-ts/README/
@@ -260,7 +286,7 @@
 /en/firehose/
 /en/glossary/
 /en/graphcast/
-/en/managing/deprecate-a-subgraph/
+/en/managing/delete-a-subgraph/
 /en/managing/transfer-a-subgraph/
 /en/network/benefits/
 /en/network/contracts/
@@ -328,6 +354,12 @@
 /es/deploying/subgraph-studio-faqs/
 /es/deploying/subgraph-studio/
 /es/developing/creating-a-subgraph/
+/es/developing/creating-a-subgraph/advanced/
+/es/developing/creating-a-subgraph/assemblyscript-mappings/
+/es/developing/creating-a-subgraph/install-the-cli/
+/es/developing/creating-a-subgraph/ql-schema/
+/es/developing/creating-a-subgraph/starting-your-subgraph/
+/es/developing/creating-a-subgraph/subgraph-manifest/
 /es/developing/developer-faqs/
 /es/developing/graph-ts/api/
 /es/developing/graph-ts/common-issues/
@@ -337,6 +369,7 @@
 /es/firehose/
 /es/glossary/
 /es/graphcast/
+/es/managing/delete-a-subgraph/
 /es/managing/deprecate-a-subgraph/
 /es/managing/transfer-a-subgraph/
 /es/mips-faqs/
@@ -403,6 +436,12 @@
 /fr/deploying/subgraph-studio-faqs/
 /fr/deploying/subgraph-studio/
 /fr/developing/creating-a-subgraph/
+/fr/developing/creating-a-subgraph/advanced/
+/fr/developing/creating-a-subgraph/assemblyscript-mappings/
+/fr/developing/creating-a-subgraph/install-the-cli/
+/fr/developing/creating-a-subgraph/ql-schema/
+/fr/developing/creating-a-subgraph/starting-your-subgraph/
+/fr/developing/creating-a-subgraph/subgraph-manifest/
 /fr/developing/developer-faqs/
 /fr/developing/graph-ts/api/
 /fr/developing/graph-ts/common-issues/
@@ -412,6 +451,7 @@
 /fr/firehose/
 /fr/glossary/
 /fr/graphcast/
+/fr/managing/delete-a-subgraph/
 /fr/managing/deprecate-a-subgraph/
 /fr/managing/transfer-a-subgraph/
 /fr/mips-faqs/
@@ -480,6 +520,7 @@
 /ha/firehose/
 /ha/glossary/
 /ha/graphcast/
+/ha/managing/delete-a-subgraph/
 /ha/managing/deprecate-a-subgraph/
 /ha/managing/transfer-a-subgraph/
 /ha/mips-faqs/
@@ -545,6 +586,12 @@
 /hi/deploying/subgraph-studio-faqs/
 /hi/deploying/subgraph-studio/
 /hi/developing/creating-a-subgraph/
+/hi/developing/creating-a-subgraph/advanced/
+/hi/developing/creating-a-subgraph/assemblyscript-mappings/
+/hi/developing/creating-a-subgraph/install-the-cli/
+/hi/developing/creating-a-subgraph/ql-schema/
+/hi/developing/creating-a-subgraph/starting-your-subgraph/
+/hi/developing/creating-a-subgraph/subgraph-manifest/
 /hi/developing/developer-faqs/
 /hi/developing/graph-ts/api/
 /hi/developing/graph-ts/common-issues/
@@ -554,6 +601,7 @@
 /hi/firehose/
 /hi/glossary/
 /hi/graphcast/
+/hi/managing/delete-a-subgraph/
 /hi/managing/deprecate-a-subgraph/
 /hi/managing/transfer-a-subgraph/
 /hi/mips-faqs/
@@ -620,6 +668,12 @@
 /it/deploying/subgraph-studio-faqs/
 /it/deploying/subgraph-studio/
 /it/developing/creating-a-subgraph/
+/it/developing/creating-a-subgraph/advanced/
+/it/developing/creating-a-subgraph/assemblyscript-mappings/
+/it/developing/creating-a-subgraph/install-the-cli/
+/it/developing/creating-a-subgraph/ql-schema/
+/it/developing/creating-a-subgraph/starting-your-subgraph/
+/it/developing/creating-a-subgraph/subgraph-manifest/
 /it/developing/developer-faqs/
 /it/developing/graph-ts/api/
 /it/developing/graph-ts/common-issues/
@@ -629,6 +683,7 @@
 /it/firehose/
 /it/glossary/
 /it/graphcast/
+/it/managing/delete-a-subgraph/
 /it/managing/deprecate-a-subgraph/
 /it/managing/transfer-a-subgraph/
 /it/mips-faqs/
@@ -695,6 +750,12 @@
 /ja/deploying/subgraph-studio-faqs/
 /ja/deploying/subgraph-studio/
 /ja/developing/creating-a-subgraph/
+/ja/developing/creating-a-subgraph/advanced/
+/ja/developing/creating-a-subgraph/assemblyscript-mappings/
+/ja/developing/creating-a-subgraph/install-the-cli/
+/ja/developing/creating-a-subgraph/ql-schema/
+/ja/developing/creating-a-subgraph/starting-your-subgraph/
+/ja/developing/creating-a-subgraph/subgraph-manifest/
 /ja/developing/developer-faqs/
 /ja/developing/graph-ts/api/
 /ja/developing/graph-ts/common-issues/
@@ -704,6 +765,7 @@
 /ja/firehose/
 /ja/glossary/
 /ja/graphcast/
+/ja/managing/delete-a-subgraph/
 /ja/managing/deprecate-a-subgraph/
 /ja/managing/transfer-a-subgraph/
 /ja/mips-faqs/
@@ -768,6 +830,12 @@
 /ko/deploying/subgraph-studio-faqs/
 /ko/deploying/subgraph-studio/
 /ko/developing/creating-a-subgraph/
+/ko/developing/creating-a-subgraph/advanced/
+/ko/developing/creating-a-subgraph/assemblyscript-mappings/
+/ko/developing/creating-a-subgraph/install-the-cli/
+/ko/developing/creating-a-subgraph/ql-schema/
+/ko/developing/creating-a-subgraph/starting-your-subgraph/
+/ko/developing/creating-a-subgraph/subgraph-manifest/
 /ko/developing/developer-faqs/
 /ko/developing/graph-ts/api/
 /ko/developing/graph-ts/common-issues/
@@ -777,6 +845,7 @@
 /ko/firehose/
 /ko/glossary/
 /ko/graphcast/
+/ko/managing/delete-a-subgraph/
 /ko/managing/deprecate-a-subgraph/
 /ko/managing/transfer-a-subgraph/
 /ko/mips-faqs/
@@ -843,6 +912,12 @@
 /mr/deploying/subgraph-studio-faqs/
 /mr/deploying/subgraph-studio/
 /mr/developing/creating-a-subgraph/
+/mr/developing/creating-a-subgraph/advanced/
+/mr/developing/creating-a-subgraph/assemblyscript-mappings/
+/mr/developing/creating-a-subgraph/install-the-cli/
+/mr/developing/creating-a-subgraph/ql-schema/
+/mr/developing/creating-a-subgraph/starting-your-subgraph/
+/mr/developing/creating-a-subgraph/subgraph-manifest/
 /mr/developing/developer-faqs/
 /mr/developing/graph-ts/api/
 /mr/developing/graph-ts/common-issues/
@@ -852,6 +927,7 @@
 /mr/firehose/
 /mr/glossary/
 /mr/graphcast/
+/mr/managing/delete-a-subgraph/
 /mr/managing/deprecate-a-subgraph/
 /mr/managing/transfer-a-subgraph/
 /mr/mips-faqs/
@@ -916,6 +992,12 @@
 /nl/deploying/subgraph-studio-faqs/
 /nl/deploying/subgraph-studio/
 /nl/developing/creating-a-subgraph/
+/nl/developing/creating-a-subgraph/advanced/
+/nl/developing/creating-a-subgraph/assemblyscript-mappings/
+/nl/developing/creating-a-subgraph/install-the-cli/
+/nl/developing/creating-a-subgraph/ql-schema/
+/nl/developing/creating-a-subgraph/starting-your-subgraph/
+/nl/developing/creating-a-subgraph/subgraph-manifest/
 /nl/developing/developer-faqs/
 /nl/developing/graph-ts/api/
 /nl/developing/graph-ts/common-issues/
@@ -925,6 +1007,7 @@
 /nl/firehose/
 /nl/glossary/
 /nl/graphcast/
+/nl/managing/delete-a-subgraph/
 /nl/managing/deprecate-a-subgraph/
 /nl/managing/transfer-a-subgraph/
 /nl/mips-faqs/
@@ -989,6 +1072,12 @@
 /pl/deploying/subgraph-studio-faqs/
 /pl/deploying/subgraph-studio/
 /pl/developing/creating-a-subgraph/
+/pl/developing/creating-a-subgraph/advanced/
+/pl/developing/creating-a-subgraph/assemblyscript-mappings/
+/pl/developing/creating-a-subgraph/install-the-cli/
+/pl/developing/creating-a-subgraph/ql-schema/
+/pl/developing/creating-a-subgraph/starting-your-subgraph/
+/pl/developing/creating-a-subgraph/subgraph-manifest/
 /pl/developing/developer-faqs/
 /pl/developing/graph-ts/api/
 /pl/developing/graph-ts/common-issues/
@@ -998,6 +1087,7 @@
 /pl/firehose/
 /pl/glossary/
 /pl/graphcast/
+/pl/managing/delete-a-subgraph/
 /pl/managing/deprecate-a-subgraph/
 /pl/managing/transfer-a-subgraph/
 /pl/mips-faqs/
@@ -1064,6 +1154,12 @@
 /pt/deploying/subgraph-studio-faqs/
 /pt/deploying/subgraph-studio/
 /pt/developing/creating-a-subgraph/
+/pt/developing/creating-a-subgraph/advanced/
+/pt/developing/creating-a-subgraph/assemblyscript-mappings/
+/pt/developing/creating-a-subgraph/install-the-cli/
+/pt/developing/creating-a-subgraph/ql-schema/
+/pt/developing/creating-a-subgraph/starting-your-subgraph/
+/pt/developing/creating-a-subgraph/subgraph-manifest/
 /pt/developing/developer-faqs/
 /pt/developing/graph-ts/api/
 /pt/developing/graph-ts/common-issues/
@@ -1073,6 +1169,7 @@
 /pt/firehose/
 /pt/glossary/
 /pt/graphcast/
+/pt/managing/delete-a-subgraph/
 /pt/managing/deprecate-a-subgraph/
 /pt/managing/transfer-a-subgraph/
 /pt/mips-faqs/
@@ -1137,6 +1234,12 @@
 /ro/deploying/subgraph-studio-faqs/
 /ro/deploying/subgraph-studio/
 /ro/developing/creating-a-subgraph/
+/ro/developing/creating-a-subgraph/advanced/
+/ro/developing/creating-a-subgraph/assemblyscript-mappings/
+/ro/developing/creating-a-subgraph/install-the-cli/
+/ro/developing/creating-a-subgraph/ql-schema/
+/ro/developing/creating-a-subgraph/starting-your-subgraph/
+/ro/developing/creating-a-subgraph/subgraph-manifest/
 /ro/developing/developer-faqs/
 /ro/developing/graph-ts/api/
 /ro/developing/graph-ts/common-issues/
@@ -1146,6 +1249,7 @@
 /ro/firehose/
 /ro/glossary/
 /ro/graphcast/
+/ro/managing/delete-a-subgraph/
 /ro/managing/deprecate-a-subgraph/
 /ro/managing/transfer-a-subgraph/
 /ro/mips-faqs/
@@ -1212,6 +1316,12 @@
 /ru/deploying/subgraph-studio-faqs/
 /ru/deploying/subgraph-studio/
 /ru/developing/creating-a-subgraph/
+/ru/developing/creating-a-subgraph/advanced/
+/ru/developing/creating-a-subgraph/assemblyscript-mappings/
+/ru/developing/creating-a-subgraph/install-the-cli/
+/ru/developing/creating-a-subgraph/ql-schema/
+/ru/developing/creating-a-subgraph/starting-your-subgraph/
+/ru/developing/creating-a-subgraph/subgraph-manifest/
 /ru/developing/developer-faqs/
 /ru/developing/graph-ts/api/
 /ru/developing/graph-ts/common-issues/
@@ -1221,6 +1331,7 @@
 /ru/firehose/
 /ru/glossary/
 /ru/graphcast/
+/ru/managing/delete-a-subgraph/
 /ru/managing/deprecate-a-subgraph/
 /ru/managing/transfer-a-subgraph/
 /ru/mips-faqs/
@@ -1287,6 +1398,12 @@
 /sv/deploying/subgraph-studio-faqs/
 /sv/deploying/subgraph-studio/
 /sv/developing/creating-a-subgraph/
+/sv/developing/creating-a-subgraph/advanced/
+/sv/developing/creating-a-subgraph/assemblyscript-mappings/
+/sv/developing/creating-a-subgraph/install-the-cli/
+/sv/developing/creating-a-subgraph/ql-schema/
+/sv/developing/creating-a-subgraph/starting-your-subgraph/
+/sv/developing/creating-a-subgraph/subgraph-manifest/
 /sv/developing/developer-faqs/
 /sv/developing/graph-ts/api/
 /sv/developing/graph-ts/common-issues/
@@ -1296,6 +1413,7 @@
 /sv/firehose/
 /sv/glossary/
 /sv/graphcast/
+/sv/managing/delete-a-subgraph/
 /sv/managing/deprecate-a-subgraph/
 /sv/managing/transfer-a-subgraph/
 /sv/mips-faqs/
@@ -1330,6 +1448,79 @@
 /sv/supported-network-requirements/
 /sv/tap/
 /sv/tokenomics/
+/sw/about/
+/sw/arbitrum/arbitrum-faq/
+/sw/arbitrum/l2-transfer-tools-faq/
+/sw/arbitrum/l2-transfer-tools-guide/
+/sw/billing/
+/sw/chain-integration-overview/
+/sw/cookbook/arweave/
+/sw/cookbook/avoid-eth-calls/
+/sw/cookbook/cosmos/
+/sw/cookbook/derivedfrom/
+/sw/cookbook/enums/
+/sw/cookbook/grafting-hotfix/
+/sw/cookbook/grafting/
+/sw/cookbook/how-to-secure-api-keys-using-nextjs-server-components/
+/sw/cookbook/immutable-entities-bytes-as-ids/
+/sw/cookbook/near/
+/sw/cookbook/pruning/
+/sw/cookbook/subgraph-debug-forking/
+/sw/cookbook/subgraph-uncrashable/
+/sw/cookbook/substreams-powered-subgraphs/
+/sw/cookbook/timeseries/
+/sw/cookbook/transfer-to-the-graph/
+/sw/deploying/deploy-using-subgraph-studio/
+/sw/deploying/multiple-networks/
+/sw/deploying/subgraph-studio-faqs/
+/sw/developing/creating-a-subgraph/advanced/
+/sw/developing/creating-a-subgraph/assemblyscript-mappings/
+/sw/developing/creating-a-subgraph/install-the-cli/
+/sw/developing/creating-a-subgraph/ql-schema/
+/sw/developing/creating-a-subgraph/starting-your-subgraph/
+/sw/developing/creating-a-subgraph/subgraph-manifest/
+/sw/developing/developer-faqs/
+/sw/developing/graph-ts/api/
+/sw/developing/graph-ts/common-issues/
+/sw/developing/substreams-powered-subgraphs-faq/
+/sw/developing/supported-networks/
+/sw/developing/unit-testing-framework/
+/sw/firehose/
+/sw/glossary/
+/sw/graphcast/
+/sw/managing/delete-a-subgraph/
+/sw/managing/transfer-a-subgraph/
+/sw/network/benefits/
+/sw/network/contracts/
+/sw/network/curating/
+/sw/network/delegating/
+/sw/network/developing/
+/sw/network/explorer/
+/sw/network/indexing/
+/sw/network/overview/
+/sw/new-chain-integration/
+/sw/operating-graph-node/
+/sw/publishing/publishing-a-subgraph/
+/sw/querying/distributed-systems/
+/sw/querying/graphql-api/
+/sw/querying/managing-api-keys/
+/sw/querying/querying-best-practices/
+/sw/querying/querying-by-subgraph-id-vs-deployment-id/
+/sw/querying/querying-from-an-application/
+/sw/querying/querying-the-graph/
+/sw/querying/querying-with-python/
+/sw/quick-start/
+/sw/release-notes/assemblyscript-migration-guide/
+/sw/release-notes/graphql-validations-migration-guide/
+/sw/sps/introduction/
+/sw/sps/triggers-example/
+/sw/sps/triggers/
+/sw/subgraphs/
+/sw/substreams/
+/sw/sunrise/
+/sw/supported-network-requirements/
+/sw/tap/
+/sw/tokenomics/
 /tr/
 /tr/404/
 /tr/about/
@@ -1362,6 +1553,12 @@
 /tr/deploying/subgraph-studio-faqs/
 /tr/deploying/subgraph-studio/
 /tr/developing/creating-a-subgraph/
+/tr/developing/creating-a-subgraph/advanced/
+/tr/developing/creating-a-subgraph/assemblyscript-mappings/
+/tr/developing/creating-a-subgraph/install-the-cli/
+/tr/developing/creating-a-subgraph/ql-schema/
+/tr/developing/creating-a-subgraph/starting-your-subgraph/
+/tr/developing/creating-a-subgraph/subgraph-manifest/
 /tr/developing/developer-faqs/
 /tr/developing/graph-ts/api/
 /tr/developing/graph-ts/common-issues/
@@ -1371,6 +1568,7 @@
 /tr/firehose/
 /tr/glossary/
 /tr/graphcast/
+/tr/managing/delete-a-subgraph/
 /tr/managing/deprecate-a-subgraph/
 /tr/managing/transfer-a-subgraph/
 /tr/mips-faqs/
@@ -1435,6 +1633,12 @@
 /uk/deploying/subgraph-studio-faqs/
 /uk/deploying/subgraph-studio/
 /uk/developing/creating-a-subgraph/
+/uk/developing/creating-a-subgraph/advanced/
+/uk/developing/creating-a-subgraph/assemblyscript-mappings/
+/uk/developing/creating-a-subgraph/install-the-cli/
+/uk/developing/creating-a-subgraph/ql-schema/
+/uk/developing/creating-a-subgraph/starting-your-subgraph/
+/uk/developing/creating-a-subgraph/subgraph-manifest/
 /uk/developing/developer-faqs/
 /uk/developing/graph-ts/api/
 /uk/developing/graph-ts/common-issues/
@@ -1444,6 +1648,7 @@
 /uk/firehose/
 /uk/glossary/
 /uk/graphcast/
+/uk/managing/delete-a-subgraph/
 /uk/managing/deprecate-a-subgraph/
 /uk/managing/transfer-a-subgraph/
 /uk/mips-faqs/
@@ -1510,6 +1715,12 @@
 /ur/deploying/subgraph-studio-faqs/
 /ur/deploying/subgraph-studio/
 /ur/developing/creating-a-subgraph/
+/ur/developing/creating-a-subgraph/advanced/
+/ur/developing/creating-a-subgraph/assemblyscript-mappings/
+/ur/developing/creating-a-subgraph/install-the-cli/
+/ur/developing/creating-a-subgraph/ql-schema/
+/ur/developing/creating-a-subgraph/starting-your-subgraph/
+/ur/developing/creating-a-subgraph/subgraph-manifest/
 /ur/developing/developer-faqs/
 /ur/developing/graph-ts/api/
 /ur/developing/graph-ts/common-issues/
@@ -1519,6 +1730,7 @@
 /ur/firehose/
 /ur/glossary/
 /ur/graphcast/
+/ur/managing/delete-a-subgraph/
 /ur/managing/deprecate-a-subgraph/
 /ur/managing/transfer-a-subgraph/
 /ur/mips-faqs/
@@ -1583,6 +1795,12 @@
 /vi/deploying/subgraph-studio-faqs/
 /vi/deploying/subgraph-studio/
 /vi/developing/creating-a-subgraph/
+/vi/developing/creating-a-subgraph/advanced/
+/vi/developing/creating-a-subgraph/assemblyscript-mappings/
+/vi/developing/creating-a-subgraph/install-the-cli/
+/vi/developing/creating-a-subgraph/ql-schema/
+/vi/developing/creating-a-subgraph/starting-your-subgraph/
+/vi/developing/creating-a-subgraph/subgraph-manifest/
 /vi/developing/developer-faqs/
 /vi/developing/graph-ts/api/
 /vi/developing/graph-ts/common-issues/
@@ -1592,6 +1810,7 @@
 /vi/firehose/
 /vi/glossary/
 /vi/graphcast/
+/vi/managing/delete-a-subgraph/
 /vi/managing/deprecate-a-subgraph/
 /vi/managing/transfer-a-subgraph/
 /vi/mips-faqs/
@@ -1665,6 +1884,7 @@
 /yo/firehose/
 /yo/glossary/
 /yo/graphcast/
+/yo/managing/delete-a-subgraph/
 /yo/managing/deprecate-a-subgraph/
 /yo/managing/transfer-a-subgraph/
 /yo/mips-faqs/
@@ -1731,6 +1951,12 @@
 /zh/deploying/subgraph-studio-faqs/
 /zh/deploying/subgraph-studio/
 /zh/developing/creating-a-subgraph/
+/zh/developing/creating-a-subgraph/advanced/
+/zh/developing/creating-a-subgraph/assemblyscript-mappings/
+/zh/developing/creating-a-subgraph/install-the-cli/
+/zh/developing/creating-a-subgraph/ql-schema/
+/zh/developing/creating-a-subgraph/starting-your-subgraph/
+/zh/developing/creating-a-subgraph/subgraph-manifest/
 /zh/developing/developer-faqs/
 /zh/developing/graph-ts/api/
 /zh/developing/graph-ts/common-issues/
@@ -1740,6 +1966,7 @@
 /zh/firehose/
 /zh/glossary/
 /zh/graphcast/
+/zh/managing/delete-a-subgraph/
 /zh/managing/deprecate-a-subgraph/
 /zh/managing/transfer-a-subgraph/
 /zh/mips-faqs/